Security

Executing untrusted code

Two parts of the engine run code we did not write: the parametric CAD build scripts, and the firmware compiled for the emulated MCU. Both execute inside Firecracker microVMs — hardware-virtualised isolation, one per job, rather than shared-kernel containers.

Each microVM is created for a single job and destroyed when it ends. Emulated targets have no route to production infrastructure, and firmware cannot reach anything beyond the simulated machine it is driving.

Data protection

• Encrypted in transit over TLS.
• Encrypted at rest.
• Secrets held in a managed secret store, not in source or images.
• Infrastructure runs on Amazon Web Services.

Access control

• Least-privilege access to production, reviewed periodically.
• Multi-factor authentication required for staff accounts.
• Administrative actions are logged.

Reporting a vulnerability

Report to support@argentrontech.com with [Security] in the subject. Include reproduction steps, affected endpoints, and any proof-of-concept.

We commit to:

• Acknowledging your report within three working days.
• An initial assessment within ten working days.
• Keeping you updated until resolution, and crediting you if you wish.

Safe harbour

We will not pursue legal action for good-faith research that respects user privacy, avoids service degradation, uses only your own accounts, and gives us reasonable time to remediate before disclosure.

Out of scope: denial-of-service, social engineering of staff or users, physical attacks, and automated scanner output without a demonstrated impact.

Incident disclosure

Where an incident affects your data we will notify affected users and, where required, the Data Protection Board of India and any other applicable authority within the statutory window. See the privacy policy.

Certifications

We do not currently hold SOC 2, ISO 27001, or any equivalent third-party audit. We would rather say so than imply otherwise.