Protection and access
HTTPS / TLS. The public site is intended to be served over HTTPS. Transport security settings will be reviewed again before any connected product is released.
Encryption. Sensitive data should be encrypted in transit and at rest where it is stored. The final implementation details will be documented before production use.
Credential protection. Credentials and secrets must not be committed to source control or exposed in client-side code. They will be held in a managed secret environment when integrations exist.
OAuth token protection. Any future OAuth tokens will be treated as sensitive credentials, stored server-side where appropriate, scoped to the minimum required access, and protected through rotation and revocation processes.
Least privilege. Future integrations will request only the permissions required for a clearly defined feature.
Tenant isolation. If multi-user services are introduced, account and marketplace data must be isolated by tenant with tests covering cross-tenant access boundaries.
Access control. Administrative access will require explicit role assignment, strong authentication, and periodic review.
Detection and response
Audit logging. Security-relevant access and configuration events should be logged with enough context for investigation, while avoiding unnecessary sensitive data.
Incident response. A written response process will define triage, containment, communication, recovery, and post-incident review before any public connected service launches.
Credential rotation. Integration credentials and tokens should have a documented rotation and revocation path.
Data lifecycle
Data retention. Data should be kept only for as long as it supports a defined product or legal purpose. Retention periods will be confirmed for each data category.
Data deletion. Users will have a clear path to request deletion of stored connection information and marketplace data. See the data deletion page.
Backup. Any future backups must use access controls and retention limits consistent with the source data.
Vulnerability management. Dependencies, configuration, and exposed surfaces will be reviewed as the implementation matures. Material issues will be triaged and addressed according to risk.