Privacy Policy

Updated October 26, 2026 · Applies when the encrypted-vault release is enabled

Crypto Cashflow is a personal finance application operated by the owner of cashflow.limitraider.xyz. It helps you track assets, cashflow, budgets, and project estimates. This policy explains how information is handled in browser storage and when account sign-in and cloud storage are enabled.

Information we handle

• Account information. When you sign in with Google, Google provides your account identifier, email address and verification status, name, and profile picture if available. The app stores account information and authentication records needed to sign you in. Google handles your password; Crypto Cashflow does not receive it or request access to your Gmail messages, Drive files, or contacts.
• Financial information you provide. This includes assets, liabilities, balances, transactions, dates, notes, budget items, project estimates, settings, historical valuations, and data you import from a backup.
• Connected portfolios. If you connect a Jupiter or Hyperliquid portfolio or an Ethereum or Solana wallet, the app handles the public wallet address and the balances, positions, and prices returned for it. These connections read portfolio information; the app does not ask for your wallet seed phrase or private key.
• Technical information. The server and sign-in service may record IP addresses, browser information, request times, and error or security events to operate the service and limit abuse.

How information is used

Information is used to verify accounts, associate your records with your account, save and synchronize your data, calculate financial views, refresh connected portfolio values, and maintain the service. Google account information is used for sign-in and account features. We do not sell your information or use it for advertising, tracking across websites, or training AI models.

Where information is stored

You can use the app without an account, or sign in and still choose browser storage. In browser mode, your financial records stay in that browser and are not uploaded to your cloud account. Signing in alone does not transfer local records. Choosing cloud storage opens a separate set of account records; importing local records into it requires your explicit choice.

Cloud account records are stored in Postgres on the operator's VPS. New encrypted vaults encrypt financial records in your browser before upload. The normal server and database do not receive your vault passphrase, recovery key or unwrapped data key. Account identity, vault identifiers, encrypted sizes, versions and update times remain visible. Account checks restrict access to the signed-in user's stored records.

Account sign-in and vault unlock are separate. Resetting Google or email sign-in does not decrypt a vault. If both the vault passphrase and recovery key are lost, the service cannot recover encrypted records. Anyone with a vault secret and a corresponding encrypted file may be able to decrypt it.

Existing readable cloud accounts remain readable until you explicitly migrate. Migration retains the previous readable record in an operator-controlled archive for recovery. Older database backups, replicas, logs, files and other browsers may also retain readable data. Encryption of the active record does not erase those copies; their retention and deletion require a separate operator process.

Encrypted vaults keep pending drafts and recovery copies encrypted in this browser. Unlocked records and keys are held in memory as far as practical; JavaScript cannot guarantee secure memory erasure. Local-only mode still stores readable financial records. Older readable cloud browser caches can be replaced with verified encrypted copies after your consent. Local copies may remain after sign-out. Encrypted downloaded files need the secrets active when they were created; deliberate plaintext exports and older JSON files remain readable.

HTTPS protects network connections. Vault encryption does not protect against malicious code served by a compromised deployment, XSS, malicious extensions, malware, a compromised device or someone using an unlocked vault. The operator and software supply chain remain trusted for the code your browser runs. This application has not received an independent security audit.

Services that receive information

• Google processes Google sign-in and receives the information needed for that authentication flow. See Google's Privacy Policy.
• Contabo provides the infrastructure on which this website and its database run.
• Jupiter, Hyperliquid and Routescan receive public wallet addresses and related lookup requests through this application's server after you enable connected portfolio refreshes. Routescan supplies Ethereum wallet balances; token identifiers are sent to DefiLlama for prices. Jupiter supplies Solana wallet balances and prices. The app server sees the lookup and returned balances, positions and prices, and keeps successful Ethereum and Solana wallet results in memory for two minutes. Providers see the server connection and, for Jupiter, its API-key organization. A public address can link activity to a person; vault encryption does not hide these lookups or public blockchain records. Your entered budgets, project estimates and Google profile are not included in portfolio requests. Encrypted vaults refresh only while unlocked; consenting readable legacy accounts may use an operator-enabled background collector.
• The exchange-rate service at open.er-api.com receives requests directly from your browser for currency rates, including normal connection information such as your IP address. The app does not send your financial records in these requests.
• A configured email provider receives your email address and sign-in message if email-code backup is enabled and you request a code. Email-code sign-in is unavailable until a mail service is configured.

These services process information under their own terms and privacy policies. Information may be disclosed if required by applicable law.

Cookies and browser storage

If you sign in, essential session cookies keep you signed in and support the authentication flow. Browser storage preserves records, preferences, and pending changes. The app does not install advertising cookies or third-party analytics. Blocking cookies can prevent sign-in; clearing browser storage can remove local records and changes that have not yet synchronized.

Your choices, retention, and deletion

You can edit or delete financial items in the app and download a backup from Settings. Removing a connected portfolio stops its future refreshes in the app; it does not delete public blockchain records.

Saved records, legacy migration archives and encrypted browser recovery copies do not automatically expire in this release. To request account deletion or removal of server-stored records, contact the owner who provided access. We may ask you to verify the account; do not send vault secrets to support. Archives, replicas and backups require a separately approved retention/deletion process and may retain earlier copies. Copies on your devices and downloaded files must be removed separately. We do not claim cryptographic erasure of historical plaintext.

You can revoke Google access through your Google Account connections. Revoking access or signing out does not by itself delete records already saved in the app.

Contact and changes

For privacy questions or data requests, contact the owner of Crypto Cashflow through the contact channel used to arrange your access. An account is optional for using browser storage.

Updates to this policy will be published at this URL with a revised effective date. If the app introduces a new use of Google account information, the disclosure will be updated and consent requested before that new use begins.