Principles · Privacy
Your life is not raw material.
Pamplemousse holds information that can be deeply personal: commitments, relationships, routines, notes, and plans. That deserves plain explanations, restrained data use, and no promises that run ahead of the product.
This page is not a privacy policy. It describes the posture Pamplemousse is being built to. A formal notice covering data categories, processors, retention, deletion and how to make a privacy request should be published before availability widens beyond a controlled beta.
Collect for a reason
Pamplemousse processes the information needed to provide the service.
That may include account information such as your name and email address; the content you add to your workspace; preferences and settings; and operational information needed to maintain access and diagnose problems. If you request an invitation, the email address you submit is stored so the request can be reviewed.
The principle is straightforward: every category of information should have an identifiable product or operational purpose.
Purpose before collection.If information does not have a clear job, Pamplemousse should not ask for it.
Personal data is not the business model
Pamplemousse is not being built around advertising or the sale of personal information.
That statement should be understood as a product and business commitment, not as a substitute for a complete privacy policy. Before broader availability, Pamplemousse should publish precise terms covering data categories, processors, retention, deletion, legal bases where applicable, and how to make a privacy request.
Earn value from the product, not the person’s private context.
Be exact about AI
Zest can use an external AI service to phrase a small set of already-ranked signals. The current implementation prepares a structured payload containing the active mode, aggregate counts, and up to three selected signals. Those signals can include a subject, supporting evidence, and a suggested action.
That is substantially narrower than sending the entire workspace, but it is still user-derived information. It should not be described as anonymous, zero-knowledge, or incapable of containing sensitive text.
AI-supported Zest can be disabled by user or workspace settings. When external AI is disabled or unavailable, Pamplemousse can return deterministic suggestions without sending the request to the AI gateway.
Minimize before transmitting.Send the smallest useful context, explain what it contains, and provide a path that does not require external AI.
Name the services involved
Pamplemousse does not run on its own hardware. The application and database are hosted with external infrastructure providers, product analytics are collected by a first-party-hosted analytics service, Zest requests can be routed through an AI gateway to a configured model provider, sign-in is handled through an identity provider, and transactional email is sent through a delivery provider.
Each of those may process limited technical or product information according to its own terms and configuration. A production privacy notice should name each processor actually in use, describe its role, and link to the applicable policy. Privacy is clearer when “third parties” are not left as an abstraction — and that list is worth publishing once, accurately, rather than early and out of date.
A short, specific list is better than a broad reassurance.
Make retention and control real
Pamplemousse has settings for retention-related policies, but the current help content states that some saved policies are not yet enforced. Those controls should not be marketed as active deletion guarantees until their behavior has been implemented and tested.
The private beta should use this period to establish practical answers to basic questions: how someone requests a copy of their information, how an account or workspace is deleted, what remains in backups, and how long invite requests and operational records are kept.
A control is not a control until it works.Settings, policies, and promises should describe actual behavior, not future intent.
Privacy should become clearer as the product grows.
Pamplemousse is in private beta. Questions about how information is handled are welcome before you request access.