Privacy

Developer inventory clients (CLI / IDE)

• · We collect: device fingerprint, requested surface, time waited, whether the sponsored line was shown for the required duration.
• · We never collect: your code, prompts, model responses, filesystem contents, or terminal scrollback.
• · No third-party analytics or advertising trackers run inside developer clients.
• · The CLI sends one first-party launch signal per UTC day using a random installation identifier, client type, and version. Set WAITLINE_DISABLE_ANALYTICS=1 to disable it. The signal never includes code, prompts, commands, filenames, or terminal content.

Website and download analytics

• · We count visits to the Earn page, download responses, and first-party client launch signals so we can measure whether installation is working.
• · A random first-party session cookie lasts for 24 hours. Only its SHA-256 hash is stored. We do not store raw IP addresses, full user agents, referrer URLs, or cross-site identifiers in the analytics table.
• · Analytics are visible only to an authenticated Waitline operator and are not sold or shared for third-party advertising.

Earners

• · Account identifiers: email, one-time codes, connected device labels.
• · Referral data: your referral code, permanent referrer attribution, aggregate referral counts, and referral-ledger earnings. We do not show a referred person's email or identity to their referrer.
• · Payout identifiers are only collected when Stripe Connect goes live.
• · You may request access, correction, export, or deletion by contacting us. Legal and accounting records may need to be retained.

Advertisers

• · Billing is handled by Stripe. We store customer/session/payment identifiers and receipt email.
• · Creative content is public once approved. Your billing email and internal notes are not.

Contact

Advertisers can submit private requests through campaign management. A dedicated private privacy-request channel must be configured before general availability.