Legal & data protection

How this platform handles your data, who to contact about it, and how long records are kept.

Policies

Terms of ServiceNot published yet
The contract between the customer and the platform.
Privacy PolicyNot published yet
How personal data is collected, used, retained and erased — and who to contact about it.
Data Processing AgreementNot published yet
Required by essentially every enterprise buyer's vendor onboarding before a first subscription.
Subprocessor listNot published yet
Every third party that processes customer data. Changes when LLM_PROVIDER changes.
Cookie noticeNot published yet
The session cookie is strictly necessary; anything added beyond it needs disclosure.

None of these documents is published yet. They are drafted with counsel, not generated — this page deliberately shows the gap rather than filling it with text no lawyer has read.

Contact about your data

No grievance officer is designated yet. India's DPDP Act 2023 reaches extraterritorially and requires a named contact with published details for data subjects. Until one is designated there is no route here — rather than an address that reaches nobody.

Your rights, and what we can do today

Stated as it is, not as it should be. A contact who cannot act on a request is worse than no contact.

AccessPartial
An ORGANIZATION can export its own governance records (docs/119, /api/organizations/export). There is no per-INDIVIDUAL export, so an individual's request is served today by an operator running the org export and extracting their records by hand.
CorrectionPartial
Profile and company fields are editable in the product. Records already frozen into an issued PO, invoice or customs filing are immutable by design and are corrected by amendment, not by edit.
ErasureNot implemented
NOT IMPLEMENTED. There is no deletion path in the codebase — a request can be received and acknowledged but not executed, and the retention schedule above shows several record classes could not be fully erased even once one exists. This is the single largest gap behind the grievance-officer designation.
Grievance / complaintPartial
Routed to the designated grievance officer when one is configured. With none configured there is no route at all, and the surface says so instead of implying one.

How long records are kept

This schedule is an engineering proposal derived from public obligations. It has NOT been reviewed by counsel and must not be published as policy until it has. The customs-vs-erasure tension in particular is a legal determination, not an implementation choice.

Record type	Minimum retention	Overrides an erasure request?
Customs and import records Legal obligation (US import recordkeeping).	5 years from entry	YES — US customs recordkeeping obligations run to five years from the date of entry. An erasure request cannot remove an import record inside that window; the response must say so rather than silently declining.
Financial and settlement records Legal obligation (tax/audit), and contract performance.	As required by the customer's own tax and audit obligations	YES — deleting a settlement record breaks the customer's own audit trail, not only ours.
Governance and audit trail Legitimate interest (security, dispute resolution, ISO 42001 / SOX evidence).	Life of the customer relationship, plus the audit window	PARTIAL — the EVENT must survive (an audit trail with holes is not an audit trail), but the actor's identifying fields can be pseudonymised without destroying the record's evidential value.
Supplier prospect and verification evidence Consent / legitimate interest in supplier due diligence.	No statutory minimum	NO — a prospect who was never onboarded, or a supplier who has left, can be erased. This is the clearest erasable class and the one a DPDP request is most likely to concern.
Messages and clarifications Contract performance.	Life of the cycle, plus the dispute window	PARTIAL — commercial correspondence about a live or disputed deal is evidence; content on a closed, undisputed cycle is erasable.
Accounts and memberships Contract performance.	No statutory minimum	NO — a departed user's account is erasable once their actions are pseudonymised in the audit trail above.