Legal · for businesses

Security measures.

The annex referenced by the data processing agreement, in plain words. The trust page says the same thing for a general reader and lists what is not yet done.

Per ora questo documento è disponibile solo in inglese. Fa fede la versione inglese; una traduzione italiana seguirà dopo la revisione legale.

Version 0.9 · Last updated 2026-11-10 · Describes the Service as built; updated when a measure changes.

  1. Tenant isolation. Every record carries its venue, the data layer requires a venue for every query, and an automated test on every build signs in as one venue and attempts every route with another venue's identifiers, expecting refusal.
  2. Encryption in transit. TLS 1.2 or later with HSTS on every public endpoint, including the pass update service and the join pages.
  3. Encryption at rest. Provider disk encryption, plus application-level encryption of email, phone, birthday, device push tokens and 2FA secrets, with a blind index so lookups never decrypt in bulk.
  4. Authentication. No passwords. Email code or Apple or Google sign-in; two-factor authentication (an authenticator app or a passkey) required for owners and managers; for a passkey we store only its public key, never biometric data; staff PINs hashed; sessions revocable from the dashboard.
  5. Access control. Role-based: owner, manager, staff, partner. StoreWallet staff reach member data only through a step-up prompt that records who, what and why.
  6. Audit log. Append-only record of every write, retained twelve months, visible to the venue for its own data.
  7. Secrets. Held in the hosting provider's encrypted store, never in code; rotation runbook; certificate expiry monitored, with the Apple pass certificate renewed 60 days before expiry.
  8. Backups. Point-in-time recovery of the database; quarterly restore drill with the result recorded.
  9. Dependencies. Every dependency pinned; automated vulnerability alerts; weekly updates; builds fail on known critical vulnerabilities.
  10. Testing. External penetration test before public launch and annually; summary published on the trust page.
  11. Logging. Structured logs with no member email or phone; a scrubber removes them from error reports.
  12. Incident response. Detection through monitoring and alerts, triage, containment, notification to affected venues within 48 hours of awareness, support for their regulator notification, post-incident review published to affected venues.
  13. Personnel. Confidentiality obligations; least privilege; access removed the day someone leaves.
  14. Hardware. NFC chips locked at encoding; lost chips disabled server-side within a second.
Chiedici