Privacy & security at Joring
Confidence starts
with control.
Security for your business. Privacy for your people. Practical controls over how your information is collected, protected, and accessed.
Room to move.
Boundaries that matter.
Encrypted in transit and at rest.
TLS 1.3 protects data in transit. AES-256-GCM encrypts captured content at rest, with a separate encryption key for each workspace.
- At rest
- AES-256-GCM
- In transit
- TLS 1.3
- Key management
- AWS KMS
AWS Key Management Service (KMS) safeguards root encryption keys in hardware security modules (HSMs). Enterprise customers can bring their own AWS KMS key.
You decide what is collected.
Collect AI activity for your whole team, choose specific members, or turn collection off. Adjust individual settings as your team’s needs change.
Give access to the right people.
Team permissions, single sign-on through SAML or OIDC, and SCIM provisioning support the way your business manages access.
Your activity, on your terms.
View, export, or delete your personal activity history. Authorized admins can review team usage and policy events, which may include prompt excerpts.
Keep a record of important changes.
Audit logs help your team review administrative activity, policy changes, and access decisions.
Put your AI policies into practice.
Define rules for covered AI activity, review policy events, and choose when to guide, warn, or block a submission.
Security assurance
SOC 2 compliant.
Review our security controls, policies, and compliance information in the Joring Trust Center. Clear information to help you make an informed decision.
Visit our Trust CenterA conversation about your requirements
Clear answers.
An informed decision.
We’ll walk through your deployment, data collection settings, access requirements, and the AI tools you need to cover. Features and controls vary by plan and configuration.
For a security review or a suspected vulnerability, contact our team. Please avoid including sensitive customer information in your first message.
Contact Joring