Privacy Policy
Last updated 10 November 2026
The operator of hotcfg.run ("we", "us") is responsible for the personal data described here. Contact: [email protected]. This policy applies from 5 November 2026.
What we collect
| Data | Where it comes from | Why |
|---|---|---|
| GitHub user id, name, avatar and email | GitHub, when you sign in | Your account, and to show who changed what |
| Google account id, name, picture and email | Google, when you sign in with Google | Your account, and to show who changed what |
| Your email address | You, when you ask for a sign-in link | Sending the link, and your account |
| Session IP address and browser (user agent) | Your browser | Security: you can see and end your sessions |
| Invited people's email addresses | Administrators who invite them | Sending the invite |
| Audit log entries, including IP addresses (Pro) | Actions in your organization | Showing administrators who did what |
| Billing details | Stripe | Payments; Stripe holds card details, we never see them |
| Your content (bins, schemas, versions) | You | Running the Service |
| Request logs and IP addresses | Requests to the API | Security, abuse prevention and rate limiting |
| How you found us (details) | The link you arrived on, when you sign up | Knowing which of our posts and links bring people |
We use this data to provide the Service under our contract with you, and for its security and for knowing where sign-ups come from under our legitimate interest. We don't sell it or use it for advertising.
How you found us
Links we share can carry campaign tags, like hotcfg.run/?utm_source=reddit&utm_campaign=launch. When you arrive on such a link, the page keeps the tags (utm_source, utm_medium, utm_campaign) and the name of the site that sent you (for example www.reddit.com, never the page's full address) in memory while it's open. If you sign up, they're sent with your sign-in request and saved once on your new account. If you don't sign up, or already have an account, nothing is kept. They're deleted with your account, never shared, and only used to count sign-ups per source.
Cookies and local storage
We set one lasting cookie, hotcfg_session, which keeps you signed in. Signing in with GitHub or Google also sets short-lived cookies (at most 10 minutes) that protect the sign-in and carry how you found us to the account it creates. Your theme and preferred code language are kept in your browser's local storage. All of these are strictly necessary or set at your request. How you found us (see above) is never stored in your browser: it's sent with your sign-in request, and kept only if that creates your account. We don't use analytics or advertising cookies, so there's no consent banner.
How long we keep it
- Sessions until they expire or you sign out; expired ones are deleted hourly.
- Revoked and expired API keys for 90 days.
- Audit log entries for 90 days.
- Your account and content until you delete them.
- Deleted data is overwritten in our database straight away and removed from backups within 7 days.
Who processes it
Our providers are listed on the Subprocessors page. Data is stored in Frankfurt, Germany, and passes through Cloudflare's global network. Where data leaves the EEA or UK, transfers rely on the providers' standard contractual clauses.
Your rights
You can see your data in the dashboard and export your content from Settings → Export or over the API (how). You can delete your account under Account → Delete account. Depending on where you live, you may also have the right to access, correct, restrict or object to processing, and to complain to your data protection authority. Write to [email protected] and we'll answer within 30 days.
Children
The Service isn't meant for children under 16.
Changes
We'll post changes here and, if they're significant, tell you by email or in the dashboard.