Skip to content

Security

How Titus Core is being built to protect your email

Titus Core is in development. This page sets out the design commitments it is being built to, and what is running today. We'll keep it up to date as the product is built.

Design commitments

An assistant that can act on your mailbox has to be trustworthy in two ways: it must never do more than you asked, and it must never keep more than it needs. These are the rules the product is being built around.

  • Hosted on Google Cloud, in the US

    Titus Core will run on Google Cloud, through Firebase, in Google's data centers in the United States.
  • Encrypted in transit and at rest

    Every connection to Titus Core will use HTTPS, and Google Cloud will encrypt the little we store at rest.
  • Every action goes through our server

    Your browser will never talk to your mailbox or our database directly. Every command will go to our server, which will check who you are before anything is read or changed.
  • One permission, and never permanent deletion

    Titus Core will ask for a single Google permission: to read, organize and reply from your mailbox, and to move email to the Trash. That permission cannot permanently delete anything, so neither can Titus Core. Outlook mailboxes, when they come, need Microsoft's mail permission, which could; Titus Core will have no command that does, and will only move email to Deleted Items.
  • A spoken yes before anything bulk or outgoing

    Clearing out a sender, sending a reply, adding someone to it, and creating a new label will each wait for your confirmation in a turn of its own. The server will enforce it, not just the assistant.
  • Email is treated as untrusted

    An email can try to give the assistant instructions. Titus Core will treat everything in a mailbox as data, never as a command; there will be no forward command in the first version; and a reply will only go to people already on the thread unless you confirm a new one.
  • Nothing copied, nothing kept

    Titus Core will read from your mailbox during a session and act on it there. It won't copy your email into its own database, and it won't keep the text it read aloud or drafted. Session records (what ran, not the words) will be deleted after 30 days.
  • Logs without content

    Our server logs will record that a command ran and whether it succeeded, by codes, never the text of an email, a reply, or anything you said.
  • Encrypted, revocable access

    The token that lets Titus Core act on your mailbox will be stored encrypted and unreadable by any browser. Disconnecting, from Titus Core or from your Google account, will revoke it at Google at once.

What's running today

Right now there is this website, its waitlist, and accounts for the people we have invited so far. Connecting a mailbox, and the voice assistant that reads it to you, are being tested with a small number of accounts.

  • When you join the waitlist or create an account, your details go over HTTPS to our server, which checks them before storing them. No browser can write to our database, and the only things a signed-in browser can read from it are that person's own profile and the address and state of their own mailbox connection.
  • A connected Gmail mailbox is reached with one Google permission, which cannot permanently delete email. An Outlook mailbox is reached with Microsoft's mail permissions, which could; Titus Core has no command that does, and moves email only to Deleted Items. The token is stored encrypted (AES-256-GCM), with the key kept apart from the database, where no browser can read it. The Inbox page shows your email and stores none of it. Disconnecting deletes the token, and asks Google to withdraw a Gmail permission.
  • In an assistant session, our server carries out each command and keeps only what ran: message ids, command names and outcomes, deleted after 30 days. Clearing out a sender, sending a reply, adding someone to it and creating a label happen only after a yes the server itself recognized, for the exact action it asked about. Email reaches the language model as information, never as instructions, and there is no forward command.
  • To tell you what's new, our server accepts Gmail's notices of new email only with a token Google signs for our own notification service, and records each arrival by its id alone. Who sent it and what it says are read from your mailbox when you ask, and the records are deleted after 30 days.
  • Another Titus product you connect can send news only with the key you gave it, which we keep as a one-way hash, and with a signature from a secret that product shares with us, checked on every message and refused when it is more than five minutes old. What it sends is read to you, never followed as an instruction, and disconnecting stops it at once.
  • Accounts are by invitation, and created by our server, not by the browser. Passwords are kept only as salted hashes by Firebase Authentication; we don't store or log them. Every new account is sent a link to confirm its email address, and sign-in never says whether an address has an account.
  • To stop the forms being flooded, we limit waitlist sign-ups and account sign-ups per connection using a keyed hash of the IP address, not the address itself.
  • The site sets no cookies and runs no analytics or advertising scripts. A signed-in session is kept in your browser's own storage, and signing out removes it.

Who handles data for us

  • Google Cloud and Firebase host the site, sign people in (Firebase Authentication), store waitlist sign-ups, account profiles, mailbox connections and assistant session records in Cloud Firestore, deliver Gmail's notices of new email (Cloud Pub/Sub), and make the natural voices and listen where a browser can't (Cloud Text-to-Speech and Speech-to-Text), in the United States.
  • Anthropic provides Claude, the language model that understands your commands, summarizes the emails you hear and drafts the replies you ask for, under terms that do not allow it to train on that data.
  • Stripe takes payments for paid plans on its own secure pages, so card details never reach our servers.
  • Brevo delivers our email, such as the confirmation you get when you join the waitlist and the link that verifies an account's address.
  • Cloudflare runs the DNS for tituscore.com, which points the address at our hosting and at our mail provider.
  • Google Workspace hosts our tituscore.com mailbox, where sign-up notifications and emails sent to us are stored.

The Privacy Policy has the detail, including what your browser's own speech services do.

Report a vulnerability

If you think you've found a security problem in tituscore.com, please tell us privately so we can fix it.

  • Tell us what you found, where, and the steps to see it, with any proof of concept.
  • Please don't access, change or delete data that isn't yours, don't degrade the site for anyone else, and give us a reasonable time to fix the problem before you share it.
  • We'll confirm we received your report and keep you updated while we work on it. We don't run a paid bug bounty.

Security contact

For vulnerability reports only. For anything else, see Contact.
info@tituscore.com

Also published in security.txt.

Questions about how your email will be handled?

Join the waitlist to follow along, or call us and ask. We'd rather explain a design decision than have you guess.