What happens when you paste a URL.

We process enough information to deliver the audit, prevent abuse, and keep the service reliable. We do not ask for a profile, billing details, or access to Search Console for the current free product.

A submitted domain tells our servers what to fetch. Checks are limited to publicly reachable pages and public infrastructure records; we do not sign in to the target website.

Audit results are published at predictable /audit/[host/path] routes. When protocol, port, trailing slash, encoded path, or an allowed query matters, the full submitted URL is also included in the report address as an encoded ?url= parameter. Anyone with the link can open the report. Treat it as public and do not submit a URL if you do not want it or its publicly observable technical signals summarized this way.

A shareable URL is not the same as broad search distribution. Newly generated and random reports default to noindex,follow, and our sitemap includes only a small curated set of example domains. Search engines and third parties ultimately control their own crawling and caches.

The “Recent audits” convenience list is stored in your browser using local storage. It keeps a readable label and the exact public report link, which can include the submitted path and allowed query parameters, so you can return without creating an account. This list stays on that browser and can be removed with the Clear action or by clearing site data in your browser settings.

Theme preference may also be stored locally so dark or light mode persists between visits. Interactive tools, including the SEO Site Ladder, may store progress locally so you can continue later.

Your analytics choice is stored under the local-storage key theseosoul:analytics-consent:v1. It contains only granted or denied. Clearing site data removes this choice and we will ask again on a later visit.

Like most hosted web services, our infrastructure may record IP address, user agent, timestamps, requested paths, submitted domains, response codes, and diagnostic errors. We use these records to apply rate limits, investigate failures, prevent abuse, and maintain security.

Do not place passwords, API keys, personal messages, or other secrets in a URL submitted for audit. URLs can be included in request logs and the resulting report.

The current free product does not embed third-party advertising and does not sell personal information. Essential product features do not require analytics consent.

We use Google Analytics 4 (measurement ID G-6GC0B6V6TB) only after you select Allow analytics. Before that choice, the Google Analytics script is not requested and no analytics event is sent by our code. If allowed, your browser connects to Google and sends visit and usage events with page, referrer, browser, device, and related technical data. Google Analytics may set first-party identifiers such as _ga cookies.

The choice itself is remembered in local storage, not in an analytics cookie. You can change it at any time. Selecting Decline disables future Google Analytics events from this site and attempts to remove Google Analytics cookies accessible to us; it cannot recall information already sent. You can also clear this site's data in your browser.

Hosting, networking, DNS resolution, certificate inspection, and public RDAP services help us deliver an audit. Those providers may process request metadata under their own privacy terms and security practices. We disclose only what is reasonably needed to make the requested check operate.

Google acts as our analytics provider only when you allow analytics. Google processes those events under its own terms and privacy practices. Analytics retention is also governed by the settings of our Google Analytics property and Google's provider rules.

When error monitoring is configured, Sentry helps us diagnose failures and protect service reliability independently of optional audience analytics. An error event may include a stack trace, browser or server metadata, the affected page or tool, and the URL submitted for that failed check. We configure Sentry not to collect default personal identifiers. Retention follows our project settings and Sentry's provider rules. See the Sentry Privacy Policy.

Fetching a target website also reveals our server request to that website and its hosting or security providers, just as any web crawler request would.

Audit results may be cached to make repeated checks faster and protect free upstream services. Shareable report routes can continue to regenerate a current public-data snapshot when visited.

Operational logs are kept only as long as reasonably needed for security, abuse prevention, debugging, and infrastructure requirements. Backups and provider logs may expire on separate schedules.

• Do not submit a URL you do not want summarized.
• Clear recent audits from the homepage or browser storage.
• Review or withdraw analytics permission using the control in the Cookies & analytics section above.
• Use your site’s robots.txt and access controls to express crawler policy.
• Contact us about a report, log, correction, or deletion request.

For a request involving a domain report, include its full URL and be prepared to demonstrate reasonable control of the domain. Legal privacy rights vary by location; we will assess applicable requests based on the information involved.

This page will change as the product evolves. The date and version at the top identify the current policy. Material changes will be reflected here, especially before introducing accounts, payments, or materially different tracking.

Email hello@theseosoul.com with privacy questions or requests. Include the report URL or domain when relevant, but do not send passwords or identity documents unless we specifically request a safe verification method.