Trust

Your revenue data stays yours.

Bayesin fits models on your own data. We don't sell it, we do not train models on it, we don't share it for advertising, and we work with aggregated performance data wherever we can.

Your data only

  • Each model is fit on one customer's data. No pooling, and never used to train models for anyone else.

Never sold

  • No sale of data, and no sharing with advertisers or data brokers.

Minimal by design

  • Spend, conversions and revenue by channel and date. A model needs nothing more.

Data we use

The data a model needs.

  1. What does Bayesin need?

    Spend, impressions, clicks, conversions and revenue by channel and date. No names, emails or other direct identifiers. Every field each source reads is listed in the data field map.

  2. Do you collect personal data?

    Not to fit a model. If you send identifiers, such as CRM contact IDs for attribution, we process them only on your behalf. You can aggregate or hash them before upload.

  3. How do you connect?

    Through connected sources or a weekly file. Read-only access wherever the platform supports it, and you can disconnect any source at any time.

Privacy and compliance

Your obligations, supported.

  1. GDPR

    We act as your processor and you remain the controller. A Data Processing Agreement covers Article 28 terms; we publish our subprocessors and honor access, export and deletion requests.

  2. CCPA and CPRA

    We act as a service provider and use your data only to deliver the service. We don't sell it or share it for cross-context behavioral advertising.

  3. Where it's stored

    Amazon Web Services, in the United States.

  4. Certifications

    SOC 2 is planned for Q1 2027 - Our security overview and questionnaire responses are available on request.

  5. Retention and deletion

    Export your data or request deletion at any time. When you leave, we hold your data for seven days in case the cancellation was a billing problem, then delete it. Deleted data leaves our backups within 15 days of your subscription ending.

Third parties

Who else handles it, and why.

A small set of vendors runs the service. We email customers 30 days before any change to this list.

Staff access is limited to support and operations, requires role-based permission, and is logged.

Amazon Web ServicesInfrastructure, data storage and compute for model fitting
SupabaseAccount sign-in and the application database
VercelApplication and website hosting
StripePayment processing and billing
SentryError and performance monitoring
PostHogProduct analytics
AnthropicPlain-language explanations of results, only if your organization turns them on (off by default). Receives aggregate figures only, never identifiers, subject-level rows, raw events or credentials.
ResendTransactional email

Security

How it's protected.

  1. Encryption

    TLS 1.2 or higher in transit. AES-256 at rest.

  2. Credentials for connected sources

    Kept in a managed secrets store, never shown in plaintext, never used outside the source you authorized.

  3. Sign-in

    SSO and two-factor sign-in are available.

  4. Incidents

    We notify affected customers without undue delay, and within 72 hours of confirming an incident that affects their data, with its scope and the steps we're taking.

  5. Testing

    Penetration testing, vulnerability scanning and dependency monitoring.

Hosting

You choose what it sees.

  1. Can we host it ourselves?

    Bayesin is a cloud service. To limit what leaves your environment, connect a scoped, read-only warehouse view or send weekly files of aggregated data.

  2. Can we limit access?

    Yes. You choose the sources, tables and fields. We recommend starting with channel-level aggregates.

Questions about security or privacy?

Email security@bayesin.com. We reply within 2 business days, and complete security questionnaires within 7. Researchers can report vulnerabilities to the same address.