Privacy

Your account email and a hashed password. The registrant contact you enter at checkout: name, optional company, street address, city, state or province, postal code, country and phone number. The searches you run, the domains you buy, and the prompts, files and commits that make up your site.

Our registrar. The registrant contact is sent to the registrar so the domain can be registered in your name. This is required by ICANN and there is no way to register a domain without it.

Stripe. Payments are processed by Stripe. Card details are entered directly into Stripe’s own form and never reach see.io’s servers. Stripe keeps the card you pay with on file so that domain renewals, and monthly hosting if you enable it, can be charged to it; your card details stay with Stripe, and see.io keeps only its own account and subscription identifiers.

Anthropic. When you use the AI builder, your prompts, any files you attach and the relevant contents of your site repository are sent to Anthropic’s Claude API to generate the changes. Do not paste secrets, credentials or other people’s personal data into the build chat.

Meta. Our public pages carry Meta’s advertising pixel, because our ads run on Facebook and Instagram and it is how we can tell which of them work. It tells Meta that a browser opened one of those pages and, if that visit becomes an account, a built site or a purchase, that it did. We do not send Meta your email, your name or the domain you bought, and Meta’s advanced matching is switched off. The pixel does not run once you are inside your workspace: not on your dashboard, your billing page or the build chat.

Google. Our public pages carry Google’s advertising tag, because we also run ads on Google and it is how we can tell which of them work. It tells Google that a browser opened one of those pages, and Google may use that to show you our ads again elsewhere. When you create an account, the tag also reports that a signup happened, together with a hashed form of the email address you signed up with: the tag hashes it on your own device, so the address itself never leaves your browser and we never send Google the plain address, your name or the domain you bought. Like Meta’s pixel, it runs on the same list of public pages and nowhere inside your workspace: not on your dashboard, your billing page or the build chat.

We do not sell your data. The Meta and Google tags above are the only advertising use of it, and both are limited to the pages listed there.

Your site itself is public once deployed. Your registrant details are published in WHOIS unless privacy protection is available for that TLD, in which case it is enabled free and they are not.

Account, order and domain records are kept for as long as you have a domain with us and afterwards for as long as tax and registry rules require. Searches are kept only long enough to serve and improve results. Deleting a site deletes its repository and the instance it ran on.

You can see and correct your registrant contact from checkout and from your account settings. Correcting it does not rewrite the WHOIS of domains already registered, which has to go through the registrar. You can delete your account yourself: in the iOS app, Settings → Delete account removes your sign-in and personal details right away (records we must keep by law, such as orders and domain registrations, are kept without your name on them). To ask for a copy of your data, or to delete an account from the web, write to info@see.io.

see.io sets what it needs to keep you signed in and to complete a payment. Our public pages also carry Meta’s advertising pixel and Google’s advertising tag, which set their own cookies to measure our ads; those are the only advertising cookies here, and neither is set inside your workspace. Blocking them costs you nothing: every part of see.io works without them.

Write to info@see.io. See also our Terms.