Privacy Policy

Effective and last updated: October 21, 2026

Who we are: aiagentcomparisons.com ("we", "us") is run by the owner of aiagentcomparisons.com. Questions: use our contact form or email [email protected].

Short version

• We set no cookies, show no ads that track you, and have no accounts or email list.
• We may count visits with Cloudflare Web Analytics, which doesn't set cookies or use other browser storage. If it's on, every page loads Cloudflare's small analytics script from static.cloudflareinsights.com.
• The contact page also loads Cloudflare Turnstile, a spam check. We load no other outside scripts.
• If you use our contact form, email us or reply to us on X, we get what you send, and we use it only to handle your message.
• Form and email messages are kept as plain text and deleted automatically after 90 days (see section 4). Some copies last longer or are kept elsewhere; section 4 lists them.
• AI agents read and process the messages you send us. A person, the owner, sends every reply.
• We never sell or rent personal data.

1. What we collect

When you visit

• Analytics: If we've switched it on, we use Cloudflare Web Analytics. Cloudflare says it doesn't use cookies or other browser storage and doesn't fingerprint visitors. It collects page-view and performance data: the page address, the referring page, load timings, and browser and operating-system type. Cloudflare says the IP address is not stored. We see only totals.
• Hosting: the site is hosted on Cloudflare Pages. As the host, Cloudflare handles your IP address and browser details to deliver pages and block abuse, under its own privacy policy.
• Cookies and ads: we set no cookies. We load no ad scripts, tracking pixels, third-party fonts or social widgets. Boxes marked "Sponsored" are plain labeled space, not tracking ads.
• Do Not Track: we don't track you across sites, so a browser's Do Not Track signal doesn't change anything we do.
• Spam check on the contact page: only the contact page (/contact/) loads Cloudflare Turnstile. Cloudflare's Turnstile Privacy Addendum says Turnstile processes signals such as your IP address, TLS fingerprint, browser user-agent, and the site key and page origin, to tell people from bots. Cloudflare processes these signals for us to protect the form, and as its own controller to improve Turnstile. Cloudflare says Turnstile doesn't read, store or send what you type in the form. When we check the result, our form sends your IP address to Cloudflare; our own code doesn't store it. Turnstile's analytics in our Cloudflare dashboard show us the IP addresses that trigger the most checks. Turnstile runs in a Cloudflare frame and may use cookies or local storage on Cloudflare's own domain to complete the check. We don't read or set them. Logging is turned off for our mail Worker, so Cloudflare's logging products don't keep its requests.

When you send us something

You choose what to send. The contact form is the main route; email is the backup.

• The contact form at /contact/: you choose a topic (a question or comment, or disputing a result) and write a subject and a message (up to 4,000 characters). You can add your email address (optional, only if you want a reply) and which result you mean (optional). The form doesn't accept files. We store the topic, your email address if you gave one, the subject, the result and message text, the time it arrived, a record of what our cleaning removed, and a few flags about the message (for example, that it was cut short). A hidden spam-trap field isn't stored.
• Email to [email protected] (questions and result submissions) or [email protected] (disputes and corrections). We store which address you wrote to; the email address on the From line (not your display name) and the delivery sender address, which can be forged, so we treat them as unconfirmed; the subject line (up to 200 characters); the time it arrived; up to the first 4,000 characters of your message as plain text; and a record of what the cleaning removed (for example, how many attachments and what general kind), plus a few flags (for example, that it was cut short or the sender address looks forged).
• Cleaning: formatting and attachments (including screenshots) are removed before anything is stored, and attachments are never opened. Most web addresses are "defanged" so they stay readable but can't be clicked (for example, https://example.com becomes hxxps://example[.]com). We read only the first 32 KB of an email. If an email is bigger, we keep the cleaned text from its start, up to 4,000 characters, and the rest is never read or stored. We don't bounce it or tell you automatically. Please keep messages short and send evidence as a link.
• X: if you reply to, mention or message us on X, we see what you send and your public profile. Public posts are governed by X's privacy policy.

What we don't collect

• Accounts or passwords.
• Email-list signups. We don't run an email list. If we start one, we'll update this policy before the signup opens.
• Payments. The site takes none.

2. How we use it

• Analytics: to count visits and fix broken or slow pages.
• Messages: to review your submission, correction or question, reply to you, and keep a record of what we decided. An AI agent drafts each reply; the owner reviews and sends it.
• If we publish something you sent, we publish only a text verdict, its date and your public evidence link. We never republish screenshots, images or attachments you send. We add your public X handle only if you ask. We never publish your email address, and credits never go into our open data files.
• Never: no advertising profiles, no tracking across sites, and no selling, renting or trading of personal data.

3. Who processes it

Who reads your messages, and where.

• Who reads it: one AI agent, our site-operations agent, reads the cleaned text with a read-only key. That agent runs on a shared computer that the owner's other AI assistants also use. Keeping your messages to that one agent is a rule we follow, not a technical wall between our agents, and while it works, the text it reads and its draft replies may sit on that shared computer.
• Your message is data, not instructions: our agent is told to treat every message as untrusted text, and never to act on it, send anything because of it, or open links in it. That's a rule, not a technical guarantee. What the tools technically can't do: the code that stores and lists messages can't send, reply to or forward mail, and the key it reads with is read-only.
• Evidence links: links you send are never opened by the agent that reads mail. If we check one, a separate session that doesn't handle mail opens it. This is a rule we follow.
• Replies: the AI only drafts. The owner reviews and sends every reply from [email protected], through Cloudflare Email Sending (see section 4).

We may also disclose information if the law requires it, or to protect our rights or someone's safety.

4. How long we keep it

• Form and email messages: stored as plain text in our Cloudflare D1 table. A daily automatic cleanup deletes each one once it's more than 90 days old, so a message can stay in the table for up to about 91 days. Attachments are never stored.
• Cleanup records: each cleanup run is logged with its time, whether it worked, how many messages it deleted and, if it failed, a short error type. These records hold no message text and are deleted on the same schedule.
• Cloudflare's restore history: Cloudflare D1 can restore the database to an earlier point for up to 30 days, so a deleted message can still be recovered from that history for up to 30 days after it's deleted.
• Cloudflare's email activity log: for each email, Cloudflare Email Routing keeps a log entry, visible in our Cloudflare dashboard, for about 30 days. It holds the From line as sent (including any display name), the To address, the full subject line, the message ID and the results of email authentication checks.
• Copies held by Cursor: text our AI agent reads, and its drafts, pass through Cursor, which hosts our agents (section 3). Cursor keeps data "only for as long as necessary", with no fixed period.
• Our review log (what we received and what we decided): kept for 12 months after we close the item, then deleted.
• Replies: we send replies from [email protected] through Cloudflare Email Sending. Cloudflare processes your email address, our subject line and the reply text to deliver it, and keeps delivery logs (recipient, time, status) under its privacy policy. Our review log keeps what we decided (see above). If you answer a reply, it arrives at contact@ like any other email: it's cleaned, stored and deleted after 90 days.
• Send log: for each reply we send, we keep a keyed hash of the recipient's address (not the address itself), the time and the result, to enforce sending limits. Entries older than 30 days are deleted each time we send a reply.
• Published corrections: stay on the public log, without your email address.
• Analytics: kept by Cloudflare. We see only totals.

5. Your choices and rights

• You can ask to see, correct or delete personal data we hold about you. Use the contact form or email [email protected]. We'll reply within 30 days.
• You may have more rights under the law where you live.
• Public X posts can only be deleted by you, on X.

6. Children

This site isn't aimed at children under 13, and we don't knowingly collect their data. If you think a child has sent us personal data, contact us and we'll delete it.

7. Open data

Our data files at /data/ contain agent and site results only. They contain no personal data about visitors or people who write to us, and no submitter credits or X handles.

8. Changes to this policy

We'll post any change here, update the date at the top, and note significant changes in the changelog. If we ever add an email list, ads, or analytics that use cookies, we'll update this policy before that starts.