Skip to content

Privacy Policy

Last updated:

Draft. This document was written in-house and is pending review by a lawyer. It describes what this site actually does today, and we will publish a reviewed version once that review is done.

Titus Core is made by Titus Hub Inc. (“we”, “us”). This policy covers our website, tituscore.com, as it is today: what it collects when you visit, join the waitlist or, once invited, create an account; why; who else handles it; how long we keep it; and how to have it deleted. It also sets out what Titus Core does with a mailbox you connect.

Who we are

Titus Hub Inc. is building Titus Core, a voice assistant that reads your email aloud and acts on what you say. For the personal information described on this page, Titus Hub Inc. is responsible for it (the “controller”, in privacy-law terms).

Questions about this policy or your information: email info@tituscore.com or call 631-977-7400.

Titus Core itself

Titus Core is in development. People we invite can create an account and sign in. Connecting a mailbox, and the voice assistant that reads it to you, are being tested with a small number of accounts. This section says what Titus Core does with a connected mailbox, so you can decide now whether to join. We will update this policy, and the date at the top of this page, before that changes.

Connecting a mailbox

You connect a Gmail and Google Workspace mailbox by signing in with Google and granting one permission: to read, organize and reply from your mailbox, and to move email to the Trash. That permission does not allow permanent deletion, and Titus Core asks for no other: not your contacts, your calendar or your files. You can disconnect at any time, in Titus Core's Settings or in your Google account's own settings, and Titus Core's access ends when you do.

An Outlook.com or Microsoft 365 mailbox is connected by signing in with Microsoft, where you allow Titus Core to read, organize and send email from your mailbox, and to know your account's name and address. Microsoft's mail permission would also allow deleting email for good; Titus Core has no command that does: it moves email to Deleted Items, which you can restore. Disconnecting in Titus Core's Settings deletes the key it holds, so its access ends; you can also remove it in your Microsoft account's app permissions, or for a work or school account, under My Apps.

What Titus Core does with your email

When you open your Inbox in Titus Core, our server reads the list of emails in your mailbox's inbox, and the one email you open, through Google's Gmail API, or Microsoft Graph for an Outlook mailbox, and shows them to you. The Inbox page changes nothing.

On the Assistant page, in a session you start, Titus Core reads the emails you ask for aloud and does what you say: it moves email to the Trash, archives it, files it under a label, marks it read, unread or starred, and sends the replies you approve. Hearing an email marks it read in your mailbox, as opening it would. Clearing out everything from a sender, sending a reply, adding someone to it and creating a new label each wait for your yes. While careful mode is on, as it is unless you turn it off in Settings, a single trash or archive waits for your yes too.

Titus Core does not keep what it read: no email text, subject or sender, and no reply it drafted, is written to our database or our logs.

Noticing new email

So it can tell you what's new, Titus Core asks Google to let it know when email arrives in your inbox. Google then sends our server your address and a change number, and our server asks Gmail which emails arrived: their ids and labels only, not who sent them or what they say. For each new email in your inbox it records that the email arrived, by its id. When you open What's new, or say “what's new”, the sender and subject are read from your mailbox at that moment, as the Inbox does. Apart from this, Titus Core does not read your mailbox when you are not using it. Disconnecting stops the notices and deletes those records.

An Outlook mailbox sends no such notices. Instead, every ten minutes, our server asks Microsoft which emails arrived in your inbox since it last looked, by their ids and arrival times only, and records each new one the same way.

Your other Titus products

In Settings you can connect Titus Core to TitusVoice, TitusChat and Titus Board, so it can tell you what's new there as well. Connecting makes a key that you paste into the other product; Titus Core keeps only a one-way fingerprint of it. From then on, that product sends Titus Core what it has for you: a voicemail with the caller and what they said, a message from a visitor to your website, a task of yours coming due, a comment that mentions you.

Unlike your email, which stays in your mailbox, what another product sends is kept as it was sent, so it can be read to you later. It is shown only to you, read aloud the same way answers are (see below), and never sent to the language model. It is deleted after 30 days, or at once when you disconnect that product, here or in the product itself.

Listening and speaking

Where it can, your browser does the listening, with its own speech service. Depending on the browser, what you say may be sent to the browser maker's speech service (Google for Chrome, Microsoft for Edge, Apple for Safari) to be turned into text; the browser maker's privacy terms cover that, and Titus Core receives only the words. Once you turn the microphone on, it stays on until you turn it off, and it turns itself off after two minutes in which nobody speaks, or when you leave the page. While it is on, the browser listens to everything said near your device; what it hears while Titus Core is quiet is sent as a command, and what it hears while Titus Core is speaking is sent only when it holds a command, such as “next” or “stop”. In a browser that can't listen (Firefox), the page records each command, a few seconds at most, while you hold the microphone on, and sends that recording to our server, which has Google Cloud's Speech-to-Text turn it into words. The recording and the words are used for that command only; neither is kept. If you type a command instead, only what you type is sent.

The answers are read to you either by your browser's own voice (some browsers' voices send the text to the browser maker to be spoken) or, if you choose a natural voice and your plan includes it, by Google Cloud's Text-to-Speech: our server sends it the text of the answer, a sentence or two at a time, which can include an email's summary or text when that is what you asked to hear, or what one of your other Titus products sent, and plays you the audio it returns. Neither the text nor the audio is kept. The voice you choose and your speaking speed are saved with your settings.

The language model

To understand each command, Titus Core sends the words you said to Claude, a language model made by Anthropic, together with where the session stands: your name and mailbox address, the sender, subject and age of the email being discussed, and a reply draft if there is one. To summarize an email, answer a question about it or draft a reply you asked for, the text of that one email goes too. Anthropic handles it as our service provider, under its commercial terms, which do not allow it to train its models on what we send. See also Anthropic's privacy policy. Text in an email is treated as information to read to you, never as instructions to follow.

Google's rules

Titus Core's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: your Google data will be used only to provide the features you see and asked for, never for advertising, never sold, never used to train general-purpose machine-learning models, and never read by a person at Titus Hub Inc. except with your permission, for security, or where the law requires.

What is stored for a connected mailbox

Today: the mailbox's address; the permissions your mail provider says you granted; whether the connection still works, and when it last failed; and a token that lets Titus Core reach the mailbox until you disconnect. The token is stored encrypted, in a part of our database that no browser can read. While you are connecting, a record of that attempt is kept for up to ten minutes.

When you use the assistant, also: a record of each session and each command in it (which commands ran, what they acted on, identified by message ids, and how they ended, never the words); how many commands you used each month and how much language-model processing they took; and, while an action waits for your yes, a fingerprint of it (a one-way hash), not its content. Session and command records are deleted after 30 days. For noticing new email: a record of each email that arrived (its id, when, and whether you have heard it or cleared it), deleted after 30 days, and for the mailbox, its address, how far through its changes we have read, and when Google's notices were last renewed. For your other Titus products: which ones you connected and when, the name each gives your account there, a fingerprint of each key, and what each sent, as described above. A reply draft waiting for your yes is held only by the open page in your browser, never in its storage, and is gone when you leave the page.

What we collect today

The site collects six things.

Your waitlist sign-up

When you join the waitlist, we store:

  • your email address, how you would use Titus Core (for work, for personal email, or both) and where your email lives today (for example, Gmail or Outlook);
  • your name, company name and any note you add, if you give them;
  • which page of the site you first joined from, and the latest;
  • when you first joined, when you last sent the form, and how many times you have sent it;
  • whether our emails about your latest sign-up were sent.

If the form is sent again with the same address, we keep your one entry and your first answers as they were, and store the latest answers beside them, rather than adding a second entry. To change your answers, email us.

Please don't put passwords or other sensitive information in the note; we never need them. If you email or call us instead, we keep what you tell us in the same way.

Your account, if you create one

Sign-up is by invitation for now. If we invite you, we add your email address to an invitation list, so the sign-up form accepts it. When you create an account, we store:

  • your name and email address, and whether you have confirmed the address;
  • your password, kept only as a salted hash by Firebase Authentication, Google's sign-in service. It reaches our server once, when you create the account, over an encrypted connection; the server hands it to Firebase and neither stores nor logs it. When you sign in, your browser sends it to Firebase directly;
  • your time zone, taken from your browser when you sign up and yours to change, and your settings: how emails are read to you, and whether single actions ask first;
  • the date of the Terms of Service and Privacy Policy you accepted, and when you accepted them;
  • when the account was created and when it last signed in, which Firebase Authentication records.

To keep you signed in, your browser also stores your session; see Cookies and tracking.

Your mailbox connection, if you make one

If you connect a mailbox, we store what the section above lists: its address, the permissions granted, the state of the connection, an encrypted token, the records of which new emails arrived and, when you use the assistant, the session records, monthly counts and fingerprints described there. We do not store your email or what you said.

Your plan

Once you connect a mailbox, we record your free trial: when it started and when it ends. If you choose a paid plan, you enter your card on a page run by our payment processor, Stripe; your card details go to Stripe and never reach our servers. We store which plan you have, the ids Stripe gives your customer record and your subscription, whether the plan is active and when the current period ends, and whether you have cancelled it. Stripe gets your email address and an internal id that links your payments to your account. If we give you a plan free, we record that too. To make sure each payment update from Stripe is handled once, we keep the id of each update we receive for 30 days.

Keyed hashes, to limit use of the forms

To keep the form from being flooded, we limit how many sign-ups can come from one connection. To do that we store a one-way keyed hash of your IP address: a scrambled value made from the address and a secret key, which lets us recognize repeat submissions without keeping the address. We don't store your IP address itself. The hash is kept in the record that counts submissions for the limit, and the hash from your latest submission is kept with your sign-up, so we can spot repeated abuse of the form.

We also limit how often one email address can be sent through the form in a day, and how many confirmation emails it can receive, so nobody can use the form to send our email to someone over and over. For that we store a keyed hash of the email address you entered, made the same way, in the records that count those. We use these hashes only to prevent spam and abuse.

The account forms are limited too. Sign-up attempts are counted against the same keyed hash of your IP address. Requests for a verification email are counted per account, and requests for a password reset per email address, against a one-way hash of the address rather than the address itself, so nobody can use them to flood an inbox. Commands to the assistant are counted per account, per minute and per day, against the account's internal ID.

Request logs kept by our hosting provider

Our hosting provider, Google Cloud, logs each request to this site: the time, the page requested, your IP address, your browser's user agent and the response. We use these logs only to keep the site secure and running, and to look into problems or abuse.

Our own server also writes a log entry for each sign-up. It records what happened (for example, whether our emails were sent) and a shortened keyed hash of your email address, made the same way as the hashes above, never the address itself. For accounts, it records what happened and the account's internal ID, never your password or your email address. For each command to the assistant, it records the account's internal ID, which commands ran and how they ended, how long that took and how much language-model processing it used: never what you said, and never anything from an email.

Cookies and tracking

This site sets no cookies, and runs no analytics, advertising or third-party tracking scripts at this time. If we ever add any, we will update this policy first.

When you sign in, your browser keeps your session in its own storage for this site, so you stay signed in until you sign out: the session data Firebase Authentication needs, and a marker that this browser was signed in. It is used only to keep you signed in, and signing out removes it. If you never sign in, no session is stored.

The emails we send through Brevo may record when they are opened and when a link in them is clicked, as described under Who else handles it.

How we use it

  • To confirm your sign-up, and to email you about Titus Core: an invitation to the private beta, the prices, and launch news.
  • To understand who Titus Core is for, such as which mailbox providers people use, so we build the right connection first.
  • To create and secure your account, keep you signed in, and send the emails an account needs: the link that confirms your address, and password resets.
  • To run your free trial and any plan you pay for, and to answer questions about billing.
  • To show you the email in a mailbox you connected, to tell you what's new in it, to read it to you and do what you ask in an assistant session, and to tell you by email if that connection stops working.
  • To reply if you get in touch with us.
  • To prevent spam and abuse of the forms, and to keep the site secure.

We only email you about Titus Core. We don't sell your personal information, and we don't share it with anyone for advertising.

Who else handles it

We use a small number of service providers to run this site:

  • Google (Firebase and Google Cloud) hosts the site, signs you in (Firebase Authentication), and stores waitlist sign-ups, account profiles, mailbox connections and assistant session records in its database, Cloud Firestore, on our behalf, in the United States. A connected Gmail mailbox is read and acted on through Google's Gmail API (an Outlook mailbox stays with Microsoft, your mail provider, and is reached through Microsoft Graph), and Gmail's notices of new email reach our server through Google Cloud Pub/Sub. Google Cloud's Text-to-Speech makes the natural voices from the text of an answer, and its Speech-to-Text turns a spoken command into words in a browser that can't (both described in Listening and speaking). See Firebase's privacy and security information.
  • Brevo delivers the site's email on our behalf: the confirmation when you join the waitlist, a notification to us with the details you sent, the emails an account needs (confirming your address, resetting your password, a notice that your mailbox needs reconnecting), and our later emails about Titus Core. Brevo may record when an email we send is opened and when a link in it is clicked. See Brevo's privacy policy.
  • Anthropic provides Claude, the language model that understands your commands, summarizes the emails you hear and drafts the replies you ask for. It receives what you say and the email details described in The language model, under its commercial terms, which do not allow it to train its models on that data. See Anthropic's privacy policy.
  • Stripe takes payments for paid plans, on its own secure pages. It receives the card details you enter there, your email address, and an internal id that links the payments to your account; it does not receive your email or anything you said to the assistant. See Stripe's privacy policy.
  • Cloudflare runs the DNS for tituscore.com: it answers the lookups that point the address at our hosting and at our mail provider. It does not handle the email itself. See Cloudflare's privacy policy.
  • Google Workspace hosts our mailbox, info@tituscore.com. The notification of each sign-up, with the details you sent, and any email you send us are stored there. See Google Workspace's privacy policy.

We may also disclose information where the law requires it, or where it is needed to protect the rights, property or safety of our users, the public or us. We will update this list before we add another provider that handles personal information from this site. The speech services built into your browser are your browser maker's, not ours; see Listening and speaking.

How long we keep it

  • Your sign-up: while you are on the waitlist. Ask us to take you off at any time and we delete it. If you go on to use Titus Core, it becomes part of your account records.
  • Your account: until you ask us to delete it. Email us and we delete the account, its profile and your invitation.
  • Your plan: with your account. Stripe keeps its own records of your payments and invoices for as long as tax and accounting law require. The ids of Stripe's updates are deleted after 30 days.
  • Your mailbox connection: until you disconnect it or we delete your account. Disconnecting deletes the stored token and the connection record at once, and asks Google to withdraw the permission. The record of a connection attempt expires after ten minutes and is deleted automatically, usually within a day.
  • New-email records: deleted 30 days after the email arrived, usually within a day after that, or at once when you disconnect the mailbox. Clearing them on What's new hides them sooner.
  • What your other Titus products sent: deleted 30 days after it arrived, usually within a day after that, or at once when you disconnect that product. The connection itself is kept until you disconnect it.
  • Assistant sessions: the record of a session and its commands is deleted 30 days after its last command, usually within a day after that. Monthly usage counts are kept with your account. Anthropic keeps what we send it only as its commercial terms allow.
  • The hashes: the records that count submissions, sign-up attempts, confirmation emails, account emails and assistant commands are deleted automatically once their limit period has passed, usually within a day after that. The copy of the IP address hash stored with your sign-up is kept, and deleted, along with the sign-up.
  • Emails in our mailbox: the notification of your sign-up, and any email you send us, stay in our mailbox while you are on the waitlist. When we delete your sign-up at your request, we delete those emails too.
  • Email delivery logs: Brevo keeps a log of the emails it delivers for us, for its own retention period.
  • Request logs, and our server's own log entries: for Google Cloud's log retention period, which is 30 days by default.

Your choices and rights

You can leave the waitlist or close your account at any time, and ask us for a copy of what we hold about you, to correct it, or to delete it. Your name, time zone and settings are yours to change in the app, and you can disconnect your mailbox there at any time. Email info@tituscore.com, ideally from the address you signed up with, so we can confirm the request comes from you. There is no charge.

If you live in a US state with a consumer privacy law, such as California, you may have further rights, such as to know what we collect and why, and to opt out of the sale or sharing of your personal information. We don't sell or share personal information, but we will handle any request under those laws: email us and tell us which right you want to use. We will not treat you differently for using your rights.

If you live outside the United States, the law where you live may give you similar rights, including the right to complain to your data protection authority. Email us and we will help.

Security

What you send travels over an encrypted (HTTPS) connection to a server route on this site, which checks it before storing it. No browser can write to our database, and the only thing a signed-in browser can read from it is that person's own profile, the address and state of their own mailbox connection, their own records of which new emails arrived, and their own plan; everything else is reachable only by our own server. Payment updates from Stripe are accepted only with Stripe's signature. A small number of people at Titus Hub Inc. who run Titus Core can see, for each account, its email address and name, when it was created, the connected mailbox's address and state, the plan, and how many assistant commands it used this month; never any email, and every change they make is recorded. Google's notices of new email are accepted only with a token Google signs for our own notification service. The token for a connected mailbox is encrypted (AES-256-GCM) with a key kept in Google's Secret Manager, apart from the database. Access to sign-ups and accounts is limited to the people at Titus Hub Inc. who need it. No website can promise perfect security, but if a breach affects your information we will tell you as the law requires. Our security page has more, including how to report a vulnerability.

Children

This site is for adults and businesses and is not directed at children. We don't knowingly collect personal information from anyone under 16. If you believe a child has joined the waitlist or created an account, email us and we will delete it.

Changes to this policy

We will update this page before we change what the site collects or who handles it, and before Titus Core opens. The date at the top always shows when it last changed.

Contact

Titus Hub Inc.
Email: info@tituscore.com
Phone: 631-977-7400

See also our Terms of Service.