Life Written

Privacy Policy for Life Written

Last updated: June 12, 2026

Effective date: June 12, 2026

1. Introduction and Who We Are

This Privacy Policy explains how personal information is collected, used, shared, and protected in connection with Life Written (the "App"), a personal journaling application for iOS (with an Android package also configured).

The App is provided by Lilac Impact Ventures LLC, a Delaware limited liability company based in the United States, with a mailing address at 131 Continental Drive, Suite 305, Newark, DE ("we," "us," "our," or the "Operator"). We are the controller of the personal information described in this Policy.

By creating an account or using the App, you ("you" or the "User") acknowledge the practices described here. If you do not agree, please do not use the App.

Plain-English summary (not a substitute for the full Policy): Life Written stores your journal entries and photos on cloud infrastructure. Your journals are private to your account but are NOT end-to-end encrypted — they are readable by our backend and, when you choose to use AI Features, are sent to a third-party AI provider (OpenAI) to generate output. Your voice recordings are highly sensitive. When you use voice input, your recording is sent to OpenAI only to be transcribed into text and is never stored by us — only the resulting text is saved, and only if you keep it in your entry. We do not show ads and do not sell your information. You own your content and can delete entries or your whole account.

2. Defined Terms

• "Account Data" — information tied to your identity: your name, email address, Google account identifier, and Clerk user ID.
• "Journal Content" — the content you create: entry titles, body text, dates, attached photos, and recorded audio.
• "Device/Usage Data" — technical information generated when you use the App (e.g., device type, OS version, app version, IP address, diagnostic/crash data, and feature-usage logs).
• "AI Features" — the Voice transcription, "Clean up," "Storify," template-learning, and suggestion features that send content to a third-party AI provider for processing.
• "Subprocessor" — a third-party service that processes data on our behalf or receives data to provide a feature (listed in Section 6).
• "Special-Category Information" — sensitive information such as that revealing health, mental health, religious or philosophical beliefs, sex life or sexual orientation, racial or ethnic origin, political opinions, or similar categories protected by law.

3. Information We Collect

3.1 Account Data (from you and from Clerk via Google Sign-In)

When you sign in, we use Clerk with Google OAuth. We receive: your name, email address, a Google account identifier, and a Clerk user ID. We do not receive or store your Google password.

3.2 Journal Content (from you)

The core of the App. This includes everything you write or attach: entry titles, body text, entry dates, and photos (from your camera or photo library). When you use voice input, you also create a temporary audio recording, which is processed for transcription only and is not stored by us (see Section 7 for the full audio lifecycle). What we save from voice input is the resulting transcribed text, and only if you keep it in your entry.

Important: Journal Content is highly sensitive by nature. Diary entries commonly contain Special-Category Information — for example details about your health, mental health, relationships, sexuality, religion, or biometric-adjacent material (such as your voice when you use voice input). We treat all Journal Content as confidential to your account. See Sections 5, 7, and 9.

3.3 Device and Usage Data

We (and our infrastructure providers) automatically collect Device/Usage Data such as device model, operating system version, app version, IP address, timestamps, crash and diagnostic logs, and feature-usage events, to operate, secure, and improve the App.

3.4 Permissions You Grant

The App requests the following device permissions, only when needed for a feature:

• Microphone — to record audio for voice input.
• Photo Library — to let you attach existing photos to entries.
• Camera — to let you capture and attach new photos.

You can grant or revoke these in your device settings. Revoking a permission disables the related feature but does not delete content you already saved.

3.5 On-Device Storage

A small amount of data is stored locally on your device's secure storage — specifically, your recently-used template IDs — to improve your experience. This stays on your device.

3.6 We Do Not

We do not show third-party advertising, do not use third-party ad trackers for advertising, and do not sell your personal information.

4. How and Why We Use Information

We use information for the following purposes and legal bases (GDPR bases noted in brackets):

We do not use your Journal Content for advertising, and we do not sell it or use it to train any advertising profile. We do not use your Journal Content to train our own or any third party's general-purpose AI models. See Section 7.

5. Sensitive / Special-Category Information

Because a journal is inherently personal, you may choose to record Special-Category Information. Where the App processes such information, we rely on your explicit consent, which you provide by voluntarily entering that content and (for AI Features) by choosing to use a feature that sends content to our AI Subprocessor.

Your responsibilities and choices:

• You decide what to write, photograph, or record. Please only include Special-Category Information you are comfortable storing on cloud infrastructure that is not end-to-end encrypted.
• You should not include other people's sensitive information without a lawful basis or their consent.
• You can withdraw consent at any time by deleting the relevant content, declining to use AI Features, or deleting your account (Section 8). Withdrawal does not affect processing already carried out.

6. Third-Party Subprocessors

To run the App we share limited data with the Subprocessors below. Each acts under its own terms and privacy policy. We share only what a Subprocessor needs for its function.

Be clear: When you use an AI Feature, your journal text and/or voice recording is transmitted to a third-party AI provider (OpenAI) to generate the requested output. Voice audio is sent only to be transcribed and is not stored by us. If you never use AI Features, your Journal Content is not sent to any AI provider.

These Subprocessors may use their own infrastructure providers. The list may change as the App evolves; material changes will be reflected in this Policy (Section 14).

7. AI Features — What Happens to Your Content

The App offers optional AI Features powered by OpenAI's API platform (Whisper for transcription; GPT-4o / GPT-4o-mini for text features — CONFIRM models).

Voice input — full audio lifecycle (important). When you record voice input, the App captures the audio locally on your device and sends it to our backend (a Cloudflare Worker) for the sole purpose of transcription. The backend holds the audio only transiently in memory, forwards it to OpenAI's Whisper API to be converted to text, and returns that text to the App. The audio recording is never written to our database (Cloudflare D1) or our file storage (Cloudflare R2). We do not persist your voice recordings — not on the device beyond the recording session, and not on our backend. The only thing that may be saved is the resulting transcribed text, and only if you keep it in your entry (stored in D1). If you discard the text, nothing from that voice session is retained by us.

What is sent to OpenAI, and when:

• Voice input: the audio you record is transmitted to OpenAI's Whisper API and converted to text; the audio is not stored by us (see above).
• Clean up: your entry text is sent to OpenAI to be polished (grammar/clarity) and returned.
• Storify: your entry text (and the selected template, including any template you created from your own writing samples) is sent to OpenAI to be rewritten into a narrative. The feature is instructed to stay faithful to your source, but AI output can still differ from your original meaning.
• Template-learning: when you create a template from your own writing samples, those samples are sent to OpenAI so the App can reflect your style.
• Suggestions: relevant entry text may be sent to OpenAI to generate suggestions.

How OpenAI uses it: Data submitted through OpenAI's API platform is processed to generate the output returned to you. OpenAI represents, in its API platform terms and Data Processing Addendum, that data submitted via its API is not used to train its models (unless a customer opts in). We rely on OpenAI's API terms and DPA as in effect and verify this representation at launch; we will update this Policy if those terms change. This is a representation we rely on, not an absolute guarantee we can make on OpenAI's behalf. Your content is transmitted to and processed by OpenAI (a U.S. provider) — it is not kept solely on our infrastructure during processing. Per OpenAI's policies, API inputs are retained only transiently for abuse monitoring/operational purposes and not for training; we verify the applicable retention window at launch and, where eligible given the sensitivity of journal and voice content, may pursue OpenAI's zero-data-retention tier.

Your choice (AI Features are opt-in). AI Features are optional and opt-in. You can write, store, and read journals without using them, in which case no Journal Content (text or audio) is sent to OpenAI. Before the first time any content is sent to OpenAI, the App asks for your affirmative, specific consent to that processing; using an AI Feature thereafter is your affirmative choice and, where required, your consent. No content is sent to OpenAI automatically or in the background without your action.

No professional advice: AI output may be inaccurate or incomplete and is not medical, mental-health, legal, financial, or other professional advice. See the Terms & Conditions.

8. Data Retention and Deletion

Retention. We keep your Account Data and Journal Content for as long as your account is active, and as needed to provide the App, comply with legal obligations, resolve disputes, and enforce our agreements.

Voice recordings are not retained. As described in Section 7, your voice recordings are processed transiently for transcription only and are never stored in our database (D1) or file storage (R2). Only the resulting transcribed text — if you keep it — is retained as part of your entry.

Deleting an entry. You can delete an individual entry (and its attached photos) in the App. Deletion removes it from your active view and is propagated to deletion in our database (D1) and file storage (R2).

Deleting your account. You can request deletion of your entire account and associated Journal Content by [using the in-app account-deletion option / contacting us at team@thelilac.app]. We will delete or de-identify your data, except where retention is required by law or for legitimate security purposes.

Backups. When you delete an entry or your account, the data is removed from our active systems promptly. Deleted data may persist in routine encrypted backups and edge-replicated copies for a limited period — approximately 30 days (this default is adjustable once Cloudflare D1 point-in-time-recovery and R2 deletion timing are confirmed; if the verified window differs, this number will be corrected before publication) — after which it is overwritten or purged in the ordinary course. During that window the data is not used for any active purpose.

Subprocessors. Transient copies held by Subprocessors (e.g., OpenAI processing logs, Clerk auth records) are deleted per their respective retention policies.

9. International Data Transfers

We are based in the United States, and our infrastructure is global. Cloudflare processes and stores data on globally distributed edge infrastructure, and OpenAI processes AI-Feature data in the United States. As a result, your information may be transferred to, stored in, and processed in countries other than your own, including the United States, which may have different data-protection laws than your jurisdiction.

Where we transfer personal information out of the EEA, UK, or Switzerland, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (and the UK Addendum / Swiss equivalents), and/or other lawful transfer mechanisms made available by our Subprocessors. You may request information about these safeguards at team@thelilac.app.

10. Your Privacy Rights

10.1 EEA/UK (GDPR/UK GDPR)

Subject to conditions and exemptions, you have the right to: access your data; rectify inaccurate data; erase data ("right to be forgotten"); restrict processing; object to processing based on legitimate interests; data portability; and to withdraw consent at any time (without affecting prior processing). You also have the right to lodge a complaint with your supervisory authority.

10.2 California (CCPA/CPRA)

California residents have the right to: know what personal information we collect and how it is used and disclosed; access/obtain a copy; delete; correct; and opt out of the "sale" or "sharing" of personal information. We do not "sell" or "share" your personal information as those terms are defined under the CPRA. We use sensitive personal information only to provide the journaling features you request and do not use it to infer characteristics about you or for any purpose that would trigger your "Right to Limit the Use of Sensitive Personal Information"; accordingly we are not required to offer a "Limit" link. You have the right to non-discrimination for exercising your rights. We do not use Journal Content for cross-context behavioral advertising.

10.3 Other U.S. State Laws

Residents of states with comprehensive privacy laws (e.g., Virginia, Colorado, Connecticut, Utah, Texas, and others) may have similar rights to access, correct, delete, and obtain a copy of their data, and to opt out of targeted advertising, sale, or certain profiling. We honor applicable rights.

10.4 How to Exercise Your Rights

Email team@thelilac.app with your request. We will verify your identity (typically via your account email) before acting, respond within the timeframes required by applicable law, and will not discriminate against you for exercising your rights. You may use an authorized agent where the law permits. Some data may be available for direct download or deletion within the App.

11. Children's Privacy and Minimum Age

Minimum age: 13. You must be at least 13 years old to create an account or use the App.

Not for children under 13. The App is not directed to, and is not for use by, children under 13. We do not knowingly collect personal information from anyone under 13. Consistent with the U.S. Children's Online Privacy Protection Act (COPPA), if we learn that we have collected personal information from a child under 13, we will delete that information and terminate the account promptly. If you believe a child under 13 has provided us information, contact team@thelilac.app. By keeping the minimum age at 13, we avoid the App being subject to COPPA's verifiable-parental-consent regime, which applies only to children under 13.

Minors aged 13–17 (parent/guardian consent required). If you are between 13 and 17 (or below the age of legal majority in your jurisdiction), you may use the App only if a parent or legal guardian has reviewed and agreed to our Terms & Conditions and this Privacy Policy on your behalf and consents to the processing described here — including the use of optional AI Features and the storage of potentially sensitive content. By using the App, a minor in this range represents that such parental/guardian review and consent has been given. OpenAI's own policies generally expect users under 18 to have parental or guardian permission to use AI features; our consent posture is designed to reflect that.

EU/UK "age of digital consent." In the EEA and UK, the age at which a person can consent to data processing on their own ("age of digital consent") varies by country between 13 and 16. Where the law of your country sets a higher age than 13, you must meet that higher age or have the consent of the holder of parental responsibility. Where a higher age applies, references above to "13" should be read as that higher applicable age for purposes of self-consent.

12. Security

We use reasonable technical and organizational measures to protect your information, including encryption in transit (HTTPS/TLS), access controls, and reputable infrastructure providers (Cloudflare, Clerk). Data is encrypted at rest by our storage providers in the ordinary course.

Honest limitations — please read:

• The App is NOT end-to-end encrypted and is not "zero-knowledge." Journal Content is readable by our backend in order to provide features, and is transmitted to AI Subprocessors when you use AI Features.
• No method of transmission or storage is 100% secure. We cannot guarantee absolute security, and you provide information at your own risk.

Please keep your Google/Clerk credentials secure; access to your sign-in account is access to your journals.

13. No Sale of Personal Information; No Advertising

We do not sell your personal information, do not share it for cross-context behavioral advertising, and do not display third-party advertising in the App.

14. Changes to This Policy

We may update this Policy as the App evolves or as required by law. We will revise the "Effective date" above and, for material changes, provide a more prominent notice (such as in-app notice). Your continued use after an update means you acknowledge the revised Policy.

15. Contact Us

Lilac Impact Ventures LLC (operator of Life Written)

131 Continental Drive, Suite 305, Newark, DE

Email: team@thelilac.app