Security & privacy

What QuiltHosting does to protect your guild's data, and the few things officers need to do themselves.

What the platform does

  • Roles are enforced on every request. Each call to the server is checked against the role table in Roles & team, not just the buttons on screen. Areas a role may not see return "Forbidden".
  • Each guild's data is separate. Every record belongs to one guild and every query is limited to it.
  • Everything is over HTTPS, including your subdomain and custom domain, with certificates issued automatically. Browsers are told to stay on HTTPS, not to sniff file types, and not to show QuiltHosting pages inside other sites (except the embeds you choose to place).
  • Abuse limits. Sign-in link requests, joins, donations, event registrations, store purchases and quote requests are rate-limited per connection.

Sign-in and sessions

  • Officers sign in with Google; there are no guild-managed passwords to leak. Members sign in with an emailed link that lasts 15 minutes and works once.
  • A sign-in lasts 7 days on that browser and then expires; there is no "remember me forever". Signing out on one browser does not sign out others, and removing an officer from the team does not end a session they already hold — it simply stops working within 7 days.
  • Receipt and document links from the portal are valid for 10 minutes and for one item only.
  • While in private preview, the entire site also sits behind a shared access password.

Content and files

  • Anything typed or pasted into pages, posts or emails is cleaned before it is stored and again before it is shown: scripts, styles, forms and event handlers are removed; only safe links and images are kept; embedded frames are allowed only from YouTube, Vimeo and Google Maps.
  • Uploaded files are stored privately. Images are served only if they really are PNG, JPEG, GIF, WebP or AVIF; logos are checked by their contents, not their file name, and SVG is refused. Files that could run code are stored as plain downloads.
  • Member photos in the directory are shown only while the member is active and has chosen to be listed.

Payments

  • Card details go straight to Stripe; QuiltHosting never sees or stores card numbers.
  • Notices from Stripe are checked for a valid signature and a recent timestamp before anything happens, and a payment is never applied twice (see Billing & payments).
  • Seats and stock are reserved with a single atomic check, so two people cannot buy the same last seat or item.
  • Any third-party credentials you store (currently PayPal keys) are encrypted at rest and can never be read back through the admin. Twilio and QuickBooks details are stored in your guild settings and are visible to your team.

Email consent

  • Every newsletter and automation carries an unsubscribe link and one-click unsubscribe headers. Unsubscribing takes effect immediately and is never overridden by a CSV import.
  • Hard bounces and spam complaints block further mail automatically.
  • Transactional mail (sign-in links, receipts, renewal and event notices) is kept separate from newsletters so members can opt out of one without losing the other.

What officers should do

  • Remove departed officers from Admin → Team as soon as they step down, and change the Owner role during a handover (see Handing over ownership).
  • Give people the smallest role that does the job. A newsletter editor needs Membership chair, not Admin; a treasurer's helper may only need Viewer.
  • Never forward a sign-in link. It signs in whoever clicks it. Ask the person to request their own.
  • Use your own Google account for the admin, not a shared guild mailbox, so access can be revoked person by person.
  • Only email people who agreed to hear from the guild, and put a real contact address in newsletters, since replies to the sending address are not delivered.
  • Protect API keys and webhook secrets like passwords; revoke a key the moment it may have leaked.
  • Export your members and payments from time to time and keep the CSVs somewhere safe; QuiltHosting does not offer a self-service backup.

Your data

Your guild owns its member data; QuiltMap LLC hosts it on Cloudflare, uses Stripe for payments, Resend for email and Google for sign-in, and does not sell personal information. Members can update their own details in the portal; officers can export members and payments at any time. Full details: Privacy Policy and Terms of Service. Report a security concern to hello@quilthosting.com.