Security Starts With Controlled Web Access

All connections between the browser and The Forge use HTTPS with TLS encryption enforced by the hosting provider.

A Content Security Policy restricts which scripts, styles, images, fonts, and network connections the browser is allowed to load, and blocks page framing, plugin content, and base-URL hijacking to limit the impact of content-injection attacks.

Additional security headers are set on all responses: X-Frame-Options DENY, X-Content-Type-Options nosniff, Referrer-Policy strict-origin-when-cross-origin, Permissions-Policy, and HSTS.

Authenticated sessions use HttpOnly cookies that are not accessible to client-side scripts. Sessions expire after a configured period of inactivity.

The Forge is accessible through supported mobile browsers with the same authentication and session protections as desktop access.

Each user accesses The Forge through an individual account with a verified email address, so actions can be attributed to the correct person.

User passwords must meet minimum length and complexity requirements. Passwords are stored using PBKDF2 key derivation, not in plaintext.

Repeated failed sign-in attempts trigger rate limiting and temporary account lockout to resist brute-force attacks.

An additional verification step beyond a password for sign-in.

Integration with an organization's existing identity provider for centralized authentication.

Users are assigned roles that determine what they can view, create, modify, and approve within The Forge. Standard roles include owner, manager, employee, and contractor.

Permissions can be scoped so a location manager sees only their assigned location and a business-entity administrator sees only their assigned entity.

Administrative actions such as user creation, role changes, and integration configuration require appropriate administrative authority and are recorded in the activity history.

Multiple legal entities or operating companies can be managed under one account with access boundaries that prevent users assigned to one entity from accessing another entity's records without authorization.

Users can be assigned to specific operating locations so they see only the records, schedules, and reporting relevant to their assigned location.

Authorized executives can view reporting across multiple entities and locations without giving every user the same cross-organization access.

All data transmitted between the browser and The Forge is encrypted using HTTPS with TLS, enforced by the hosting infrastructure.

Customer data stored in the platform database is encrypted at rest by the hosting provider's storage infrastructure.

Integration credentials and API keys are stored separately from application data using the hosting platform's secret management capabilities.

User-submitted content is sanitized before storage and display to prevent injection attacks.

Each integration must be explicitly authorized by an account administrator before it can access or modify customer data.

Integrations are configured with specific permissions that define which data they can read and which actions they can perform.

Account administrators can disconnect an integration and revoke its access at any time.

Actions above a configured dollar amount or sensitivity level can require owner or manager approval before they execute.

Authorized administrators can stop all optional purchasing activity when immediate intervention is required.

No optional campaign, lead purchase, subscription expansion, or external service is activated without the configured customer approval. Monthly caps, category limits, and approval workflows are configurable.

User creation, permission changes, integration changes, and administrative actions are recorded with the actor, timestamp, and action details.

Successful and failed sign-in attempts are recorded for review by account administrators.

Changes to customer records, workflow configurations, and approval decisions are recorded with the actor and timestamp.

The platform is monitored for availability and performance. Degradations are detected and addressed by the operations team.

Application errors, failed requests, and unexpected conditions are captured and reviewed to identify issues before they affect customer operations.

Connected integrations are monitored for authentication failures, synchronization errors, and provider outages.

Platform databases are backed up according to the hosting provider's backup schedule. Backups are used for disaster recovery, not for individual record-level restoration on demand.

Failed or problematic deployments can be rolled back to restore the previous working version of the platform.

Recovery procedures are tested to verify that platform data and operations can be restored after an incident.

All platform code is maintained in version control with a code review process before changes are merged.

Third-party dependencies are tracked, reviewed for known vulnerabilities, and updated as part of the development process.

Development, staging, and production environments are separated so that changes are tested before reaching the production platform.

Independent security testing of the platform by a qualified external party.

Platform updates are applied centrally by HustleForge. Customers do not need to install updates on their devices or manage separate software versions.

Updates go through development, review, testing, and staging before reaching the production environment.

A defined process for detecting, assessing, containing, and resolving security events, including customer notification where required.

A contact method for reporting security vulnerabilities discovered in The Forge, with an expected acknowledgment process.

The customer controls which users have access, what roles they hold, and when access is removed. HustleForge provides the access-control capabilities.

The customer is responsible for the security of the devices and browsers used to access The Forge. HustleForge secures the platform application.

Authorized users can export customer-supplied records from The Forge in supported formats.

Customer data is retained according to the terms of the service agreement. Upon account termination, customer data is handled according to the documented retention and deletion process.

Customer-supplied data remains the property of the customer organization. HustleForge does not sell, share, or use customer data for purposes outside the scope of operating The Forge.