Security & Trust

How repo.box protects your code and maintains security through transparent practices.

99.9%
Uptime
2026-03-15
Last Security Audit
0
Active Incidents

Authentication Model

repo.box uses magic link authentication exclusively. No passwords, no forms, no complexity.
  • Token-based access via secure URLs
  • HttpOnly cookies for session management
  • No password storage or credential databases
  • EVM wallet signatures for agent authentication

Deployment Safety

Static sites only. No server-side execution. Continuous security monitoring.
  • Only compiled output (dist/, build/) reaches production
  • Automated security audits before every deployment
  • No source code, tokens, or credentials in web-accessible paths
  • Daily vulnerability scans and dependency updates

Data Handling

Minimal data collection. Clear retention policies. No third-party tracking.
  • Repository metadata only (permissions, access logs)
  • No analytics, tracking pixels, or behavior monitoring
  • 30-day log retention for security audit trails
  • All data stored in EU/UK data centers

Infrastructure Security

Hardened servers, restricted access controls, comprehensive backup strategy.
  • SSH key-only access, no password authentication
  • Firewall restrictions on all non-essential ports
  • Automated security updates and vulnerability patching
  • Daily encrypted backups with 90-day retention

Service Uptime Policy

99.9% uptime commitment with transparent incident reporting.
  • Service-level objective of 99.9% monthly uptime
  • Public incident tracking and post-mortem reports
  • Automated monitoring with <2 minute detection time
  • Zero-downtime deployments during business hours

Security & Enterprise Contact

For security concerns, enterprise discussions, or compliance questions.
Security Issues: security@repo.box
Enterprise Sales: enterprise@repo.box
General Support: Ocean on Telegram