TailTempo Privacy Policy
Version: 1 · Effective from: 16 November 2026
1. Who we are
Until the company (SIA) is registered, the data controller is Jurijs Smirnovs, a private individual, Kleistu iela 15 - 144, Riga, LV-1067, Latvia. Contact for data questions and support: [email protected]. When the company is registered, it becomes the controller: we will update these texts and send an e-mail to everyone on the waitlist and to every user.
We have not appointed a Data Protection Officer (DPO) because our core activities do not involve large-scale processing of special categories of data or large-scale regular monitoring (Art. 37(1) GDPR). Data questions are read and handled by Jurijs Smirnovs.
TailTempo is a mobile app for pet owners. You use it to keep a pet health journal, reminders and medications. The app turns your entries into a one-page summary for the vet. The app is currently in closed testing and available on Android only.
2. The short version
- Your journal is stored on your phone. The copy on our server is encrypted on your phone with a key that only the members of your family (household) have. We cannot read your journal entries, photos or documents.
- The text of your entries is decrypted and leaves your phone only when you act:
- you ask the AI to transcribe a voice note, read a photo or write a summary;
- you create a link for your vet;
- you send a summary to your vet by e-mail.
- We do not sell data and do not show ads. No trackers follow you across apps or websites.
- You can delete your account in the app, and all your data on the server is deleted right away (section 8).
3. What data we process and why
| Data | Source | Purpose | Legal basis (Art. 6 GDPR) |
|---|---|---|---|
| Account: e-mail, or sign-in with Google, or anonymous sign-in; sign-in dates | you, sign-in provider | sign-in, sync, account recovery | performance of a contract (6(1)(b)) |
| Family: members, roles (owner, helper, viewer), invitations | you and members | one shared journal for several people | performance of a contract |
| Journal: entries, medications, doses, reminders, weight, episodes, photos, documents, voice | you | the core feature | performance of a contract |
| Technical data about entries on the server: entry type, created and changed time, file size, key version | the app | sync between phones | performance of a contract |
| Devices: phone model, platform, app version, device public key, push notification token | the app | encryption for each phone, notifications | performance of a contract |
| Consent log: which text you accepted and when, app version, phone model | the app | prove consent and ask again when the text changes | legal obligation (6(1)(c)), Art. 7(1) GDPR |
| Subscription: status, term, customer ID at RevenueCat | Google Play via RevenueCat | paid features (Plus) | performance of a contract |
| Trial and Plus: the date the family's 21-day trial started, whether the family has Plus | server | give and end the trial and Plus | performance of a contract |
| AI counters: number of requests, tokens and seconds of audio | server | free plan limits, abuse prevention | performance of a contract; legitimate interest (6(1)(f)) |
| Content of an AI request (only while the request runs) | your phone | voice transcription, reading photos, summary, notes after the visit, the assistant | performance of a contract (6(1)(b)), only when you tap the button; before the first use we tell you that the request goes to OpenAI |
| Vet link: summary page and PDF for 24–48 hours | your phone | show the summary to a vet without an account | performance of a contract, on your action |
| Vet's e-mail (if you send the summary by e-mail) | you | deliver the e-mail with the link | performance of a contract |
| Activity log: account events without content (export, deletion, members, links) | server | security, incident review | legitimate interest |
| Reminder counters (section 5) | the app | improve reminders | consent (6(1)(a)) and Art. 5(3) ePrivacy; off by default, you can turn it off at any time |
| Crash reports: error type, app version, phone model, without journal content, names or e-mail | the app | fix bugs | legitimate interest |
| Website waitlist: e-mail, page language, visitor's country (2 letters, from Cloudflare), the version of the consent sentence you saw, whether and when you confirmed the address | you; country from Cloudflare | one e-mail to confirm the address (sent through Resend), then one e-mail when your invitation is ready; without a confirmation we do not write again. Stored in Supabase (EU, Ireland). Cloudflare Turnstile protects the form from spam | consent (6(1)(a)) |
Animal health data is not a special category of data under Art. 9 GDPR. If you write something about people in the journal, those entries get the same protection: they are encrypted, and the server cannot read them.
4. End-to-end encryption: what the server sees and does not see
The server does not see: the text of entries, medication names, notes, photos, documents, voice notes, pet names. All of this is encrypted on the phone (XChaCha20-Poly1305) with the family key. The family key only travels between the members' phones, encrypted for each phone.
The server sees: your e-mail and sign-in data, who is in which family and with which role, when an entry was created and its type, file sizes, phone models, consents, AI and reminder counters, when your trial started and whether you have Plus.
Recovery phrase. During setup you get a phrase made of words. You need it to get access back on a new phone. We do not have it, and we cannot restore your journal without it or without the phone of another family member. Never send the phrase to anyone, including support.
Exceptions, when content knowingly leaves the phone decrypted, always on your action:
- AI (section 6): the entries needed go through our server to OpenAI. We do not store them.
- Vet link: the page and PDF are stored on the server unencrypted until the link expires (24 or 48 hours). Access is only by link and, if you set one, by PIN code. You can revoke the link earlier. The files are deleted within one day after the link expires.
- E-mail to the vet: the e-mail contains only the link, not the summary.
5. Reminder counters
Once a week the app sends anonymous counters: the reminder category (from a fixed list), the schedule type (for example "every 3 days", "on weekdays", "custom dates") and how many times the reminder was marked done, snoozed, skipped or recalculated. We never send the reminder name, dates, your account or your family. The counters carry a random install ID created on the phone. It is not linked to your account.
This is off by default. You turn it on yourself in "Settings → Help improve reminders". The legal basis is your consent (Art. 6(1)(a) GDPR). We ask for it because the install ID is stored on your phone (Art. 5(3) of the ePrivacy Directive). You can turn it off at any time. After you turn it off, nothing is sent. Counters are kept for 24 months.
6. Artificial intelligence
Details are on the page "How TailTempo uses AI" (ai-disclosure.en.md). In short:
- a request is sent only when you act, and only with the entries needed for the task;
- before sending, the server removes your name and e-mail from the text;
- the processor is OpenAI, using a project in the European data residency region. OpenAI keeps a request for up to 30 days for safety checks and then deletes it. OpenAI does not use API data to train models;
- the legal basis is our contract with you (Art. 6(1)(b) GDPR). AI runs only when you tap the button of an AI feature: voice note, photo of a document, summary, "what the vet said". Before the first use, the app tells you clearly that the request goes to OpenAI and is not used to train models;
- you do not have to use these features: you can type everything by hand, and the rest of the app works;
- pet health data is not special category data under Art. 9 GDPR, because it is about animals.
7. Who else processes data (processors)
We share data only with processors that have signed a data processing agreement (DPA), and only as much as they need to do their job.
| Processor | What it does | What data | Where | Basis for transfer outside the EEA |
|---|---|---|---|---|
| Supabase | database, sign-in, files, server functions | everything stored on the server (journal content encrypted) | EU (Ireland) | SCC (for support and operations from Singapore and the USA) |
| PowerSync (Journey Mobile, Inc. / JourneyApps) | sync between phones and server | the same data in transit, content encrypted | EU | SCC |
| OpenAI | voice transcription, reading photos, summaries | content of the specific request, without name and e-mail | project in the Europe region | SCC |
| RevenueCat | subscriptions in Google Play | customer ID, subscription status | USA | SCC |
| Resend | e-mails to vets, service e-mails | recipient's e-mail, link | USA | EU-US DPF; SCC |
| Expo (650 Industries) | app updates, push notifications | push token, notification text (written by the sender's phone), app version | USA | EU-US DPF; SCC |
| Sentry (Functional Software) | crash reports | error, version, phone model, without content or names | not connected yet; when connected, its EU region | EU-US DPF; SCC |
| Cloudflare | website, form protection (Turnstile), website statistics without cookies | IP address, browser data | global | EU-US DPF; SCC |
Each of them processes data under a data processing agreement with us.
Independent controllers (their own policies apply): Google as the app store (Google Play) and sign-in provider; your e-mail service and messengers you use to share a link.
8. How long we keep data
| What | How long |
|---|---|
| Account, family, journal on the server | while the account exists; deleted right away when you delete the account |
| Anonymous account with no entries | deleted after 90 days without sign-in |
| Vet link | 24 or 48 hours; files deleted within one day after expiry |
| Content of AI requests | not stored by us; at OpenAI — up to 30 days for safety checks, then deleted |
| Consent log | while the account exists; deleted with it |
| Activity log | 12 months; when you delete your account, the link to you is removed |
| AI counters | as long as the family; when you delete your account, the link to you is removed |
| Database backups | daily — 7 days, separate weekly — 8 weeks; deleted data disappears from backups when these periods end |
| Crash reports | 90 days |
| Waitlist | until we send the invitation e-mail and 12 months after, or earlier if you ask us to delete it |
9. Your rights
You can:
- get a copy of your data (Art. 15, 20): "Settings → Export". The app collects everything stored on the server and decrypts the journal on your phone;
- correct your data (Art. 16): directly in the app;
- delete your account and data (Art. 17): "Settings → Delete account" or the deletion page on the website (
data-deletion.en.md); - restrict processing or object to it (Art. 18, 21);
- withdraw consent (Art. 7(3)) to the reminder counters (a switch in Settings) or to the waitlist. This does not affect the lawfulness of processing before you withdrew;
- complain to a supervisory authority. In Latvia this is the Data State Inspectorate (Datu valsts inspekcija, www.dvi.gov.lv). You can also contact the authority in the country where you live.
We answer requests within one month (Art. 12(3)). We accept requests from the app or from the e-mail linked to the account.
10. Cookies and tracking
The app does not use advertising IDs or third-party trackers. The TailTempo website does not set cookies. Website statistics (Cloudflare Web Analytics) count visits without cookies and without tracking across sites. Form protection (Cloudflare Turnstile) checks that a person, not a bot, sends the form. It may keep short-lived technical data in the browser only for this security check, which does not need a consent banner. To improve its bot detection, Cloudflare acts as a separate controller (Cloudflare Turnstile privacy addendum).
11. Children
TailTempo is not meant for children under 16, and we do not knowingly collect their data.
12. Security
Encryption on the phone, secure connection (TLS), row-level access rules on the server (RLS), third-party service keys kept only on the server, two-factor protection for work accounts, activity log. If a breach puts you at risk, we will tell you and the supervisory authority within the GDPR deadlines (72 hours for the authority).
13. Changes
We tell you about important changes in the app and ask you to accept the new version. Previous versions are kept and published on tailtempo.com when a new version replaces them.