Privacy Policy
Effective 2026-09-24
This policy explains what data ArmRec holds, where it comes from, who can see it and how long we keep it. Controller: ArmRec, Ukraine. Contact: [email protected]. Full registration details are available on request.
Two things are true of this service and worth stating plainly: we run no advertising, and we do not track you. We count visits to the public website with Cloudflare Web Analytics, which sets no cookies and does not identify you; the app and the cabinet have no analytics at all.
What we hold
| Data | Where it comes from | Who can see it |
|---|---|---|
| Name, name in Latin script, sex, date of birth, country | You, when you fill in your profile | You; the organization that issued your licence; the organizer of a competition you entered |
| Athlete number | Issued by the platform, once | Printed on your badge, so effectively public |
| Email address | Your Google account, at sign-in | You and our staff |
| Phone, city, nickname, time zone | You | You |
| Profile photo | You | You and the registry of your issuing organization |
| Licence photo and licence fields | The organization that issued the licence | You and that organization |
| Documents attached to an application | You | The reviewer of that application. They are deleted once the application is decided |
| Matches, places, rating, refereeing record | The competition engine, during an event | Visibility of start lists is set by the organizer; results are part of the sporting record |
| Training sessions, weights, body weight | You | Only you, and anyone you deliberately share a program with |
| Guardian name and email, for minors | The minor, at registration | You, the guardian, and our staff |
| Your public profile on armrec.net: name in Latin script, country, club, matches, places, ranking, and a photo supplied by the organization | The organization that issued your licence or ran your competitions, if it publishes its results on the public website | Anyone, including search engines. Only for adults; see Public website below |
| Athletes in a coach’s group: name, date of birth, phone, photo, attendance and training plans | The coach who adds them, or your own profile once you accept that coach | The coach, and you once you have an account |
Why we are allowed to hold it
- To provide the service you asked for: your profile, licences, entries and diary.
- With your consent, for things you choose to add, such as a photo.
- For the integrity of the registry: an athlete number and a competition result must remain stable, otherwise the sporting record stops being true.
- To meet legal obligations, once payments exist.
Who else sees it
- The organization that issues or holds your licence, and, where applicable, its local branch.
- The organizer of a competition you enter, and the competition engine while that event runs.
- Everyone, for athletes of organizations that publish their results on the public website: see Public website below.
- Your coach, if you accept one.
- Google, when you sign in.
- Our infrastructure providers: Hetzner (servers, Germany) and Cloudflare (network protection and visit counting without cookies).
We do not sell data and we do not share it with advertisers or data brokers.
How long we keep it
Account data is kept while your account exists. Personal details are erased when you delete it. The sporting record, meaning licences, entries, matches and places, is kept indefinitely, because it belongs to the history of the competitions and to the organizations that issued the documents. The Account deletion page explains this in detail.
Public website
An organization can choose to publish its results on the ArmRec website. For its adult athletes we then show a public profile: name in Latin script, country, club, matches, places, supermatch ranking, and a photo if the organization supplied one. These pages can be found through search engines. The choice is made by the organization, because the results are part of its sporting record.
We never publish a date of birth, contact details or a photo you uploaded yourself, and athletes under 18 are never shown. You can object to your public profile as described under Your rights.
Coaches
A coach can add the athletes they train to a group, with name, date of birth, phone and photo, and keep attendance and training plans for them. The coach is responsible for having the athlete’s permission, and a parent’s permission for a minor. When you have an account and accept a coach, the coach also sees your profile details and training. You can ask to end that link at any time; it ends when the coach confirms, or seven days after your request.
Minors
You may create an account from the age of 13. If you are under 18, we ask for the name and email of a parent or guardian, and the account waits until they confirm it. Until then it cannot apply for a licence, enter a competition or keep a training diary. We record when the confirmation was given and for which version of these documents.
This confirmation is a reasonable effort to verify guardianship, not proof of it. We do not ask for identity documents at this step because the service has no advertising, no tracking of people, no messaging between users and no purchases. The decisions that matter, issuing a licence and admitting an athlete to a competition, are taken by an adult on the side of the federation or the organizer, on the basis of documents.
Children under 13 do not have accounts. A child can still exist in a registry or a coach’s group, entered by a federation or a coach, who is responsible for the consent of the parents.
Your rights
- Access a copy of your data.
- Correct it. Data frozen on an issued licence is corrected through the organization that issued it, and the app has a request form for that.
- Delete your account, within the limits described on the Account deletion page.
- Object to processing, and ask for your data in a portable form.
- Complain to a supervisory authority, in Ukraine to the Verkhovna Rada Commissioner for Human Rights, or to the authority of your country of residence.
Security
Access is checked on the server, not in the browser: private fields are closed at the collection level, and each screen is allowed to see only what its viewer may see. Application documents live only until the application is decided. Backups are kept encrypted at rest.
Changes
When this policy changes, we publish the new version with its effective date and record which version you accepted.