docs: clarify data access and deletion, remove encrypted sandbox pricing - #51
Merged
Merged
Conversation
polly3223
marked this pull request as ready for review
September 14, 2026 12:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the unsupported “Encrypted sandbox” Enterprise pricing claim and its repeated mention in the pricing-page answer. Adds two approved FAQs explaining connected-app data access, encrypted inference versus runtime access controls, customer-cloud deployment options, and deletion of all account-associated data. Links to
/deployment-models.Validation:
bun run buildpasses, including TypeScript and static export;git diff --checkpasses.Review note: SOC 2 Type II status and the complete account-deletion statement are owner-supplied product claims. This documentation change does not implement or independently verify deletion across all stores, backups, or retained records; confirm the wording matches release behavior before publication.