1. About TinyLore and this policy
TinyLore is a private, local-first journal for life with your pet. It is published under the name AEE Studio by an independent developer. This policy explains what the app keeps on your device, when information may be handled by Apple, Google or a service you choose, and what AEE Studio may receive when you contact us.
Privacy questions can be sent to [email protected].
2. Your journal is stored locally
TinyLore stores your journal in a local SQLite database and keeps attachments in app-managed files on your device. This can include pet profiles, signals, observations, contexts, rituals, moments, Little Things responses, media references and local preferences.
No TinyLore account is required. TinyLore does not currently provide an account-based cloud journal or automatically upload your pet's records or stored media to an AEE Studio journal service. AEE Studio does not automatically receive or view your journal.
The journal database and media do not have a separate TinyLore encryption layer. Their protection depends on the security, lock and backup settings of your device and operating system.
3. Photos, videos, audio and permissions
You select photos and videos through your operating system's picker. TinyLore uses microphone access only when you start a supported sound recording for a signal or observation. It does not record in the background, continuously monitor your pet, automatically use the camera or request location for journal tracking.
You can review or change permissions in your device settings. The original photo or video in your library is not changed when TinyLore makes its app-managed copy.
4. Photo metadata
When a newly selected photo is a supported JPEG, TinyLore rewrites its stored copy without supported sensitive metadata such as GPS location, camera and device details, owner or artist fields, MakerNote, XMP and IPTC/Photoshop data. It preserves appropriate display information such as orientation, original capture date, colour space and an ICC profile when available. The compressed image content is copied without a second lossy JPEG encoding pass.
A JPEG that cannot be cleaned safely is not added. The original gallery file remains unchanged.
This protection is not universal. PNG, GIF, WebP, unexpected HEIC output, videos and photos stored before this protection was introduced may retain metadata, including location or device information. TinyLore does not promise that every attachment is metadata-free.
5. Sharing and share cards
TinyLore can create share cards from information you choose. A share card is a newly drawn PNG and does not automatically carry the original photo file's source metadata. Your device's share sheet lets you decide where the card goes.
Once you share a card, export or other content with another app or person, that destination may keep its own copy. Deleting the TinyLore record does not delete copies held elsewhere.
6. Local ZIP export
You can start Export Your Data from Profile → Privacy & Data. TinyLore creates a ZIP containing versioned data.json, a README and the available media referenced by eligible journal records. The export includes eligible existing journal data regardless of Free or Pro state. You choose the external destination through the system share sheet.
The ZIP is not encrypted. Store it somewhere secure and consider the privacy practices of any app or location you send it to. Media files are copied as TinyLore stores them, so formats and historical files that retained metadata may also retain it in the ZIP.
TinyLore cannot currently import this ZIP or use it to restore the journal. Export does not change or remove the source journal. Missing files and protected obsolete media that are not part of the visible journal may be excluded and identified by the export where applicable.
7. Device backups and changing phones
TinyLore does not operate its own backup or sync server. Apple or Google operating-system backup and device-transfer features may include supported TinyLore journal files, depending on device settings, platform behaviour, available storage and restoration conditions.
On Android, cloud backup is subject to an approximately 25 MB total per-app limit. A media-rich journal may exceed that limit and may not receive a complete cloud backup. TinyLore cannot guarantee that every record or attachment will return after reinstalling, restoring or changing phones, and it does not provide cross-platform journal transfer.
Device backup, the local ZIP export and Restore Purchase are separate mechanisms. Restore Purchase restores an eligible store entitlement, not journal data.
8. Deleting records and uninstalling
Deleting a record removes its application references and starts the supported cleanup of associated media. A confirmed deletion that was interrupted may finish after restart. When TinyLore cannot establish safely that a file should be removed, it preserves the uncertain file rather than risk deleting the wrong media. Historical untracked files can therefore occasionally remain in app storage; they are not shown in the journal or included in export.
Uninstalling normally removes TinyLore's local app data according to operating-system behaviour. Neither record deletion nor uninstalling removes original gallery files, exported ZIPs, shared copies, device backups or copies held by other apps or people. AEE Studio cannot recover journal records it never received.
9. App Store, Google Play and purchases
TinyLore uses Apple App Store and Google Play billing functionality. Store SDK communication may occur to check availability, show product information and process purchase events. Apple and Google process purchase-related information under their own policies; AEE Studio does not receive your payment-card details. On Android, Play Billing components may retain diagnostic or transport information.
TinyLore does not currently send purchase-verification information to an operational AEE Studio verification backend. If that changes, this policy must be reviewed and updated before the service is enabled.
10. Support email
If you email [email protected], AEE Studio receives the sender address, message and attachments you deliberately include. TinyLore does not automatically attach your journal, photos, purchases or logs. Support email is handled through Google Workspace.
Our operational target is to review support conversations for deletion after 12 months from the last message, subject to unresolved requests and legal record-keeping needs. This is not an automatic deletion guarantee while the deletion routine is still being finalized.
Please do not send passwords, payment details or private media unless they are genuinely needed to resolve the issue.
11. Analytics, advertising and children
The current app does not include a proprietary advertising, analytics or third-party crash-reporting SDK. This does not mean Apple, Google, the operating system or a destination you choose processes no information under its own terms.
TinyLore is not designed for children. If you believe a child has sent personal information to the support mailbox, contact us.
12. Your choices, requests and policy changes
You decide what to add, edit, delete, export and share. For personal information AEE Studio actually receives through support or another implemented service, you may contact [email protected] to request access, correction or deletion. Available rights and exceptions depend on applicable law.
We will review this policy when TinyLore's features, platform services or data handling change. Any future purchase-verification backend must be reflected here before it becomes operational.
Privacy contact: [email protected]