Privacy notice

Draft, not yet reviewed by counsel. Last updated 2026-10-17.

When you run a scan

We keep the website address you submit, and for each public page our scanner fetches: its address, HTTP status, size, a content hash, and the facts the checks need, such as titles, headings, links, and structured data. Findings keep short excerpts as evidence, not full copies of pages. Your IP address is used in memory to rate limit scans and is not stored with the scan.

When you create an account

Sign-in is handled by our authentication provider, Clerk, which keeps your email address and sign-in details. We keep your user id and what you set up: the businesses you create, the domains you add and verify, the feeds and API descriptions you import, and the capabilities you configure. If you publish an agent endpoint, we record the calls agents make to it so we can show you analytics.

When you connect an AI assistant (OAuth sign-in)

When you connect an assistant such as Muse or ChatGPT to a2ahello, you sign in with Clerk and choose what the assistant may do. We store a principal id (a random identifier linked to your Clerk account), which assistant app you connected, the permissions you granted, the businesses you allowed it to order from, and when. Access and refresh tokens are stored only as hashes, never in readable form; access tokens last one hour and refresh tokens 30 days. Businesses never receive your tokens, only a signed statement of who is calling that is valid for 5 minutes. You can disconnect at any time by removing the connector in your assistant; a business can also disconnect an assistant from its own business.

When you place an order or booking through an assistant

To let a business fulfil an order or booking, we keep the order (items, prices, totals, status, cancellation terms, and which assistant and principal placed it) and the buyer, guest, and payer details you give (name, email, phone, notes). Those details are encrypted (AES-256-GCM) before they are stored, are never returned to assistants in tool results, and inside a business only its owners and admins can see them. We share an order only with the business that receives it and its payment processor. Orders and buyer details are deleted 90 days after the order is completed or cancelled (or its payment failed), together with the order's events and payment records; a business may set a different period, from 7 days to 10 years, for its own record keeping. Orders still open or awaiting payment are kept until they end, and everything goes when the business closes its account. Our fee ledger keeps only the order number and amounts, because it is what we invoice from. Sample businesses on a2ahello are fictional and their orders are never fulfilled.

Payment mandates

If you let an assistant pay within limits you set (a mandate), we store the mandate: which businesses it covers, the per-order and total limits, the currency, the expiry, and each use with its amount, so every order can be checked against what is left. You can see and stop a mandate at any time. A mandate never contains card details or other payment credentials, and we do not store any.

Payments

Payment goes to each business's own payment processor (for example Stripe). A payment token from you or your assistant is passed through to that processor within the order request and is never stored, logged, or shown again; we keep only the payment method kind and the processor's reference. a2ahello never holds funds. A business's processor key is stored encrypted.

Audit logs and webhooks

Each tool call to a business writes an audit record: time, platform, principal, tool, a hash of the arguments (not the arguments themselves), the result, and the policy decision. Audit records are kept 90 days by default. A business can receive signed notifications (webhooks) about its orders and stock at addresses it chooses; the order events behind them, and their delivery records, are kept 90 days. Notification signing secrets are derived when needed and not stored.

When you or your AI agent talk to a business's agent

A business on a2ahello can have a hosted AI agent that answers other agents and the people they work for. When you send it a message, we store the conversation (your messages, its answers, and the business data it looked up) so the conversation can continue and the business can see how its agent is used. Before storing your messages we remove email addresses, phone numbers, and card-like numbers; the full text is used only in memory to produce the answer. Do not send passwords, payment details, or health information. To answer, your message and the business's data are sent to OpenRouter, which routes it to the AI model provider; both act as our processors, and we ask OpenRouter to use only providers that do not keep the data for training. Your IP address is used in memory to rate limit messages and is not stored with the conversation. The agent is automated, not a person, and cannot book, buy, or change anything.

When a business's agent remembers your agent

A business's agent remembers customer agents it can recognize, so it can help them again and tell them when something they asked for is back. This is on by default. Recognized means one of: another agent hosted on a2ahello, or a long random handle the agent chooses to send (a2ahello.customer_handle), on its own or together with an API key the business issued or a request signed by the agent (Web Bot Auth, verified against the agent's published keys). An API key or a signature alone is not enough, since one platform may serve many people, unless the business marked that key as a single customer. We never recognize an agent by its IP address or user agent, and keep nothing for agents we cannot recognize. What is stored is structured only, no message text: the items, sizes, variants, dates or filters it asked for, whether they were available, and the messages sent to it. The handle is stored only as a keyed hash. When something an agent asked for is back in stock, the business's agent may send it one message, at most once every 7 days, saying that it is an automated agent and how to stop. That message, including any offer code in it, stays in the delivered task and its conversation for 30 days, like other agent conversations. Any agent can ask what is remembered ({"a2ahello.memory": "status"}), stop messages ("opt_out" or "stop messages"), or have it erased ("delete" or "forget me"). Erasure takes effect at once; only a hashed record of the choice remains, for 180 days, so the agent does not remember or message it again in that time.

How long we keep it

Anonymous scans, meaning scans not saved to an account, are deleted automatically after 30 days, with their pages and findings. Agent conversations are deleted automatically after 30 days. What a business's agent remembers about a customer agent is deleted 180 days after that agent's last visit; after an erasure, the hashed record of it is deleted 180 days later. Proactive messages, including any offer codes, stay in the delivered conversation for 30 days. The log of proactive messages, which keeps no message text, is deleted after 90 days. Orders and buyer details are deleted 90 days after the order ends, unless the business set another period. Audit records and order events are kept 90 days. Account data is kept while your account is open, and we delete it when you ask.

What we do not do

We do not sell your data. These public pages use no advertising or tracking cookies and no third-party analytics. We share data only with the providers that host and run the service, and only for that purpose.

Your choices and contact

To see, correct, or delete your data, email [email protected]. Website owners can block our scanner; see the scanner page. For help or to report a security problem, see support.