Privacy Policy
Last updated: 5 August 2026
Przeczytaj tę politykę po polsku
- Company
- runn3r Limited
- Address
- Flat A, 15/F Hillier Comm. Bldg., 65-67 Bonham Strand East, Sheung Wan, Hong Kong
- Company Number
- 79575250
- Email
- hello@runn3r.ai
- Customer Service
- Monday to Friday, 10:00 AM – 5:00 PM HKT
Introduction
runn3r Limited is committed to protecting our users' privacy and takes its responsibility regarding the security of your information very seriously. We aim to be clear and transparent about the information we collect and what we do with it.
This policy covers:
- what personal data we collect,
- how we collect it,
- what we use it for,
- who we share it with,
- how long we keep it and what rights you have.
This policy covers the Runn3r service — our marketing pages and the creator application. Websites published by our users have their own privacy policies, and for those the site creator is the data controller.
Data controller
The controller of personal data processed in connection with your use of Runn3r is runn3r Limited, Flat A, 15/F Hillier Comm. Bldg., 65-67 Bonham Strand East, Sheung Wan, Hong Kong, company number 79575250.
Contact for data protection matters and for our Data Protection Officer: hello@runn3r.ai.
Customer service: Monday to Friday, 10:00 AM – 5:00 PM HKT.
What personal data we collect
We collect the following categories of data:
- Account data — email address, name and the credentials needed to create and maintain your creator account.
- Third-party sign-in data — if you sign in with Google, Apple or Facebook, we receive a limited set of data from them, described in "Third-party sign-in (OAuth)".
- Session data — cookies and technical data required to keep you signed in.
- Billing data — your plan, payment history and issued documents. We do not store card details; those are handled by the payment provider.
- Content you create — descriptions, assets and files you upload so we can generate and run your website, including content passed to the AI models that generate the site.
- Technical data — browser type, operating system, approximate location derived from your IP address, and product usage events.
- Analytics and marketing data — only after you give consent in the cookie banner. See "Cookies" for details.
How we collect this information
We receive data in the following ways:
- you provide it yourself when creating an account, in settings, or through the contact form,
- we receive it from a third-party sign-in provider if you choose Google, Apple or Facebook,
- it is generated as you use the service (creating and publishing sites, purchases, support correspondence),
- it is stored in cookies and similar technologies — necessary ones always, analytics and marketing only with your consent,
- the payment provider passes it to us after a completed transaction (payment status, not card details).
How we use your personal data
We use your personal data to:
- provide the service and generate, publish and maintain your websites,
- run your account and authenticate your sign-in,
- handle your subscription, payments and billing documents,
- send transactional messages (password resets, security notifications, confirmations),
- provide technical support and respond to your requests,
- keep the service secure and prevent abuse,
- improve our products and services — analytics only with your consent,
- tell you about news and promotions, if you have separately opted in.
Third-party sign-in (OAuth)
We offer sign-in via Google, Facebook (Meta Platforms, Inc.) and Apple as an alternative to email/password registration. When you choose one of these providers, we receive a limited set of data from them:
- Google — email address, name, profile picture and Google account identifier.
- Facebook — email address, first and last name, profile picture, and a Facebook-scoped user identifier (email and public_profile permissions).
- Apple — email address (real or Apple’s private relay address) and name, provided only at first sign-in; Apple does not share profile pictures.
We use this data solely to create and identify your Runn3r account, display your name and avatar in the application, and send transactional emails. We do not post anything to your social media accounts and we do not request permissions beyond those listed above.
If you signed up with email and password and later sign in with one of the providers above using the same email address, we automatically link the two sign-in methods to the same Runn3r account to prevent duplicate accounts.
You can disconnect any third-party sign-in provider at any time in your account settings (/settings → Account). Disconnecting removes the link between your Runn3r account and that provider; it does not delete your Runn3r account or affect your other sign-in methods.
To fully revoke Runn3r’s access on the provider’s side, also remove us from your provider’s authorized applications list: Google https://myaccount.google.com/permissions , Facebook https://www.facebook.com/settings?tab=applications , Apple https://appleid.apple.com/
Cookies
Necessary cookies — always active, because the service cannot work without them. They do not require consent:
- auth_session — keeps you signed in as a creator.
- runn3r_consent — remembers your cookie banner choice together with the policy version and the date, so we do not ask again on every visit.
- locale — remembers your chosen interface language.
- lp_variant, lp_visitor, runn3r_landing — keep you on one version of the landing page so its content does not change between visits.
- runn3r_ref, affiliate_partner — remember that you reached us through a partner referral, so the partner programme can be settled correctly.
- runn3r_utm — records the first source of your visit (campaign parameters and referring page).
- google_oauth_state, google_oauth_code_verifier, google_oauth_intent, google_oauth_link and their Apple and Facebook equivalents — short-lived cookies securing the third-party sign-in flow.
- impersonator_session, impersonator_marker — set only when a Runn3r administrator is acting inside your account for technical support.
- _maintenance_bypass — allows access to the service during scheduled maintenance.
- Cloudflare technical cookies — set by our infrastructure provider (CDN, bot protection) and required for the service to run securely. Cloudflare policy: https://www.cloudflare.com/privacypolicy/
Analytics cookies — loaded only after you give consent. They help us understand how you use the service and improve it:
- Microsoft Clarity — heatmaps and session recordings. Sets the _clck and _clsk cookies. Recordings are masked so that sensitive information such as passwords and payment data is not captured. When you are logged in, we pass Clarity only a pseudonymous account identifier (no email or name). Microsoft policy: https://privacy.microsoft.com/privacystatement
- Google Analytics — visit statistics and content performance. Google policy: https://policies.google.com/privacy
- Google Tag Manager — manages the loading of the tags above; it does not itself collect analytics data. Google policy: https://policies.google.com/privacy
Marketing cookies — loaded only after you give consent. They measure the effectiveness of our advertising:
We use Google Consent Mode to manage consent: before you choose, analytics and advertising tags run in denied mode, and after your choice they receive exactly the scope you consented to.
Recipients and sub-processors
Your personal data will never be sold to any third party for marketing purposes. We work with trusted service providers (sub-processors) who are contractually bound to process your data only on our instructions and in accordance with GDPR:
- Cloudflare, Inc. (United States) — application hosting, edge compute, content delivery and storage.
- Neon, Inc. (United States) — managed PostgreSQL database hosting.
- Resend Corp. (United States) — transactional email delivery (password resets, security notifications).
- Google LLC, Meta Platforms, Inc., Apple Inc. — only when you choose to sign in with their respective OAuth services (see "Third-party sign-in (OAuth)" above), and for the analytics and marketing tools you have consented to.
- Microsoft Corporation — only for Microsoft Clarity analytics, and only after you give consent.
- Payment processors (Stripe, PayPal, Paddle, Przelewy24) — only when you make a purchase, and limited to the data required to complete the transaction.
- AI service providers — for the content passed to them in order to generate your website.
- Domain registrars — when you purchase a domain through Runn3r, the registrar processes the data required to register and maintain that domain. Current registrar partners: OVH sp. z o.o. (Poland) — .pl domains and selected European TLDs; Porkbun LLC (United States) — .com, .net, .io, .app and most other generic TLDs.
Registrars are themselves required to forward registrant details to the relevant registry (e.g. NASK for .pl, Verisign for .com) and, where applicable, publish them in the public RDDS / WHOIS directory in accordance with ICANN and registry policies.
We ensure that every sub-processor we engage provides an adequate level of data protection, and we maintain Data Processing Agreements with each.
Domain registration data
If you purchase a domain through Runn3r, additional data may be processed beyond what is described above:
- Registrant data. Runn3r is recorded as the registrant for operational reasons (see our Terms of Service). The registrant contact details sent to the registrar and registry are Runn3r’s own business contact details, not yours, unless you explicitly request a transfer of the domain to your own account.
- Identity verification. In limited cases — for example, the registrar’s anti-fraud review for country-code TLDs such as .pl — the registrar may ask Runn3r for additional documentation to verify the registrant. We will only share information about you with the registrar if you have explicitly authorised the transfer of the domain to you, in which case the registration is updated to use your own contact details.
- Public WHOIS / RDDS. Where the registry operates a public directory, the registered contact details (i.e. Runn3r’s, or yours after transfer) may be published. Runn3r itself does not publish your personal data in WHOIS / RDDS.
- Retention. Domain registration records are retained for as long as the domain is active in your account, plus the legal retention period for transactional data (six years), after which they are deleted in line with the rest of this Policy.
Data retention
We will keep your personal data as long as required to fulfil our obligations to you. After fulfilling our obligations, under applicable law we are required to keep transaction details for a further 6 years. After this period, your personal data will be deleted.
Account data and content are kept for as long as you hold an account, and after its deletion for the period required by law or needed to establish and defend legal claims.
We keep a record of your cookie consent (categories, policy version and the date of your choice) so that we can demonstrate it was given. That record contains neither your IP address nor any other information that directly identifies you.
Your data protection rights (GDPR)
Under GDPR, you have the right to:
- access your data,
- rectify (correct) your data,
- have your data erased,
- restrict processing,
- data portability,
- object to processing,
- not be subject to decisions based solely on automated processing, including profiling.
To exercise your rights, write to us at hello@runn3r.ai.
You also have the right to lodge a complaint with your national supervisory authority if you believe your data is processed unlawfully. In Poland this is the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw.
Withdrawing consent
You can change or withdraw your consent for analytics and marketing cookies at any time using the "Cookie settings" link in the site footer, or — once signed in — in the profile menu.
Withdrawing consent is as easy as giving it and does not affect the lawfulness of processing carried out before the withdrawal.
Necessary cookies operate regardless of your choice, because the service cannot run without them.
Changes to this policy
This policy may change from time to time. We will inform you of significant changes by email or a notice in the service.
If a change affects the scope of consent, we will ask you for consent again — your previous choice then stops applying.
For any complaints or queries regarding your personal data, please contact us at hello@runn3r.ai.
Last updated: 5 August 2026.