LifeMap

Privacy Policy

Effective October 22, 2026

This policy describes how LifeMap at inlifemap.com handles information when you browse public LifeMaps, create an account, record your history, or share your story. LifeMap is responsible for the information it processes to provide this service.

1. Information we collect

Account information includes your email, authentication information, profile name, birth date at the precision you choose, profile image, and preferences. Your history may include moments, dates, descriptions, life tracks, chapters, decisions, alternatives, relationships between moments, and imported content. What you write may reveal sensitive information about health, relationships, finances, or other people; only add information you are comfortable storing and entitled to provide.

We also process publication settings, share links, saved profiles, feedback you submit, and technical information such as IP addresses, browser and device information, requests, usage events, and error reports. Authentication passwords are handled by our authentication provider; they are not included in your public profile.

2. How we use information

We use information to authenticate you, save and display your LifeMap, provide imports and exports, apply your sharing choices, send account emails, respond to feedback, protect the service, diagnose failures, and understand usage. We do not sell your private life history or use it to target advertising.

Where applicable privacy law requires a legal basis, we rely on providing the service you request, legitimate interests in security and service improvement, compliance with legal obligations, and consent where required. You may withdraw consent where processing relies on it.

3. Private histories and sharing

Your personal history is private by default. Publishing makes the content selected in Sharing settings available on a public page. Unlisted pages are accessible to anyone with their URL; discoverable pages can also appear in Explore. Eligibility for search indexing requires separate affirmative permission and meaningful permitted public content. Withdrawing that permission makes subsequent responses ineligible for indexing. Public information may still be copied or redistributed by others.

Private share links allow anyone possessing the link to view the included content without signing in. Keep those links confidential and revoke them when needed. Making your public page private does not automatically revoke independent private share links. Hiding content, revoking links, or removing publication cannot erase copies already made by recipients or search engines.

4. Imports and external AI tools

LifeMap lets you paste text and upload files for review before saving proposed moments. Drafts and preferences may be stored in your browser to support recovery. Downloads and exported backups contain your information; keep them secure.

The Generate with AI workflow provides instructions for you to copy into an external tool such as ChatGPT or Claude. Those instructions include your saved name and birth date at the precision you provided. LifeMap does not automatically send your history to those AI tools through this workflow. Information you paste into an external AI conversation is handled under that provider’s terms and privacy policy.

Connected ChatGPT account

When you choose to connect LifeMap to ChatGPT, the connection can return your stable account identity, display name, available life tracks, relevant saved moments and descriptions, date precision, Significance, authored Decision/Project alternatives, and bounded relationship details. Birth date is optional and retains its recorded precision. OpenAI handles information returned to ChatGPT under its own terms and privacy policy. LifeMap does not request entire chat transcripts or silently save conversation information.

When you explicitly request saving facts, ChatGPT can create confirmed moments directly. Requested AI-inferred or reconstructed history is stored as suggestions, awaiting your acceptance in LifeMap and excluded from normal connected history retrieval. Draft means incomplete user-authored work. Deliberate bulk imports retain inline review and final confirmation. Creation receipts retain request, owner/client/session binding and payload hashes for replay protection; Undo capabilities and created-record details expire after ten minutes. Reviewed-import approval payloads expire after fifteen minutes. History clearing invalidates both kinds of outstanding capabilities, and account deletion removes their integration records.

You can revoke the connection in Settings → Account. Revocation immediately stops further private LifeMap reads and writes. It does not remove information already returned to ChatGPT.

5. Cookies, storage and analytics

Optional ChatGPT sign-in

Where available, Continue with ChatGPT lets OpenAI provide a stable sign-in identity, verified email and available basic profile information to LifeMap and Supabase. Supabase manages this sign-in method on your existing LifeMap account. If you already use Google or email, sign in to that account and explicitly link ChatGPT to keep the same history. A different, unlinked ChatGPT account can create a separate LifeMap only after the account-creation choice shown in the sign-in flow.

This sign-in method requests only identity, profile and email permissions. It does not read ChatGPT conversations or give ChatGPT access to LifeMap history. The separate connected-app consent controls that access. Disconnect ChatGPT revokes the history connection, not the linked sign-in method.

A separate encrypted, HttpOnly authentication cookie lasts up to ten minutes and holds only the temporary sign-in transaction, its return destination and, for linking, your account identifier. LifeMap processes OpenAI tokens on the server to verify identity and obtain a Supabase session; it does not persist those tokens or send them to browser code, history records or analytics.

Authentication, security, preferences and draft recovery use essential cookies or storage. Optional Google Analytics 4 marketing measurement, Microsoft Clarity homepage analytics and PostHog product analytics are off until you affirmatively accept them in Analytics choices. Rejecting or withdrawing does not disable sign-in, saving, drafts or other app features. Google Analytics measures visits to allowlisted marketing and account-entry pages and explicit marketing link clicks; it does not measure your private workspace or public LifeMap/share pages. Operational error monitoring through Sentry is separate from optional product analytics and is limited by our diagnostic safeguards.

Analytics choices are separate from Explore visibility, search-indexing permission, photo sharing and connected-app authorization. The versioned preference applies to this browser for 180 days; it does not synchronize across your devices. A global privacy signal keeps optional analytics off. Use Analytics choices on this page to change your decision at any time. Withdrawal stops future optional collection and clears analytics-only browser state; it cannot recall events already delivered.

With permission, PostHog receives explicit usage events and bounded route, device and source categories. A random identifier held for this browser session connects consented visits across our Astro and Next.js pages; withdrawal clears it. Google Analytics receives sanitized public page addresses, a generic page title, fixed source categories and explicit marketing link clicks, without your account identifier. Advertising storage, advertising personalization and Google signals are disabled in our tag configuration. A signed-in account may be identified by its account identifier. Signup, first saved moment and activation are separate conversions; first-moment eligibility applies only to new consented registrations. Events do not include authored history, exact timeline dates, searches, raw landing/referrer URLs, URL queries, public profile slugs, share tokens or arbitrary campaign text. Public profile, share-link and publication-preview pages have no product analytics even after acceptance. Microsoft Clarity may record interactions and session replays on the public homepage, including page content and device information; it does not run in the private workspace or on LifeMap/share pages. PostHog replay and automatic interaction capture remain disabled.

Microsoft Clarity retains data according to its own policies; contact us for access or deletion requests. The browser preference lifetime is not the retention period for delivered analytics events. Google Analytics is configured for two months of event data and fourteen months of user data, without resetting user retention on new activity; aggregated standard reports can remain longer. Our current PostHog plan provides a one-year event query window. That window does not guarantee physical deletion of old events or person profiles; removal uses the provider’s deletion tools. Replay is disabled, so its separate recording-retention setting is not an event-retention promise. Contact us for analytics access or deletion requests; clearing browser preferences alone does not delete provider-held records.

6. Providers and other disclosures

We use service providers to operate LifeMap, including Vercel for hosting, Supabase for authentication, database and file storage, Resend for email, and the measurement and monitoring providers described above. They process information needed for their services. Account signups and feedback may generate internal notifications to the LifeMap team.

We may disclose information when reasonably necessary to comply with law, protect people or the service, investigate abuse, or complete a business transfer subject to applicable privacy protections. Information may be processed outside your country, including in the United States; where required, appropriate transfer safeguards apply.

7. Retention and security

We retain account data while needed to provide your account and service. You can remove moments, clear your history, or delete your account in Settings. Some information may remain temporarily in backups or be retained where necessary for security, dispute resolution, or legal obligations. We do not promise a fixed deletion period for every provider’s backups or logs.

We use access controls, authentication, and encrypted network connections to protect information. No storage or transmission system can guarantee absolute security.

8. Your choices and rights

Settings lets you edit your profile, choose sharing visibility, download JSON or CSV exports, clear history, and delete your account. Sharing settings also let you revoke private links. Depending on your location, you may have rights to access, correct, delete, receive a copy of, restrict, or object to processing of your information, and to complain to your local data protection authority.

9. Children

LifeMap is intended for people aged 18 or older. We do not knowingly collect information from children under 18. If you believe a child has provided information, contact us so we can investigate and remove it where appropriate.

10. Contact and changes

For privacy questions or rights requests, sign in and use the Feedback button, selecting Other and describing your request. Do not include passwords or unnecessary sensitive information. We may need to verify your identity before acting on an account request.

We may update this policy as the service changes. We will update the effective date and give additional notice of material changes where required. See also our Terms of Service.