Privacy Policy
Last updated: 4 September 2026
This policy explains what personal data Sequo collects, why, who else sees it, and what you can do about it.
Who is responsible for your data
The controller of your personal data is:
Artem Horobchenko
Warsaw, Poland
Contact for anything in this policy, including requests about your data:
privacy@sequo.app
Sequo is operated from Poland. The EU General Data Protection Regulation (GDPR) applies.
What Sequo does, in one paragraph
Sequo turns a description of a software project into a build plan, a set of project documents, and one prompt per step that you paste into your own AI coding agent. Sequo does not write or run your code. It stores your project description and everything generated from it.
What we collect
When you use Sequo without an account. We create a random identifier and store it in a cookie on your device so we can show you your own work when you come back: the project you started, and any capability you asked us to add you to the list for. We do not know who you are. If you later create an account, that project is linked to your account and the anonymous identifier stops being used for it.
When you create an account. Your email address, and either a password (stored by our authentication provider as a hash, never as text we can read) or the email address and basic profile information your Google account returns if you sign in with Google.
What you type into Sequo. The project description you enter, your answers to the clarifying questions, and any revisions you request. Everything generated from that: the structured version of your idea, the technology choices, the build plan, the project documents, and the step prompts.
As you work through the plan. Which steps you have marked complete, which of a step's "done when" checks you have ticked, and which of the setup confirmations you have ticked. This is how Sequo knows where you are when you come back to a project.
When you continue a project. Once a plan is finished you can have a further phase built on top of it. We store the directions we suggest for what to build next, which of them you chose, and any direction you write yourself in your own words. The new plan steps are stored with the phase they belong to and that phase's name, and we store a record of which of your documents that phase changed — that record is what lets us tell you the copies you already downloaded are out of date.
Technical data. Your IP address and request timestamps, used to limit how often the same visitor can trigger expensive operations and to block automated abuse. Your browser user agent when you send feedback.
Page views. We use Vercel Web Analytics to count how many people reach each page and where they arrived from. It records, for each page view: the time, the page address, the site that linked you here, the country and region your request came from, and your browser, operating system and device type. It identifies a visitor by a hash computed from the request itself, which is discarded after 24 hours, so it cannot follow you from one day to the next and cannot recognise you on another website.
On cookies we repeat Vercel's own words rather than a stronger version of them: it works "without using any third-party cookies". We have not seen it write anything to a browser, but "no third-party cookies" is the claim Vercel actually stands behind, so it is the claim we make here. This counting runs for everyone, including people who decline the analytics described next.
Product analytics, and session recordings only if you accept them. The first time you visit, a banner asks whether you accept analytics. Your answer decides how you are measured, not whether you are counted at all — and it is worth being exact about the difference.
Before you answer, and if you decline. We count the visit, anonymously. PostHog records the page views, how far you scroll, and the same list of product events set out below. Nothing is written to your device and nothing is read from it — no cookie, no local storage, no identifier of any kind. There is no session recording. You are never identified, never tied to your account, and never joined up with an earlier or later visit: PostHog counts you with a hash it works out on its own servers from the request your browser was already making, and that hash changes every day, so even we cannot tell that two visits on two days were the same person.
If you accept. PostHog stores a cookie, your visits join into one session, session recording starts, and your account is linked to it. All of that is described below.
You can change the answer at any time at the bottom of this page.
What it records about how you use Sequo. Page views and the address of each page; which screens you reach and in what order; how far down the landing page you scroll and how long you are on it before you first interact; when you focus the idea field, when you first type in it, whether you used the example button, and how many characters you sent; how many clarifying questions you were asked and which of them you answered; whether you edited the structured idea and how many times; whether generation succeeded or failed, how long it took and how many steps came back; and whether you reached the build screen. It also records clicks and form submissions on its own, and aggregates clicks and scrolling into heatmaps. None of that carries text you wrote — it carries counts, lengths, positions and yes-or-no answers.
Session recordings, which are the part to read twice. PostHog records your screen as you use Sequo — a replay of the page exactly as it was rendered to you, which we can watch back afterwards. That includes the text of your own project: your project description, your answers to the clarifying questions, your structured idea, your build plan, your project documents and your step prompts. If it was on your screen, it is in the recording. We use these to find where the product confuses people. They are private to us and are not shown to other users.
Some things are hidden before a recording leaves your device, so they are never recorded and never reach PostHog: password fields, email addresses wherever they appear — both as a field you type into and as text printed on the page — and the tokens the bot check uses. That masking happens in your browser, not on PostHog's servers.
Page addresses are cleaned in your browser before anything is sent, to Vercel and to PostHog
alike. The identifier of a project is replaced with a placeholder, so every project reports
the same address, and the query string is reduced to campaign parameters such as
utm_source. Nothing that names your project, your checkout, or where you were being sent
after signing in leaves your browser. Inside a recording, the address bar and the network
requests it captures are cleaned by the same rule.
How it knows it is still you. If you accept, PostHog stores a cookie and a small amount of data in your browser, and your browser is given a random identifier so the screens you visit join into one session. When you create an account, that identifier is tied to your account's internal id — never to your email address, which is attached as a separate property so we can find you if you write to us. Joining a journey up like this is the thing you are agreeing to when you accept, and it is the reason it is a choice rather than something we do on legitimate interest.
Feedback. If you use the feedback widget: the message you write, the page you sent it from, the project it relates to, your account email if you are signed in, and an email address if you choose to give one.
When you ask for help on a build step. If your coding agent asks you something, errors, or wants something done that you are unsure about, you can paste that text into the step and we will answer it. We store what you pasted and what we answered, against that step. We keep it for two reasons: so you can reopen the answer when you come back to the step, and so we can see where the prompts we generate leave people stuck — that is how those prompts get better. We take nothing else from your machine or your code; only the text you paste.
Payments. If you subscribe, the payment is handled by Polar, which acts as the seller of record. Polar collects and processes your payment details. We never see or store your card number. We receive confirmation that a subscription is active, and the identifiers needed to link it to your account.
Please do not paste secrets
Treat the idea field as you would a message to a colleague. Do not paste passwords, API keys, access tokens, or personal data about other people. Your text is sent to an external AI provider (see below) and stored in our database.
The same applies to the step help box. Error output from a coding agent sometimes carries a key or a connection string in it — check before you paste, and replace anything sensitive with a placeholder. It reaches the same provider and the same database.
One more reason to be careful, if you accepted analytics: a secret pasted into either box is on your screen, and a session recording captures your screen. We mask passwords and email addresses, but we cannot recognise an API key inside a wall of pasted error output. Replace it before you paste it.
Why we process it, and on what legal basis
| What | Why | Legal basis (GDPR Art. 6) |
|---|---|---|
| Account data | To create your account, sign you in, and let you return to your projects | Performance of a contract, Art. 6(1)(b) |
| Anonymous identifier | To show you your own project, and any capability you asked to be added to the list for, before you register | Performance of a contract, Art. 6(1)(b) |
| Your project content | To generate the plan, documents, and prompts you asked for, and to show them back to you | Performance of a contract, Art. 6(1)(b) |
| IP address, request timestamps | To rate-limit and block automated abuse that would otherwise exhaust our costs | Legitimate interests, Art. 6(1)(f) |
| Page views | To see how many people reach each page and where they came from, so we know which parts of Sequo are used and which are not | Legitimate interests, Art. 6(1)(f) |
| Anonymous product analytics, before you answer the banner or after declining | To see which steps of the flow people finish and where they stop, without holding anything about you | Legitimate interests, Art. 6(1)(f) |
| Cookies, session recordings, and linking your visits to your account | To watch back what a confusing screen actually looked like, and to follow one person's journey across screens and visits | Consent, Art. 6(1)(a) — you give it on the banner and can withdraw it at any time |
| Feedback | To understand problems and improve the product | Legitimate interests, Art. 6(1)(f) |
| Step help you ask for | To answer you, to show you that answer again later, and to find the generated prompts that leave people stuck | Performance of a contract, Art. 6(1)(b), and legitimate interests, Art. 6(1)(f) |
| Subscription status | To give you access to paid features | Performance of a contract, Art. 6(1)(b) |
| Invoice and tax records | Because tax law requires us to keep them | Legal obligation, Art. 6(1)(c) |
| Operational alerts | To find out that an account was created, a plan generation failed, a subscription became active, or feedback arrived, without reading the database | Legitimate interests, Art. 6(1)(f) |
Our legitimate interest in the abuse-prevention case is keeping a small service financially viable and available. We use the smallest amount of data that achieves that.
Our legitimate interest in the page-view case is knowing whether the product is reaching anyone and which pages they read. The tool that does that counting answers it with very little: no third-party cookie, no identifier that outlives a day, no profile, and nothing that follows you to another website.
The product analytics split across two bases, and the line between them is the point of the banner. Counting a visit anonymously — no cookie, no storage, no identifier, a hash worked out on PostHog's servers that changes daily — takes nothing from you and holds nothing about you, and we rely on our legitimate interest for it, the same interest as the page counting above: knowing whether the thing works.
What we do NOT claim a legitimate interest in is the rest of it. Setting a cookie, joining your visits into one person, tying that to your account, and recording your screen are a different order of thing, and they run on consent alone. Nothing of that kind happens until you say yes, and withdrawing is one button on this page. Withdrawing stops the cookies, the identification and the recording at once; it does not by itself erase what was already recorded, so if you want that too, ask us and we will delete it. Anonymous counting continues either way, and you can object to it on the terms in the rights section below.
Our legitimate interest in the alerts is reaching a problem before you give up on it. The one that matters is a failed plan generation: it is the moment a person is most likely to close the tab for good, and a message that arrives within the minute is the only thing that gives us a chance to fix it while they are still there. The alerts carry the least that makes them useful — an identifier, an email address where there is one, and the opening of the text in question — and there is no alert for anything that merely went well.
Who else processes your data
We use the following providers. Each one only receives what it needs.
| Provider | What it does | What it receives |
|---|---|---|
| xAI (Grok) | Generates your plan, documents, and step prompts, and answers the help you ask for on a step | Your project description, your clarifying answers, the previously generated content for that project, and anything you paste into the step help box |
| Supabase | Database and authentication | All stored data: account, projects, generated content, feedback |
| Vercel | Hosting | Request data, including IP address |
| Vercel | Web Analytics, which counts page views | The cleaned page address, the referring site, approximate location, and browser and device type. No third-party cookie, and no identifier that lasts beyond 24 hours |
| PostHog | Product analytics for everyone; cookies, identification and session recordings only if you accept analytics | Always: the cleaned page address and the events listed above, counted against a daily server-side hash. Only after you accept: a cookie, your account id, and a recording of your screen, which contains your project text. Hosted on PostHog Cloud EU, in Frankfurt |
| Resend | Sends account emails and feedback notifications | Your email address and the email content |
| Cloudflare | Turnstile, which distinguishes people from bots | IP address and browser signals at the moment you submit a form |
| Sign-in, only if you choose "Sign in with Google" | The sign-in exchange; Google tells us your email address | |
| Polar | Payments and subscription billing | Your payment details, which it collects directly |
| Telegram | Carries four operational alerts to a private chat we read | Your email address when an account is created or a subscription starts, the first sentence of your project description if its plan fails to generate, and the opening of a feedback message you send |
Read that first row carefully. Sending your project description to xAI is how Sequo works. There is no version of the product where that does not happen.
The Telegram row is how we find out that something happened without waiting for someone to tell us. Four things are sent, and nothing else: an account was created, a plan generation failed, a subscription became active, and feedback arrived. A failed generation carries the opening of your project description, because without it the alert names a problem we cannot recognise. Routine activity — projects created, plans generated, phases continued — is never sent anywhere.
The PostHog row is the one that receives your project text, and it receives it only because a recording is a picture of your screen — so it receives it only from people who accepted. If you declined, or have not answered, PostHog still receives the anonymous counting described earlier, and never a recording.
We do not sell your data. We do not share it with advertisers. We run no advertising. We run two analytics tools and no others, both described above in full: the page counting, which runs for everyone and cannot identify you, and PostHog, which counts everyone anonymously and only sets cookies, identifies you and records your screen once you have accepted.
Where your data is stored, and when it leaves the EU
Our database sits in Frankfurt, Germany. Your account, your projects, and everything Sequo generates for you are stored inside the European Union. Supabase, which operates that database, is a US company, so its staff may access the infrastructure for support and maintenance.
If you accept analytics, your events and recordings are stored on PostHog Cloud EU, whose servers are in Frankfurt — so that data, including the project text a recording contains, stays inside the European Union too. PostHog is a US company, so the same caveat applies as to Supabase: its staff may access the infrastructure for support and maintenance, and the safeguards below cover that.
Some processing happens outside the European Economic Area. xAI generates your content in the United States. Vercel serves the site and counts page views, Resend sends the email, Cloudflare runs the bot check, Google handles sign-in if you use it, Polar processes payments, and Telegram carries the operational alerts described above, all from outside the EEA.
These transfers rely on the safeguards in Chapter V of the GDPR, which in practice means the European Commission's Standard Contractual Clauses, the EU-US Data Privacy Framework where the provider is certified, or both. Ask us and we will tell you which mechanism covers a specific provider.
How long we keep it
Your account and project data stay until you ask us to delete them, or until you delete your account. We do not expire inactive projects.
Rate-limiting records hold an identifier and a counter for the length of the limit window, measured in hours, then stop being used.
Page-view records carry nothing that identifies you. The hash that stands in for a visitor is discarded after 24 hours, and what stays is a count against a page.
Product analytics sit with PostHog. The anonymous kind — everything collected before you answer the banner, or after declining — is keyed to a hash that PostHog recomputes daily and then cannot reverse, so those events stay as counts against a page and there is nothing in them to trace back to you, by us or by anyone asking us.
Session recordings and the events tied to your account, if you accepted, are a different matter. Recordings expire on their own: our plan allows a maximum of 30 days and we do not extend it, so a recording of your screen is gone within a month of being made. Events have no automatic expiry and stay until we delete them. Ask us and we will delete both — PostHog supports erasing a person together with their events and recordings, and deleting your account is our cue to do it without being asked.
Feedback is kept for two years so we can track recurring problems.
Step help exchanges stay with the project they belong to, and go when it does.
Your progress marks, the phases of your plan, the directions you chose for a next phase, and the record of which documents it changed are part of the project too, and go with it.
Invoices and payment records are kept for as long as tax law requires, which in Poland is generally five years from the end of the tax year.
Operational alerts sit in the private Telegram chat they were sent to until it is cleared. They are a copy of something we already hold, so deleting your data means deleting the record it came from; ask us and we will clear the alerts too.
Your rights
Under the GDPR you can ask us to:
- give you a copy of the personal data we hold about you
- correct anything inaccurate
- delete your data
- restrict how we process it
- send you your data in a portable format
- stop processing based on legitimate interests, by objecting
- withdraw consent you gave for analytics and session recordings
Write to privacy@sequo.app. We answer within one month.
Withdrawing analytics consent needs no email. The control is at the bottom of this page and takes effect immediately. Withdrawing stops further collection; to have what was already recorded deleted as well, write to us and we will do it.
On deletion, one honest note. Sequo has no self-service delete button yet. Email us and we remove your account and your projects manually.
If you think we are handling your data wrongly, you can complain to the Polish supervisory authority:
Prezes Urzędu Ochrony Danych Osobowych (UODO)
ul. Stawki 2, 00-193 Warszawa
uodo.gov.pl
You can also complain to the authority in the EU country where you live.
Cookies
Sequo sets these cookies without asking, because each one is strictly necessary to deliver something you asked for:
- an identifier that links you to work you did without an account: a project you started, or a capability you asked us to add you to the list for
- session cookies that keep you signed in, set by our authentication provider
- a cookie set by Cloudflare Turnstile when it checks that a form submission comes from a person
- a cookie recording your answer to the analytics banner, so we do not ask again and so a "no" is remembered
We also set analytics cookies, but only after you accept them. That is what the banner is for. Accepting lets PostHog store a cookie and a small amount of data in your browser, which is what joins your visits into one session; it also turns on the session recordings described earlier in this policy.
Declining, or simply not answering, means none of that is stored: no analytics cookie, no local storage, nothing written to your device and nothing read from it. It does not mean you vanish from the numbers. The anonymous counting described earlier keeps running, on a hash PostHog computes on its own servers rather than on anything kept on your machine. We think that is the honest trade — we can still tell whether the product is working without holding anything about you — but it is the reason the banner asks about cookies and recording rather than about being counted.
You can change the answer at the bottom of this page at any time.
Switching analytics off does not only stop the collection. It also deletes what was stored on your device for it — the analytics cookie, the identifier that joined your visits together, and the copies PostHog kept in your browser's storage. Nothing analytics-related is left behind, and accepting again later starts a new person rather than resuming the old one.
We run no advertising cookies and no ad-network pixels, and nothing we set is used to follow you to another website. The two analytics tools above are the whole of it, and neither follows you off Sequo.
The page counting is the exception that needs no banner. Vercel Web Analytics identifies a visitor by a hash computed from the request your browser was already making, holds it for 24 hours and then discards it, and Vercel describes it as working without third-party cookies. It runs on our legitimate interest, on the terms set out earlier, and it keeps running whichever way you answer the banner.
Automated processing
Sequo uses an AI model to produce your plan and documents. That is the product working as intended, and you decide what to do with the output. We make no automated decisions that produce legal effects for you or similarly significantly affect you within the meaning of Article 22 of the GDPR.
Treat generated content as a draft. Review it before acting on it.
Children
Sequo is not for anyone under 18. We do not knowingly collect data from children. If you believe a child has given us data, write to us and we will delete it.
Security
Access to your data is restricted at the database level, so one user cannot read another user's projects. Traffic runs over HTTPS. Passwords are hashed by our authentication provider. No system is perfectly secure, and we do not claim otherwise. If a breach puts your rights at risk, we will notify you and the supervisory authority as the GDPR requires.
Changes to this policy
When this policy changes we post the new version here and update the date at the top. We do not email you about it, so check this page before you rely on what it says.
Contact
privacy@sequo.app
Artem Horobchenko, Warsaw, Poland
You have not chosen yet. Nothing is loaded.