Draft, under review

This document is a draft that has not yet been checked by an attorney. Parts in [square brackets] are still to be filled in. Version 2026-09-29-draft.

Privacy Notice

1. Who we are

Diski Connect is run by [Diski Connect (Pty) Ltd, registration number ____] ("we"). We help organisers run football tournaments and help teams, officials, sponsors, vendors and supporters take part. We are a "responsible party" for the personal information described here.

Information officer [name]
Email [email]
Phone [phone]
Address [address]

Organisers are responsible parties too for the information they collect and use to run their own tournaments (for example squad sheets). They must follow this notice and the Terms of Use.

2. What we collect, and why

Who What we collect Why
Everyone with an account Name, email, phone (optional), password (stored scrambled, never in plain text), the roles you choose To let you sign in and use the parts of Diski Connect that are yours
Players Full name, date of birth, ID number (and an ID check code made from it), position, jersey number, photo, medical certificate To register you, check age-group eligibility, keep matches safe and apply bans fairly
Team managers Team name, township, contact name and phone, squad list, logo, equipment records To enter tournaments and run the team
Organisers Tournament details, entry fees, prizes, grounds and map pins, sponsor deals, posters, photos, headcounts To run the tournament and show it on the public events guide
Match officials and observers Name, contact details, qualifications, match ratings and reports To book officials and keep matches fair
Sponsors Company name, contact person, logo, pledges and deposit records (including the slip) To record what was agreed, and show that it was paid and delivered
Vendors Business name, contact details, stall bookings To manage stalls
Commentators Name, contact details, clips To book commentary and show clips
Payments Amount, purpose, status and reference. Card details are handled by our payment provider and are never stored by us To show who has paid
Everyone One sign-in cookie that the site needs to work; basic technical logs To keep the site working and safe

We do not use your information for advertising, and we do not sell it.

3. Sensitive information

Some of what we hold needs extra care.

  • Medical certificates are health information. They are seen only by you, your team manager, the organiser of a tournament you are entered in, and our administrators where needed to check you can play. Never shown publicly.
  • Conduct records and notes about police reports. If someone is sent off, banned, or a serious incident is reported, we keep a record and, sometimes, a note that the police were told. A ban follows the person (matched by ID number) across teams and across divisions of the same event, so a suspension cannot be dodged. These records are seen only by the people who need them to run a fair tournament, and by the person concerned (see section 4). They describe events and decisions and are not a finding of guilt in a court.
  • Children. Many players are under 18. We keep a child's information only with the consent of a parent or guardian (Form B1). We never show a child's ID number, date of birth or medical information publicly.

4. Who can see what

Who What they can see
Anyone on the internet Public tournament pages: event name, dates, ground and map pin, entry fee, prizes, fixtures, results, team names, confirmed sponsors, and gallery photos people have agreed to. Never a player's ID number, date of birth, phone number or medical information, and never a list of attendees
The organiser of a tournament Teams, squads and records needed to run it
Verified organisers Conduct records [intended: limited to organisers with a legitimate connection] so that a ban is recognised
Match officials and observers Fixtures and squads for their matches
A team manager Their own team and squad; their team's conduct records
Sponsors Their own pledges and deposit records, and the public pages. Totals (teams, matches, people counted) and photographs of branding, but never player lists or details
Administrators What they need to verify accounts, resolve disputes and keep the platform working

The organiser's registered name appears on their tournament's public page.

5. Who we share it with

  • Our payment provider (PayFast), to take payments.
  • Our hosting provider, which stores the site, database and files on servers in [country and city]. [If outside South Africa, say so and say how it is protected.]
  • Organisers, officials and sponsors, only as section 4 describes.
  • The police or a court, where the law requires it.

We do not give sponsors or anyone else lists of players or their details.

6. How long we keep it

[Proposals: decide with your attorney and accountant.]

Information Proposed
Your account While it is open, and [12 months] after you close it
Player records Until the player asks, or [3 years] after they last played
ID number and exact date of birth Deleted [12 months] after the team's last tournament. The ID check code and the year of birth are kept, as described below
ID check code While a ban could still apply, or [5 years] after the player last took part, whichever is later
Medical certificates Until the end of the season they were for, then deleted
Conduct records and suspensions While a ban could still apply, then [5 years]
Gallery photos Until the person asks for removal
Payment and financial records As long as the law requires (commonly 5 years; confirm)
Sponsor deposit records The same as financial records
Technical logs [90 days]

Some records (for example a conduct record or a payment record) may have to be kept even if you ask us to delete them. We will tell you why.

7. How we keep it safe

  • Passwords are stored scrambled (hashed), never in plain text.
  • People see only what their role needs. Restricted files (medical certificates, deposit slips, equipment documents) open only for the people the record allows.
  • Private files are not stored in shared caches.
  • We back the database up and check that the backups can be restored. [Confirm once backups exist.]
  • We keep a plan for security incidents. If something goes wrong that could harm you, we will tell you and the Information Regulator as the law requires.

No system is perfect.

8. Your rights

You may ask us to:

  • show you what we hold about you;
  • correct it if it is wrong or out of date;
  • delete it, subject to records we must keep;
  • stop using it in a particular way, or object to how we use it;
  • withdraw a consent you gave (for example for photos). Withdrawing does not undo what was already lawfully done.

Ask by writing to the information officer (section 1). We will answer within [30 days]. We may need to check who you are first.

9. Children

A parent or guardian must agree before we keep a child's information or show a child's photo. They can withdraw that agreement at any time by writing to the information officer. If we discover we hold a child's information without consent, we will remove it or obtain the consent.

10. Automated decisions

We do not use artificial intelligence or automated decision-making to decide anything about a person. Rules such as tiebreaks, ban carry-over and rating windows are applied by the platform as written, and a person can appeal a conduct decision.

11. Cookies

We use one cookie to keep you signed in, and one to remember which team a manager is working on. Neither is used for tracking or advertising.

12. Complaints and changes

If you think we have handled your information wrongly, tell us first. You may also complain to the Information Regulator: [current contact details, check before publishing].

If we change this notice, we will publish the new version with its date and tell you if the change matters. Last updated: [date].

ID check codes

When a player is registered we make an ID check code from their ID number. It is a scrambled code: it cannot be turned back into the number. We use it for two things only: so that a ban follows the same person to another team or tournament, and so that we can confirm, if you register again, that you are the same player. We delete the readable ID number a few months after your team's last tournament and keep the code. The code is still personal information, because it identifies you when your ID number is entered again, so it is protected like the rest of your record and deleted on the schedule above.