Server-side workspace access
Private dashboard queries and write actions verify the signed-in user and their role before loading tenant data.
Lead data deserves careful boundaries.
BeeCNC combines server-side authorization, tenant-scoped data access, protected uploads, validated public forms, and signed billing events. This page describes controls present in the application today—not aspirational certifications.
Tenant-scoped records
Leads, notes, attachments, analytics, and subscriptions are stored with business ownership and queried within that business boundary.
Protected uploads
Supported images are checked for type, signature, dimensions, count, and size. Private files require authorized workspace membership to read.
Secret and payment handling
Provider secrets remain server-side. Stripe entitlement changes are accepted only from signature-verified, mode-matched webhooks.
Abuse and error controls
Public submissions use server validation, duplicate suppression, payload limits, origin checks, and persistent request throttling.
Security regression testing
Automated tests cover cross-tenant access, uploads, billing events, authentication boundaries, and tracked-secret scanning.
RESPONSIBLE DISCLOSURE
Found something that may put data at risk?
Email security@beecnc.com with the affected page, steps to reproduce, and potential impact. Please do not access other people's data or run disruptive testing against production.
Privacy and data documentation
Review how BeeCNC handles requests, retention, service providers, and client responsibilities.