Owner review required before publication. Verify this policy against OneRecord’s actual data handling, backend behavior, and applicable requirements.
1. Introduction and scope
This Privacy Policy applies to the OneRecord Android application, this public website, and related support and account-deletion processes operated by Electronic Droid.
OneRecord helps people maintain subscription, expense, budget, renewal, and related personal-finance records. The application can be used locally. Authentication, cloud synchronization, Google Drive backup, Android Usage Access, and exports are separate features that a user may choose.
Back to contents ↑2. Information stored locally
OneRecord may store account-scoped application records in a local SQLite/Drift database on the device, including:
- Subscriptions, expenses, budgets, budget allocations, and categories
- Renewal dates, reminders, subscription audits or usage answers, and price history
- Non-sensitive payment-display metadata, such as a label or the last four digits
- Appearance, currency, notification, application, and home-screen widget preferences
- Local Android app-usage summaries when that optional feature is enabled
OneRecord is not intended to collect or store full payment-card numbers, CVV codes, bank passwords, or banking credentials.
Back to contents ↑3. Account information
If you choose Google/Supabase authentication, the providers may process a Supabase user identifier, display name, email address, profile metadata needed for account features, and authentication or session data. Authentication credentials and sessions are managed through those providers; OneRecord does not ask you to provide your Google password.
Back to contents ↑4. Optional cloud synchronization
Authenticated users may choose to synchronize eligible subscription fields with Supabase, such as a record identifier, name, price and currency, billing interval, renewal information, category, status, notes, timestamps, and account ownership identifier. The exact production schema must be verified before this policy is published.
Expenses, budgets, Android app-usage summaries, and other local records remain local-only unless the application and final policy explicitly say otherwise. Cloud synchronization is not required for core local record keeping.
Back to contents ↑5. Google Drive backup
Google Drive backup is optional. When enabled, OneRecord requests the narrow Drive application-data scope and stores a private application backup in Google Drive’s hidden application data folder. OneRecord does not need permission to browse unrelated personal Drive files.
A backup may contain subscriptions and supported local application records. Authentication credentials, API keys, access tokens, Google tokens, Supabase JWTs, complete payment-card information, CVV values, and passwords are excluded.
Back to contents ↑6. Android Usage Access
App-usage insights are optional and Android-only. Android grants Usage Access at the application level; OneRecord processes only selected or linked subscription applications. It derives daily summaries such as foreground time, approximate sessions, active days, and last-used time. Raw Android usage events are not retained.
These summaries remain on the device and are excluded from Supabase synchronization and Google Drive backup. They cannot measure usage on televisions, browsers, computers, other phones, or background listening. You can stop tracking, delete stored summaries in OneRecord, and revoke Usage Access in Android system settings.
Back to contents ↑7. Exchange-rate data
OneRecord may request daily reference exchange rates from the Frankfurter service to prepare reporting-currency views. These are reference rates, not real-time trading quotes. The provider may receive ordinary network information, including an IP address and request metadata, under its own privacy practices. Original records retain their native currency.
Back to contents ↑8. Notifications
Renewal reminders and application notifications are scheduled on the device where applicable. You can disable notification categories inside OneRecord and revoke notification permission through the device’s operating-system settings.
Back to contents ↑9. Data export and sharing
You may generate PDF or spreadsheet exports. OneRecord presents those files to the operating-system share controls only when you request it. Once you choose a third-party destination, that destination controls its copy under its own terms and privacy practices.
Back to contents ↑10. Data collected automatically
This website does not include advertising SDKs, behavioral analytics, or non-essential cookies by default. It stores only an appearance preference in local browser storage. The configured hosting provider (Vercel) may process essential server logs such as IP address, user agent, request path, timestamps, and security events.
The production application’s crash reporting, diagnostics, SDK telemetry, and hosting configuration must be verified and disclosed here before publication.
Back to contents ↑11. Purposes of processing
Information is processed as needed to provide requested app functionality, authenticate users, synchronize and recover eligible records, create user-requested backups, schedule reminders, perform reference currency conversion, protect security and service reliability, prevent misuse, and respond to support or deletion requests.
Back to contents ↑12. Third-party service providers
Optional authentication and eligible subscription synchronization. Privacy information
Optional account authentication. Google Privacy Policy
Optional backup in the hidden application-data area. User Data Policy
Android platform and distribution functionality. Google Privacy Policy
Daily reference exchange-rate data. Service information
Website delivery, security, and essential request logs.
13. Data sharing
Service providers process limited information to provide authentication, synchronization, backup, exchange-rate, platform, hosting, and support functions. That processing is different from selling personal data.
OneRecord is not intended to sell personal information or use it for cross-context behavioral advertising. The operator must verify this statement against all production SDKs, contracts, and business practices before publishing.
Back to contents ↑14. Data retention
Local data remains until you delete it, clear application storage, remove account data through the application, or uninstall OneRecord. Cloud records generally remain while an account exists or until deletion is requested, subject to limited retention required for security, legal, or operational purposes.
Support and deletion-request records are kept only as long as needed to complete and document the request. Provider backups and recovery systems may require a reasonable deletion period.
Back to contents ↑15. Account and data deletion
Visit the public Delete Account and Data page for in-app steps and the website request path. A completed account deletion may remove the authentication account, synced subscription records, cloud profile metadata, and eligible OneRecord backup data according to the confirmed backend behavior.
Deleting the app does not necessarily delete an online account. Deleting an online account does not remove copies you separately exported or shared. Device-local data must be removed through the in-app flow, by clearing application storage, or by uninstalling the application. If Drive backup deletion cannot be completed on the website, use the in-app flow before account deletion or request support.
Back to contents ↑16. Security
OneRecord uses reasonable technical and organizational safeguards appropriate to the service, which may include scoped provider access, transport encryption, access controls, input validation, and secure credential handling. No system can guarantee absolute security. Sensitive service credentials are not intentionally included in browser code.
Back to contents ↑17. User choices and rights
Depending on your location, you may have rights to access, correct, export, restrict, object to, or delete personal information. OneRecord also provides controls to withdraw optional permissions, disable notifications, stop app-usage tracking, manage backup, and request account deletion. Contact electronicdroidofficial@gmail.com to exercise applicable rights.
Back to contents ↑18. Children’s privacy
The configured minimum user age for OneRecord is 10 years. If the operator learns that information was processed from a child contrary to applicable law, it will take reasonable steps to delete it.
Back to contents ↑19. International processing
Service providers may process information in countries other than the one where you live. Where applicable, the operator and its providers use appropriate legal mechanisms and safeguards for international processing.
Back to contents ↑20. Changes to this policy
This policy may be updated as OneRecord changes or legal requirements evolve. The “Last updated” date will change when revisions are published. Material changes may also be communicated inside the application where appropriate.
Back to contents ↑21. Contact information
Privacy questions and rights requests can be sent to electronicdroidofficial@gmail.com. The responsible developer or legal entity is Electronic Droid, located at India.
For account deletion, use the public deletion page. For general help, visit Help & Support.
Back to contents ↑