Your work.
Your privacy.
Operational privacy notice · website release 9.0.0 · September 7, 2026.
What this website records
Project inquiries record your name, email, organization, selected products and project message. Customer accounts add a password hash, verification state, organization membership and account activity. The workspace records requests, proposals, access entitlements, support conversations and protected release downloads.
What the information is used for
These records support your inquiry, account access, product evaluation, licensing administration, delivery and support. Inquiry and verification emails are placed in a delivery queue for the configured email relay. A request is recorded even when external email delivery is pending.
Cookies and local storage
A first-party HTTP-only session cookie provides session and security-token functionality. Product comparisons, catalog navigation and project selections use local browser storage. No advertising pixels, third-party tracking scripts or analytics cookies are installed. Aggregate daily operation counts omit requests that send Do Not Track.
Software playground
Input is processed on the website server by a bounded execution adapter. The adapter does not store the full input or output in the customer database. Do not submit confidential data to a public demo. The result can be downloaded to your device.
Artifact inspection and signed evidence
The public inspector parses selected files in memory and does not persist them. Private uploads retain files and digests in your organization. Server-generated execution envelopes carry an installation-specific signing identity. Trust that identity only through an independently obtained approved keyring; a signature does not certify semiconductor performance.
Private engineering and security
Saved engineering projects retain inputs, revisions, resource/model planning results, run states, evidence artifacts and organization audit activity. Practice-lab records refer to the saved run used for verification. Authenticator enrollment stores an encrypted TOTP secret and hashed recovery codes. Keep exported evidence and recovery codes under your own access controls.
Native service transfer
An operator-approved native GSP integration sends the explicitly confirmed input and organization/request identity to the configured service. Access is release-bound and requires an organization grant. Do not send confidential or foundry-protected data without the required authority. Hosting, mail and native service providers must be disclosed and approved before a public production launch.
Retention and access requests
Operator retention and deletion settings must be approved before public launch. An account, license or support record may need to be retained for the authorized relationship. Contact patrick@garmolabs.com for access, correction or deletion requests and any questions about the production hosting or email providers.
Protected materials
Licensed artifacts are not in the public web directory. Access requires a verified organization account and a current entitlement. A download is checked against that entitlement and the archive digest before delivery.