What aeogeo.site does with your pages, keys and account data: no AI model on your content, hashed keys, guarded fetches, and the providers involved.

Security and data handling

aeogeo.site runs no AI model on your content, and the scanner keeps a scanned page only in memory for the request that checks it. A shareable report you create keeps the scanned URL and its findings for up to 90 days; a whole-site scan keeps its results for 7 days.

Your content

No inference on your pages. The checks are deterministic code: the same page gives the same result. The API, the MCP server and the site import no AI-model SDK, and a test fails CI if one appears.
Pages and drafts aren't stored. Raw HTML and draft text are read in memory and dropped after the check. What is kept, and for how long, is listed on the privacy page.
Reports only when you ask. A report link stores the URL and derived findings (not the page HTML) under a random 128-bit ID. Pro and Team customers can revoke their links on the account page.
Your agent makes the changes. aeogeo returns findings, rules and fixes; it never edits your code, CMS or site. A connected agent works under its own provider's terms.

Fetching pages

The scanner fetches only public http and https URLs. It refuses URLs with credentials, private, loopback and other reserved IP addresses, and internal hostnames such as localhost or *.internal, before any request is made.
It reads the site's robots.txt and stops with an explanation when the page is disallowed.
Free scans have daily limits per domain and per IP address.

Keys and accounts

API keys are shown once and stored only as SHA-256 hashes, plus the first four characters so the account page can tell keys apart.
Sign-in for connected agents uses OAuth; grant metadata is stored encrypted.
Production access is limited to the operator, with two-factor authentication on every provider account. Secrets live in a secrets manager, never in the code.

MCP tools

The tools read and check; none of them changes your systems. Three keep data on our side, each on request: export_report creates a report link (as above), scan_site keeps a whole-site scan's results for 7 days so your agent can page through them, and set_retention_webhook stores the HTTPS address you give it for the Monday rule-change ping. Keyed tools need Authorization: Bearer <key>; the free tools at https://mcp.aeogeo.site need no key or sign-in. The full tool list is in llms.txt.

Providers

Cloudflare (hosting, database, edge), Contabo GmbH (a virtual server in France for the MCP server and analysis engine), PostHog EU (analytics), Resend (email delivery) and PayPal (payments). Traffic is encrypted in transit. Details and transfer safeguards are on the privacy page.

Reporting a vulnerability

Email support@aeogeo.site with the details; the contact is also in security.txt. If a breach affects personal data, we notify the data protection authority within 72 hours of becoming aware of it, and the people affected where the law requires it.

There is no security certification yet. If your security review uses a questionnaire, email it to the same address.