Privacy policy

What this notice covers

This notice covers this website, synqflow.ai. It says what we collect when you fill in a form, talk to the assistant on the home page, or simply read a page.

It does not cover a Synq deployment. When Synq runs inside your company it runs on a machine in your own office, and what happens to your data there is set by the agreement you signed with us, not by this notice. The controls that apply to a deployment are described on the Saffron page.

The site is run by Synq AI, from DLF Cyber Greens, DLF Cyber City, DLF Phase 2, Sector 24, Gurugram, Haryana 122002, India. Write to swastik@synqflow.ai about anything on this page.

What we collect, and when

We collect nothing until you send it. There is no account, no login and no profile. There are three places where you can send us something, and one thing every website records.

Book a demo

The form at /book-demo asks for your name, your job title, your work email, your company and its size, when you want the first system live, the work you most want AI to take on, roughly how many hours a week it takes today, where that information lives, where AI is in your company now, whether your AI can show its sources, whether it respects who may see what, who owns AI inside the company, and anything you write in the last box.

Only the name, the email, the company, the work and the timing are required. The rest is asked because it makes the first conversation shorter, and you can leave it blank.

Academy, register interest

The form on /academy asks for your name, your email, your role and a note about what your team would build first.

The voice assistant

Tapping the orb on the home page asks for your email, then starts a spoken conversation.

Beside the transcript we keep the email you gave, a random id for that call, and four things read back out of the transcript afterwards: your name, your company, what you need, and the language you spoke. Those four are filled by one automated pass over the saved transcript, and anything you did not say is left empty.

If the assistant asks whether it may pass your details to the team, that question is about the note it writes for a person to read. It is not about the recording. The recording happens on every call.

Server logs

Our host keeps ordinary web server logs. We read the IP address of a request only to count how many requests come from one place in ten minutes, which is how the site turns away scripts. We do not file that address beside anything you sent us.

Measuring the site, if you agree

Since 16 September 2026 we count visits with PostHog, and only for visitors who press Yes, measure on the bar at the foot of the page. Until that press, nothing is stored in your browser and not one request is made to PostHog. Ignoring the bar counts as no, and Do Not Track is honoured whatever you answered.

After a yes, PostHog receives:

• Which pages you open, and what you click on them.
• Your device, browser, screen size and the page you came from.
• Your IP address, from which PostHog derives an approximate town. We do not file it beside anything you sent us.
• Three events of our own: that a demo was requested, that Academy interest was registered, and that a talk with the assistant began. Each is a bare fact with nothing attached, no email, no name, no text you typed.
• An error report if a page breaks in your browser, so we can fix it.

PostHog Inc. processes this for us on servers in the United States. The cookie policy lists the one cookie it sets and how long it lasts.

What we never collect

• No advertising identifiers, and nothing that follows you to another site.
• No recording of your screen. PostHog can do that; we have it switched off in code.
• No name or email attached to what you read. We never tell PostHog who you are, even if you have written to us.
• Nothing sensitive. Please do not send us any.

The voice assistant, in plain words

The assistant gets its own section, because it is the one part of this site that listens.

• It starts only when you tap it, and only after you give an email and the bot check passes. It is not listening before that.
• Your voice goes to Google. The conversation runs on Google's Gemini Live model for as long as the call lasts, so your microphone audio and the words of the call pass through Google to produce a spoken reply.
• It knows only what is public on this site. Its knowledge is built from the same pages you can read. It has no access to any customer deployment, and it cannot look anything up about you.
• It ends by itself. A call stops when you tap the orb again, when you press Escape, when you say goodbye, after about 25 seconds of silence, or after four minutes.
• The microphone is asked for by your browser, and you can refuse. Refusing changes nothing else on the site.

The transcript is kept as described above, and deleted after 90 days.

Cookies and browser storage

This site sets one cookie, PostHog's, and only after you press Yes, measure. Before that, and after a no, there is none. The cookie policy lists it in full, with what it holds and how long it lasts.

Two other things are kept in your browser and never sent anywhere. Your answer to that question, as synq-analytics-consent in local storage, so we do not ask again on every page. And, if you use the assistant, the email you typed, as synq-voice-email in session storage, so you do not have to type it again to start a second talk in the same tab. That one goes when you close the tab, and nothing but the assistant's email box ever reads it.

The bot check

Before a form is saved, and before a talk starts, the site runs Cloudflare Turnstile to tell a person from a script. Most visitors see nothing. Sometimes Cloudflare asks you to tick a box.

The check loads from Cloudflare at the moment you start filling a form or open the assistant's email box, never with the page. When it runs, your browser sends Cloudflare a token and your IP address, and we ask Cloudflare whether that token is good. What Cloudflare does with what it receives is covered by Cloudflare's own terms.

Without this check, a script could run up a bill on the voice assistant in an afternoon. That is the whole reason it is there.

Who else sees it

We use five services, and each sees only the part it needs. We sell nothing, we share nothing for advertising, and we have no advertising partners.

• Google Workspace. Form submissions and call rows are written to one spreadsheet in our own Google account, through a script we wrote. It is open to the people at Synq AI who answer enquiries.
• Google Gemini. The spoken conversation runs on Gemini Live. One further text request reads the saved transcript afterwards, to fill in the name, company, need and language.
• Cloudflare. The bot check, described above.
• PostHog. Only if you agreed to be measured. It receives what the section above lists, on servers in the United States, and nothing you typed into a form.
• Vercel. The site is hosted on Vercel, so every request reaches their servers first.
• Cloudinary. Pictures and video are delivered by Cloudinary, so your browser fetches them from there.

Fonts are served from this domain, not from a font service. No social network, video platform or tag manager is embedded on any page. Nobody else receives your personal data unless a law requires it of us.

How long we keep it

• Voice assistant rows: 90 days. The email, the notes and the transcript of a call are deleted by a job that runs every day and removes anything older than that.
• Form submissions: until you ask. A demo request or an Academy registration stays in the sheet until you ask us to remove it, because it is a conversation we may still be having.
• Your browser: until you close the tab. The one stored email goes with it.

Ask, and we delete either of the first two sooner. You do not have to give a reason.

Your rights, and how to use them

India's Digital Personal Data Protection Act, 2023 gives you rights over the personal data we hold about you. Wherever you are, we answer the same requests the same way.

• Ask what we hold. We will tell you, and send you a copy.
• Correct it. If something is wrong, we fix it.
• Delete it. We take it out of the sheet.
• Withdraw your consent. End a call at any time by tapping the orb, and ask us to delete what it left behind.
• Complain. If our answer does not satisfy you, say so and we will look at it again.

Write to swastik@synqflow.ai. Tell us which form you filled in, or roughly when you called and from which email address, so that we can find the right rows. A person answers, not a ticket queue.

How it is kept

• Every page and every request is served over HTTPS, and browsers are asked to refuse anything else.
• The key behind the voice assistant never reaches your browser. The page is given a single-use token that expires in minutes, with the assistant's instructions locked into it so they cannot be swapped.
• The routes that save a form or start a talk accept requests from our own pages only, and turn away more than a few from the same address in ten minutes.
• Anything you type is stripped of control characters and cut to a length before it is stored.
• The spreadsheet sits in our own Google Workspace, open to the team who reads enquiries and to nobody else.

No system is perfect. If you think you have found a problem with this site, write to us before telling anyone else, and we will fix it.

Not for children

This is a site for people buying software for a company. It is not directed at children, and we do not knowingly collect anything from anyone under 18. If you believe a child has sent us something, write to us and we will delete it.

Changes to this notice

The date at the top is the date this document last changed. When we change it, that date moves. If a change widens what we collect or who receives it, we will say so here plainly rather than quietly.

Who to write to

swastik@synqflow.ai