Version 1.5.0 · Last updated 2026-10-15

Life Log - Privacy Policy Supplement

Effective Date: October 15, 2026
Last Updated: October 15, 2026

This Privacy Policy Supplement is specific to Life Log and supplements WagDev LLC's general Privacy Policy and Data Security Standards.

1. Life Log Data Collection

1.1 Information You Provide

Basic Account Data:

Life Log Entries (All Users):

Life Log Plus User Data:

Life Log Plus is our subscription tier, referred to elsewhere in this supplement as premium.

1.2 Automatically Collected Data

Life Log collects far less automatically than most apps. There are exactly two automatic flows, and both are described in full below.

Crash, error and performance diagnostics (via Sentry, all users): see Section 1.4.

Advertising (via Google AdMob, free tier only):

Section 1.3 describes this in full.

1.3 Advertising and the Free Tier

The free tier of Life Log is solo and ad-supported. You see a single banner strip anchored above the tab bar. It never covers your entries and never appears over a dialog or modal. Life Log Plus, our subscription, adds cloud sync across your devices and shared logs, and removes advertising. A Plus subscription is the only way to remove ads: there is no standalone ad-removal purchase in Life Log.

When Life Log requests an ad, the embedded Google Mobile Ads SDK collects, on Google's behalf, the identifiers, IP address, ad interactions and diagnostics listed in Section 1.2. Google uses them for advertising, analytics and fraud prevention. That data is governed by Google's privacy policy, and the full disclosure of AdMob data practices appears in Section 4.3 ("Advertising in Some Apps") of the WagDev Privacy Policy, which is incorporated here by reference.

AdMob never receives your entry content. Entry text and descriptions are never handed to the ad SDK. Nothing you write in Life Log is used to select, target, or measure an ad. Neither are your entry dates, titles, categories, tags, or moods.

Ad personalization. Life Log requests non-personalized ads on both platforms. On iOS it presents no App Tracking Transparency prompt, so the advertising identifier stays unavailable to the ad SDK; on Android it asks Google for non-personalized ads regardless of your Ad ID settings. Life Log holds anniversaries, milestones and family memories, so it keeps the tighter posture on purpose, and gives up the higher ad rate that personalization would earn.

Consent in the EEA, the UK and Switzerland. If you are in the European Economic Area, the United Kingdom or Switzerland, Life Log presents Google's User Messaging Platform consent form before it requests a single ad, and nothing is requested from AdMob until you have answered it. The form is shown even where the ads that follow will be non-personalized: serving any ad at all still involves storing or reading information on your device, so choosing non-personalized narrows what is used rather than skipping the question. If you refuse consent, Life Log does not request an ad at all and simply shows no banner. If you are outside these regions, you are never shown a consent form.

Changing or withdrawing your consent. Your first answer is not binding on you. Open Settings and tap Privacy options to bring the same consent form back up at any time, change any choice, or withdraw your consent altogether. A withdrawal takes effect on the next ad request. The Privacy options row appears only if you were shown a consent form in the first place, so it is not there for users outside the EEA, the UK and Switzerland.

1.4 What Sentry Collects for Crash and Error Reporting

To find and fix bugs, Life Log embeds Sentry, a crash, error and performance reporting service operated by Functional Software, Inc. (d/b/a Sentry). Sentry is our only diagnostics processor. Life Log has no analytics SDK at all, which is covered in Section 1.5.

When Life Log crashes, hits a runtime error, or detects that it has become unresponsive, the Sentry SDK transmits:

What Sentry does not receive from Life Log:

Credentials are stripped before anything is sent. Our logging layer replaces the value of any field named like a password, token, key, credential or cookie with [REDACTED] before a log entry reaches Sentry or any other destination.

On linkage, stated plainly. Because diagnostic context can carry your account identifier, we treat Life Log's crash, performance and other diagnostic data as linked to you in our App Store privacy declarations, and we do not claim that it is anonymous. It is never used to track you across other companies' apps or websites.

Sentry data is retained per Sentry's data retention policy and governed by Sentry's privacy policy. The full disclosure of how WagDev uses Sentry across apps appears in Section 4.2 ("Service Providers") of the WagDev Privacy Policy.

1.5 What Life Log Does Not Collect

This list is here because an earlier version of this supplement described two things Life Log does not actually do. Both are corrected as of version 1.5.0.

2. How Life Log Uses Your Data

2.1 Core Functionality

2.2 Service Improvement

We do not profile how you use Life Log for product analysis. There is no analytics SDK to do it with (Section 1.5).

3. Data Sharing Specifics

3.1 Group Log Sharing (Premium)

3.2 Third-Party Services

Firebase (Google):

Sentry (Functional Software, Inc.):

Apple (Sign in with Apple):

RevenueCat (Subscription Management):

Google AdMob and Google's User Messaging Platform (Advertising, free tier only):

Apple App Store and Google Play (Payments):

3.3 What We Don't Share

Some US state privacy laws treat personalized advertising as a "sale" or a "share" of personal information. Where those laws apply, Google's consent form carries a "Do Not Sell or Share My Personal Information" choice, reachable at any time through Settings, then Privacy options.

4. Your Privacy Controls

4.1 In-App Controls

4.2 Data Portability

4.3 Deletion Rights

4.4 Advertising Controls

5. Data Retention

5.1 Active Accounts

5.2 After Deletion

When you delete a single entry. It is removed from view in the app immediately. On the free tier, where nothing was ever sent to us, that is the whole story. On Life Log Plus, the synced copy is marked as deleted instead of being erased at that moment, because that marker is how your other devices learn the entry is gone. While it is marked, the document still holds the encrypted content from the last time it synced. It is purged automatically 180 days after you delete it, by a retention rule on our database, and the copy on each of your devices is cleared after 90 days.

When you delete your account. Your encryption key is destroyed first, which makes every synced copy of your content unreadable to anyone, us included, from that moment on. Your entries and categories are then deleted outright, along with your profile, preferences, sync records and subscription record. Nothing is left that could be read.

What we keep after an account is deleted, and why:

What we cannot remove:

The deletion page at legal.wag.dev/life-log/data-deletion sets this out in more detail.

5.3 Subscription Changes

6. Children's Privacy

Life Log is not intended for children under 13. If we learn a child under 13 has created an account:

7. Security Measures

Life Log implements security through:

See our Data Security Standards for complete details.

8. Location Information

9. Marketing and Communications

9.1 What We Send

9.2 What We Don't Send

This section is about messages we send you. It is separate from the in-app banner advertising shown to free-tier users, which is described in Section 1.3.

10. Encryption and Data Security

This section explains, in plain language, how Life Log encrypts your content and, just as importantly, what our encryption does not do.

10.1 The Two Layers, and Which One You Get

Life Log protects your entries in two different ways, with two different keys. Which ones apply to you depends on whether your entries ever leave your device.

On your device, for everyone. Life Log's local database is encrypted as a whole file, using a 256-bit key that is generated on your device the first time you open the app and kept in the operating system's own secure storage (the iOS Keychain or the Android Keystore). That key never leaves your device and we never receive it. If your entries never leave your device, which is the case on the free tier, this is the only encryption that applies to them, and we hold no key to it.

In our cloud, for Life Log Plus. When you sync or share an entry, the parts of it that are your own words (the title, the description, the tags, and the names of your categories) are encrypted before they are written to our cloud:

10.2 What This Is, and What It Is Not

We want to be clear and not overstate our protections.

10.3 What Is Not Encrypted (Metadata)

Encryption of individual fields applies to the words you write. Certain metadata is stored in our cloud in plaintext (unencrypted) so the app can function, including:

This means that, even though the words in your entries are encrypted, information about the existence, timing, dates, mood, categorization, and grouping of your synced entries is stored in readable form. The mood is listed explicitly because it is the one piece of metadata that carries a feeling rather than a structure, and we would rather name it than let it hide inside "similar metadata."

10.4 Summary of What We Can and Cannot See

For more on our overall security practices and operator access controls, see our Data Security Standards.

11. Privacy Contact

For Life Log privacy questions:

For urgent privacy concerns:

This Privacy Policy Supplement should be read together with WagDev LLC's general Privacy Policy and Data Security Standards for a complete understanding of our privacy practices.