Privacy in the BonusCircuit beta
Updated November 5, 2026. This notice describes the currently deployed beta. It is not a claim of a completed privacy or security certification.
Records you provide
Your browser stores workspace records locally. If you create an account, the app sends your email address, password for hashing, and synced profile, offer, account, activity, and reminder records to the BonusCircuit server over HTTPS. Do not enter bank passwords, full account numbers, routing numbers, identity documents, or other credentials.
Storage and access
The application is hosted on a DigitalOcean server. Passwords are stored as Argon2 hashes. Session tokens are stored hashed on the server. Notification endpoints, authenticator secrets and purchase proofs use server-side encryption when those features are configured. Workspace records are not end-to-end encrypted; the server operator can access them.
Optional services
External payment stores and email delivery have not been activated for this beta. No real payment is collected. Browser push requires your permission, an enabled endpoint and an eligible plan. When enabled, external delivery messages use generic content rather than your account names, amounts or deadlines.
Retention and your controls
You can export records in Settings. Deleting your account removes its active server records; existing database backups can retain them until the configured 30-day local retention period expires. Local browser storage and exported files must be removed separately. Signing out clears the app’s local workspace cache. A subscription, when available, must be cancelled separately through its provider.
Operational logs
The server keeps request, security, delivery and audit information needed to operate the beta. The landing page has no advertising trackers or analytics. Server access logs may include connection information. Operator identity, a support contact and the final release privacy terms remain to be completed before a general release.
Return to BonusCircuit