Sub (https://app.sub.ad) is a service of Sup AI Labs, Inc. ("we", "us"),
111 Lena Way, Apartment 3319, Mountain View, CA 94040, US. Sub provides AI employees ("subs"): AI assistants that work for an organization, each with
its own name and email address; a sub can also have its own phone number. Subs are AI, not people.
This policy explains what we collect, how we use it, and the choices you have. Write to us at ada@hq.sub.ad.
What we collect
Account information: the name and email address of each member of an organization, and the role
they have there; once they sign in to Sub with Google, their Google account identifier; any other email address they
add, and whether they confirmed it; their sign-in sessions, with the browser they used; and a record of what they do in Sub, such as approving work or changing a sub's settings.
What people send to a sub, and what it sends: chat messages and emails, with their date and time,
the sender's and recipients' addresses, and their attachments.
A sub's work: its notes, its tasks and their results, the commands it runs and what they print
(also on a person's own computer, when that person has it help there), screenshots of its computer, and the files and
code it works on.
Contacts: the people a sub works with, as it records them: their name and email address, what it
learns about them (such as their organization, role, language, preferred channel, and time zone), and where each fact
came from.
Phone numbers: a member's mobile number once they enter it in Sub, and whether they confirmed it;
and the numbers of people whom a sub texts.
Consent and opt-out records: the consent record Sub writes when its phone form texts a verification
code (the member, the number, when, how, the exact wording of the box they checked, and that it covers the code alone);
when a member confirmed their mobile number in Sub, which is their agreement to texts; and any opt-out Twilio reports
when it refuses a text (for example, after a STOP reply).
Usage and cost records: what each sub did, what its work cost, and the spending limits its
organization set.
How we use it
To run the service: a sub reads the messages it receives and answers those the sections below allow, does the work it
was given, and keeps a record of it for its organization.
To text a verification code to a number a member enters in Sub.
To keep the service secure, to keep each organization's spending within the limits it set, and to meet legal
duties.
Text messages
We do not share, sell, or rent mobile phone numbers, or text-messaging opt-in data and consent, with any
third parties or affiliates for marketing or promotional purposes.
Text-messaging opt-in data and consent are never sold, rented, or shared with third parties or affiliates for
marketing. We give them only to the service providers below, only to run Sub, with one exception: proof of a person's
consent goes to Twilio or to phone carriers when they ask for it.
Message frequency varies.
Message and data rates may apply.
Reply STOP to a sub's number to stop texts from that number, or HELP for help. See
how texting works.
Who else processes it
We use these service providers to run Sub. Each handles personal information to provide its service, under its own
terms. The Claude Code and Twilio entries also say what those two may use it for themselves:
Sign-in: Google, when a person signs in with their Google account.
AI models: Anthropic's Claude models, through Amazon Web Services (Amazon Bedrock), which write a
sub's replies and do its work; and Anthropic's Claude Code, which a sub uses on its own computer for coding, reviews,
research, and long reading (which can include the messages and files it works on), signed in to the Claude account set up
on that computer. Anthropic handles those sessions under that account's terms and settings, including whether they may
be used to improve Anthropic's models; Sub neither sets nor checks those settings, or whose account it is.
Memory: Hindsight, from Vectorize, which keeps a searchable copy of a sub's records so that it can
remember its work.
Email: AgentMail, which hosts each sub's mailbox and sends and receives its email.
Text messages: Twilio, which sends and receives a sub's text messages. Twilio is also an
independent controller of those texts, and of the phone numbers they go to and from, for some purposes of its own under
its terms, among them checking texts for spam, fraud, and abuse, and improving its services, including by training
models for those purposes. See Twilio's privacy notice.
Computers: Daytona, which runs a sub's own computer, where it keeps its working files.
Code: GitHub, which hosts the code repositories a sub works in.
Hosting and storage: Railway, which runs Sub and its database, and Amazon Web Services (Amazon S3),
which stores files, attachments, and backups.
We do not sell personal information.
Who sees it inside Sub
Inside an organization, a sub's email can be read only by the people who direct that sub (the
organization's owners and administrators, and the sub's designated manager) and by the sub it reports to, if another sub
hired it. Every member of the organization can see the records a sub keeps of its work, such as its notes, the results of
its tasks, and its requests for help, and those can quote a message. No one outside the organization can open any of it
in Sub, except those who operate Sub for us, who can reach every record when they run and support the service.
Keeping and deleting
We keep records until they are deleted, so that subs can remember their work, and nothing deletes an organization's
records when it stops using Sub. Messages, emails, notes, contacts, and the records of what members and subs do in Sub
have no automatic retention period, with two exceptions:
The images of screenshots of a sub's computer are deleted after 7 days. The record that each was taken, with its
caption, stays. On a sub's own computer, each of its browser tools keeps the last 20 page images it took.
When a sub runs a command on a person's own computer, the output kept with that command is erased 30 days after the
command finished. The command itself stays, and the record of the sub's work keeps the first 4,000 characters of each
result the sub got back, with no end date.
A person who directs a sub can have it forget a message it keeps in its memory, such as a chat message or an email.
Sub then replaces the message's text in its records with a removal note at once, and clears the copies it made of it in
the sub's memory and in Sub's file storage, retrying until that is done, at least once a day (a file keeps its name).
Other copies remain:
Sub's backups made before the removal keep the message, and copies of its attachment files, until those backups are
deleted. A deleted backup stays as an older version for at least 35 more days, until Amazon S3 erases it, unless that
version is deleted sooner. Our database host's own backups, if turned on, keep it on their schedule.
Our email provider keeps its copy until it is deleted there, and the people who received the message keep theirs.
Twilio keeps its own copy of each text a sub's number sends or receives until it is deleted there. Twilio's backups may keep a deleted text for up to 30 days more, and what Twilio keeps as an independent
controller (see its entry above) stays under its own retention policies.
What a sub wrote about it in its own words stays, apart from notes that rest on that message alone, and so do some
records of its earlier work that hold it word for word, such as its coding sessions; what those sessions sent Anthropic
stays under the terms of the Claude account set up on its computer.
Files a sub saved or wrote on its own computer, such as an attachment it saved there, or committed to a code
repository, stay there.
To ask for access to, correction of, or deletion of your information, write to ada@hq.sub.ad.
Children
Sub is for businesses and is not directed to children under 13.