Legal
Privacy Policy
Untangl is a workspace that connects the tools you already use — email, calendar, chat, code and issue trackers — so you can ask questions across them, track the commitments you make, plan your day and automate routine work. This policy explains what information Untangl handles, why, who else processes it, how long it is kept and what you can do about it.
It covers the website at untanglapp.com, the Untangl web app and the Untangl desktop app for macOS (together, the "Service"). It is operated by Untangl ("Untangl", "we", "us").
The short version
- Untangl reads the tools you connect live, under the permission you granted, when a feature you use needs them. We do not keep a mirrored copy or search index of your mailbox, calendar, files or repositories.
- We do store what is Untangl's own: your account, tasks and commitments, concepts, automations and their results, meeting transcripts, your conversations with Untangl and the work profile it learns — which can include short excerpts of, and links to, items from your connected tools.
- We do not sell your information, use it for advertising, or use it to train AI models. Google user data is handled under Google's Limited Use rules (section 5).
- You can disconnect any tool at any time, and delete your account yourself in Settings → Danger zone.
- Untangl is in beta. If the beta ends, we will tell you first and help you get a copy of your data or delete it (section 15).
1. Information we handle
Account information
When you sign in with Google we receive your name, email address and profile picture. When you sign in with your email address, we send you a sign-in email (through Resend) with a one-time link and a 6-digit code; both work once and expire after 15 minutes, and we store the code only as a keyed hash. If you join a team, we keep the team, your role in it and the invitations sent to or by you.
Beta places and the waitlist
Untangl is in beta and places are limited. If none are free when you sign up, we put the email address you used on our waitlist, with any note you add, and email you when a place opens. When we let you in, that record is what allows your address to sign in, so we keep it until you ask us to delete it. The approval link our team uses to let you in works for 30 days.
If you ask on our website to hear when Untangl for Windows is out, we keep the email address you give only to send that notice, and remove it when you ask.
Content you create in Untangl
Tasks, subtasks, reminders and commitments; concepts and their cards; automations ("Actions"), their schedules and each run's output; your conversations with Untangl; notes, labels and settings; files you upload or that a feature generates; and the work profile — a written summary of your role, preferences, collaborators and recurring work that Untangl keeps so you do not have to repeat yourself. You can read and edit your work profile in the app. Feedback you send from the app is kept too, with a picture of the Untangl window if you choose to include one.
Usage and technical information
Which features you use, errors, performance timings, device and browser type, and how many AI tokens and beta credits each feature used (so we can meter usage and control cost). These events are linked to your account identifier. In production, what we send to our analytics provider is usage numbers and internal identifiers, with your analytics profile labelled by your sign-in email address and name: not error messages or stack traces, and not the text of your AI requests, answers or connected-tool content. Content is sent only from our own development environments, and anything not marked as one is treated as production. The apps do not use automatic click capture or session recording.
IP address. Your IP address reaches our servers with every request. We use it to limit how often requests can be made and to protect sign-in; our limits keep a one-way hash of it, not the address itself. Our hosting and network providers also see it (section 7).
Sign-in sessions. For each session we keep when it started and was last used, which app it came from (desktop or web) and your browser's or app's user-agent string, so you can recognise your sessions in Settings and sign them out.
Cookies and local storage
The web app keeps your sign-in token in your browser's local storage; the desktop app keeps it in the macOS Keychain. Both apps keep interface preferences, your selected team, meeting reminders and some unsent work (such as a note in progress) in local storage. What the app reads from your connected tools is held in memory for up to 1 hour so pages open quickly; it is never written to disk, and it is cleared when you sign out or disconnect that tool.
Untangl sets no cookies of its own. Our analytics provider (PostHog) stores an identifier in a cookie and local storage so events can be attributed to your account, and Cloudflare, which sits in front of our sites, can set its own security cookies. We do not use advertising cookies or trackers. Clearing local storage signs you out of the web app and can remove unsent notes.
2. Your connected tools
When you connect a tool, its provider shows you a consent screen and issues Untangl an access token limited to the permissions you approve. Untangl uses that token to read (and, where you have allowed it, write to) the tool on your behalf, only for the features described below. Connecting any tool is optional.
| Tool | What Untangl reads | What Untangl can change |
|---|---|---|
| Gmail | Messages and threads, to answer your questions, find commitments, prepare briefs and notice replies you are waiting on | Creates drafts, sends drafts you approve, and changes messages (such as starring) within the capabilities you authorize |
| Google Calendar | Your calendars and events, attendees and meeting links | Creates or updates events on your primary calendar when you ask (each can be undone) |
| Google Drive, Docs, Sheets, Slides | Files you ask about or that a feature needs, including document text, spreadsheet cells and slide text | Where you have granted edit access, applies a change Untangl has shown you only when you press Apply |
| Outlook / Microsoft 365 | Mail, calendar, To Do and Planner tasks; OneDrive and SharePoint files only if you separately grant them | Mail drafts, calendar events and tasks, when you ask |
| Slack | Messages in the conversations your grant covers | Posts the results of Actions to the channel or direct message you choose |
| GitHub | Repositories, pull requests, issues, reviews and commits you grant | Nothing |
| Linear | Issues, projects and teams you can access | Creates an issue (and a label for it) when you approve it |
| Jira / Confluence | Issues, projects and pages you can access | Moves a Jira issue to another status (optionally with a comment) when you ask |
| Notion, PostHog | Pages or product analytics you can access in your own workspace | Nothing |
What "live" means, and what Untangl keeps
Untangl does not copy your connected tools into its own database for search. When you ask a question, run an Action or open a concept, Untangl reads what it needs at that moment under your own permission. If you turn on tracking for a task or an Action with a trigger, Untangl also checks the relevant tool in the background for new activity (for example, new email or a merged pull request) so it can update that task or run that Action. Answers are held in short-lived caches — at most 60 seconds for anything read from a connected tool — to avoid repeated requests.
Some results do become part of Untangl's own records, because the feature you used needs to show its work later:
- a short excerpt of, and link to, an item used as evidence on a task;
- the output of an Action run (for example, a morning brief that lists unanswered emails);
- the card preview of a source you placed on a concept, stored separately for each viewer;
- your conversations with Untangl, including answers that quote your connected content;
- lines in your work profile. When you connect a tool you can ask Untangl to draft a profile section from up to 300 of your own recent items (up to 90 days back). The items are read, used once and discarded; only the resulting sentences, plus references and counts, are kept.
3. Meetings and voice
The desktop app can record a meeting's microphone and system audio when you start or accept a recording, or automatically if you turn on automatic recording (off by default). Recordings are kept on your device.
- Transcription. After a meeting, the recording is sent through our servers to Groq for transcription (and to pyannoteAI for speaker separation, if you turn that on), together with attendee names to improve accuracy. We do not store the audio on our servers: it is passed on for that request and the words come straight back to your Mac. Our Groq account has zero data retention turned on. Breeze (hold a key and speak) also uses Groq by default; if you choose on-device recognition, it uses Apple's speech engine on your Mac, which sends nothing to Apple, and falls back to Groq if that engine fails. The resulting transcript is uploaded to your Untangl account.
- Speaker separation runs on your device by default. If you turn on cloud speaker separation (off by default), the system-audio track is sent through our servers to pyannoteAI. We do not create voiceprints or match voices across meetings.
- Speaker names from the screen (off by default, needs macOS Screen Recording permission) reads the name label in the meeting window on your device; the image is not saved or uploaded, only the names and times it read.
Recording laws differ by place, and some require every participant's consent. Tell participants when you record and obtain any consent the law requires.
4. How we use information
- To provide the features you use: answering questions, planning, tracking commitments, running your Actions, transcribing your meetings and showing proactive suggestions about your own work.
- To keep the Service secure, prevent abuse and fix problems.
- To meter usage and your beta credits.
- To understand which features are used and improve them, using usage information with content removed.
- To send service email: sign-in links and codes, waitlist and team invitations, and results you asked to receive by email.
- To comply with the law and to establish or defend legal claims.
Where the EU or UK GDPR applies, we rely on performance of our contract with you for the features you use, on our legitimate interests for security, product improvement and proactive suggestions, on legal obligation where the law requires processing, and on consent where we ask for it.
We do not sell your information, use it for advertising, build profiles about you for anyone else, or use your content to train or fine-tune AI models.
5. Google user data
Untangl'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.
What we access
With your permission, and only for the Google products you connect:
- Sign in with Google: your name, email address and profile picture.
- Gmail: read your messages and threads; create drafts; send drafts you approve; and change messages, such as starring, within the capabilities you authorize.
- Google Calendar: read your calendars and events; create and update events on your primary calendar when you ask.
- Google Drive, Docs, Sheets and Slides: read the files, documents, spreadsheets and presentations a feature needs; and, where you have granted edit access, write a change to a file only after Untangl has shown you the proposed change and you press Apply.
How we use it
We use Google user data only to provide and improve the user-facing features you invoke and that are visible in the Untangl interface: answering your questions about your email, calendar and files; preparing briefs and plans; tracking commitments and waiting-on-reply items; drafting emails and calendar events for your review; applying file edits you approve; running the Actions you set up; and drafting your work profile. Google data is read live when these features need it; what is kept is described in section 2. The tokens Google issues for your connection are stored in our database, encrypted with AES-256-GCM, and deleted when you disconnect.
What we do not do
- We do not sell Google user data.
- We do not use or transfer it for serving advertisements, including retargeting, personalized or interest-based advertising.
- We do not use it to develop, improve or train generalized or non-personalized AI or machine-learning models, and we do not allow our AI providers to train on it.
- We do not use it to determine creditworthiness or for lending purposes.
- We do not transfer it to others except as necessary to provide or improve the user-facing features above with your consent (for example, to an AI provider that generates the answer you asked for — see section 6), to comply with applicable law, for security purposes, or as part of a merger, acquisition or sale of assets after obtaining your explicit prior consent.
- We do not allow humans to read it, unless we have your affirmative agreement for specific messages or files (for example, when you ask support to look at a problem), it is necessary for security purposes such as investigating abuse, it is necessary to comply with applicable law, or the data has been aggregated and anonymized for internal operations.
Removing access
You can disconnect Google at any time in Untangl (Settings → Connectors). Disconnecting attempts to revoke the Google grant, deletes the connection from Untangl, and at once removes from view the text Untangl kept from your Google data: excerpts on task evidence, suggested tasks and nudges read from it, what Action runs read and produced from it, proposed file and calendar changes, lines in Untangl's notes and your work profile (including its earlier versions) that came from it, concept card previews, and the Google results stored in your conversations with Untangl. The records themselves stay, marked "Removed when you disconnected Google", so your history still adds up; the text on them is blanked straight away, and what remains expires on the schedule in section 9: 90 days for most records (a conversation's running summary 90 days after the conversation was last used), 180 days for Action run records. Your own tasks, meetings and the questions and answers in your conversations stay. If provider revocation fails, you can revoke access directly with Google at myaccount.google.com/permissions.
6. AI processing
Untangl uses large language models to answer questions, summarize, draft, plan and classify. To do that, the content needed for your request — your question, relevant conversation history, meeting text, work-profile context and results read from your connected tools — is sent to an AI model provider, which returns the result to us.
- We use Google (Gemini API), Anthropic and OpenAI. A request can be routed to another of these providers if the first is unavailable.
- We use these providers under their paid API terms, which do not allow them to use our requests to train their models. That does not mean zero retention: under their terms, Anthropic and OpenAI can keep API requests for up to 30 days (with limited exceptions, such as abuse investigations), and Google keeps Gemini API requests for a limited period for abuse monitoring.
- We do not train our own models on your content.
- AI output can be wrong. Untangl shows the evidence behind a status or suggestion so you can check it; see our Terms of Service.
7. Service providers
These providers process information only to run the Service, under their terms and data controls. Each keeps data for its own limited periods (for example, for abuse monitoring) as those terms allow.
| Provider | Purpose | Information involved |
|---|---|---|
| Railway | Hosting our servers, database and cache (europe-west4, the Netherlands) | All information the Service stores |
| Cloudflare | DNS, network protection and encryption in transit (TLS) for all our sites | Traffic to and from our sites and servers, including your IP address |
| Cloudflare R2 | Storing uploaded and generated files (Western Europe) | File contents |
| Google (Gemini API), Anthropic, OpenAI | AI models | The content needed for each request (section 6) |
| TypeSafe AI | A classifier that decides whether an incoming update needs an AI model's attention, when enabled | The text of that update |
| Groq | Meeting and Breeze transcription, sent through our servers; zero data retention is on for our account | Audio recordings and attendee names |
| pyannoteAI | Cloud speaker separation, only if you turn it on | Meeting system audio |
| Apple | On-device speech recognition for Breeze, if you choose it | Nothing: it runs on your Mac |
| Exa | Web search, when a question or Action needs the public web | The search query, which the AI writes from your request and can include names or terms you used |
| PostHog (United States) | Product analytics, application logs and AI cost and latency monitoring | Usage numbers and internal identifiers (your account ID), with your sign-in email address and name on your analytics profile: no error messages or stack traces, and no AI requests, answers or connected-tool content |
| Resend | Sending sign-in emails (a one-time link and code), waitlist and team invitations, and emailed results | Your email address and the message |
| Autumn and Stripe | Billing (Autumn) and payments (Stripe), only once paid plans are switched on; not active during the beta | Your account ID, plan and credit balance; card details would go to Stripe, never to us |
The tools you connect also receive the requests Untangl makes to them on your behalf, under your own agreement with each of them. We also disclose information when you direct us to (for example, sharing a task with a teammate), to a successor in a merger or acquisition subject to applicable protections and consent requirements, and where the law requires it. Google-derived data remains subject to section 5, including explicit prior consent for a covered business transfer.
8. Teams and sharing
Untangl is a team product with a private personal layer. Tasks can be shared within your team. Your connected-tool permissions, planner, work profile, search results and private conversations are never pooled with your team.
Sharing a task, concept or Action shares only that item, at the role you choose. It never shares access to your tools: a teammate who opens shared evidence, or runs a shared Action, does so under their own connections, never yours. Content you place in a shared item is visible to the people you share it with.
9. Retention and deletion
| Information | How long we keep it |
|---|---|
| Data read from connected tools | Not stored, except where it becomes part of a record listed below. Caches last at most 60 seconds. |
| Account, tasks, concepts, Actions, transcripts, conversations, work profile, feedback you send from the app | Until you delete them or your account is deleted. |
| Tasks and concepts you delete | Removed for good 30 days after you delete them. |
| Excerpts from connected tools saved as task evidence | Cleared after 90 days (the evidence line and link to the item stay). Disconnecting the tool blanks them straight away. |
| Results from connected tools stored in your conversations with Untangl | Removed after 90 days. Disconnecting the tool removes them straight away. The conversation itself stays. |
| Untangl's daily notes about your work | Deleted after 90 days. |
| Running summaries of long conversations (AI memory) | Deleted once a conversation has been idle for 90 days. |
| Proposed changes to Google files and calendar events | Deleted after 7 days. Disconnecting Google blanks them straight away. |
| Action run history | Finished runs are eligible for scheduled cleanup after 180 days; each Action's most recent run is kept as a baseline, and unfinished runs are retained while pending. Disconnecting a tool blanks what finished runs read and produced from it straight away; the run record itself follows the 180-day rule. |
| Inbox notifications | Eligible for scheduled cleanup after 30 days. |
| Connection tokens | Until you disconnect the tool, which deletes them. |
| Sign-in sessions | End 30 days after you sign in, or after 90 days without use, whichever comes first. Signing out, or Sign out everywhere in Settings, ends them at once. |
| Meeting audio on your device | By default, kept for speaker naming. Audio is eligible for cleanup at 90 days; a closed or offline app can delay cleanup. Local transcript archives and screen-text records need separate deletion. |
| Waitlist entry (your email address and note) | Until you ask us to delete it (section 1). |
| “Notify me” email address | Kept only to send that notice; removed when you ask (section 1). |
| Beta credit and AI cost records | Kept as accounting records, also after your account is deleted, under an internal account number and without your content. |
| Server and error logs | Up to 30 days. |
| Product analytics events (what was used, never your content) | While your account exists. Deleted when you delete your account. |
| Database backups | Up to 90 days, then overwritten. If we restore a backup, accounts deleted since it was taken are deleted again. |
Deleting your account
Open Settings → Danger zone → Delete account and type the email address on your account to confirm. Deletion starts straight away and cannot be undone. If you cannot sign in, email privacy@untanglapp.com from that address and we will delete it for you. If you own a team other people use, you are asked to pick a new owner for it first.
When you confirm, we delete:
- your account, sign-in sessions and settings;
- the tasks on your own list, your meetings and transcripts, concepts, Actions and their runs, inbox, nudges, work profile and memory;
- your conversations with Untangl;
- files you uploaded or Untangl generated for you;
- your stored connection tokens. We also cancel Untangl's access at Google, Linear and Slack (your personal grant), and stop Outlook's mail notifications to us. GitHub, Jira, Microsoft and the Slack workspace app offer no way for us to cancel access remotely, so remove Untangl in their settings too;
- any billing record we hold with our billing provider, which ends a subscription (cost records, below, stay);
- your product analytics events;
- teams in which you are the only member.
What stays:
- Shared work. A task in a team moves to that team's owner, so the team keeps it. Where you were the author of something that stays, the team owner is recorded instead. The change history of a shared task keeps an internal account number that no longer leads to your name or email.
- Cost and credit records. The cost and token count of each AI request, and the beta credits granted to you and used by each request, under that internal account number, without your name, email or content.
- Your waitlist entry (your email address and note). Email us to remove it too.
- Copies we do not control: recordings, files and browser storage on your own devices, copies other people saved, and what our providers keep under their own retention rules.
- Logs and backups, until they expire: logs within 30 days, backups within 90 days.
Deletion finishes within seconds, and every other signed-in device is signed out at once. There is no self-service export yet: email us before deleting if you want a copy. You can also delete individual meetings, tasks and other items in the app at any time.
Revoking access. Disconnect a tool in Settings → Connectors, or revoke Untangl at the provider (for Google, myaccount.google.com/permissions). Once access is revoked, Untangl can no longer read that tool. Disconnecting in Untangl also blanks the text Untangl kept from that tool straight away (see Removing access in section 5; the same applies to every tool): your tasks, evidence rows and run records stay, without the tool's text, and what remains expires on the schedule above. If you revoke at the provider instead, Untangl stops reading at once and the stored text ages out as in the table above; disconnect in Untangl as well, or email us, to blank it straight away.
10. Security
- Each connection uses your own delegated permission (OAuth); there is no shared account that reads everyone's data.
- Connection tokens are encrypted at rest with AES-256-GCM.
- The desktop app keeps your sign-in token in the macOS Keychain.
- Data is encrypted in transit with TLS.
No system is perfectly secure. If a breach affects your personal information, we will notify you and the relevant authorities as the law requires.
11. International transfers
Untangl is operated from India. Our backend, database and cache run on Railway in its europe-west4 region (the Netherlands), and uploaded and generated files are stored in Cloudflare R2 in Western Europe. Cloudflare serves our sites from its global network, PostHog is in the United States, and our AI and transcription providers process requests in the United States and other countries. Our development environment is separate from this production service and is used by our team for testing.
Where the law requires a safeguard for these transfers, we are putting these in place with each provider (Railway, Cloudflare, PostHog, Google, Anthropic, OpenAI and the other providers in section 7), using the EU Standard Contractual Clauses in the provider's data processing terms. Email privacy@untanglapp.com for their status or a copy.
12. Your rights
Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, to object to or restrict certain processing, and to withdraw consent. To exercise any of these rights, email privacy@untanglapp.com. You do not need an account to contact us. We will verify your request and aim to respond within 30 days, or sooner where the law requires.
- EU and UK: you can also complain to your local data protection authority.
- California: we do not sell or share personal information for cross-context behavioral advertising, and we will not discriminate against you for exercising your rights.
- India: our grievance officer can be reached at privacy@untanglapp.com. We will acknowledge a grievance and respond within 30 days.
If your information appears in someone else's email, document or meeting that was processed by Untangl, you can contact us too; where that person's organization controls the information, we will help route your request.
13. Children
Untangl is a work tool for adults and is not directed to anyone under 18. If you believe a child has created an account, contact us and we will remove it.
14. Changes to this policy
We will post any change on this page and update the date at the top. If a change materially affects how we use information we already hold, we will tell you in the app or by email before it takes effect.
15. Beta
Untangl is in beta (version 0.x). Places are limited: when none are free, new sign-ups join a waitlist and we email them when a place opens. Features can change, break or be removed while we build it. Our Terms of Service explain what the beta means for you.
Beta credits. Every account starts with 1,500 beta credits ($15 of AI use). When they run out, AI features pause until more are added; your data stays. We keep a ledger of the credits granted to your account and the credits each AI request used, under an internal account number. It does not contain the content of your requests, and it stays as an accounting record after your account is deleted. Beta credits have no cash value, and no payment provider is active during the beta.
If the beta ends. We will email you before the beta ends or Untangl closes, and give you time to ask us for a copy of your data or to have it deleted. If we start charging, we will tell you first; nothing is charged without your agreement.
16. Contact us
Untangl
Privacy: privacy@untanglapp.com · Support:
support@untanglapp.com