Back to Security

Access Policy

How we control and audit access to production systems

Our Commitment

We follow least-privilege principles. All production data access is logged, auditable, and tied to business justification. This document explains how we protect your data internally.

Access Levels

We define five access levels to ensure appropriate permissions:

LevelWhoAccessLogging
L0 - NoneDefaultNo production accessN/A
L1 - LogsOn-call engineersApplication logs, metricsAutomatic
L2 - ReadSenior engineers (approved)Database read accessAudit logged
L3 - WriteEngineering leads onlyDatabase modificationsAudit + approval
L4 - AdminLeadership onlyFull accessFull audit trail

Access Request Process

Elevated access (L2 and above) requires documented justification:

1

Engineer submits request with business justification (support ticket, incident ID)

2

Engineering lead reviews and approves within 4 hours

3

Access granted with automatic expiration time

4

All actions logged to audit trail with request reference

What We Log

Every production data access is recorded with:

  • Who: User ID and email of accessor
  • What: Resource type and ID accessed
  • When: Timestamp of access
  • Why: Reference to ticket or incident
  • How: IP address and user agent
  • Action: Read, write, delete, or other operation

Audit logs are retained for compliance purposes and are immutable (append-only).

Time-Limited Access

Elevated access is never permanent:

  • Standard requests: 1-4 hours typical, 24 hours maximum
  • Emergency access: Self-granted during incidents, reviewed within 24 hours
  • Automatic revocation: Access expires without manual intervention
  • Session timeout: 8-hour maximum session length

Prohibited Actions

The following are strictly prohibited without documented approval:

  • Viewing customer records out of curiosity
  • Exporting customer data to local machines
  • Sharing customer data externally
  • Accessing data outside the approved scope
  • Using shared credentials

Violations result in immediate access revocation and HR involvement.

Technical Controls

ControlImplementation
AuthenticationSSO with MFA required for production
AuthorizationRole-based with individual credentials
Database accessIndividual accounts, no shared credentials
API keysPersonal keys, rotated quarterly
ImpersonationAdmin-only, logged, time-limited

Offboarding

When employees leave, we immediately:

  • Revoke SSO and database access
  • Rotate any shared secrets they knew
  • Audit recent access for anomalies
  • Remove from all team permissions

Questions?

For questions about our access policies or to report concerns, contact security@brazilnut.ai

Last updated: January 2026

Data Processing Agreement · Privacy Policy · Security