privacy policy

you can use the free editor with no account at all — your work stays in your own browser. if you create an account we store your email address and the robots.txt configs you choose to save. we don't sell your data, and we don't run ad trackers.

robot.guard is built by ogbuilds, a uk-based studio (ogbuilds ltd). ogbuilds ltd is the data controller for any personal data described here, and this policy is governed by uk data-protection law (uk gdpr and the data protection act 2018).

• account info. if you sign in, we store your email address and a verification timestamp. sign-in is passwordless — we never receive or store a password.
• your configs. the robots.txt rules you save to your account (the bots you allow or block, custom rules, a sitemap url, and a name you give the config). these are settings you author — not personal data about other people.
• billing info. if you subscribe to pro, we store a stripe customer id, a subscription id, your subscription status, and the current period-end date. card details are handled entirely by stripe — we never see or store them.
• newsletter (optional).if you enter your email in the “stay in the loop” box, we add it to our mailing list. you can unsubscribe at any time.

we don't use third-party analytics or advertising trackers, and we don't build behavioural profiles.

without an account, the configs you build are saved to your browser's local storage on your own machine — they never reach our servers. generating and downloading a robots.txt happens locally too. clearing your browser storage removes them.

we use your data only to run the service: to sign you in, to save and sync the configs you create, to bill and manage your pro subscription, and — if you opted in — to send you the newsletter. we never sell your data or share it for advertising.

• performance of a contract — to provide your account, saved configs, and pro subscription.
• legitimate interest — to keep the service secure and working.
• consent — for the optional newsletter; you can withdraw it any time by unsubscribing.

we use a small set of trusted providers to run robot.guard. they process data on our behalf:

• vercel — hosting and serving the app.
• neon — the postgres database where accounts and saved configs live.
• stripe — subscription billing and payment processing.
• resend — sending sign-in (magic-link) emails and the newsletter.

when you sign in, we set a session cookie so you stay logged in. it's strictly necessary for the account to work — there are no advertising or tracking cookies. the free editor also uses your browser's local storage to keep your unsaved configs on your own device.

we keep your account data while your account is active. if you cancel and close your account, or ask us to delete it, we remove your saved configs and personal data (we may retain limited billing records where the law requires). deleting your account cascades to your saved configs.

under uk gdpr you can ask us to access, correct, delete, or export your data, and you can object to or restrict certain processing or withdraw consent. to make a request, reach us via the studio link below. you also have the right to complain to the uk ico.

some of our providers (for example stripe, and our hosting and database infrastructure) process data outside the uk/eea, including in the united states. where that happens, transfers are covered by appropriate safeguards such as standard contractual clauses.

robot.guard is a tool for site owners and isn't intended for children under 13. we don't knowingly collect data from anyone under 13.

data is encrypted in transit (https). sign-in is passwordless via single-use, expiring magic links, and payment card data never touches our servers — it's handled by stripe. no system is perfectly secure, but we take reasonable measures to protect your data.

if this policy changes, we'll update the date above and, for material changes, note it on this page.

questions, or want to exercise your rights? reach out via ogbuilds, the studio behind robot.guard.