Trust, plainly stated
A concise view of CAM's data boundary, action authorization, website operations, and framework status.
CAM governs sensitive data access and actions requested by AI agents or people. At least M of N named human approvers must approve, any denial permanently vetoes the request, and the configured veto window must pass before CAM sends one signed call to the customer's system. That system releases data or executes the action. CAM does not execute actions or store governed data and records each decision in a tamper-evident, SHA-256 hash-chained audit log.
The website is served over HTTPS/TLS on Replit. Contact submissions are stored in PostgreSQL, and encryption at rest is managed by the infrastructure provider.
Contact submissions include name, email, optional company, topic, and message, used only to respond. They are stored securely in PostgreSQL and emailed to the founder, never sold. IP and user-agent information supports spam prevention and security. Cloudflare analytics are cookie-free and aggregate. There are no advertising trackers.
SafeLoc uses Replit for hosting, PostgreSQL for the contact database, Resend for email delivery, and Cloudflare Web Analytics for cookie-free aggregate analytics that do not track individual visitors. There are no advertising trackers.
If you choose to book a call, the scheduling link opens Calendly in a new tab. Calendly is an external service and its own privacy policy and terms apply when you leave this site.
SafeLoc does not claim that CAM or SafeLoc is certified or compliant with HIPAA, SOC 2, GDPR, or other frameworks. CAM's named human approval workflow, signed call to the customer's system, policy of not storing governed data, and tamper-evident, hash-chained decision log are design features customers may assess against their own requirements.
Report a vulnerability using our disclosure policy. The security.txt file lists the security contact and policy.
info@safeloc.co