Data & Trust

Last updated: June 2026

Memephant is designed to turn project context into user-controlled handoffs. The important boundary is simple: Memephant prepares context locally where possible; you decide when to copy, sync, sign in, or publish.

Local-first project storage

Project memory starts on your device. Desktop data is stored in local app data; web/PWA data can use browser storage.

User-controlled exports

Context Passport and Launch Studio outputs are copied, exported, or shared only when you choose an action.

Optional cloud sync

Cloud Backup requires sign-in and stores cloud-safe project rows in Supabase for sync.

Review before sharing

Redaction is pattern-based and helpful, not magic. Review exports before sending them anywhere.

Data flow

Project context Stored locally first as project memory, settings, checkpoints, and structured fields.

Cloud sync enabled Cloud-safe project data is transmitted to Supabase and linked to the signed-in user.

Login Handled by Supabase Auth. Google OAuth is handled through Google and Supabase where configured.

Billing Handled through Stripe-hosted checkout, customer portal, and subscription webhooks where paid plans are available.

Context Passport Generated for review and copied only when you choose. Nothing is sent to another AI unless you copy/paste it.

Social Bridge Opens manual composer/share links. Memephant does not auto-post or store social access tokens.

Export boundary

Memephant formats exports for AI handoff and launch/social workflows. The app includes deterministic redaction for known secret patterns and local path handling. This is designed to reduce accidental sharing of obvious secrets, but it may not catch every sensitive phrase, proprietary detail, personal data item, or unusual credential format.

Before sharing an export, read it. You control what leaves Memephant.

What Memephant does not do by default

It does not send project content to ChatGPT, Claude, Gemini, Grok, Perplexity, or other AI platforms automatically.
It does not auto-post to social networks.
It does not store OAuth tokens for social platforms.
It does not require product analytics to use the app. Production web may use anonymous product usage event names when configured; desktop and local development stay analytics-off.
It does not rewrite your project memory silently.

Current limits

Cloud sync is optional, but when enabled it depends on Supabase and internet availability.
Pattern-based sanitisation is not a substitute for human review.
Exports copied into third-party tools are then governed by those tools' policies.
Crash reporting, if enabled, depends on a third-party provider and is intended for diagnostics.
Billing, where available, depends on Stripe-hosted flows.

Read the Privacy Policy, Terms of Service, and Refund / Billing Policy.

Data & Trust

Local-first project storage

User-controlled exports

Optional cloud sync

Review before sharing

Data flow

Export boundary

What Memephant does not do by default

Current limits

Related pages