Privacy

Who runs this

The site is run privately at kidtracker.ai. It is one person's site rather than a company, it sells nothing, and nobody else has a hand in what is held here.

What the site keeps

• Who you are. Your Google account's email address and the name on it. Both are read off the Google account you sign in with and neither is typed here. That is the whole of the account — there is no password, no profile and no photo.
• The agreement you upload. The signed PDF, stored privately, and the reading of it: the clause numbers, the short titles your tabs carry, a plain summary of each clause and the words of the clause itself. Nothing on this site serves the document back out, and the reading of it is only ever sent to your own browser, behind your login.
• What you log. Each breach as you wrote it: which clause, your description of what happened, the date and time you gave it, and when you logged it.
• The evidence you attach. The files themselves — photos, screenshots, PDFs, recordings — stored encrypted in a private bucket under your account, reachable only through a link this site signs for you that stops working after five minutes.
• A session. A signed cookie that says you are logged in, valid for twelve hours, plus a short-lived cookie used only to carry a login safely from this site to Google and back.

Everything you type is stored as typed. What you write here is a record you may one day want to show somebody, so write it the way you would want it read: what happened, when, and nothing you would not say out loud.

The other party

This is a one-sided record by design, and that is worth being direct about. Your agreement names somebody else; their name is read out of it, and what you log is your account of what they did. They are not given a login, are not notified that this account exists, and cannot see, correct or delete anything in it.

That does not make them nobody. If they ask us directly what is held about them we will answer honestly that this is your record, held on your instruction, and point them at you — and where the law where you live gives them a right we have to honour, we will honour it and tell you we did.

What it does not keep

• No analytics, no tracking pixels, no advertising, no fingerprinting.
• No cookies except the two described above — none of them for measurement.
• No location, no contacts, no access to anything on your device we were not handed.
• Nothing is sold, rented or handed to anyone for marketing. Ever.

What it sends you

Three emails, all of them to the address you signed up with, all of them from no-reply@kidtracker.ai:

• A note when the account is created, saying it is ready.
• Once a month, what was logged last month and the clauses it happened on most.
• During a week, only if something was logged: what it was, and against which clause. A quiet week gets no email.

There is no marketing email and nothing to unsubscribe from — these are your own records read back to you, and they stop when the account does.

Who can see it

One Google account: the one that opened the tracker. Every request is checked against the address inside the session, at the login callback before any session exists and again on every call afterwards, and a tracker answers to that address alone. Anybody else signing in with Google gets a tracker of their own and no sight of yours. There is no sharing feature, no second seat and no link that lets somebody else look.

Beyond you, the only parties who can technically reach the data are the service providers below, in the ordinary course of hosting it.

Where it lives

• Amazon Web Services, in the us-west-2 region. Your account and your breach records sit in DynamoDB; the agreement and its reading sit in one private S3 bucket and your evidence in another; the pages are served from a third through CloudFront; the API runs on Lambda; the three emails go out through Amazon SES from the same account.
• Anthropic's Claude, through Amazon Bedrock, reads your agreement once, inside AWS, to produce the clause list your tabs are built from. It is not used to train anything.
• WorkOS handles the sign-in handshake with Google and tells this site the email address and name that came back.
• Google authenticates you. Google sees that you signed in to this site; it does not see anything in it.

AWS and CloudFront keep their own operational logs, which include IP addresses and requested URLs and are retained on their normal schedule. The application itself writes only sparse diagnostic logs and never logs what you wrote in a breach.

Data is stored in the United States. If you are in Israel or elsewhere, using the site means your data is handled there.

How long it is kept

• Breaches and their evidence — until you delete them. Deleting a breach deletes the files filed with it, and neither is recoverable afterwards.
• The agreement and its reading — for the life of the account, or until you replace it with a different agreement. Replacing it deletes the document on file and every earlier one, together with every breach logged against it and every file filed with those; you are told that and asked to confirm it before anything is deleted.
• Sessions — twelve hours. Logging out clears the cookie immediately.
• Provider logs — on AWS's and WorkOS's own retention schedules, which this site does not set.

A record about a family

What is in here is about children, a separation and somebody you used to live with. That is exactly the kind of information that should stay small and stay closed. It is why one account can open it, why there is no sharing feature, and why nothing here is analysed, profiled or used for any purpose beyond showing it back to you.

No child is a user of this site and no child has an account.

What you can ask for

You can see everything held about you, correct it, or delete it, and most of it you can do yourself from the dashboard without asking anyone. Deleting a breach deletes the files filed with it. Replacing the agreement deletes the document, its reading, every breach logged against it and every file attached to one.

Security, told straight

The buckets are private and none of them is public; the site is served over HTTPS only; sessions are signed cookies that expire after twelve hours; your evidence is reachable only through a signed link that expires in five minutes; and the check on who may sign in fails closed — if the accounts cannot be read, everyone is locked out rather than let in.

None of that is a promise that nothing can go wrong. It is a small private site, not a bank. If something does go wrong in a way that affects what is held here, you will be told directly.

Changes to this page

If what the site keeps changes, this page changes with it and the date at the top moves.