Taskr
Open the app
Privacy
Taskr keeps what a household types into it on a server, so that every member's phone shows the same split. This page says what that is, who can read it, which other companies handle it, and how to get it deleted. Taskr publishes no other privacy policy, so this is the one that governs.
What it stores
Everything in the table is kept on Taskr's server, in the household's own records. The last column says who in the household can read each row through the app. Every member can read every other member's email address; it is stated here plainly because a household app is likely to include people who did not expect that.
| What | Who in the household can read it |
|---|---|
| The name you are shown as | Everyone in the household |
| Your email address, which is your sign-in | Everyone in the household |
| Your password | Nobody. It is held by the sign-in service Taskr uses, not by Taskr: the app hands it straight to that service, and Taskr's database never stores it. A PIN issued before 11 September 2026 is held the same way, as the password of an account with no email behind it. |
| Your available minutes for a week, and a note of where a week's figure came from | Everyone in the household |
| Each chore: its name, how many minutes it takes and took, when it is due and how it repeats, where it came from, who holds it, who it is marked as unsuitable for, and when it was done or missed | Everyone in the household. Any member can delete a chore. |
| Since 18 September 2026, a record of each time a chore changed hands: who held it, who moved it, and in which week. It stays after the chore is deleted, until the household is. | Everyone in the household |
| The household's name, its time zone, and who organizes it | Everyone in the household |
| Each invitation code the organizer creates: a scrambled fingerprint of the code, never the code itself; who created it and when; when it stops working; and whether it was withdrawn or used, and by whom | The organizer only |
| When each invitation email was last sent, and whether it has been accepted | Everyone in the household |
| The name the organizer typed when inviting you, kept by the sign-in service with your account | Nobody through the app |
| Shopping lists, what is on them with any note, who added or bought each item, and who finished each trip | Everyone in the household |
| If you connect Google Calendar: the key Google issues so Taskr can read your calendar, which permission it covers, and Google's identifier for the Google account it belongs to (not its address) | Nobody through the app. Only Taskr's own server-side functions can read it. |
| If you connect Google Calendar: how many minutes you are busy each week, and how many events that came from. Not the events' names, who is in them, or when they are. | Everyone in the household |
| If you import a calendar event as a chore: Google's identifier for that event, kept so it is not imported twice. The event's name becomes the chore's name, which everyone can see; the calendar entry itself is kept nowhere. | Everyone in the household |
| Each time you use Work out the minutes or Work out the chores: who asked and when, and which of the two it was. Not what you typed. | Nobody through the app |
Everything you type has a limit. Taskr's server enforces these: a person's name is at most forty characters, a household's name sixty, a chore's name eighty, and a description you ask Taskr to work out two thousand, and that one is not kept. The app enforces these: a shopping list's or item's name is at most eighty characters, and an item's note a hundred and twenty. There is no other free-text field that is kept.
What it keeps on your device
In your browser's own storage, and nowhere else: your sign-in session, kept by the browser if Trust this device — stay signed in is ticked, or by this tab alone until the browser closes if it is not, with a marker saying so; which household you last switched to, so the app reopens on it; an invitation code and the name you typed with it before you were signed in, cleared the moment it is used or refused, and on sign-out; and whether you said Not now to installing Taskr (forgotten after thirty days) or installed it. While a calendar connection is in progress, the tab holds a one-off token and which household it is for, and forgets both on the way back or when the tab closes. The browser also keeps the app's own files so that it opens quickly; they hold nothing of yours.
Signing out removes all of it except the note about installing. Clearing the site's data in your browser removes everything.
Who else can read it
Every read the app makes goes through the database's own row-level rules, keyed on which household you are a member of. A member of one household cannot read another household's records, and the app has no way to ask for them.
As the person who runs Taskr I can read the database it stores this in. I do that only to fix a problem you have reported or to delete data you have asked me to delete. Stated 15 October 2026.
Third parties
Which companies handle it
Taskr is built on services other companies run. Each row says what that company handles for Taskr and whether it is switched on today. What each company keeps of what it handles is under its own privacy policy, not this one.
| Who | What they handle | Is it on? |
|---|---|---|
| Supabase | The database that holds everything in the table above, the sign-in service that holds your password, and the emails Taskr sends: confirming your address, inviting you to a household, and resetting a password. Supabase writes those emails; Resend delivers them. | Yes |
| Resend | Delivers the emails Taskr sends: confirming your address, inviting you to a household (which carries the name the organizer typed for you), and resetting a password. It handles the address each one goes to and what it says. | Yes |
| Vercel | Serves the app at taskr.madcowhq.com, and runs the once-a-day job that purges deleted households. No analytics. | Yes |
| Google Calendar | Only if you connect a calendar: Taskr asks Google for your free and busy times and which Google account they belong to, and, if you choose to import an event, for a read-only view of your events. Google's approval screen for Taskr is still in testing, so only people registered with Google as Taskr's testers can connect a calendar. | Yes, for registered testers |
| Google sign-in | Continue with Google on the sign-in screen signs you in with your Google account instead of a password; Google tells Taskr's sign-in service your Google address and basic profile. Taskr keeps no Google key for this and cannot withdraw the permission for you: remove Taskr from your Google account's third-party access yourself when you stop using it. | Yes |
| Anthropic | Only when you press Work out the minutes or Work out the chores: the sentence you typed, which of the two you asked for, and one name (yours for Work out the chores; for Work out the minutes, the person the minutes are for) are sent to Anthropic's service to be turned into minutes or chores. Taskr keeps a record of who asked, when and which kind, and not the sentence. | Yes |
There is nothing else: no advertising, no analytics, no crash reporting, and no tracking cookies. The only things kept in your browser are the ones listed above.
How to get it deleted
All four routes are in the app, on the Who tab. Deleting your account is also on the screen you see when you are signed in to no household.
- Leave a household
- Leave this household, near the foot of the Who tab. The chores dealt to you go to the others; any placed on you by hand become unassigned, and chores you finished stay finished without your name. Then your row and what hangs from it go: your minutes, which chores you were marked as unable to do, your calendar connection, and your record in the table above. Things you added to shopping lists, invitations you sent and calendar events you imported stay, without your name, and the record of which chores changed hands keeps an unnamed entry for you. If you had connected Google Calendar, Taskr asks Google to cancel its access before your key is deleted, unless another Taskr connection uses the same Google account, or the connection dates from before 17 September 2026 and Taskr does not know which account it was. If this was the only household you were in, your sign-in is deleted as well. An organizer cannot leave without first handing the household to another member who has signed in, or deleting it.
- Delete a household
- The organizer's Delete this household, near the bottom of the Who tab. It disappears from everyone's app at once. For seven days the organizer sees Restore with the household's name on signing in, and can bring it back whole. After that it is purged for good: Taskr asks Google to cancel each member's calendar access, unless another household uses the same Google account (or, for a connection made before 17 September 2026, the account is unknown), and every sign-in that belonged only to this household is deleted.
- Be removed by the organizer
- Your row and everything hanging from it go the same way. Taskr does not, in this case, tell Google, so if you had connected a calendar, cancel Taskr's access yourself from your Google account's connected apps.
- Delete your account
- Delete my account. On the Who tab it takes you through leaving, and leaving the last household you are in deletes your sign-in at once. If you are signed in but in no household, the screen you see has Delete my account, which deletes the sign-in immediately and cannot be undone; if you were in a household waiting to be deleted, your calendar connection there is cancelled first.
Nothing else is deleted on a timer. Apart from the seven-day purge of a deleted household, Taskr keeps what it stores until somebody deletes it by one of the routes above.
Children
Members of a household may be children; a child with sixty available minutes and a parent with three hundred is the case Taskr was built for. There is no age check. The organizer decides who is added, and since 11 September 2026 every new member is added by their own email address and sets their own password. Members added before that date with a PIN keep it.
Whether a child's own school calendar should be connected is a question Taskr has not settled, so nothing here recommends it.
Security
Passwords are held by the sign-in service, never by Taskr. The key Google issues for a connected calendar can be read only by Taskr's own server-side functions, and the credential those functions use never reaches the app in your browser; a check at build time refuses a build that would ship it. The row-level rules above are enforced by the database itself, not by the app asking nicely.
Changes to this policy
If Taskr's behaviour changes in a way that affects this page, the page is updated before that change reaches taskr.madcowhq.com. The date at the foot is when it was last checked against the app.
Contact
Questions about this policy go to dave@madcowhq.com.
This is the only privacy policy Taskr publishes, and it governs. Checked against the app on 15 October 2026, version 1.0.2. If the app and this page ever disagree, the page is the defect — please say so at the address above.