Start without sending secrets.

Already paid? Reply to your Stripe receipt or email Stefano.Stokes@forhemit.com. Send only the business facts below. We will establish an approved project channel before requesting access.

Business and product facts

• Legal business name, billing contact, and primary time zone
• Public product name and URL
• Short description of the customer-facing AI interaction or generation surface
• Evidence of EU availability or intended EU use
• Repository stack and staging environment—not credentials

Named owners

Provide one product owner, one engineering owner, and the counsel or authorized compliance owner who will identify the applicable duty, approve the scope, and approve the disclosure language. Work cannot begin until those responsibilities are explicit.

Approved legal scope

Ask your counsel or authorized compliance owner to state which specific Article 50 implementation duty is selected for this engagement, which product surfaces it covers, the approved user-facing language, any claimed exception, and the evidence they expect. Forhemit records this decision; it does not make it.

Access sequence

1. Complete qualification and accept the written kickoff scope.
2. Invite the named Forhemit engineer through your authorized repository system.
3. Grant least-privilege access to one repository and staging environment.
4. Use short-lived credentials and your normal secret manager where access is unavoidable.
5. Keep production release under your engineering owner's change-control process.
6. Revoke project access after handover.

Do not email

Do not email passwords, API keys, private keys, production tokens, customer records, private source archives, confidential legal advice, or regulated personal data. If the approved work would require real end-user data or production access, stop and agree a separate security process before sharing anything.

Kickoff acceptance checklist

• One TypeScript/JavaScript web product and one repository
• Up to three user-facing surfaces and one output modality
• Named product, engineering, and legal/compliance owners
• Written duty and language approved by the buyer
• Staging environment available
• Five-business-day calendar and review windows agreed
• Twenty-four-hour delivery cap acknowledged