Your data
Your titra data: where it lives, export, delete
Your log is stored on your phone. It is uploaded in one case: when you have titra+ and sign in for cloud backup. You can export it for free and delete it whenever you like.
titra records what you log. It never gives dosing or medical advice. Follow your prescriber's guidance.
Your titra log is stored in a database on your phone. It is uploaded in one case: if you have titra+ and sign in for cloud backup, the log goes to Google Firestore. You can export all of it as a CSV file for free, and delete it at any time.
Separately from the log, crash reports are always sent, and they hold no health entries. The rest of this page sets out what is stored where, and what each button does.
Sources checked (5)
The log on your phone
Your medication, doses, injection sites, pain scores, weights, side effects, daily food-noise ratings and settings [1]. They sit in the app's own database on the device. No account is involved, and we cannot see any of it.
What leaves the phone, and when
| What | When | Where it goes |
|---|---|---|
| Your log and treatment settings (medication, current dose, starting and goal weight, reminder time) | Only if you have titra+ and sign in for cloud backup | Google Firebase: Authentication and Cloud Firestore |
| Email address and account ID | Only if you create an account | Firebase Authentication |
| Crash reports: what went wrong, device model, system and app version, and your account ID if signed in. No health entries. | When the app crashes or records an error. This is always on. | Firebase Crashlytics |
| Usage events such as "dose logged". No doses, weights or symptoms. | Only if you switch on Share anonymous usage data, which is off by default | Google Analytics for Firebase |
| Purchase and subscription status | When you view or buy titra+ | RevenueCat, and the App Store or Google Play |
That table is the privacy policy's own list [1]. titra has no ads, uses no advertising networks or attribution SDKs, and does not use the advertising identifier.
What cloud backup does
Cloud backup is part of titra+ and needs you to sign in. It is the one feature that uploads your log.
When a backup runs, titra merges the log on the phone with the copy in the cloud: every dose, weight, side effect and food-noise rating, plus your treatment settings. A backup runs when you sign in, when titra starts while you are signed in, and when you tap Back up now. The Cloud backup screen shows when the last one finished. On a new phone, the first backup after you sign in brings your log down.
A few details matter here:
- Weights imported from Apple Health or Health Connect are stored like weights you typed. They are uploaded only if cloud backup is on.
- The phone remembers which account its log belongs to. Sign in with a different account and titra refuses to mix the two logs, and tells you why.
- The backup does not use a key that only you hold. It is stored by Google, a processor acting for us, under Google's keys [1][3].
Export to CSV
In the You tab, under Your log, tap Export CSV. titra builds one file, named titra-export- plus the date, and opens your phone's share sheet so you can save it or send it somewhere.
The file has one row per entry and these columns:
kind, date, brand, dose_mg, site, pain, weight_kg, side_effect, severity, duration, food_noise, notes
The kind column says what the row is: a dose, a weight, a side effect or a food-noise rating. Weights are always written in kilograms, whichever unit the app is showing.
Export is free, needs no account and covers your full history. The working copy titra makes for the share sheet is deleted as soon as the sheet closes. Whatever you shared the file with keeps its own copy, which is then yours to look after.
The PDF summary, also in the You tab, is part of titra+. It lists your dose steps, weights, doses and side effects, and ends with the line "Recorded by the patient in titra. Not a medical record and not medical advice."
Delete all data
In the You tab, under Your log, tap Delete all data. titra asks you to confirm, with the warning "This deletes every dose, weight and side effect on this phone. It cannot be undone."
Confirm, and every dose, weight, side effect, food-noise rating and setting is removed from the phone, and the reminders already planned are cancelled. The app goes back to its setup screens.
If you are signed in for cloud backup, titra signs you out first, so a backup cannot bring the deleted entries back onto the phone. The cloud copy itself is untouched: it stays until you delete your account. To remove both, delete your account as well. Uninstalling titra also removes the database on the phone [1].
Delete your account
In the You tab, open Cloud backup and tap Delete account. This removes the cloud copy of your log and then your sign-in account. If the first part fails, nothing is deleted and you can try again [2].
Three things it does not do:
- It does not delete the log on your phone, so titra keeps working without an account.
- It does not cancel a titra+ subscription. That is billed by the App Store or Google Play, and you cancel it there [4][5].
- It does not erase every record at once. Crash reports are kept for 90 days, and purchase records are kept as long as billing and legal duties require [1][2].
If you can no longer sign in, the account deletion page explains how to ask by email.
Quick answers
Can AgentM see my log?
Not the log on your phone: we have no access to it. If you turn on cloud backup, a copy is stored in Google Firestore under your account, and the privacy policy sets out who processes it and why.
Is CSV export free?
Yes. Export CSV is free, needs no account and always includes your full history.
Does Delete all data remove my cloud backup?
No. It clears the phone and, if you are signed in, signs you out. The cloud copy is removed when you delete your account, under Cloud backup in the You tab.
Does deleting my account cancel titra+?
No. titra+ is billed by the App Store or Google Play, so you cancel it there. Deleting your account removes the cloud copy of your log and your sign-in.
Sources
The app behaviour on this page was checked against titra 2.0.2. The privacy policy is the binding description of what is processed and by whom.
What changed
- First published, checked against titra 2.0.2.