版本 1.1，发布于 2026-08-29。本声明无需接受：它说明我们如何处理您的数据。
本声明仅有英文版本。
Eurhosting Partner Program — Privacy Notice
Version 1.1 — published 29 August 2026
This notice explains what we do with your personal data as a Partner in the Eurhosting Partner Program: what we hold, why, for how long, who else sees it, and what you can require of us.
It describes what the system actually does. Every retention period below is enforced by code that runs every day, not by intention.
1. Who is responsible
Eurhosting SHPK, Sallmone, Shijak, Durrës, Albania, NIPT M52305043P, is the controller of your personal data.
For anything in this notice — including exercising the rights in section 7 — write to partners@eurhosting.net.
2. What we do not do
Before the detail, the two things that shape everything else.
You never receive customer data. The dashboard shows you aggregate numbers only: reflink opens, trials, active customers, amounts. You do not receive, and cannot obtain through the Program, the identity of any customer — no name, no email address, no account identifier, not even a pseudonymous one. This is a deliberate design constraint, enforced in the code that builds those figures, and not merely a policy.
We do not profile you and we do not advertise to you. There is no automated decision-making, no scoring, no behavioural tracking of your use of the site, and no advertising or analytics cookie anywhere in your account area.
3. What we hold, why, and for how long
3.1 Registration and sign-in
Your email address, a hash of your password, your second-factor secret (stored encrypted), and hashes of your recovery codes. Recovery codes are never stored in readable form — only their hashes, so we cannot tell you what they are, we can only check one you present.
Purpose: creating and protecting your account. Legal basis: performance of the contract, Art. 6(1)(b) GDPR. Retention: for as long as your account exists.
3.2 Identity and address
First name, surname, address, city, country, and — if you act as a business — company name and VAT number.
Purpose: identifying our contractual counterparty and issuing the documents that accompany a payment. Legal basis: performance of the contract, and legal obligation, Art. 6(1)(c), for the parts that appear on accounting documents. Retention: for as long as your account exists; the copies that appear on issued documents follow section 3.7.
3.3 Payment details, and their history
Payment method, account holder, IBAN, BIC, bank name, account number, or the free-form details you give us for a method we do not model. We also keep a record of each change: what the details were, who changed them, and when.
Purpose: paying you, and being able to answer a question about a payment that went to the wrong place. Legal basis: performance of the contract. Retention: current details for as long as your account exists; superseded entries in the change history are deleted after 24 months. The details actually used for a payment already made are frozen inside that payment's document and follow section 3.7.
3.4 Sign-in attempts
Each failed and successful sign-in attempt is counted, against the email address used and against the network the request came from.
We do not store your full IP address for this purpose in every case, and the difference is worth stating precisely:
- an IPv4 address is stored in full — four bytes, the whole address;
- an IPv6 address is truncated to its first 64 bits, its network prefix, with the remaining half overwritten with zeroes.
The reason is practical rather than decorative: whoever attacks a login form over IPv6 typically controls an entire /64 and would change the last half at every attempt, so counting the exact address would protect nobody, while the prefix is both effective and less identifying.
Purpose: stopping password guessing. Legal basis: legitimate interest, Art. 6(1)(f) — our interest in keeping accounts from being broken into, and yours in the same thing. Retention: 7 days, and the attempts recorded against your account are deleted immediately when you sign in successfully.
3.5 Password reset requests
When you ask to reset your password we store a hash of the single-use link, its expiry, whether it was used, and the network the request came from (treated exactly as in 3.4).
Purpose: letting you back into your account, and letting us answer if you report a reset email you did not ask for. Legal basis: performance of the contract and legitimate interest in the security of the account. Retention: the link expires in 30 minutes and the record is deleted one day after expiry.
3.6 Messages we send you
Every message the system sends you is queued before delivery: recipient address, subject, and the body of the message in both HTML and plain text.
Purpose: delivering welcome messages, password resets, threshold alerts and payment documents reliably, so that a temporary mail failure does not lose them. Legal basis: performance of the contract. Retention: 30 days after the message is sent, or 30 days after it is abandoned if it could not be delivered. The queue is a delivery mechanism, not an archive of correspondence.
3.7 Accounting and payment records
Commission entries, payouts, the frozen snapshot of the data each pro forma was built from — including your identity and the payment details used at that moment — and the PDF documents themselves.
Purpose: paying you and meeting our accounting and tax obligations. Legal basis: legal obligation, Art. 6(1)(c). Retention: these are not deleted. Accounting records are kept for the periods our obligations require, and our accountants keep the fiscal documents for the period their own obligations impose on them. A request to erase your data cannot remove them; see section 7.
3.8 Record of documents you accepted
For each document you accept — today, the Partner Agreement — we store which version, in which language, when, and a cryptographic fingerprint of the exact text.
Purpose: being able to establish, later and for either of us, what was agreed. Legal basis: legal obligation and our legitimate interest in being able to prove the terms of a contract. Retention: not deleted — a record that disappears proves nothing.
3.9 Operator action log
Actions taken on the system are recorded with the email address they concern: registration, password change, second factor enabled, document accepted, payout marked as paid — and also failed sign-in attempts and account blocks.
Purpose: security and accountability, so that we can reconstruct who did what after an incident. Legal basis: legitimate interest, Art. 6(1)(f). Retention: 24 months.
3.10 Activity metadata
The date of your last sign-in, whether you have been notified that your balance crossed the payout threshold, and the moment from which your existing sessions stop being valid (which is how a password change signs out every other device).
Purpose: operating the account. Legal basis: performance of the contract. Retention: for as long as your account exists.
3.11 Language
The language you choose, stored in a cookie and, once you have an account, against it. Legal basis: performance of the contract. Retention: for as long as your account exists.
3.12 Cookies and session data
The site sets only technical cookies. There are no advertising, profiling or third-party analytics cookies anywhere in the Program.
- a session cookie while you are signed in, which expires after 30 minutes of inactivity;
- a language cookie, holding your language choice;
- a separate session cookie for our own operators, on the operator area.
The corresponding session files on the server hold a session identifier and the anti-forgery token for your forms. Abandoned session files are deleted after 24 hours, which is well beyond the 30-minute lifetime of the session itself.
3.13 Web server logs
Like every web server, ours records each request: IP address, browser identification, the address requested, and the moment.
Purpose: operating the service and investigating faults and abuse. Legal basis: legitimate interest, Art. 6(1)(f). Retention: logs rotate weekly and rotated logs are kept for about four weeks. IP addresses are anonymised when the log rotates, so full addresses exist only in the log of the current week.
3.14 Reflink statistics
We count how many times pages carrying your referral code were opened. The counting is done with Umami, an analytics program we run ourselves on Eurhosting infrastructure — it is not a third-party service, and nothing is sent to anyone else.
What the Program keeps for you is a count per referral code and per calendar month: no IP address, no cookie, no browser identification, nothing about any individual visitor.
The Umami instance itself measures the products' public websites, and for those it keeps what ordinary web analytics keeps — country, browser, device, pages opened — without setting cookies and without storing IP addresses. That is analytics of a product's own website rather than of this Program: none of it reaches your dashboard, and nothing in it is linked to you beyond the monthly count above. We are drawing the distinction because the previous version of this notice described only the count, which was true of your data and could be read as a description of the whole instance.
Purpose: showing you how your link is performing. Legal basis: performance of the contract. Retention: 24 months.
3.15 Events received from products
When a customer you referred registers or pays, the product sends us the event. It carries an opaque reference to the customer's account — never a name or an email address — plus the amount and the moment.
This is customer data, not yours, and it never reaches you (section 2). It is listed here because it is the material from which your commissions are calculated. Legal basis: performance of the contract with you, and with the customer on the product's side. Retention: 24 months for the raw events; the resulting commission entries follow section 3.7. A customer's attribution to your code is kept while it is live, and deleted 24 months after that customer relationship ends.
4. Who else sees your data
4.1 Our own infrastructure
These are not third-party recipients — they are our own systems — but you should know what runs where.
- The mail server (
box.euhostingmail.it), operated by Eurhosting and hosted in the Aruba datacentre in Italy. Every message we send you passes through it: your address, your name, and the content of the message. - Umami, the analytics program described in 3.14, on Eurhosting infrastructure. What it holds for this Program is the monthly counts; what it holds about visitors to the products' own websites is described in that section.
4.2 Third parties
- Cloudflare — the anti-automation check on the **registration page only**, and on no other page of this site. When you open that page your browser contacts Cloudflare, which receives your IP address, browser characteristics and interaction signals in order to tell a person from a script. It is the only request this site makes to any external domain.
- Our accountants, who receive the fiscal documents relating to payments made to you, as required to keep our books.
- Keyweb, the datacentre hosting the machine this site runs on, and Hetzner, hosting other servers of the ecosystem. Both within the European Union. They provide the machines; they do not use your data.
We do not sell your data, and we do not share it with anyone for their own purposes.
5. Transfers outside the European Union
Two, and we would rather name both plainly.
Albania. All the servers described above are in the European Union, but Eurhosting SHPK is an Albanian company and administers the system from Albania. Access from a country outside the Union is itself a transfer to a third country, whatever the location of the hardware. Albania has no adequacy decision from the European Commission, so the transfer relies on the Standard Contractual Clauses adopted by the Commission, together with the technical measures described in this notice.
The United States. The Cloudflare check in 4.2 sends the data listed there to a company established in the United States. That transfer relies on Cloudflare's own transfer framework and the Standard Contractual Clauses. It happens on the registration page only, once, before you have an account.
6. Where the data is not
For completeness, since a notice that only lists what exists tells half the story: there is no advertising network, no marketing platform, no CRM, no external analytics service, no chat widget, and no social plugin anywhere in the Program. The complete list of external requests this site makes is the single one in 4.2.
7. Your rights
You have the right to:
- access your data and obtain a copy of it;
- rectify anything inaccurate or incomplete;
- erase your data, subject to what follows;
- restrict processing while a dispute about it is resolved;
- portability — receive the data you gave us in a structured, commonly used, machine-readable format, and have it sent to another controller where technically feasible;
- object to processing based on legitimate interest, including the processing described in 3.4, 3.9 and 3.13;
- complain to a supervisory authority, in the country where you live or work, or where you believe the problem occurred.
How to exercise them: write to partners@eurhosting.net from the address registered on your account, or from another address if you also tell us how to identify you. We reply without undue delay and within one month. If a request is complex we may extend that by two further months, and we will tell you within the first month if that happens.
The one limit worth stating in advance. Erasure cannot reach the accounting records in 3.7 or the acceptance records in 3.8: we are required to keep the first, and the second is the proof of an agreement between us. Everything else can be deleted, and closing your account removes it on the schedules described above. If you close your account with commissions still owed to you, the Partner Agreement provides that they are paid at the next billing run.
8. Changes to this notice
If this notice changes we publish a new version at the same address, with a new version number and date. The version you are reading is at the top of this page, and earlier versions are kept.
Version 1.1 clarified section 3.14: it now distinguishes what the Program keeps about you — a monthly count — from what the analytics instance keeps about visitors to the products' websites. Nothing about the handling of your own data changed.
本文本的指纹（SHA-256），每次接受时一并记录：
923943b201bc7b1a8100789aa7701981fa4e86057d626336ebb5aea23a854da2