Privacy
What we collect, and what we do not.
Last updated 16 November 2026
What this page covers
This covers stea.dev, the site you are reading, and the Stea product: the dashboard at app.stea.dev, where our customers build their agents, and the demos those agents run on our customers' sites.
Who we are
Individual Entrepreneur Anton Selikhov, Tbilisi, Georgia, runs Stea. For visitors to stea.dev and for customers who sign up at app.stea.dev, we decide what happens to your data. For people who watch a demo on a customer's site, that customer decides, and we process the data on their behalf. You can reach us at support@stea.dev.
What we collect here
A page count, and nothing that identifies you, unless you start the live demo: what that takes is in the next section. We use Plausible, which sets no cookie, writes nothing to your browser storage and builds no profile across sites. That is also why there is no consent banner on this page: there is nothing to consent to.
What it records: which page was opened, which site you arrived from, and a rough country, browser and device type worked out from your IP address. The address itself is not stored. The counter is served from our own domain rather than loaded from somewhere else, so your browser makes no request to a third party when the page loads.
On top of page counts we count three things, as totals only: clicks on the button that opens our booking page, the verdict the demoable check reaches, and whether the calculator found a gap — as a band, never your numbers.
The check and the calculator run entirely in your browser. The answers you pick and the figures you type are never sent anywhere, and we could not read them if we wanted to.
Our host keeps ordinary server logs, which include IP addresses and are used to run and secure the site.
The live demo on this site
The home page loads the demo's script from poc.stea.dev, our own server. That request does not include your email.
The demo box asks for a work email and says, next to the field, that the demo shares it with us. Pressing the button is your consent: the address is sent to poc.stea.dev and kept as a lead, so that we can follow up about the demo. A message with it goes to our team's Telegram chat, and it also appears in that server's logs.
That server decides whether the address opens the demo. A personal address does not: the demo shows it back to you with a way to book a call instead, and the server does not keep an address it refuses. If it refuses an address, you can enter another one there; pressing Start in the demo sends that address the same way. The demo remembers two display choices, whether subtitles and its list of topics are shown, in your browser's local storage for poc.stea.dev; nothing in them identifies you.
The demo is a conversation, so it asks for your microphone. What you say is processed and recorded by LiveKit Cloud, which runs the voice side of the demo and keeps the recording and its text for 30 days. LiveKit passes it to the speech and language models listed under “Who processes data for us”. The text of the conversation is also kept in the Stea dashboard for 30 days.
Our server keeps the text of the conversation, your answers to the questions the demo asks, and its own logs of the demo for 30 days. Its daily backup can hold them for up to 36 days in all.
Ask us to delete any of it and we will.
When you book a call
The booking button opens Calendly, a separate company. Whatever you type there — your name, your email, anything you add — goes to Calendly and then to us. That happens under Calendly's privacy policy, not this page.
The link carries one thing with it: where on this site you pressed the button, and which page you were on. That is how we tell which page brought someone to a call. It says nothing about you.
We use what you give us to hold the meeting and to follow up about it. We do not sell it and we do not add you to a marketing list you did not ask for.
If you sign up for Stea
You sign in to app.stea.dev with Google or with a link we email you. We keep your email address and, if you use Google, the name on that account.
In the dashboard you give us your organization's name, your product's address, a brief, and the materials your agent answers from: files, links and text. We keep them for as long as your organization exists with us.
You sign in to your demo account on a page run by Kernel, our cloud browser provider. Kernel keeps the password encrypted and uses it to sign back in for demos and checks. We never see it.
To build your agent, our builder opens your product in a Kernel browser, signed in to the demo account, and reads its screens together with your brief and materials. The builder runs on models by Anthropic. When you ask for a draft of the brief, an Anthropic model writes it from your product's website.
Paddle sells our plans as Merchant of Record: your card and billing details go to Paddle, not to us. We keep the state of your subscription and how many extra demos were charged.
Emails from the dashboard, such as an agent going live or demos pausing, are sent through Resend. Our team gets short notices about agents in a Telegram chat: your organization's name, the agent's name and your product's address.
To close your account, write to support@stea.dev. We delete your organization and its data within 30 days, unless the law requires us to keep something.
Demos on our customers' sites
When a customer's agent runs a demo on their site, the customer is responsible for the data of the people watching it. We process it only to run the demo and to show the customer its record. If you watched such a demo, ask that company about your data; they can ask us to delete it.
What the demo handles: your voice and the text of the conversation, the language you speak, the screens it shows you, and your email, but only if the customer's demo asks for it or the customer's site passes it on. The demo also remembers the two display choices described above, in your browser.
Your voice goes to LiveKit Cloud, which runs the conversation. Through LiveKit Inference it is transcribed by AssemblyAI (by Deepgram when the demo detects your language), answered by a Google language model, and spoken back in a voice by Inworld. The screen you watch is a Kernel cloud browser signed in to the customer's demo account, and Kernel records a video of that screen.
LiveKit keeps the recording of the conversation and its text for 30 days. Our server keeps the text, its own logs of the demo and your email for 30 days; its daily backup can hold them for up to 36 days in all.
The customer's dashboard keeps the text of the conversation, with the questions the agent could not answer, for 30 days. Your email, the screens shown, the language, and when and how long the demo ran stay there for as long as the customer's organization exists with us.
Who processes data for us
Railway hosts this site, our demo server and the dashboard. Supabase holds the dashboard's database and runs its sign-in. Cloudflare runs our domain names and routes email sent to support@stea.dev.
Plausible counts visits to this site. Calendly runs the booking page. Paddle takes payments as Merchant of Record. Resend sends the dashboard's emails. Telegram carries our team's notices.
Kernel runs the cloud browsers that build and show demos, and keeps demo account sign-ins. LiveKit runs the voice of every demo, with speech and language models by AssemblyAI, Deepgram, Google and Inworld through LiveKit Inference. Anthropic's models build agents and draft briefs.
We do not sell any of it.
Your rights
You can ask us what we hold about you, have it corrected or deleted, and get a copy. Write to support@stea.dev.
If you think we got it wrong, you can complain to the data protection authority where you live or work.
Changes
If this page changes, the date at the top changes with it.
Questions about any of this? Write to support@stea.dev or book a call.