Privacy policy
This policy covers the Velvet developer portal: this website, your developer account, API keys, the docs, the contact form and our AI-tool endpoints (the MCP server and llms.txt). Last updated: 19 November 2026.
1. Who is responsible
The controller is Velvet Technologies GmbH, Ahornweg 9, 22395 Hamburg, Germany (Amtsgericht Hamburg, HRB 192449). Full details are in the imprint.
- Data Protection Officer: [email protected]
- Users in India (Digital Personal Data Protection Act 2023): [email protected]
Write to either address to use any of your rights in section 11. We reply within one month.
2. Your Velvet account
A developer account is an ordinary Velvet account, the same one you can use for Velvet Stories and AI Partner. You become a developer by creating an app.
- What we hold: your name, email address, a username, your password (stored only as a salted hash) or, with Google sign-in, your Google account id, plus sign-in times and a device id for staying signed in.
- Why: to give you the account and the services you asked for (Art. 6(1)(b) GDPR), and to keep them secure (Art. 6(1)(f)).
- Where: Velvet accounts are run for us by our group company Velvet Rituals India Private Limited on Microsoft Azure in India, as our processor, under a data processing agreement and the EU Standard Contractual Clauses.
How the other Velvet products use your account is covered in their own privacy policies.
3. Developer data
When you create an app we store:
- the app's name, your one line on what you're building, and its allowed origins (domains or app ids)
- that you confirmed you're 18 or older, and which version of the developer terms you accepted, with the time
- your API keys. We show a key once and then keep only a cryptographic hash and its first and last characters.
- key checks: when the SDK starts, it checks its publishable key with us. We see the key, the website (origin) or app id it runs on, the SDK version and the time, and use them to apply limits and stop abuse. Velvet Live's server API works the same way with secret keys.
Legal basis: providing the services under the developer terms (Art. 6(1)(b)), and our interest in running them safely (Art. 6(1)(f)).
4. What never reaches us: toy commands
The SDK connects to a toy directly over Bluetooth, in the browser. Commands such as vibrate or stop go from the page to the toy and never pass through our servers. How someone uses a toy can reveal their sex life, which the GDPR protects as special-category data (Art. 9), so we built the SDK so that we don't receive it.
If your app processes your users' data, you're the controller for it (see the developer terms, section 8).
5. Contact form
When you use Contact us, we receive your name, email address, topic and message, and send them by email to our team. We use Mailgun (EU region) to deliver it. We use your details only to answer you and keep the conversation as long as we need it for that (Art. 6(1)(b) or (f)).
6. AI tools: the MCP server and llms.txt
Our MCP server (/api/mcp) lets AI assistants look up these docs. For every tool call we log the tool, what was searched or opened, the number of results and how long it took. We use this to see what's missing from the docs (Art. 6(1)(f)). We don't log your IP address, an account or any key, and the logs are deleted after 30 days. The plain-text docs (/llms.txt, /llms-full.txt, /docs/…md) are ordinary web pages.
7. Hosting, security and statistics
- Microsoft Azure Static Web Apps (EU, West Europe) hosts this site and the MCP server.
- Cloudflare sits in front of the site as a content delivery network. It protects it from attacks, limits how many requests one IP address can send, and gives us cookieless visitor statistics (Cloudflare Web Analytics: pages, referrers, countries, load times; no cookies and no tracking across sites). Cloudflare processes your IP address to do this.
- Microsoft Application Insights collects error and performance logs from the MCP server, with IP addresses masked. They're kept for 30 days.
Legal basis: our interest in a fast, secure and working site (Art. 6(1)(f)). We don't use advertising trackers or analytics cookies.
8. Google sign-in
"Continue with Google" is optional. Our pages load nothing from Google until you click it. After the click, your browser loads Google's sign-in service and Google learns your IP address. If you go ahead, Google tells us your name, email address and Google account id, and we sign you in or create your account (Art. 6(1)(b)). Google's privacy policy: policies.google.com/privacy.
9. Cookies and storage on your device
We store only what the site needs to work, or what you chose. That's why there's no cookie banner (§ 25(2) TDDDG).
| Name | Where | What it's for | How long |
|---|---|---|---|
token | cookie | keeps you signed in | 3 hours |
refreshToken | cookie | renews your sign-in | until you close the browser, or 1 year with "Remember me" |
userInfo, rememberMe | browser storage | your signed-in profile and the "Remember me" choice | until you sign out |
deviceId | browser storage | a random id that ties your sign-in to this browser | until you clear it |
theme | browser storage | light or dark mode, only if you pick one | until you clear it |
g_state | cookie (set by Google) | only after you use Google sign-in: Google's sign-in state | set by Google |
10. Who receives data, and transfers outside the EU
We share data only with the service providers named in this policy, who work for us under data processing agreements: Velvet Rituals India Private Limited, Microsoft, Cloudflare and Mailgun, plus Google when you use Google sign-in. Where data leaves the EU (India, the USA), it's protected by the EU Standard Contractual Clauses or, for US providers certified under it, the EU-US Data Privacy Framework. We don't sell personal data.
11. How long we keep data
- Account and developer data: as long as you have your account. When you delete it, we deactivate it at once and remove it permanently later. Write to us if you want developer data (apps, keys, origins) removed sooner.
- Key checks and server logs: only as long as we need them for security and limits.
- MCP and Application Insights logs: 30 days.
- Contact messages: as long as we need them to answer you.
- Cookies and storage: see the table in section 9.
12. Your rights
You have the right to access (Art. 15 GDPR), correct (Art. 16), delete (Art. 17) and restrict (Art. 18) your data, to receive it in a portable format (Art. 20), and to object to processing based on our legitimate interests (Art. 21). Write to [email protected].
You can also complain to a data protection authority. Ours is the Hamburgische Beauftragte für Datenschutz und Informationsfreiheit (HmbBfDI), Hamburg. Users in India have the rights of the Digital Personal Data Protection Act 2023 and can write to [email protected].
You must be 18 or older to use the portal. We don't knowingly collect data from anyone younger.
13. Changes
When the portal changes, this policy changes with it, and we update the date at the top. If a change affects you significantly, we'll tell you by email or when you next sign in.