Privacy policy.

No accounts.

We never ask for a name, an email address or a password. We never ask for a seed phrase or a private key. Anyone who asks for one is not SECONDED.

Your check goes to two AI companies.

Everything your agent sends for a check is processed by one model from OpenAI and one from Anthropic. Send a check only what it needs.

Payments are public.

You pay in USDC or USDG from a wallet, on a public blockchain. Anyone can see the paying address, the amount and the time.

Deleted on a schedule.

The records of a finished check are deleted automatically after 90 days, and support messages after 30 days. Some records go sooner, as listed below. A minimal accounting record of each payment and refund is kept.

The check input.

What your agent sends: a transaction or a permit, a token or contract address, an agent to look up, a message, or a web page or document. We use it to run the check. We do not store the whole input. We keep two things derived from it:

A salted fingerprint. A fingerprint of the input, made with a random salt for each check, so a receipt can be matched to its request. We keep the salt with the check’s record until that record is deleted, and your SECONDED client keeps its own copy on your machine. A receipt alone does not contain the salt. Because we hold the salt while we hold the record, the fingerprint does not stop someone with access to our database from confirming a guess of a short input, such as a single token address. Receipts issued before this change also carry a plain, unsalted fingerprint of the input; new receipts do not.

Findings. The facts the check computed, such as the addresses, amounts and transaction hashes it examined. Findings are stored encrypted, with a separate key for each record.

The verdict. The label of the answer, stored encrypted. Never the models’ own text.

The paying wallet address.

Read from your signed payment. We use it to settle the payment, to issue refunds, to apply fair-use limits (such as free results per wallet per 24 hours), and to keep per-wallet totals of paid checks.

The signed payment.

Your wallet’s signed payment authorization is stored encrypted, readable only by our settlement service. It is erased once the check is finished or the authorization expires.

Payment and usage records.

The amount, the network, the settlement transaction, any refund, and how much model work the check used and what it cost. No check content.

Support messages.

What you send through the support form: your message, its topic, and a way to reach you if you choose to give one. We use it only to answer you, and delete it after 30 days.

Your IP address.

We do not store it. To rate-limit requests we keep a keyed fingerprint of your network block (the first three parts of an IPv4 address, or the first 48 bits of an IPv6 address), and delete it after 24 hours. Our API server keeps no access logs.

Operational logs.

Our services log only a fixed set of operational details, such as check IDs, states, timings and token counts. Anything else is dropped before it is written. Logs are kept for up to 3 days.

OpenAI and Anthropic.

They receive the check input, plus the public facts SECONDED gathered for it. The models may use their provider’s built-in web search while answering, so search queries based on your input can pass through those providers’ search tools. Their API terms govern how they handle it.

Blockchain data providers.

We read public chain data through Alchemy and through public RPC endpoints for Base, Arc and Robinhood Chain, including PublicNode and dRPC. They see the addresses looked up, including the paying wallet. For Trade Check, the transaction you asked about is simulated on these providers, so they see its contents.

Block explorers.

Blockscout and Sourcify see the token and contract addresses a check looks up. Sourcify’s signature database sees function identifiers from a transaction being decoded.

Robinhood.

For Stock Token Check, Robinhood’s public API sees the stock token symbol being checked.

Domain record services.

When a message sent to Scam Check contains links, we look up each link’s domain in public registration records (the RDAP server for that domain ending), public certificate logs (crt.sh) and Google Public DNS. They see the domain names.

Payment facilitators.

On Base, payments settle through Coinbase’s CDP x402 facilitator, which receives the signed payment, including the paying address and amount. Coinbase screens both addresses (KYT and OFAC sanctions screening) and can decline a payment. On the Base test network, payments settle through the public x402.org facilitator. On Arc and Robinhood Chain, SECONDED settles payments on chain itself.

Our alert channel.

Our team gets service alerts through Telegram. A service alert carries only its type, the network, a count, and an internal check number or transaction hash: never an address, an amount or check content. Messages you send through the support form are forwarded there as plain text, with the way to reach you if you gave one.

Hosting.

The API runs on servers we rent from DigitalOcean. This website is hosted by Vercel.

Lists we download.

We download public reference lists, such as the OFAC sanctions list, MetaMask’s phishing list and stablecoin token lists. Nothing about you is sent to fetch them.

Every check returns a signed receipt.

SECONDED signs each receipt so anyone can check it came from us. It contains the check ID, the product, the paying wallet, the amount and network, the settlement transaction, the salted request fingerprint, the names of the labs whose models answered, the findings and what the check could not examine, and the verdict.

You can prove what a receipt covers.

Your SECONDED client keeps each check’s salt on your machine and never sends it to us. With the salt and the original input, you can prove offline which input a receipt covers, even after we have deleted our copy. Keep the salt private: anyone who holds it and the receipt can test guesses of the input.

A receipt travels with whoever holds it.

Anyone you share a receipt with can read everything in it, including the findings. While we hold a check’s record, we can rebuild its receipt when asked; once the record is deleted, we cannot. We cannot recall a receipt already given out.

Deleted within days.

The signed payment authorization: once the check is finished or the authorization expires. The duplicate-request key: when the check finishes or its quote expires. The network-block fingerprint: after 24 hours. Operational logs: after up to 3 days.

Deleted after 30 days.

Support messages, with their topic and the way to reach you.

Deleted after 90 days.

A job runs every day. It deletes a finished check’s records 90 days after the check’s last activity: the salted fingerprint and its salt, any older unsalted fingerprint, the findings, the encrypted verdict, and that check’s payment, refund and usage records, including the wallet address stored with them. Per-wallet counters for wallets that have been inactive that long, old alerts and expired signing challenges are deleted too.

Kept until it is settled.

A check with a payment still pending, a paid answer not yet delivered, or a refund still open is kept until that is resolved, then deleted on the same schedule.

Kept for accounting.

When a check’s records are deleted, we keep a minimal record of each payment and refund: the network, the asset, the amount, the time and the public transaction hash, with no check ID and no wallet column. We also keep daily totals of model costs and of unpaid amounts. A public transaction hash can be looked up on its chain, so these records are minimized, not anonymous. They have no deletion date yet.

Backups.

Deletion removes records from the live database. Encrypted database backups are kept separately and can still hold a deleted record until that backup is itself removed.

Encrypted where it counts.

Verdicts and findings are encrypted with a separate key for each record. Signed payments are encrypted to the settlement service and erased after use. All API traffic uses HTTPS.

Least access.

Each part of the service has its own database role with only the access it needs. The deletion job can delete records but cannot read them or reach any key. The server can connect only to an approved list of outside services.

No system is perfect.

If a breach affects your data, we will say so on this site.

No names, no passwords, no keys.

There are no accounts. A request you send us contains only what you choose to put in it. The support form asks for a way to reach you only if you want a reply, and you choose what to give.

No tracking on this site.

This site runs no analytics, loads nothing from other sites and sets no cookies. Its only script is on the support page: it comes from this site and does nothing but send the form.

No one can erase a chain.

We cannot change or delete what a public blockchain records. If the link between a wallet and its activity matters to you, choose which wallet your agent pays from.

Ask us.

You can ask what we hold about a wallet, or ask us to correct or delete it. Send the wallet address and any receipt IDs through the support form. We may ask you to sign a message with that wallet to show it is yours. We will never ask for a seed phrase or a private key.

What we may keep.

What we need to finish a payment or refund that is still open, and the minimal accounting record of each payment and refund described above.

What deletion cannot reach.

Public blockchains, and what OpenAI, Anthropic, Coinbase, Alchemy, another RPC provider, an explorer, a domain-record service or Telegram holds under its own terms.

Where you live may give you more rights.

Depending on your location, privacy laws may give you further rights, including the right to complain to a regulator.

Changes.

When this policy changes, the new version is posted here with a new date.

Contact.

Use the support form. It is how to reach us about anything on this page.

Beta terms, subject to change · Effective September 25, 2026. Payment and refunds are covered by the terms of service.