tasks.ai/privacy

Privacy Policy

Last updated: October 28, 2026 · Status: Beta

Tasks.AI turns the work people do into tasks that it carries out for them, with their own tools. It learns from recordings of how work is done, writes the tasks and procedures it finds, and runs them once a person has approved them: on the person's own agent when a task needs anything personal, on Tasks.AI when it does not.

That means we hold recordings, the words in them, and the record of what runs did. This page says exactly what, who else sees it, where it is kept and how to have it deleted.

1. What we collect

Your account. Your email address and name, collected when you sign in, and the organization you belong to and your role in it.

Recordings. The audio or video files you upload, of interviews and of work being done. They contain whatever is said and shown, and the voices and faces of the people in them. We transcribe each one, work out who is speaking, and for a video we keep frames taken from it.

What we find in them. The tasks and procedures described, the quotes that show them, and how much each is worth automating. Each task is stored with the passages of the transcript it rests on.

What you build and ask for. The tasks you write or import, their versions, the instructions you type in the chat, and the messages you send to the Tasks.AI bot if you connect Telegram.

A record of each run. What a run did and what it produced, as reported by the agent that ran it, kept next to what the record itself shows. Documents you give a run as input are kept too; we have not yet set how long.

Email you forward, if you set up a trigger. A task can start from a message sent to an address made for that task. We keep the message and its attachments.

What we do not collect: your passwords for other sites, or your browser's cookies. A run on your own agent happens on your own computer, with your own sign-ins, and those stay there.

2. Why

To do what you asked: to read your recordings, build and run your tasks, and show you what happened. That is the only purpose. We do not sell your data, we do not use it for advertising, and we do not use it to build a profile of you.

3. Who else sees it

Model providers. Reading a recording, finding its tasks and running a task on Tasks.AI means sending audio, text or both to a language model. We route through OpenRouter, which forwards each request to a provider that serves the model. Which provider depends on the model a step uses. Each handles requests under its own data policy, which OpenRouter publishes per provider. We do not send them anything beyond what the step needs.

Your own agent, and Anthropic. When a task runs on your agent, it runs under your own Claude Code login, on your plan. What your agent sends to Anthropic is covered by your agreement with Anthropic, not by this page.

Sign-in. Clerk handles sign-in and the list of people in your organization.

Infrastructure. Amazon Web Services, in Ireland, where our servers, database, file storage and inbound email run.

Telegram, only if you connect it. Your messages to the bot pass through Telegram, under its own policy.

GitHub, only if an owner of a project attaches a repository. The tasks of that project are then written there.

We use no advertising networks and no data brokers, and the Tasks.AI app runs no analytics trackers.

This website. tasks.ai loads its fonts from Google Fonts, so Google receives your IP address when a page loads. It sets no cookies and runs no analytics. It remembers in your browser which version of the page you saw last, so that the next visit shows a different one; nothing about it leaves your browser.

4. Where it is stored

On our servers in Ireland (AWS, eu-west-1). If you are outside the EU, using Tasks.AI means your data is processed there. Requests to a model provider may be processed in that provider's own location.

5. How long we keep it

A recording file is deleted as soon as its transcript is written. The transcript, the frames taken from a video and the quotes found in them are kept, because the tasks rest on them, until you delete the source or the project.

Everything else we keep while your account and project exist. Server logs are kept for 14 days. We do not currently expire old runs or conversations automatically. An owner can delete a task, a run, a recording or a whole project; deleting a project removes its data, its stored files and its link to the repository, and tells the owner what it could not reach.

Ask us and we will delete it. Email contact@tasks.ai and we will delete your account and everything associated with it within 30 days. During beta this is a person doing it, not a button, which is why we would rather say so than imply otherwise.

6. Recording other people

Interviews are the point of Tasks.AI, and an interview has two people in it. If you upload or record one, you are responsible for telling the people in it that it is recorded and why, and for having their agreement where the law asks for it. Do not upload a recording you do not have the right to share.

Anyone who appears in a recording can email contact@tasks.ai to ask for it, and what was taken from it, to be removed.

7. Your choices

8. Beta

Tasks.AI is in beta and changes quickly. If we change this policy in a way that affects what we do with your data, we will say so here and update the date at the top. Continuing to use it after that means you accept the change.

9. Contact

Tasks.AI Inc
contact@tasks.ai

← Back to tasks.ai