Privacy Policy
Last updated 4 September 2026
The short version. Alex reads the email threads you CC it on, and nothing else in your mailbox. On your calendar it sees which hours are busy, never what the meetings are. It stores who is on a thread and what times were discussed, not the emails themselves.
To work out what an email means and to write its replies, Alex sends the message text to Anthropic's API. Nothing is used to train anyone's AI models. Ask us to delete your data and we will delete it.
1. Who we are
Alex is run by Balint Bertok, an individual rather than a company ("we", "us"). We are the data controller for the personal data described here.
You can reach us about anything on this page at [email protected].
2. What Alex can and cannot see
Alex has its own email address. It receives a message only when somebody sends or copies one to that address. We have no access to your mailbox, no mailbox credentials, and no ability to read anything you do not send to Alex.
You connect a Google Calendar when you sign up. We request two permissions and no others:
- Free/busy, which tells us that an hour is taken. It does not tell us the title of a meeting, who is attending, or where it is.
- Calendar events, which lets Alex create, update and cancel the entries it makes for you.
Alex cannot read back the entries in your calendar that it did not create itself. This is a deliberate design constraint rather than a promise about behaviour: the software has no code path that fetches them.
3. What we collect
If you sign up as a user
- Your name, email address and time zone.
- The Google credential that lets Alex reach your calendar, held so it can act on later emails. You can revoke it at any time, see section 8.
- Your scheduling preferences, such as working hours and days you keep clear.
From the email threads Alex is on
- The email addresses and display names of the people on the thread.
- The subject line, the message identifiers that let Alex follow a thread, and the times that were proposed, accepted or rejected.
- The identifier of the calendar entry Alex created.
We do not store the body of the emails. The text is processed when the message arrives and is not written to our database.
There is one exception, and we would rather name it than bury it. When somebody asks Alex for something it cannot do, we save the subject line and a short excerpt of the request so we know what to build next. If you would rather that had not been kept, ask and we will delete it.
If you join the waitlist
Your email address, the date you submitted it, and the country our host saw the request come from. It is used to email you when the beta opens, and for nothing else.
4. If you are not a user, but Alex emailed you
Somebody copied Alex into a thread with you. We hold your email address, your name if it was on the thread, and which times you said worked. We use it only to arrange the meeting that thread is about.
Our lawful basis is legitimate interests: arranging a meeting you are already being asked to attend, using the address the organiser already had for you. You can object at any time, and you have the same rights set out in section 8. Write to [email protected] and we will remove you.
5. Why we are allowed to hold it
| What | Why | Lawful basis |
|---|---|---|
| User account and calendar | To provide the service you signed up for | Performance of a contract |
| Thread participants | To arrange the meeting | Legitimate interests |
| Waitlist address | To tell you when the beta opens | Consent |
| Counts of what Alex did | To see whether the product works | Legitimate interests |
6. Who else processes it
We use these providers. Each is bound by a data processing agreement and none of them may use your data for their own purposes.
| Provider | What it handles | Where |
|---|---|---|
| Anthropic | Reads an incoming email to work out what it asks for, and writes the wording of replies | United States |
| Your calendar | United States | |
| Amazon Web Services (SES) | Sending Alex's email | Germany (eu-central-1) |
| Cloudflare | Receiving Alex's email, this website, and the waitlist | Global network |
| netcup | The server the service runs on | Nuremberg, Germany |
Transfers outside the UK and EEA rely on the European Commission's standard contractual clauses.
Email text is sent to Anthropic's API so that Alex can understand it and reply. Under Anthropic's API terms that content is not used to train their models. What is sent to write a reply is a set of decisions already made, such as which two times to offer, and free/busy blocks. It never includes the titles or attendees of your other meetings.
We do not sell personal data, and there is no advertising or analytics tracking on this site. This site sets no cookies and stores nothing in your browser, so there is nothing here to consent to.
7. How long we keep it
- Account data, for as long as you have an account.
- Scheduling records, for as long as your account exists, because a thread can be picked up months later.
- Backups, for 14 days, after which they are overwritten. Something deleted at your request may sit in a backup until then.
- Waitlist addresses, until the beta opens or you ask us to remove yours.
When you close your account we delete your data, including the stored Google credential, within 30 days.
8. Your rights
Wherever you are, you can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, ask us to restrict what we do with it, or object to us holding it at all. Write to [email protected] and we will answer within 30 days. There is no charge.
You can disconnect Alex from your calendar yourself at any time, without asking us, at myaccount.google.com/permissions. Alex stops being able to see or change anything the moment you do.
If you are in the UK or the EEA and think we have handled your data badly, you can complain to your national data protection authority. We would rather you told us first, but it is your right either way.
9. Google user data
Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Specifically: we use Google Calendar data only to provide the scheduling features described on this site, we transfer it to others only as needed to provide those features, to comply with the law, or as part of a merger where you have been told first, we do not use it for advertising, we do not sell it, and we do not let humans read it except where you have asked us to, where it is needed for security, or where the law requires it.
We do not use Google user data to develop, improve or train generalised artificial intelligence models.
10. Security
Traffic is encrypted in transit. Access to the server is by key only and limited to the people running the service. Alex checks the authentication results on every incoming email before it acts on it, and can only ever reply to addresses already on the thread, which is enforced in code rather than by instruction.
No system is perfect. If we ever suffer a breach affecting your data, we will tell you and the relevant regulator as the law requires.
11. Children
This service is for people at work. It is not directed at children and we do not knowingly collect their data.
12. Changes
If we change this policy we will change the date at the top, and if the change is significant we will email you about it before it takes effect.