Privacy

This site collects nothing.

No analytics, no tracking pixels, no cookies, no form endpoint. The enquiry form composes a message in your own mail client and posts nothing to any server. That is unusual enough to be worth stating plainly rather than burying in a policy nobody reads.

What the website does

Serves static pages from Cloudflare Pages. Cloudflare processes standard request data (IP address, user agent) to deliver and protect the site; we do not query, export or retain it.
Loads one typeface from Google Fonts, which means your browser makes a request to fonts.googleapis.com and fonts.gstatic.com. That is the only third party involved in serving this site.
Sets no cookies and runs no analytics.
Cloudflare injects its own analytics beacon into pages it serves. This site's Content-Security-Policy blocks it from executing, so it collects nothing — verified from the browser console, not assumed. If that ever changes, this page changes with it.

The enquiry form

Nothing typed into the form on the contact page is sent anywhere by the site. It is assembled into a message that opens in your own mail client, or is copied to your clipboard. There is no endpoint, no database, and no third-party form service.

If you send that message, we hold it as ordinary email correspondence in Google Workspace, and reply to it. Ask us to delete the thread and we will.

Client data during an engagement

Engagements need read access to systems that contain your data. That access is delegated to a named identity, logged, scoped, and revocable without you changing any credential.

What we ask for: Search Console, Analytics, server or CDN logs, CMS at editor level, Bing Webmaster Tools. Read access except where a specific named task requires more, which is time-boxed and handed back.
What we never accept, even if offered: DNS or registrar credentials, hosting root or server administration, or a shared password of any kind.
Logging: every access grant is recorded with its level, purpose and date.
On termination: delegated access is revoked and your data is returned or deleted, at your election.

Server logs supplied for crawler verification contain visitor IP addresses. We use them only to confirm crawler identity by published IP range, we do not build profiles from them, and we delete our copies at the end of the engagement or on request.

Subprocessors

Cloudflare (hosting and CDN), Google Workspace (email), and Google Fonts (typeface delivery). Any tool used to gather data during an engagement is named in the engagement brief before it is used.

Contact

Questions, or a deletion request: jason@auspexseo.com.

Last updated 6 September 2026.