Data Retention and Deletion Policy

We aim to collect only information needed for the service, retain it only for a justified purpose, and remove it when it is no longer needed, subject to applicable law. We distinguish financial planning records from account identity, security, support, and provider-held records.

We do not promise a retention period or legal exception that has not been established. Specific periods for logs, backups, support records, and request records still require review. Our Privacy Policy explains the information we collect, service providers, and your privacy rights.

• Planning information: your profile, settings, income, expenses, budgets, paycheck allocations, goals, assets, debts, activity and net-worth history are saved in the application’s PostgreSQL database. They remain until you change or clear them. There is no automatic age-based deletion schedule in the current app.
• Account identity: your Whop identifier, available name/email and account timestamps are stored separately from the financial plan. The planning-data reset does not remove this identity record.
• History access: a plan’s limit on displayed history does not mean older database records are automatically deleted.

In Settings → Your data, Export my data downloads your saved planning data as a JSON file and is available on Free. Plus also provides CSV exports. These exports do not include Whop’s separate payment records or the application’s separate identity record.

You can correct planning entries in the relevant app sections. Contact spenzoadmin@gmail.com for access, correction, portability, or deletion requests beyond the app’s existing controls. We may need to verify your identity to protect your account; do not send passwords, tokens, card numbers, or unnecessary identity documents.

Downloaded exports are copies on your own device. Clearing your app data does not delete those files.

Settings → Your data → Delete all my data resets the financial plan and returns you to setup after the change saves. It preserves your theme preference.

When that save succeeds, the existing income, expense, paycheck, goal, asset, debt, activity and net-worth-history rows are replaced with the default/empty plan in the active application database. A default financial profile remains, and the separate account identity record is not deleted.

This reset does not delete your Whop account, cancel a subscription, invalidate sessions on every device, or establish immediate erasure from provider backups and logs.

A complete self-service account/identity deletion workflow is not currently implemented. Requests beyond the planning reset require manual handling through spenzoadmin@gmail.com. We must determine the request’s scope, verify the requester as appropriate, review actual legal or contractual requirements, and confirm only actions that have been completed. We will explain any necessary exceptions or remaining provider-held copies rather than represent a plan reset as complete account deletion.

• Session cookies: the signed Razka session lasts up to 30 days and renews during active use. Logout clears session cookies in that browser. Temporary OAuth cookies expire after ten minutes and are cleared during the callback.
• Appearance preference: browser local storage remembers your theme until you change or clear it. Financial data also exists in browser memory while the app displays it; the app does not explicitly persist the financial plan in browser local/session storage.
• Logs: the application and its infrastructure providers may keep operational/error records. A complete redaction process, access/retention configuration, and automatic deletion schedule have not been verified by this policy. Retention requires operational review; no fixed number of days is promised here.
• Support: the Contact page opens your email app. Mailbox retention and access are separate operational responsibilities. We should keep only the information necessary to handle a request and should not request bank credentials or full financial exports by email.
• Payments: Whop holds its own account, subscription and payment records under its terms and legal obligations. Use Settings → Plan or your Whop account to manage billing separately.

Database/hosting backup schedules, retention, restoration and deletion propagation are not established by application code and require provider verification. Clearing the active plan does not prove that every backup copy has been erased.

No legal-hold mechanism or automatic retention scheduler is implemented in the app. Any restriction on deletion must be based on a real, identified legal or contractual requirement with a defined scope—not an assumed obligation to keep all financial records.

Retention periods and any backup-restoration procedure must be reviewed so restoring a backup does not improperly reintroduce information that should have been deleted. That process still needs operational implementation and verification.

Bank syncing is not live in the current application. There is no active Plaid Link, token exchange, bank synchronization, recurring-transaction import, or bank-disconnect/revocation workflow.

Before bank connectivity launches, we will update the public disclosures and seek consent before connecting an account. The planned approach is to keep application-managed bank data and access tokens server-side in Neon, collect only needed information, and verify ownership for every operation.

Disconnect and complete account-deletion controls must stop synchronization and revoke applicable Plaid access before erasing tokens, then handle associated stored records under the adopted data-minimization rules. These are launch requirements, not controls represented as operational today. Failed revocation, provider copies, and deletion retries must be addressed before activation.

Contact spenzoadmin@gmail.com for the attention of Nicolas Abdo, the person responsible for the protection of personal information. We will assess the request under applicable privacy requirements, including Quebec’s private-sector privacy law as amended by Law 25, PIPEDA where applicable, and GDPR/UK GDPR where applicable. This policy does not limit your statutory rights.

Our Privacy Policy explains request and complaint options, including contacting the Commission d’accès à l’information du Québec or the Office of the Privacy Commissioner of Canada where applicable.

We will review this policy before bank syncing launches and when data categories, purposes, providers, legal requirements or lifecycle behavior change. We will revise the published update date when the policy changes.