Privacy policy

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.

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.
• 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.
• 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 by page, when the product demo is opened and how much of it plays, and how far down the home page a visit reads. 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), kept with the workspace when it’s created. Nothing that identifies you is part of it.

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.

We don’t sell personal data, show ads, or use project content to train AI models.

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 Team plan, 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.

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, and bill for Unblockd, under contracts that limit them to doing that work for us. Data is stored and processed in the United States. Customers can request the current list by writing to hello@unblockd.ai.

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 our public site, a cookie that remembers for 30 days how you first found us (the page, campaign tags, and referring site), and, if a team’s page sent you, which team, so a workspace you create records it. Neither identifies you.
• 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 everything, or delete the workspace from Settings: that removes its projects, files, and history at once and cancels its subscription. 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. 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 may also have the right to object or complain to your data protection authority.

Changes

When this policy changes, we update the date above, and for material changes we tell workspace admins by email before they take effect.