Security Controls
Security controls and operational safeguards for Roadscape.
This page summarizes the practical controls Roadscape uses to protect accounts, connected services, customer data, and operational workflows.
Access Controls
Access is limited to authorized users and service processes. We use account authentication, role-based access where supported, least-privilege provider tokens, and connected-account permissions scoped to the workflow being performed.
Approval Gates
High-impact workflows should preview changes before applying them. DNS changes, code commits, deploys, publishing, campaign sends, payment actions, and destructive operations should require explicit approval unless the account owner intentionally configures automation.
Security in Transit
Public pages, dashboards, API calls, callbacks, and authentication flows use HTTPS/TLS. Sensitive tokens should never be sent over plain HTTP.
Secrets and Token Handling
API keys, OAuth secrets, refresh tokens, Stripe keys, database strings, and Cloudflare tokens should be stored in encrypted secrets or provider-managed environment variables. Secrets must not be committed to source control, pasted into public pages, logged, or included in generated site bundles.
Tenant Separation
Customer and workspace data should be separated by tenant, workspace, or owner identifiers. Backend policies and service checks should prevent one account from reading or writing another account's data.
Change Management
Material production changes should be tested, reviewed, and recorded through deploy logs, commit history, audit records, or task records. Rollback paths should be available for changes that affect production pages, DNS, payments, authentication, or campaigns.
Monitoring and Logging
We use provider logs and application logs to diagnose errors, failed authentications, suspicious access, integration failures, and delivery issues. Logs should avoid storing full secrets or unnecessary personal data.
Backups and Recovery
Critical data should be backed up through the database or hosting provider. Recovery depends on the specific provider and plan used for the product or customer workspace.
Responsible Testing
Security, DNS, mail, SMTP, search, and website diagnostics should be run only against domains, systems, and accounts you own or are authorized to test.
Report a Security Issue
Report suspected security issues to [email protected]. Do not include secrets in email unless we specifically request a secure exchange method.