Privacy and security
The practical privacy, provider-key, local-first, and approval-gate model behind FluxonLab.
FluxonLab is designed for European data expectations and practical operator safety. The exact implementation differs by product, but the principles stay consistent.
Baseline rules
- Public site fonts are self-hosted.
- Provider keys are used server-side or locally, never exposed in browser code.
- Local-first products keep their working data on the user’s machine unless an integration is explicitly configured.
- Mutations against external systems need approval gates.
- Logs and manifests redact secrets and store variable names instead of values.
Provider keys
Products that call AI providers name the required environment variables or settings without printing values. If a key is missing, the product fails with a clear setup message rather than silently switching to an unsafe path.
Accounts, credits and the ledger
Membership access and FC credits are granted only by the verified server-side ledger, never by a browser state or a checkout return page. FC lots stay separated by source and eligible use, and they are never cash or a transferable balance. See FluxCore.
Local-first data
Products designed local-first — such as Nisaba and Obsermania when they open — keep the default working copy, history and operator decisions under the user’s control. That does not mean they never connect to external services; it means nothing leaves your machine without an explicit integration.
Demo requests
The free demo request form stores request details on approved EU systems, under the retention and deletion rules in our privacy policy. A human reviews every request; nothing is auto-published.
Approval gates
Approval gates are required when an action can send a message, mutate a website, publish content, change production data, or spend money. Automation can prepare the action; the operator approves it.
Reporting security issues
If you find a vulnerability, contact us privately first through Support. Include the product name, affected version or URL, reproduction steps, and impact. Do not include secrets in the initial report.