Least privilege
Products should request only the capabilities needed for the task. Where practical, reading, editing, publishing and destructive actions are separated.
Security is treated as part of product design, not as a feature added after the workflow is built.
Products should request only the capabilities needed for the task. Where practical, reading, editing, publishing and destructive actions are separated.
Supported integrations use scoped credentials and authorization flows instead of asking users to hand AI systems a primary website password.
Access should be removable without changing the site owner’s core login credentials.
Administrative actions should leave enough information for the site owner to understand what happened and when.
Higher-risk actions should not be silently bundled into routine content permissions.
If you believe you found a security issue, use the support form and select Security issue. Include enough detail to reproduce the problem without sending passwords or secret keys.