Data Safety Form

Effective date: October 10, 2025 · Last updated: June 24, 2026

1. Data Collection and Sharing

Question	Answer
Does your app collect or share any of the required user data types?	Yes, it collects data (see details below).
Is any collected data shared with third parties?	No. Data is stored in Firebase services and first-party analytics infrastructure controlled by Tefteri, and is not shared with external third parties for their independent use.
Is all transmitted data encrypted in transit?	Yes. Communication with Firebase uses HTTPS/TLS.
Do you provide a way for users to request data deletion?	Yes. Users can delete entries and accounts in-app, or request deletion through theAccount Deletion page.

Notebook entries, history, reminder details, and optional sensitive notes
Collected: Yes (user-generated)
Shared: No
Purpose: Core functionality — tracking personal entries, reminders, and history.
Data handling: Users control entries and may delete or request full account deletion.

Sync metadata and analytics events (created/updated timestamps for entries, screen views, entry-form submissions, notification actions, sync/auth status, sanitized client errors, event timing, and limited metadata)
Collected: Yes
Shared: No
Purpose: Sync reliability, data integrity, analytics, and app reliability.
Data handling: Sync metadata is stored locally and, for signed-in sync users, in Firestore; analytics records are stored in first-party analytics infrastructure and retained only as long as needed for measurement, debugging, and trend analysis, normally no longer than 24 months.

Firebase or device identifiers processed by service SDKs, plus a random app analytics session identifier
Collected: Yes for the analytics session identifier; Firebase or platform SDK identifiers may also be processed automatically for authentication, security, and service reliability.
Shared: No
Purpose: Maintain authentication, security, analytics, and service reliability. Tefteri uses local device notifications and does not collect an Expo push token.
Data handling: Managed by the relevant service provider and deleted or disassociated where feasible when the account is deleted.

Location data, financial info, contact lists, photos & videos, microphone/voice data, calendar events (outside the app) — Not collected.

App functionality: Email, notebook entries, app activity, device IDs.
Analytics: App activity, app version, platform/device category, language, timing, sanitized client errors, and random analytics session identifiers.
Advertising: Not used.
Developer communications: Email for responding to support requests.
Fraud prevention, security: Device IDs, app activity used to protect accounts.
Account management: Email and user-generated data.

Handling Requirement	Approach
User-initiated deletion	Users can edit or delete visits/reminders in-app. Full account deletion is available in-app and through the public Account Deletion page.
Automatic deletion schedule	Account deletion requests are completed within 30 days unless retention is legally required. Backup copies may remain temporarily under Firebase/Google backup retention processes before automatic purge.
Data retention justification	Data retained while account active to provide notebook functionality.

The app may request notification permissions for reminders. No SMS, contacts, or phone permissions are requested.
No background location access or physical activity sensors are used.
No data is sold.
Update the Data Safety answers if you integrate new SDKs (analytics, ads, crash reporting beyond Firebase) or begin sharing data externally.

Privacy inquiries and deletion requests:privacy@pavlossta.com