Data safety
Google Play treats data as collected only when it leaves the device. Journaling in Travel Dairy is on-device. The rows below match how the Play Data safety form should be filled for the current app.
Copy these answers into Play Console. If you later add analytics, ads, or always-on cloud backup, update this page and the form together.
Overview answers
| Play question | Answer |
|---|---|
| Does the app collect or share user data? | Yes — only for optional features (account/sync, feedback, map tiles). Core diary use does not send your journal to us. |
| Is all user data encrypted in transit? | Yes — HTTPS for map tiles, feedback, and optional APIs. |
| Do you provide a way for users to request that their data is deleted? | Yes — see Delete your data. |
| Does the app allow users to create an account? | Optional — journaling works without one. If sign-in is shown in the store build, also submit the account deletion URL. |
| Does the app contain ads? | No |
| Committed to Play Families Policy / designed for children? | No — target age 13+ |
Data types to declare
Mark each type as optional (users can decline the permission or skip the feature). Purposes are App functionality unless noted.
| Type | Collected? | Shared? | When |
|---|---|---|---|
| Location → Precise location | Optional | No | Saved on device with an entry. Sent to us only if the user opts into cloud sync. |
| Location → Approximate location | Optional | Yes — map tiles | OpenStreetMap receives IP + tile coordinates when the map is displayed. Not linked to the diary. |
| Personal info → Email address | Optional | No | Only if the user registers. Purpose: Account management. |
| Personal info → Name | Optional | No | Optional display name on registration. |
| Personal info → User IDs | Optional | No | Account UUID after sign-in. |
| Photos and videos → Photos | Optional | No | On device for entries. Uploaded only if the user syncs. Optional screenshot with feedback. |
| App activity → Other user-generated content | Optional | No | Diary text if synced; feedback message if submitted. |
| App info → Diagnostics / crash logs | No | No | No Crashlytics / analytics SDK. |
| Device or other IDs | Optional | No | Device model and OS version only with in-app feedback. Purpose: Developer communications. |
Do not declare (local only)
- Diary entries, GPS and photos that never leave the phone
- Exported PDFs saved via the system share sheet
- Encrypted
.tdbakbackups the user stores themselves - Financial, health, contacts, SMS, calendar, or web-history data — not used
Security practices
- Data encrypted in transit (HTTPS)
- Local diary database and photos encrypted at rest
- Users can request deletion of account / synced copies
- Independent security review: no (leave unchecked unless you later pay for one)
Sensitive permissions (App content)
| Permission | Play explanation to paste |
|---|---|
| Location (foreground) | Travel Dairy records an optional GPS point when you save a diary entry so the memory appears on the map. Location is not used in the background and is not required to write an entry. |
| Camera | Travel Dairy uses the camera only when you choose to photograph a moment for a diary entry. You can also pick an existing photo or skip photos entirely. |
| Photos / media | Used to attach gallery photos to an entry and to save or open PDF and backup files that you request. |
Full policy: Privacy Policy.
Travel Dairy