Security & privacy · Draft prepared 17 November 2026

Your saved list is private by default.

Saved company numbers live in Duewell’s managed cloud database in the EU, with encryption and team-level access controls. This notice distinguishes current safeguards from proposed legal and operational arrangements.

Encrypted
Database storage is encrypted at rest. Connections to the published site and backend services use HTTPS/TLS.
Team-only access
Database rules restrict each saved list to signed-in members of that team. A public lookup never exposes list membership.
EU data region
The managed cloud database for this deployment is located in the European Union region eu-central-1.

01

Where your list is saved

When you follow a company, Duewell saves its company number, your team identifier and the date added in the managed Lovable Cloud database. This deployment’s database is in the EU region eu-central-1. It is not saved in a publicly readable table.

Company names, statuses, addresses and filing dates come from the public Companies House register. A separate shared cache stores that public information so companies can be refreshed efficiently; it does not store who added the company or which teams follow it.

CSV files stay on your device. When you upload a CSV, the browser reads the company numbers and saves only those numbers to your team list. The CSV file itself is not uploaded to storage. CSV and calendar exports are generated for you to download; once downloaded, you control those copies.

02

What is stored, and why

Account

Email address, account identifier, authentication/session records, signup and verification dates, and last successful login.

Why: To create and secure your account and sign you in, and administer authorised access.

Team and invitations

Team name, member email addresses, owner/member role, invited email addresses and timestamps.

Why: To share the right list with the right colleagues and administer access.

Saved company list

The team identifier, each saved Companies House number and the date it was added.

Why: To provide your tracker, calendar and exports.

Reminder preferences

Your on/off choice, notice period, and last checked/sent dates for each team.

Why: To apply your chosen notice period and prevent duplicate reminders.

Personal preferences

Your preferred tracking-list sort order, associated with your account.

Why: To restore your chosen view without changing colleagues' settings.

Public company cache

Company number, public register profile, status and filing dates, plus cache timestamps.

Why: To reduce Companies House requests and refresh company information. It does not record which user or team requested it.

Duewell does not sell account or saved-list data and does not use it for advertising.

03

Encryption and access

In transit and at rest

HTTPS/TLS protects information while it travels between your browser, the application and backend APIs. The managed database platform encrypts database storage at rest.

Passwords and secrets

Passwords are handled by the managed authentication service; plaintext passwords are never written into Duewell’s application tables. Companies House credentials and privileged keys are server-side secrets, not browser code.

  • Database-enforced team isolation. Signed-in members can read and change only lists for teams they belong to. These rules are enforced by the database, not just hidden in the interface.
  • Clear team permissions. Members can add and remove companies. Owners can also rename the team, invite or remove people, and cancel invitations. Reminder settings are private to each user.
  • Restricted privileged access. The shared Companies House cache is available only to server-side privileged code. Public lookup returns register data, never account or saved-list records.
  • Account administration. Team owners can see invitation history, signup dates, email-verification status and last successful login for members of their own team. Approved website administrators can view registered email addresses and account dates across the site for service administration. These checks are enforced on every request; neither area exposes passwords or session tokens.

04

Public lookup and shared links

Anyone can look up one company without an account. That search returns public Companies House information and does not reveal whether you or anyone else follows that company.

A shared calendar link is a confidential link

Anyone who has a team’s secret share URL can view that team’s name, followed companies and deadlines without signing in. It is view-only, but you should send it only to people who should see that information. Do not post it publicly.

The calendar feed URL works the same way: it is the same secret share token in a form your calendar app can subscribe to, so anyone holding it can read those deadlines as they are refreshed. Treat both links as confidential. The team owner can create a new one from the Team members page, which stops the old link and the old feed working straight away.

05

Service providers

The services below receive information as described. An EU database region does not mean every provider processes all information exclusively in the EU.

  • Lovable Cloud provides application hosting, the managed database, authentication, scheduled jobs, email infrastructure and visitor analytics. It processes the data needed to provide those services. Lovable’s privacy policy explains how it handles data.
  • Companies House receives the company number being looked up or refreshed and returns public register data. Your account email and team membership are not sent with those requests.
  • Google or Lovable sign-in processes authentication information only when you choose that sign-in method. Their own privacy terms apply.
  • Google Fonts supplies the typefaces used on the site. Your browser requests font files from Google, which receives technical request information such as your IP address and browser details.
  • Email delivery services process your email address, message content and delivery metadata when confirmation, recovery or enabled reminder emails are sent. Reminder messages, if activated, may contain your team name, company names and deadlines. Automatic reminders and strike-off/liquidation email alerts are not currently active. [PLACEHOLDER — confirm the configured sending provider and its processing terms before launch.]
  • Your calendar provider and export recipients receive the company/deadline information you download, share or subscribe to; a subscription also gives that provider your confidential feed URL. Their storage and retention are outside our control.

No advertising pixels or advertising trackers are configured in the application.

[SOLICITOR / OPERATOR REVIEW — confirm each provider’s contractual role, processor agreement, subprocessors and processing locations. Where personal data is transferred outside the UK or EEA, confirm an applicable adequacy decision or appropriate safeguards such as approved contractual clauses, a UK addendum or IDTA, and any required transfer assessment. These arrangements have not been independently verified for this deployment; an EU database alone does not establish them.]

06

Analytics and browser storage

Visitor analytics

Lovable’s analytics uses no cookies, stores nothing on the visitor’s device, doesn’t keep IP addresses and doesn’t identify visitors. Lovable collects this data for us. Lovable’s privacy policy explains how it handles it.

On the published site, it records pages visited, where visitors came from, their country, browser, operating system and device type, how long they stay, how fast pages load, errors, and which buttons and links they click. Click tracking is enabled. Button and link clicks, page visits, time on page, page speed and errors are recorded for every visitor, without cookies and without identifying anyone. The editor preview is not counted.

Detailed analytics data is kept for 90 days and daily summaries for a year.

No consent banner or Google Consent Mode connection is currently configured. The application reports runtime errors through Lovable’s error reporting; it does not send separate custom activity events. Error diagnostics can include the page, error message and stack trace. This reporting is covered by the errors described above, not an additional marketing profile.

Essential browser storage

Duewell uses browser storage for your sign-in session, your selected team and the short-lived destination used to return you after sign-in. This keeps you signed in and restores your view. It is not an advertising profile. Signing out clears the authentication session; you can also clear site data in your browser.

The session is kept in local storage while valid and refreshed while you remain signed in; the selected team remains until overwritten or you clear site data. The return destination uses session storage and is removed when used or when the browser session ends. External sign-in providers may use their own cookies on their sites. [SOLICITOR REVIEW — assess applicable browser-storage and communications rules for the markets served; this notice is not a determination that a banner is or is not legally required.]

07

Retention and deletion

  • Saved companies remain in a team list until a member removes them or the team is deleted.
  • Pending invitations remain until accepted or cancelled by a team owner. A separate invitation history retains invited addresses, invitation dates and outcomes for owner administration; cancellation does not erase that history.
  • Reminder preferences remain while the account and team record exist, so your choice can be applied on later checks.
  • Cached public company records are automatically removed after 30 days without a request.
  • Account and team records remain until deleted through the service operator.

[PROPOSED RETENTION POLICY — keep account, membership and preference records only while needed to provide the service, then delete or anonymise them within 30 days of an approved deletion request unless a documented legal obligation or dispute requires retention. Retain invitation history for up to 12 months after its outcome and operational/security logs for up to 90 days, unless necessary for a specific incident.] These are proposals, not implemented automatic deletion rules. [OPERATOR ACTION — approve the schedule, identify actual provider log retention and establish deletion procedures before launch.] The analytics periods above are separate provider periods.

Deleted live data may remain in restricted backups until they rotate out. [PLACEHOLDER — verify this deployment’s backup frequency, retention and restoration/deletion procedure with the provider before promising a specific period.] Exports and information retained independently by teammates or calendar providers are not erased by deleting an account. Deleting your saved list does not delete the underlying public Companies House records.

08

Your GDPR rights and controls

You can already export your saved list as a CSV, remove companies, leave a team, switch off reminders, and—if you own a team—cancel invitations or remove members.

Depending on the circumstances, data protection law can give you rights to request access, correction, deletion, restriction, objection and data portability. You can object to processing based on legitimate interests, and withdraw consent for any future consent-based processing without affecting prior lawful use. Rights are subject to applicable exceptions; portability applies to eligible data, not necessarily every record we hold. Corrections to official register data should also be raised with Companies House.

For account-level exports, account deletion or requests not covered by the in-app controls, use the privacy contact in the legal-details panel once supplied. We may need proportionate identity checks, but will not ask for your password. Under UK GDPR, requests are normally answered within one month; a lawful extension of up to two further months may apply to complex or numerous requests, with reasons given within the first month. Requests are normally free, subject to statutory exceptions. [OPERATOR ACTION — establish a monitored contact and verified request-handling procedure before launch.]

The operator identified above is the proposed controller for accounts, security and service administration. A team’s organisation may separately control personal data it chooses to monitor or share. [SOLICITOR REVIEW — determine whether the operator acts as a processor for any team-provided data and whether a separate data-processing agreement is required; suppliers may also act as independent controllers for some activities.]

You may complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint, or another competent local supervisory authority, without first exhausting our complaints process.

09

Purposes and lawful bases

[PROPOSED LAWFUL BASES — solicitor to confirm these against the operator’s actual activities before adoption.] Under the proposed UK GDPR approach:

  • Providing an individual user’s service: account creation, sign-in, saved lists, calendars, preferences and requested reminders may rely on performance of a contract, only where necessary for a contract with that individual.
  • Organisational accounts and invitations: managing colleagues’ access and contact details may rely on legitimate interests in providing the organisation’s requested service. An invitation address is supplied by a team owner, rather than directly by the invited person.
  • Security and administration: preventing misuse, controlling access, maintaining invitation history and investigating faults may rely on legitimate interests in running a secure and reliable service, subject to necessity and a documented balancing assessment.
  • Public register information: company, officer and PSC information comes from Companies House. Public availability does not remove data-protection obligations; processing personal data for monitoring may rely on legitimate interests, subject to assessment and any applicable indirect-collection transparency obligations.
  • Legal obligations: necessary record keeping or disclosure may rely on a specific legal obligation, where one applies; it is not a general permission to retain all data indefinitely.

Anonymous visitor counting is described separately above. No marketing-email programme or automated decision making with legal or similarly significant effects is currently configured. Reminder settings are service preferences, not consent to marketing. If marketing or other consent-based processing is introduced, a separate lawful choice and withdrawal mechanism will be required.

Account details are needed to provide saved monitoring; without them you can still use public lookup. Team invitations and public-register data are received indirectly as described above. The service does not request identity documents or complete identity verification; it displays reported public statement requirements.

10

Disclosures, incidents and changes

Team members can see the team’s shared tracking information; owners can see their own team’s account and invitation dates. Approved website administrators can see account emails and dates for administration. Public calendar recipients receive only the information exposed by the confidential link, not account credentials.

[PROPOSED POLICY — disclose personal data outside the providers and authorised recipients described above only where necessary for a legal obligation, a legitimate and proportionate security investigation or a lawful business transfer with appropriate safeguards and notice.] This is not permission for unrestricted disclosure or sale of your data.

No service can guarantee absolute security. [OPERATOR ACTION — document incident response, access reviews and breach handling before launch.] Where UK GDPR applies, a notifiable personal-data breach must be reported to the relevant authority without undue delay and, where feasible, within 72 hours of awareness; affected people must be informed without undue delay where the breach is likely to result in a high risk to their rights and freedoms, subject to legal exceptions.

[PROPOSED POLICY — show the updated date on material revisions and provide additional notice where legally required; do not retrospectively authorise incompatible uses of personal data.] Review this notice alongside the draft Terms & conditions. The operator identity, contact, lawful bases, provider agreements, transfer safeguards and retention procedures must be approved before the draft is finalised.

A note on shared responsibility

Use a strong, unique password, keep your email account secure, review team membership regularly and treat shared calendar links and exported files as confidential. No online service can promise absolute security, but clear controls and limited access reduce risk.