Privacy Policy

For account data — the information you give us when you sign up, subscribe, and use the platform — we act as the data controller.

For customer content — investor contact records, uploaded documents, campaign material, and mailbox messages our customers bring into the platform — the customer is the data controller and we act as their processor. We handle that data only on the customer's instructions, as set out in our Terms of Service and data processing terms. If you are an investor whose details a customer has uploaded, that customer is responsible for having a lawful basis to hold and use your data; we describe below what we do on their behalf and how to reach us directly.

Account data. Name, work email address, and sign-in credentials, managed through our authentication provider (Clerk). If you sign in with Google, we receive your name, email, and profile image from Google.

Billing data. Subscription tier, invoices, and payment status via Stripe. Card numbers are entered directly with Stripe and never touch our servers.

Customer content. Investor contact records (names, firms, roles, work email addresses, investment preferences) uploaded by customers via CSV or entered manually; documents added to the knowledge base; and the emails composed and sent through the platform, including delivery, open, and reply events.

Connected mailbox data. If a customer connects a Gmail or Microsoft Outlook account, we store OAuth tokens (encrypted with AES-256-GCM) and sync messages from the connected mailbox so replies can be tracked and threaded. We access only the scopes the customer grants during the OAuth flow, and mailboxes can be disconnected at any time in Settings.

Usage data. Logs of platform activity (pages visited, actions taken, API errors) used for security, debugging, and metered billing.

• To provide the platform: storing investor records, managing campaigns, and tracking outreach.
• To draft and classify email on the customer's behalf using AI models (see section 4).
• To send email the customer approves, through Resend or the customer's own connected Gmail or Outlook account.
• To operate billing, enforce plan limits, and prevent abuse.
• To provide support and communicate service updates.

We do not sell personal data, and we do not use customer content for advertising.

Proteus One uses large language models to draft outreach, classify replies, and answer diligence questionnaires. Customer content is sent to Anthropic (Claude models) for text generation and classification, and to OpenAI for text embeddings used in search and matching.

Data sent to these providers is processed under data processing agreements that prohibit its use for training their models. AI requests are scoped to a single organisation — content from one customer is never used in another customer's context.

We use the following subprocessors to run the service:

• Supabase — database and file storage (Frankfurt, Germany — EU).
• Vercel — application hosting and delivery.
• Clerk — authentication and account management.
• Stripe — payments and subscription billing.
• Resend — transactional and outreach email delivery.
• Anthropic — AI text generation and classification.
• OpenAI — text embeddings.
• Google and Microsoft — mailbox sync, only when a customer connects a Gmail or Outlook account.

Our primary data store is hosted in the EU (Frankfurt, eu-central-1). Some subprocessors process data in the United States; where they do, transfers rely on the EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework.

Our customers use Proteus One to contact institutional investors about their funds. If you received such an email, the sender — not Proteus One — chose to contact you and controls your data. Every commercial email sent through the platform carries an unsubscribe link; using it adds your address to a suppression list that blocks all further outreach to you from that sender through our platform.

You can also contact us at [PRIVACY CONTACT EMAIL] and we will relay your request to the customer concerned, or suppress your address directly where we are able to.

Account data is kept for as long as the account is active. Customer content is retained under the customer's control: customers can delete investor records, documents, and campaigns at any time, and deletion takes effect immediately in the live database. When an account is closed, we delete the organisation's content within 30 days, except records we must keep for legal, billing, or suppression-list purposes.

If you are in the EU or UK, you have the right to access, rectify, erase, restrict, and port your personal data, and to object to processing based on legitimate interests. California residents have comparable rights under the CCPA. To exercise any of these rights, contact [PRIVACY CONTACT EMAIL]. Where we act as a processor for a customer, we will forward your request to them and assist with their response.

You also have the right to lodge a complaint with your local supervisory authority ([SUPERVISORY AUTHORITY] for our lead establishment).

Data is encrypted in transit (TLS 1.3) and at rest. OAuth tokens and other stored secrets are additionally encrypted at the application layer with AES-256-GCM. Database access is scoped per-organisation with row-level security. Read more on our Security page.

We use only the cookies required to run the service — authentication and session cookies set by Clerk, and anti-fraud cookies set by Stripe during checkout. We do not use third-party advertising or cross-site tracking cookies.

We will post any changes to this policy on this page and update the date above; material changes will be notified to account holders by email. Questions about this policy or our data practices: [PRIVACY CONTACT EMAIL], or write to [COMPANY LEGAL NAME], [REGISTERED ADDRESS].