Privacy Policy

1. About this notice

WealthLens is a personal finance management and analytics application. It has no user accounts, authentication, database or bank connection. Use sample or non-sensitive information. Anyone with access to the same browser profile may access its records.

This notice describes the application code. Production hosting, infrastructure logs, operator identity, processing locations and applicable jurisdiction require owner review before public use.

2. Information you choose to enter

Profile fields can include a display name, age, occupation, base currency, monthly income and savings target. Financial records can include manual accounts, opening balances, transaction dates, amounts, categories, notes, budgets, goals and earmarked contributions. Backup and CSV imports provide the records you choose to import.

Cookie choices, requested application activation, tutorial status and permitted appearance, language and sidebar preferences are also stored. Do not enter bank credentials, payment-card details, government identifiers or another person's private financial information.

3. Storage, requests & recipients

Cookies are stored by your browser and sent to the WealthLens Next.js server on matching requests. The server decodes records to render pages, calculate summaries and process validated Server Actions. Data is not confined solely to your device. No application database or filesystem persistence is implemented.

The application includes no analytics or marketing tracker and does not send financial records to an external service. The hosting operator necessarily receives requests; infrastructure logging, hosting recipients and processing countries depend on deployment and are not verified here. External product or social links only navigate when activated and then follow the destination's own policies.

4. Retention & deletion

Financial cookies have a maximum age of one year from a successful write; the browser can remove them sooner. The onboarding draft expires after one hour. Exact cookie lifetimes and purposes appear in the Cookie Policy. Clearing browser site data, expiry or losing the browser profile can remove records permanently.

Settings provides separate confirmed reset operations. Clearing financial data removes financial entities while retaining the profile; resetting all data removes the profile and returns to onboarding. Exported CSV files and JSON backups are separate files under your control and are not deleted by clearing site cookies.

5. Your choices & controls

Public pages remain available without optional-cookie consent. Starting the finance application is a deliberate request to activate its cookie storage. Optional preferences can be accepted, rejected or changed through Cookie Preferences. Refusing optional preferences does not prevent using the core application.

You can inspect and edit entered records, export your data, and use confirmed deletion controls in Settings. Withdrawing optional preferences clears the related controllable cookies and does not silently erase financial records. Browser cookie controls offer an additional way to remove all site data.

6. Security & practical limitations

Financial cookies are HttpOnly, use SameSite=Lax and are marked Secure on HTTPS deployments. Server boundaries validate mutations, origin and storage quotas. These safeguards do not provide authentication, end-to-end encryption, encryption at rest or bank-grade protection. Cookie compression is not encryption.

Use HTTPS when deploying. Avoid sensitive data and shared browsers. Cookie capacity is intentionally limited, and data loss or corrupted storage can occur. Keep private backups if you need to retain records; this tool is not reliable long-term financial storage.

7. Children's information

This application is not designed to collect children's information. Do not enter information about a child. Age fields are optional profile information and do not verify identity or establish that parental consent has been obtained. The owner must review any age restrictions and applicable duties before offering the service to children.

8. Policy changes

The document version and update date identify this draft. Material changes to cookie purposes require updating the inventory and preference policy version so users can review their choices again. A production operator must confirm the actual deployment disclosures and any applicable legal notices before publication.