Privacy Policy
Who is responsible for your data
This policy covers koru-casino.app, the website you are reading, which publishes independent coverage of Koru Casino. We are the controller of the personal data described below. You can reach us about anything on this page at [email protected]. We publish this site in 23 language versions and this policy applies to all of them. Outbound links to the casino are routed through go.afftrackio.com, which records that the visit came from this website.
What we collect
We collect very little, and we do not ask you to register. In normal use that means:
- Server logs. Your IP address, the page requested, the time, the referring page and your browser’s user-agent string. These are written automatically by the web server and are what let us find faults and spot abuse.
- Analytics. Aggregate measurements of which pages are read, how long they hold attention, roughly which country a visit came from, and whether the visit came from a search engine or a link.
- Anything you send us. If you email us, we keep the message and your address for as long as it takes to deal with it.
We do not collect payment details, we do not run accounts, and we do not knowingly collect anything about children.
Why we are allowed to hold it
Server logs and basic security records rest on our legitimate interest in keeping the site running and defending it against abuse. Analytics and any non-essential cookies rest on your consent, which you give or refuse when you first arrive and can change at any time. Correspondence rests on our legitimate interest in answering you. Where the law requires us to keep something, that legal obligation is the basis.
Cookies and similar technology
Cookies are small files a site asks your browser to keep. We use a small number of them: one to remember your cookie choice, one to remember your language, and — only with your consent — analytics cookies that count visits. Blocking all cookies in your browser settings will not stop you reading the site; it may mean your language choice is forgotten between visits.
Links out, and what they carry
When you follow a link to an operator, that link usually carries a tracking parameter identifying us as the source of the visit. That is how our commission is attributed. The parameter identifies this website, not you. What the destination collects once you arrive is governed by its own privacy policy, which is worth reading before you register anywhere.
Who else sees your data
We do not sell personal data and we do not trade mailing lists. Data is handled by the companies that host this site, deliver it through a content network and provide our analytics, each acting on our instructions. We disclose data beyond that only where a law or a valid court order requires it.
Where it is processed
Our providers may process data outside the country you are reading from, including outside the European Economic Area. Where that happens it is covered by the safeguards the law provides for such transfers, such as standard contractual clauses or an adequacy decision.
How long we keep it
Server logs are kept for a short operational period and then deleted or anonymised. Analytics is held in aggregate, which stops it identifying anyone. Email is kept while the matter is open and for a reasonable period afterwards in case you write again.
Your rights
Depending on where you live you can ask us for a copy of what we hold, ask us to correct it, ask us to delete it, object to processing based on legitimate interest, ask us to restrict it, or withdraw a consent you gave. You can also complain to your national data protection authority. We answer these requests free of charge and within the period the law sets.
One practical note: because we do not run accounts, we usually hold nothing that identifies you beyond a log entry, so a request may be answered by telling you exactly that.
Security, and changes to this policy
The site is served over an encrypted connection and access to what little we store is restricted. No system is perfect, and we do not claim otherwise. If we change how we handle data we will update this page; the version here is always the one in force.