Private storage, no public rules
Card images live in a storage bucket with no public access policies on it at all. There is no setting to get wrong, because there is no public path to begin with.
How your cards, your members and your results are handled
A golf club is handing over its members' names, handicaps and scores. This page sets out exactly what happens to them, who can reach them, and where our responsibility ends and yours begins.
The boundary
We are not a handicap authority, and we do not act like one.
GolfRSA is the official World Handicap System authority in South Africa, and HNA operates the technology behind it. They hold the official handicap relationship with the golfer.
ScribbleScore runs an HNA-compatible workflow. It takes the handicaps you give it, scores your competition with them, and produces a reviewed record of what was played.
What ScribbleScore does not do.
It does not submit scores for official handicap purposes. It does not calculate an official Handicap Index. It is not integrated with HNA, and we will not describe it as integrated until an agreement exists that makes that true.
What that means for your members.
They keep one handicap identity, and it is not ours. Nobody is asked to maintain a second app, a second profile, or a second set of numbers.
Where things live
Scorecard images, and who can reach them
A photograph of a scorecard carries names, handicaps and, usually, signatures. It is treated accordingly.
Short-lived signed links
When your staff open a card in the review screen, the image is fetched through a signed link generated for that request. There is no URL that can be shared, guessed or left lying in a browser history.
Unpublished stays unreachable
A competition is only publicly readable once an admin publishes it. Before that it is not reachable from the internet, not by a link and not by guessing an address.
Published results are deliberately kept out of search.
Result pages are set to noindex, and the administration, authentication and API routes are excluded in robots.txt. A member's name and score should be findable by someone you gave the link to, and by nobody else. Searching a member's name should not surface their Saturday score.
Who can do what
Permissions the software enforces
Role separation only counts if the software refuses, rather than the policy document asking nicely.
| Action | Scorer | Admin | Superadmin |
|---|---|---|---|
| Photograph and upload cards | Yes | Yes | Yes |
| Resolve exceptions | Yes | Yes | Yes |
| Mark a card as checked | Yes | Yes | Yes |
| Lock a card | No | Yes | Yes |
| Publish a result | No | Yes | Yes |
| Invite staff and set roles | No | Yes | Yes |
| Change another user's email address | No | Yes | Yes |
| Change a superadmin's role | No | No | No |
Superadmin is a protected role, not a more powerful one.
An admin can do everything a superadmin can do. What the superadmin role adds is protection: their own role cannot be changed from the users screen, so a club cannot accidentally demote its last owner and lock itself out of its own competitions.
Every card records who checked it and who locked it, with the time. Every correction records who made it, what it was before, and what it became. That history stays attached to the published result, which is what lets a committee settle a prize dispute from the record weeks later rather than from memory.
POPIA
Who is responsible for what
South African law is specific about this, and it is worth being specific back.
Your club is the responsible party
Your members' personal information is yours. You decide what is collected, why, and who at the club may see it. You are the one with the relationship with the member.
ScribbleScore is an operator
We process that information on your instruction, to provide the service and for nothing else. We do not sell it, we do not use it to market to your members, and we do not use it to train anything we sell to somebody else.
What we collect, and why.
Names, handicaps and scores, because a competition cannot be scored without them. Photographs of the cards, because the evidence has to outlive the argument. Staff email addresses, to sign in. Nothing else, and nothing that is not used.
Deletion, and the one thing that survives it.
Anyone can ask for their personal information to be removed, and we act within 30 days. What survives is the record that a correction was made, with no name or email attached to it, because removing that would take a result's history away from people it does not belong to. See deleting your account.
Getting your records out.
Every competition exports to CSV, with a row per player, gross and points for every hole, totals, all four countback figures and the rank. That export is deliberately complete: if you ever stop using ScribbleScore, you leave with your records in a format anything can read.
Being straight with you
What we would want to know if we were you
Every vendor security page reads the same. These are the parts ours would rather not mention.
We are early
ScribbleScore is a young product with a small number of users. We have no independent security certification, and we are not going to imply one by listing standards we merely admire.
Reading a card uses a third party
The handwriting reading runs on a commercial AI provider, which means the card image is sent to them to be read. It is not used to train their models. If that is a problem for your committee, tell us on the call rather than after.
The paper is still your backstop
We would rather you kept the signed cards for the season. Not because we expect to lose anything, but because a competition record with a paper original behind it is a stronger record than one without.
Questions
Data and privacy questions
Where are the scorecard photographs kept, and who can see them?
In private storage that is not readable from the internet. There are no public access rules on the bucket at all.
When a member of your staff opens a card in the review screen, the image is fetched through a short-lived signed link generated for that request. There is no URL that can be shared or guessed to reach a scorecard image.
Who owns the data?
You do. The competitions, the cards, the scores and the results are your club's records.
Every competition exports to CSV, with a row per player, the gross and points for every hole, the totals, the countback figures and the rank. That export is deliberately complete: if you ever stop using ScribbleScore, you leave with your records in a format anything can read.
How does this work under POPIA?
Your club is the responsible party for your members' personal information. ScribbleScore is an operator processing it on your instruction, and we process it only to provide the service.
In practice that means: we collect the minimum needed to score a competition, published results are not indexed by search engines, scorecard images are private, and we will delete a person's information on request. Our full privacy policy sets out what is held, why, and for how long.
How long do you keep everything, and can we have it deleted?
Competition records are kept for as long as your club wants them, because that history is the point: a club settles a dispute from it and publishes its honours board from it.
Anyone can ask for their personal information to be removed, and we act on that within 30 days. What survives a deletion is the record that a correction was made, without a name or email attached, because taking that away would remove a result's history from people it does not belong to.
Who can see the results?
Whoever you share the link with. A competition is only publicly readable once someone with admin rights publishes it; until then it is not reachable from the internet at all.
Published result pages are set not to be indexed by search engines, so a member's name and score do not turn up in a web search for them.
Who you are actually contracting with.
K2024490035 (Pty) Ltd trading as Lumanaire, registration number 2024/490035/07, 2-6a Lifestyle on Kloof, 50 Kloof Street, Gardens, Cape Town, 8001, South Africa. Information Officer: Jarryd Phillips, hello@lumanaire.co.za. The full privacy policy and terms are the binding versions of all of this.
Related