Skip to content

Security Policy

Last updated

Draft, pending legal review. This document describes how the BunonBrain product works today. Highlighted text must still be confirmed by the company or its legal advisers.

This page describes security controls implemented in the BunonBrain application. BunonBrain does not currently hold an independent security certification.

Accounts and sign-in

  • Passwords are stored as salted hashes; nobody, including administrators, can read them.
  • Signing in issues a short-lived access token (15 minutes) held in memory, and an HttpOnly refresh cookie valid for up to 7 days.
  • Sign-in, registration and password-reset requests are rate-limited per IP address.
  • Password-reset links work once and expire after 30 minutes; using one signs out other sessions.
  • Deactivating an account ends all of its sessions immediately.

Authorisation

  • Every API endpoint declares the permission it requires; requests without it are refused.
  • Data is scoped by factory and, for supervisors, by production line.
  • High-risk approvals require a separate permission.

Audit

Approval decisions and administrative changes are written to an audit log in the same database transaction as the change. The database rejects updates and deletions of audit entries.

Data handling

  • API keys for AI providers are stored encrypted.
  • Uploaded images are checked to match their declared type.
  • Uploaded files are stored under server-generated names, not the names supplied by users.
  • Website forms are rate-limited and store no IP address.

Infrastructure

hosting provider, region, encryption at rest and in transit, backups and their testing, and access to production systems.

Reporting a vulnerability

Please report vulnerabilities through the problem-report form with the type set to Security, and give us reasonable time to fix the issue before disclosing it. Do not access other people's data or disrupt the service while testing.