Privacy and security

TeeGuard analyses an encrypted video stream from the course in real time and stores only what the club needs to manage play. The system looks for people, never for faces, and blurs the head of every person it detects before anything is stored in the cloud. No video is stored. What is kept is numbers and one blurred image per event, and the image is deleted within 24 hours. The club is the data controller, TeeGuard is the data processor, and the database and the images are stored in the EU.

Last updated 4 November 2026 · Version 1.1

1.The reality
The camera sensor sends an encrypted video stream to TeeGuard's service. A group is in the picture, for example two players: one in white trousers and a green top, the other in white trousers and a blue top, around 170 and 180 cm tall.
2.The analysis
The service identifies that two people are standing on the tee, the combination of clothes they are wearing and a coarse height class for each person, in 10 cm ranges.
3.Storage & Privacy
What the system stores is the number of people, their clothing combinations, a coarse height class for each person and the time.
A blurred image is kept and deleted within 24 hours. The sensors do not know who the players are.

Illustration with sample data.

What happens on the course

1.
The sensor watches the playing area
The sensor sits at a selected location, faces the playing area and sends an encrypted video stream to TeeGuard's service in the region.
2.
The service only looks for the number of people
The model is set to a single class: number of people. It has no function for faces or body posture, and it cannot tell who anyone is.
3.
The head is blurred
The service blurs the top 30 per cent of the box around every person it detects, where the head is. This happens in memory, before anything is stored in the cloud.
4.
The image is discarded
The video stream is analysed frame by frame in the service's memory and is never stored. If the sensor loses contact, nothing is analysed and no image is stored. No video is recorded.
5.
Numbers and a blurred image are stored
What is stored is the number of people, the time, clothing colour, a rough height band (a 10 cm range, never an exact height) and one blurred image per event. Clothing colour is used to recognise the same group at the next sensor.

What TeeGuard never does

Face detection or facial recognition. Our codebase has an automated check that stops the build if known face or pose detection libraries are added.
Record or store video.
Sell data or share it for marketing.
Mix clubs' data. Each club sees only its own.

Can the club see who is playing?

The sensor cannot tell who anyone is. The club can however choose to connect its GIT booking schedule to TeeGuard's system. The system then matches which group passed a specific sensor at a given time against the booking. During an active alert, the club's authorised staff can see who is booked in that group. This is done entirely on the club's instructions. Marshals and other users cannot look up individual players or personal data in the system.

What is stored, where and for how long

The table applies unless the club has agreed otherwise.

Data	Where	How long	Who sees it
Count, time, clothing colour and rough height band	In the EU	30 days	The club manager, or staff the club manager appoints
Blurred image per event	In the EU	Deleted automatically within 24 hours	Only the club's owners
Video	Not stored	Never recorded. The stream is analysed in real time and never stored.	No one
Images during a network outage	Not stored	During an outage nothing is analysed and no image is stored	No one
Names and tee times, if the club connects its booking system	In the EU	As agreed with the club	The club manager, or staff the club manager appoints
Alert events per player, such as slow play or a missed tee time, if the club uses the feature	In the EU	As agreed with the club	The club manager, or staff the club manager appoints

Roles and agreements

The club is the data controller for the pace-of-play analysis. TeeGuard is the data processor and processes data only on the club's instructions. We sign a data processing agreement with the club before anything is installed. If we change a sub-processor we give the club 30 days' notice, and if the agreement ends the club's data is deleted within 30 days.

What the club needs to do

Under Swedish law, a golf club normally needs no permit to put up camera sensors to analyse the pace of play on its course. Rules differ between countries, and at the demo we go through what applies to your club. As data controller, the club does need to:

Carry out a balancing test, weighing the club's interest against players' privacy.
Carry out an impact assessment, since the pace-of-play analysis is systematic and uses new technology.
Approve TeeGuard putting up signs at the sensors and by the first tee stating the purpose, who is responsible and how to reach them, people's rights and where the full information can be found.
Inform members and guests, for example on the club's website.

Security

Encrypted traffic (TLS) between the course, the cloud and the web app.
Encrypted storage in the cloud.
Access per role and per club, checked by the database on every request from the web app.
Blurred images are deleted automatically within 24 hours, and the deletion is monitored.
If a personal data breach occurs, we notify the club within 24 hours so that it can report it to the Swedish Authority for Privacy Protection (IMY) within 72 hours.

Read about the platform TeeGuard is built on