Every connection carries documented credentials, permissions, mappings, sync direction, retry rules, and failure handling. Integrations are managed as infrastructure, not as marketing checkboxes.
The Forge is currently in a limited beta. This page describes the controls we implement per-integration; it does not claim third-party compliance certifications we have not undergone. Ask us directly about the specific control you need — we’ll answer honestly.
Authentication, encryption, permissions, audit, revocation, and ownership — configured per integration, documented per connector, and reviewed at each launch.
Authentication
Encryption
Permissions
Audit
Revocation
Ownership
No hedging. If we don't do something, we say so. If it's beta, we say that too.
The minimum object scopes needed for the specific workflow. Broader scopes are not requested even if the provider offers them. Every scope is documented before the connection is enabled.
Yes — at any time, by the customer. Outbound writes stop immediately. Inbound data respects the source system's own access controls once the connection is severed.
Only those permitted by the customer's role, department, entity, and location settings. Connecting a system does not automatically grant every user access to what it holds.
Configurable per action. Sensitive writes — refunds, payroll batches, cancellations — can require explicit human approval; low-risk writes proceed automatically.
Yes. Every sync event carries timestamp, direction, actor, and outcome. Failed events carry a specific reason.
The Forge detects the rejected request on the first 401 / 403, pauses unsafe writes, and notifies the technical owner with the specific credential and provider. Pending actions are preserved until re-authorization is confirmed.
Yes. Records synchronized into The Forge are exportable at any time. Deletion in the source system is respected inside The Forge.
Idempotency keys and provider-supplied event identifiers are used to detect and drop duplicate deliveries — a retried webhook does not create a second record.
The customer. The Forge processes synchronized data on the customer's behalf and does not resell or repurpose it.
Only the third-party providers you explicitly connect, plus the infrastructure providers The Forge runs on. The provider list is documented and updated when it changes.
On unsupported compliance claims
The Forge does not currently carry SOC 2, HIPAA, or PCI audit certifications. Where a specific customer engagement requires those, we scope the gap explicitly during the Blueprint. We would rather turn down work than misrepresent the posture.
IT and technical administrators get a direct security review during the Blueprint — including the credential, scope, retry, failure, and ownership model for each proposed connection.
