Computable Privacy Policy
Version 2026-11-02
Last updated: November 4, 2026
1. Who we are and what this policy covers
Trade Hobby Inc, a Delaware corporation doing business as Computable ("Computable", "we", "us"), makes Backchannel, our main product, and two smaller tools, the Price index and the Hedge rate floor tool. This policy explains what information we collect across those products and our website, how we use it, who sees it, how long we keep it and what you can do about it. Most of it is about Backchannel, because Backchannel is the product that reads chats.
It covers the Backchannel web app, the Backchannel Agent in Telegram, WhatsApp, Slack and email, the Backchannel API and MCP connector, and the matching and introduction network. It applies to account holders, to the people they invite to their Team, and to people who do not have an account but whose messages the Agent reads because someone added it to a chat they are in ("Non-Account Participants"). Section 4 is written for that last group.
It also covers the getcomputable.com website and the Price and Hedge tools. For those, we collect only what Section 2 lists under "Sign-up and account", "Web app usage" and "Support and feedback", plus the inputs you type into the tool; Sections 3, 4, 6 and 16 apply to Backchannel only.
Capitalized words (Agent, Board, Team, Intent, Lead, Intro, Connect, Wallet) mean what they mean in the Backchannel Terms of Service.
Our role. For the content on a Team's Board (chat messages, Intents, Leads, attachments), the Team is the controller and we process it on the Team's behalf to run the Service. For account, billing, security, matching and usage data, and for the records we keep about Non-Account Participants, we are the controller. Business customers that need a data processing agreement can request one from us.
2. Information we collect
We collect only what the Service needs to run. Nothing below is collected for advertising, and we do not buy data about you from brokers.
| Source | What we collect | Who it is about |
|---|---|---|
| Sign-up and account | Email address, phone number, company name, Team membership and role, Slack identity if you sign in with Slack, the Terms version you accepted and when | Account holders |
| Chats the Agent is added to | Message text, attachments and images, sender name and Platform handle or number, timestamps, reactions, the list of participants seen; earlier history only if a member chooses to share it | Everyone in the chat, including Non-Account Participants |
| Messages you send the Agent directly | The text you send, the deal terms you confirm, your corrections and board commands | Account holders |
| Connected mailbox (Gmail) | Message bodies, senders, recipients, subject lines and thread details in your Inbox or the one label you choose; images are processed in memory and other attachments are skipped | You and the people you email with |
| Board data | Intents, Leads, deal stages, deadlines, private notes, attachments, who logged what and when | Your Team and the counterparties your Team deals with |
| Matching | Field-by-field scores between Intents, Match scores, Intros sent, Accepts, declines, Connects, estimated deal value | Your Team and the matched Team |
| Wallet and billing | Plan, seats, credit balances and kinds, Holds, charges, invoices, the last four digits and card brand from our payment processor (we never see full card numbers), auto-reload settings | The Team Owner |
| Platform credentials | Tokens and session data needed to read the chats and mailboxes you connect, encrypted at rest | Account holders |
| API and MCP | Keys, calls made, agent authorizations and fee caps | Account holders |
| Reviews | Survey answers and tapped phrases about a counterparty after a Connect | The reviewer and the reviewed Team |
| Web app usage | IP address, browser and device type, pages viewed, actions taken, error logs, session cookies | Account holders |
| Support and feedback | What you write to us and anything you attach | Whoever writes to us |
| Screening | Results of checks against sanctions and export-control lists, run on company names and account holders | Account holders and their companies |
What we do not collect. We do not collect government ID numbers, bank account numbers, health information or biometric data, and you should not put them in a chat the Agent reads. We do not read chats the Agent has not been added to, and we do not read a Telegram folder, WhatsApp group, Slack channel or Gmail label you have not connected.
3. How the Agent reads each Platform
The Agent reads a chat from the moment it is added, plus any earlier history a member chooses to share when adding it. It identifies itself as an automated assistant when it joins. In every chat it does the same four things: records Intents, Leads, deal stages and corrections on the Board of each Team present; adds a check-mark reaction when it logs something; answers only when mentioned, and only about that chat; and never posts a Team's private Board into the chat.
| Platform | What it reads | What it stores | How to stop it |
|---|---|---|---|
| Telegram | Every message in groups where the bot is a member, and the folder you label for it | The latest 500 messages per group (sender, display name at the time, text, time) for as long as the bot is a member; its own replies; derived Board entries | Remove the bot from the group, or unlink Telegram in Settings. Removal deletes the group record in the same transaction |
| WhatsApp groups ("Backchannel Groups") | Every message in groups the shared Backchannel number is added to | The latest 500 messages per group and the participant list, for as long as it is in the group; the WhatsApp connection keeps an encrypted copy of chats on the shared number for up to 7 days | Remove the Backchannel number from the group. Removal deletes the stored messages and participant list |
| WhatsApp direct ("Backchannel DM") | Messages you send it | The deal terms you confirm and a copilot transcript with contact details masked, kept for one hundred eighty days | Unlink WhatsApp in Settings |
| Slack | Messages, senders and thread details in channels the app is invited to | What is needed to provide the Service, including derived Board entries and its own replies | Remove the app from the channel or disconnect Slack on the Copilot page |
| Email (Gmail) | Your Inbox, or one label you choose, starting with the last 7 days, then new mail as it arrives; read-only | Saved messages until you disconnect; Intents and their evidence on your Board until you remove them | Disconnect Gmail on the Copilot page. Disconnecting revokes Google access and deletes saved messages. Your mailbox is untouched |
| Email relay (new@ address) | Messages sent to or copied to the Backchannel address | What is needed to provide the Service | Stop copying the address |
| Web chat | Messages you type to the Agent in the app | A copilot transcript with contact details masked, kept for one hundred eighty days; derived Board entries | Delete the conversation in the app |
| MCP and API | Reads and writes your own Board and Matches on your instruction | Call logs and the actions taken | Revoke the key or authorization in Settings |
What the Agent never does: it does not read other chats to answer a question in this one; it does not bring Board, match, note or DM content into a group answer; it does not reveal who a source is. We also keep copilot transcripts with contact details masked and full model inputs and outputs in Langfuse, as described in Sections 7 and 9.
4. If you do not have an account
If you are reading this because a Backchannel bot appeared in a chat you are in, this section is for you.
What happened. Someone in your chat added the Backchannel Agent. From that moment it reads the messages in that chat, including yours, to keep that person's private deal board up to date. It did this at their request and on their behalf; under our Terms they are responsible for telling you and for getting any consent the law requires, and we provide the technology only.
What we keep about you. Your messages in that chat, in a record limited to the latest 500 messages, for as long as the Agent is in the chat. Your display name and Platform handle or number as they appeared. If you said you want to buy, sell or rent GPU compute, that statement is recorded as a Lead on the board of each Team in the chat, tied to your Platform profile. Leads are that Team's private records; other Teams cannot see them, and no one outside the chat is told who you are.
What we do not do. We do not add you to our matching pool. We do not send you Intros. We do not reveal you to anyone as the source of a Lead. We do not use your messages to train AI models. If you mention the Agent, it will answer with a factual recap of that chat only, with no advice, and it will rate-limit how often it replies to you.
If you sign up later. Leads recorded under your Platform profile can be linked to your new account and become your own Intents, after you confirm.
What you can do. Ask the chat owner to remove the Agent; removal deletes the chat record. Or email support@getcomputable.com from, or with, the Platform handle in question; once we have verified the request we will delete the message record we hold about you within the time the law requires. Leads already on a Team's Board are that Team's records: we will pass your request to the Team, and whether they remove a Lead is their decision. Section 12 describes any further rights you may have where you live.
5. How we use information
| Purpose | What we use | Legal basis (EU/UK) |
|---|---|---|
| Run the Agent: read chats, extract Intents and Leads, keep Boards current, answer mentions | Chat, mailbox and DM content; Board data | Performance of our contract with the Team; the Team's legitimate interest in managing its deals, for Non-Account Participants' messages |
| Match Intents and send Intros | Board data of Teams in the matching pool; Match scores | Contract |
| Estimate deal value and set Match Fees | Intent fields; reference prices; aggregated Board data | Contract |
| Connect two Teams and exchange profiles | Profile and contact details of both sides | Contract (both sides have Accepted) |
| Bill plans, run the Wallet, process payments | Account, plan, billing and payment-processor data | Contract; legal obligation (tax and accounting) |
| Security, fraud prevention, abuse investigation | Usage data, logs, credentials, support records | Legitimate interest in a secure service; legal obligation |
| Sanctions and export-control screening | Names, company names, countries | Legal obligation; legitimate interest in not facilitating prohibited transactions |
| Improve the product, fix bugs, measure use | Usage data; de-identified Board and matching data | Legitimate interest |
| Build reference prices and market statistics | Aggregated, de-identified Intent and match data | Legitimate interest (no individual is identifiable) |
| Service messages (Intros, Hold releases, credit expiry, billing) | Contact details | Contract |
| Product news and marketing | Email address | Legitimate interest for business contacts; consent where required. Opt out any time |
| Reviews | Survey answers after a Connect | Contract; consent to submit |
| Legal claims and compliance | Any of the above as needed | Legal obligation; legitimate interest |
We do not use your information to train generally available AI models, we do not sell it, and we do not use it to serve you advertising.
6. Matching and Intros: who sees what, and when
Matching is done by our software, not by people, and it compares typed fields, never raw chat. On Free, your intents are shared anonymously. With Member, your team chooses what stays private. The Member plan's Sharing Switch is controlled by the Team's Owner. Agent-only and Platform plan Intents are always in the pool. Private notes never enter matching.
| Stage | What the other side sees | What stays hidden |
|---|---|---|
| Match found | Nothing yet | Everything |
| Intro sent | Which categories fit, which need information, a general one-line description, and their own fee | Your values, prices, quantities, source, company and identity |
| Teaser (Agent-only plan, before the Member Accepts) | A reduced version of the Intro | As above |
| You Accept | That one side has Accepted | Who you are |
| Connect (both Accepted) | Your company name, verified email, and phone and Telegram handle if you chose to share them; the Agent's one-line summary of your Intent | Your Board, your other Intents, your Leads, your sources, your private notes |
| After Connect | Whatever you choose to tell them directly | We do not monitor or pass on anything further |
A source is never revealed: if a Lead on your Board came from someone else's message, the counterparty learns that you have a matching Intent, not where it came from. One Team's Board is never shown to another Team, including when both Teams are in the same chat.
Reviews. After a Connect, each side may rate the other. Individual reviews are shown only to the two people connected. If we later show a summary to other users, it will be a broad aggregate shown only once a Team has enough reviews that no single review can be identified.
7. AI providers and other sub-processors
The Agent is built on third-party large language models. To extract Intents, answer mentions, write recaps and score free-text fields, we send the relevant chat, email or Board text to our AI provider(s). We contractually require them not to train on that text or use it for any purpose other than providing services to us. Your text is not used to train our models or theirs.
Langfuse is our subprocessor for recording and reviewing how the Agent works. Its United States cloud stores full model inputs and outputs, including chat text, chat history, sender details and any email addresses or phone numbers in that text, until we delete them. These records help us investigate failures and check the quality of responses. Contact masking in the copilot transcript does not mask these Langfuse records.
We share information with these categories of service providers, each bound to use it only to provide services to us:
- Third-party AI model providers, which receive chat, email and Board text per request
- Langfuse, which stores the full model inputs and outputs described above
- Payment processors and subscription-billing providers, which receive billing details and payment methods
- Cloud hosting and database providers, which hold data at rest, encrypted
- Messaging platforms and email providers (Meta for WhatsApp, Telegram, Slack, Google for Gmail), which carry messages in transit under their own policies; WhatsApp keeps an encrypted chat copy on the shared number for up to 7 days
- Email delivery providers, which send service and marketing email
- Sanctions and export-control screening providers, which receive names and company names
- Error reporting and product analytics providers, which receive usage data and no chat content
We may change service providers from time to time. Business customers can request the current list.
8. When we share information
We share information only in these cases:
- Your Team. Everyone on your Team sees the Team's Board, Intents, Leads and Matches. Only the Owner sees card, auto-reload and refund details.
- Counterparties, on Connect. The profile and contact details in Section 6, and nothing else, after both sides Accept.
- Sub-processors. The providers in Section 7, under contracts that limit them to working for us.
- Other Teams in the same chat. The Agent updates each present Team's own Board from that Team's own side. It does not copy one Team's Board to another; each Team sees only what its own members could already see in the chat.
- Our staff. Authorized staff can access stored chats, Boards and usage data to operate the Service, prevent abuse, investigate reports, handle support and deletion requests and improve the product. They are bound by confidentiality, access only what the task needs, and never use a Team's data to trade or to tip off another Team.
- Legal requests. We disclose information when we believe in good faith the law requires it, including to comply with a subpoena, court order, sanctions or export-control obligation, or a lawful government request. Where the law allows and it is safe to do so, we will tell the affected Team first.
- Protecting people and the Service. To enforce our Terms, investigate fraud or security incidents, collect amounts owed, or protect the rights, property or safety of users, the public or us.
- Business transfers. If Computable is acquired, merges, or sells the Backchannel business or substantially all its assets, information transfers to the successor, who must honour this policy or give you notice of changes.
- With your direction. When you tell the Agent to share something, send Content through MCP or the API, or export data.
- Aggregated or de-identified data. Statistics that do not identify any Team, counterparty or person, such as reference prices and market trends, which we may publish or license.
We do not sell personal information, and we do not share it with advertising networks or data brokers.
9. How long we keep information
| Data | Kept for | Then |
|---|---|---|
| Telegram and WhatsApp group message records | While the Agent is in the chat, capped at the latest 500 messages | Deleted when the Agent is removed |
| Encrypted chat copy on the shared WhatsApp number | Up to 7 days | Deleted |
| Agent replies and recaps in chats | As long as needed for the purposes in Section 5; no fixed period | Deleted |
| Saved Gmail messages | Until you disconnect Gmail | Deleted on disconnect |
| Copilot transcripts from direct messages and web chat, with contact details masked | One hundred eighty days | Deleted by the retention sweep; account revocation also removes them at the next sweep |
| Full model inputs and outputs in Langfuse, including chat text and contact details | Until we delete them; no automatic expiry | Deleted when we delete the records in Langfuse |
| Intents, Leads, Board entries, attachments | Until you remove them or your Team is deleted | Deleted within a commercially reasonable time after Team deletion, except as below |
| Leads about a Non-Account Participant | As above, on the Team's Board | Deleted on verified request under Section 4 where the Team agrees or the law requires |
| Match, Intro, Accept, Connect and fee records | As long as needed for billing, disputes, audit and legal compliance | Deleted or de-identified |
| Wallet, billing, invoices, Stripe records | As long as tax and accounting law requires | Deleted, as tax law allows |
| Account and Team details | While the account exists | Deleted within a commercially reasonable time after Team deletion |
| Platform credentials and tokens | While the connection is active | Revoked and deleted on unlink |
| Screening results | As long as sanctions and export-control recordkeeping rules require | Deleted |
| Usage logs and error logs | A limited period for security and debugging | Deleted or de-identified |
| Support correspondence | As long as needed to resolve the issue and for a reasonable period after | Deleted |
| Reviews | While both Teams exist | Deleted or de-identified when either Team is deleted |
| Aggregated, de-identified data | Indefinitely | Kept; it identifies no one |
| Backups | A limited rolling period | Cycle out |
Where this table gives criteria rather than a fixed period, we keep information no longer than needed for the purpose and review retention periodically. If a legal hold, dispute or investigation requires it, we keep the affected records until it ends. We may retain backup copies of removed or deleted information for a limited time and use them only for the purposes in this policy.
10. Security
We protect information with measures appropriate to its sensitivity: encryption in transit and at rest, encrypted storage of Platform credentials and tokens separate from the web app, access controls that give staff only what their task needs, audit logs on database access and founder-only actions, database privileges that keep raw chat records readable only through narrow service functions, and automated monitoring for abuse. Payment card data never touches our servers; Stripe handles it.
No system is perfectly secure. If we learn of a breach that affects your personal information, we will notify you, and any regulator the law requires, without undue delay and within the time the law sets. Teams under a DPA get the notice timing in the DPA.
You are responsible for your own devices, your Platform accounts and your sign-in email: anyone who can read your sign-in code can sign in as you.
11. Your controls
| You want to | Do this |
|---|---|
| Stop the Agent reading a chat | Remove it from the group or channel. The stored message record for that chat is deleted |
| Stop a whole Platform | Unlink Telegram or WhatsApp in Settings; disconnect Slack or Gmail on the Copilot page. Tokens are revoked |
| Keep your Intents out of matching | On the Member plan, make an Intent private or have the Owner turn the Sharing Switch off. Free, Agent-only and Platform plans keep sharing on |
| Keep something out of matching entirely | Mark it as a private note |
| Correct a wrong Intent, stage or Lead | Edit it on the Board, or tell the Agent in a DM |
| Undo a wrong "closed" | Tap undo in the DM the Agent sends |
| Remove a Lead or Intent | Delete it on the Board |
| Stop marketing email | Unsubscribe link in any marketing email, or Settings. Service messages (Intros, Hold releases, credit-expiry warnings, billing) continue while you have an account |
| Export your Board | Use the export option in the app where available, or email us |
| Delete your account or Team | Use the delete option in the app where available, or email support@getcomputable.com. See Section 9 for what we keep afterwards |
| Ask about or object to an automated match decision | Email us. We can explain which fields matched or did not, without revealing the other Team's data, and a person will review any decision to restrict your account |
12. Your rights
Depending on where you live, you may have the right to access the personal information we hold about you, receive a copy in a portable format, correct it, delete it, restrict or object to how we use it, withdraw consent where we rely on it, and not be discriminated against for exercising these rights. These rights apply whether or not you have an account.
How to exercise them. Email support@getcomputable.com or use the controls in Section 11. We will verify that you are who you say you are, usually by replying to the email or Platform handle on record, and respond within the time applicable law allows. You can authorize someone to act for you; we will ask for proof. We do not charge for requests unless they are repetitive or excessive.
Limits. Content on a Team's Board belongs to that Team. If you ask us to delete something a Team recorded, we will pass the request to the Team where we act as its processor, delete what we hold as controller, and tell you the outcome. We may keep information where we have a legal obligation or a legal claim to defend; Section 9 lists those cases.
EU and UK. Our legal bases are in Section 5. If you are in the EU or UK you may also complain to the data protection authority where you live.
California. In the last 12 months we have collected the categories in Section 2 (identifiers, commercial information, internet activity, professional information, inferences used for matching) from the sources in Section 2, for the purposes in Section 5, and disclosed them for business purposes to the recipients in Section 8. We do not sell personal information and do not share it for cross-context behavioral advertising, so there is nothing to opt out of; we do not use or disclose sensitive personal information for purposes other than running the Service. California residents can also ask what personal information we disclosed to third parties for their direct marketing purposes; the answer is none.
Other US states. Residents of Colorado, Connecticut, Virginia, Texas, Oregon and other states with privacy laws have similar rights, including to appeal a decision we make on a request by replying to our response; we will answer the appeal within the time that state's law sets.
Non-Account Participants have the same rights and can use the same address; Section 4 explains what we can and cannot do about Leads held by a Team.
13. International transfers
We are based in the United States and store and process information there. By using Backchannel you consent to your information being transferred to, processed and stored in the United States. If you are in the EU, UK or Switzerland, that is a transfer outside your region. Where the law requires a transfer mechanism, we use the Standard Contractual Clauses approved by the European Commission, with the UK Addendum where applicable. Our service providers may process information in the United States and other countries.
14. Children
Backchannel is for business use by adults. We do not knowingly collect information from anyone under 18, and the Agent is not meant for chats that include minors. If you believe a minor's information has reached us, email support@getcomputable.com and we will delete it.
15. Cookies and tracking
The web app uses cookies and similar technologies to keep you signed in, remember your settings, and understand how the app is used and where it fails, including through third-party analytics and error-reporting tools. We do not use advertising cookies or cross-site tracking, and we do not share contact details with advertising platforms to build audiences. We honour Global Privacy Control signals where the law gives them effect, which in practice changes nothing, because we do not sell or share data for advertising.
16. Google API Services disclosure
Backchannel's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: we use Gmail data only to keep your Board current and answer you; we do not use it for advertising; no human reads it except for security, abuse, support you asked for, or where the law requires; and we do not sell it or transfer it to anyone except our sub-processors in Section 7 as needed to provide the Service. Gmail access is read-only and we never send, delete, label or change your mail.
17. Changes and contact
We will post changes here with a new version date. If a change materially reduces your rights or expands what we collect or share, we will give you reasonable advance notice by email or in the app, and where the law requires it we will ask for consent again. Earlier versions are available on request.
Questions, requests and complaints: support@getcomputable.com.