Last updated · August 30, 2026

Privacy, explained
by data boundary.

Molsim is local-first. This notice explains what stays on your computer and what is sent when you choose research-list updates, the optional Assistant, an online account, billing, or a remote service.

Local research work

Community workflows can run without an account. Project inputs, simulation outputs, run history, and reproducibility artifacts remain on the computer or infrastructure you choose unless you explicitly submit work to a remote provider.

The current website does not use advertising trackers or behavioral analytics.

Research list

When you join the optional research list, Molsim stores your name, email address, role, organization when supplied, primary simulation use case, compute environment, and your consent record. If the signup link contains campaign parameters, Molsim also stores the source, medium, and campaign labels so we can understand which outreach led to the request. It does not add behavioral tracking.

We use this information to prioritize product work and send beta release notes, research-interview requests, or product updates. Do not submit structures, sequences, unpublished results, credentials, or other confidential research data through this form.

Optional Assistant

If you configure the Assistant, the context categories you select—such as project metadata, run summaries, structured-result excerpts, compute readiness, or input locations—are sent directly from your desktop to your chosen model provider under that provider’s terms. Molsim Cloud does not proxy Assistant prompts. Provider credentials remain in the operating-system keychain.

Review the context selection before sending it. Do not send confidential research data to a provider unless you are authorized to do so and its terms meet your requirements.

Account data

When you sign in, the account service processes your email address, identity-provider subject identifier, display name when supplied, plan, session records, and entitlement status. Passwordless email codes are short-lived and stored only as protected digests. Desktop refresh tokens belong in the operating-system keychain.

Service records

Security and billing events may be retained to prevent replay, reconcile subscriptions, diagnose failures, and protect the service.

Billing

Stripe processes checkout and payment details. Molsim stores the Stripe customer reference and subscription/entitlement state needed to provide access; the website does not receive or store full card numbers.

Your control

You may use local Community workflows without creating an account. To request access to, correction of, or deletion of account data, email privacy@molsim.app. Some records may be retained when required for security, billing reconciliation, or legal obligations.

Contact

Questions, unsubscribe requests, and requests to access, correct, or delete beta data: privacy@molsim.app. This notice covers the public technical beta; commercial or institution-specific terms may require additional review.