Security & Data Handling
What data is safe to upload during beta?
Section titled “What data is safe to upload during beta?”The beta environment is production-grade in terms of security controls, but we recommend treating it as a pre-production environment until the platform reaches general availability.
Suitable for beta:
- Internal test documents and sample files
- Non-sensitive business documents for workflow validation
- Synthetic or anonymized data for compliance testing
Not recommended during beta:
- Highly sensitive personal data (patient records, financial statements) unless required to test a specific workflow
- Credentials or secrets of any kind
- Data subject to regulatory holds or litigation
If your use case requires handling sensitive data during beta, contact the Claryn team first so we can review together.
Storage
Section titled “Storage”By default, Claryn uses its own managed storage during beta. You can also connect your own storage bucket (AWS S3, Cloudflare R2, Google Cloud Storage, or Azure Blob Storage). Customer-managed storage means your files never leave your own infrastructure. See Storage Connections.
Encryption
Section titled “Encryption”All data is encrypted in transit (TLS 1.2+) and at rest. Personally identifiable information (PII) in the database is encrypted at the field level.
Access controls
Section titled “Access controls”Access to your organization’s data is restricted to members you explicitly invite. Claryn staff access to customer data is logged, audited, and limited to support purposes.
Security contact
Section titled “Security contact”To report a security vulnerability or concern, contact [email protected]. See Incident Response for the full process.