Privacy: what we collect and why
We keep data collection on these pages limited to what the reader’s actions call for. Two categories dominate the picture: the data a reader sends deliberately, such as a message through our contact routes, and the technical traces a visit leaves automatically, such as load-time measurements and consent records.
Both categories exist for the reader’s benefit, and the sections that follow give each piece a purpose, a storage span and a set of rights, written in plain terms, so no legal background is needed to act on them.
Data types and their purposes
| Data type | Source | Purpose |
|---|---|---|
| Contact details | Messages sent through our routes | Answering the request and keeping a case history |
| Verification documents | Uploads inside the account | Identity and payment-method checks before payouts |
| Usage data | Automatic collection during visits | Page performance, error diagnosis, security |
| Preference data | Choices made in the browser | Language, display and consent settings |
Every row serves the reader’s own action: nobody receives marketing for data given to a support case, and the purposes do not drift.
Cookies and analytics in brief
Cookies and analytics tools remember choices and measure how pages perform, and the dedicated cookie policy holds the detail.
- Essential cookies keep pages functional - session state, consent choices, security tokens.
- Analytics data arrives aggregated: page views, load times, error rates, without identifying a person.
- Preference cookies remember language and display choices between visits.
- Consent sits with the reader: the consent banner governs everything beyond the essential set.
Rights over your own data
Data protection rights apply to every category collected, and using them follows one route.
- Access: a request through the contact routes returns which data is held and for which purpose.
- Correction: wrong records get fixed once the correct value arrives.
- Deletion: data whose purpose has ended is removed, with legal retention duties named where they exist.
- Objection and restriction: processing can be narrowed or stopped where the law grants it, and the answer explains what remains and why.
- Complaint: a right that runs beside the others, addressed to the supervisory authority of the reader’s residence.
How we use information, purpose by purpose
Collection without a purpose is dead weight, so each category carries exactly one job, and the jobs stay separable.
Operating and maintaining the pages
Usage data keeps pages fast and available: error rates point at broken elements, load times point at heavy ones, and neither needs a name attached to do its work.
Answering cases and documenting them
Contact data lives as long as the case needs it plus the retention period the applicable rules set, so a follow-up question months later finds its history instead of starting over.
Security and the integrity of the service
Technical traces serve the integrity of the pages themselves: abuse patterns, automated access and consent records sit in this category, and they exist to keep the service working for everyone else.
Last updated: 11 November 2026