Privacy Policy

Last updated: 7 October 2026

Who we are

Tre (tre-app.com) is operated by Teralabs LLC, 1111B S Governors Ave, STE 52993, Dover, DE 19904, USA. Teralabs LLC is the data controller for the personal data described here. Contact: support@tre-app.com.

What we collect

Account data. When you sign in with Google we receive and store your name, email address and avatar image. Google sign-in is the only authentication method; we never see or store a password.

Content. Everything you or your AI agents create in Tre — workspaces, boards, lists, cards, checklists, comments, and card description history — is stored so we can provide the service. Content belongs to the workspace it was created in.

Activity. Tre keeps a log of what changes in a workspace: who did it, on which board and card, and through which surface — the app, the REST API or MCP — including the name of the API token an agent used. Entries carry short extracts of what changed, never whole documents. It is what lets a person or an agent catch up on what happened while they were away, and each entry is readable by the members who can already read that board. Entries are kept no longer than 90 days of activity, or the most recent 10,000 entries per workspace, whichever comes first. Cleanup runs as the workspace is written to, not on a timer and not on every write, so entries in a quiet workspace can outlive that window — and a workspace that stops being written to altogether keeps them until the workspace itself is deleted.

Billing data. If a workspace subscribes to a paid plan, payment is processed by Stripe. We store the subscription state and Stripe’s identifiers for it; your card details go to Stripe directly and never reach our servers.

Technical data. Server logs and error reports may include your IP address, user-agent and request identifiers. We use them to operate, secure and debug the service — not for advertising. Tre uses no advertising or analytics trackers.

Administrative access. To run the service, answer you and keep it secure, the person who operates Tre at Teralabs can see account and billing metadata: your name and email address; the workspaces you belong to, your role in each and who else belongs to them; each workspace’s name, plan, trial and subscription state, how many boards, people and pending invitations it has, how many entries its activity log holds and when it was last written to; for API tokens, their prefix, scope, workspace and dates; for connected apps, the name and address of the app and its dates; and whether you have a session open. From that view the operator cannot see board names, cards, comments, checklists, description history, token names or the content of the activity log, and Tre has no feature that lets staff sign in as you. If you want help that needs someone to read a board, you invite an address of ours into your workspace and remove it when you are done. Actions an operator takes on an account or a workspace, from the console or with Tre’s own command-line tools — revoking a leaked token, signing an account out of its browsers, closing an account at its holder’s request — are recorded: which action, when, by which operator or tool, a reason category and a ticket reference, with the identifiers of the account, workspace or credential concerned and never the content involved. Those records are kept for twelve months — older entries are removed the next time an action is recorded — and you can ask us for the entries about you.

Access requests. If you ask for access to the beta we store the email address, the agents you say you use and your note, in order to answer you. Requests are deleted when the beta ends, together with any working note we kept of them in our own workspace, which then follows the trash rule described under “How long we keep it”.

Cookies. Tre sets only cookies that are strictly necessary to run the service: your session, and small preferences such as your last-used workspace and theme. There is no tracking or marketing cookie, which is why there is no cookie banner.

Why we process it (legal bases)

We process account data and content to perform our contract with you (GDPR art. 6(1)(b)); a request for access to the beta is processed to take steps at your request before a contract (art. 6(1)(b)); technical logs and abuse prevention rest on our legitimate interest in running a secure service (art. 6(1)(f)); billing records are kept to meet legal obligations (art. 6(1)(c)); administrative access to account and billing metadata rests on the contract (art. 6(1)(b)) and on our legitimate interest in running a secure service (art. 6(1)(f)).

Where your data lives

The application and its database run in the United States (Virginia). Every subprocessor below is a US company or operates a global network, so personal data of users in the EU/EEA is transferred outside it. For those transfers we rely on the Standard Contractual Clauses together with a transfer impact assessment; where a subprocessor is also certified under the EU–US Data Privacy Framework, that certification is an additional layer rather than the one we depend on.

Subprocessors

ProviderPurposeNotes
Vercel Inc. (US)Application hosting and servingFunctions pinned to US East (Virginia)
Neon Inc. (US)Postgres database hostingUS East (Virginia)
Cloudflare Inc. (US)Realtime relay (live board updates)Global edge network
Upstash Inc. (US)Rate-limit counters and retry-dedup keysTransient request metadata only
Functional Software Inc. (Sentry) (US)Error monitoring and performance tracingError diagnostics
Stripe Inc. (US)Subscription billing and paymentsCard data never reaches Tre

How long we keep it

Your data is kept for as long as your account or workspace exists. Deleting a workspace deletes it and everything in it immediately and permanently. Deleting your account does the same for your own data — what that covers is set out under “Your rights” below — and for any workspace you are the only member of; it is refused while you are the only owner of a workspace other people still use, until you transfer or delete that workspace. Deleting a list, a checklist item, a subtask or a comment deletes it immediately and permanently too. Cards and boards are the two exceptions.

Cards go to a trash. Deleting a card moves it to its board’s trash, and deleting a list moves the list’s cards there. A card in the trash keeps everything on it — checklist, subtasks, comments and description history — and an editor of the board can restore it for at least 30 days. A card that has been in the trash for more than 30 days is deleted for good, with everything on it, the next time someone on that board deletes or restores a card or deletes a list. That cleanup runs on those actions, not on a timer, so on a board where none of them happens again an expired card stays in the trash until the workspace itself is deleted.

Boards are archived. Deleting a board archives it — the board leaves the listings and its rows are kept, so its content is deleted only when the workspace is.

What the activity log keeps. The activity log described above keeps a bounded trace of what was deleted — a trashed card’s key, title and the list it was in, a deleted list’s title and how many cards it sent to the trash, the text of a deleted checklist item or subtask, and the capped extracts of earlier edits — for no longer than 90 days of activity, or the most recent 10,000 entries per workspace, whichever comes first, pruned as the workspace is used.

Our database host also keeps a rolling history of the database, so that we can recover from a failure or a mistake: up to 7 days of it. Data you delete stays in that history until the window has passed, and is gone from it afterwards. Invoices and billing records are retained as long as tax law requires.

Your rights

Under the GDPR you can ask for access, rectification, erasure, restriction, portability, and to object to processing based on legitimate interest. Two of these are built into the product: from Settings → Account you can export your data as JSON and delete your account entirely (workspace owners can likewise rename, transfer or delete a workspace from its settings page). For anything else, write to support@tre-app.com. You also have the right to lodge a complaint with your local supervisory authority.

Note on shared content: deleting your account removes your profile, sessions, API tokens and comments, and detaches your name from cards you created. Cards and checklist items themselves belong to the workspace and remain there, no longer associated with you. Your comments are deleted, but the short extracts of them (up to 280 characters) already recorded in the activity log stay in other members’ feeds for no longer than 90 days of activity, or the most recent 10,000 entries per workspace, whichever comes first, pruned as the workspace is used — shown as the work of a former member. That severs the account link: entries point to no profile of yours. It does not erase your name everywhere in the ledger, though. The name you gave an API token is kept as written on the events that token produced, and a name or email recorded inside a past board-membership event you were part of — someone added you to a board, changed your role on it, or removed you from it — remains part of other members’ activity records.

Changes

If this policy changes materially we will update this page and its date. Continued use of the service after a change means the updated policy applies.

See also the Terms of Service.