Private beta · effective 11 July 2026

Privacy and No-PHI Notice

Synsigra minimizes account and operational data and is designed for synthetic engineering inputs only.

What is processed

Account email and display name; salted password hashes; session and API-key hashes; organization, project, job, usage and quota metadata; synthetic scenario drafts and custom-pack descriptions; generated packages; and limited method/route/status/duration and worker-event logs.

Why

To secure accounts, deliver account email, generate and retain requested packages, enforce quotas, diagnose failures, protect the service and provide beta support. Personal data is not sold and there is no advertising or patient-level automated decision-making.

No-PHI rule

Do not submit PHI, real patient data, patient identifiers, medical records, clinical notes, real-person waveforms or annotations, or another person's personal data. The beta is not offered as a HIPAA business-associate service and no BAA is provided.

Retention and infrastructure

Generated artifacts are normally cached for 7 days. Reproducibility metadata, immutable pack recipes, and exact generator releases may remain after expiry so Synsigra can prepare a fingerprint-verified rebuild when the user downloads again. Account and security records are retained while needed to operate and protect the beta. Data is processed on the service VPS and by required hosting, DNS and Gmail SMTP providers. Essential secure session cookies are used; advertising and cross-site tracking cookies are not.

Requests and support

Eligible jobs, drafts, custom packs and API keys can be deleted in the product. Account access, correction or deletion requests may be started through the public support tracker. Use only the minimum account identifier needed to arrange a non-public follow-up; never post sensitive information.

Private Beta Terms · Support & service expectations · Back to account