ESP32 Agent
Account privacy
Last updated: October 28, 2026
This notice covers the Handsy website account, payments and hosted AI service, provided by Holomix, Inc. The released iOS app is covered by the separate app privacy policy.
1. Sign-in
Google Firebase Authentication handles website sign-in. It processes the identity information supplied by the sign-in provider you choose, along with the connection and device information needed for authentication and abuse prevention. See Firebase's privacy information. A sign-in option is shown only when it has been set up. When the Google One Tap prompt is available, it lets you choose an account; the regular Google button stays available. Your browser and Google may hide the prompt.
Firebase keeps your sign-in state in your browser's local storage, so you can come back from checkout without signing in again. Use Sign out on a shared device. The account page sends a short-lived sign-in token to our servers to authenticate requests. Our servers check it and match it to your Handsy account. They do not keep the raw token, your sign-in email or your display name. Matching email addresses do not merge separate Handsy accounts.
Our servers check that a sign-in token is genuine and not expired. They do not check for account deletion or sign-out elsewhere on every request, so a token that was already issued may keep working until it expires, for up to about one hour. Signing out in this browser stops the account page from using it.
2. Payments and account records
Stripe handles card entry and payment processing on the website. See Stripe's privacy policy. We keep your Handsy account ID and the order, customer, subscription, invoice, transaction, refund, dispute and balance records needed to deliver purchases, reconcile payments and prevent abuse. We do not receive or store full card numbers.
Pages marked Sandbox use Stripe test payments; live checkout takes a real payment. A Handsy API key lets supported clients use this account's balance when hosted AI is enabled. App Store purchases remain separate.
3. Hosted AI usage
When you use Handsy's hosted AI service, our upstream provider, Infron, receives the messages, screenshots and tool information needed to answer your request. It may retain this content and process it outside your country. Infron's retention terms and processing region have not been verified. We do not promise zero data retention.
We may retain AI requests and responses, including prompts, screenshots, tool calls and tool results, in private Cloudflare storage. Available records also include account, request and response identifiers, links between calls, model/provider details, token counts, costs, timings, status, reservations and balance adjustments. We use these records for service history, billing, debugging, review and improvement. They are not public.
Authentication headers, API keys, sign-in tokens, cookies and payment credentials are excluded or redacted from operational capture. Do not put credentials or card details into AI prompts or screenshots.
Training on these retained records is off. Records are ineligible by default and remain pending consent. Any future training use requires separate consent and a review of rights and permitted use; buying usage or retaining a record does not authorize training.
A completed answer may also stay in server memory for up to ten minutes for retries with the same request ID and unchanged content. Retaining a history record does not guarantee response recovery; a client that loses its request ID may be unable to recover a lost answer.
API keys
The account page displays a newly created API key once, masked by default. It keeps that new value only in page memory until you dismiss it, sign out, switch accounts or leave the page; it does not save it in browser storage or analytics. Copying the key places it on your system clipboard at your request. The server stores a one-way hash rather than the full key. Key management shows the key’s name, prefix, dates, spending limit, usage and reservations. An optional connection check sends the key only to this site’s model-list endpoint and does not generate an AI response.
4. Security and service providers
We use sign-in checks, payment verification and request limits to protect accounts and purchases. Where set up, Cloudflare Turnstile checks checkout requests to limit automated abuse. Our website hosting, sign-in and payment providers process the network information needed to provide their services. We do not put prompts, screenshots, AI answers or sign-in tokens into product analytics.
The local sandbox may offer a separate test account. The browser remembers only that you chose it and asks for a new temporary test token after a reload; the token is not saved in browser storage. This test account is not a Google or Apple login.
5. Your choices and requests
For access, correction, account deletion or other privacy requests, email [email protected]. We may need to check that the account is yours. Signing out, revoking an API key or clearing browser storage does not delete retained AI, purchase or usage records. Financial and abuse-prevention records may need to be kept for accounting, disputes or legal requirements, and deletion requests are reviewed with those obligations in mind.
See also the purchase terms and pricing.