Identity
Adaptive password hashes, one-time hashed email tokens, revocable database sessions and secure HttpOnly cookies.
Controls that exist today, limitations stated plainly.
TubeBear uses layered access controls for the public account system, protected operator cockpit, credit ledger and internal production services. No certification is claimed.
Request protection
CSRF checks, body limits, durable rate limiting, brute-force controls and non-enumerating recovery responses.
Authorization
Server-side RBAC, separate user ownership checks and an additional perimeter around the operator cockpit.
Credits
Integer balances, row locks, immutable transactions, unique idempotency keys and reserve/capture/release semantics.
Service boundary
Account and production services bind to loopback behind TLS termination. Provider secrets remain in protected server environment files.
Releases
Additive migrations, disposable-database tests, atomic symlinks, health gates, Nginx validation and rollback.
Current limitations
Private beta is not a security certification.
A formal privacy program, retention schedule, subprocessor register, incident policy, external assessment and organization-wide SSO are not yet published.
- No certification claim: no SOC 2, ISO 27001 or similar badge is asserted.
- Email gate: public registration stays paused until transactional delivery is verified.
- Vendor review: provider contracts and data-processing terms require owner review.
- Responsible reporting: use the contact form and do not access data that is not yours.
Security contact
Report securelyFound a vulnerability or privacy concern?
Send a concise report with impact and reproduction steps. Do not include third-party personal data.