Spendwise policies · Draft for review
Cookie Policy
A plain-language overview of the browser cookies and local preference storage used by Spendwise.
Draft date: October 15, 2026
1. What cookies are
Cookies are small pieces of information stored in your browser. Similar technologies can also store or access information on your device. This policy covers the application’s current use; the operator should review it whenever analytics, embedded content, or other third-party tools are added.
2. Cookies used for authentication
Spendwise uses Auth.js with database-backed sessions and Google sign-in. During sign-in and authenticated use, Auth.js may use first-party cookies for the session token and for security or OAuth flow state (such as CSRF protection, callback state, or PKCE). Exact cookie names and options can differ between local development and production settings.
These cookies help protect sign-in and keep a signed-in user’s session working. They are not used by the application for advertising or cross-site tracking. Clearing them may sign you out or require you to restart sign-in.
3. Analytics and advertising cookies
When you choose “Accept analytics” in the consent banner, Spendwise may enable PostHog product analytics to understand usage events such as page views and sync, import, and forecast actions. The analytics script is configured with in-memory persistence, does not record sessions, and does not capture form input. No advertising cookies or tracking pixels are used. Choosing “Only necessary” keeps optional analytics disabled.
4. Third-party and hosting technologies
Google participates in the sign-in flow and Google Ads data sync only when a user chooses those features. Meta participates in data sync only when a user connects Meta Ads. Hosting, security, or delivery providers may use their own technical technologies; the service operator must identify and document the providers and technologies used by the production deployment.
5. Managing cookies
You can use the consent banner to choose “Accept analytics” or “Only necessary.” Your choice is stored in browser local storage under a Spendwise-specific consent preference so the banner does not reappear on every page. It is not a tracking cookie and is not sent to the application server. Clearing site storage removes the choice and shows the banner again. Blocking authentication cookies may prevent Google sign-in or the Spendwise workspace from functioning. Spendwise uses a light interface throughout.
6. Questions and updates
For cookie questions, contact [add the operator’s monitored privacy contact]. The operator should confirm the production cookie inventory, contact information, and applicable jurisdiction before publishing this policy as final.