Privacy architecture

Private by design,
plain by explanation.

Wealth Clarity stores financial information in your browser using IndexedDB. There is no account, sync service, analytics pipeline, or bank connection.

Architecture note · updated July 18, 2026 · not a lawyer-reviewed policy

01

What is stored

The app stores a primary local profile containing entered balances, monthly amounts, yes-or-no protection details, declared unknowns, and update timestamps. It also stores a versioned consent record in this browser.

Its offline shell may be cached so supported routes can reopen without a network connection.

02

What leaves your device

No entered financial values are sent to a remote service. There is no login, analytics SDK, cloud database, or bank-data provider in the product.

The public website’s release-status control stores one local, non-financial flag and sends nothing.

If you choose a “Talk with Nicole” link, your browser opens Nicole Andrea Spencer’s separate website. The link contains no map data, answers, totals, or identifying details from Wealth Clarity.

03

Your controls

  • Skip an intake value or explicitly mark an area unknown.
  • Export the profile, calculated snapshot, questions, run records, and consent record as readable JSON.
  • Delete the profile, consent record, legacy profile key, and Wealth Clarity offline cache.
04

The current legal boundary

Formal privacy language, retention rules, PIPEDA mapping, Quebec Law 25 analysis, breach procedures, and a named privacy contact still require qualified Canadian legal and operational review before public financial-service launch.

See the conversation and contact boundary or read the terms of use.