Kept

Privacy

Kept does not collect anything.

This is the privacy policy for Kept, the childhood archive app for Android published at keptbook.app. It is short because there is little to describe: there are no accounts, no profiles, no analytics, and no server holding your family's photographs.

Last updated 22 August 2026

The short version

ThingWhat happens to it
Where photographs live On each keeper's phone. Every keeper holds a complete copy of the archive.
What we store Nothing. There are no accounts, no profiles, no user records and no analytics. We do not operate a server that holds your archive.
How photographs travel Directly between your phones over your own Wi-Fi network, never through us.
Google Drive Optional backup into your own Google account, using the drive.file scope — which means Kept can see only the folder it created and nothing else in your Drive.
Photo library access The Android photo picker. Kept sees only the photographs you choose. The release build requests no broad media permission.
Logging There is no analytics and no crash reporting. Nothing about a photograph, a memory, a name or a file path ever leaves the phone.
Deletion Uninstalling removes Kept's copy from that phone. Your Drive folder and your gallery originals are untouched.
Children's data The subject of the archive is a child, and the archive is private to the family by construction — no feed, no public link, no discovery, no sharing outside the keepers you invite.

Where your photographs actually are

On your phone, and on the phone of any keeper you have paired with. That is the whole architecture.

Kept is not a service you upload to. There is no Kept server that holds photographs, and no database anywhere with your child's name in it. When a second keeper joins, they receive a complete copy of the archive on their own phone, and from then on both phones hold the whole thing independently. If we disappeared tomorrow, both archives would keep working.

Photographs move between paired phones directly, over your own Wi-Fi network, when both phones are on it. They do not pass through us.

Google Drive, if you choose it

Backup to Google Drive is optional. Kept works completely without it.

If you turn it on, you sign in to Google — not to Kept. Kept then has permission to work with files in your Drive using the drive.file scope. That scope is the narrowest one Google offers for this purpose: it grants access only to files and folders the app itself creates. Kept cannot see, list or read anything else in your Drive, including files you created yourself.

The backup goes into your own Google account, under your own storage. We have no access to it, no copy of it, and no way to reach it. If you revoke Kept's access in your Google account settings, the folder and everything in it stays exactly where it is — it is yours.

What the sign-in itself shares

Signing in with Google means Google tells Kept that the sign-in succeeded and issues a token the app uses to write to its own folder. Whatever Google shows you on the consent screen is the accurate description of what is being granted; read it before you accept. Kept does not transmit anything it learns at sign-in to us, because there is no server to transmit it to.

Your photo library

Kept brings in photographs through the Android photo picker. The picker is run by the operating system, not by Kept: you choose the photographs, and the app receives only those. The release build requests no broad media permission, so Kept has no ability to scan your gallery, and no way to see a photograph you did not select.

What we would have to collect to be a normal app, and do not

Because none of this exists, there is nothing to opt out of and no consent banner. That absence is deliberate and it is the product.

Children

Kept is used by adults to keep a record of a child. The child is the subject of the archive, not a user of the app.

Everything in the archive is private to the family by construction rather than by setting. There is no public link, no discovery, no feed, no sharing outside the keepers you have personally paired with, and no ability for anyone else to reach the content. There is no profile of the child anywhere, because there is no server holding one.

Your rights

Data protection law gives you rights to access, correct, export and erase personal data held about you. In Kept's case these are unusually simple to exercise, because we hold nothing:

If you want any of this explained, write to us and a person will answer.

Changes, and how you will know

If this policy changes in a way that affects what happens to your data, the date at the top changes and the change is described here. We will not quietly widen what the app collects; if that ever became necessary, it would be a visible decision in the app, not a revision to a page you have already read.

Who is responsible

The controller of any personal data connected with Kept is Jipikaje OÜ, a private limited company registered in Estonia. In practice there is very little for a controller to control here, because the app is built so that personal data stays on your own phone — but the law requires the responsible party to be named, and this is it.

ControllerJipikaje OÜ
Registry code11675155
Registered addressSääse tn 12-28, 12918 Tallinn, Estonia
Emailhello@keptbook.app
ApplicationKept, for Android
Websitekeptbook.app