Privacy policy
What Unblockd collects, why, who helps us process it, how long we keep it, and what you can ask of us.
Last updated November 13, 2026
Who we are
Unblockd is run by Conversint Consulting LLC, a Texas limited liability company, 5900 Balcones Drive, STE 100, Austin, TX 78731, US. Questions about this policy or your data go to hello@unblockd.ai.
Teams use Unblockd to run projects with their sponsors and stakeholders. The team’s organization is our customer. For the project content a team puts into Unblockd, including the names and email addresses of the sponsors and stakeholders they share it with, we act on the customer’s instructions as their processor. For our own account, billing, and website records, we are the controller. Our data processing agreement sets out how we act as a processor.
We are appointing a representative in the EU and UK; until then, people there can reach us directly at hello@unblockd.ai.
What we collect
- Team accounts: name, email address, and organization membership, through our sign-in provider.
- Project content: outcomes, deliverables, activities, tasks, evidence links, blockers, risks, decisions, comments, and the history of changes.
- Sponsor and stakeholder details a team adds: name, email address, and role on a project, plus what they do on their page (answers, replies, feedback).
- Access links: we store only a one-way hash of each private link, when it was used, and which link was used for each action. The codes we email to confirm a new browser are kept the same way, as a one-way hash, and deleted a day after they expire.
- Connected assistants: which assistant acted for which person, and what it changed, recorded in the project’s history.
- Connected tools: what a workspace admin connects, and the items your team brings in from it, as set out in Tools you connect.
- Tool requests and searches: when you ask for a tool, its name, your note, where you asked from, and the search that led there, plus your name and workspace when signed in (or the email you give us when signed out, which we use only to reply; we keep just a scrambled form of it for a day or two to limit repeat requests). Tool searches are counted by the search term, whether it found a tool, and, when signed in, the workspace, never who searched; terms that look like an email address, a link, or a long number are dropped.
- Feedback you send us from Send feedback (in the app or through a connected assistant): whether it’s an idea, a problem, or a question, what you wrote, the app page you sent it from (without anything after a “?”), and your name, email address, and workspace. It’s emailed to our team so we can reply, and kept with your workspace until the workspace is deleted.
- Billing: the plan, seat count, and subscription status. Payment details are handled by our payment provider and never reach our servers.
- Emails we send: recipient, type, and delivery status, so each alert is sent once.
- Technical data: request logs from our hosting provider, kept to run and secure the service.
- Website analytics: on our public site and in the app, which pages are viewed (with project and task identifiers and anything after a “?” removed), the referring site, rough location (country), device type, and how fast pages load, plus a few clicks such as Start free trial by page, when the product demo is opened and how much of it plays, and how far down each public page a visit reads. We also count, on our own servers, visits per public page and per source (the campaign tag, else the referring site’s name), and how many of them go on to read further, click Start free trial, open and start the sign-up form, and create a workspace: daily totals only. A visit’s source and the first page it opened are held in your browser tab’s session storage, cleared when the tab closes. It uses no cookies and doesn’t identify you, and it never records sponsor pages, answer links, or unsubscribe links. It also counts which tools are requested, and tool searches that find nothing, by the tool name or search term only.
- How a new workspace found us: the first page of our site you opened, the campaign tags on that link, the referring site’s name, the page you signed up from, and which kinds of page you read first (help, comparison, use case, or guide; never which page). It holds no name or email address, but once it’s stored with the workspace it’s part of that workspace’s record, and so linked to the organization that created it. If you came from one of our Google ads, it also keeps the ad click identifiers Google adds to that link, used to tell Google Ads which ads led to sign-ups.
How we use it
- To run the service: show each person what they’re allowed to see, send alerts and access links, and keep the history accurate.
- To bill the workspace for its plan.
- To keep the service secure: rate limits, abuse prevention, and investigating problems.
- To answer support requests and the feedback you send, and to improve Unblockd from it.
We don’t sell personal data, show ads, or use project content to train AI models.
Our legal bases
Where the law asks us for one (for example, in the EU, UK, and Brazil), these are the reasons we may use personal data:
- Contract: running the service for the customer and its team, and billing.
- Legitimate interests: security and abuse prevention, counting how the website and product are used (without identifying visitors), improving Unblockd, and telling business contacts about it, which they can stop at any time.
- Legal obligation: keeping billing and tax records, and answering lawful requests.
- Consent: where we ask for it, such as an optional newsletter; you can withdraw it at any time.
For project content, the customer decides why it’s processed, and we follow its instructions.
Assistants you connect
When someone connects an assistant such as Claude, ChatGPT, Codex, or Cursor, that assistant reads and changes project data as that person, through their own account with that provider. It can read anything that person can see in Unblockd, including items brought in from connected tools, and what it reads is sent to that provider. What the provider does with it is governed by their terms with that person or their organization. Unblockd never receives your assistant’s credentials, and you can disconnect it at any time from the assistant’s settings.
Built-in AI
On the Basic and Team plans, a team member can ask Unblockd to draft an ask, an update’s opening note, a project from a pasted plan, or items from meeting notes, or to answer a question from the workspace’s projects. Only then is the text involved sent to OpenAI, the only AI provider built-in AI uses, and that text can include the titles of tasks brought in from connected tools. A draft is shown to that person to check before anything is saved or sent; an answer changes nothing. We use OpenAI’s API, which does not use this text to train its models. Assistants you connect yourself use their own AI and never go through ours.
On every plan, Unblockd also sends two things to OpenAI on its own, to read them for the team: a sponsor’s emailed reply to an ask, to tell which option it picks and whether it adds a condition or asks for a change; and a file a sponsor sends with an answer, to check it looks like what was asked for (an image as it is, a PDF or text file as its text, anything else by its name and type). These checks return likelihoods, never text; the team sees the result, nothing is rejected because of it, and a reply that isn’t clear is left for a person.
Chat channels you connect
A workspace admin can connect Slack, Microsoft Teams, or Google Chat channels. Alerts then post there, including project names and the short text of questions, answers, and blockers, internal blockers included, so connect a channel only your team can see. That content is then held by that chat provider under your organization’s agreement with them. The webhook address is stored encrypted, and an admin can remove the channel at any time.
Tools you connect
A workspace admin can connect task, code, and docs tools such as Jira, Asana, Monday, Linear, GitHub, Google Tasks, Confluence, or Miro. Unblockd only reads them and never creates, changes, or deletes your work in them. For the tools that send change notices (Jira, Asana, and Monday), it also registers the webhook that sends them.
- For each connection: the account or site name shown in Settings, the tool’s id for it, and the access token or API key. Details typed in with an API key, such as your site’s address, are kept as entered.
- For each list, project, board, or repository linked to an Unblockd project: its id, its name, and a link to it.
- Task tools: when someone brings items in, we read the open items in the linked source. For each item brought in we keep its title (up to 300 characters), its status, its id and key in the tool, and a link back to it. An item marked blocked in the tool opens a team-only blocker with the same title and link, and if your team connected a chat channel, its title is posted there.
- GitHub: we read the titles, descriptions, and branch names of merged pull requests and published releases only to find Unblockd task keys, and attach each match’s title and link to that task as proof.
- Docs tools (Confluence, Lucid, Miro): the titles and links of the pages or boards someone adds as proof.
We re-read those items to keep their status current. Tools that send change notices tell us when an item changes, and we read it again from the tool. The others are re-read when someone opens the project’s Sources tab and it’s been more than 10 minutes, when someone taps Sync now, and once a day.
Access tokens, refresh tokens, and API keys are encrypted with AES-256-GCM before they’re stored, the key is kept outside our database, and they’re never included in exports. Only a workspace admin can connect or disconnect a tool. Disconnecting it from Settings, under Connected tools, deletes its stored tokens and unlinks everything linked through it. Where the tool offers a way to revoke access (Google, Asana, Linear, Notion, Miro, Smartsheet, Lucid, Monday, and Zoho), we also ask it to revoke ours; for GitHub, we uninstall the Unblockd app from your account. If another Unblockd workspace connected the same account, its access is left in place. Items already brought in stay as ordinary tasks until the project or workspace is deleted. You can also remove Unblockd’s access from the tool itself, for Google at myaccount.google.com/permissions.
Items brought in from a tool are project content: only your workspace’s members see them, unless a teammate shares one with your sponsor; otherwise sponsors see them only as part of a deliverable’s progress. They reach other services only as described above: a teammate’s own connected assistant can read them, and built-in AI can include them in a draft or answer that teammate asked for.
Google user data
Unblockd’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.
When an admin connects Google Tasks, Unblockd asks Google for read-only access to Google Tasks, and for your Google account’s email address to show which account is connected. We read your task lists and the open tasks in a list linked to a project, and keep only what Tools you connect describes: the list’s id and name, and for each task your team brings in, its title, whether it’s open or done, its Google ids, and its link. We use this data only to show those tasks in your project and keep their status current.
We transfer it only to provide features your team uses: a task’s title can be sent to OpenAI when a teammate asks built-in AI for a draft or an answer, and a teammate’s own connected assistant can read it as that teammate. We don’t sell Google user data, use it for advertising, or use or transfer it to create, train, or improve AI or machine-learning models. People at Unblockd don’t read it except as set out under Security.
Who processes it for us
A small set of providers host, store, sign in, email, track errors, and bill for Unblockd, and run the built-in AI you choose to use, under contracts that limit them to doing that work for us. Customers can request the current list by writing to hello@unblockd.ai, and we give 30 days’ notice before adding one.
Where data goes
Unblockd stores and processes data in the United States. When it comes from the European Economic Area, Switzerland, or the United Kingdom, we transfer it under the European Commission’s standard contractual clauses and the UK addendum (part of our data processing agreement), and our providers use the same clauses or the EU-US Data Privacy Framework.
Cookies and local storage
- A sign-in session cookie for team members.
- A session cookie on a sponsor’s private page after they open their link.
- On a sponsor’s private page, a cookie that remembers for 30 days that this browser confirmed it belongs to them with an emailed code, holding only a keyed hash of their email address, and a short-lived one that holds their link while they enter the code.
- On our public site, a cookie that remembers for 30 days how you first found us (the page, campaign tags, and referring site), a separate cookie that remembers for 30 days a Google ad click identifier if you came from an ad, and, in separate cookies, if a team’s page sent you, which team, so a workspace you create records it. These cookies hold no name or email address; they’re tied to you only by being stored with the workspace you create. In the European Economic Area, the United Kingdom, and Switzerland, and wherever we can’t tell your location, we ask two separate questions and set nothing until you answer. Measurement is the cookie that records the page, campaign tags, and referring site. Ads, asked only if you came from a Google ad, is keeping the ad click identifier and telling Google Ads which ad it was. You can allow or refuse each on its own; which team’s page sent you is still recorded so that team is credited for the referral. You can change either choice at any time with Cookie choices in the page footer, and the rule follows your location.
- Small preferences on your device, such as light or dark theme and the last assistant you picked to connect.
We don’t use advertising or cross-site tracking cookies. Our website analytics works without cookies.
How long we keep it
Project content stays while the workspace is active. Archiving a project hides it; a workspace admin can choose to delete archived projects automatically after 90 days, a year, or two years. An admin can download the workspace’s data (uploaded files are listed with their links), or delete the workspace from Settings: that removes its projects, files, history, and feedback at once and cancels its subscription, with no later export, so download first. Canceling a subscription instead keeps the workspace and its data. Database backups that still hold it expire within 30 days, and billing records stay with Stripe as tax law requires. Access links expire on their own; removed people lose access at once.
Security
Every request is scoped to one workspace, data is encrypted in transit, access links are stored only as hashes, and every change is recorded with who made it. Tokens and keys from tools you connect, and chat webhook addresses, are encrypted at rest with AES-256-GCM. Assistants connect through OAuth with tokens issued for Unblockd only.
People at Unblockd don’t read your project content, including items from tools you connect, unless you ask us to for support, it’s needed to investigate abuse or a security issue, or the law requires it. Our internal reporting counts activity across workspaces, such as how many asks were sent and answered, not what your projects contain.
Your choices and rights
You can ask to see, correct, export, or delete your personal data by writing to hello@unblockd.ai, and we’ll answer within 30 days. If you’re a sponsor or stakeholder on someone’s project, we’ll work with the team that added you, since they decide what the project holds.
Depending on where you live, you also have the right to restrict or object to how we use your data (including any use based on legitimate interests, and any business email from us), to take it to another service, to withdraw consent you gave, and to complain to your data protection authority. In the EU and UK that’s the authority where you live or work.
California residents: we don’t sell or share personal information for cross-context advertising, and we don’t use sensitive personal information to infer anything about you. You can use the rights above without being treated differently for it.
Automated decisions and children
We don’t make decisions about anyone by automated means that have legal or similarly significant effects. Built-in AI only drafts text a person reviews. Unblockd is for organizations and isn’t meant for anyone under 16.
Changes
When this policy changes, we update the date above, and for material changes we tell workspace admins by email before they take effect.