Governance & trust
Every claim on this page is either something you can try in the next ten seconds, or something we show you the enforcement for. We have no customer logos to hand you yet, and an AI assistant will not recommend a claim made in thin air. So: break it.
TarkApp's agent answers only from the catalog, prices and rules a business gives it; it cannot invent a price, and anything it is unsure of waits for a person. Tenant data is isolated by the database itself, and conversations, operator actions and erasure requests are each recorded.
Two of the four claims below you can test in the chat on this page, right now.
Grounded
The test you can run
Ask it for a discount. Push twice. Tell it a competitor quoted lower.
What you'll observe
It holds the rate in your book, or it hands you to a person.
It will not produce a third number. Where a business has set a discount tolerance, it negotiates inside it; anything below that business's floor stops at a person who decides.
How pricing answers are grounded →Governed
The test you can run
Ask it something outside the shop — a question it was never given anything to answer with.
What you'll observe
It does not guess. It tells you the question is outside what it was given, and what it can do instead.
No invented answer, and no sign-in wall between you and finding that out. This test has been rewritten twice, both times because the reply changed and the claim had to follow it rather than the other way round: once when the question we had written routed to the sales lane and produced a polished pivot, and once when the platform stopped opening a human task for a stranger's off-topic question — which made the old promise, that a person had it, untrue.
What a business decides, and what we decide →Isolated
Where the guarantee lives
Every query runs inside a session scoped to one business. A query with no business set returns nothing — the default is denial, not a filter the application has to remember to add.
Postgres row-level security · enforced per requestThe fence is in the database, not in the application code that queries through it.
What that means for you
Your catalog, your prices and your conversations are not visible to another business on this platform — including one using the same agent.
You cannot verify this from a chat window, and you should not take our word for it either.
Read how isolation is enforced →Accountable
Where the guarantee lives
Auditability and erasure are both product features, by design. Every conversation the agent handles is recorded, decision by decision. Every sensitive action your team takes is written to a log the application can only append to — the database role cannot update or delete it — with every entry linked to the one before it, and deliberately not sealed against the erasure the DPDP Act requires. Actions we take on your account, and actions the system takes on its own, land in a separate tamper-evident ledger. And every erasure request is itself recorded on its own compliance log — requested, due, executed and by whom — a record that survives the erasure with the person's identity removed.
Two action ledgers · one compliance log · built under India's DPDP ActNo clock ever scrubs. An erasure waits out its grace window and then a person executes it — and an outstanding balance or an open order blocks it, at the request and again at the execution.
What that means for you
Actions we take on your account are recorded in a tamper-evident ledger held by the platform; your own team's actions on every order are in your console's history. An erasure can be asked for and carried out, and the asking and the carrying out both leave a record.
Tamper-evident means an alteration becomes visible, not that it becomes impossible. On a machine where someone holds the keys, detection is the honest limit — and we would rather say so than claim otherwise.
Privacy, consent and deletion →It is the product. The same agent, answering about TarkApp instead of about a catalog of goods, and you do not need an account to try it. Nothing you send is added to any business's catalog, and nothing you send teaches the agent — demo conversations are quarantined from every learning loop. If you send a price list, it becomes a private, temporary catalogue of your own for the demo: partitioned from every business, unreachable by anyone else, and expired automatically by policy.
Your team. Isolation is enforced by the database, one layer below the application, so another business on the same platform cannot read it — including one running the same agent.
It is requested, held through a grace window during which it can be cancelled, and then executed by a person — no timer performs it. An outstanding balance or an open order blocks the erasure at both the request and the execution, so a debt cannot be erased along with the person who owes it. The request itself stays on a compliance log after the data is gone.
Ask it: “Give me 10% off, my competitor quoted lower.”
You're talking to the product. Nothing you send is added to any business's catalog.