In short
- We collect what we need to run PromptHelm: your email address, your projects and prompts, and basic security data about your sign-ins.
- The values your app fills into prompts, your LLM provider keys, your users' data and your LLM traffic never reach us.
- If you buy Pro, Paddle, our reseller, takes the payment under its own privacy policy. We never see your card.
- We don't sell personal data, show ads, or train AI models on your content.
- You can delete your account, and everything in it, at any time from the dashboard.
1. Who we are
PromptHelm is run by Runivox Ltd, a company registered in England and Wales (company number 16980284), whose registered office is at 20 Wenlock Road, London, England, N1 7GU ("Runivox", "we", "us"). We are the controller of the personal data this policy describes, under the UK GDPR, the Data Protection Act 2018 and, for people in the European Economic Area, the EU GDPR. Where your prompts contain personal data, we process it on your behalf as your processor, under our Data Processing Addendum.
Questions or requests about your data: privacy@prompthelm.app.
2. The data we collect, and why
| What | Details | Why | Legal basis |
|---|---|---|---|
| Account | Your email address. If you sign in with GitHub, also the name and profile picture it shares. | To create your account, sign you in, and write to you about your account. | Contract |
| Sign-in links | Your email address and a one-time code. | To email you a link that signs you in. | Contract |
| Sessions | A session token, the IP address and browser you signed in from, and when; and a log of your sign-ins and sign-outs, with the IP address each came from. | To keep you signed in and protect your account. | Contract; legitimate interests (security) |
| Your content | Project names, prompt slugs, drafts, published versions with their model settings and how the model is called (the provider, addresses and parameters you set), and the notes you write on them. | To provide PromptHelm. | Contract |
| API keys | A SHA-256 hash of each key, its last four characters, its name, and when it was created, last used and revoked. | To check your app's requests and show you which keys are in use. | Contract |
| API requests | When your app fetches a prompt, its API key and the slug. We record when each key was last used, and which version of each prompt it was last served and when, at most once a minute. If your app had to use its own fallback text, the SDK says why with its next request: an error code such as missing_variables, never the text or any value. While you run an A/B test, the SDK also sends totals, which we add up by day: how many calls each version served, and the outcomes, token counts and durations your code reports. Never the text, a variable's value or who the call was for. Our hosting provider may log technical details, such as your server's IP address. | To serve your prompts, show you which version your apps are getting, whether they fell back and how an A/B test splits their calls, prevent abuse and fix faults. | Legitimate interests (running a secure, reliable service) |
| Emails we send | Your email address; the prompts, projects and API key names a fallback alert, an A/B test email or the weekly summary mentions; whether each project sends each kind, and when your last summary was considered. | To tell you when an app falls back because of a published version, and to sum up your week. You can turn either off in each project's Settings or from the email. | Legitimate interests (keeping your apps working) |
| Checks on model settings | When the model catalog stops a publish or an A/B test because the provider would reject a setting, or you tell us the catalog is wrong: the project's and the prompt's IDs, the model, where it's called and the settings' values, emailed to us. Never the prompt's text or its slug. | To correct the catalog quickly, so it never stops a setting that works. | Legitimate interests (keeping the catalog accurate) |
| Subscription | If you buy Pro: your Paddle customer and subscription IDs, your plan and billing period, the subscription's status, and when it renews or ends. Never your card details. | To give you Pro, show your plan, and cancel it if you delete your account. | Contract |
| Messages | What you send when you email us. | To answer you. | Legitimate interests |
| Analytics (Ahrefs) | The public pages you open (address and title), the links you click on them, the page that linked to them, your screen size, your browser's language and your IP address, which Ahrefs says it doesn't store with the rest. Collected by Ahrefs without cookies; never in the dashboard. | It counts visits to each public page and where they came from, so we learn which help. | Consent |
| Analytics (Google Analytics) | The public pages you open (address and title), the page that linked to them, how far you scroll, the links out, downloads and forms you use, your device, browser and approximate location, and a random ID kept in its cookies. Google works out the location from your IP address, which it says it doesn't store for visitors in the UK, the EU and Switzerland. If you type an email address or phone number into a form on those pages, it may also send it to Google, hashed. Never in the dashboard. | It shows how visitors find and use our public pages (the pages they view, how far they scroll, the links out, downloads and forms they use), so we learn which pages work. | Consent |
| Analytics (Google Ads) | The public pages and the sign-up page you open (address and title), the Google ad you clicked to get here, how far you scroll, the links out, downloads and forms you use, your device and browser, and a random ID kept in its cookies. On the sign-up page, the email address you type is sent to Google hashed, so Google can match the sign-up to an ad you saw or clicked. Your IP address reaches Google with every request. Never in the dashboard. | It tells us which of our Google ads bring visitors and sign-ups, so we spend on the ads that work. | Consent |
| Analytics (PostHog) | The pages you open on the site and in the dashboard (their addresses, with project IDs and prompt slugs replaced in your browser first; titles on public pages only), the page that linked to them, the buttons and links you click, errors your browser hits, your device, browser and screen size, and a random ID kept in its cookie; once you sign in, your account's ID, never your email address. A recording replays the page as you used it. In the dashboard your browser replaces all text and everything you type with asterisks before anything is sent, along with the labels, notes and names the page carries out of sight, so a recording shows the layout and where you clicked, not your prompts or their names. Your IP address reaches PostHog with each request, and we have set it to discard it. | It shows how our pages and the dashboard are used, replays visits so we can see where people get stuck, and reports errors your browser hits, so we can fix what doesn't work. | Consent |
What never reaches us. The SDK fills your prompt's variables in on your own server, so their values never reach PromptHelm. During an A/B test it also picks the version for each call there, and the unit it splits by, such as a user id, stays on your server too. Nor do your LLM provider keys, your users' data, or the requests your app sends to LLM providers.
Legal bases. "Contract" means the processing is needed to provide the service you signed up for (Article 6(1)(b) UK GDPR and EU GDPR). "Legitimate interests" means our interest in running a secure and reliable service, which we balance against your rights (Article 6(1)(f)); you can object to it. "Consent" means we ask first (Article 6(1)(a)), and you can withdraw it at any time.
Prompts are templates. Please don't put personal data in them, and never special category data such as health information. We don't make decisions about you by automated means.
3. How long we keep it
- Your account, content and API keys, which version each key was last served, and your email settings: until you delete them or your account. Deleting your account erases them from our database at once.
- Sign-in links: they work once and expire after 5 minutes.
- Sessions: until you sign out, or 7 days after you were last active.
- The log of your sign-ins: until you delete your account.
- Technical logs and backups kept by our hosting, database and email providers: for the limited period each provider keeps them, after which they are overwritten.
- Subscription records: until you delete your account. Paddle keeps its own record of your purchase for as long as tax law and its privacy policy require.
- Analytics in Ahrefs: until we delete it from our account.
- Analytics in Google Analytics: 14 months, then Google deletes it.
- Analytics in Google Ads: as long as Google's own retention policy allows (policies.google.com/technologies/retention).
- Analytics in PostHog: recordings for 30 days; the rest until we delete it from our account.
- Emails with us: for as long as we need to deal with your message.
4. Who we share it with
We don't sell personal data or use it to show you ads; if you accept analytics, Google Ads measures which of our own ads bring visits and sign-ups, as described below. These service providers process it for us, only on our instructions and under contracts that require them to protect it:
| Provider | What they do for us | Where |
|---|---|---|
| Amazon Web Services EMEA SARL | Runs PromptHelm. | Germany (Frankfurt) |
| Supabase, Inc. | Signs you in and stores PromptHelm's database. | Germany (Frankfurt) |
| Resend, Inc. | Sends sign-in emails, fallback alerts, A/B test emails and the weekly summary. | United States |
Paddle. If you buy Pro, you buy it from Paddle.com Market Ltd, our reseller and Merchant of Record. Paddle collects your payment details and billing address at checkout and uses them, as an independent controller, under its own privacy policy at paddle.com. We give it your email address to fill in the checkout, and it tells us the status of your subscription. The Plan & billing page loads Paddle's checkout from its servers, so Paddle receives your IP address and browser details when you open that page.
Ahrefs. If you accept analytics, Ahrefs Pte Ltd measures visits to our public pages for us, as the Cookie policy describes. It receives what section 2 lists under Analytics (Ahrefs) and processes it in Singapore and the United States. It never runs in the dashboard, so it never sees your account or your content.
Google Analytics. If you accept analytics, Google Ireland Limited measures visits to our public pages for us, as the Cookie policy describes. It receives what section 2 lists under Analytics (Google Analytics) and processes it in the EU and the United States. It never runs in the dashboard, so it never sees your account or your content.
Google Ads. If you accept analytics, Google Ireland Limited measures visits to our public pages and the sign-up page for us, as the Cookie policy describes. It receives what section 2 lists under Analytics (Google Ads) and processes it in the EU and the United States. It never runs in the dashboard, so it never sees your content.
PostHog. If you accept analytics, PostHog, Inc. measures how our public pages and the dashboard are used for us, as the Cookie policy describes. It receives what section 2 lists under Analytics (PostHog) and processes it in Germany (Frankfurt). In the dashboard it knows your account by its ID alone, and your browser masks the text of your prompts and everything you type before anything is sent, so it never receives them.
If you choose to sign in with GitHub (GitHub, Inc.), GitHub learns that you signed in to PromptHelm, under its own privacy policy. We may also share data with professional advisers, with authorities when the law requires it, and with a buyer if Runivox or PromptHelm is sold, in which case we'll tell you first.
5. International transfers
We are based in the United Kingdom. Some providers process data in other countries, including the United States. When personal data leaves the UK or the European Economic Area, we rely on adequacy regulations (such as the UK Extension to the EU-US Data Privacy Framework, for certified companies) or on standard contractual clauses (the UK International Data Transfer Addendum and the EU Standard Contractual Clauses). Ask us at privacy@prompthelm.app for a copy of the safeguards.
6. How we protect it
- Connections to PromptHelm are encrypted in transit (HTTPS).
- API keys are stored only as SHA-256 hashes; we show a full key once, when it's created.
- There are no passwords to leak: sign-in links work once and expire in 5 minutes.
- Access to production data is limited to the people who need it to run the service.
No system is perfectly secure. If a breach puts your data at risk, we'll tell you and the regulators as the law requires.
7. Your rights
Under the UK GDPR and the EU GDPR you can ask us to give you a copy of your data, correct it, erase it, restrict how we use it, or hand it to you in a portable format; you can object to processing based on legitimate interests; and you can withdraw consent at any time.
- Erase everything yourself: in the dashboard, open the account menu next to your email address, choose Plan & billing, then Delete account.
- Anything else: email privacy@prompthelm.app. We answer within one month and may ask you to confirm your identity first.
- Complaints: you can complain to the UK Information Commissioner's Office (ico.org.uk) or, in the EEA, to your local data protection authority. We'd appreciate the chance to put things right first.
If you are in Türkiye
You have the rights in Article 11 of the Personal Data Protection Law No. 6698 (KVKK), including to learn whether your data is processed, to ask for information about it, to have it corrected or deleted, and to object. Send requests to privacy@prompthelm.app; you can also complain to the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu).
If you are in the United States
We don't sell personal information or share it for cross-context behavioral advertising. Where a state privacy law gives you rights to access, correct or delete your personal information, email privacy@prompthelm.app and we'll honour them.
8. Cookies
We use only the cookies PromptHelm needs to work, and those of Google Analytics, Google Ads, and PostHog if you accept analytics. The Cookie policy lists each one.
9. Children
PromptHelm is a tool for professionals and is not meant for anyone under 18. We don't knowingly collect children's data; if you think we have, email privacy@prompthelm.app and we'll delete it.
10. Changes to this policy
When we change this policy we update the date at the top. If a change matters, we'll tell you by email or in the dashboard before it applies.
11. Contact
Runivox Ltd, 20 Wenlock Road, London, England, N1 7GU. Email: privacy@prompthelm.app.