Skip to content
SpendByTeam

GDPR, KVKK and compliance

Last updated November 7, 2026

SpendByTeam is built around counting usage, not reading work. This page says what we do for the EU GDPR and Türkiye's KVKK (Law No. 6698), and what we do not have yet, so your legal or security team can decide for themselves. It is not legal advice. For the full detail, see our Privacy Policy and security page. Türkçe bilgilendirme için KVKK Aydınlatma Metni.

Who is responsible for what

  • Your organization decides what usage data is collected about its developers, and is responsible for telling them and having a lawful basis (controller).
  • WebKoding, the company behind SpendByTeam, acts on your organization's instructions for that usage data (processor). For account, billing and website data, WebKoding is the controller.
  • Paddle is the Merchant of Record: it handles payments, card data, invoices and tax. We never see or store card numbers.

What you can do yourself

  • Access: anyone can download their account data and the usage recorded under their e-mail. Owners and admins can export one developer's record.
  • Correction: anyone can edit their name and e-mail.
  • Erasure: anyone can delete their account. Owners and admins can remove one developer's identity, which also stops collecting their usage, or delete a whole organization after a 7-day grace period.
  • Who sees what: choose whether names are visible to everyone or only to owners and admins. On Team and Agency, you can also hide names from everyone.
  • Retention: choose how long your numbers are kept, from 30 days to 5 years. The default is 13 months.

Encrypted backups keep deleted data for about 4 weeks until they expire. To tell your developers about reporting, start from our notice template.

How data is minimized

  • We do not receive prompts, model responses, source code, file contents, file paths, tool inputs or shell commands.
  • Only a fixed list of metric attributes is accepted. Anything else is dropped before it is stored.
  • In anonymous mode, developer e-mails are replaced with a keyed hash before they reach storage. This is pseudonymous data, not anonymous data: repository URLs and branch names are still stored.

How data is protected

  • Each organization's data is separated by row-level security in the database.
  • Ingest tokens are stored only as hashes and can be revoked in one click.
  • Two-factor authentication is available, and an organization can require it for owners and admins.
  • Backups are encrypted, with the decryption key kept off the server, and a copy is stored off-site.
  • Access logs and error reports have tokens and e-mail addresses removed.

Where data is

Our servers and database are in Germany (Hetzner). Traffic passes through Cloudflare, and an encrypted backup copy is on Cloudflare R2. We are based in Türkiye and our team may access the Service from there. The full list of providers is in our Privacy Policy.

What we do not have yet

  • Certifications: we hold no SOC 2 or ISO 27001 certification, and no independent audit has been done.
  • Data processing agreement: a standard DPA is being prepared. If you need one now, write to us.
  • Automatic erasure in backups: if a backup is ever restored, erasures made since then have to be applied again.

Questions or requests

Write to hello@spendbyteam.com. If you are a developer whose usage is reported, please contact your organization first. It controls that data.