This policy explains how the Your Timesheet application handles information. It describes version 1.0.0 (versionCode 1) and should be reviewed if the application’s behaviour or dependencies change.
1. Local application data
Your Timesheet stores timesheets and settings locally on the user’s device. The application does not require a Your Timesheet account and does not operate a developer backend or cloud-sync service for timesheet data. It does not automatically upload timesheet data to the developer.
Depending on what the user enters and configures, local data may include a name; dates; start and finish times; breaks; day classifications; comments; worked-time values; working days and standard hours; overtime rules; an optional hourly rate; appearance, field, label, app and export preferences; and versioning metadata used to validate and interpret the data.
Earnings estimates are calculated from locally stored hours, rates and rules. They are not payroll records and are not transmitted to the developer.
2. Earnings display and export preferences
Show earnings in app controls whether monetary estimates appear inside the application. Include earnings in exports controls whether earnings information is included by default in newly created Excel and PDF exports. Changing either preference does not delete the underlying hourly-rate or pay configuration.
3. Excel and PDF exports
Excel and PDF files are generated only when the user chooses an export action. Exported files are separate from the private application database. On Android they can be saved to Downloads and may contain timesheet details and, when selected, earnings information. They are not automatically uploaded to the developer.
4. Sharing files
Android Share is user initiated. Your Timesheet passes the selected export to the Android system share interface only after the user chooses Share File. A transfer occurs only after the user selects a destination application or service. That destination operates under its own terms and privacy practices.
5. Backup files and restore
A Your Timesheet backup file is created only when the user requests one. Where values exist, it can contain timesheet entries, settings, hourly-rate and pay information, comments, preferences and version metadata. Backup files are not encrypted or password-protected by the app and should be stored somewhere trusted.
Restore is user initiated. The app validates supported backup data before replacing current local data. Selecting a file for preview does not itself replace data.
6. Deleting data
Clear Month Data deletes Daily Entry records for the month explicitly selected. It does not remove settings, other months, exports or backup files. Android normally removes current private local data when the app is uninstalled. Files exported, backed up or sent outside app-private storage must be deleted separately by the user.
7. Internet, analytics and advertising
Core timesheet functionality does not require an internet connection. Your Timesheet does not include advertising, analytics, telemetry or crash-reporting services. The Android package includes the framework’s normal INTERNET permission, but the audited production application contains no developer backend, remote timesheet service or automatic application/SDK user-data transmission.
8. Android operating-system backup
The Android manifest permits Android backup and does not define app-specific include or exclude rules. If device backup is enabled, Android may include eligible application-private data in an operating-system backup to the user’s Google account or support device-to-device transfer.
These services are controlled by Android, the device manufacturer and the user’s settings. They are separate from Your Timesheet’s JSON backup feature. The developer does not receive or have access to Android system backup datasets. See Android’s Auto Backup documentation.
9. Third-party code and applications
Your Timesheet packages software libraries used to render the interface, store information locally, create Excel/PDF files and invoke Android file/share features. The audited production dependency set does not include advertising, analytics, telemetry or crash-reporting SDKs. A third party’s privacy practices apply when a user deliberately sends or stores a file with that provider.
10. Contact and public-policy status
Privacy or data-handling enquiries: