Seeing the wrong customers
Roles come from Account, set once and followed here. Read-only seats see what their role allows and can change nothing.
CENTILIO RELATE / SELL · EMBER
The question that decides whether a CRM gets used.
"Will my whole company see my inbox?" Every seller asks it, most CRMs answer it badly, and the ones that answer it badly end up with half the conversations outside the record. Relate syncs email per person and shares it per thread , not per mailbox. This page is that answer, and the rest of what Relate is designed to protect.
proposed per-thread privacycustomer-level visibilitysecurity targets, not certificationsroles proposed from Account
Product design preview · Relate has not shipped. All features, screens and prices are proposals.
Relate has not shipped yet.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Relate is not available yet. These are proposed screens, features and prices—not a beta or live CRM. All console actions affect fictional data in this page only.
Your mailbox is not the company's mailbox
Per person, per thread.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Email sync is set up by each person for their own mailbox, and every thread carries a choice: shared with the customer record, or private to you. Shared threads land where the next person needs them; private ones never leave your mail client. The default is that nothing is shared until you say so, and the choice can be changed on a thread after the fact.
This is a design decision, not a setting we buried. A CRM that quietly publishes a seller's inbox to their manager gets used for a fortnight.
What is designed against what
The six that matter in a CRM.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
The private thread
Per-thread sharing, defaulting to private, changeable after the fact. Your sent items stay yours.
The person who left
Contacts belong to companies and records belong to the business, not to a mailbox. When someone leaves, the relationship does not walk out with them — and their private threads do not become the company's either.
Being scored
Celia scores deals and pipelines, never people. No lead score attached to a human being, no ranking of your team, no inference about character from response times.
The export you cannot get
Every field, every note, every timeline entry, on every plan including Free, any time. Export is a right, not a retention lever.
Not knowing who saw what
Who viewed a customer, who changed a field, who moved a deal, who exported — with who, when and from where. CSV on Business.
Celia, and the limits on it
Written down so we can be held to them.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Celia works inside your organisation. It drafts, summarises, scores and notices. It never trains on your data, never sends a message to a customer by itself, never moves a deal stage, and never scores a person. Every draft it produces shows what it was drawn from, and a person approves before anything leaves.
Where it is wrong — and it will be — you should be able to see why in one click. That is a design requirement, not a nice-to-have, and it is the reason the console on the overview page shows what filed itself and what a person typed.
Standards
The same platform as Sign, Vault and Account.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Encrypted in transit and at rest on AWS and Google Cloud, inside your organisation's space; passkeys, MFA and device rules come from Account. Indian accounts will be able to ask for India residency on Enterprise. None of this is running yet — Relate is not built — and the page will be rewritten with what is actually true on the day it ships.
- ISO 27001-aligned controls · proposed, unverified
- GDPR · proposed, unverified
- DPDP Act 2023 · proposed, unverified
- AES-256 at rest · proposed, unverified
- TLS 1.2 · 1.3 · proposed, unverified
- SSO through Account · proposed, unverified
Questions
About privacy, roles and Celia.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Will my whole company see my inbox?
Proposed design, not an implemented control: No, and this is the question that decides whether a CRM gets used. Email sync is per person, and the choice about what the team sees is per thread, not per mailbox. A private thread stays private; a shared thread lands on the customer record where the next person needs it.
Who can see which customers?
Proposed design, not an implemented control: Whoever the roles in Account allow. Roles are set once, in one place, and followed here — not maintained twice. Read-only seats see what their role allows and change nothing.
Where does my data live?
Proposed design, not an implemented control: In your organisation's space, encrypted in transit (TLS 1.2 and 1.3) and at rest (AES-256), on AWS and Google Cloud; Indian accounts will be able to ask for India residency on Enterprise.
Does Celia train on my customers' data?
Proposed design, not an implemented control: No. It works inside your organisation to draft, summarise and notice. Nothing of yours trains anything, nothing leaves, and nothing is sent to a customer without a person approving it.
Does Celia score people?
Proposed design, not an implemented control: It scores deals and pipelines, never individuals. No lead score attached to a human being, no ranking of your team, no inference about a person's character from how they answer email.
What is on the audit trail?
Proposed design, not an implemented control: Who saw a customer, who changed a field, who moved a deal, who exported what, and when. On Business it exports as CSV.
Can I get my data out?
Proposed design, not an implemented control: Every field, every note, every timeline entry, on every plan including Free, any time. Export is a right, not a retention lever.
Next for you
What people add after Relate.
The tools Relate sits between. Check each product’s current stage while Relate is built.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
The proposed shared record connects these products as they launch. Follow each product page for its current stage.
Account live
Who may see which customers, set once
Sign live
The quote on the record, signed in minutes
Bill next wave
The signed quote, invoiced without retyping
Drive live
Every file about this customer, filed
Pulse next wave
Outreach whose replies land on the record
Book next wave
The meeting the next step needs
Be told when Relate opens.
Design targets only: Relate has not been built or independently security-audited. The controls described here are proposals, not verified certifications or a claim of legal compliance.
Wave 2 is the next build after the currently available tools. Leave your name and you will hear before the announcement — and tell us what your CRM actually has to do while it is still being designed.