What ApexClaw collects, what it does not, and how to reach us about it.
This page states what is actually true of this site today — built from the same rule the rest of the site holds to: sourced, first-party, and dated. See the trust center for the full claims ledger this policy draws on.
Published · updated · reviewed by Julian Joseph, founder
Who this covers
This policy covers apexclawai.com. ApexClaw (company entity) is personally funded and personally owned by Julian Joseph, founder (see the founder page). Omega is a governed system operated by ApexClaw. Growth services referenced on this site are delivered by ThruLiquid.
What is collected today
This site keeps standard web-server access logs for every visitor, human or automated: requesting IP address, user agent, path requested, and timestamp. That log is used for security and for first-party measurement — for example, the AI-crawler request counts published on the agentic AI governance statistics page are drawn from exactly this log, nothing more.
There is no account system, no checkout, and no payment collection anywhere on this site. The contact page is explicit that a server-side intake form is on the roadmap and not yet live — the only channel today is direct email, and anything sent that way is read and used solely to respond to the enquiry.
- Server access logs: IP address, user agent, path, timestamp — every visitor.
- Direct email enquiries — read and used solely to respond.
Cookies and tracking
This site does not set tracking cookies and does not run third-party analytics or advertising pixels. If that changes, this page will say so, with a new dateModified, rather than silently starting to track visitors.
AI and agent access
Automated and AI-agent access to this site is governed by the posture published in robots.txt: crawlers are grouped by the job they do — retrieval, live agent fetch, training, and classic search — and observed rather than blocked. The same posture and its rationale are explained on the trust center.
What is never done
- No sale of personal data. ApexClaw does not sell visitor or enquiry data to third parties — 0% of visitor or enquiry data is shared with third-party analytics or ad networks.
- No client named, ever. Engagements are described without identifying the client — the same rule the trust center states for every public claim.
- No fabricated numbers. Any figure on this site is sourced, first-party with stated methodology, or labelled TARGET, SYNTHETIC, or COLLECTING.
Security disclosures
Security researchers can report findings via security.txt (RFC 9116). Reports about agent-facing surfaces — MCP endpoints, published schemas, the signing key directory — are especially welcome. Structured data on this page follows JSON-LD 1.1 and schema.org, per Google's structured data guidance.
Common questions
Does ApexClaw sell my data?
No. ApexClaw does not sell visitor or enquiry data to third parties.
Does this site use tracking cookies?
No. This site does not set tracking cookies and does not run third-party analytics or advertising pixels.
What does ApexClaw collect?
Standard web-server access logs for every visitor (IP address, user agent, path, timestamp), and direct email enquiries. No account system, checkout or payment collection exists on this site.
How do AI agents access this site?
Governed by the posture published in robots.txt: crawlers are grouped by job (retrieval, live agent fetch, training, search) and observed rather than blocked.
How do I report a security issue?
Via security.txt (RFC 9116). Reports about agent-facing surfaces are especially welcome.
Changes to this policy
This page carries a datePublished and dateModified, the same convention the claims ledger uses: changes are dated, not made quietly. Questions about this policy go to the contact below.
Contact
Email: julian [at] thruliquid [dot] com. For anything else, use the contact page. See also Terms.