SEOBuilder
SEOBuilder

Privacy Policy

Last updated: August 24, 2026

1. Introduction

SEOBuilder ("we," "our," or "us") respects your privacy and is committed to protecting your personal data. This privacy policy explains how we collect, use, and safeguard your information when you use our SEO platform at seobuilder.tech.

Contact Information: For any privacy-related questions or requests, please contact us at [email protected].

2. Information We Collect

2.1 Account Information

  • Name and email address
  • Password, held by Clerk, our authentication provider. We never see it.
  • Billing details, entered with DodoPayments and never stored by us
  • Company name (optional)

2.2 Project and SEO Data

  • Website domains you add for tracking
  • Keywords you research and monitor
  • Site audit results and SEO scores
  • Competitor domains you track
  • Content created using our AI tools

2.3 Free Checks and Tools

Our free tools and checks work without an account. If you choose to leave an email address on one of them, we store that address together with which tool you used and the address or domain you were checking. We use it only for the purpose stated next to the form where you entered it, and you can ask us to delete it at any time via the contact details below.

2.4 Technical Data

  • IP address and approximate location
  • Browser type and version
  • Device information
  • Usage patterns and feature interactions

3. Google API Services - Data Usage Disclosure

SEOBuilder integrates with Google services to provide comprehensive SEO analytics. This section specifically describes our use of Google API Services.

3.1 Google Services We Connect To

  • Google Search Console: To retrieve your website's search performance data, including queries, impressions, clicks, and average position
  • Google OAuth: To securely authenticate your Google account without accessing your password

3.2 Data We Access from Google

When you connect your Google account, we request access to:

  • Search Console data: Search queries, page URLs, click counts, impression counts, click-through rates, and average position for your verified properties

That is the only scope we request: webmasters.readonly. We do not request Google Analytics access and cannot read your Analytics data. If we add it we will ask you to grant it and say so here first.

3.3 How We Use Google Data

We use data from Google APIs exclusively to:

  • Display your search performance metrics in our dashboard
  • Generate SEO reports and insights for your websites
  • Track ranking changes and identify optimization opportunities
  • Provide personalized SEO recommendations

We do NOT:

  • Sell your Google data to third parties
  • Use your Google data for advertising purposes
  • Share your Google data with other users
  • Access any Google data beyond what is necessary for our stated features

3.4 Google Data Storage & Retention

OAuth tokens (access and refresh tokens) are encrypted at rest with AES-256-GCM. The only Search Console data we store is one derived report per project, which is what draws the trends and comparisons in your reports. It is deleted when you disconnect, along with the tokens.

3.5 Revoking Google Access

You can disconnect your Google account at any time through:

  • Google Account: Visit Google Account Permissions and remove SEOBuilder from connected apps. This takes effect immediately at Google and our stored tokens stop working.
  • Ask us at [email protected]. We do not simply forget the token: we revoke the grant at Google, and delete the stored tokens and the cached Search Console data at the same time. All of it immediately, not on a schedule.
  • Delete your account in Dashboard → Settings. That destroys the stored tokens along with everything else, but it does not by itself revoke the grant at Google, so remove us at the link above too if you want it gone from both ends.

Two things stated exactly rather than comfortably. There is no one-click Disconnect in Settings yet: the capability exists and the control is being built. And revocation is something we attempt on every disconnection, but Google does not always confirm it. When it does not we still delete our copy and say so, and removing us at Google Account Permissions is what makes it certain.

3.6 Google API Services User Data Policy Compliance

SEOBuilder's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. How We Use Your Information

We use your information to:

  • Provide and maintain our SEO platform and features
  • Process your subscription through DodoPayments, our merchant of record
  • Send important service updates and notifications
  • Improve and personalize your experience
  • Generate SEO reports and actionable insights
  • Respond to your support requests
  • Comply with legal obligations

5. Data Sharing

We do not sell your personal data. We may share data with:

  • Service Providers: Essential third parties that help us operate:
    • DodoPayments, our merchant of record. They are the seller on your receipt and handle payment and tax.
    • Clerk, which stores your account and password and runs sign-in
    • Railway, which hosts the application and the database
    • Resend (transactional email)
    • DataForSEO, which receives the domains and keywords you ask us to check
    • Bright Data, which asks the AI answer engines your questions and so receives the domain and topic of every AI visibility scan you run
    • Anthropic, whose Claude model receives those same scan questions when Claude is one of the engines checked
    • Google, whose Gemini model receives page content and keywords when you use an AI feature. Gemini is the model configured today.
    • OpenAI, which would receive that same content if we switch model provider. It receives nothing at present, and we will date a change here before it does.
    • PostHog (product analytics) and Sentry (error monitoring)
  • Legal Requirements: When required by law, court order, or to protect our rights
  • Business Transfers: In connection with a merger, acquisition, or sale of assets (with notice to you)

6. Data Security

What we actually do, rather than what sounds reassuring:

  • TLS encryption for all data in transit
  • Your Google account tokens are encrypted at rest with AES-256-GCM, and are the only credential of yours we hold
  • Your API keys are stored only as a SHA-256 hash, so a copy of our database is not a set of working keys
  • Sign-in, sessions and password storage are handled by Clerk. We never see or store your password
  • Every query that reads your data is filtered by your account, and an id in a request can only narrow that set, never widen it
  • Errors and access are monitored continuously through Sentry

We are a new product and we will not imply more than that. We hold no compliance certification, we have had no independent security audit, and we offer no uptime guarantee. If that changes we will say so here and date it.

7. Data Retention & Deletion

We retain your data for as long as your account is active or as needed to provide services.

Account Deletion

You can delete your account at any time through Dashboard → Settings → Preferences → "Delete Account". It runs while you wait. It is not queued, and there is no window during which we still hold it:

  • Any live subscription is cancelled first, so nothing is charged after it
  • We attempt to revoke the Google grant before the tokens are destroyed. Forgetting a token does not tell Google anything, and that would leave SEOBuilder sitting in your Google permissions with nobody able to remove it
  • Your account record is deleted, and the database removes everything hanging off it in the same statement: projects, keywords, rank history, audits and their issues, backlinks, competitors, Search Console snapshots, AI visibility scans and their mentions, reports, drafts, API keys and usage counts
  • Your sign-in record at Clerk is deleted last, so a failure leaves an account you can still sign in to and retry rather than one you are locked out of
  • Billing records held by DodoPayments, our merchant of record, are kept as required by law. Those are theirs to retain, not ours to delete

One case where we deliberately do nothing: if we cannot cancel your subscription automatically, we delete nothing at all and tell you so. An account you can no longer sign in to that is still being billed is the worst outcome available here, so we refuse rather than risk it.

To delete some of your data without deleting your account, email [email protected] and we will do it within 30 days of the request. That one has a window and the button above does not, for the honest reason: a person does it by hand.

8. Your Rights

Depending on your location, you may have the right to:

  • Access: Request a copy of your personal data
  • Correction: Update or correct inaccurate data
  • Deletion: Request deletion of your data
  • Export: Download your data in a portable format (available in Settings)
  • Objection: Object to certain types of processing
  • Withdraw Consent: Revoke previously given consent

To exercise these rights, please contact us or email [email protected].

9. Cookies

We use the following types of cookies:

  • Essential Cookies: Required for authentication and core functionality. Set by Clerk, which runs sign-in.
  • Analytics Cookies: PostHog and Google Analytics, to see which features get used. These run in production only.

We do not offer an in-product cookie toggle today, so we will not pretend otherwise: analytics cookies are refused through your browser settings or an extension, and the product works normally without them.

10. International Transfers

Your data is processed in the United States, and in any other country a provider in section 5 operates from. Each of those transfers happens under the data protection terms that provider publishes, and those terms are what we rely on. This section used to say we ensure appropriate safeguards are in place, which names a specific mechanism under the GDPR. We are not going to claim a mechanism we cannot show you.

11. Children's Privacy

SEOBuilder is not intended for use by children under 18 years of age. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting a notice on our website and updating the "Last updated" date. Continued use of the service after changes constitutes acceptance of the updated policy.

13. Contact Us

If you have questions about this Privacy Policy, our data practices, or wish to exercise your rights, please contact us:

← Back to home