Privacy Policy

TrustSERP exists to independently verify SEO claims using data you already own — your Google Search Console (GSC) data. We read it through a read-only OAuth scope, never modify it, and only display what you explicitly approve for public display through privacy mode settings on each claim.

• We request read-only access to GSC (webmasters.readonly). We cannot edit your Search Console.
• Refresh tokens are encrypted at rest with AES-256-GCM envelope encryption before being written to our database.
• You can disconnect at any time. You can delete your account and all data at any time.
• We do not sell your data. We do not run third-party ads.

TrustSERP is operated by Michael Patrick (“TrustSERP”, “we”, “us”). Contact: hello@trustserp.io.

From you, when you sign in with Google

• Your Google account name, email address, and profile photo URL (from the openid, email, and profile scopes).
• An OAuth refresh token, encrypted with AES-256-GCM before storage.
• The list of scopes you granted (webmasters.readonly).

From Google Search Console

• The list of Search Console properties you have access to, shown only to you so you can pick which one to verify.
• Aggregate metrics (clicks, impressions, average position) for properties you explicitly select, over date ranges you authorize when creating a verification or claim.
• We do not read keyword-level data, individual URL data, or per-query data unless you explicitly request a claim that requires it (and then only for the scope of that claim).

From you, when you use the site

• Information you enter into your profile: handle, name, bio, operator type, operator privacy mode.
• Claims you create: claim text, the metric and value being claimed, the validation window, and the privacy mode for the site referenced in the claim.
• Standard server logs from our hosting provider (IP address, user agent, request path) for the purpose of operating the service and detecting abuse. These logs are retained for up to 30 days.

• To verify claims.When you create a claim, we fetch the relevant GSC metrics, compare them to the value you're claiming, and issue a verification if the data supports it.
• To keep verifications fresh. When someone visits a public claim page, if its data is older than 7 days, we re-fetch your GSC metrics and refresh the snapshot.
• To render share artifacts. We generate OG images, downloadable PNGs, and SVG badges for the claims you choose to make public.
• To operate the service. Authentication, session management, rate limiting, and abuse detection.

Privacy works in two independent layers — your operator identity, and each site you verify.

Operator privacy modes

• Public — your name and handle are shown on every claim you issue.
• Handle only — only your @handle is shown. Your real name is private.
• Anonymous— you appear as “Anonymous Operator” (or Agency / Consultant / Creator, per your operator type). No identifying information is exposed.

Site privacy modes (per claim)

• Public — the domain appears on the claim page.
• Category only— only an industry label (e.g. “B2B SaaS”) appears. The domain is hidden.
• Anonymous — no information identifying the site is shown.

The combination of these two layers determines what a visitor sees on any given claim page. Default is the most restrictive option in both layers.

• Database. All data is stored in a managed Postgres database (Neon) in the United States.
• Refresh tokens. Google OAuth refresh tokens are encrypted with AES-256-GCM before being written. The encryption key is held in our server environment and is not stored in the database. A successful database breach without the encryption key cannot recover the tokens.
• Transport. All traffic is served over TLS 1.2+.
• Access controls. Only you can connect or disconnect your Google account. Only you can read your own GSC data. Only the metrics you publish in a public claim are visible to other users.

We use the following third-party processors purely to operate the service:

• Google (Search Console API).To retrieve your authorized metrics. Use is governed by Google's terms.
• Vercel. Hosting and edge networking.
• Neon. Managed Postgres.

We do not sell, rent, or share your data with advertisers, data brokers, or any party not strictly required to operate the service.

• Disconnect. Revoke our access at any time via Google Account permissions.
• Delete. Email hello@trustserp.io with the subject “Delete my account”. We will permanently delete your account, all GSC tokens, all verifications, and all claims within 7 days, except where retention is required by law.
• Export.Email the same address with subject “Export my data” and we will send you a JSON export within 14 days.
• GDPR / CCPA. If you reside in a jurisdiction that grants you rights of access, correction, deletion, or portability of your personal data, we will honor those rights. Send a request to the email above.

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

• We use Google user data only to provide and improve the user-facing features of TrustSERP that are visible in our user interface.
• We do not transfer Google user data to others except as necessary to operate the service.
• We do not use Google user data for advertising.
• We do not allow humans to read Google user data unless we have explicit consent from the user, we need to for security or to comply with law, or the data has been aggregated and is used for internal operations.

We use first-party cookies for authentication (your session) and CSRF protection. We do not use tracking cookies, ad cookies, or third-party analytics cookies.

TrustSERP is intended for use by SEO professionals and site operators. We do not knowingly collect data from anyone under 16.

When we change this policy materially, we will email registered users at least 14 days before the change takes effect. The current effective date is shown at the top of this page.

Email hello@trustserp.io.