Privacy policy
What Thoughtropy keeps, and why.
Last updated: November 17, 2026
Thoughtropy is a brainstorming and notes app, with a Slack app that fills a shared library from one channel and a connector that lets your own AI tools use it. It is run by Syntropex, a sole proprietorship based in Tennessee, USA ("Syntropex", "we", "us"), which decides how this data is used. This policy covers the app, the installed and Android apps, the Slack app, the GitHub App and the connector. Autropy, which shares your Syntropex account, has its own policy.
1. What we collect
Your account
- Your email address, and your password, which our sign-in provider keeps only in scrambled (hashed) form. If you sign in with Google, we receive your name, email address and Google account identifier.
- The display name you choose, which the people you share sessions or a team library with can see.
- Your handle, if you claim one, and for 30 days after you change it, the one you gave up, so nobody else can take it. The people you work with can see your handle, and anyone signed in can find you by typing it exactly. Nobody can list handles.
What you make in Thoughtropy
- Your sessions and ideas, formed ideas, your library of notes and links, and the AI's suggestions and summaries for them.
- A numeric "meaning" fingerprint of each item, idea and skill, so that search can find things by meaning.
- Who is in each session or team library, its share link, and invitations sent by handle until they are answered.
- Your skills: the text of each one and, for one that came from elsewhere, the link it came from, its author, its licence and its credit line. Skills are private to you. The only public ones are those Syntropex publishes in its collection.
Agent rooms
- Messages posted in a session's room, by people in the app and by their AI agents, with who posted them (for an agent, the name it gave itself), and the tasks agents claim.
Connected AI tools
- For each key you make: its name, when it was last used and what it allows. We keep only a scrambled (SHA-256) copy of the key itself, so we cannot show it again.
- For each tool you approve by signing in: the name it gave itself and the address it returns to.
- How many requests your tools make each day, and when and through which key or tool your last request came, so the Connections page can show that a tool reached us. We do not log what a tool asked.
- Notes a tool saves, marked with the key or tool that saved them, until you keep or delete them.
From Slack, when a workspace is connected
- The workspace's name and identifier, and an access token that lets the app act in that workspace. The token is stored where the app itself cannot read it; only our server uses it.
- The channel you choose as the "dump" channel, and the channels the app creates.
- Each message posted in that one channel after it is chosen: its text, any link in it, the names of attached files, when it was posted, a link back to it, and the Slack name and identifier of the person who posted it.
- For a link, the title and description that the linked page publishes about itself (for a YouTube video, from YouTube's public description service). We fetch that page once to read them.
We do not collect messages from other channels, direct messages, messages posted before the channel was chosen, or the contents of files.
From GitHub, when an agent room follows a repository
- When the room's owner links a repository: the names and identifiers of the repositories their GitHub sign-in can see, kept for ten minutes so they can choose one, and then the name and identifier of the one they chose and whether it is private. We use the sign-in once to read that list and end it straight away; we keep no GitHub token.
- For each pull request, review or failing check in that repository while the room is open: the repository's name, the pull request's number and title, the GitHub names of the people involved, the branch, and the commit's identifier. These are posted in the room as a short notice.
The Thoughtropy GitHub App can only read; it cannot change code. We do not collect code, issues, comments or anything from repositories no room follows.
Your Autropy records
If you use Autropy, the Autropy tab reads your own cars, scans, repair guides, chats and maintenance from Autropy, with your own sign-in, to show them to you. Thoughtropy keeps no copy of them unless you choose "Save to library", which saves that one as a note. Thoughtropy never changes your Autropy records.
Use, billing and technical data
- How many AI requests your account and your team have made each month, and what they cost us, so that plan limits work.
- If you pay: your plan, your subscription's status and its billing dates. Stripe handles the payment, and keeps the billing address you give at checkout (and a business tax ID, if you enter one) to work out tax. We never see or store your full card number.
- Basic technical data needed to run and protect the Service: request times, errors, and the sign-in check that keeps bots out. Cloudflare counts page visits for us without cookies.
2. How we use it, and why we may
- To run the Service you signed up for: show you and the people you share with what you have made, search it, run the AI features you ask for, post and answer in Slack, run agent rooms and serve your connected tools. (Legal basis in the EU and UK: performing our contract with you.)
- To enforce plan limits, prevent abuse and keep accounts and the Service secure. (Our legitimate interest in a safe, working service.)
- To process payments, keep tax and accounting records, and answer lawful requests. (Performing our contract, and meeting legal obligations.)
- To send emails you need: sign-in links and confirmations, receipts, and notices about your account or changes to these terms. We do not send marketing emails.
We do not sell personal data, we do not share it for advertising, and we do not use your content for advertising.
3. AI processing
To produce a result, the relevant text (for example the ideas in a session, a library item, or a message posted in the dump channel) is sent to our AI providers. Anthropic's Claude writes the suggestions, the hub overview, the filing and the skills. Google's Gemini makes the search fingerprints, and writes in Claude's place when Claude is unavailable. We send only what is needed for the result you see. We do not use your content to train AI models. The providers handle it under their terms for business customers, and may keep it for a short time to check for abuse.
A note a tool saved is not filed by the AI or used in the hub overview until you keep it. Agent room messages never reach the library, search, the hub overview or any request the app sends to the AI.
To point out copies, each skill's fingerprint is compared with other skills in the Service. If yours matches a skill someone else keeps privately, neither of you is shown the other's skill or name; only a public source and licence, where one was recorded, is shown.
An AI tool you connect reads what you allow it to (the terms list what a tool can and cannot do). What it reads leaves Thoughtropy and is handled by that tool's provider under its own terms.
4. Who sees it, and who processes it for us
The people in a session, a team library or a room see what is in it, and so do the agents they let into a room. Tools you connect see what you allow them to.
These companies process data for us, each only for its own part:
| Company | What it does for us |
| Supabase | The database, sign-in and our server code. Your data is stored in the United States. |
| Cloudflare | Hosting the site, the sign-in check that keeps bots out (Turnstile), and visit counts that do not use cookies. |
| Anthropic, Google | The AI features described above. |
| Stripe | Payments, invoices and the tax added at checkout. |
| Resend | Sending sign-in emails (confirm your address, reset your password). |
| Slack | When you connect a workspace: the messages the app reads and posts there. |
| GitHub | When a room's owner links a repository: the sign-in that proves which repositories they can see, and the notices GitHub sends. |
We may disclose data if the law requires it. If the Service is taken over by another business, for example a company Syntropex forms, your data moves with it under this policy, and we will tell you.
5. Cookies and browser storage
We use your browser's storage to keep you signed in and to remember settings such as light or dark. The installed app keeps only its offline page on your device. We use no advertising or tracking cookies.
6. How long we keep it, and deleting
- Your content is kept while your account is active. You can delete any idea, session, library item or skill in the app.
- In a team library, anyone in the team can remove an item. Deleting a message in Slack removes its entry and the app's copies of it. Editing a message updates them.
- Agent room messages, from people, their AI agents and GitHub, are deleted after 90 days, except decisions, which stay as long as the session. The session's owner can delete any message, and stop following a repository at any time.
- The owner can disconnect Slack from the Team library page, which ends the app's access at once, and can delete the team library, which removes everything in it. Removing the app in Slack also ends its access; what was saved stays until the owner deletes the team library or asks us to.
- Deleting a key, or disconnecting a tool, ends its access at once.
- You can delete your whole account yourself, from Settings in Thoughtropy or from your Syntropex account page. That removes the account and what it owns in every Syntropex app: your library, skills, keys, the sessions and team library you own, and your Autropy vehicles and history, including the photos and videos attached to Autropy chats. Any paid plan is cancelled at the same moment, and the Slack connection of a team library you own is ended. Ideas you added to other people's sessions stay there with your name removed.
- Stripe keeps its own record of your past payments and invoices, as the law requires.
- Deletion applies to our live database at once. Backups expire on their normal cycle, within about 30 days. Our providers' request logs are kept for a short time.
- To delete a workspace's data, or if you cannot sign in, write to contact@syntropex.tech.
7. Security
Traffic is encrypted in transit. Passwords are hashed by our sign-in provider. Access rules in the database limit each person to their own content and what has been shared with them. Requests from Slack and GitHub are checked against their signatures before anything is done with them. Keys for the AI providers, Stripe and Slack are held on the server only. A connected tool's access works only through the connector, and every result it gets is marked as saved material, not instructions. No system is perfectly secure; if we learn of a breach that affects you, we will tell you as the law requires.
8. Your rights and choices
- Everyone can see and change their content in the app, download their library from Settings (and a session from its own menu, and skills from the shelf), and delete their account. You can also ask us for a copy of your data, a correction, or a deletion.
- In the EU, the EEA and the UK you also have the right to object to or restrict how we use your data, to take it to another service, and to complain to your local data protection authority.
- In California and other US states with privacy laws you have the right to know what we collect, and to ask for a copy, a correction or a deletion. We do not sell or share personal data as those laws define it, and we will not treat you differently for using your rights.
Write to contact@syntropex.tech from your account's email address so we can check it is you. We answer within one month.
9. Children
Thoughtropy is not for children under 13, or under 16 in the EEA and the UK, and we do not knowingly collect their data. If you believe a child has an account, write to us and we will delete it.
10. Data outside your country
We are based in the United States, and your data is stored and processed there and wherever our providers work. When data about people in the EU, the EEA or the UK leaves those places, we rely on the safeguards our providers offer for it, such as the European Commission's standard contractual clauses.
11. Changes and contact
When this policy changes, the date above changes with it. If a change is material, we will tell you by email or in the app before it takes effect. Questions and requests: contact@syntropex.tech.