Privacy policy.

The short version

• Teamtrail runs on your own machine. Your trails, tickets, decisions, code and agents' work stay there, or in the GitHub or Linear tracker you connect. We never receive them.
• If you connect Scout to Slack, messages between Slack and your machine pass through our Scout service. It doesn't store or log their text.
• We don't sell data, show ads, or use anything here to train AI models.

Who we are

The controller of the data described here is GOMOVEO, which makes Teamtrail. Write to kontakt@gomoveo.pl with any question or request about your data.

This website

• Analytics. We use Vercel Web Analytics to count page views and referring sites. It sets no cookies and doesn't build a profile of you.
• The Cloud waitlist. If you join it, we keep your email address in a mailing list hosted by Resend, to email you when Teamtrail Cloud opens. We keep it until then, or until you ask us to remove it.
• Hosting. The site is hosted by Vercel, which processes your IP address and browser details to serve pages and keep them safe from abuse.
• GitHub stars. Your browser asks GitHub's public API for the star count shown in the menu, so GitHub sees that request.

Scout in Slack

Scout is Teamtrail's Slack app. Slack can't reach your machine directly, so it works through the Scout service, which we run on Railway. Your Teamtrail keeps one outbound connection to it.

What the Scout service stores

• For each Slack workspace that installs Scout: its id and name, Scout's bot user id, the permissions Slack granted, who installed it and when, and the bot token Slack issues, encrypted.
• For each person who connects their Teamtrail: their Slack user id and workspace id, a link id, a hash of the link's secret (never the secret itself), and when it was created and last connected.
• To route clicks to the right Teamtrail: the ids of messages and views each link posted or opened (channel, timestamp and view ids, never their content), for up to 30 days; the id of your direct message with Scout, for up to a year; and a thread you used Save as decision on, for 10 minutes.
• While you connect: one-time codes and install states, stored as hashes, for at most 10 minutes.

What passes through without being stored

The questions, answers, digests and approvals Scout posts, your clicks, /scout commands and the threads you save as decisions travel through the service in memory, on their way between Slack and your machine. The service doesn't write their text to its database or its logs. Its logs record what happened (for example, a delivery or a Slack call) with ids, method names and timings only.

How Slack data is used

• Only to deliver Scout's features to the person who connected it.
• Never sold, shared for advertising, or used to train AI models.
• Shared only with the providers that run the service (Railway, for hosting and its database) and with Slack itself.

Keeping and deleting it

• Disconnect in the Lookout (Settings → Slack) deletes your link and the message ids tied to it.
• Uninstalling Scout from a workspace, or revoking its tokens, deletes the workspace's token and every link in it.
• Message and view ids expire on their own within 30 days, the id of your direct message with Scout within a year, and connection codes within minutes.
• To have anything else deleted, write to kontakt@gomoveo.pl.

The Teamtrail software

The teamtrail command and the Lookout run on your machine and don't send us your project data or usage. They talk to the trackers you connect (GitHub, Linear), the guide catalogs you use, and, only if you connect Slack, the Scout service.

Your rights

You can ask us what we hold about you, and ask us to correct, export or delete it. Write to kontakt@gomoveo.pl; we answer within 30 days, usually much sooner. If you're in the EU or UK, you can also complain to your data protection authority.

Changes

When this policy changes, we update it here and change the date at the top. For changes that affect what Scout handles, we also say so in the release notes.