Trust & security

Last updated 29 October 2026

Your club’s members, dues and records sit with us. Here, in plain English, is how we protect them, and what we never keep.

Location

Your data stays in Australia

Capofila and its database run in AWS Sydney, and nowhere else.

No open doors

Nothing can connect in

Our server has no open ports. It reaches out to Cloudflare through a private tunnel; there is no way in from the internet except through that tunnel.

Encryption

Locked in transit and at rest

Every connection uses TLS, and the database and server disk are encrypted with AES-256.

Payments

Dues go to your club

Your club’s own Stripe account takes the money. We never hold it, and never see a card.

How your data is protected

In transitAES-256At rest
Your browserAdmins, treasurers and members
Nothing stored but a sign-in cookieYour session, sent only over HTTPS.
Wallet card (optional)A membership card in Apple Wallet, protected by iOS.
TLS 1.3browser to edge
Cloudflare edgeabsorbs attacks
Private tunnel to our serverOur server dials out; nothing dials in.Encrypted tunnel
Tunneledge to server
Capofila — AWS SydneyNo open ports. Nothing public.
Members, tiers, dues status, recordsPostgres database, not reachable from the internetAES-256 · AWS KMS
Server diskThe machine Capofila runs onAES-256 · AWS KMS
Backups7 days of automatic database backupsAES-256 · AWS KMS

Capofila ⇄ Stripe: TLS, using only your club’s account ID. Card details go from the member straight to Stripe and never pass through Capofila.

Payments tab

Dues go to your club, not to us

When your club turns on online dues, you connect your club’s own Stripe account. Members pay your club directly. We never hold the money, and we add no fee on top of Stripe’s.

Stored

What we store

  • Your club’s Stripe account ID. It starts “acct_” and is not a password.
  • Whether the connection is on or off.
  • A reference number for each member’s subscription, so we can show who is paid up.
Never

What we never store

  • Your club’s Stripe password or secret keys.
  • Card numbers or bank details. Members type them into Stripe, never into Capofila.
  • The money. Dues land in your club’s account.
Your control

You can switch us off

  • Your treasurer approves Capofila on Stripe’s own page.
  • Remove Capofila in your Stripe dashboard at any time.
  • Stripe tells us straight away, and the connection is marked revoked.

Where a dues payment goes

Memberpays dues in a browser
TLS 1.2+card details
Stripecard typed here · PCI DSS Level 1
money
Your club’s Stripethe dues land here
CapofilaAWS Sydney
TLS · account ID only

Asks Stripe to set up each member’s subscription on your club’s account. It never sees the card.

Signature checked

Hears back from Stripe when a payment succeeds or fails. Every message is signed by Stripe and checked before we act on it.

How the connection is protected

StepWhat happensProtection
ConnectingYour treasurer approves Capofila on Stripe’s own page. The link is signed and tied to your club and the admin who started it, so it can’t be replayed for another club.Signed · one club
Every request to StripeSent from our server over an encrypted connection, naming your club’s account. Your club’s own keys are never needed.TLS 1.2+
Messages from StripeEach carries Stripe’s signature, which we check first. Anything unsigned is refused.Signature checked
DisconnectingRemove us in your Stripe dashboard. Stripe tells us, and we stop at once.Instant
Our own Stripe keyKept out of our code. Only the Capofila server can use it, and it can only reach accounts that have approved us.Server only

Where your data lives

Everything runs in Amazon Web Services’ Sydney region, and nowhere else.

DataWhere it livesProtection
Members, tiers, dues status and recordsPostgres database in AWS Sydney, not reachable from the internetAES-256 · AWS KMS
Server diskThe machine Capofila runs onAES-256 · AWS KMS
Backups7 days of automatic database backupsAES-256 · AWS KMS
ConnectionsBrowser to Cloudflare over TLS 1.3; Cloudflare to our server over a private tunnel that our server opens outward; no open portsTLS 1.3 · encrypted tunnel

Report a problem

Email [email protected]. We’ll acknowledge it within 3 business days and keep you posted until it’s fixed. Our security.txt is at capofila.app/.well-known/security.txt.

Please test only against your own account, don’t access or change anyone else’s data, and don’t disrupt the service. We won’t pursue good-faith research that follows these rules.