Security
This page says, plainly, how StaffParty protects the people who run businesses here, the customers of those businesses, and the money that moves between them. It describes what is in place today. When something changes, this page changes with it.
- Your account
- Your customers' accounts
- Payments
- Data and infrastructure
- Keys and secrets
- How we work
- Bots and automated traffic
- Reporting a security problem
1. Your account
- Passwords are never stored. We keep only a salted bcrypt hash. Passwords must be at least 8 characters.
- Two-factor sign-in works with any standard authenticator app. Once it is on, signing in needs a code, a code cannot be used twice, and turning it off needs both your password and a current code.
- Guessing is stopped. Repeated wrong passwords or codes lock sign-in for that network address for a while, and the sign-in endpoint is rate-limited.
- Money actions ask for you again. Setting up or changing where your payouts go, refunds, customer credits and charging your card for an upgrade need you to confirm your password (or your two-factor code) within the last 10 minutes. A stolen session alone cannot do them, and StaffParty staff cannot change where your business is paid.
- Sessions end when you say so. Changing your password signs out every other session, and "sign out everywhere" ends them all on our servers, not just in your browser. Every sign-in attempt is recorded.
- API tokens are shown once and stored only as a hash.
- Team access is by invitation. An invite is a signed, single-use, expiring link that must be accepted signed in as the invited email, and each person has their own role.
2. Your customers' accounts
- Each customer account belongs to one business. The same email at two businesses is two separate accounts, and a session from one business is refused by every other.
- Customer passwords are stored only as bcrypt hashes, with the same lockout on repeated wrong guesses. Sign-in takes the same time whether or not an email has an account, so accounts cannot be discovered by trying addresses.
- Two-factor for customers can be offered or required by the business: an authenticator app, an emailed code or, where texting is set up, a texted code, with 10 single-use backup codes stored hashed.
- Account takeover before sign-up is closed. If someone registers an address before its owner does, the owner's first sign-in that proves the mailbox clears what that person set and ends their sessions.
- A password reset signs the customer out everywhere and revokes their API keys. Customers can see where they are signed in.
- Session cookies are HttpOnly, Secure and SameSite, and requests that change something must come from the business's own pages.
3. Payments
- Card details never touch our servers. Customers pay on Stripe's hosted checkout; StaffParty never sees or stores a card number.
- A business's sales go to its own Stripe account, not to StaffParty.
- Payment notifications are verified. Every message from Stripe must carry a valid signature from the last two minutes, and each one is processed once.
4. Data and infrastructure
- Encrypted in transit: every connection is HTTPS on TLS 1.2 or 1.3, and plain HTTP is redirected. The connection from our application to the database is encrypted and the database refuses any that isn't.
- Encrypted at rest: the database and our file storage are encrypted, and the storage buckets block public access.
- The database is private. It has no public address and accepts connections only from our application servers.
- Backups: the database is backed up automatically every day, backups are kept for 7 days, and it is protected against deletion.
- Isolation: a business's app runs in its own container as an unprivileged user, unable to gain privileges or reach the server's credentials.
- A web application firewall screens traffic to the platform for known attack patterns and limits how fast any one client can call it.
- Browser protections: every page is sent with headers that stop it being framed by another site or misread as another file type, and HTTPS is enforced.
5. Keys and secrets
- A business's API keys and integration credentials are kept in AWS Systems Manager Parameter Store, encrypted with AWS KMS, not in the application database.
- Staff who investigate problems use a read-only role that is denied access to secrets, and read data through views that cannot show passwords, keys or tokens.
6. How we work
- Every change to the platform is recorded with who made it: deploys, configuration, and secrets (by name, never their values).
- Cloud activity is logged across every region, with encrypted, tamper-evident log files.
- Dependencies are pinned. Every software package installs at an exact version checked against a recorded hash, new releases wait a week before we take them, and container images and dependencies are scanned for known vulnerabilities.
- Destructive database changes cannot run during a deploy unless a person explicitly allows them.
- The platform refuses to start in production with default secrets or a default administrator password.
7. Bots and automated traffic
Every business can turn on Gatehouse, which decides which automated clients may read its pages and submit its forms, and caps how fast any client can call it. It is off until the business turns it on. A business can also turn away AI training crawlers from its site with one switch.
8. Reporting a security problem
If you think you have found a vulnerability, email security@staffparty.ai with what you found and how to reproduce it. Please give us a reasonable chance to fix it before telling anyone else, and don't access or change other people's data while testing. We'll reply, keep you updated, and say what we changed. The same address is in our security.txt.
Changes to this document
- 2026-11-15 — First published.