Gatherd is an issue tracker for people who run several products at once, made by Abyssinia Labs LLC. This page says what it stores about you, where that lives, who else touches it, and how you get it out.
What we store
Your account. You sign in with Google or GitHub. We keep the name, email address and profile picture that account gives us, the link to that account so the next sign-in finds you, and a session so you stay signed in. We keep no token from Google or GitHub, and we never see your password there.
Your workspace. Its products, tickets, comments, labels, groups and links, and who is a member of it with what role. Every change to a ticket is kept as a line of its history — what changed, who changed it and when, with the words before and after when a title or a description changes — because answering “who moved this, and when” is the point of the product.
Invitations. The address a workspace’s owner invites, the role, who invited it and when, and whether its mail went. Whoever signs in with that address joins. An accepted invitation stays as the record of who invited whom; a revoked one is deleted. The mail is sent through ZeptoMail, by Zoho, in the inviter’s name, with replies coming to our support address, and with no click or open tracking.
Your agents. The agents you create, and their API tokens stored hashed with only the first few characters kept so you can tell two apart. A token’s value is shown once, when it is issued, and never again. When you approve an app’s connection instead, such as MCPCloud’s, we record which agent it works as and who approved it, and keep only hashes of the tokens it holds: one for an hour, one to renew it for up to a month. Disconnecting it deletes them.
API calls. When an agent calls /v1, which call it made, what it was answered and when are logged for 30 days, with the name and version of the app it says it is, such as Claude Code, where MCPCloud passes that on. The agents page shows the latest of those beside each token. The key that makes a repeated create idempotent is kept for 24 hours. We also count each agent’s calls today, which a plan’s daily limit is measured against.
Webhooks you add. A workspace can send its ticket changes to a URL it names. We keep that URL, and the secret each delivery is signed with, stored as it is because signing needs it. Each delivery is logged, with the change as it was sent and what the other end answered, for seven days. What arrives at that URL is in the hands of whoever runs it.
What you connect to GitHub. Which installation is bound to your workspace, the account it is installed on, and which repositories are mapped to which products. Pull request events arrive on a webhook; we keep the delivery’s id for seven days so a redelivery is not handled twice. A pull request that names a ticket is kept on it as a link, with its title, number, state and its author’s GitHub username. Open issues you import become tickets. Binding an installation spends a one-time code for a token that proves you can see that installation, and the token is discarded once it has answered.
TakeOne and Antescript. A TakeOne recording or an Antescript page attached to a ticket is read once from its public page for a title, a poster and a length. Where TakeOne is connected to a workspace, it tells us when a take is published, so the take is attached to the ticket its title names; we keep that delivery’s id for seven days.
Files. Images you paste into a ticket, a product’s picture, and the exports you generate, on Cloudflare R2. A picture taken from GitHub is a copy of the public avatar of the account that owns the repository. We store the key, never a signed URL; a URL is signed when you read it and expires. An image uploaded but never filed on a ticket is removed after a day.
Payments. If a workspace pays for a plan, Stripe takes the payment and holds the card details; we never see or store a card number. We keep a copy of what Stripe tells us about the workspace’s customer record, subscription, invoices and payments: the name and email address on the record, the plan, its status, amounts and dates, and the ids Stripe gives them. Stripe’s notices are kept for 30 days so none is handled twice.
Feedback. Notes you send from the Feedback dialog, with your account and, if you chose, the page you sent them from.
In your browser. A session cookie for sign-in, and cookies for your theme, its light or dark scheme, and whether the sidebar is collapsed. If a link you followed to Gatherd was tagged with where it was posted (as in ?ref=hn), a cookie keeps that tag for 30 days and the workspace you create records it, so we can tell which places bring people; it goes nowhere else. Your browser’s own storage keeps which board columns you put away, which billing notice you dismissed, and the last day you opened What’s new. No advertising, no analytics, no tracking pixels.
Where it lives
Your workspace, its tickets and the logs are in Convex. The files, and the app itself, run on Cloudflare. Sign-in is by Google or GitHub, payments are processed by Stripe, and invitations are mailed by ZeptoMail. The app’s fonts are served by Google Fonts, so your browser asks Google for them, which tells Google your IP address.
If you connect an agent through the MCP server, MCPCloud holds its credential for you, a token you pasted or a connection you approved here, and uses it only for the calls you allowed. Approving a connection also signs you in to MCPCloud, so it learns your account’s id, your name and your email address. The GitHub App reads the repositories you installed it on; it has read-only permission to pull requests, issues and metadata, and writes nothing back to GitHub.
Your tickets leave Gatherd only for the places you send them: an agent you connect, a webhook you add, an export you download. Gatherd itself sends them to no AI service, sells none of them, and uses none to train anything.
Who can see your workspace
You; the other members of the workspace, within their roles; any agent you issued a token to, within the products that token is restricted to; and whoever runs a URL a webhook sends to, for what it sends. We look at a workspace only to run the service or when you ask for help.
Keeping and deleting
A ticket, a product or a group is archived rather than deleted, so its history stays answerable. Deleting a comment, a link, a file or a webhook removes it at once. The ticket’s history still says that a link was added and removed, with its address, and a change already sent to a webhook stays in its delivery log until that ages out. The API log and Stripe’s notices are kept for 30 days, idempotency keys for 24 hours, and the webhook delivery log and the ids of GitHub and TakeOne deliveries for seven. Export a whole workspace as JSON or markdown from its settings at any time.
To delete your account and everything in it, use Delete your account on your Account page, or write to the address below from the email you signed in with and we will do it within 30 days. That deletes your account and its sign-in links, and every workspace only you are in, with everything in it, its files and exports, and its Stripe customer, which ends a paid plan at once. A workspace you own that other people use is deleted only if you choose to delete it for them; otherwise you hand it over first. What you wrote in a workspace other people keep stays there as theirs, shown as a former member’s, without your name, address or picture. Stripe keeps its record of past invoices and payments.
Contact
Abyssinia Labs LLC, support@gatherd.dev