This privacy policy explains what the enKronk website and app collect about you, why, who else sees it, and how to have it removed.

enKronk is a service from ThinkTech ApS, the data controller for the information described here.

ThinkTech ApS
Aarhus, Danmark
CVR 44998459
hello@thnktech.dk

This policy covers the enKronk website and the enKronk mobile app on iOS and Android.

• Your account — name, email address, and a hashed password. You never send us a password we can read.
• Your profile — anything you choose to add: a short bio, a picture, a location, and your interests.
• Your play — the groups you belong to, the competitions you enter, every round and hole score you record, and the handicap history calculated from them.
• Your messages — messages you send to other members through the app.
• Your device — a push notification token per device, so we can reach you. Removed when you sign out.
• Linked accounts — if you connect enKronk to another service in the same family, we store the identifier that links the two.
• Which pages get visited — we keep a log of page requests so we can see what people look for, and which search engines and AI crawlers read the site. It records the page, the country, where the visit came from, and whether the visitor was signed in — never who. Your address is not stored: it is turned into a short code using a key that changes every day, so the same visitor is a different code tomorrow and the code cannot be turned back into an address. This log is not connected to your account.
• Your address, while you are signed in — your login session records the IP address it was started from, so we can spot a session being used from somewhere it should not be. It goes when the session does.

We do not collect payment card details, and we do not run advertising trackers.

Two cookies, both ours, and both needed for the site to work at all.

• Your session — keeps you signed in, and remembers your language. It holds only an identifier; everything it refers to is stored on our servers, not on your device.
• A form token — stops a form you submit from being forged by another website.

There is no advertising cookie, no analytics cookie, and nothing that follows you to other websites. That is why you are not asked to accept anything: the rules require consent for cookies that are not strictly necessary, and we do not set any.

If we ever add one, you will be asked first.

To run the thing you signed up for: keeping a scorecard, calculating standings, adjusting handicaps, and letting your group see the result. That is performance of our agreement with you.

Scores are visible to the other members of the group they were recorded in. That is the point of a group competition, and it is worth being clear about: a round you record is not private to you.

We also keep enough technical logs to find and fix faults, on the basis of our legitimate interest in the service working.

We use a small number of processors, each doing one job:

• Hosting — our servers and database, inside the EU.
• Email delivery — sending sign-in, verification and notification email.
• Push notifications — Google Firebase Cloud Messaging, which delivers to both Android and iOS.
• Error diagnostics — an EU service that receives crash and error reports so faults get fixed. It runs on the server AND in your browser: if a page throws an error, a report is sent containing the address of the page, your browser version, the page you came from and your IP address. It sends nothing when nothing goes wrong.
• Backup storage — encrypted backups held with an EU object-storage provider.
• Map tiles — OpenStreetMap draws the maps on club and discovery pages. A map does not load until you ask for it, and only then does OpenStreetMap receive your IP address.

We do not sell your data, and we do not share it for anyone else's marketing.

If you join a group challenge counted in steps, distance or exercise time, the app can fill your entries from Apple Health or Health Connect instead of you typing them.

• Only if you turn it on. Your phone asks first, per data type, and you can withdraw it at any time in iOS Health or Android Health Connect. Nothing is read before you agree.
• Only daily totals — steps, distance, and exercise minutes. We read nothing else. We do not read heart rate, and we do not read workout routes or any other location from your health data.
• Only the total leaves your phone. Individual samples stay on the device; what reaches us is the number that fills in a challenge entry.
• Only the group sees it. A total appears to the members of the challenge you entered it in, exactly as a typed number would. It is never used for advertising and never sold.

Turning the connection off stops any further reading. Entries already counted in a finished challenge stay, for the same reason a recorded score does.

The camera is used only when you choose to take a photo or a video. A photo or video you send is stored like any other message or album photo.

Lenses find your face on your phone. When you pick a lens, the app finds where your face is in the camera picture, so the effect sits on it. That happens entirely on the phone: no picture, no face data and no measurement of your face is sent to us or to anyone else — not even to Google, whose face model it is — and none of it is stored. The finished photo or video, with the effect in it, is only sent if you send it.

A group can keep its own routes — a loop, a hill — and members can put their times on them. Both start with a file you choose to upload, and neither keeps more of it than this:

• A route you share is kept as a line on the map and the heights along it, and the whole line is shown to the members of that group. Any times in the file are not read: we do not keep when, or how fast, anyone travelled it. If the line starts at your door, you can cut its ends off, and what you cut is deleted.
• A ride you upload to be timed is compared with the group's routes while the file is being read. What we keep is the route, your name, the day and the time it took you — shown to the members of that group. The file is not stored, and neither is where you went.
• A route you draw by picking points on the map is made by sending those points to LokalAtlas, our sister service, which answers with the road between them. Only the points are sent — nothing about you or your group.
• A route your group lists in the catalogue can be found and copied by other groups on enKronk. What they see is the route: its name, its line and its heights. They do not see who shared it, which group it is from, or anyone's times on it. It can be taken out of the catalogue again at any time; a group that has already copied it keeps its copy.

You can take your own times off a route at any time, and whoever shared a route can remove it.

Your account and your play stay until you delete the account. Backups are kept on a rolling schedule and age out, so a deleted account can persist in a backup for a short period after deletion before it is overwritten.

The page log described above is kept for 30 days, after which only counts remain — no addresses, no identifiers. A login session, and the address recorded with it, expires after 10 days.

You can ask for a copy of your data, ask us to correct it, ask us to delete it, or object to how we use it. Write to hello@thnktech.dk and we will answer within one month.

One limit worth stating plainly: scores you recorded in a group competition form part of that competition's result for everyone in it. If you delete your account we remove your profile, but a finished competition keeps its result.

If you think we have handled your data badly you can complain to the Danish Data Protection Agency (Datatilsynet), datatilsynet.dk.

enKronk is not intended for children under 13, and we do not knowingly create accounts for them.

If this policy changes in a way that affects you, we will tell you in the app before the change takes effect.