Security Overview
GGNomad inherits a complete security backbone from the Burdenoff platform. Authentication, role-based access control, multi-tenant isolation, encryption, and audit apply uniformly across GGNomad and every other Burdenoff product — so a travel marketplace ships enterprise-ready without reinventing security. Trust is a property of the data model: every booking is attributable, every field is permission-gated, and every action is recorded.
GGNomad makes no claim to formal certifications; compliance evidence and attestations remain on the roadmap.
Security architecture
🔒 Authentication
Enterprise identity via OIDC SSO, OAuth flows for clients and integrations, and platform-managed sessions.
🛡️ Authorization
Every API operation is permission-checked before it runs and scoped to the caller's workspace.
🔐 Encryption
Encryption in transit and at rest, with secrets held in managed, per-environment secret storage.
Core security features
Access control Authorization
A governed, multi-role marketplace:
- One identity can be a traveler, host/operator, or administrator
- Every action is scoped by role
- Every read and write is permission-checked before it runs
- Identity and workspace come from the authenticated session, never from a client-supplied argument
Data protection Encryption
- TLS in transit and encryption at rest
- Multi-tenant isolation — a workspace never sees another's data
- PII and payment-data handling with scoped access
- Secrets held in managed, per-environment secret storage, never baked into client builds
Audit & governance Monitoring
- Every mutation is recorded with actor, target, and result
- Searchable, exportable activity timelines
- Verification lifecycle gates listings before they go live
- Transparent, itemized totals so bookings are explained before they confirm
Security controls
🔍 Monitoring
Operational security signal:
- Structured logging and tracing
- Health checks and alerting
- Activity and audit tracking
- Usage metering and quota enforcement
📋 Compliance posture
Privacy-aligned:
- GDPR/CCPA-aligned data handling
- Retention and deletion policies
- Scoped, least-privilege access
- Certifications: none claimed today
What's inherited from the platform
Identity Auth
- OIDC SSO and OAuth client/device-code flows
- Workspace-scoped API keys for automation
- Platform-managed sessions
Governance Control
- RBAC on every operation
- Multi-tenant isolation by default
- End-to-end audit and activity log
- Per-action quota enforcement
Best practices
🎯 For integrators
Request least-privilege permissions and respect workspace scoping.
🔧 For operators
Review roles, watch the audit log, and verify listings before they go live.
For security and compliance questions, contact our team. Contact the security team