TraceLockTraceLock help center
Keep your control program moving.
Get help connecting your estate, interpreting control posture, and preparing evidence for customers, auditors, and regulators.
Email support@odingard.comRead the documentationSeverity 1
1 hour, 24×7 for Enterprise.
Include your workspace, integration, and a short description so we can route the request quickly.
Severity 2
4 business hours.
Include your workspace, integration, and a short description so we can route the request quickly.
Severity 3
1 business day.
Include your workspace, integration, and a short description so we can route the request quickly.
Severity 4
2 business days.
Include your workspace, integration, and a short description so we can route the request quickly.
TraceLock notifies affected subscription administrators within 72 hours of confirming an incident that affects their organization's data.
Connect your estate
Integration starting points
GitHub
Repository posture, identity, and webhook telemetry.
Google Cloud
IAM, estate, and control evidence from GCP.
Microsoft Azure
Cloud posture and control telemetry for Azure estates.
Identity
Workspace membership, access review, and authentication signals.
Getting started
Create your workspace
Invite your team through TraceLock and assign least-privilege roles.
Connect a signal source
Start with GitHub, GCP, Azure, or identity telemetry from the Integrations workspace.
Review and share posture
Resolve failed controls, inspect retained evidence, and publish a customer-facing Trust Center.
FAQ
How quickly does a new connector appear?
Most connector checks appear after the initial sync completes. If a provider is delayed or rate-limited, TraceLock shows the latest successful check and the next scan state.
Why is a control marked for review?
A review state means TraceLock needs a human decision, additional evidence, or a provider response before it can mark the control passed or failed.
Can I share evidence with an auditor?
Yes. Trust Center and Auditor Room workflows provide scoped, expiring access. Evidence retention clocks and download requirements continue to apply.
What should I include in a support request?
Send your workspace name, affected integration or control code, approximate time, and the visible error or request ID. Never email passwords, API keys, or raw connector secrets.