We measure engines, not people.

What we collect

Your email address and first name when you request a free visibility report or create a workspace.

The brand domain and competitor names you ask us to measure, the prompts you track, and the answers AI engines return for them.

Operational records of what the product did for you: measurement runs, drafted fixes, approvals and outcome receipts.

If you connect your own request logs, we process them on your behalf and only to classify AI crawlers, AI agents and visits for you. For each request your site served, the AI traffic feature receives the path, the host, the user agent, the referrer, the Accept header, the client IP and, where the source records it, the status your site answered with, and for a request signed with Web Bot Auth also its method, its full URL and its signature headers. The client IP, the Accept header and the signature material are used in memory to check the visitor against its vendor's published ranges or keys and are not stored. What lands in the table is the classified bot, what the visit was for, its verification level, whether it asked for Markdown, the status your site answered with, the path, the host and which collector sent it. Cookies and bodies are not collected.

If you arrive through a partner's referral link (an address ending in ?ref= and a code), a first party cookie on this site remembers that code for 30 days, so a signup in that time is credited to the partner once. It holds the code and nothing else, and no third party tracker is involved. The signup form shows you the code before you create an account, and you can change it or clear it.

A partner whose link you signed up through sees that a workspace joined through it, when, its plan, whether it pays and the monthly amount. It never sees your name, your email address or anything you measure.

Why we collect it

Email is how we deliver your report, your daily digest and account messages. Nothing else.

Brand and prompt data is the product: we measure how AI engines answer, diagnose why you are absent, and prove whether fixes moved the needle.

Anonymised statistics

Measurements may feed anonymised statistics about how AI engines behave, as the terms set out: never naming you, your brands, your clients or a person, never quoting your questions, drawn from at least five workspaces with none making up more than half, only from measurements taken after the terms applied to you, and never from a workspace that opted out in Settings.

What we never do

We do not sell your data or share it with advertisers.

We do not train models on your workspace data.

We do not post anywhere on your behalf on our own initiative. Publishing runs on a request from your workspace, and every push writes a receipt you can read.

Who processes data for us

Measurement reaches the engines two ways, and both carry only the prompt text, never your account details. Some engines answer through their own API (OpenAI, Anthropic, Google and xAI), and the consumer surfaces are read by scrape through DataForSEO and SearchAPI, with OpenRouter routing Perplexity. So DataForSEO and SearchAPI see every prompt measured on a scraped surface, and OpenRouter sees every Perplexity prompt.

Email delivery runs on Resend, billing on Polar, hosting and the database on Railway and Vercel, and jobs on Inngest. The full list, every vendor with what it is for and every account you can connect yourself, is on the security page at /security.

Your controls

You can ask us to delete your workspace and its data at any time by emailing kailesk@ansengine.co. Deletion removes your brands, prompts, answers and receipts.

One kind of record survives that deletion on purpose: a platform wide suppression, the note that somebody asked to stop being contacted at all. It holds a hash of their address and nothing else, and removing it would quietly restore our ability to mail a person who opted out. Your workspace's own suppression list goes with the workspace.