Draft — must be reviewed by a lawyer before launch
This text describes what Realy actually does today, but it has not been legally reviewed and contains placeholders. It is not yet a binding legal document.
Legal
Privacy Policy
Last updated: November 20, 2026
This policy explains which personal data Realy collects, why, who receives it and which rights you have. It covers the Realy website and application (the "Service").
1. Who is responsible
The controller for account, billing and website data is [company legal name / address / email].
For business data that customers put into Realy (for example their leads, contacts, employees, tickets or chat visitors), the customer company is the controller and we act as its processor under the Data Processing Agreement.
2. Data we process
- Account data: name, email address, password (stored only as an Argon2 hash), language, time zone, two-factor authentication factors and recovery codes (stored protected), sign-in method (email/password, Google or Microsoft sign-in, or company SSO).
- Session and security data: a session record per sign-in (with IP address and browser user agent), sign-in attempts, rate-limit counters and an audit log of important actions.
- Organization and company data: company profile, members, roles and permissions, and settings.
- Business data you enter or import: CRM records, marketing content and campaigns, finance and HR records, projects, support tickets, live-chat conversations, documents and files.
- Integration credentials: access tokens and API keys for the services you connect. They are encrypted at rest and never shown again.
- AI data: instructions you give AI employees, the context they read through tools, their outputs, approvals and usage (token counts).
- Billing data: plan, billing country, tax details and invoices. Card details are entered at Stripe and never stored by us.
- Email interaction data: when you send marketing email through Realy, opens (tracking pixel) and clicks (redirect links) are recorded, and recipients can unsubscribe with one click.
- Technical logs and error reports needed to run and secure the Service.
3. Why we process it (legal bases)
- To provide the Service you signed up for — contract (GDPR Art. 6(1)(b)).
- To secure the Service, prevent abuse and keep audit trails — legitimate interests (Art. 6(1)(f)) and, where applicable, legal obligations (Art. 6(1)(c)).
- To bill you and keep accounting records — contract and legal obligation.
- To send service emails (sign-in, password reset, invitations, notifications and briefings you subscribe to) — contract.
- Product announcements or marketing emails, if any — consent or legitimate interests, always with an opt-out.
4. AI processing
AI employees and AI tasks send the instructions and the business context they need to the AI provider configured by the operator (Anthropic's Claude API). Some features (quick rewrites, summaries, translations, images, research, contact data) use providers that your company connects under Integrations, such as OpenAI, Google Gemini, Tavily, Exa, SerpAPI, Apollo, Hunter, People Data Labs, Stability AI, Replicate or Runway; these are only called when connected and your contract with them applies.
AI actions that change data or contact people require a person's approval unless your company enables Auto mode for that kind of action; automatic actions are logged and can be reviewed. AI output can be wrong and should be checked.
5. Who receives data
We use the sub-processors listed below. Services you connect yourself under Integrations (for example Google, Microsoft, Slack, HubSpot, Salesforce, social networks and ad platforms, Shopify, WordPress, Webflow, SendGrid, Mailchimp, Twilio, WhatsApp, Vapi, Retell, Razorpay, QuickBooks, Xero, your own S3-compatible storage) receive the data needed for what you ask them to do.
We do not sell personal data and do not use it for advertising.
6. International transfers
Some providers process data outside the EU/EEA (notably in the United States). Where that happens we rely on an adequacy decision (such as the EU-U.S. Data Privacy Framework for certified providers) or Standard Contractual Clauses. Each company records a data region; [describe where data is actually hosted for each region].
7. How long we keep data
- Account and business data: for as long as the account exists, then deleted [within N days] unless the law requires us to keep it.
- Sessions, one-time links and idempotency records: until they expire; expired records are purged automatically.
- Audit logs and invoices: [retention period] as required for security and accounting.
8. Your rights
Under the GDPR (and similar laws) you have the right to:
- Access — get a copy of the personal data we hold about you.
- Rectification — have inaccurate data corrected (most profile data can be edited in Settings).
- Erasure — have your data deleted where there is no legal reason to keep it.
- Restriction — ask us to limit processing while a request or objection is being handled.
- Portability — receive data you gave us in a structured, machine-readable format.
- Objection — object to processing based on legitimate interests, and at any time to direct marketing.
- Withdraw consent — where processing is based on consent, without affecting earlier processing.
- Complaint — lodge a complaint with your local data protection supervisory authority.
To exercise them, contact [company legal name / address / email]. We answer within one month.
9. Cookies
We use only strictly necessary and preference cookies and no analytics or advertising cookies. See the Cookie Policy.
10. Security
Passwords are hashed with Argon2, integration credentials are encrypted at rest, sessions are httpOnly cookies, and two-factor authentication is available (required for platform administrators). Access to business data is limited by roles and permissions within each company.
11. Changes
We will post changes on this page and, for material changes, notify account owners by email.
Sub-processors
- [Hosting provider, e.g. Vercel] — Hosting of the web application (Always).
- [Database provider] — PostgreSQL database storing all account and business data (Always).
- [Redis provider] — Background job queues and rate limiting (short-lived job data) (When background work is enabled).
- [Worker hosting, e.g. Render / Fly.io] — Background worker running scheduled and AI jobs (When background work is enabled).
- Anthropic (Claude API) — AI employees and AI tasks: prompts with the business context needed for the task (When the operator configures an Anthropic API key).
- Resend or Postmark — Transactional email (sign-in, password reset, invitations, notifications, briefings) (When the operator configures an email provider).
- Stripe — Subscription billing, payment methods, invoices and tax (When billing is enabled).
- Sentry — Error reports (no cookies, headers, request bodies or user details are sent) (When the operator configures a Sentry DSN).
- [OpenTelemetry collector] — Technical traces and metrics (When the operator configures an OTLP endpoint).