Privacy Policy

Last updated: October 15, 2026

This Privacy Policy explains how flow9 ("flow9," "we," "us," or "our") collects, uses, stores, and protects information when you use flow9 Studio at flow9ai.com.

flow9 converts natural-language descriptions of tasks into working software agents. To provide this service, we store information such as your prompts, generated code, build history, and credentials that you choose to provide.

1. Who Is Responsible for Your Data

flow9 is operated by Dagmfre Seid, an individual developer based in Ethiopia.

For questions about this Privacy Policy or your personal data, contact:

Email: support@flow9ai.com

2. Information We Collect

Anonymous sessions

When you first visit flow9, we create an anonymous session so that you can use the Studio before creating an account. This consists of a database record and a session cookie in your browser. The anonymous session does not contain personal information.

Device cookie and abuse prevention

Every browser that reaches the Studio is given a random device cookie, which lasts a year and carries no personal information. The Studio's page also stores a second cookie listing a few facts every browser on one computer reports alike: the screen size and colour depth, the number of processor cores, touch support, the time zone, the first language and the operating system. The first time a confirmed account is used, flow9 records one-way hashes of both cookies, the network address the request came from (for a newer IPv6 address, only the part that identifies the home network) and the browser's user-agent string on the free-credit record, and uses them for one purpose: to tell whether the same browser, network or computer has already received free credit or free builds in the last 30 days, so that one person does not receive them several times. An account that matches gets neither, can still sign in and can still subscribe. These signals are never used for advertising. The address, the computer hash and the user-agent string are deleted from the record after 30 days; the device cookie hash stays, because that is what the check is made against.

Three more checks may run when free credit is first decided, each only where flow9 has it switched on. The network address is sent once to proxycheck.io, which says whether it belongs to a VPN, a proxy, Tor or a data centre, and which time zone it is in. If it is a VPN, Tor or a data centre, or if your browser's clock is two hours or more away from that zone, the free credit and free builds wait until you come back without the VPN; the address is not stored with that record. The Studio's page runs Fingerprint's check once, which sends browser and device signals to Fingerprint and returns an identifier for this device; flow9 keeps only a one-way hash of it, to tell whether the same device already received free credit, and keeps it as long as the device cookie hash. If you choose to add a card to unlock the rest of the free credit, you add it on Polar's own page; flow9 reads the card's brand, last four digits and expiry from Polar once, keeps only a one-way check value of them so that the same card cannot unlock free credit twice, and then removes the card from Polar. The card is never charged.

Account information

If you create an account, we may collect:

• Your email address
• Your name and profile image, if provided by Google or GitHub when you use either service to sign in
• A securely hashed password if you register using email and password

Passwords are never stored in plaintext.

Prompts and conversations

We store the prompts you submit and the questions or responses generated by flow9 during a build. This information is stored with the associated build so that the Studio can display and restore your conversations.

Build runs and transcripts

We maintain records of builds, including:

• Build stages and execution history
• Generated code
• Execution times
• Token usage
• Build status, such as completed, stopped, or declined
• Relevant run transcripts

This information allows the Studio to display and replay previous builds.

Generated code and files

We store the agent modules and related files generated by your builds so that you can view, run, and export them from the Studio.

Model provider API keys

If you provide your own model provider API key, flow9 encrypts it using AES-256-GCM before storing it.

The Studio displays only the last four characters of the key. The plaintext key is never returned to your browser. It is decrypted only in server memory when required to execute a build and is not permanently stored in plaintext.

While your account runs on free credit, builds and workflow runs use flow9's own provider key instead, and your prompts and build context are sent to Anthropic under flow9's account with that provider.

Connected applications

If you connect an external application such as Slack, Linear, Notion, GitHub, or Gmail, the connection and its associated access tokens are managed by Composio, which provides the integration infrastructure.

flow9 stores the identifier for the connection rather than the underlying access token.

Analytics and tracking

flow9 currently does not use:

• Advertising trackers
• Tracking pixels
• Third-party analytics
• Session-recording tools
• Advertising cookies

If product analytics are introduced in the future, this Privacy Policy will be updated before those features are introduced. Any product analytics will be limited to event names and counts and will not include your prompts, build content, or generated code.

3. Where Your Data Is Stored and Who Processes It

Model providers process data according to their applicable terms and policies. By using your own provider API key, you are responsible for your relationship with that provider and the terms applicable to your account.

flow9's own server is in the European Union. Several of the services listed above are based in the United States, so information you send through flow9 may be transferred to and processed in the United States.

Payments

If you buy a paid plan, Polar (Polar Software, Inc.) is the merchant of record for that purchase and is an independent controller of the payment data you give it, under its own privacy notice at polar.sh/legal/privacy-policy. We give Polar your account's email, name and account id when you open a checkout, so the purchase reaches the right account. Your card details go to Polar and never reach flow9. What we receive back from Polar, and store, is limited to what we need to run your account: Polar's customer and subscription identifiers, which plan you are on, and its status and renewal date. If you add a card to unlock free credit, we give Polar the same three things to make your customer record, and read back only the card's brand, last four digits and expiry, which we turn into a one-way check value before removing the card. Refunds and cancellations are covered by the Refund and Cancellation Policy.

4. Cookies

flow9 uses a session cookie to maintain your authenticated session or associate an anonymous session with your conversations, and two cookies whose only use is the free-credit check described in section 2: a device cookie (a random id, one year) and a computer cookie (the hardware facts listed there, one year).

flow9 does not currently use advertising or tracking cookies.

If you clear your session cookie, you will be signed out. An anonymous session that has been cleared cannot be recovered.

5. Data Retention

Conversations and build records are retained until you delete them or request deletion of your account.

Stored model provider API keys remain until you remove them through Settings or your account is deleted.

One small record outlives a deletion. Every build that is delivered counts against the monthly free allowance, and that count is kept under a one-way code made from your email address, not under your account. It is kept for at most two months, so deleting a build, a conversation or your account and signing up again with the same address does not reset the allowance. We can check whether a new sign-up matches the code; we cannot turn the code back into your address.

The free-credit record is kept under the same one-way code and is not deleted, because a grant made once must stay made: deleting the account and signing up again with the same address finds it. It holds the amount granted and spent, the device cookie hash described in section 2, and for 30 days the network address, the computer hash and the user-agent string.

The server keeps its own operating logs for 14 days, visible only to flow9's operators. A log line can hold your email address (for example, when an email to you could not be sent) or part of a build's or workflow's error output. Keys, tokens and passwords are masked before a line is stored. Timings, memory and token counts for a build or a workflow run are kept for 90 days.

Files generated by builds and stored on the server are not intended to be permanent storage. flow9 is currently in beta, and the server filesystem may be replaced during deployments. As a result, files from previous builds may become unavailable.

You should export any files or builds you wish to retain.

Exported code belongs to you and does not depend on flow9 to run.

6. Your Rights and Choices

You can:

• Export your work: Export builds as ZIP files and conversations as Markdown from the Studio.
• Delete conversations: Delete a conversation and its associated runs from the Studio, using the menu on any conversation in the sidebar.
• Remove API keys: Remove a stored provider API key at any time through Settings.
• Delete your account yourself: Settings contains a delete-account control. It removes your account and everything associated with it, including your conversations, build records, generated files, workflow conversations, and stored API keys, and any build you published stops being public. The deletion is immediate and cannot be undone. The one exception is the build count described in Section 5.
• Request access or deletion: Contact support@flow9ai.com from the email address associated with your account to request a copy of your data or deletion of your account.

We aim to respond to data requests within seven days.

If you are located in the European Union or United Kingdom, you may have rights under applicable data protection laws, including rights of access, correction, erasure, data portability, and objection.

7. Publishing a Build

Builds are private by default.

If you choose to publish a build, the build's prompt, generated code, and transcript become publicly accessible to anyone with the link, including people who are not signed in.

You are responsible for ensuring that you have the necessary rights and permissions to publish the content.

You can unpublish a build at any time. Unpublishing removes it from the public gallery, but it cannot remove copies that other people may have previously accessed, downloaded, or reproduced.

Do not publish a build containing confidential, personal, or otherwise sensitive information that you do not intend to make public.

8. Security

flow9 uses reasonable technical measures to protect stored information, including:

• HTTPS for data transmitted between your browser and the service
• AES-256-GCM encryption for stored provider API keys
• Server-side storage of encryption keys through environment configuration
• Secure password hashing
• Rate limiting for authentication attempts

flow9's internal instructions and other users' private work are not exposed to users through the Studio.

No online service can guarantee absolute security. flow9 is currently a beta service operated by a single developer. If you believe your data or account has been compromised, contact support@flow9ai.com.

If we become aware of a security incident that requires notification under applicable law, we will provide the required notice.

9. Children

flow9 is not intended for individuals under 16 years of age. Individuals under 16 must not create or use an account.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page will be updated whenever changes are made.

If a change materially affects how we handle your data, we will notify registered users by email before the change takes effect.