Last updated 15 September 2026

Privacy Policy

This is a founder-drafted policy describing how DealSafe actually handles data today, written to match the real system rather than boilerplate. It is not a substitute for review by a qualified solicitor before DealSafe accepts real users, and it should be kept in sync as the product changes.

1. Who we are

XLR8 operates DealSafe and is the data controller for the personal data described here, under UK GDPR and the Data Protection Act 2018.

2. What we collect

  • Account data: name, email, hashed password (we never store your password itself).
  • Deal data you choose to enter: brand names, deal values, payment schedules, commission rates, deliverables.
  • Contract-check flags you’re shown, and any deal details you separately choose to save (see Section 4).
  • If you opt in per deal: the original contract file, encrypted, kept in your Deal History until you remove it (see Section 4a).
  • Billing data via Stripe: we store your Stripe customer/subscription IDs, not your card details.
  • Usage and audit data: sign-ins, actions taken on sensitive records, IP address for security/rate-limiting.

3. What we don't build

We do not automatically keep a permanent store of your uploaded contracts — the default for every Contract Check is analyse-then-delete (Section 4). The only exception is your own explicit, per-deal choice to keep a contract in your Deal History (Section 4a); we never make that choice for you. We do not sell personal data, and we do not use your contract or deal content to train AI models without your explicit, separate opt-in.

4. Contract Check: the 5-minute deletion promise (the default)

When you upload or paste a contract, we run rule-based checks and send the extracted text to a third-party AI provider for structured analysis. By default, the original file and any extracted text are:

  • never written to disk — processed in memory only;
  • deleted from our systems within 5 minutes of analysis, enforced on three layers: an in-process timer, a scheduled cleanup job that catches anything a crash left behind, and a manual “delete now” control in the product;
  • never stored in our database — only the resulting flags (title, explanation, a short evidence quote) are kept, and only until you choose to save or discard them.

Where our AI provider processes your text, that processing follows their API data-handling terms. We do not promise our provider deletes data on the same 5-minute timeline as our own systems — we use the retention and no-training controls available to us and will update this policy if that changes.

4a. Deal History: keeping a contract on purpose

After a Contract Check, you can choose “Keep the original contract in my Deal History” for that specific deal. If you do, we store the file itself — encrypted with application-level AES-256-GCM before it is written to our database, in addition to our hosting provider’s disk-level encryption — and it is retained until you remove it from that deal (available at any time from the deal’s page) or delete your account. This never happens without you actively choosing it, deal by deal; the 5-minute deletion in Section 4 remains the default for everything else, including any deal where you don’t make this choice.

5. Encryption and security

  • All traffic to DealSafe is encrypted in transit (TLS).
  • Passwords are hashed with bcrypt, never stored in plain text.
  • Sensitive free-text fields we do persist (e.g. deal notes) use application-level AES-256-GCM envelope encryption, layered on top of our database provider’s disk encryption.
  • Access to your data is role-based and workspace-scoped, enforced on every server action and API route.
  • Sensitive actions (viewing a report, downloading an export, deleting data) are recorded in an audit log.

6. Who we share data with

Only the processors needed to run the service:

  • Our AI analysis provider — contract text you submit for analysis.
  • Stripe — billing and subscription management.
  • Resend — transactional email (verification, password reset, reminders).
  • Railway — hosting for our database, application, and background jobs.

We don’t share your data with any other third party for marketing purposes, and never sell it.

7. Your rights

Under UK GDPR you can ask us to:

  • export a copy of your personal data;
  • correct inaccurate data;
  • delete your account and associated data (request it from Settings — it’s logged and fulfilled, not just acknowledged);
  • restrict or object to certain processing;
  • complain to the UK Information Commissioner’s Office (ico.org.uk) if you think we’ve got something wrong.

8. Data retention

We keep account and deal-ledger data for as long as your account is active, plus a reasonable period afterward for legal/accounting reasons unless you request earlier deletion. Contract-check source text follows the 5-minute rule in Section 4 regardless of your account status, unless you opted to keep that specific contract in your Deal History (Section 4a), in which case it’s kept until you remove it or delete your account.

9. Cookies

We use a single essential session cookie to keep you signed in. We don’t use third-party advertising or tracking cookies.

10. Children

DealSafe is for creators 18 and over. We don’t knowingly collect data from anyone younger.

11. Changes to this policy

If this policy changes materially, we’ll notify active users by email before the change takes effect.

12. Contact

Questions or data requests: privacy@dealsafe.app (placeholder — update before launch).