Privacy Policy

Data We Use

Waitline uses account email, authentication identity, advertiser organization data, campaign content, payment references, payout account status, install identifiers, coarse surface/version metadata, event identifiers, timestamps, visibility duration, abuse report submissions, IP-derived rate-limit keys, and user-agent strings.

We use this data to authenticate users, run campaign delivery, prevent fraud, calculate ledgers, support payouts, debug service health, and comply with legal or payment obligations.

Data We Avoid

Waitline does not use prompts, source code, terminal output, file paths, project names, repository names, or private editor content for ad targeting.

Supported local adapters should only request a decision for a visible wait-state surface and report coarse delivery events needed for advertiser spend accounting and viewer credit.

Cookies And Sessions

The web app uses signed session cookies and browser-bound OAuth state cookies for authentication and CSRF protection. Email magic links and OAuth providers are used only for sign-in and account continuity.

Processors

We may use infrastructure, email, analytics, payment, payout, security, and hosting providers to operate the service. These providers process data for Waitline operations, not for reading developer workspaces.

Retention

We retain account, campaign, ledger, audit, event, abuse report, and payout records as needed for spend integrity, fraud review, tax/payment obligations, dispute handling, security, and service operations.

You can contact support to request account review or deletion. Some records may be retained when needed for legal, anti-fraud, payment, or accounting requirements.