Last updated 20 September 2026

Your memories
are yours.

Yearshelf does not collect your journal data. OUTWORLD APPS S.R.L. does not receive your writing, book names, photos or settings. There is no account, journal server, advertising SDK or analytics service in the app.

What stays on your device

Book details, entries, photos and settings are kept locally. Journal files and photos are encrypted with AES-256-GCM, with the key held in the platform’s secure storage. An optional app lock helps keep the screen private. It does not replace the need to keep your device secure.

Encryption does not protect a journal that someone can read in an unlocked app, a compromised operating system, or a readable export you give to someone. We do not have a copy of your encryption key and cannot recover a lost journal.

Photos, reminders and device access

You choose which photos to add. Yearshelf does not need your contacts or location. Photo processing happens on the device. The optional daily reminder is scheduled by your operating system and uses general wording, without including your entries. Biometric checks, if enabled, are handled by your operating system; the app does not receive biometric templates.

Backups and exports

Your open Yearshelf backup is a readable ZIP file, not an encrypted archive. It contains book and entry data, readable text and photos. PDFs and share cards are also readable. Anyone with access to one of these files may be able to read its contents. Choose a private destination and share deliberately.

Files stay on the device until you choose a destination through the system file picker or share sheet. If you save to iCloud Drive, Google Drive or another service, that provider handles the file under its own terms. Yearshelf does not receive it. Local backup verification does not establish that your cloud provider has finished uploading it.

There is no automatic journal sync between devices. Keep a separate verified backup before uninstalling Yearshelf, erasing a phone or moving to another phone. A normal operating-system backup may not restore the encryption key on a different device. See the backup guide.

Purchases

Full Shelf is a nonconsumable purchase handled by Apple or Google. They process your payment and store account. Yearshelf uses native store results to determine ownership and caches access locally. We do not receive payment-card details or purchase receipts, and there is no publisher purchase-verification server.

Tracking and diagnostics

Yearshelf does not track you across apps or websites and does not use an advertising identifier. An iOS tracking choice does not enable data collection in Yearshelf. The app has no analytics or third-party crash-reporting SDK. Apple or Google may provide platform diagnostics according to choices you make in their operating systems.

Deleting data

You control the journal on your device. Removing content in the app changes its local data; deleting the app removes app storage, subject to your operating system’s own backup behavior. Copies you exported, shared or saved to other services remain there until you delete them. We cannot remove copies from those destinations.

This website and support

This website has no analytics or advertising scripts and loads its fonts and images locally. Our hosting provider, Microsoft Azure, processes technical data such as IP addresses to serve and secure the site and may use a necessary load-balancing cookie. If you email support, we process your message and email address to answer you. Please do not include private journal files unless they are necessary and you choose to share them.

Audience and contact

Yearshelf is a general journaling app for its adult keeper, including when a book is about a child. It is not part of Apple’s Kids Category or Google Play’s Families program.

Contact support@outworldapps.com · OUTWORLD APPS S.R.L., Romania. You can contact us about personal information in support correspondence or website logs, and you may contact your data protection authority. We will update this policy and store disclosures if our data practices change.