OxSlate · last updated 10 August 2026
OxSlate lets one person (the supporter) keep a queue of household admin and send a single calm reminder at a time to another person (the recipient). Because one person is entering information about another, we are deliberately narrow about what we collect and what either side can see.
Stated first, because these absences are the point of the product rather than gaps we intend to fill:
| Data | Why | Where it goes |
|---|---|---|
| A generated device identifier and access token | To pair two phones and authorise requests without accounts. Tokens are stored hashed. | Our API (AWS, US East) |
| A hash of the supporter's email address, if they choose to add one | Optional. So a supporter can sign back in and recover their queue on a new phone. Never collected from the recipient. | Our API, and Amazon SES to send the code |
| Reminder content: subject, due date, category, repeat, any note or link you add | To deliver the reminder to the recipient's phone at the right time | Our API, and the recipient's device |
| The supporter's display name | Shown on reminders so the recipient knows who asked | Our API, and the recipient's device |
| Time zone | So reminders arrive at a sensible local hour and respect quiet hours | Our API |
| The recipient's delivery choices: paused, disconnected, and what happens if a date passes | To enforce their control over delivery | Our API. The escalation choice is never revealed to the supporter. |
| Text you dictate or type into "Say it once" | To turn a spoken list into separate dated reminders | Our API, then Amazon Bedrock for processing |
| A photo of a bill or letter, if the supporter uses "Snap a bill" | To read the due date, amount and reference so they do not have to type them. Read once and discarded — never stored. | Our API, then Amazon Bedrock for processing |
| Purchase and subscription status | To unlock paid features and restore purchases | RevenueCat and Google Play |
Photographing a bill is different, and only happens when you choose it. If the supporter uses "Snap a bill", that one photo is sent to be read so the date, amount and reference can be filled in for them. It is read and discarded in the same request — never stored by us, and never kept as a copy of the document. Only the text they confirm is saved.
The supporter can see only that a reminder was delivered, marked done, snoozed, stopped, or that a date passed. Nothing else about the recipient's behaviour is recorded or shown.
The recipient can pause deliveries, stop any single reminder, or disconnect entirely, at any time, without giving a reason. Disconnecting cannot be undone by the supporter — it requires a fresh invitation that the recipient chooses to accept.
Reminders are kept while the connection exists. Invitations expire after seven days automatically. Disconnecting deletes the queue from the recipient's device and stops all delivery. Uninstalling ends collection; backups are disabled, so nothing is copied to a cloud account or transferred to a new phone.
Sign-in codes are deleted automatically ten minutes after they are issued, or as soon as they are used. If email sign-in is used, the hashed address and the list of connections it can recover are kept for as long as the account is in use, and expire automatically after about thirteen months without a sign-in.
To have server-side data for a connection deleted, or an email sign-in removed, contact us at the address below and we will remove it. Signing out on the phone deletes the address from that device immediately.
OxSlate is not directed at children and we do not knowingly collect data from children under 13.
OxSlate is a household organisation and reminder tool. It does not diagnose, treat or provide medical advice, and it is not a medical device.
Questions, or a deletion request: [email protected]