Skip to main content
Security

Specific controls. No magic words.

Security claims should tell you what is protected, how, and where the boundary ends. Here is what Gibon can support with current engineering evidence.

Current controls

How Gibon protects studio information

These are the controls supported by current engineering evidence. Each one has a defined scope, because security copy should be more useful than a row of impressive-looking badges.

Studio access boundaries

Access to studio records is enforced on the server using the signed-in user, active studio membership, role, studio status, and section permissions. Student and family queries are scoped to the active studio. A guessed identifier from another studio is not authorization.

Passwords and selected credentials

Passwords are hashed with bcrypt. Selected service credentials, including tenant Stripe secrets and scanner recovery material, are encrypted with AES-256-GCM before database storage. That statement applies to those selected credentials, not every field in the platform.

Payments

Payment card details are handled by Stripe rather than stored by Gibon. Gibon stores provider identifiers, payment status, and limited billing metadata needed to connect studio operations to Stripe.

Development and release checks

Development uses synthetic studio data isolated from production. Releases run repository rules, type checks, unit tests, lint, production builds, dependency checks, and browser tests. Protected release tests exercise separate synthetic studios and verify both allowed actions and denied cross-studio access.

Clear boundaries

What we do not claim

Gibon servers must process rosters, attendance, billing, notifications, exports, and administration to provide the service. We describe specific controls and boundaries instead of promising absolute security, using vague superlatives, or claiming a compliance certification that has not been independently completed and approved for an exact scope.

Report a security concern

Email security concerns to noreply@gibonstudios.com with the affected page or feature and enough detail for us to investigate. Do not include passwords, access tokens, payment card details, or student records in the message.

Bring the requirements. We’ll bring the evidence.

If your studio, school, or procurement team has specific security questions, we will walk through the current controls and the work still in progress.