Skip to main content
Security

How we protect your work.

This page describes the controls in FORGE and Virtual Crew today. Enterprise deployment options are on the Enterprise page.

Last updated 5 November 2026

Access control
Every FORGE user signs in, and each role is held on the server. Access is denied by default, checked on every request, and checked again inside high-risk actions.
Sign-in protection
FORGE rate-limits sign-in attempts and binds sessions to the device that created them. Salary figures need a second passphrase, and that access expires.
Data handling
Data travels over TLS. FORGE stores uploaded files privately and writes every lot change to a permanent history showing who made it and when.
Infrastructure
FORGE runs on Microsoft Azure. Its responses carry a strict Content Security Policy and HSTS, and it refuses to load inside another site’s frame.
Virtual Crew
Connector credentials are encrypted at rest with AES-256, and secrets are masked in API responses and logs. Every route enforces tenant context.
Governance
Virtual Crew risk-scores its jobs and pauses them at set thresholds until a person approves. Model calls, tool calls, and decisions are logged.
Your data
Your data stays yours, and we don’t train on it.
Certifications
We don’t hold ISO 27001 or ISO 42001 certification today. Both are on our roadmap.
Reporting a vulnerability
If you find a security issue, email us the steps to reproduce it. Please don’t access other people’s data or disrupt the service while testing.

Security questions and reports: management@sentienx.in