Security & Privacy

Your cultivation data belongs in your control.

GeneticRX is designed around account isolation, least-privilege access, explicit authorization, validated input, and secure handling of application data.

Account-scoped data

Workspace and private records are scoped to the active account so one account does not automatically expose its records to another.

Roles & permissions

Role and permission checks separate user and administrator capabilities and govern protected actions.

Server-side validation

Application endpoints validate input on the server rather than trusting browser-side checks alone.

Web attack defenses

The application uses CSRF protection, request validation, rate limits on selected public actions, and browser security headers.

Secure sessions

Authentication and session handling are separated between the user and administrator portals and use secure cookie settings.

Secrets discipline

Known credential and token fields are redacted from security and audit metadata rather than being displayed as ordinary application data.

Explicit integrations

Protected integrations use effective plan or user-entitlement authorization, account-scoped checks, provider configuration, and connection verification before live access is enabled.

Controlled access

Protected administrative and integration actions are separated from ordinary user capabilities and require the appropriate authorization checks.

Release controls

Production promotion uses exact source verification, CI gates, deployment preflight, artifact verification, and post-deploy health checks.

AI & external data

AI and external-data features are kept distinct from your cultivation records so provenance can be represented separately from account-owned observations.

Privacy by defaultData ownership

The platform is designed so that private account data is not automatically exposed to other accounts. External research and AI findings retain source and provenance information so users can distinguish their own records from outside information.

Where information comes fromProvenance

Reference data, your observations, sensor telemetry, and AI analysis are visually and conceptually distinct in every screen. You should be able to tell whether a number came from your sensor, your note, or an outside source.

Have security questions before you start?

We'd rather answer them clearly than vaguely. Ask us anything about the design.

Contact the Team