1. Introduction
This draft describes potential privacy considerations for CoinQuest, an Android personal expense tracking application developed by Leiji Mark Gaviola. Replace or confirm this language after verifying the released app and all services it uses.
2. Information users enter
Based on the inspected app project and screens, users can enter financial records such as income source and amount, expense name and amount, expense category, dates, savings goal details, and amounts added toward a goal. These entries may be sensitive personal information. The actual data collected, processed, or shared must be confirmed from the release build and applicable services.
3. Automatically collected information
Not yet verified. The app package, embedded Android libraries, distribution configuration, and any analytics, diagnostics, advertising, or platform services must be reviewed before stating whether technical or device information is collected automatically.
4. Local storage and TinyDB
The provided MIT App Inventor project uses TinyDB components. The project includes TinyDB reads and writes for app values, including income, expenses, savings information, and sound preference. This confirms use of TinyDB in the project source; it does not by itself establish the full storage lifecycle, security properties, backup behavior, or whether any data is transmitted by the final app or its dependencies.
5. Purposes of processing
Financial entries are used by app features to display totals, transaction history, reports, and savings progress. Confirm whether any information is processed for additional purposes by libraries, operating-system features, or distribution services.
6. Third-party services and data sharing
Not verified. Before publishing, identify each included SDK or service, the information it receives, its purpose, and its own privacy terms. Do not claim that CoinQuest shares no data until the compiled release and all integrations have been checked. Google Play and Android may process information under their own terms.
7. Data security
Specific security safeguards have not been verified for this draft. No claim is made here about encryption, secure deletion, or protection against unauthorized access. Review the app and storage implementation before making any security statement.
8. Retention and deletion
The app's data retention and deletion behavior must be confirmed. Verify what happens when users edit records, clear app data, uninstall the app, restore a device, or use Android backup. No account deletion or cloud deletion feature is confirmed by the materials reviewed.
9. Children's privacy
The intended age range and applicable child-directed data practices have not been verified. Confirm the app's target audience and Google Play declarations, and document appropriate handling before publishing this section as final.
10. User choices and rights
Users can contact the developer with questions or requests concerning privacy. The actual ability to access, correct, export, or delete data depends on the verified app storage and services. Contact leijigaviola@gmail.com for privacy inquiries.
11. Policy updates
This draft may change when the app or its data practices change. When finalized, update the effective date and explain material changes on this page.
12. Developer contact
Developer: Leiji Mark Gaviola
Email: leijigaviola@gmail.com
Publication gate: Do not submit this page as the final Google Play Privacy Policy until the checklist in docs/privacy-verification.md is completed and all statements are checked against the released app and Data Safety form.