Privacy, security, and billing

We collect minimal account information required to provide the service: account identifiers, generation job metadata, and billing transactions. Generated molecules and job artifacts are stored in the customer's Supabase project and may be retained to provide history, previews, and downloads. We do not use customer data for training models.

Job artifacts and generated molecules are retained to support the product experience and audits. Administrators may configure retention policies; by default we keep the last three completed generations per account and allow exports. Personal data is retained only as long as necessary to provide the service and comply with legal obligations.

Data is transmitted over TLS and access to storage and database resources is controlled using Supabase authentication and role-based access. Backend services run in isolated processes with least-privilege credentials. Regular backups and monitoring are recommended for production deployments.

Billing is credits-based: one credit equals one downloadable molecule. Top-ups are processed through the configured payment provider via the backend. Refunds and disputes are handled by customer support according to the subscription agreement and payment processor rules.

Users must not use generated molecules for unlawful activity. High-risk use cases should be reviewed under a separate agreement. The platform reserves the right to suspend accounts that violate these terms.

The service integrates with Supabase for storage and authentication and may use third-party payment processors. Their terms and privacy policies also apply.