Legal
Privacy policy
Last updated October 26, 2026
This policy explains what personal data RecordHTML collects, why, who processes it for us, how long we keep it and what your rights are under the EU General Data Protection Regulation (GDPR).
Who is responsible
The controller of your personal data is Primoz Zagoricnik S.P., a sole proprietorship registered in Slovenia, which operates RecordHTML. For any question or request about your data, email [email protected]. More details are on the contact page.
In short
- We collect what we need to run your account and your recordings, plus product analytics to understand how the site is used and to fix errors.
- Uploaded creatives are public by link: anyone who has the address of an uploaded file can open it. Don't upload personal data or secrets.
- API keys are stored only as a one-way hash; we cannot show or recover a key after it is created.
- We do not sell personal data and do not use it for advertising.
What we collect and why
Your account (through Clerk)
Sign-up and sign-in are handled by Clerk. Clerk processes your email address, your name and profile picture if you provide them or sign in with Google or another provider, your sign-in methods and session data, and the device and IP address of each sign-in. RecordHTML keeps a copy of your account ID, email address, name, profile picture address, role, when we first and last saw you, and whether the account is suspended.
Purpose and legal basis: to provide your account and the service you signed up for (contract, Art. 6(1)(b) GDPR), and to keep the service secure (legitimate interest, Art. 6(1)(f)).
Your recordings
For each recording we store the creative URL or uploaded creative, the settings you chose, its status and progress, a technical report from the recorder (timings, errors), the finished video or GIF, and any crop or trim you apply. If you started it with an API key, we note which key. Our recorder opens the URL from our own servers, so the site you record sees our server, not your device.
Purpose and legal basis: to record, store and deliver your videos (contract).
Uploaded creatives are public by link
When you upload a creative as a ZIP file, or an AI assistant sends HTML through the MCP server, its files are unpacked into a separate public storage location so that the recorder's browser can load them. Anyone who knows the address of an uploaded file can open it; the addresses are hard to guess, but they are not protected by a password or by your account. Uploaded creatives are kept until we delete them, also after you delete the recording, because re-runs may use them. Do not put personal data, passwords or other secrets in an upload. To have an upload removed, email us with the recording ID.
API keys
When you create an API key, we show it to you once and store only its SHA-256 hash, the first characters (so you can tell keys apart), the name you gave it, when it was created, when it was last used and whether it was revoked. Nobody at RecordHTML can read your key. Purpose: to authenticate requests from your code (contract).
Webhooks
If you set up a webhook, we store its URL and the signing secret, and a log of each delivery: the event, recording ID, attempts, response status and error. Purpose: to notify your system when a recording is ready or has failed (contract).
AI assistants and the MCP server (OAuth)
When you connect an AI assistant such as Claude or ChatGPT to the RecordHTML MCP server, you sign in through Clerk, which acts as the OAuth authorization server and gives the assistant an access token for your account. We verify that token on each request and the assistant acts as you, with your limits; it never gets your password. What the assistant sends us (URLs, HTML, settings) is handled like any other recording. You can disconnect an assistant in its own settings; deleting your account also ends its access.
Your conversation with the assistant is processed by the assistant's provider (for example Anthropic or OpenAI) under its own privacy policy, not ours. We receive only the tool calls it makes.
Analytics and error reports (through PostHog)
We use PostHog to understand how RecordHTML is used and to find errors. PostHog records page views, clicks and product events (for example that a recording was started or downloaded, with its format and size, not its content), the referring page, approximate location derived from your IP address, browser and device type, error reports from the page, and session recordings of how pages are used. Typed input is masked in session recordings, and the API key panel is excluded from capture. PostHog stores an identifier in a cookie and in your browser's local storage. When you are signed in, these events are linked to your account ID, email address and name, so that we can help you when you report a problem. Our servers also send PostHog operational logs about the service itself.
Purpose and legal basis: to improve the product and fix errors (legitimate interest, Art. 6(1)(f)). You can object at any time by emailing us, and you can block analytics with your browser's tracking protection or a content blocker; the service keeps working.
Emails from us
We send emails about your account and the service, and occasional product news. Emails are delivered by Resend; we store the address, the message and its delivery status. Every product-news email has an unsubscribe link, which takes effect at once. Purpose and legal basis: service messages (contract); product news (legitimate interest in informing users about a service they use, with a right to opt out at any time).
When you contact us
If you email us, we keep the message and our reply to handle your request and any follow-up (legitimate interest).
Server logs
Our servers log requests and errors, which can include your IP address, to keep the service secure, enforce rate limits and investigate problems (legitimate interest).
Who processes data for us
We use these service providers, under data processing agreements, only to run RecordHTML:
- Clerk (Clerk, Inc., United States): accounts, sign-in and OAuth for AI assistants. Clerk privacy policy.
- PostHog (PostHog, Inc.): product analytics, session recordings and error reports. PostHog privacy policy.
- Resend (Resend, Inc., United States): sending emails. Resend privacy policy.
- Hosting and storage providers: the servers that run the app and the recorder, and the storage that holds videos and uploaded creatives.
Some of these providers are in the United States or process data there. Such transfers rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission's standard contractual clauses.
We may disclose data when the law requires it, for example to a court or authority, or to protect the service and its users from abuse.
How long we keep data
- Account data: while your account exists. To delete your account, email us; we then delete your account data, recordings and videos within 30 days, except where the law requires us to keep something.
- Recordings and videos: until you delete them, or until the storage period on the pricing page ends.
- Uploaded creatives: until we delete them, on request or when they are no longer needed for re-runs.
- API keys: the hash and its details stay with your account until the account is deleted; a revoked key no longer works.
- Webhook and email delivery logs: while your account exists.
- Analytics: according to the retention settings of our PostHog project.
- Server logs and backups: only for the limited period needed for security and recovery.
Your rights
Under the GDPR you have the right to access your data, to have it corrected or erased, to restrict or object to its processing (including analytics), to receive it in a portable format, and to withdraw any consent you have given. Email [email protected] from the address on your account; we reply within one month. You can delete recordings yourself at any time in My recordings.
You also have the right to lodge a complaint with a supervisory authority. In Slovenia, that is the Information Commissioner of the Republic of Slovenia (ip-rs.si); you can also contact the authority in the EU country where you live or work.
Security
Traffic is encrypted with HTTPS. API keys are stored only as hashes, links to your videos are signed and expire, webhooks are signed so your system can verify them, and webhook addresses must be public HTTPS endpoints. No system is perfectly secure; if you notice a problem, please tell us at [email protected].
Children
RecordHTML is a tool for professionals and is not meant for children. You must be at least 16 years old to create an account.
Changes to this policy
When we change this policy, we update the date at the top. If a change materially affects how we use your data, we will also tell you by email before it takes effect.
See also the terms of service.