Where your data lives and who can touch it
Your contact list is the most sensitive thing your organisation owns. This page says plainly how fullhall stores it, who can reach it, and what we don't have yet. Every claim here is true of the running system, and when the infrastructure changes, this page changes.
Where your data lives
The fullhall database runs on infrastructure in Australia. Your contacts, events and RSVPs stay onshore. Uploaded files (event banners, logos, shared PDFs) are held in Cloudflare's object storage. A small number of services we build on process data overseas; the full list, with what each one sees, is in the privacy policy.
Who can reach it
Every admin has their own login. Sign-in is handled by Clerk, which supports multi-factor authentication and means fullhall never stores a password. There is no shared account to leak in a group chat, and when someone leaves your team you remove them, not the password.
Inside the product, every record belongs to exactly one organisation and every query is scoped to it. Owner and admin roles control who can invite, who can remove, and who can delete. The people you invite never have accounts at all: an RSVP is a record, not a login.
Encryption
All traffic between your browser and fullhall runs over TLS. Data is encrypted at rest on our storage. Public file links use long random tokens and can be taken private again; taking one private kills existing copies of the link within minutes.
Card payments
Ticket and membership payments run on Stripe's hosted checkout page. Card numbers travel from the buyer's browser to Stripe and never touch fullhall's servers; there is no card form of ours to compromise. What we store is the record of the sale (who paid for which tickets or membership, for how much, and its refund state), and the money settles in the organisation's own Stripe account, not ours.
What we don't have yet
fullhall is not SOC 2 or ISO 27001 certified. Those audits cost more than a product this size can justify, and a certificate we bought before we could afford to do it properly would be theatre. What you get instead is a short, true list of controls and a founder who answers security questions himself.
Found a problem?
Email [email protected] with the details and you'll hear back from me quickly. If you can, include steps to reproduce. Please don't access other organisations' data while testing; a proof of concept against your own is plenty.