Security

A catering business hands Shindig its clients, contracts and money. This is what we do with that trust, in plain terms.

Your data stays yours — and separate from everyone else's

  • Each business is its own workspace. Separation between workspaces is enforced by the database's own security rules on every read and write — not only by application code — so a bug in a page can't open another business's clients.
  • Customer data is stored on Google Cloud (Firebase). Traffic to and from Shindig is encrypted over HTTPS.
  • Connection credentials for Gmail and Square are kept in server-only storage that no browser can read, and are never part of a data export.

Payments

  • Card details never touch Shindig. Clients pay on a Stripe- or Square-hosted checkout, and the money goes to the caterer's own account.
  • Payment records come from the payment provider and an append-only ledger. Staff can add a manual payment (a cheque, cash) or void one, but can't edit or delete an amount after the fact.
  • Payment webhooks are signature-checked and safe to receive twice, so a retry can't double-credit an invoice.

Contracts and e-signatures

  • A signature records the signer's typed name and drawn mark, the time, the device and network address, and a fingerprint of the exact document they saw. Only the server can write those fields; nobody on the caterer's team can alter a signed proposal.
  • The signer is emailed a copy of what they signed.
  • Contract terms we provide are samples, not legal advice, and a business must review and adopt them before sending its first proposal.

Access

  • People sign in with an account of their own and have a role (owner, admin or member). Billing and member management are limited to owners and admins.
  • Crew can be given a limited login: it opens only the events they're scheduled on — address, run of show, kitchen notes and who's working — through a copy that holds no pricing, client contact details or internal notes, plus their own tasks and conversations.
  • When someone is removed from a workspace or disabled, our servers stop accepting their requests straight away. Direct access to their workspace data ends when their sign-in token next refreshes, within the hour.
  • Public endpoints (inquiry forms, proposal and invoice pages, access requests) are rate-limited.

Email

  • If a business connects Gmail, replies are sent from its own address. Shindig only keeps mail with people who are already that business's clients; everything else is looked at just long enough to check, then dropped.
  • Automated emails carry an unsubscribe link, and people who unsubscribe aren't emailed again.

Your control

  • The workspace owner can download everything in the workspace as one file at any time (Settings → Workspace).
  • Closing a workspace cancels billing and keeps the data for 90 days in case of a change of mind; after that the workspace, its files and the owner's account are permanently deleted, and the connections to Google are revoked.

What we don't have yet

Shindig is a young product. We don't currently hold a SOC 2 or ISO 27001 certification, and we don't make claims we can't back up. If your business needs a security review, ask — we'll answer specifics.

Found a problem?

Please tell us before telling anyone else. Email support@getshindig.com with “Security” in the subject. We read these ourselves, and we won't pursue anyone who reports in good faith. See also our Privacy Policy.