WaitSpin Privacy

TEMNIKOVA LDA, NIPC/VAT PT516343653, trading through the WaitSpin product, is the data controller. Its registered address is Campo Grande, 28, 7C, Lisboa, Portugal, 1700-093. Privacy requests can be submitted through the WaitSpin support page. Dmitri Sergeev, CTO, is the internal privacy-policy owner; this does not designate him as a statutory data protection officer.

• Email address, verification attempts, OTP delivery metadata, account status, plan/trust level, and API key metadata such as prefix, scopes, hashed secret, status, and last-used timestamps.
• Advertiser campaign data, including ad line, brand name, destination URL, block count, price, campaign state, Checkout session IDs, Stripe payment identifiers, stablecoin MPP PaymentIntent and receipt identifiers, and webhook event IDs.
• User install data, including install ID, target, status, serve sessions, impression events, creative views, valid clicks, visible time, timestamps, HMAC-derived network/client risk signals, and audit events. Raw IP addresses and user-agent strings are not stored with click events; their HMAC risk fields are marked for purge after 30 days.
• Operational logs, support messages, incident notes, monitor evidence, abuse reports, and security/audit records needed to run and protect the service.

Data comes from you; from the WaitSpin clients and website when you use them; and from service providers involved in the requested transaction or operation, such as Stripe payment and Connect status, Resend email-delivery status, and infrastructure security signals. WaitSpin does not obtain personal data from unrelated data brokers.

Verified user earning surfaces include the VS Code Activity Bar/status-bar extension, VS Code-compatible Cursor Editor Mode and Devin Desktop editor surfaces, Claude Code statusline command, Antigravity CLI statusline command, GitHub Copilot CLI statusline command, MiMo Code shell hook, OpenCode TUI plugin slot, Grok Code CLI footer, and Qoder CLI UserPromptSubmit/Stop hooks. They poll the WaitSpin API for a sponsored message, show the message in the relevant wait-state surface, open the advertiser destination only after user action, and report an impression after the required visible interval. The documented surfaces do not need source code, keystrokes, editor contents, terminal output, or repository files to serve ads. Qoder's official hook payload is delivered locally by Qoder and can include prompt or assistant-message fields; the WaitSpin Qoder runtime discards those fields before cache or API work.

The VS Code extension connects a user install inside VS Code, stores the extension API key in VS Code SecretStorage, stores the install ID in user-scoped extension state, and polls only the WaitSpin API. Serve polling sends the install ID; impression reporting sends the serve ID, serve receipt, install ID, and visible duration. When click measurement is enabled for a capability-aware clickable surface, the client reports one receipt-bound view and opens an opaque WaitSpin redirect URL on user click. WaitSpin also receives standard network metadata used for rate limits, abuse prevention, and audit logging.

• VS Code: Uses VS Code SecretStorage for the extension API key and user-scoped extension state for the install ID. The Marketplace extension provides an Activity Bar user view, status-bar mini state, wallet balance, pending balance, recent ledger entries, current sponsor card, no-inventory state, connect/polling/refresh/open commands, and a five-second visible impression hold.
• Cursor: Uses the same VS Code-compatible WaitSpin extension in Cursor, installed or updated with cursor --install-extension waitspin.waitspin-vscode --force, waitspin extension install --target cursor, or Cursor's Extensions panel. Detected Cursor installs are included in waitspin install --all. It stores keys through the VS Code-compatible SecretStorage API and uses the same Activity Bar/status-bar privacy boundary as the VS Code surface.
• Devin Desktop: Uses the Open VSX-published WaitSpin VS Code-compatible extension in Devin Desktop, installed from the Extensions panel/Open VSX, with devin-desktop --install-extension waitspin.waitspin-vscode --force, or with waitspin extension install --target devin. Windows lifecycle detection includes %LOCALAPPDATA%\devin\bin\devin.exe. Detected Devin installs are included in waitspin install --all. It stores keys through the VS Code-compatible SecretStorage API and uses the same Activity Bar/status-bar privacy boundary as the VS Code surface.
• Claude Code: Inspects user/scoped Claude settings, manages statusLine.command with --compose-existing support, and stores WaitSpin state/cache under ~/.waitspin.
• MiMo Code: Installs a managed runtime under ~/.local/bin, adds a bash hook in ~/.bashrc, and stores WaitSpin state/cache under ~/.waitspin.
• OpenCode: Installs a plugin under ~/.config/opencode/plugins, manages the tui.json plugin entry, and stores WaitSpin state/cache under ~/.waitspin.
• Grok Code CLI: Uses a managed text-asset footer patch with hash-backed backup/restore plus managed runtime/cache/state; it does not patch native binaries.
• Antigravity CLI: Manages Antigravity CLI statusLine.command in ~/.gemini/antigravity-cli/settings.json and stores WaitSpin state/cache under ~/.waitspin without patching native binaries.
• GitHub Copilot CLI: Manages GitHub Copilot CLI statusLine.command in ~/.copilot/settings.json or COPILOT_HOME/settings.json and stores WaitSpin state/cache under ~/.waitspin without patching native binaries.
• Qoder CLI: Installs through Qoder's official UserPromptSubmit/Stop hooks, returns sponsored copy with statusMessage/systemMessage, discards prompt and assistant-message hook fields locally before cache/API work, merges ~/.qoder/settings.json without patching Qoder binaries, and stores WaitSpin runtime/state/cache under ~/.waitspin.

The VS Code-compatible extension is distributed through the Visual Studio Marketplace for VS Code and Cursor, and through Open VSX for Devin Desktop. Public source is published at github.com/citedy/waitspin. Public source and provenance are documented on the WaitSpin Trust page, including the machine-readable manifest at /provenance/waitspin-vscode.json.

WaitSpin is designed to measure wait-state ad visibility, not your work. The public clients do not send:

• workspace files
• source code
• open editor text
• prompts
• model responses
• integrated terminal output
• shell history
• repository URLs
• screenshots
• clipboard contents
• raw keystrokes

WaitSpin has no separate analytics telemetry stream in the public clients. Serve, impression, capability-gated view/click, wallet, and accounting events are operational telemetry needed to run the marketplace. Click measurement is not inferred from editor contents and does not run on text-only surfaces.

On the public website, Google Analytics 4 and the X Pixel provide page and conversion measurement. Both are gated by a GDPR cookie preference notice for EU/EEA visitors and run without that notice outside the EU/EEA. EU/EEA visitors can accept all cookies, keep necessary cookies only, or choose analytics and advertising measurement separately. Website events are limited to page views, install-link clicks, command-copy success, list signup success, advertiser-path clicks, checkout-return status, and public surface selection. They do not include email addresses, company names, API keys, wallet addresses, command contents, clipboard contents, source code, editor data, terminal output, or repository files.

• user install registration: {install_id,target}
• serve polling: {install_id,capabilities?}
• impression event: {serve_id,serve_receipt,install_id,visible_ms}
• capability-gated view event: {serve_id,serve_receipt,install_id}
• capability-gated click redirect: opaque token; only its digest and 30-day HMAC risk signals are stored
• standard network metadata used for rate limits, fraud controls, abuse response, and audit logs

We use WaitSpin data to verify accounts, issue and secure API keys, create campaigns, route Checkout, activate paid blocks, select and route Stripe/Tempo stablecoin MPP pay-ins, activate paid blocks, select and serve ads, record billable impressions, enforce quotas, prevent fraud, investigate incidents, provide support, and satisfy legal, accounting, tax, and security obligations.

• Contract necessity under GDPR Article 6(1)(b): account access, campaign and marketplace operation, purchases, publisher earnings, balances, payouts, support, and delivery of requested services.
• Legal obligation under Article 6(1)(c): Portuguese tax, accounting, payment, regulatory, and legally required recordkeeping.
• Legitimate interests under Article 6(1)(f): service security and reliability, fraud and abuse prevention, reconciliation, defence of legal claims, limited accountability evidence, and a minimum direct- marketing suppression entry. These interests are applied with data minimisation and the rights described below.
• Consent under Article 6(1)(a): optional website analytics, advertising measurement, and marketing messages where consent is required. Consent can be withdrawn at any time without affecting processing that was lawful before withdrawal.

WaitSpin uses PostgreSQL/Supabase-compatible database infrastructure, a dedicated DigitalOcean VPS, Cloudflare DNS/security services, Stripe for payments, Resend for email, Google Analytics 4 and the X Pixel for consent-gated website page-view and conversion measurement, GitHub Actions for public smoke checks, and logging/monitoring tools needed for reliability and abuse response. These providers receive only the data needed for their function. Professional advisers, auditors, payment partners, or public authorities receive data only when necessary for a service, legal obligation, claim, or lawful request. WaitSpin does not sell personal data. Stripe handles card data and stablecoin payment processing directly; WaitSpin stores Stripe identifiers, MPP receipt references, and payment state, not full card numbers, raw wallet addresses, private keys, or crypto custody balances.

Some providers may process data outside the EEA. Where a transfer is not covered by an EU adequacy decision, WaitSpin requires an applicable GDPR Article 46 safeguard, such as the European Commission's standard contractual clauses, plus supplementary measures where required. A copy or description of the applicable safeguard can be requested through the support page.

Direct account identifiers, credentials, devices, installations, verification records, temporary mutation records, and local analytics identities are deleted, revoked, or replaced with non-deliverable tombstones immediately after confirmed account deletion. Routine operational logs are retained for no more than 30 days and must not contain the deletion token, email confirmation fragment, or reusable credentials. A scoped incident copy may be retained only until the incident or a documented legal hold closes.

When you delete an account, WaitSpin revokes credentials and devices, removes email verification and temporary mutation records, suppresses marketing email, tombstones associated analytics identities, and queues deletion with the analytics processor. Raw processor identifiers are removed after processor deletion succeeds. The account email and local installation identifiers are replaced with non-deliverable tombstones.

Pseudonymous purchases and Stripe evidence; balances, Stripe Connect payout-account evidence, payouts, and payout transitions; financially relevant delivery records; refunds; and disputes are retained for 10 years from the applicable Portuguese tax or accounting period. Risk, quarantine, abuse, and fraud evidence is retained only until the related matter closes, capped at 10 years unless a documented legal hold requires longer. An open dispute or legal hold extends only the records needed for that matter until it closes; it does not justify retaining unrelated direct identity.

Marketing subscriber data and send logs are deleted immediately. A minimal suppression entry is retained only to prevent accidental re-enrollment or further direct marketing for as long as WaitSpin operates its email-marketing service; it is reviewed annually and is never used to contact or profile the person. For analytics processor deletion, the processor identifier is retained only until deletion completes; a blocked request requires remediation within 30 days. Redacted processor-deletion result evidence is retained for 12 months. Revoked credential tombstones, pseudonymous analytics consent/deletion tombstones, prior audit event/time/resource envelopes with direct-identifier and secret fields removed, the remaining pseudonymous forensic metadata, and the aggregate account-deletion audit event are retained for 3 years. These retained records cannot restore the account, create a refund, recreate credentials, change a balance, cancel a payout, or rewrite historical ledger totals.

Subject to the conditions and exceptions in applicable law, you may request access, correction, deletion, restriction, and portability of your personal data; object to processing based on legitimate interests; and withdraw consent at any time. You may object to direct marketing at any time. Requests can be made through the support page, and WaitSpin may request proportionate information to verify identity. WaitSpin will communicate the action taken without undue delay and, in any event, within one month after receiving the request. Where a request is complex or numerous requests are being handled, that period may be extended by up to two further months; WaitSpin will explain the extension within the first month.

You also have the right to lodge a complaint with the supervisory authority where you live or work or where an alleged infringement occurred. In Portugal, complaints can be submitted to the Comissão Nacional de Proteção de Dados (CNPD).

An email address and verification data are required to create and access an account. Campaign, payment, tax, payout, and connected- account data are required only when the corresponding advertiser or publisher function is used. Without required data, WaitSpin cannot provide that function. Marketing and consent-gated website analytics are optional.

WaitSpin uses automated security, quota, invalid-traffic, and fraud controls that can reject an event, pause delivery, quarantine a publisher, or restrict a credential. WaitSpin does not use personal data for solely automated decisions that produce legal or similarly significant effects without an available human review path. A user can request review through the support page.

You can stop using the extension, remove local extension settings, rotate API keys, avoid storing keys in workspace settings, and contact support for privacy or account questions. WaitSpin protects keys with hashed storage, uses trusted-edge and host-isolation checks in production, limits request rates, and avoids printing secrets in launch evidence or incident notes.

A signed-in user can start permanent account deletion from the WaitSpin account deletion page. The email confirmation opens a final warning; only the explicit final button performs deletion. Completed deletion cannot be undone.

Wallet, ledger, Stripe Connect onboarding, payout dry-run, and payout execution process payout, tax, compliance, account, balance, ledger, trust level and warmup status, and Stripe Connect status data when used. Trust level starts at 1/10 and can rise by one level after each clean 24-hour period of billable activity, up to 10/10, while daily exposure limits scale with that level. Earnings mature for 72 hours before becoming withdrawable; trust warmup controls paid inventory exposure, not payout maturity. Live transfers execute only when payout policy eligibility checks pass. See User levels and limits for the public cap tables. Account-credit redemption and self-serve refund workflows are not shipped; if they are added later, updated public docs will describe the additional data they require. Publisher payouts remain standard Stripe-managed fiat payouts; WaitSpin does not offer direct EU crypto publisher payouts.