Privacy on casina.biz
The most important thing on this page is what is absent. casina.biz is an editorial site: it has no accounts, no registration, no cashier and no payment processing. It never sees a card number, an IBAN, an identity document or a balance, because none of those things pass through it. Anything of that kind belongs to the operator, under the operator's own privacy policy — a separate document, on a separate site, controlled by a separate company.
What is collected here
Ordinary web technical data, gathered automatically when a page loads: an IP address, browser and device type, operating system, the page requested, the referring page and the timestamp. Where a reader writes to us, we hold the message and the address it came from for as long as it takes to deal with it. Nothing else is asked for, and there is no form on this site that requests personal details.
Why it is collected
To keep the site working and to make it better: understanding which guides are read, where readers leave, whether pages load acceptably on mobile connections in Portugal, and where the navigation fails people. Aggregate patterns are the useful output; individual readers are not the subject of interest.
Cookies and analytics
Like most sites, casina.biz uses cookies — some necessary for the pages to function, others for analytics. Google Analytics 4 provides the audience measurement. You are in control of the analytics layer: browser settings can block or delete cookies, and the major browsers all offer a per-site control that survives future visits. Blocking them does not break the reading experience here.
Under the GDPR the lawful basis for necessary cookies is legitimate interest in operating the site; anything beyond that is handled through consent. Because this is an EU-facing site, the rules that apply are the European ones, supervised in Portugal by the CNPD.
Affiliate links and what they pass on
Some links here are partner links, and following one hands the operator a tracking parameter identifying this site as the referrer. That is the entire mechanism behind the commission described on our affiliate disclosure page. What crosses over is the referral identifier, not your personal data — we do not know who followed a link, whether you registered, or what you did afterwards. Once you are on the operator's domain, their privacy policy governs everything.
How long anything is kept
Analytics data is retained no longer than 24 months from the last visit and then deleted. Correspondence is kept only as long as the matter is live, plus a short period in case it reopens. Nothing here is held indefinitely, because there is no reason to hold it.
Your rights
Under the GDPR you may ask what data is held about you, ask for it to be corrected, ask for it to be erased, object to processing, or ask for it in a portable form. Requests are handled through the contact page, and a reader in Portugal who is unsatisfied with the response may complain to the CNPD, the national data protection authority. Note again that requests about an account, a deposit or a document have to go to the operator, since that data has never been ours.
Security and transfers
The site is served over an encrypted connection, access to the systems behind it is restricted, and the data held is deliberately minimal — the strongest protection against a breach being not to hold anything worth stealing. Because analytics providers operate internationally, some processing takes place outside the European Economic Area under the safeguards those providers are required to maintain.
Changes to this page
If the practice changes — a different analytics tool, a new category of data — this page is updated and re-dated rather than quietly amended. Continued use of the site after a change means the current version applies.
Cookies in practice
A privacy policy is a statement of what is collected and why; cookies are the mechanism through which most of it happens on a website. Necessary cookies keep pages functioning and remember basic preferences. Analytics cookies count visits and describe behaviour in aggregate. Neither category on this site identifies a reader by name, because no reader ever supplies a name.
Responsible handling means collecting only what is needed and deleting it when it stops being needed, which is the standard applied here. Browser-level cookie controls are the practical tool for anyone who prefers to opt out entirely, and using them costs nothing in functionality on this domain.
What the operator collects, by contrast
An operator's data footprint is far larger, and understanding it is part of deciding whether to open an account. Everything typed into a cashier — card details, an identity document, an address, an IBAN — travels to the operator over an encrypted channel and is retained under obligations that come with the licence rather than being deleted on request; anti-money-laundering rules generally require records to be kept for years.
From there data moves in a few predictable directions: to the payment provider that executes the transfer, to the service that verifies documents, and to the regulator when it asks. That is normal and it is also the reason to read the operator's own privacy policy before depositing rather than after. The verification process itself is described on our withdrawal guide.