Privacy Policy
01Who is responsible#
The data controller is VibeDojo — operated with Cardinal (“we”, “us”), Italy. For any privacy question or request, contact us at hello@kryptonite.gg. We have not appointed a Data Protection Officer because we are not required to; the contact above handles all data-protection matters.
02What data we process#
| Category | Data | Source |
|---|---|---|
| Account | Name, email address, password (stored only as a salted hash), email-verification status, role, profile image and provider ID if you sign in with GitHub or Google, account creation date. | You / your login provider |
| Sessions & security | Session identifier, expiry, IP address and browser user agent of each session; sign-in attempt counters keyed by IP address to stop brute-force attacks. | Your browser |
| Quota usage | Daily counters of searches and downloads, keyed by your user ID or — if you are not signed in — by a salted one-way hash of your IP address. We never store the raw IP for this purpose. | Your requests / your agent's requests |
| API keys | Key name, visible prefix, a hash of the key, creation, last-use and revocation timestamps. | You |
| Uploads | The audio file and its technical analysis, title, description, tags, attribution, licence, your user ID, and an upload consent record (the statements you accepted, the agreement version, a hashed IP address, user agent and timestamp). | You |
| Reports | The sound reported, reason, details and — only if you provide it — a contact email; your user ID if signed in. | You |
| Studio conversations | The messages you type in the Studio and the AI responses, processed to generate suggestions. We do not use them to train models. | You |
| Technical logs | Standard server logs: IP address, user agent, requested URL, MCP tool/API endpoint called, status code, timestamps. | Your browser or agent |
| Correspondence | Emails you send us (e.g. privacy requests, DMCA notices) and our replies. | You |
We do not intentionally collect special categories of data. Please don't include them in uploads, reports or Studio prompts.
03Purposes and legal bases#
| Purpose | Legal basis (GDPR art. 6) |
|---|---|
| Providing the Service: accounts, sign-in, API keys, quotas, downloads, uploads, the Studio | Performance of a contract — art. 6(1)(b) |
| Security, fraud and abuse prevention: rate limiting, hashed-IP quotas, malware scanning of uploads, logs | Legitimate interests in keeping the Service safe and available — art. 6(1)(f) |
| Keeping evidence of upload consents and handling copyright notices, counter-notices and reports | Legal obligations (e.g. EU Digital Services Act) — art. 6(1)(c) — and legitimate interest in defending legal claims — art. 6(1)(f) |
| Optional usage analytics | Your consent — art. 6(1)(a), which you can withdraw at any time via “Cookie settings” |
| Answering your messages and requests | Legitimate interests / pre-contractual steps — art. 6(1)(b) and (f) |
Where we rely on legitimate interests, we have balanced them against your rights; you can object at any time (see section 10). We do not carry out automated decision-making that produces legal or similarly significant effects on you. Automatic moderation (for example hiding a sound after several malware reports) is always subject to human review on request.
04AI agents, MCP and the API#
When an AI agent uses the MCP server or the REST API, we receive only the request it sends: the tool or endpoint called and its parameters (for example a search query or a sound ID), plus your API key or the agent's network address. We never receive the rest of your conversation with the agent. Avoid putting personal data in search queries.
A local MCP server you run on your own machine does not send us anything except the catalog requests it makes on your behalf.
05How long we keep data#
- Account data: as long as your account exists; deleted within 30 days of account deletion (backups roll over within a further 30 days).
- Sessions: until they expire or you sign out (sessions last up to 7 days and are refreshed while you use the site).
- Quota counters and sign-in rate-limit entries: kept per day and deleted after at most 90 days.
- Uploads: until you or we remove them. Upload consent records are kept for as long as the sound is online and for up to 10 years after removal, the Italian limitation period for contractual claims, to prove what was accepted.
- Reports, copyright notices and counter-notices: up to 3 years after the case is closed.
- Studio conversations: not stored by us beyond the session; model providers may retain them for a short period (typically up to 30 days) for abuse monitoring under their own terms.
- Technical logs: short-term, normally no more than 30 days.
06Who we share data with#
We don't sell or rent personal data and we don't share it for advertising. We use the following service providers, who act as our processors under data-processing agreements:
| Provider | Role | Location |
|---|---|---|
| Vercel Inc. | Hosting, content delivery, serverless functions, logs | USA / global edge (EU regions used where available) |
| Vercel Blob (Vercel Inc.) | Storage and delivery of audio files | USA / global CDN |
| Neon (Databricks, Inc.) | Managed Postgres database (accounts, catalog, usage, consents) | Region chosen by us; provider in USA |
| Vercel AI Gateway and the AI model providers it routes to (e.g. Anthropic) | Generating Studio suggestions from your prompts | USA |
| Sending.dev (on Amazon SES) | Delivery of account emails only: address confirmation and password reset. No marketing, no open or click tracking | EU / USA |
| GitHub, Google | Optional sign-in — only if you choose them (independent controllers for their own processing) | USA |
| VirusTotal (Google) | Malware check of uploaded files using the file's hash only, when enabled | USA / EU |
We may also disclose data where required by law or by a competent authority, to enforce our Terms, or to protect the rights, property or safety of users, rights holders or the public. In a copyright dispute, a counter-notice — including the contact details it contains — may be forwarded to the person who filed the original notice, as described in our DMCA Policy.
07International transfers#
Some providers are located in, or access data from, the United States. Transfers rely on the EU–US Data Privacy Framework where the provider is certified, and otherwise on the European Commission's Standard Contractual Clauses with supplementary measures. You can request a copy of the relevant safeguards by writing to hello@kryptonite.gg.
09Security#
We use encryption in transit (HTTPS), hashed passwords and API keys, salted hashing of IP addresses for quotas, access controls on our systems, and a sanitising re-encode of every uploaded file. No system is perfectly secure; if a personal-data breach is likely to put you at risk, we will notify you and the supervisory authority as required by law.
10Your rights#
Under articles 15–22 GDPR you have the right to:
- access your personal data and get a copy of it;
- have inaccurate data corrected;
- have your data erased (“right to be forgotten”), including by deleting your account;
- restrict processing in certain cases;
- receive your data in a portable, machine-readable format;
- object to processing based on legitimate interests;
- withdraw consent at any time (for analytics, via the “Cookie settings” link in the footer), without affecting prior processing.
Send requests to hello@kryptonite.gg. We reply within one month (extendable by two months for complex requests) and may ask you to verify your identity. You also have the right to lodge a complaint with a supervisory authority — in Italy the Garante per la protezione dei dati personali — or with the authority of your country of residence or work.
11Children#
The Service is not directed at children under 14. If you are below the age of digital consent in your country, you may create an account only with your parent's or guardian's consent. If you believe a child has given us personal data without such consent, contact us and we will delete it.
12Changes to this policy#
We will post any changes here and update the “Last updated” date. If changes are significant — for example a new purpose or a new category of processor — we will tell you in advance on the site or by email.