Data privacy
History, saved reports, and related data stay inside the user account boundary.
EN
Security
How seodot protects access and reports
This page explains how sign-in, report history, saved reports, public site areas, and security contact paths are organized in seodot.
Google OAuth 2.0
History and reports stay inside the account
Public and personal areas are separated
Service status and security contact
Main controls
What service protection relies on
Sign-in, personal data, public pages, and service communication are kept separate so access is easier to control and questions are easier to handle.
Access control
Personal areas use Google OAuth 2.0 for sign-in. That keeps authentication separate from the service and avoids password storage in seodot.
Separated service areas
The homepage, documentation, and other public pages stay separate from personal actions tied to history and saved work.
Clear communication
The status page, legal pages, and the security contact provide a direct path when users need answers quickly.
How it works
What to know before using the service
The blocks below cover sign-in, report storage, public-area boundaries, and what to do when something needs attention.
Sign-in
How account sign-in works
Sign-in for personal areas runs through Google OAuth 2.0. Users confirm access with Google, while seodot receives only the data needed for authentication.
- Sign-in is required for history, saved reports, and comparisons.
- Google passwords are not stored in seodot.
- Access to personal data stays tied to the user account.
If a user signs out, personal areas stay closed until the next sign-in.
History and reports
How history and saved reports are kept
Analysis history and saved reports stay inside the account. That lets users return to earlier results without mixing data between people.
- Guest-facing pages do not need access to history.
- Saved material opens from the personal area.
- History is kept separate from public pages on the site.
Retention and deletion are covered in the privacy policy.
Service boundaries
How public and personal areas are separated
Public pages, account sign-in, personal history, and background jobs serve different roles. That separation reduces the chance of unnecessary access.
- Public pages stay available without sign-in.
- Personal actions live in separate service areas.
- Report workflows are kept apart from marketing pages.
This keeps the product easier to follow without adding unnecessary complexity.
Status and contact
How users get status and support information
Trust depends on more than access rules. The status page and the security contact give users a direct path to the information they need.
- The status page shows the overall state of important service areas.
- Security questions have a dedicated contact address.
- Legal pages add clear rules around service use and data handling.
The simpler the path from question to answer, the stronger the trust around the service.
Available
The main service areas are available
This page helps users understand the current service state and where to look if anything changes.
Homepage and static pages
SEO dashboard
Google sign-in
Background jobs
Open service status
Need more detail about security?
If you need to confirm how sign-in, data storage, personal history, or service notifications work, write to [email protected].
Before you start
We can answer questions about sign-in, access, data storage, and service status.
When a question appears
We can explain where to write and what to include so the answer comes faster.