Your family’s story deserves thoughtful protection.

01 · What we handle

Information we process

Journal and family information

You may add a child’s name, birth or expected-birth date, gender, photos, audio recordings, videos, written entries, milestones, and other family memories. Little Forever stores a local copy on your device. When cloud features are available and you use an account, journal records and media may also be uploaded to Firebase for synchronization and restoration.

Account information

If you sign in with Google, Google and Firebase Authentication process information such as your account identifier, display name, email address, and profile photo. If you continue as a guest, Firebase may create an anonymous account identifier. We use these identifiers to keep each account’s information separate.

Invitations and guest messages

When you create a welcome or birthday invitation, Little Forever generates a hard-to-guess link that currently expires after 30 days and can be revoked. The link contains a limited snapshot chosen for that invitation, such as a child’s first name, thumbnail, headline, and selected birth details. It does not provide access to the full private journal.

Someone using a valid invitation link may submit their name, relationship, and a welcome message or birthday wish. That response is stored for the journal owner. Anyone with the link can view its snapshot while it is active, so treat it like a private invitation.

Name discovery

If you use name discovery, the Names service processes the search terms and preferences you submit, which may include language, region, cultural tradition, meaning, sound, and gender usage. Little Forever does not infer your religion, ethnicity, or culture. Correction reports may require an authenticated account so we can prevent abuse and follow up on a report.

Analytics, diagnostics, and notifications

Firebase Analytics helps us understand product journeys, such as onboarding completion, feature use, saving a first memory, or sharing an invitation. Analytics events are designed not to include journal text, message text, children’s names, photos, or recordings as event values.

Firebase Crashlytics may receive crash details, app version, device model, operating-system information, diagnostic state, and identifiers needed to investigate failures. If you enable notifications, Firebase Cloud Messaging processes a device notification token and delivery-related information. The website may also use Google Analytics. If you join the iOS launch list, we store your email address, signup source, consent record, and unsubscribe token only to manage that notification.

Device permissions and local settings

With your permission, the app can use the camera, photo or file library, microphone, notifications, and related device capabilities needed for the feature you choose. Theme, onboarding, widget, reminder, and other preferences may be stored locally on your device. The Android home-screen widget may display the child name or date you choose; you can hide the name in widget settings.

02 · Why it is needed

How we use information

We process information to:

• provide the journal, backup, sync, export, widget, reminders, invitations, messages, and name-discovery features you request;
• authenticate accounts and keep one family’s records separate from another’s;
• deliver notifications you enable;
• understand whether important product journeys work and improve the experience;
• diagnose crashes, secure the service, prevent abuse, and enforce limits; and
• respond to support, privacy, or legal requests.

Depending on where you live, our legal basis may be performing the service you requested, your consent, our legitimate interests in operating and improving a safe service, or compliance with law. You can withdraw consent for optional device permissions through your device settings.

03 · Who helps us

Sharing and service providers

We disclose information only as needed to operate features, follow your instructions, protect the service, or comply with law. Our current service providers include Google services such as Firebase Authentication, Cloud Firestore, Cloud Storage, Analytics, Crashlytics, App Check, Cloud Messaging, Google Sign-In, and Google Play Services. The website may use hosting, database, analytics, and email-delivery providers.

When you export or share through another app, that app and the people you choose may receive a copy. Recipients can save, copy, or forward invitation content, and we cannot control information after it has been copied outside Little Forever.

We may disclose information if reasonably necessary to comply with valid legal process, protect users or the public, investigate fraud or security issues, or as part of a business transaction subject to appropriate safeguards. We do not sell personal information.

04 · Your controls

Your privacy choices and rights

You can choose whether to add optional media, link a Google account, enable notifications, show a name on a widget, create an invitation, or join the iOS launch list. You can leave that list at any time using the unsubscribe link in its confirmation email. In the app, you can edit or delete journal content, revoke active share links, export a copy, and delete your account and data.

Depending on your location, you may also have rights to request access, correction, deletion, restriction, objection, or portability of personal information, and to withdraw consent or complain to your local data-protection authority. Some rights can be limited where the law permits. Contact us to make a request; we may need to verify that you control the relevant account.

05 · How long it stays

Retention and deletion

Local information remains on your device until you remove it, clear app data, or uninstall the app. Cloud journal information generally remains while the account exists unless you delete it sooner. Invitation snapshots remain available until they expire, are revoked, or their owner deletes the account. Guest messages remain in the owner’s journal until deleted or the account is deleted. Analytics and diagnostics follow the retention settings of the relevant Google service.

Uninstalling removes local app data but does not by itself delete cloud data. Use Delete Account & Data before uninstalling if you also want account-owned cloud data removed. Limited information may remain temporarily in backups, security records, or where retention is required by law; it is isolated or deleted according to the provider’s normal lifecycle.

06 · Built for caregivers

Children’s privacy

Little Forever is intended for parents and adult caregivers, not for children to use independently. Adults decide what information about a child to record and share. We do not knowingly ask children under 13—or the higher minimum age in their country—to create an account or submit personal information directly.

If you believe a child submitted information without appropriate adult authorization, contact us. We will investigate and take appropriate steps, including deletion where required.

07 · Around the world

International processing

Little Forever may be used from different countries. Our providers may process information in countries other than the one where you live, including locations where data-protection rules differ. Where required, we and our providers rely on recognized transfer safeguards or other lawful mechanisms.

08 · Protection

How we protect information

We use technical and organizational safeguards appropriate to the service, including authenticated access controls for private cloud records, encrypted network connections provided by our platforms, Firebase App Check where configured, limited invitation snapshots, expiring share links, and account-scoped deletion.

No storage or transmission method is completely secure. Protect your device and Google account, keep exported files safe, and share invitation links only with people you trust.

09 · Keeping this current

Changes and contact

We may update this policy when Little Forever changes or when legal requirements evolve. We will revise the effective date and provide additional notice when required. The version posted here is the current policy.