Privacy

What NetCaptr stores, and where

NetCaptr runs in your browser and keeps your data on your device. The workspace — portfolios, containers, accounts, records, planned and recurring records, automation rules, categories, and labels — runs in your browser and does not require you to create an account before you can use it.

By default, the data you enter stays in your browser on your device. There is no NetCaptr backend that mirrors your records, and the landing site does not ask you to hand over your financial accounts to get started. NetCaptr does not ask for bank credentials, and neither the app nor this site runs analytics or advertising trackers.

You can bring your own storage. If you connect Google Drive, the app reads and writes your workspace data to your own Drive — not a NetCaptr server — using the permissions you grant Google. You can disconnect Drive at any time and the local workspace keeps working. Exporting and importing JSON is always available as an alternative under your direct control.

Connecting Drive turns on automatic sync by default. While your Google account is connected and auto-sync is on, NetCaptr uploads a snapshot of your workspace shortly after you change something, and downloads the newest snapshot when you return to the app — you do not have to press a button each time. Before every upload it re-reads what is already in Drive so a second device’s work is not overwritten; if the two sides have genuinely diverged, sync pauses and asks you which version to keep. You can switch auto-sync off in the cloud-backup dialog and move data only when you press sync or load. Disconnecting stops all of it, and your local workspace is untouched.

If NetCaptr adds further storage destinations or optional integrations in the future, treat each one as a separate choice that you opt into. If you have a question about privacy or data handling, or about a feature on the public roadmap, contact John Erwin Fabre before using that feature for anything sensitive.

Google API Services

When you connect Google Drive, NetCaptr requests two OAuth permissions from Google:

• openid — verifies your Google identity so the app can silently re-authenticate your session without prompting you on every visit.
• drive.appdata — reads and writes a single JSON backup file to your Google Drive Application Data folder. This is a private per-app space within your Drive that is not visible in the standard Drive UI and requires explicit OAuth consent to access.

No Google user data — including your Google account information or any Drive content — is transmitted to a NetCaptr server. The backup file lives solely in your own Google Drive. NetCaptr does not share, sell, or use this data for any purpose other than keeping your own workspace in sync across the devices you connect.

To make that sync safe, a few small values are kept on your device alongside your workspace: a random identifier for this browser, the identifier of the Google account you connected so re-authentication stays silent, and bookkeeping about the last successful sync. The Google access token itself is held only for the life of the browser tab and expires on Google’s schedule.

Signing out of Google clears your access token and the sync bookkeeping. One thing stays: the random identifier for this browser, which NetCaptr keeps so that if you reconnect Drive later it can still tell whether the file in Drive was written here or on another device. It is not a credential, it is not tied to your Google account, it identifies a browser rather than a person, and it never appears in an export — restoring your backup on another device cannot make that device look like this one. Clearing this site’s data removes it along with everything else NetCaptr has stored here.

Disconnecting stops all syncing and leaves your local workspace untouched. The snapshot already in your Drive stays there — it is your file, in your account, and NetCaptr has no way to reach into your Drive and delete it. To remove it, use Google’s own controls: in your Google account, Drive’s settings list the apps that hold hidden application data and let you delete that data. Revoking NetCaptr’s access there also ends its permission to write a new one.

NetCaptr’s use of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.

Installing and offline use

NetCaptr can be installed from your browser and used offline. What gets cached for that is the application itself — the code, styles, and icons — not a copy of your financial data sent anywhere. Your records were already on your device; installing simply lets the app start without a network. Uninstalling or clearing site data removes the local workspace, so export a JSON backup or connect Drive first if you want to keep it. The app loads its typeface and icon fonts from Google Fonts the first time you open it, and caches them on your device afterwards. No other third-party request is made unless you connect Google Drive.