Security

WaveWage handles two sensitive things: what people are paid, and the sales that fund it. We treat that data as if it were our own payroll. Security is built into how the product is designed: least-privilege access, isolation between businesses, and a payout pipeline engineered so money is never paid twice and never silently dropped.

All traffic to WaveWage is served over TLS, so data is encrypted in transit. Data at rest, including pay and attendance records, is stored on encrypted infrastructure. Credentials and integration tokens are stored using one-way hashing or encryption, never in plain text.

• Role-based access: operators, managers, and employees each see only what their role allows.
• Manager-PIN gates on sensitive in-store actions, such as exiting the live wall display.
• Internal access to production data is limited to the people who need it to operate the service.

Sessions are authenticated with signed, expiring tokens. Passwords are stored only as salted hashes. Employee access is scoped to a single identity and location, so a signed-in employee can only ever act as themselves.

WaveWage is multi-tenant, and every query is scoped to the location it belongs to. One restaurant cannot see another's employees, sales, rules, or payouts. This boundary is enforced in the data layer, not just the interface.

When you connect a scheduling or time-tracking provider, WaveWage requests only the access needed to read the hours and attendance a payout depends on. Integration tokens are stored encrypted and scoped to your account, and you can revoke a connection at any time.

Subscription billing is handled by a PCI-compliant payment processor. Card details are entered directly with the processor and tokenized. WaveWage never receives or stores full card numbers.

The end-of-shift payout pipeline is built for correctness under failure: each push carries a deterministic identifier, runs through a two-phase log, and drains cleanly on shutdown, so a payout is never duplicated and never lost mid-flight if a server restarts. Operators get an alert if anything looks off before money moves.

We monitor the service for errors and integration failures, and degraded states are recorded and surfaced rather than hidden. Because WaveWage derives pay from synced data, we validate that data and fall back safely rather than guessing when something is missing.

If you believe you have found a security issue, we want to hear from you. Email security@wavewage.com with the details and steps to reproduce. Please give us a reasonable window to investigate and fix before disclosing publicly; we will not pursue action against good-faith research that respects user privacy and avoids service disruption.