How PeasyDone protects your tasks

We're a small team, not a bank, and we won't pretend to be. But a to-do list says a lot about someone's life, and we think yours is your business. This page explains, plainly, what we do to keep it that way, and where the limits are.

Our promise

Your tasks are encrypted before they're stored, with a key made from your passphrase in your browser. We never store your passphrase or your key. To answer a request, our server unlocks your tasks in memory, then forgets the key. Nothing unlocked is ever written to disk or to our logs. Anyone with access to our database, our backups or our admin tools sees only scrambled text, plus dates, done or open, flags and order. No tool or API, ours included, can read your tasks without your key.

How it works

Your browser

You type your passphrase.
Your browser turns it into your key.
The passphrase never leaves your browser.

your key, with each request (HTTPS)your tasks

PeasyDone server

App logicYour tasks, unlocked in memory, only while answering you

Encryption layerLocks text on its way to storage and unlocks it on the way back, with your key

Nothing unlocked is written to disk. Your key is forgotten after each request.

locked text only

Database and backups

pd1.Xk9fQ2…r7Lw

Readable: dates, done or open, flags, order.

Unreadable: names, notes, free text.

Anyone with database or admin access sees only locked text.

Only when you use an AI feature (Dictate, chat, suggestions, estimates, search by meaning): the text involved is sent to our AI provider, OpenAI.

Your key travels with each request and is used only for that request. The database and its backups only ever hold your task text locked.

You choose a passphrase when you first sign in. Your browser turns it into a key. The passphrase itself never leaves your browser, and the key is kept only in that browser tab while it's open.
Your browser sends the key with each request, over an encrypted connection (HTTPS).
On our server, one layer of code locks and unlocks. It locks your task text as it's saved and unlocks it as it's read, using the key from your request. The rest of PeasyDone only sees your tasks unlocked in memory, while answering you. When the request is done, the key is forgotten.
The database and its backups only ever hold your task text locked. A test in our code checks this, and another checks that task text never reaches our logs.

If you connect an AI agent (such as Claude) to PeasyDone, you copy your key into that agent's settings on your own computer. It then sends the key the same way your browser does.

What's locked, and what isn't

Locked (encrypted):

task titles and notes;
list names;
where a task came from (links and their titles);
saved notes and context;
your undo history;
the data PeasyDone uses to search by meaning.

Stored readable, so the app can sort and filter quickly:

dates;
done, open or deleted;
the urgent and important flags;
which lists a task is in (by a code, not the list's name);
the order of your tasks;
hour estimates;
when things changed;
your time zone.

What this protects against

A stolen or leaked copy of our database or backups.
Someone reading our database through a bug.
Anyone at PeasyDone browsing stored data. We don't, and with this design we can't without your key.

What it doesn't

The server while it's answering you. Your tasks are unlocked in the server's memory for that moment. Someone who could change the code we run, or read the memory of the running server, could see tasks while they're in use. We don't, and our policy is that we never will.
AI features. See below.
We don't call this "end-to-end encryption". That term means the server never sees your data, and ours does, briefly, to do its job.

AI features

Some features need an AI model to read the text involved:

Dictate (turning what you describe into tasks);
chat with your list;
Today suggestions;
hour estimates;
search by meaning.

When you use one, the text it needs is sent, unlocked, to our AI provider, OpenAI. OpenAI doesn't use it to train its models. It keeps it for up to 30 days to watch for abuse, then deletes it. We never ask OpenAI to keep it longer.

Services we use

These are the outside services that run PeasyDone or might touch your data. Each has a privacy policy we've read and think is reasonable.

Service	What it does for us	What it can see
Fly.io	Runs our server and stores the database on an encrypted disk	The stored database: your task text only locked. Your tasks unlocked in the server's memory while it answers you.
Tigris	Keeps a continuous backup copy of the database	The same as the database: your task text only locked
OpenAI	The AI features above	The text sent for that feature, unlocked, kept up to 30 days
Clerk	Sign-in	Your email, name and sign-in details. Never your tasks, passphrase or key.
Google or Apple	Only if you choose to sign in with them	That you signed in to PeasyDone

We don't use analytics, advertising or tracking services, in the app or on this site. If you dictate with Wispr Flow or your computer's dictation, that's your own tool; PeasyDone only receives the text.

If you forget your passphrase

Nobody can recover your tasks, not even us. That's the other side of us never having your key. Keep your passphrase somewhere safe, such as your password manager.

Questions

Write to information@advocara.com. PeasyDone is made by Advocara.

Last updated November 10, 2026.