Privacy
Here When You Are is a shared board for one household — the schedules, tasks, goals and rewards a family already keeps on a fridge door. This page says plainly what it stores, where that lives, and who can reach it. It is written to be read, not to be survived.
What signing in tells us
Signing in goes through Google. We ask Google for three things — that you are signed in, your email address, and your name — and we keep exactly those, plus the permanent account identifier Google issues so that changing your address later does not lock you out.
We do not ask Google for offline access during sign-in and we store no sign-in token, so the app cannot act on your Google account afterwards. It reads who you are once, and then has no further conversation with Google about you.
If you sign in with a link by email instead, we keep your email address — and, if you ask to join a board, what you tap on that page and a family member's email if you give one — and nothing else about you. Each link works once and lapses after an hour, is stored only as a one-way hash, and the record of it is deleted within a day. So that nobody can ask for links in bulk, that record also holds a one-way hash of the network address the request came from, never the address itself, and it is deleted with the rest.
Every email from us that you could do without ends with a link to unsubscribe. Sign-in links you ask for do not, so you can always get into your board. To keep that link working and to remember your answer, we keep your email address beside a random code and, if you unsubscribe, the date you did.
Paying
Plans and Playground cards are paid through Stripe. You type your card details on Stripe's own page, and we never see or store your card number. What we keep is what Stripe tells us back: which plan you are on, whether it is in its free trial, paid up or ended, the dates that go with that, the name and email given at checkout, and Stripe's reference for your account so we can send you to Stripe to manage it. Stripe keeps its own records of the payment, under Stripe's privacy policy.
What the board itself holds
Everything a household puts on its board: the names and rough ages of the people on it, tasks and checklists, calendar events, goals and habits, rewards and the points behind them, the piggy bank's amounts and wishes, notes, the record of who checked in and when, and whatever a family chooses to use of the rest — how someone felt about a task, the food ticked off today, a period calendar, pets and their play dates. The codes a family sets for each person are stored with the board too.
This is family life, in some detail, and a good deal of it is about children. We collect it because the board cannot work without it, we use it only to draw that household's own board, and it is never sold, never used for advertising, and never fed to anybody's model for training.
Pictures and voice recordings
A family can add its own pictures — to a task, a step or the food list — and a child can record themselves talking. Pictures are shrunk on the device before they are sent, and both are kept on our server in that family's own folder, reachable only from that board. Each family has room for 50 MB of them.
A recording is kept for as long as the family chooses in Settings — a week unless someone changes it — and then deleted. Children’s recordings are never sent to AI. An adult may request a write-up of their own recordings; when that feature is configured, those adult recordings are sent to OpenAI for transcription and summarizing. Adults’ recipe reading remains available. Optional Mandarin lessons send the sentence you enter to Google’s Gemini service when configured; otherwise the app builds the free lesson itself.
Children's phones and notifications
Parent-permission enforcement is off by default. Adults can read the notice and acknowledge that they are the parent or guardian; we record their account, name, time, listed children and exact notice version. This acknowledgment does not block features and is not verified consent. If enforcement is enabled, only each unapproved child’s own submissions pause; adult saves, reminders, phone pairing, recipes and wishes remain available. Verified permission uses an operator-reviewed signed form or a qualifying positive card payment with a receipt after the declaration. Cards on file and zero-dollar invoices do not count. Parents can review, export, withdraw permission or request individual child deletion. Requests are completed through operator review; deleting one child does not withdraw siblings’ consent. Consent evidence is retained while permission is active, and withdrawn, rejected or abandoned evidence is removed within 60 days. Children’s recordings are not sent to AI.
A grown-up can pair a child's phone with the board. The phone then keeps a cookie that says which board and which child it belongs to, and nothing else about the phone is kept.
If someone turns notifications on, their browser gives us an address to send them to, run by the company behind that browser — Apple, Google or Mozilla — which delivers them. Each message is encrypted before it leaves our server, so the company delivering it cannot read it. Turning notifications off deletes that address.
Connecting a calendar is optional
A household can connect a Google Calendar so its events appear on the board. This is read-only in the strongest sense available: the permission we request cannot write, so even a bug on our side could not add, change or delete anything in your real calendar.
Connecting does mean we hold a token that lets us re-read those calendars in the background. It is encrypted, sits in the app's database on an encrypted disk, and disconnecting the calendar (Calendars, on the Calendar page) discards both the token and every event we imported with it. You can also revoke it yourself at any time from your Google account's permissions page, without asking us.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
When something breaks
If a screen crashes, the device sends us a crash report so it can be fixed: the error, the page it happened on, the kind of device and browser, and the technical trace. It is not linked to a family's account and holds no names. Crash reports are deleted after 30 days.
Where it is kept
On a server in Toronto, Canada, rented from Fly.io, on an encrypted disk with automatic snapshots so a household's board survives a failure. Once a day a backup copy is also saved to encrypted storage at Sync.com, which keeps its data in Canada and which only I can open, so a board can be recovered even if the server is lost. Session and invite codes are stored only as one-way hashes — we could not tell you your own invite code back.
Households are separated at the point where data is read, not by anything the browser is trusted to ask for politely. Every query names a household; no page can request another one's.
Who else is involved
These are the third-party services currently involved in operating Here When You Are: Google, for signing in and — if you connect one — reading your calendar. Fly.io, who host the server. Stripe, who take payments. Resend, who deliver the few emails this site sends — sign-in links, welcome emails, the one reminder before an ended board is cleared, and what you tap when you ask to join, which is forwarded to me — and so see your email address and those messages. Sync.com, who hold the encrypted daily backup. The company behind your browser, for notifications if you turn them on. And Open-Meteo, a free weather service: if a board shows the forecast, the device fetches it directly using the approximate location for the town chosen in Settings. That request goes from the device, and it carries a place, never a person.
When you save a recipe, or a piggy bank wish, from a link, our server opens that link to read it, so the website sees our server, not you. A recipe saved from YouTube shows YouTube's own preview picture, which your device fetches from YouTube. And a “see on map” link opens Google Maps only when you tap it.
There are no third-party analytics, no advertising and no third-party trackers on any page, and nothing about your visit is sent to Meta, Google or any other advertiser.
If you came from one of our ads
We advertise Here When You Are, on Instagram for example. The link in each ad carries a few words naming that ad, such as utm_campaign=launch. If you arrive through one, our own server counts how many people came from that ad, and how many of them went on to press Try it, leave the try-out for sign-up, press Start free, begin signing up, finish signing up, open the payment page and start a free trial. That is how we tell whether an ad is worth paying for.
To connect those steps, your browser keeps one small cookie of ours for a week. It holds only the ad's words, the page you landed on, and which of those steps have been counted, which is the same for everyone who tapped that ad. It holds nothing that identifies you. When you go to Stripe to start a free trial, the ad's words are noted with your sign-up on our server, and deleted the moment the trial starts, or after a week if you don't finish. What we keep is a count for each ad and each day, never a record of you or of the pages you read. None of it is sent to Instagram, Meta, Stripe or anyone else, and it is never sold. Our Taiwan address, tw.herewhenyouare.com, is shared as a plain link, so a visit to it is counted the same way, as if it were one ad. If you came to the site any other way, none of this happens.
How the Playground is used
Our own server counts how many times each Playground app and game is opened, in which hour of the day, and how many minutes an app was on screen. These are totals for each app and each day, so we can see which apps get used and make more like them. They never say which child or device it was, families never see them, and none of it is sent to anyone else.
Cookies
Only the ones the board needs to work: one that keeps you signed in, one that remembers a paired phone, and short-lived ones that carry you through signing in or paying. The one exception is the week-long cookie described above, set only if you arrived from one of our ads. None of them follows you anywhere else. A few settings that belong to one device, such as high contrast, are kept in that browser rather than on our server.
Getting it back, or getting rid of it
A household can export its whole board from Settings at any time, as a file it keeps. To have a board and its accounts deleted from the server, write to aitesting123lab@gmail.com from an address that is on it. We keep a household's data for as long as it is using the board, and remove it when asked. If a plan ends, the board is kept for a year in case the family comes back — a free trial that ran out without ever being paid for counts as an ended plan too. A month before the year is up, each account address on it gets one email with a link to download everything; once the year is up, and at least four weeks after that email, everything on the board is cleared, with its pictures and recordings. The accounts, the record of the plan, any Playground card credit, and connected phones and calendars are kept so the family can come back; ask, and those go too, and the board goes sooner. Backup copies are deleted within 60 days, so a deleted or cleared board is gone from those within two months.
Changes
If this ever changes in a way that affects what is collected or who it reaches, the date at the foot of the page changes with it and the households on the board are told directly rather than left to notice.