1. Default-deny choices
On a first visit, the consent panel gives equally understandable routes to keep Essential only or Allow analytics, plus details. Ignoring or closing a prompt is not consent. Marketing storage is not used in this release.
Necessary storage is used without consent only where it is genuinely required to provide a feature you request, preserve a choice, secure the service or meet another applicable exemption. Optional analytics must not load or transmit events before consent.
2. Necessary cookies and browser storage
bw_finance_v4 — local storage
Contains your workspace, preferences and financial entries so the app can function locally. It has no fixed expiry and remains until you delete/reset the workspace, clear site data or the browser removes it.
bab_v3_state — legacy local storage
If present from the legacy app, it may be read to migrate a workspace. It remains until you clear it. Tenthwise does not need to create it for a new workspace.
bw_email_for_signin — temporary local storage
Holds an email address after you request an email sign-in link so sign-in can finish on the same browser. It is removed after successful completion; you can also remove it by clearing site data.
bw_country and bw_locale — cookies
Remember the country and language/locale you save so the requested regional experience can be restored. Current maximum age: one year. Attributes: Path=/, SameSite=Lax and Secure.
tenthwise_consent_v1 — local storage
Records the consent-policy version, necessary status, analytics and marketing choices, and decision time so the site can respect and demonstrate your selection. It remains until you change it or clear site data.
tenthwise_consent — cookie
Stores essential or all so the website can apply your selection. Current maximum age: 180 days. Attributes: Path=/, SameSite=Lax and Secure.
Optional Firebase authentication, if enabled and requested, may set or use provider-controlled browser storage required to keep you signed in and protect the session. The exact names and lifetimes vary by Firebase configuration and must be captured in the final production audit.
3. Optional analytics and marketing
The interface can record an “analytics allowed” preference, but no analytics provider is specified in this release. Before any analytics is activated, this policy and the consent panel must identify the provider, storage names, purpose, event fields, recipients, expiry, international transfers and how consent is relayed or withdrawn.
Marketing storage, cross-site advertising and tracking pixels are not enabled. If that changes, they will remain off until valid consent and will be listed separately rather than bundled with analytics.
4. Change or withdraw your choice
Use the control here or in the footer at any time. Choosing “Essential only” withdraws optional analytics consent for future processing. Withdrawal does not make earlier consent-based processing unlawful.
You can also remove stored data in your browser’s site/privacy settings. Doing so may erase the local workspace, sign you out and reset preferences. Export your workspace first if you want to keep a copy. Browser blocking can affect necessary features.
A browser “Do Not Track” signal is not currently a substitute for the explicit choice control. Because optional analytics defaults off, no optional processing should begin until consent regardless of that signal.
5. Updates and contact
We will update this policy if storage, providers or purposes change and ask again where a change requires renewed consent. The final operator must periodically audit the live site against this inventory.
Operator, privacy contact and business address: pending before commercial launch. See the privacy notice for data-protection rights and supervisory-authority information.