Privacy policy
Last updated: May 2026 · Beta 0.3
This Privacy policy describes how Bitsync ("we", "us") handles information when you use the Service. The Service is in beta; practices may evolve. See also our Terms of use for limitation of liability and use-at-your-own-risk terms.
1. What we collect
- Account data: such as name and email address from your Google account when you sign in with Google. We do not use email/password sign-in.
- Sign-in with Google: we receive your verified email and Google account identifier to link or create your Bitsync account. We do not receive your Google password.
- App content you enter: budget periods, lines, categories, expenses, income, health-related metrics (e.g. steps, water, sleep), preferences, and similar data. Where this content is stored depends on your account setup — see section 3 (Google Drive) below.
- Technical data: typical server and hosting logs (e.g. IP address, user agent, timestamps) needed to operate, secure, and debug the Service.
2. How we use data
We use the information above to provide the Service (authentication, syncing your data with Google Drive when you have connected it, displaying dashboards), to maintain security, to fix bugs, and to comply with law. We do not sell your personal information. We do not use your data for third-party advertising in the Service.
3. Google Drive storage (with your approval)
If you complete Drive onboarding, you explicitly choose to store your budget, health, and preference data in your own Google Drive, not as the primary long-term copy on our servers. Summary:
- Your Drive, your data. App content is saved as files (for example budget, health, and preferences snapshots plus a sync manifest) in a Bitsync area of the Google Drive account you connect. You remain the owner of that Google account and those files.
- Not access to your whole Drive. Connecting Google Drive does not give Bitsync permission to browse, read, or modify your entire Google Drive, your photos, your other apps' files, or unrelated folders. Access is limited to what Google's OAuth consent screen describes for this app — typically creating and using files the app needs in your Drive (for example a dedicated app folder and the JSON files used for sync). We use that access only to read and write those Bitsync-related files when you use the Service.
- How sync works. The app keeps a working copy in your browser (for example IndexedDB) for speed. When you sign in or tap Sync, our servers use an encrypted OAuth token stored in our database to call Google's API on your behalf and transfer only those app snapshot files. We do not keep a permanent duplicate of your full app content in our database when Drive storage is active.
- You can revoke access. You may disconnect or revoke Bitsync's Google access at any time in your Google Account permissions. After revocation, sync may stop working until you reconnect; data already in your Drive generally remains there under Google's terms.
- We cannot recover lost Drive data. If files are deleted, overwritten, corrupted, unavailable due to a Google outage, lost because your Google account is closed or suspended, or lost for any other reason outside our control, Bitsync has no way to restore that data. We do not operate a separate backup of your Drive files. You are responsible for your own backups (for example Google Drive version history, exporting copies, or other tools Google provides).
- Sync is best-effort. Beta software may fail to sync, show stale data, or conflict if you use multiple devices. We do not guarantee that local and Drive copies are always identical or up to date.
4. Where data is processed
The Service relies on infrastructure providers (for example hosting, database, DNS, and Google's APIs). Account metadata and OAuth tokens may be stored or processed in data centres those providers operate. Your Drive-hosted app files are stored and processed under Google's privacy policy as well. By using the Service, you understand that subprocessors may handle data on our behalf under their terms and security practices.
5. Beta risk and limited liability
Because the Service is in beta, backups, retention, sync reliability, and incident response may not match enterprise-grade products. You should assume a higher risk of bugs, outages, sync failures, or data issues than in a mature commercial product.
To the maximum extent permitted by law, we are not responsible for loss or damage to your data — including data stored in Google Drive, data in your browser, or data on our systems — arising from use of the Service, Google or third-party failures, your actions, or events beyond our reasonable control. Full limitation-of-liability wording is in our Terms of use. Nothing in this policy limits your statutory rights where the law does not allow such limits.
6. Cookies and storage
The app may store authentication tokens or preferences in your browser (e.g. local storage, IndexedDB, or cookies) to keep you signed in, hold a local working copy of your data, and remember settings such as theme. You can clear site data in your browser to remove them; clearing data may affect offline use until you sign in and sync again.
7. Your choices
Depending on your jurisdiction, you may have rights to access, correct, or delete personal data we hold (such as account and token records), or to object to certain processing. Deleting app content stored only in your Google Drive is done through your Google account or by removing the relevant files. Contact the operator to exercise rights regarding data we control. We will respond in line with applicable law and technical feasibility.
8. Changes
We may update this policy; the "Last updated" date will change. Continued use after updates means you accept the revised policy where required by law.