HONEST & VERIFIABLE DATA ARCHITECTURE

Privacy Policy

Last updated: September 2026

Our Non-Negotiable Privacy Commitment

1. Raw CSVs are processed in memory and deleted immediately — never stored. When you upload Meta Ads or Google Ads exports, our compute service parses and fits statistical forecasting models in an ephemeral sandbox. The moment your report is generated, all temporary files are purged.

2. Saved runs contain forecast outputs only, opt-in and linked to your account. Saving a run stores model receipts (`report.json` — spend totals, predicted conversions, calibrated intervals, campaign names, and error metrics). Your underlying daily CSV rows are never saved.

3. You can delete any or all runs anytime. You maintain complete sovereign ownership. Individual runs can be deleted with one click, or all account history can be permanently wiped from your Settings page.

Zero Raw CSV Persistence

Uploaded advertising exports exist exclusively in volatile RAM during computation. No raw files are ever written to disk or database.

Output Reports Only

Only calculated forecasts, conformal confidence bounds, and backtest accuracy scores are preserved for authenticated accounts.

Sovereign Deletion

Delete individual forecasts or use the one-click Danger Zone purge in your Settings to erase all stored data immediately.

1. Self-Run Local CLI

When you run the standalone PaceCast Python CLI on your machine, 100% of execution happens locally on your computer. PaceCast makes zero external network calls, collects zero telemetry, and performs zero phone-home pings. Your advertising data never leaves your workstation.

2. Web Studio In-Memory Processing

When you use our online Studio to generate a forecast:

  • Your CSV exports are transmitted over encrypted TLS 1.3 to our stateless forecasting compute engine.
  • Files are ingested into a volatile POSIX temporary directory strictly for the duration of the cross-validation calculation (~6 to 30 seconds).
  • The temporary directory is purged and shredded immediately upon completion or execution failure.
  • The compute engine is completely stateless and never retains user tokens, database credentials, or file copies.

3. Authenticated Accounts & Saved Runs

When you create an account to save your forecasts:

  • We store your authentication credentials (email and password hash, or Google OAuth identity) securely using Supabase Auth.
  • When you save a forecast, we persist the forecast output structure (report.json), including campaign names, planned budget, predicted conversions, 90% conformal intervals, and rolling backtest receipts.
  • All saved runs are protected by PostgreSQL Row Level Security (RLS) policies enforcing that only your authenticated account UID can query, view, or delete your forecasts.
  • Raw transaction CSV rows are never stored.

4. Data Deletion Rights

You have the unconditional right to purge your stored data at any time:

  • Per-Run Deletion: Any saved forecast can be deleted directly from the History table or the Run Detail view.
  • Account-Wide Purge: In your Settings dashboard, the Danger Zone provides a "Delete all my runs" button that immediately and irreversibly removes all stored forecasts from the database.
  • Account Termination: You can request full account closure and removal of your authentication profile at any time.

5. Done-For-You Report Service

When you order a Done-for-you report audit, your files are processed in an isolated, encrypted working environment solely to produce your forecast package. All customer export files are permanently shredded within 24 hours of delivery.

6. Website Tracking & Cookies

We do not use advertising tracking pixels or third-party marketing beacons. Essential cookies are used solely to preserve your authenticated session state and sidebar preferences.