Data and security

Your website, you control it.

Clarify which data is read, what it is used for, and how to stop.

Google

Login and read-only authorization

AISEO Site

Read the selected property and save analysis

AI service

Process search summaries needed for analysis

Your email

Receive proactively subscribed daily reports

Processing path diagram. Only after proactive analysis or enabling daily reports does the corresponding AI analysis process begin.

Google identity and read-only scope

Log in via Google OAuth and read Search Console; Google passwords are not collected. Each read verifies the user's permission for the property.

User record isolation

Analysis records are isolated by Google user identifier. Login tokens are encrypted and stored on the server, and are not written into public web pages or images.

AI data processing

Proactive analysis and subscribed daily reports transmit the search summary of the specified property and up to 30 page, query, and country details to a third-party AI service; tokens or account emails are not sent.

Revocation and deletion

Disconnecting first deletes this site's tokens, analysis, and subscription records, then attempts to revoke Google authorization; confirm the two results separately. The service inquiry is an independent record, and deletion requests can be submitted through the contact page.

Notes when selecting data

Query terms and URLs may also contain personal or business-sensitive information. Even if tokens and emails are not transmitted, it does not mean all search details are non-sensitive. Only connect properties you have the right to process, and check organizational requirements before proactive analysis.

Security measures are not certification

Server-side token encryption, user identity isolation, and permission review are current technical measures, not independent audits, compliance certifications, or absolute security guarantees. Security assessment also needs to cover permissions, backups, logs, and third-party processors.

Revocation and data requests

Use the disconnect option in settings to handle tokens and history; service inquiries and contact requests are separate records, and deletion must go through the contact process. Do not submit Google passwords or keys through the contact form.

Workspace data and sharing scope

Saved search snapshots, checks, content/language revisions, answer samples, tasks and reports belong to their workspace. Members access assigned sites only. Private pages stay out of sitemap and do not load 51LA; live Google reads use the acting user’s authorization.

Tool input and external reads

Anonymous syntax tools send input to this server without publishing a result page. HTTPS checks and audits request public destinations without user cookies or Google tokens. Workspace results are retained for review. Do not input secrets or client data you lack permission to process.

Optional data connections

GA4 requires additional Analytics read permission. Index versions come from Google URL Inspection; lab performance comes from PageSpeed/Lighthouse. Failed connections remain unavailable rather than using demo values. Data and URLs are sent to the corresponding service.

Account deletion and collaboration records

Account deletion removes personal records and owned workspaces. Membership elsewhere is removed and pending jobs stop; collaboration records remain there with system actor fields de-identified; personal details in manually written text require workspace-owner handling. Support requests, legally retained billing and historical backups follow separate processes; no instant purge from all backups is promised.

Stopping receipt does not equal deleting data.

Stop daily emails

Stop in email settings, or use the email unsubscribe link.

Disconnect Google

Delete this site's tokens, analytics, and subscription records, and attempt to revoke Google authorization. Revocation results are indicated separately.

Delete separate application records

Submit a data deletion request through the contact page.

Submit a data request

Where data goes

StageData involvedProtection and boundary
Google authorizationIdentity and access credentialsThis site does not collect Google passwords
Read GSCSearch data for user-selected propertiesServer-side verification of property access rights
Proactive AI analysisSummary and limited search detailsMay contain sensitive queries or URLs
Save historyUser identifier, window, and analysis outputIsolated by user, deleted upon disconnection process

Continue with the relevant task