Privacy Policy

We collect what the service needs to run, and a few facts about how you found it:

• Your account. Email address, a hash of your password, display name and interface language; if you turn on two-factor sign-in, its secret and recovery codes; and the email addresses of teammates you invite.
• Google sign-in, if you use it. We ask only for the openid, profile and email scopes, and receive your Google account ID, email address and name.
• Search Console, when you connect a property. We ask for read-only access (webmasters.readonly) and record the list of properties Google says you can reach, with whether each is verified to you. For the properties you choose, and only those, we fetch clicks, impressions, CTR and position by query, page, country and device once a day, with an access token we keep encrypted. Sitemaps come from your own site, not from Google.
• Your work. Groupings, notes, saved views, keyword watchlists and settings are stored with your account.
• Messages you send us. The contact form keeps your name, email address, topic and message, with your IP address, browser and the reCAPTCHA score.
• Logs. Server and security logs record your IP address (passed on by our CDN), the pages requested and when.
• Where your sign-up came from. A new account keeps the country our CDN places your connection in (a two-letter code, not an address), your answer to the cookie banner, when you gave it and which version of the banner you answered, and, only if you allowed analytics, the site that sent you here or the ref or utm_source tag of the link you followed (see the Cookie Policy).
• Card payments. You pay on Stripe's page; your card details and billing address go to Stripe and never reach us. We give Stripe your email address and name, and signals that help it spot fraud: your IP address and browser, your account's age and number of sites, whether your email address and a Search Console property are verified, and the address of your first connected property. We keep your subscription's status, when you opened the payment page, and each payment's amount, date, period and number of sites.
• Crypto payments. You pay on PayerURL's page. We give PayerURL your email address, the amount and our order reference, and keep the amount, the period it paid for and whether it arrived.

Where the EU or UK GDPR applies, each use has a legal basis:

• Providing the service: your account, sign-in, syncing and showing your data, and service emails such as address checks, password resets and invitations, card payment problems and an ended subscription, and a reminder 7 days and again 1 day before a crypto period ends. Basis: contract. We send no marketing email.
• Taking payment through the providers in section 4 (contract), and keeping the payment records accounting and tax rules require (legal obligation).
• Connecting Search Console: your consent, given on Google's own screen.
• Security: logs, spam checks on forms and preventing abuse and payment fraud. Basis: legitimate interest in keeping the service safe.
• Learning where our customers come from: the sign-up country, on legitimate interest; the referring site, only with your consent in the cookie banner. We look at these in total and next to each account in our admin view.
• Your cookie choice, kept with a new account so we can show what you agreed to (legal obligation).

Clode's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice:

• We access Search Console read-only, and use the data only to provide and improve the features you see in the app.
• It is stored on our servers in the EU (Germany), and your access token is encrypted.
• We do not sell it or use it for advertising, and we transfer it to no one except as needed to run the service, for security, or to comply with the law.
• No person reads it unless you ask us to (for example for support), for security, or where the law requires.
• It is kept as section 6 says.

To end our access, delete the project or your account, which deletes it and the token we hold, or remove Clode on your Google account permissions page.

We do not sell your data. Service providers handle it for us, on our instructions: our hosting provider in Germany, Cloudflare (our network provider, in the US), Google, the company that delivers our emails, Stripe for card payments and PayerURL for crypto payments. The sub-processor list says what the main ones receive.

Your account and Search Console data are stored in the EU (Germany). Personal data that reaches a provider outside the EU/EEA is protected by the European Commission's Standard Contractual Clauses. PayerURL does not say where it processes data, so we cannot tell you where a crypto payment's details go, and a crypto payment is recorded on a public blockchain, where anyone can see its amount and the wallets involved.

We may also disclose data where the law requires it, or to protect our users and the service.

Necessary cookies are always on. Analytics run only if you allow them in the cookie banner; change your answer at any time with Cookie settings at the bottom of our public pages. The Cookie Policy lists every cookie.

• Your account and your work: for as long as the account exists.
• Search Console history. When you connect a property we load the roughly 16 months Google still holds, then add each new day. The free plan keeps the last 14 days and the paid plan a rolling 24 months; a nightly sweep deletes older days.
• When a paid plan ends, history older than 14 days is deleted: after a 3-month grace period for a card subscription, and on the day a crypto period ends. The Terms have the details.
• Payment records (the amount, the date, what it paid for and the account's email address) for as long as accounting and tax rules require, including after the account is deleted. Stripe and PayerURL keep their own records under their own policies.
• Messages you send us: as our record of the conversation. We delete one on request.
• Logs: for a limited time, for security and troubleshooting.

Deleting a project deletes its data. Deleting your account deletes its projects, their data and the Google tokens we hold, and cancels any card subscription; payment records stay. Providers such as our email service delete their copies on their own schedules, and Google keeps your Search Console data under its own policies.

Passwords are hashed with scrypt. Google access tokens and two-factor secrets are encrypted with AES-256-GCM. All traffic uses HTTPS, and access to production systems is restricted. No system is perfectly secure, and if something goes wrong we will act quickly.

Depending on where you live, you can ask to access, correct, export or delete your data, and object to or restrict some uses. In the app you can export any report to CSV, and delete your account on the Profile page in your account menu.

You can withdraw consent at any time, without undoing what was done before: disconnect a property or remove Clode in your Google account, and change your cookie choice with Cookie settings.

For anything else, email [email protected]. In the EU or UK you can also complain to your data protection authority.

Clode is not meant for anyone under 16, and we do not knowingly collect their data. If we change this policy we update the date above, and tell you more directly about important changes.

Questions about your data: [email protected].