Privacy

What we never receive

Marketplace reports are read in your browser. Invoice lines, buyer names, delivery states, pincodes, order references and product identifiers are processed on your own device and are not transmitted to us. This is a property of how the software is built, not a promise about how we behave.

What we hold

• Your email address, a bcrypt hash of your password, and your name.
• Your business name, your plan, and when it renews.
• The GSTINs you prepare returns for.
• For each return prepared: the period, the taxable and tax totals, how many blockers and warnings there were, how many ledger lines it covered, and which sources produced it.
• Marketplace operator registrations and column mappings you choose to save.
• Messages you send through the contact form.
• Buyer names and their GSTINs, when you confirm a photographed invoice. These are kept so that next month’s invoice to the same customer can be checked against the registration you used last month — which is the only check available on a photographed invoice that the invoice itself cannot provide. They are stored whether or not the document archive below is switched on.
• Your conversations with the assistant, and any support ticket or feedback you send. We read these to answer them.
• Your IP address and browser identification, against sign-ins, sign-in failures, refused requests and administrative access. Kept as a security record, so that an attack on your account is something we can see rather than guess at.
• Payment records: which plan, which cycle, the amount, and the provider’s reference. Card details never reach us — they are entered in Razorpay’s own window and we never see them.

The document archive

Off unless the owner of your business turns it on. While it is on, the invoice-level detail behind each prepared return — invoice numbers, dates, buyer names, amounts and the checksum of the file it came from — is kept as evidence of what was filed. This is the only place invoice-level detail is stored, which is why it is a switch and not a default.

What is sent to Google

There are three cases, and they are different from one another. Nothing else in the product sends anything anywhere.

1. The second opinion on a return. When you explicitly ask for one, a summary is sent to Google’s Gemini API. That summary contains derived totals, HSN codes, your own product titles and the findings our rules produced. It contains no GSTIN, no buyer name, no address, no pincode and no order reference — and the server rebuilds the payload from a fixed list of permitted fields before it goes, so anything else is discarded rather than merely checked for. The application shows you the exact content before sending and sends nothing unless you agree, per return.
2. Reading a photographed invoice. The photograph itself is sent, in full, through our server to Google. It is a picture of a document, so everything on that document goes with it — including the buyer’s name, address and GSTIN. This is the one case where customer detail leaves your browser, which is why you are asked to agree to it once, in writing, before it ever happens, and why the agreement can be withdrawn in Settings at any time.
3. Reading an unfamiliar spreadsheet. A description of the file’s structure — its column headings and a few sample values — is sent so the columns can be identified. The rows themselves are not.

Why we hold it

To run your account, enforce the limits of the plan you chose, and give you a record of what you prepared. We do not sell data, we do not share it with advertisers, and we do not use your returns to train anything.

How long

For as long as your account exists, plus a period afterwards for tax and accounting records that we are ourselves required to keep. Ask us to delete your account and we will remove your personal details and your filing records.

Your rights

You can ask for a copy of what we hold, ask us to correct it, or ask us to delete it. Write to support@fynxiq.com and we will act within thirty days. There is no button for this yet, so it is done by hand by a person — which is worth saying plainly rather than implying an automated process that does not exist. Payment records are kept regardless of a deletion request, because we are required to keep them.

Cookies

One, for your session. It is http-only, same-site, and expires after thirty days. There is no advertising or analytics cookie on this site.

Payments

Card details are handled by our payment provider and never reach our servers. We store the plan you bought, the amount, and the provider’s reference for it.