Security and privacy

Cece sees what you cc it on, and nothing else

A scheduling assistant needs some access to your calendar and your threads. Here is exactly what Cece can see, what it keeps, for how long, and where we are on independent reviews, in plain language.

What Cece can see, and what it can't

Cece has its own mailbox. It only receives the emails people send or copy to it. It never connects to your inbox.

Cece can see

Emails sent to your assistant's address, including threads you cc it on
Your Google Calendar events, so it can check when you're free, book meetings and move them
Free/busy on the calendars you choose, and your list of calendars (read only)
Your name, email address and profile photo from Google sign-in
The rules, contacts and preferences you set in the portal

Cece never sees

Your Gmail inbox. Cece doesn't ask for any Gmail permission on your account.
Threads you didn't cc it on, even with people it has emailed before
Your contacts, Drive files or documents
Your Google password. Sign-in goes through Google.

Your calendar, your meetings. When Cece books a meeting, the event is created on your calendar with you as the organizer, the same as if you had made it. If you stop using Cece, your meetings stay where they are.

What Cece keeps, and for how long

Cece keeps the minimum it needs to do the job and to show you what it did.

Default retention periods during the beta
What	Kept for
Original emails as received	30 days
Email text and Cece's drafts	90 days by default. You can choose anything from 30 to 365 days.
Activity log of what Cece did and why	As long as your account is open. Message content is removed from log entries after 90 days.
Requests sent to the AI model	30 days, for debugging and quality checks
Backups	30 days, then overwritten

Export and deletion

You can export your data from the portal at any time. When you delete your account, your encryption keys are destroyed straight away, which makes your stored content unreadable, and the data itself is deleted within 30 days, including from backups.

Encryption

All traffic to and from Cece is encrypted in transit (TLS 1.2 or later).
Data at rest is encrypted, and each account's content is encrypted with its own key. Keys are managed in a cloud key management service, not stored next to the data.
The tokens that let Cece reach your calendar are encrypted separately, and you can revoke them from your Google account at any time.
Data is stored in the United States.

The AI model

Cece uses large language models from Anthropic to read replies and write emails. Anthropic processes this data under zero data retention terms and does not train its models on it. We don't train models on your data either.

The AI doesn't decide when you're free. Every time Cece offers is checked against your calendar by ordinary code, and checked again just before an email is sent.

Staff access

By default, nobody at Cece can read your threads.

Support: if you ask for help with a thread, you can grant access to that one thread for 24 hours. The access is logged, and you can see it in your activity log.
Emergencies: in a serious incident, an engineer can request time-limited access. It needs a second person to approve it, and you're told.

Email safety

An assistant that acts on email has to be careful about who it listens to. Cece:

Only takes instructions from you, and only after checking the email really came from you (SPF, DKIM and DMARC). If an email claiming to be from you fails those checks, Cece treats it as coming from a stranger.
Lets other people do only what makes sense on their own thread: accept a time, decline, or suggest another time. They can't change your rules, see your calendar or move other people's meetings.
Shares free or busy times only. It doesn't reveal what your other meetings are or who they're with.
Treats text inside emails as content, not commands, and is tested against attempts to trick it.

You stay in control

New accounts start at "Approve all", so nothing is sent until you approve it.
Anything involving money, legal commitments or sharing calendar details always comes to you, whatever level you choose.
Every action in the activity log shows the rule behind it, and most can be undone in one click.

Audits and status

Cece is a young product in private beta. We'd rather tell you where things actually stand than show badges we haven't earned.

Security and compliance status
Item	Status
SOC 2 Type I	Planned Planned before Team plans. Cece is not SOC 2 certified today.
SOC 2 Type II	Planned After Type I
Independent penetration test	Planned Planned before public launch
Google OAuth app verification	Planned To be submitted to Google during the beta
Privacy policy, terms and DPA	In progress Being written with counsel. See the draft privacy policy.
Data location	By design United States
Encryption in transit and at rest, per-account keys	By design Part of how Cece is built, not an external certification

Report a security problem

If you think you've found a vulnerability, please email admin@cece.to with "Security report" in the subject. Tell us what you found and how to reproduce it. Please give us a reasonable chance to fix it before sharing it publicly, and don't access other people's data. We'll reply to every report.

Received an email from Cece and want your data removed? See the guide for recipients.