Privacy policy

Last updated: October 20, 2026

This policy explains what personal information OpenIntents collects when you use openintents.io, our API, MCP server, command line tool and SDKs (together, "the service"), why we collect it, who we share it with and the choices you have. OpenIntents is operated by tinyhumans ("we", "us").

If you build on OpenIntents and send us purchases on behalf of your own customers, this policy covers how we handle their information too. You are responsible for telling your customers about it.

What we collect

Account information. Your name and email address, and your Google or GitHub account ID if you sign in with one. We do not receive your Google or GitHub password.

Credentials. API keys, sign-in links and session tokens. We store only a one-way digest of each, never the secret itself.

Purchase requests and results. The intents you send and the details they include, such as names, delivery addresses, phone numbers, preferences and spending caps; the progress of each purchase; and the receipt (store, items, totals and the store's confirmation number). Customer IDs and metadata you attach are stored as you send them.

Browser profiles. Each payer has a browser profile holding the cookies, carts and store sign-ins built up by their purchases, so a store recognises them next time. A profile can give access to the payer's store accounts, so we treat it like a password: it is encrypted at rest and only our browser workers can read it. Where a purchase runs in a browser hosted by our browser provider (below), the profile is kept by that provider instead, encrypted at rest, and deleted there when you ask us to forget it.

Sign-in pages. When a store needs a payer signed in, they sign in on a picture of the store's page that we show them. What they type there is passed to the store's page and not kept once it has been sent. Screenshots of that page are stored encrypted for the short life of the sign-in link.

Payments. Purchases are paid from the payer's own wallet at Perflo, which holds their money; we do not. When a payer connects their wallet, Perflo gives us a token that lets us ask for payments within the limits they set; we store it encrypted, along with Perflo's ID for them. For each purchase we keep the amount, its status, the dates and Perflo's reference for it. To pay the store, we read the payer's virtual card details from Perflo once and type them into the store's payment form. We keep those details in memory for that purchase only: we never store them, and they are never shown to the AI model, to you or to your agent. The money the payer adds, the cards they save and their identity check are handled by Perflo on its own pages.

Webhooks. The URLs you register and a record of what we sent them.

Technical data. IP addresses, request logs, error reports and timing, used to run, secure and debug the service.

Cookies. We use only the cookies the site needs: your sign-in session (oi_session) and your language choice (NEXT_LOCALE). Your light or dark theme is kept in your browser's local storage. We do not use advertising or cross-site tracking cookies, and we run no third-party analytics on the site.

How we use it

To carry out the purchases you ask for, from finding the item to delivering the receipt.
To pay for purchases from the payer's wallet, keep a record of each payment, and prevent fraud and abuse.
To keep you signed in and to secure your account and API keys.
To support you, answer questions and investigate problems with an order.
To keep the service running, measure its costs and fix faults.
To meet legal, tax and accounting obligations.

We do not sell personal information, and we do not use it for advertising.

We share only what each party needs to do its part:

Stores you buy from receive what any shopper gives them at checkout: the items, the delivery details in your intent, and the payer's wallet card for payment. Their own privacy policies apply to what they receive.
AI model providers process the text of your intent and the content of the store pages being shopped, to decide each step. They never receive card details.
Perflo processes payment data and holds the payer's wallet. We give it the payer's ID with us, their email and name when we have them (so the wallet is theirs and their sign-in is filled in), and for each purchase the store's name and web address, the amount and a short description. Perflo's own privacy policy applies to what payers give it directly, such as the cards they save and their identity check.
Hosting and network providers run our servers, store encrypted data and carry the browser's traffic to stores.
Our browser provider (Browser Use) may run the browser a purchase is made in, and keeps that payer's browser profile. It sees the store pages being shopped and what is typed into them, delivery and payment details included, and records no video of them.
Email providers deliver sign-in links and service emails.
Google and GitHub, if you choose to sign in with them.
Authorities, when the law requires it or to protect the rights and safety of our users, the public or us.
A successor, if the service is merged, acquired or sold, subject to this policy.

How long we keep it

Sign-in sessions, sign-in links and one-time tokens expire on their own, within hours to days.
Commands sent to a browser session are kept for a day; text typed into a store's page is dropped once it has been sent.
Repeated-request records (Idempotency-Key) are kept for 24 hours.
A browser profile is deleted 180 days after its last use, or sooner when you ask us to forget it.
Purchases, receipts, payments and ledger entries are kept as long as your account exists and afterwards as long as tax and accounting rules require.

Security

Secrets are stored as digests, browser profiles and wallet tokens are encrypted at rest, wallet card details are never stored, and connections use TLS. Our browsers run in isolated workers that cannot reach our internal network, or at our browser provider, and each browser is closed and a payer's browser data cleared from the worker after every purchase. No system is perfectly secure; if you find a weakness, please tell us at [email protected].

Your choices and rights

Forget a browser profile at any time through the API (browser profiles). We delete every saved copy of it.
Access, correct or delete your information, or close your account, by emailing [email protected] from the address on your account. We will answer within 30 days.
Depending on where you live, you may have further rights, such as to object to some processing, to receive your data in a portable format, or to complain to a data protection authority. Contact us and we will help.

Privacy policy

What we collect

How we use it

How long we keep it

Security

Your choices and rights

International transfers

Children

Changes

Contact