Memoire legal

Privacy Policy

Last updated: October 16, 2026

This policy explains what Memoire stores, what leaves your browser and where it goes. Every claim here describes what the product actually does today, not what it may do later.

Data you provide

Memoire may store account information, pipeline records, activities, stakeholders, objections, quotes, orders, receivables, review briefs, and other content you enter.

Signed in, supported records sync to a database held under your account. Not signed in, Memoire runs on browser storage only, and the app says so inside when it is doing that.

Local and sample data

Local-only and sample records stay in the browser profile where they were created unless you explicitly export or migrate them.

Clearing browser storage, changing browser profiles, or using another device can remove or hide local-only records.

Optional AI chat

Capture and Local insights run on your device without AI. Optional AI chat uses Groq only when it is configured by the operator and you choose to share the previewed context before sending a message.

AI chat sends your question, up to four recent exchanges, selected record summaries and calculated facts through the Memoire server to Groq. Summaries may contain names, prices and other customer information; inspect the preview before sharing. Raw capture notes and attachments are excluded. Source ownership is checked against your signed-in account; displayed values are browser snapshots, not an independent server audit.

Memoire keeps the conversation in page memory for this visit only and does not save chat content to browser storage, its database or application logs. The floating chat keeps its conversation when minimized or when you navigate within the app. Closing and clearing it, changing context, signing out, reloading or starting a new conversation clears it. Groq controls processing and retention on its service; its current policy is published at console.groq.com/docs/your-data. The operator should configure appropriate data controls before enabling chat for confidential records.

Product analytics

Memoire records a short list of product events - for example capture saved, commitment completed, review completed, CSV import completed, sync failed, signup completed.

Each event carries only the event name, a random identifier generated in your browser, the app path you were on with any query string removed, and which storage mode the workspace was in. It carries no notes, no customer or contact names, no deal content, no amounts and no email address.

There is currently no setting to turn these off. Rather than offer a switch that does nothing, we keep the payload small enough that turning it off would protect nothing.

Email digests

The daily digest and the Monday review are off unless you turn them on in Settings, and each can be turned off again there or from the unsubscribe link in any digest.

When they are on, the email is built from your own records and does contain account names and quote titles - that is what makes it useful. It is delivered by a transactional email provider, which necessarily receives the message in order to send it.

Payment

Subscriptions are handled by Lemon Squeezy, which acts as merchant of record. Your card details go to Lemon Squeezy and never reach Memoire; we do not see them, receive them or store them.

Memoire sends Lemon Squeezy your email address and an internal account identifier, and stores back only the customer and subscription identifiers and the resulting entitlement.

Shared workspaces and retired links

The old shared-brief link flow has been retired. Current shared workspaces use owner-selected promises and invitations to authenticated accounts. Their configuration and actor responses are synchronized to the service; this is not an anonymous, browser-only link.

When sharing is configured and synchronized, recipients must accept the current invitation. Reader and reviewer roles grant different access to the selected view; they do not grant access to the owner’s whole workspace. Revocation prevents subsequent authorized reads but cannot erase information someone already viewed or copied. Local and demo configurations do not grant remote access.

Service providers and security

Memoire relies on Supabase for its database and authentication, Vercel for hosting, Lemon Squeezy for subscriptions, a transactional email provider for digests you have enabled, Google for sign-in if you choose to sign in with Google, and Groq for optional AI chat when you explicitly use it.

The database holding synced workspaces runs in Supabase's Mumbai region (ap-south-1). Serving is global: the application itself is delivered from the hosting network's nearest edge, so a request made in Europe or Japan is answered near you while the records themselves stay in that one database region. If you are subject to rules about where your customer data may be stored, read that sentence before you sign in rather than after.

How long it is kept: for as long as the workspace exists. Deleting your account from Settings removes the account and every record keyed to it in the same operation - it is one cascading delete, not a flag that hides your rows. Copies can persist for a short window afterwards in the database provider's own routine backups, which we do not read and cannot selectively edit. Records you never synced live only in the browser you wrote them in, and clearing that browser removes them.

No online service can promise absolute security. Use appropriate judgment before entering sensitive tender, pricing, personal, or regulated information.

Your choices

You can use Memoire without signing in, accepting the limits of browser-only storage; sign out; export your workspace at any time; clear local browser data; turn digests off; or delete your account from Settings, which deletes the account and its records.

Export is never withheld. A lapsed subscription stops you adding to a workspace; it must never stop you taking your own work out of it.

Questions about privacy can be sent to support@memoire-official.com.