Read a thread elsewhere where the OP was complaining about being denied a refund after their account was terminated for abuse. I'm simply curious how other web hosting providers would react to a request for a refund given this circumstance?
Terms of Service should have this particular incident clearly outlined.Read a thread elsewhere where the OP was complaining about being denied a refund after their account was terminated for abuse. I'm simply curious how other web hosting providers would react to a request for a refund given this circumstance?
Terms of Service should have this particular incident clearly outlined.
yes, some I see are just basic copied TOS with little details, and have even seen TOS where they have not even bothered to change the name of where they copied them from.Agreed. It's a sad reality that the vast majority of small hosting providers don't dedicate nearly enough time or attention to getting their TOS right.
If it involves child pornography, phishing, harmful attacks, illegal activity then a backup will be done and this will be handed to the relevant law enforcement agency along with the clients details (no breach of data protection as it is being handed to law enforcement) and the account will be terminated with immediate effect and the client will not get any refund or backup of the files as why hand them a backup of their child pornography, phishing, harmful attacks, illegal activity files, so they can just set up with another host. Also if it is child pornography, phishing, harmful attacks, illegal activity and you had them a backup of these files then you can also get charged with aiding them.For me, the best way to handle this case is:
1. Send a mail to the client about the abuse, in most instances it can be solved by contacting the client, allowing sometimes to resolve the abuse
2. If no response from the client, then suspending the account after certain hours of standard time.
3. But if the abuse involves child pornography, phishing, harmful attacks, illegal activity then termination can be done by providing 3-12 hours notice beforehand. But, there maybe some possibility that the website might be hacked or compromised, so I do a full account backup before proceeding with termination in extreme cases.
In conclusion, I always recommend to backup the account before termination and then the backup file to the client.
WHY!I tend to send emails out with a few hours notice (usually 24 hours notice).
It's a good practice to send emails before termination. It isn't always 24 hours though, sometimes it's even 1-3. I just say in the email that it's 'up to 24 hours'.WHY!
If they abused your services etc. then it should be a case of immediate termination no refund and no files.
Think if they used your server to send out phishing emails to scam people, you just emailed them and gave them 24 hrs to get their files off your server so they can upload the files to a server elsewhere and continue their scam.
Just terminate the account so they dont get the files to upload elsewhere.
A scammer will not contact you asking for the files as they know by termination they have been found out.
This worries me though. 'Just' terminating accounts can have a serious impact if it is done by mistake. I always create backups before terminating in case it's done by mistake. If it is something like a scam (in this case), I copy it and hand all of the information over to law enforcement.Just terminate the account
You can tell if a mistake or not. If someone is sending phishing emails you can look at their files and see the landing page file. In cases like this its an immediate termination as why give them warning. A good host will do regular backups of their servers for their use. So why allow the fraudsters 24hrs to send out more emails to rob people and take copies of their files. Terminate to stop their fraud, they wont contact you regarding this, hand details to law enforcement, but 9/10 they gave false name and address and a free gmail account so if these get closed they just set up a new one.It's a good practice to send emails before termination. It isn't always 24 hours though, sometimes it's even 1-3. I just say in the email that it's 'up to 24 hours'.
This worries me though. 'Just' terminating accounts can have a serious impact if it is done by mistake. I always create backups before terminating in case it's done by mistake. If it is something like a scam (in this case), I copy it and hand all of the information over to law enforcement.
Good point. Well noted.You can tell if a mistake or not. If someone is sending phishing emails you can look at their files and see the landing page file. In cases like this its an immediate termination as why give them warning.
The reason I said 24 hours was because I was mentioning the maximum time I give until I suspend accounts. For scams I would allow 1-3 hours.So why allow the fraudsters 24hrs to send out more emails to rob people and take copies of their files.
And yes, we do take weekly backups.A good host will do regular backups of their servers for their use.
This would be a better solution, and I will stick to doing this in the future.If you suspect a mistake then suspend account so they cannot use it then inform client they have 24 hrs to contact you otherwise it will be terminated to protect server.
You have to think if you have a VPS with 50+ websites and you have 1 suspected phishing site then the 1st point is suspend account, inform client and then check through the sites files, if its deff a phishing site then terminate. If you suspect its been hacked then keep suspended inform client and ask them for a clean copy of the files, then inform the client you will be removing all the files from the site to protect others on the server as a rouge file on 1 account could give hackers access to the whole server and if you do nothing then your upstream provider can close down your server to protect their DCGood point. Well noted.
The reason I said 24 hours was because I was mentioning the maximum time I give until I suspend accounts. For scams I would allow 1-3 hours.
And yes, we do take weekly backups.
This would be a better solution, and I will stick to doing this in the future.
Thanks for your replies! Appreciate it.
Actualy, weekly backups are usually not part of a good data protection policy. You should think about at least daily backups, if not hourly for the databases. And the retention should be as much as possible, to be able to look back in the past, to a point there were no issues.Good point. Well noted.
The reason I said 24 hours was because I was mentioning the maximum time I give until I suspend accounts. For scams I would allow 1-3 hours.
And yes, we do take weekly backups.
This would be a better solution, and I will stick to doing this in the future.
Thanks for your replies! Appreciate it.
Are you sure?Actualy, weekly backups are usually not part of a good data protection policy.
We cannot afford the storage space. Especially if we are going hourly for the databases.You should think about at least daily backups, if not hourly for the databases.
We keep data every 4 weeks and then it gets deleted.And the retention should be as much as possible
It's not a matter of having 'issues'. It's telling your customers you lost 7 days of data if something happens.Are you sure?
It works fine with us. We have had no issues so far.
If you do incremental backups, the daily or hourly deltas are not gonna be such a burden.We cannot afford the storage space. Especially if we are going hourly for the databases.
Get a cheap vps (no need for paid os) then something like jetbackup and do daily incremental backups. This way you have daily backups in a diff dc to your servers.We cannot afford the storage space. Especially if we are going hourly for the databases.
We keep data every 4 weeks and then it gets deleted.
Thanks for letting me know.
Actualy, weekly backups are usually not part of a good data protection policy. You should think about at least daily backups, if not hourly for the databases. And the retention should be as much as possible, to be able to look back in the past, to a point there were no issues.