Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Gdpr and webhosting providers

Hello, some questions

How do e.u. registered (and not only) hosting providers handle data deletion requests from clients? I see there are some data retention requested by law, some financial, other for email, etc. to keep for 7-10years.

How do you handle such request, you keep those or delete them, too?

Looks like you are required to keep record logs even for data request, processing them, store the details, if accepted or not.

How do you handle fraud verification, do you use external services, is it gdpr safe to do without asking and get consent from client to pass data to another company for verification?

Services like google or cloudflare, etc for captchas, are ok to use or analytics?

Do you need to inform clients if you do not operate your own infrastructure (you are a reseller) and lease other company hardware? Or do you have to inform clients if you store backups externally and request for their permission?

For web domains, you proxy buyer data or send it, as per whois rules, to upstream provider?

Billing software like blesta, whmcs, etc does their developers have access to client data?

Should be better to not store client info in it and reduce the possibilty to leak it in case of a breach etc?
Do any of you store it hashed or anon?

Also, when you send order confirmation by email, do you send client info like name or passwords etc in clear or at least you cut some, to not expose data, in transit or to client email provider. I see some providers exposing ip address when login or order, is this ok, or you can get fined if complaint is made?

Any of you have been fined by data protection agencies? If yes, why?

Comments

  • @NeedDeal said: How do you handle such request, you keep those or delete them, too?

    All request are forwarded to /dev/null.

  • aluyaluy Member, Patron Provider

    if you ask i delete

  • @aluy said:
    if you ask i delete

    if you don't ask i don't delete

    Thanked by 2nghialele eb1995
  • MannDudeMannDude Patron Provider, Veteran
    edited July 2025

    GDPR is mostly dumb.

    Intentions may seem well at surface level but I'd say most ignore it.

    We're not EU based nor do we know which of our customers are EU based. With that said:

    • We don't use any 3rd party analytic / tracking / whatever. https://goaccess.io/ is a pretty nifty tool though.
    • We'll delete your account if you ask.
    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)
    • CAPTCHAs are annoying, we try to avoid them but may enable them in certain areas if need be temporarily. (Not 3rd party, though)

    Etc.

  • @MannDude said:

    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)

    Very underrated point, IMO. Less information given to fewer middlemen = better. Wish more hosting providers (and industries) adopted this philosophy.

    Thanked by 3NeedDeal MannDude Rero
  • eriseris Member

    @MannDude said:
    GDPR is mostly dumb.

    I don't agree with this.. It has a lot of good things but also a lot of terrible things like those stupid consent things..

    • Data breaches are required to be notified
    • Whois data are by default whois protected
    • More protection what can be done with your personal data

    and so on.

  • Anything, but please stop display COOKIE & GDPR thank you!

  • MannDudeMannDude Patron Provider, Veteran

    Additionally, > @eris said:

    @MannDude said:
    GDPR is mostly dumb.

    I don't agree with this.. It has a lot of good things but also a lot of terrible things like those stupid consent things..

    • Data breaches are required to be notified
    • Whois data are by default whois protected
    • More protection what can be done with your personal data

    and so on.

    Sure, it's good on paper and I do agree with many aspects of it. Just meant it's poorly implemented and enforced, and lot of things seem to be open to interpretation and not exactly clear.

    Thanked by 1ServerBachelor
  • joelsyjoelsy Barred

    @aluy said:
    if you ask i delete

    from a user personal account or from whole your system?

  • AndreixAndreix Member, Host Rep
    edited July 2025

    @NeedDeal said:

    How do you handle fraud verification, do you use external services, is it gdpr safe to do without asking and get consent from client to pass data to another company for verification?

    For orders we find suspicious and/or trigger our basic anti-fraud mechanisms, we do ID validation via Stripe Identity.
    They do a very thorough check and if they say it's fraud, it probably is, so we reject that order no matter how many "please sir, I am legit, no rick involved.".

    Regarding deletion, it really depends on every situation. There are also EU and local laws that forbid deletion if certain criteria is met. But that's a thing you should consult with your lawyer not on LET. :smile:

  • rustelekomrustelekom Member, Patron Provider

    @nghialele said:
    Anything, but please stop display COOKIE & GDPR thank you!

    Sorry, we can't do that :) It pisses us off, just like any Internet user, but it's a requirement of the law, and it can't be ignored under great, very great penalties.

  • rustelekomrustelekom Member, Patron Provider

    @ServerBachelor said:

    @MannDude said:

    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)

    Very underrated point, IMO. Less information given to fewer middlemen = better. Wish more hosting providers (and industries) adopted this philosophy.

    It also depends on the local legislation. For example, you cannot register .ru domains without providing personal data (passport, driver's license, etc.). The registrar does not require confirmation of your data, but has the right to request documents for confirmation in future.

  • avsispavsisp Member, Patron Provider

    Having similar laws here as it's based on GDPR (we are an EU candidate), I can tell you how most of its implemented:

    • Stupid cookie notices everyone.
    • A few extra lines in privacy policy and terms
    • if someone wants this data, you make them pay and export it for them
    • If they ask to delete account and haven't paid anything before - delete it
    • If they have paid, you lock the account and keep the data for a few years Incase of chargeback, dispute, etc. as it's a legitimate business purpose and exempt.

    Etc.

    Thanked by 1eb1995
  • cmeerwcmeerw Member

    @rustelekom said:

    @nghialele said:
    Anything, but please stop display COOKIE & GDPR thank you!

    Sorry, we can't do that :) It pisses us off, just like any Internet user, but it's a requirement of the law, and it can't be ignored under great, very great penalties.

    Sure you can, if only you wanted. Functional cookies don't need any consent, so all you need to do is stop using any privacy-invading tracking cookies. So why do you chose to piss off your customers then?

    Thanked by 2tentor quicksilver03
  • cmeerwcmeerw Member

    @avsisp said: if someone wants this data, you make them pay and export it for them

    I don't think you are allowed to do that under GDPR (at least not for an initial, basic request)

  • ReroRero Member

    @ServerBachelor said:

    @MannDude said:

    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)

    Very underrated point, IMO. Less information given to fewer middlemen = better. Wish more hosting providers (and industries) adopted this philosophy.

    Right.

  • ReroRero Member

    @rustelekom said:

    @ServerBachelor said:

    @MannDude said:

    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)

    Very underrated point, IMO. Less information given to fewer middlemen = better. Wish more hosting providers (and industries) adopted this philosophy.

    It also depends on the local legislation. For example, you cannot register .ru domains without providing personal data (passport, driver's license, etc.). The registrar does not require confirmation of your data, but has the right to request documents for confirmation in future.

    we won't register .ru domains because of that.

    Thanked by 1ServerBachelor
  • @Rero said:

    @rustelekom said:

    @ServerBachelor said:

    @MannDude said:

    • Fraud verification is done at the payment processor level. PayPal is better at this than a hosting provider. We don't request PII and don't want to see your ID. I'd avoid any LowEnd provider that requires or requests an ID. Let Stripe/PayPal/whoever be responsible for payment processing and verification of transactions on their platforms. (Hot take, but whatever.)

    Very underrated point, IMO. Less information given to fewer middlemen = better. Wish more hosting providers (and industries) adopted this philosophy.

    It also depends on the local legislation. For example, you cannot register .ru domains without providing personal data (passport, driver's license, etc.). The registrar does not require confirmation of your data, but has the right to request documents for confirmation in future.

    we won't register .ru domains because of that.

    No one should register .ru :D

  • rustelekomrustelekom Member, Patron Provider
    edited July 2025

    @cmeerw said:

    @rustelekom said:

    @nghialele said:
    Anything, but please stop display COOKIE & GDPR thank you!

    Sorry, we can't do that :) It pisses us off, just like any Internet user, but it's a requirement of the law, and it can't be ignored under great, very great penalties.

    Sure you can, if only you wanted. Functional cookies don't need any consent, so all you need to do is stop using any privacy-invading tracking cookies. So why do you chose to piss off your customers then?

    According to our legislation, any information that can determine the user's IP address, location, etc., must be specified in the https://www.robovps.biz/en/privacy.html.
    In any case, our billing software collects all the information and stores it in a database. Therefore, it does not matter what you choose on the website regarding cookies. If you become our customer, your personal data will be collected. For people who are worried about privacy, we offer a choice: they see a cookie notification and can immediately leave the site. We value any choice.

    PS. I meant about that such pop-up notice piss of visitors. It seem annoyance.

  • rustelekomrustelekom Member, Patron Provider

    @Rero said:
    we won't register .ru domains because of that.

    This requirement applies not only to .ru domains. Many national domains have the same requirements.

  • DrNutellaDrNutella Member
    edited July 2025

    Sir, we did diddly squat, but here is some free lip service.
    This is LowEnd, deadpool incoming.

  • avsispavsisp Member, Patron Provider
    edited July 2025

    @cmeerw said:

    @avsisp said: if someone wants this data, you make them pay and export it for them

    I don't think you are allowed to do that under GDPR (at least not for an initial, basic request)

    You are if your system doesn't have an automated extract system and you have to manually curate the data.

    "If a request is repetitive, clearly intended to cause disruption, or requires a disproportionate amount of effort to fulfill, a fee can be charged. "

    The user can already see all their data in their client areas on most hosts. So they can just copy it down themselves. Nothing stops them from doing the same thing host would do and copy paste it to an excel doc or something.

  • DediRockDediRock Member, Patron Provider

    just delete

  • @rustelekom said:

    @Rero said:
    we won't register .ru domains because of that.

    This requirement applies not only to .ru domains. Many national domains have the same requirements.

    No one ever suggested that other countries didn't have their own requirements. :)

  • rustelekomrustelekom Member, Patron Provider

    @ServerBachelor said:
    No one ever suggested that other countries didn't have their own requirements. :)

    Maybe I'm being paranoid, but I answered your definition: "No one wants to register .ru domains." First of all, it's not true. Secondly, it follows from the context that you have a negative attitude towards .ru domains and everything related to Russia in general. I may have made a mistake, in which case I apologize.

Sign In or Register to comment.