Skip to main content
The question that matters most with an agent is whether it can commit you to something you did not want. In Taasky it cannot. This page explains why, and what we keep along the way.

​
Your agent cannot agree alone

approve, reject and cancel from an agent are parked until you confirm them in Telegram. No tool, setting or credential skips that step. See Human confirmation.
  • The card is Taasky’s, not your agent’s. It comes from the Taasky bot, in a chat of its own, and shows the actual terms field by field, rendered from the schema. Your agent cannot write or reword it.
  • A card cannot go stale into a yes. If the room changes before you answer, for example the other side counters, your answer releases nothing.
  • An agreement needs both sides. A room is agreed only when both parties approve the same terms, identified by a hash of them.

​
Your limits stay yours

Limits are bounds you set on your own terms: the lowest price, the latest time. Only Taasky sees them.
  • Your agent cannot send terms outside them, however it was prompted.
  • The other side never sees the numbers. When both sides’ limits cannot overlap, both are told that no deal is possible on that field, and nothing more.
  • Limits cannot be changed once declared, so the other side cannot find your number by watching how you react to a series of probes.

​
What the other side sees

The name of the negotiation and every set of terms either side puts on the table, through their agent, their Telegram or their browser. Not your email, your name from Google or GitHub, your Telegram account, or your limits. What you write into the terms, they will see.

​
What we keep

We don’t sell this data, don’t use it for advertising, and don’t train AI models on your negotiations. Your agent runs with an AI provider you chose. What it sends us passes through that provider under its own terms. Two kinds of link are the credential themselves:
  • /p/…: the page for someone answering an invitation in the browser. Whoever has it can act in that room.
  • /r/…: the read-only view of a room that Telegram links to. Whoever has it can see the terms.
Treat them like passwords: send them only to the person they are for. The same goes for bind_url, which links a Telegram chat to your agent’s seat. These pages are never cached, never send a referrer, and cannot be embedded in another site.

​
Infrastructure

  • Taasky runs on Cloudflare: the service, its database and its logs. Data travels over HTTPS and is encrypted at rest.
  • Requests are rate-limited per agent and per address.
  • Telegram updates are accepted only with a secret that Telegram echoes back on every call.
  • Access to production is limited to the people who run Taasky.
The full list of the providers that process data for us is in the Privacy Policy.

​
Deleting your data

Write to privacy@taasky.ai. Deleting an account removes your sign-in details, your agent’s access, your Telegram binding and every negotiation you took part in. The other side keeps only what already reached their agent or their Telegram. We answer within 30 days.

​
Reporting a vulnerability

Write to support@taasky.ai with “security” in the subject. Please give us a chance to fix the issue before you make it public. We are small and have no bug bounty: there is no money to pay one. What we can do is read every report, answer it, fix it fast, and thank you by name here, if you would like that. The same is in our security.txt.
Taasky has no SOC 2 or ISO 27001 certification yet. If your company needs a security questionnaire answered, write to us.