Privacy Policy

PartyScrum operates PartyScrum. Privacy requests may be sent to privacy@partyscrum.app.

Free planners sign in through Google or a secure emailed link using Supabase Auth. We receive the account identifier, email address, display name when provided, and authentication session data Supabase and the selected provider supply. Premium planners may instead create a private PartyScrum account without email, SMS, Google, or another social account.

For private planner access, the planner handle is encrypted at rest and compared through a keyed blind index. The code phrase, planner PIN, and offline recovery key are stored only as one-way password hashes. PartyScrum cannot retrieve those secrets. Planner sessions use short-lived HttpOnly cookies, and the database stores only a hash of each random session token.

Guests do not create platform accounts. A guest supplies an event alias and event PIN. The alias is encrypted at rest. In Sanctum Mode, the planner must approve the alias in advance, and the guest must also know the exact event tag, creator handle, and a guest-specific secret code. Searchable comparisons use keyed blind indexes, and PINs and guest codes are stored as one-way password hashes rather than readable values.

After successful entry, the browser receives a short-lived, HttpOnly, event-scoped session cookie. PartyScrum stores only a hash of that session token. Guest credentials are not reusable identities and are not correlated across different Scrums.

We store information a planner or guest chooses to place on a Scrum, including event details, RSVP state, bring-list activity, contribution ledger entries, payment handles the planner publishes, and supported music links. Contribution boards are shared records only. PartyScrum does not hold or transfer money between guests.

• Planner and guest access are separate and checked on every protected server request.
• Direct browser access to PartyScrum database tables is denied.
• Guest aliases are encrypted, while PINs and guest codes are one-way hashed.
• Access attempts are rate-limited in shared storage. We store a keyed digest, not a raw IP address, in that counter.
• Guest sessions expire and are revoked when a planner revokes or removes a guest.
• Private planner sessions expire after twelve hours and are revoked when credentials change.

• No email address or phone number is required.
• No Google, social, or PartyScrum account is required.
• No SMS message or app download is required.
• We do not sell or rent guest or planner information.
• We do not build advertising profiles from event activity.
• We do not store full payment card numbers.

• Supabase provides planner authentication and the protected database.
• Vercel provides application hosting, delivery, and operational security logs.
• Stripe processes the one-time Sanctum Mode Scrum fee. Stripe may collect billing information under its own privacy policy.

Guest browser sessions expire after twelve hours. Successful access counters are reset, and stale rate-limit digests are removed automatically. Event records remain until the planner deletes them or deletes the planner account, subject to limited legal, security, and accounting retention. See the Data Deletion Request page to request access or deletion.

PartyScrum is not directed to children under 13. We will update the date shown on these pages when this policy changes and provide additional notice for material changes when appropriate.