Privacy Policy
Last updated October 22, 2026
This policy explains what personal information Reqflow collects, why, where it is stored, who can see it, and what you can ask us to do with it. It covers this website (reqflow.ai), the Reqflow app, the interviews the app runs, and the emails we send.
Who we are
Reqflow is operated by Aleksandr Fomichev, Product Manager, in Australia, until the company that will run Reqflow is registered. This policy will then name that company, and we will tell account holders by email.
Questions, requests and complaints about privacy: contact@reqflow.ai.
The short version
- The website sets no cookies and runs no advertising trackers.
- Interviews are conducted by an AI assistant. People decide what happens with what it records.
- Our database is in Singapore. The AI models that process interviews run in the United States.
- We do not sell personal information, and we do not use your content to train AI models.
What we collect
When you ask for early access: your name, work email, company, company size, role and country; the optional answers you give (for example, how much of your work is fixed-price); whether you agree to a call; and how you found us: the advertising tags in the link you followed, the site that referred you, and the page you landed on.
When you use the website: pages viewed, clicks on buttons, how far down a page you scroll, steps of a form, and opening of elements such as questions and answers. Each event carries a random visit number that your browser keeps for that tab only and forgets when the tab closes, your browser’s time zone, the width of your screen, the type of device, and the advertising tags of your visit. This is not linked to your name unless you then send the early-access form, or create an account through a link on this website: both carry the same visit number.
When you have an account: your name, email address, job title, company and team; your password, which our authentication provider stores only in hashed form, or the sign-in links and codes we email you; your settings and email preferences; records of sign-ins, including the IP address, kept by our authentication provider; how you use the app (screens opened and actions taken), so we can see where people get stuck; and how your company found us. That is the advertising tags and visit number of the website link you signed up through, or, if there were none, those of your early-access request, matched by your email address.
When you run projects: what you enter: your customers, the people you invite (their names, email addresses and roles), the documents you choose, and the plans and decisions you make.
When you take part in an interview: your conversation with the assistant; the statements recorded from it, with the quotes they rest on; your consent to the interview; your corrections; and your progress.
When we email you: whether an email was delivered, bounced or marked as spam, and whether an interview invitation was opened. We learn about that opening through a small image in the invitation, sent by our email provider; our other emails carry no such image. We do not track clicks on links.
When you pay: our payment provider, Stripe, collects your card details; we never see or store your card number. We keep your plan, your balance of conversation turns, and references to your payments with the amounts paid.
When you write to us: your message and your contact details.
Why we use it
- To provide Reqflow: run interviews, record requirements, build and issue documents, show progress, and send the emails the service depends on (invitations, sign-in links, reminders, summaries).
- To handle early access: confirm your address, email you when your access is ready, and call you if you said we may.
- To understand which pages, buttons and advertisements work, and what each advertisement costs us for every customer it brings. We look at these numbers in aggregate.
- To keep the service secure: bot checks, limits on how often a form can be sent, and investigating misuse.
- To bill for paid plans, and to meet our legal obligations.
We do not sell personal information, and we do not build advertising profiles. We do not use your projects, interviews or documents to train AI models.
How the AI assistant works
The assistant asks the people you invite about their part of the project, records what they say as statements in their own words, sorts those statements, finds contradictions between people, and drafts documents from them. It can be wrong, so people check its work: everyone sees the statements recorded from their own words and can correct them, a contradiction goes to the person at the customer who decides, and the project’s administrators decide what is issued.
Reqflow does not use AI to make decisions about people, such as decisions about their employment, credit or access to services.
The AI models are provided by:
| Provider | What it does | Where |
|---|---|---|
| Fireworks AI | Runs the language model that conducts interviews and processes answers | United States |
| OpenAI | Turns short excerpts of answers into numbers, to find related statements | United States |
They process this content to return a result to us, under their terms for business customers.
If you were invited to an interview
A company that uses Reqflow (a software vendor or integrator) invited you, usually because you work with them on a project. That company decided to contact you, and it is responsible for having a reason to share your name and email address with us.
Before the interview starts, you are told what it is about and asked for your consent. You can decline to talk to the assistant, stop at any time, and come back later. Reminders and follow-up questions by email each have a link to stop them.
Who sees what:
- You see your conversation and the statements recorded from your words, and you can correct them.
- The vendor’s project administrators can see the whole conversation.
- Other people in the project see the recorded statements and the quotes they rest on, but not your conversation.
Who else handles your information
We use service providers to run Reqflow. They process information for us, for the purposes above.
| Provider | What it does | Where the information is stored or processed |
|---|---|---|
| Supabase | Database, sign-in, file storage and server functions | Singapore |
| Amazon Web Services | Our processing server, email sending, backups | Singapore |
| Amazon CloudFront | Delivers this website’s pages from locations near you | Worldwide (the website’s public pages only) |
| Fireworks AI | AI language model | United States |
| OpenAI | AI processing of short excerpts | United States |
| Stripe | Payments | United States and other locations |
| Microsoft 365 | Our mailbox, contact@reqflow.ai | Microsoft’s data centers |
| Google Fonts | Delivers the app’s fonts; Google sees your IP address when your browser loads them (this website serves its own fonts) | United States and other locations |
When you export or publish documents to another tool, such as Jira or Confluence, what you send there is handled under your agreement with that tool’s provider.
We may also disclose information if the law requires it, or to protect the rights, property or safety of our users or others.
Because of the providers above, personal information is stored and processed outside Australia, mainly in Singapore and the United States.
How long we keep it
- Early-access requests that are never confirmed are deleted after 30 days. Confirmed requests are kept until your access starts. If you unsubscribe, we stop emailing you; ask us and we will delete your request entirely.
- Website events are deleted after 400 days.
- Account, project and interview data are kept while the account is open. When you ask us to delete an account, we delete its data within 30 days, except records we must keep by law, such as billing records. Copies in backups expire within a further 90 days.
- Technical records of each processing run are deleted automatically after about two weeks.
- Email delivery records are kept with the account they belong to.
Like any web service, our providers’ infrastructure keeps short-lived technical logs, which can include IP addresses.
How we protect it
Information travels encrypted (HTTPS) and is encrypted where it is stored. Access inside the database is restricted row by row, so each person sees only what their role allows. Forms are protected by a bot check and limits on how often they can be sent. Our staff access project content only to operate, secure and support the service, or when you ask us to.
No service is perfectly secure. If a data breach is likely to cause someone serious harm, we will notify the people affected and the Office of the Australian Information Commissioner, as Australian law requires.
Your choices and rights
- See or correct your information. You can correct statements recorded from your own words in the app. For anything else, write to us.
- Delete it. Ask us to delete your account, your early-access request, or your part in a project.
- Stop emails. Every email about early access, and every interview reminder and follow-up question, has a link to stop them.
- Stay anonymous. You can browse this website without telling us who you are. An account, an early-access request and an interview need your name, because statements are attributed to the people who said them.
We reply within 30 days. If you are not satisfied with our answer to a complaint, you can contact the Office of the Australian Information Commissioner at oaic.gov.au. If you live elsewhere, you may have further rights under your local law; write to us and we will help.
Cookies and browser storage
This website sets no cookies. It keeps one item in your browser’s session storage, the random visit number described above, which disappears when you close the tab.
The app keeps your sign-in session in your browser’s storage so that you stay signed in. If you open the app through a link from this website or an advertisement, it also keeps that link’s advertising tags and visit number until you create an account, which then carries them. It uses no advertising cookies or trackers.
Children
Reqflow is a service for businesses and is not meant for anyone under 18.
Changes to this policy
When we change this policy, we update the date at the top. If a change is significant, we will email account holders before it takes effect.