Skip to content

Improve compliance section from going to production #3389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zknill merged 1 commit into from
May 28, 2026
Merged

Improve compliance section from going to production #3389

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions src/pages/docs/ai-transport/going-to-production.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,13 +61,12 @@ If you persist conversations beyond the channel's retention:

## Compliance <a id="compliance"/>
Comment thread
zknill marked this conversation as resolved.

Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](https://ably.com/security) for the current certifications and how to enable HIPAA-eligible workloads.
Copy link
Copy Markdown
Contributor

@rainbowFi rainbowFi May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](https://ably.com/security) for the current certifications and how to enable HIPAA-eligible workloads.
Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](https://ably.com/security) for further information.

Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](/security-and-compliance) for more information.

For application-side compliance:
For the application-side:

- Log message metadata (turn IDs, client IDs, timestamps), not message contents, by default. Surface content logs through an opt-in path with the right retention.
- Treat tool inputs and outputs as conversation content. They are visible to every subscriber by capability.
- For region-pinned data residency, scope capabilities to namespaces hosted in the right region. See [Ably's data residency](/docs/platform/architecture/regions).
- Message content, including tool inputs and outputs are conversation content. They are visible to every subscriber by capability.
- For region-pinned data residency, scope capabilities to namespaces hosted in the right region. See [Ably's edge network](/docs/platform/architecture/edge-network).

## Deployment notes <a id="deployment"/>

Expand Down