Visiteable
Legal

Privacy Policy

Last updated October 21, 2026 · Visiteable is built and run by Sumukha Shekar, Bengaluru, India.

This Privacy Policy explains what information Visiteable collects, why, and how it's used. Visiteable is a solo-founder product — your data is never sold, and it's only ever used to make the Service work for you.

1. Information we collect

CategoryWhat, and why
Account infoEmail address, and a hashed password if you sign up that way (we never store your plaintext password).
Google dataIf you connect Google Search Console and/or Google Analytics, we store an OAuth token that lets us read your query, page, and traffic data on your behalf — so Visiteable can ground its suggestions in your real search performance instead of guessing.
Publishing credentialsIf you connect a WordPress, WordPress.com, or Ghost site, we store the credential you provide (a WordPress Application Password, a WordPress.com OAuth token, or a Ghost Admin API key) so Visiteable can publish articles to that site on your behalf.
Content you createKeywords, briefs, generated articles, and the SEO/technical data Visiteable gathers about your site while working with you.
Usage dataBasic activity needed to operate the Service, like when you last used a feature — used only to run and improve Visiteable, never to build an ad profile.

2. Google user data, specifically

Visiteable'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: your Search Console and Analytics data is read only to generate the SEO insights and content you asked for inside Visiteable, is never used to train AI models, is never shared with third parties except the AI/data providers listed below that directly process it on our behalf, and you can revoke access at any time from Visiteable's Settings or directly from your Google Account permissions.

3. Who we share data with

We don't sell your data. We share the minimum necessary with the services that make Visiteable work:

4. Data retention

We keep your account data and connected credentials for as long as your account is active. If you disconnect an integration, we delete the associated credential. If you delete your account, we delete your account data; some records may persist briefly in backups before they age out.

5. Security

Credentials and tokens are stored encrypted at rest. Access to production systems is limited to the founder. No system is perfectly secure, but we treat your connected-account credentials with the same care we'd want for our own.

6. Your choices

You can disconnect any connected Google, WordPress, WordPress.com, or Ghost account at any time from Settings. You can request a copy of your data or full account deletion by emailing us — see Contact below.

Visiteable is in early access and currently collects no payment information — there's nothing to store there yet. This policy will be updated before that changes.

7. Cookies

Visiteable uses a single session cookie to keep you signed in. We don't use third-party advertising or tracking cookies.

8. Children's privacy

Visiteable isn't directed at, and shouldn't be used by, anyone under 18.

9. Changes to this policy

We'll update the "Last updated" date above whenever this policy changes, and post the new version here.

10. Contact

Questions, or want your data deleted? Email shekarsumukha8@gmail.com.