Local by default
Receipt recognition stays on your device, and a local check does not need an account or a server. If a signed-in Pro organizer publishes a live check, Stiffed stores the structured check and a private copy of its attached receipt image. Only that organizer can recover the image on another signed-in Pro device. Guests receive the itemized check, never the image.
Accounts, links, and sessions
Organizer identity is verified with Apple, Google, or email sign-in. Join links and signed-in sessions are limited capabilities, can expire or be revoked, and are stored as one-way hashes. Anyone with an active join link may enter that live check, so share it like you would share the table itself. Stop sharing when dinner is done.
Protection and retention
Stiffed uses encrypted connections, server-side authorization, rate limits, transaction-safe claims, restricted browser policies, and provider-managed encryption for hosted data. Expired sessions and links are removed by scheduled cleanup. A deleted account has a 30-day cancellation period, and deleted hosted data may remain in provider backup history for up to one additional day.
Payments and stores
Stiffed calculates what people owe and opens payment services you choose. It does not hold money, store card or bank credentials, or confirm that a transfer completed. Apple and Google process Pro purchases and provide purchase status to Stiffed.
Service providers
Stiffed uses cloud hosting, managed database and authentication, app-store, email, DNS, and operational monitoring providers. Access is limited to the work each provider performs. See the privacy policy for the full data explanation and deletion choices.
Report a security issue
Email support@stiffed.app with the subject “Security report,” a clear description, and a safe way to reproduce the issue. Do not include passwords, store credentials, private receipt details, or another person’s live-check link. The vulnerability reporting policy is also available at security.txt.