Privacy policy

Three-Inbox is a private email and task workspace that I, Dr Nick Azizi, built for my own use and operate through PersisMed Pty Ltd. It is not offered to the public, and only my own Google account can sign in to it. It works with my three Gmail mailboxes, which include correspondence about patients. This page explains what the application does with that mail and the other data it holds, who else receives any of it and where, and how long it is kept.

Who receives data, and where

Google sign-in and the Google permissions requested

How Gmail data is used

The AI features (Anthropic)

AI processing is off until I switch it on in Settings. While it is on, these features send content to Anthropic’s API. Most requests also carry the short “About me” note I write in Settings.

Some requests ask Anthropic to keep a cached copy of the prompt for a few minutes, so that a follow-up request costs less. Beyond that and the message batches, the application asks Anthropic to keep nothing. How long Anthropic keeps what it receives, and what else it may do with it, is governed by Anthropic’s commercial terms for my API account. The application itself does not use any of this data to develop, improve or train AI models.

What the AI switch stops, and what it does not. Switching AI processing off stops every feature in the list above, including PDF transcription for Claude connections, and review batches still waiting at Anthropic are cancelled by the scheduler. It does not stop Publish in Website news, which starts my own scheduled Claude task when I press it. It does not stop Claude connections: a connection I have approved can still read my mail through claude.ai with AI processing off, because that is me using Claude, not the application calling Anthropic. It also does not affect features that use no AI: finance capture, file exports, my rules, notifications and the rest of the application.

Claude connections

What the application stores

The application stores the following in its Cloudflare database and file storage. Items marked encrypted are encrypted by the application (AES-GCM) with a key held as a Cloudflare secret, before they are stored.

Original files and saved receipts

Google Calendar

Notifications

If I turn on notifications for a device, each notification is encrypted for that device before it leaves the application (RFC 8291), so the push service cannot read it. What it says depends on its kind and on the lock-screen level I choose in Settings: by default a reminder shows the sender and subject, a new-task notification shows the first task’s title, and a new-email notification shows the sender and mailbox, with the subject only if I turn that on. A Claude connection allowed to change things can send a short message of its own when an unattended run finishes something I asked for or finds something urgent: at the “sender and subject” level its own words show, at the lower levels only that Claude has an update; it is refused if it names a person in my tasks, a date of birth or a Medicare-like number, at most 5 an hour and 20 a day are allowed, and I can switch these messages off. A finance notification uses fixed words, such as “Finance: something is due in 3 days”, and never an amount, an account or a payee; the same goes for the two about my finance engine’s jobs (“Finance: a job on your Mac failed”, “Finance: your Mac needs an answer”). A notification never contains an email’s body, a quote from it or an attachment. Waiting notifications are held encrypted and deleted within a week. A reminder for an event on my own calendar comes at its time even in quiet hours; at the generic level it shows only the time, at the sender-and-subject level the event’s title and time, and at the full level its place too. A reminder for a task’s time on the calendar shows its title (which names the patient as I choose in Settings → Calendar) at every level, the generic one included.

Pictures in emails, sender logos and other outside requests

Google API Services User Data Policy

Three-Inbox’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Gmail and Google Calendar data are used only to provide the features described on this page, for me. They are not sold, not used for advertising, and not used by the application to develop, improve or train AI or machine-learning models. They are transferred only as this page describes: to Anthropic for the AI features I switch on; to Claude, through a connection I have approved, when I use it; to Cloudflare, which hosts the application; to push services, encrypted, as notifications I turn on; to whoever holds a download link I asked for; to a sender’s web server, as a request for a picture in that sender’s email; to websites that publish a sender’s logo, as a request for that logo, using only the sender’s domain name; to a mailing list’s own unsubscribe address, when I unsubscribe from it; and to Google Calendar, as events I add. Apart from me, no person reads this data through the application.

How long data is kept, and deleting it

Contact

Questions about this policy: nickazizi@persismed.com.au.