Trust & Security

01 · The Money

Club staff never hold the game money.

Members’ game money is held by a licensed custodian, and a member’s stake is set aside the moment a game starts. Settlement is computed on the server, to the cent, and credited to the winners as soon as every player has confirmed the scores. No client can write a balance, no employee can create one, a ruling moves money only through the server with the name of whoever decided it, and every movement lands on a ledger no member, staffer or club can edit.

Games and settlement module in the Club1 Pro Dashboard

The club’s social feed in the Club1 member app

02 · The Privacy

The club’s community belongs to its members.

Club staff cannot open members’ direct messages; a message a member reports is the one a designated staffer sees. Every club’s data is isolated to that club, and member data is never sold, and never shared for anyone’s advertising. The club’s directory, its conversations, and its habits stay inside the gates.

03 · The Record

Everything auditable. Nothing arguable.

Rulings move money atomically and log who decided what, when. Hole-in-one claims take two independent witnesses and a golf staff sign-off before a dollar moves. When the connection drops, the register keeps selling to house accounts, for cash and on the club’s own card terminal, keeps each sale on the device, up to $2,000 a sale, and posts it once when the connection returns; card payments Club1 runs wait for the connection. The system is built for the moment somebody asks “prove it”, and it always can.

Dispute resolution and pro rulings in Club1

The posture, in four lines.

What a board should ask any platform, and our answers.

$0

Of members’ game money held by club staff. A licensed custodian holds it; the server settles it.

Append-only

Ledgers no user can edit. A correction is a new entry.

Isolated

Every club’s data, walled to that club.

Never sold

Member data is not a revenue line. It never will be.

Run to an audit standard

What a board can ask for, in one place.

Live status, the support promise as the desk measures it, the policy binder with its dates, the tests that run before every release, and the load report from tournament week. Everything here is written down and dated before a club goes live.

Status status.club1.io

Staff dashboard and registersmonitored

Member app servicesmonitored

Payments and emailClub1’s own checks of each servicemonitored

Public monitors check every three minutes, with ninety days of history. Nothing on the page is set by hand. The promise is 99.9% a month.

Open the live status page

The support promise Schedule A

P1The money path, the register, the tee sheet, or the app or dashboard downAnswered in 15 minutes and worked within the hour. Money, around the clock; the rest, 6 AM to 9 PM Eastern, seven days.

P2Something a member or staffer cannot doAnswered within an hour of desk hours, Monday to Friday, 8 AM to 6 PM Eastern; resolved, or a named owner with a plan, the same desk day. A ticket filed in the last two desk hours starts the next business day.

P3Everything elseResolved, or a named owner with a plan, by the close of the next business day.

Every ticket carries its own clocks, and a missed target is written down and reported in the club’s quarterly review.

Custody and money Partner custody

Club1 never holds member moneyMembers’ money is held by a licensed custodian; Club1’s server instructs it

Licensed wallet infrastructureBrale, Inc.NMLS 2376957

Full card numbers and bank credentials never reach Club1Collected and kept by the partners; Club1 keeps only the last four digits and the card brand

Outside counsel’s written review of the custody structure

SOC 2 is the standard the binder is written toIndependent penetration test and SOC 2 Type I: on the roadmap

The binder Twelve documents, dated

Information Security PolicyAug 6, 2026

Business Continuity and Disaster RecoveryAug 6, 2026

Data Retention PolicyAug 6, 2026

Risk AssessmentAug 6, 2026

System DescriptionA pre-launch description, before any independent reviewAug 6, 2026

Training and Acknowledgment PackAug 6, 2026

Incident Response PlanAug 15, 2026

Vendor Due Diligence PolicyAug 15, 2026

AML Compliance ProgramAug 15, 2026

Responsible Gaming PolicyAug 22, 2026

Terms of ServiceSep 26, 2026

Privacy PolicyOct 8, 2026

Shared under a non-disclosure agreement. Nothing is downloaded from this page.

Before every release As of Oct 24, 2026

Database testsMoney, roles and rows: every role that must be refused is refused, and the books tie to the cent489

Browser specsThe staff dashboard, screen by screen189

Phone flowsThe member app, on a device126

A release runs against the test copy before it reaches a club. The counts are test files, read from the code on the day this page is published.

Tournament week The load report

Twenty registers and two tents on one propertyPro shop sales and bar checks to house accounts, card slips recorded; at four times the pace, p95 0.22 sp95 0.20 s · 0 errors

Sunday close across the network620 members’ statements, each of 15 clubs’ day for the ledger, the settlement between clubsp95 2.3 s · 0 errors

Every TV in the clubhouse, liveTwenty screens on one clubhouse address, for ten minutesp95 3.3 s · 0 errors

Run against the test copy from many clients, with the books tied out after each run. Last run October 24, 2026: 15 clubs, 620 members, every sale, slip and charge tied out to the cent. The scripts that produced it: e2e/load/tournament.

Data The club’s

OwnershipThe club’s data is the club’s, exportable from the dashboard

IsolationEvery club’s records are walled to that club, by the database’s own rules

ResidencyStored in the United States

Never soldMember data is not a revenue line

Questions about any of this: ray@club1.io.

Request Founder access.

A small number of founding slots remain. Every request is reviewed personally.

Received. We review every Founder request personally and will reach out directly.

Built to be
trusted.