Spendwise policies · Draft for review
Privacy Policy
This draft describes the information processed by the current Spendwise application when people sign in, connect advertising accounts, import campaign data, and optionally generate AI reports.
Draft date: October 15, 2026
1. Who operates Spendwise
Spendwise is operated by [add the responsible business or legal entity] (the “operator”). The operator’s privacy contact is [add a monitored privacy contact email or address]. Complete these details before inviting customers or making the service public.
2. Information the service processes
- Account and sign-in details: name, email address, profile image, Google account identifiers, and session/account records needed for Google sign-in.
- Workspace information: organization and project names, membership, invitations, job title, and access role.
- Advertising information: account identifiers and connected account credentials; campaign identifiers and names; daily spend, conversions, revenue/value when provided, impressions, clicks, CPA, ROAS, and related metrics.
- Uploaded information: rows and fields in CSV files submitted by a workspace member. Do not upload personal or confidential information unless you are authorized to do so.
- Forecast and report information: forecasts, ranges, backtest results, and AI-generated reports associated with a project.
- AI configuration: selected provider, model, optional endpoint, and API key. Configured AI provider keys and advertising connection credentials are encrypted before storage by the application.
- Display preference: Spendwise uses a light interface. Consent choices are stored locally in your browser and are not sent to the application server.
3. How information is used
The application uses this information to authenticate users, operate organizations and projects, enforce project permissions, import or sync campaign history at a user’s request, calculate forecasts and backtests, and create reports when a user requests them. It may also be processed to maintain security, troubleshoot errors, and operate the service.
4. When information is sent to other services
- Google: Google is used for sign-in. When a user configures Google Ads, Spendwise sends authenticated requests to Google Ads to retrieve the selected account’s campaign history.
- Meta: when a user configures Meta Ads, Spendwise sends authenticated requests to Meta to retrieve the selected account’s campaign history.
- Database host: account, workspace, campaign, forecast, and report records are stored in the configured PostgreSQL database (currently Neon).
- AI provider, only when requested: generating a report sends campaign names and sources, recent spend and conversion figures, current and predicted metrics, forecast ranges, and calculated improvement/stability/decline probabilities to the configured AI provider. The provider may be OpenAI, Google Gemini, Anthropic, xAI, Mistral, DeepSeek, Cohere, or an operator-configured OpenAI-compatible endpoint. That provider’s terms and privacy practices apply to its processing.
Do not configure a provider or submit data unless your organization is permitted to share that information with the provider. Review provider settings and applicable provider terms before use.
5. Storage and security
The service stores project information in its configured PostgreSQL database. Advertising-account credentials and AI API keys are encrypted by the application before being saved. Authentication and account records are stored separately to support Google sign-in. No system can be guaranteed completely secure; the operator should document its production hosting, access controls, backups, and incident process before launch.
6. Retention and deletion
Campaign history, forecasts, backtests, and generated reports remain in the project database until they are removed by the operator or according to the operator’s retention process. The current application does not provide a self-service account or project-data deletion workflow. A member can remove a configured advertising connection, but removing a connection does not necessarily delete previously synced campaign records.
To request access, correction, export, or deletion, contact [add the operator’s privacy contact]. The operator must establish and publish a specific retention schedule and request-handling process before production.
7. Cookies and similar technologies
Spendwise uses authentication cookies needed for Google sign-in, account security, and maintaining a session. Optional PostHog analytics is enabled only after a visitor chooses “Accept analytics” in the consent banner. Consent choices are stored locally in the browser. See the Cookie Policy for more detail. The operator should also check its hosting and deployment providers for any separate technical cookies or logs.
8. Your choices and privacy rights
Depending on where you live, privacy laws may give you rights to access, correct, export, delete, or restrict certain information, or to object to some processing. Workspace members can ask their organization administrator about project information. For requests to the service operator, use [add the operator’s privacy contact]. The operator must adapt this section to the laws that apply to its business and users.
9. Changes and contact
This draft may change as product features, subprocessors, or legal requirements change. The operator should publish an effective date and notify users when required. Legal entity: [complete]. Privacy contact: [complete]. Applicable jurisdictions: [complete].