Privacy
Three separate data paths
MarginCompass is designed around separate data paths for a private-pilot application, authentication for existing pilot access, and product economics.
Pilot application data
The private-pilot application is designed to ask for your name, work email, role, agency name, approximate team-size range, client-work model, approximate number of active client projects, current AI coding environment, the project-level AI cost question you want MarginCompass to answer, and your consent to be contacted about the pilot.
It is not designed to request client names, project financials, source data, credentials, or detailed budgets.
Authentication data
Authentication is designed to use a work email and a one-time code for invited or approved pilot access. Applying for the pilot is separate and does not create an account.
Product economics data
MarginCompass is designed to receive daily aggregated Claude Code usage facts for pricing and project attribution. These facts are designed to include the UTC day, provider-reported model, token-count classes, source type, and a pseudonymous source key.
MarginCompass Connect data boundary
MarginCompass Connect is designed to aggregate Claude Code usage locally. Individual raw events, prompts, responses, source code, diffs, file contents, absolute paths, and vendor credentials are designed to stay out of the server.
Retention
Rights and requests
Controller and contact
MarginCompass is operated by Lotus Web — Julien Fourel, under Swiss law, based in Blonay, Switzerland. Contact: hello@margincompass.io.
Mailing list
An address collected through the public footer is stored to send the notes described in that form — occasional notes on AI project economics for software agencies, sent when there is something specific to report, not on a schedule. The address is used for nothing else and is removed on the one-click unsubscribe carried in every email.
Document control
- Effective date
- Pending
- Last updated
- Pending