Skip to content

Security

Security at Capve.

Your tracker sees your revenue, your sources and your partners. Here is how Capve protects them, in plain words you can check against the source.

Open code

The source is public, so you can read exactly how your data is handled.

Hashed secrets

Passwords and API tokens are stored as hashes, never in plain text.

No open redirects

Links only go where you told them to.

Audit log

Changes, token actions and support access are recorded.

Accounts and sessions

  • Passwords are hashed with PBKDF2-SHA-256 and a random salt per password.
  • Sessions are signed, HttpOnly, SameSite=Lax cookies, sent only over HTTPS in production.
  • New accounts verify their email. Team invites and admin rights only apply to verified emails.
  • Password reset and "sign out everywhere" revoke every existing session.
  • Sign-in, registration and password reset are rate limited per IP address and per email.

Access control

  • Owner, admin and viewer roles are checked on every request, not only when you sign in.
  • The account you're working in is a signed context bound to your user, and stale requests are rejected after a switch.
  • API tokens are shown once and stored as hashes. A token can't create tokens, and token management needs a browser session.
  • Support access to a personal account is limited to verified platform admins, lasts at most one hour, shows a banner, and is written to the audit log.
  • Changes made in the dashboard and with API tokens are recorded in the account's activity log.

Tracking safety

  • Links only redirect to destinations, offers and landers you configured. Capve never acts as an open redirect.
  • Each account has a postback key. Without it, payouts are capped to the offer payout, and you can reject keyless postbacks outright.
  • Postback and webhook URLs must be http or https.
  • Custom tracking domains serve only tracking paths. Everything else on them returns 404.
  • Third-party API keys for cost sync are encrypted at rest with AES-GCM.

Data handling

  • Capve runs on Cloudflare Workers and D1, served over HTTPS.
  • We process tracking data only to provide the service. We don't sell it or use it for advertising.
  • The outgoing postback delivery log is deleted after 30 days.
  • Payment cards are handled by Stripe. Capve never sees card numbers.

Processors

Who else handles data.

The service providers that process data for the hosted service. The Privacy Policy lists what each receives.

ProviderPurpose
Cloudflare, Inc.Hosting, database, edge network and email delivery
Stripe, Inc.Subscriptions and payments (no click logs)
Bento (Bentonow)Transactional email to account holders, when enabled (no click logs)
DataFastWebsite analytics on capve.app (no click logs)

Reporting a vulnerability

Email support@capgo.app with the subject "Security", the steps to reproduce, and the impact you see. Please give us reasonable time to fix the issue before you disclose it, and don't access other customers' data or degrade the service while testing.

Processing terms for customer data are in section 6 of the Terms of Service. Personal data handling is described in the Privacy Policy.

Bring your casino affiliate tracking together.

14-day free trial with every feature. No card, no server, no sales call.