Stored for the organization
The GitHub App id, the GitHub App private key, and the webhook secret are runtime configuration on the control plane. They are not columns on your connection.
Not stored
- Temporary AWS keys from
sts:AssumeRole. - GitHub installation access tokens. One is minted when a build starts and is not written down.
- GitHub personal access tokens. The product does not ask for one.
- SQL passwords in the application database. Aurora manages its master secret in your AWS account. For standard RDS, Springwinter generates a password in memory and writes it to Secrets Manager in your account. Credential reads fetch the AWS secret on demand.
- A cache password. The Valkey cache has no AUTH password. Clients in the project use TLS.
- A full CloudWatch log archive. Logs are fetched for display. Selected operational observations, including cached architecture/cost data and project-chat source evidence, can be retained; see Where the data lives.
Environment variables
Runtime variables are stored in ECS task definitions in your AWS account. ECS stores these values as plaintext configuration. Build variables are stored in the CodeBuild project; creation-time build values are temporarily staged in Secrets Manager before being applied and cleaned up. See Environment variables. These forms do not turn a secret ARN into a secret reference automatically. Build values can become part of images, public bundles, or build output. A create or preview can retain supplied runtime values in its workflow run input. Treat that operational history as sensitive data, not as a secret-isolation boundary. Request-log filtering omits environment and build-variable fields. It does not make the deployed values or workflow inputs secret from authorized operators.Database credentials
Aurora manages its master password in Secrets Manager in your account. Standard RDS uses a password that Springwinter generates in memory, stores in your account’s Secrets Manager, and supplies to RDS during creation. Springwinter reads the secret when an authorized user requests credentials and does not store the password in the application database. Springwinter does not configure your application’s database URL or enable automatic password rotation. Use your own application secret-management process. See SQL databases.API tokens
An API token is an organization credential. The plaintext secret is shown once, when it is created. Springwinter storesSHA-256 of the secret and a short prefix so you can recognize the token in the list. A later request is accepted only when the hash matches.
Revoking the token deletes that record. Later requests with the old secret are rejected.