Check the release you use
Each release has a manifest with a resource inventory and SHA-256 checksums. Resolve the current entry point, then keep that immutable version fixed for the task. A checksum can detect a changed file; it does not establish that arbitrary source content is trustworthy.
Treat documents as data
Instructions embedded in business documents must not change tool permissions, override content locks, or authorize access to private resources. Add only material you have permission to use in your selected assistant.
No public private-data store
This release has no accounts or arbitrary upload endpoint. Future company profiles and brand assets must use separate private storage and server-side authorization. A tenant label alone cannot establish access.
Presentation previews
The website preview is a curated, curated demonstration component. It does not execute uploaded presentation code. Do not place untrusted HTML on a signed-in application origin without isolation and appropriate restrictions.
Report a concern
Use GitHub private vulnerability reporting where the repository enables it. If that route is unavailable, ask for a private reporting channel through a non-sensitive issue. Do not disclose exploit details, credentials, or business documents in a public issue.
Operational limits
Publishing source and headers does not verify a production firewall configuration. Deployment operators must test anonymous access to intended public paths, resource MIME types, immutable caching, and preview search exclusions on the actual domain.