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, and the app never sees 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, when it is due, who holds it, and when it was done or missed | Everyone in the household. Any member can delete a chore. |
| The household's name, its time zone, and who organizes it | Everyone in the household |
| Each invitation the organizer sends: a scrambled fingerprint of the code, never the code itself, and when it expires | The organizer only |
| Shopping lists, what is on them, and who added or bought each item | Everyone in the household |
| If you connect Google Calendar: the key Google issues so Taskr can read your calendar, and which permission it covers | 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 is bounded: a name is at most forty characters, a chore's name at most eighty, and a description you ask Taskr to work out at most two thousand. There is no free-text field that is kept beyond those.
What it keeps on your device
In your browser's own storage, and nowhere else: which household you last had open, so the app reopens on it; an invitation code you typed before you were signed in, which is cleared the moment it is used or refused, and on sign-out; and your sign-in session. While a calendar connection is in progress, the tab holds a one-off token for the trip to Google and back, and forgets it when the tab closes.
All of it goes when you sign out or clear the site's data in your browser.
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 13 September 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. | 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, 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. | Yes, for registered testers |
| Google sign-in | If Continue with Google is offered on the sign-in screen and works, signing in that way uses your Google account as your sign-in instead of a password. It is switched off at the time of writing. | Not yet |
| 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 the name you are shown as 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
Three of the four routes are in the app, on the Who tab. The fourth is an email.
- Leave a household
- Leave this household, at the foot of the Who tab. The chores you hold are dealt out to the others first. Then your row and everything hanging from it go: your minutes, your calendar connection, and your record in the table above. If you had connected Google Calendar, Taskr asks Google to cancel its access before your key is deleted. 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, at the very bottom of the Who tab. It disappears from everyone's app at once. For seven days the organizer sees a Restore button on signing in, and can bring it back whole. After that it is purged for good: every member's Google access is cancelled, 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 sign-in
- Deleting your sign-in while you are in no household is not in the app yet. Email hsc.coach@gmail.com from the address you signed in with and I will delete it.
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 hsc.coach@gmail.com.
This is the only privacy policy Taskr publishes, and it governs. Checked against the app on 13 September 2026, build 74aed25. If the app and this page ever disagree, the page is the defect — please say so at the address above.