Production, with boundaries

Security onboarding before private production

An approved workflow—not an unreviewed public upload box.

Illustrative controlled document production layers

This website’s actual behavior

No source-file upload, form-submission backend, analytics vendor or advertising pixel is installed. The enquiry planner works locally. When hosted, delivery logs may exist at the hosting provider and must be disclosed before launch.

Proposed onboarding requirements

  • Approved transfer channel and named business accounts.
  • MFA, least-privilege access, protected devices and permitted storage locations.
  • Client-approved people, specialist reviewers and backup arrangements.
  • Written retention, incident contact and deletion process.
  • Explicit tool permissions, including external AI and conversion services.

Evidence to request

Ask for a truthful tool/data-location inventory, role list, sample issue log, restore/handoff exercise and retention arrangement. No ISO/SOC certification, staffed security operations center or universal data-residency guarantee is asserted.

Keep credentials separate

A conversion-only job does not need CCC, access tokens or shared Login.gov logins. Authorized account handling requires its own process; never place credentials in an enquiry, manifest or CRM note.

Reference: EDGAR Next roles. Verify the current requirements for the agreed job.

Private content and AI

No confidential source should reach an external AI or consumer conversion service without client authorization and suitable vendor terms. Public practice samples and marketing copy do not establish permission for private production.

Incident and continuity decisions

Define the authorized contact, containment and evidence-preservation process, contract-specific notification timing and approved continuity route. Confirm actual implementation before representing these requirements as established controls.

Read confidentiality requirements →

Google optional storage is denied by default. These controls send Google consent signals and remember your choice for up to 180 days. They do not block third-party script loading or control Jotform chat. Tags inside Tag Manager must be configured to respect consent.

Read the storage and integration inventory. Do not share confidential files or credentials in the chat.