Draft for legal review. This page is a working draft and has not yet been reviewed by a lawyer. It may change before it takes effect. Text in [square brackets] is still to be filled in.
Privacy policy
Last updated: 16 November 2026
This policy explains how [Company legal name] ("we", "us") handles personal data when you visit https://outflow.radivarius.com, create an account, or use Contract Radar (the "Service"). Contract Radar is a business tool sold to companies. It is not intended for consumers.
1. Who we are
[Company legal name], company ID [Company ID (EIK)], registered at [Registered address], Bulgaria. For anything about privacy, write to [privacy@your-domain.com]. We have not appointed a data protection officer because the GDPR does not require one for our processing; the contact above handles all data-protection requests.
2. Controller or processor
We play two different roles, and the rules differ for each:
- Controller for data about our own customers and visitors: account details, billing contacts, website and usage logs, and sales or support emails. This policy covers that data.
- Processor for the data our customers put into their workspace ("Customer Data"): uploaded contracts, vendor and tool lists, team members, and data read from connected accounting or sign-in systems. We process Customer Data only on the customer's instructions, under our Data processing agreement. If your employer uses Contract Radar and you have a question about your data in their workspace, please contact your employer first.
3. What we collect and why
| Data | Why we use it | Legal basis (GDPR Art. 6) |
|---|---|---|
| Name, work email, password (stored hashed), workspace and role | Create and secure your account, let teammates invite you | Contract (6(1)(b)) |
| Onboarding answers (company size, role, goals) | Set up your workspace and tailor suggestions | Contract (6(1)(b)) |
| Billing contact, company name, VAT number, invoices. Card details go straight to Stripe; we never see them | Charge for the subscription and keep tax records | Contract (6(1)(b)) and legal obligation (6(1)(c)) |
| IP address, browser, pages requested, error logs | Run the Service, keep it secure, fix problems | Legitimate interests (6(1)(f)): security and reliability |
| Emails you send us, call notes | Answer questions, support and sales | Legitimate interests (6(1)(f)) or steps before a contract (6(1)(b)) |
| Product emails you receive (renewal reminders, invites) | Deliver the reminders you switched on | Contract (6(1)(b)) |
We do not sell personal data, we do not use it for advertising, and we do not make decisions about people that have legal or similarly significant effects based solely on automated processing.
4. AI features
Contract Radar uses Claude, an AI model from Anthropic, to read uploaded contracts, pull out terms such as renewal dates and price caps, draft renegotiation emails, and name vendors found in accounting data. Contract text is sent to Anthropic's API for this and is not used by Anthropic to train its models under its commercial terms. AI output can be wrong: always check important dates and amounts against the contract itself.
5. Data from Google, Microsoft and accounting systems
If an admin in your company connects Google Workspace, Microsoft Entra ID, QuickBooks or Xero, we read only what is needed to find the software your company uses: user names and emails, which apps people sign in to and when, and vendor names, amounts and dates from bills and bank transactions. Access is read-only. We do not read email, files, chats or calendars. Sign-in tokens are stored encrypted, and an admin can disconnect at any time, which deletes the stored tokens.
Contract Radar's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve or train AI or machine-learning models, we do not transfer it to third parties except as needed to provide the Service or as required by law, and no person at [Company legal name] reads it unless you ask us to for support, it is needed for security, or the law requires it. User details from Google or Microsoft are never sent to Anthropic; only vendor and app names are.
6. Who we share data with
We use a small number of service providers (subprocessors) to host and run the Service, such as Supabase for the database (in Frankfurt), Vercel for hosting, Anthropic for AI, Resend for email and Stripe for payments. The full, current list, with what each one does and where, is on the Subprocessors page. We may also disclose data when the law requires it, to protect our rights, or to a buyer if the business is sold, who would be bound by this policy.
7. Transfers outside the EU
Our main database is in the EU. Some providers are based in the United States. Where data leaves the European Economic Area we rely on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses, with supplementary measures such as encryption in transit and at rest. You can ask us for a copy of these safeguards.
8. How long we keep data
- Account and workspace data: while the account is active. When a workspace is deleted we erase it within 30 days, and from backups within a further 90 days.
- Uploaded contract files: until the user or workspace deletes them.
- Invoices and billing records: 10 years, as Bulgarian accounting law requires.
- Server and security logs: up to 90 days.
- Support and sales emails: up to 3 years after our last contact.
9. Security
Data is encrypted in transit (TLS) and at rest. Each workspace is separated by database row-level security, so one customer cannot read another's data. Connector tokens are encrypted with a separate key. Access to production systems is limited to the people who need it. No system is perfectly secure; if a breach affects your personal data, we will tell you and the authorities as the GDPR requires.
10. Your rights
Under the GDPR you can ask to access, correct, delete or export your personal data, to restrict or object to our use of it, and to withdraw consent where we rely on it. Write to [privacy@your-domain.com]. We answer within one month. You can also complain to the Bulgarian Commission for Personal Data Protection (cpdp.bg) or the authority where you live or work.
11. Cookies
We use only cookies that are strictly necessary for the Service: a sign-in session cookie from Supabase and a cookie that remembers which workspace you have open. We do not use advertising or analytics cookies, so we do not show a cookie banner. If that changes, we will ask for consent first.
12. Changes
We will update the date at the top when this policy changes, and email account owners about any significant change before it applies.