Privacy Policy

Concordance · last updated 28 July 2026
Short version: the documents, suggestions, concerns, and notes you work with inside a Concordance hub are stored in your own browser, on your own device — not on a central server we operate.

1. What we collect, and where it goes

Concordance runs as a static application: the documents, suggestions, concerns, approvals, and notes you create are stored in your browser's local storage, on your own device. Nothing about the content of your negotiation is sent to or stored on our servers. Sharing between parties happens the way you choose to share it (WhatsApp, file export, email) — not through any server we control.

2. Front-door access (optional)

Where a deployment uses managed access (Cloudflare Access), we hold a list of the email addresses authorised to open that hub, so we can verify who's allowed in. That's the only personal data this feature involves — no names, no organisational data, just the email addresses an administrator has added.

3. Payment information

Where a deployment offers paid access, subscriptions are billed by Stripe. We never receive or store your card number. On a successful trial start or payment, we receive your email address from Stripe so it can be added to the front-door allow-list described above; if you cancel, it's removed.

4. Cookies and tracking

Concordance doesn't use advertising trackers or behavioural analytics. Local storage is used only to hold your own hub data on your own device, as described above.

5. Your rights

Since your document and negotiation data never reaches us, there's nothing for us to export or delete on your behalf for that content — it's already entirely under your control in your own browser. For access-list or billing data, contact us at the address below.

6. Changes

If this policy changes materially, we'll update the date at the top of this page.

7. Contact

Questions about this policy or your data: troyjeffries1970@gmail.com.

Terms of Service · Back to Concordance