Security
How Reachio protects your clients’ accounts and data.
Reachio holds the keys to your clients’ social and ad accounts. This page says how we keep them safe, what we store, for how long, and what is not there yet.
Hosting in the EU
- Reachio’s servers are in the EU (France). Talivio Technology OÜ, the company behind Reachio, is registered in Estonia.
- Some AI model providers reached through the Talivio AI gateway are outside the EU; they are listed with the sub-processors below.
- Transfers outside the EU/EEA rely on adequacy decisions or standard contractual clauses.
Encryption and secrets
- All traffic uses TLS.
- Platform tokens and secrets are encrypted at rest and never sent to the browser.
- API keys are shown once; Reachio keeps only a SHA-256 hash and a 12-character prefix to recognise them.
- Team invitations and client connect links are stored as SHA-256 hashes too; AI assistant connections keep only token identifiers.
- Error messages are scrubbed of secrets, and platform responses are never written to the audit log.
Platform connections
- You or your client sign in on the platform’s own page; Reachio never sees a password.
- Each sign-in is bound to the browser that started it and can be used only once; PKCE is used where the platform supports it.
- Connections are checked every hour: tokens are refreshed, and owners are warned before one expires.
- Disconnecting deletes the token at once and revokes it at the platform where the platform allows it (Google, X).
Access, roles and approvals
- Each agency’s data is kept apart by three separate checks: every screen, every query and every saved record is limited to that agency.
- Six roles: owners and admins manage the team; managers manage brands, connections and approvals; editors make content; client approvers and client viewers see only their own client’s brands.
- Posts, campaign launches and every ad change that raises spend wait for approval; editing after approval voids it.
- API keys and AI assistant connections act as the member who made them, with that member’s role, and can be limited to one brand, given an expiry and revoked.
Audit log
- Every change of state is written to the audit log: who, what and when.
- Ad changes are change sets with their reason, the values before and after, who approved them and a 7-day undo.
- Actions taken through the API or an AI assistant are recorded as such.
AI and your data
- AI features go through the Talivio AI gateway; Reachio holds no AI provider keys of its own.
- Only the content needed for the requested output is sent, without the names or e-mail addresses of your users.
- Customer content and connected account data are not used to train shared AI models, and our AI providers are contractually prohibited from training on it.
Your website visitors
- The tag loader loads nothing third-party before the visitor chooses.
- Visitor events are stored without IP addresses; e-mail and phone only as SHA-256 hashes and only with marketing consent.
Data processing agreement
For data you bring into Reachio we act as your processor under Talivio’s Data Processing Agreement. Reachio’s privacy addendum says what each platform connection reads.
Sub-processors
Hosting: Contabo GmbH (servers in France). Network and security (TLS, DDoS protection, content delivery): Cloudflare, Inc. Email: our own mail server (Contabo, France). AI: the model providers listed in Annex 3 of our DPA, reached through the Talivio AI Gateway; some are outside the EU. Payments: Stripe Payments Europe Ltd., reached through Talivio Pay (Talivio's payment gateway at talivio.com); Stripe receives the card and billing details and the VAT number, while Reachio keeps only the Stripe customer and subscription identifiers, the plan and the subscription status. Platforms themselves (Meta including Threads, Google, LinkedIn, TikTok, X, Microsoft, Pinterest, Apple, Telegram, Bluesky) receive data only when the user asks Reachio to send it to them (for example to publish a post) and process it under their own terms. Phone notifications travel through the push service of the user's browser (Apple, Google, Mozilla or Microsoft), end-to-end encrypted so that the push service cannot read them. Transfers outside the EU/EEA rely on adequacy decisions or standard contractual clauses.
Quoted from section 12 of the Reachio privacy addendum (English), so this list and the legal text never differ. Reachio privacy addendum
How long we keep data
Reachio enforces these periods itself, every day:
| Data | Kept for |
|---|---|
| Inbox messages and comments | 12 months |
| Names of people commenting on YouTube | 30 days |
| YouTube data after the channel is disconnected | 7 days |
| Other channels’ mirrored posts, figures and inbox after disconnecting | 30 days |
| Data of a connection whose access was revoked at the platform | 30 days |
| Google Ads change history (with the e-mail of the person who made a change) | 13 months |
| Website visitor events | 30 days |
| Client report links work without a login for | 90 days |
Closing a workspace: its owner writes to [email protected]; we delete the workspace data within 30 days and backups within a further 35 days.
Not there yet
- Two-factor sign-in.
- Closing a workspace yourself in the app (write to us instead).
- An independent security certification such as SOC 2 or ISO 27001.
Report a security issue
Found a vulnerability? Write to the address in talivio.com/.well-known/security.txt. Please do not access other customers’ data, degrade the service or publish details before we have fixed it; we reply, keep you updated and credit you if you wish.
security.txt [email protected]
Privacy questions: [email protected].
Bring your first brand in.
Free early access, no card.