OpsPulse is what your security review wants — not a checklist of buzzwords. Real isolation, real encryption, real audit trails.
OpsPulse uses Supabase Auth for operator accounts and short-lived, per-shift identity for staff. Every action on the kiosk is attributable — no shared store PINs, no anonymous taps.
Layered access on every request
Operational records live in Supabase Postgres with row-level security on every table. Photos and evidence sit in Cloudflare R2, encrypted at rest. Tenants never see each other's data — enforcement happens in the database, not the application code.
Pinned, isolated, enforced
Every LLM call routes through Cloudflare AI Gateway — rate-limited, logged, observable. Personal data is redacted before any knowledge indexing or retrieval. Your knowledge stays scoped to your tenant.
Every model call, every time
We don't claim certifications we don't have. Here's exactly where we stand today and what's on the roadmap.
EU-ready architecture with region pinning. DPA available on request. Data deletion and export honored within the regulatory window.
California-resident rights supported — access, deletion, and opt-out mechanics built into the operator dashboard.
Roadmap — Q4 2026. We're building toward a Type I report with a Type II to follow. We won't claim it until it's signed.
Full list of subprocessors available in your DPA.
Cloudflare
Compute, edge, storage (R2), AI Gateway, Durable Objects
Supabase
Auth, Postgres, Realtime
OpenAI
LLM inference (via Cloudflare AI Gateway)
If you believe you've found a security vulnerability in OpsPulse, please report it privately to security@opspulse.io. We acknowledge every report within 24 hours and will keep you posted through resolution. We don't pursue legal action against good-faith researchers who follow coordinated disclosure.
security@opspulse.ioBring your questionnaire. We've answered every one of them.