SealAudit scopes workspace data to an organization. Server-side checks use membership and permissions to control access.
Clerk handles account authentication. SealAudit checks organization membership and role permissions before allowing protected operations.
Browser connections use HTTPS. Uploaded files use private storage, and file requests pass through access checks.
Configure the evidence each workflow needs. Review your forms and location settings before sharing a workflow with field users.
Geolocation verification is available as an optional workflow step. When enabled, field users are prompted through their browser to share their location. The browser must allow location access before it returns coordinates. If a user declines or the browser cannot provide coordinates, the outcome is recorded as a verification attempt rather than silently skipped.
Workflow activity produces audit events linked by hashes. Chain validation can detect changes to stored events. This is tamper evidence, not a guarantee against privileged database access or fraud. A valid chain does not prove that submitted information is true.
For questions about security posture, data handling, or compliance suitability for your jurisdiction, contact the team directly. We can provide additional detail on encryption standards, access controls, and data residency.
SealAudit welcomes responsible disclosure of security vulnerabilities. If you believe you have identified a security issue, please report it to our team with sufficient detail to reproduce and assess the finding. Include the affected URL, reproduction steps, and potential impact. Avoid including personal data or credentials in your report.
