Security at Shift Amp

A plain description of how we protect scheduling data today, during our pilot phase. We’ll keep this page current as the product matures.

Architecture

• Every organization’s data is isolated with database-enforced row-level security — tenant boundaries are checked in the database on every query, not just in application code, and covered by an automated cross-tenant test suite that runs before every schema change.
• Access is role-based (owner, operations admin, location manager, assistant manager, employee), enforced in the database. Employees see only published schedule truth — never drafts or other people’s requests.
• Schedule-affecting actions are recorded in an append-only audit history.

Data handling

• Connections to the product use HTTPS/TLS via our hosting providers (Vercel and Supabase).
• Passwords are handled by Supabase Auth and stored only as hashes. Employee invitation links use single-use, expiring tokens; only a cryptographic hash of the token is stored.
• Development, preview, and production run against separate databases with separate credentials; production schema changes are applied only from version-controlled migrations.
• Error reports are scrubbed of credentials, tokens, notes, and contact details before leaving the application; product analytics are organization-level and contain no personal identifiers.

What we don’t claim

We are an early-stage product. We do not currently hold formal certifications (such as SOC 2), and we don’t advertise guarantees we can’t demonstrate. If your evaluation needs specifics, ask us — we’d rather show you than overstate.

Reporting a vulnerability

If you believe you’ve found a security issue, email support@shiftamp.com with the details. We’ll acknowledge your report, investigate promptly, and keep you informed. Please don’t access data that isn’t yours while demonstrating an issue.