Privacy Policy

Last updated: June 2026

This page is a plain-English privacy summary for Memephant. It is not legal advice and should be reviewed by a qualified professional before wider commercial launch.

Memephant is designed as a local-first project continuity app. Its core purpose is to help you store project context and copy user-approved handoffs into the AI tools you choose.

What is stored locally

Memephant stores project memory you enter or generate inside the app, including project names, summaries, goals, decisions, notes, current state, changelog entries, workflow settings, export checkpoints, Project Blueprint data, Launch Studio fields, and app settings.

In the desktop app, project files are stored in your operating system's application data folder as local project data. In the web/PWA version, project data and settings may be stored in browser storage for the active origin. Local settings may also include feature preferences, privacy settings, and Supabase auth session data after sign-in.

What may leave your device

Memephant does not send project context to another AI automatically. Data may leave your device when you choose or use features such as:

Supabase, auth, and cloud backup

Memephant uses Supabase for optional account authentication, Google OAuth sign-in where configured, cloud project sync, subscription lookup, account deletion, and email update subscriptions. If Cloud Backup is enabled, project rows are saved to Supabase and associated with your authenticated user account. Cloud sync attempts to redact obvious local paths and secrets before upload, but you should still avoid storing secrets in project memory.

Stripe billing

Stripe is integrated for hosted checkout, customer portal, subscription webhooks, invoices, and payment method handling where paid features are available. Memephant does not intentionally store full card details. Stripe may receive account, billing, customer, invoice, subscription, and payment information needed to process billing.

Google OAuth

If you sign in with Google, the OAuth flow is handled through Google and Supabase Auth. Memephant receives the authenticated Supabase session and basic account details needed to sign you in, such as a user ID and email address.

AI processing

Memephant does not intentionally call hosted AI APIs for the core Context Passport, Launch Studio, Build Update, Daily Content Pack, or Project Blueprint features. Exports are generated locally and are copied only when you choose. Optional Local AI/Private Mode may call a local Ollama endpoint you configure on your device.

Crash reporting and telemetry

The production web app may send anonymous product usage event names through PostHog when product analytics are configured. These events are used to understand product usage and do not include project content, project names, summaries, goals, changelog entries, Context Passport contents, Memory Vault contents, file paths, prompts, AI responses, user email, or user ID. Product analytics are disabled in Tauri desktop builds and local development. Optional crash reporting is disabled by default and controlled in Settings.

Your controls

Contact

Privacy, access, billing, or deletion questions can be sent to hello@memephant.com. If that address changes before wider launch, this page should be updated.