Legal
Privacy Policy
Last updated: 27 July 2026
Tiny Keeps is an app for storing photographs of children's artwork and schoolwork. That means the material you put into it is personal by nature, and often belongs to someone too young to consent for themselves. This page explains exactly what is stored, who else touches it, and how to get it all back or destroy it.
Contact us at support@tinykeeps.app.
Who the app is for
Tiny Keeps is designed for parents and guardians. Accounts are for adults only. We do not knowingly allow children to create accounts, and children do not log in. When you add a child profile, you are supplying information about that child as their parent or guardian, and you confirm you have the authority to do so.
What we collect
| What | Why | Where it lives |
|---|---|---|
| Your email address | To create and sign you into your account | Supabase |
| Child first name, and an optional photo if you add one | To group keeps by child and show who each keep belongs to | Supabase (photo in Supabase Storage, private per account) |
| Photographs you take or upload | They are the thing the app exists to store | Supabase Storage, private per account |
| Titles, descriptions, categories, and tags generated for each keep | So keeps are searchable and browsable | Supabase |
| Subscription status | To know whether your capacity limit is lifted | RevenueCat and Supabase |
We do not use third-party analytics or crash reporting.
How automatic naming works
When you save a keep, the image is sent to an artificial intelligence provider that returns a suggested title, description, and category. This happens on our servers, not on your phone. The provider is Anthropic (Claude API).
Your images are not used to train Anthropic’s models — zero training use. Under Anthropic’s commercial API terms, inputs and outputs are retained for up to 30 days for abuse monitoring, then deleted.
You can edit or replace anything the system suggests. Your edits are kept and are never overwritten by a later automatic pass.
Who else processes your data
- Supabase — hosting, database, file storage, and authentication. Data is stored in US East (N. Virginia,
us-east-1). - RevenueCat — subscription and entitlement management.
- Apple — processes all payments. We never see your card details.
- Cloudflare — serves this website.
- Anthropic — generates titles and descriptions.
We do not sell your data. We do not share it with advertisers. There is no advertising in Tiny Keeps.
Keeping and deleting
Your keeps stay until you delete them. Deleting a keep removes it from your account immediately; backup copies are purged within 30 days.
You can delete your entire account from within the app under Settings. This removes your profile, your child profiles, and every photograph and description associated with them. It cannot be undone. If you would rather we do it, email support@tinykeeps.app from your account address and we will action it within 30 days.
Books you have already generated are stored as files in your account and are deleted along with it.
Your rights
Depending on where you live, you may have the right to access, correct, export, or erase your personal data, to object to or restrict how it is processed, and to complain to a data protection authority. Residents of the EU and UK have these rights under the GDPR; residents of California have comparable rights under the CCPA. Exercise any of them by emailing support@tinykeeps.app. We do not charge for this and we will not degrade your service for asking.
Our legal basis for processing is the performance of our contract with you, and for children's material, your consent as their parent or guardian, which you may withdraw at any time by deleting the material or the account.
Security
Data is encrypted in transit and at rest. Storage access is scoped per account at the database level, so one account cannot read another's files. Access to production systems is limited to the account owners.
Changes to this policy
If we change this policy in a way that materially affects you, we will notify you in the app before the change takes effect. The date at the top always reflects the current version.