Acceptable Use Policy · effective 17 October 2026
Acceptable use_
Fresh is shared infrastructure: what one account does affects everyone else’s machines, addresses and reputation. These rules keep it a good place to host. They are part of our Terms of Service.
What you must not do
You, and anyone using your account or your resources, must not use Fresh to:
- break the law, or host, share or link to illegal content, including child sexual abuse material and terrorist content;
- send spam or unsolicited bulk messages, run phishing or other scams, or host pages that collect credentials under false pretences;
- distribute or control malware, ransomware or botnets;
- scan, probe, attack, flood or break into systems or networks you do not own, or have no written permission to test;
- forge addresses, email headers, DNS records or anyone’s identity;
- infringe copyright, trade marks, privacy or other people’s rights;
- harass, threaten or defraud anyone;
- get around account limits, suspensions, billing, network filters or other security controls, or try to reach another customer’s resources or our own systems;
- mine cryptocurrency;
- resell Fresh in a way that hides who is responsible for a resource, unless we have agreed it in writing.
Lawful development, hosting, research and security testing of your own systems are all welcome.
Fair use of shared resources
Plans share physical CPUs, disks and network links. Data transfer is not charged, and each machine can use 100 Mbit/s, bursting to 1 Gbit/s for short transfers. In return, please don’t run sustained traffic, CPU or disk load that harms other customers. If that happens, we will contact you first where we can, and may limit the resource if the problem continues.
- Managed apps cannot send email on port 25. Set them up with your own email provider instead.
- Virtual machines may send email, but only to people who asked for it, with a working unsubscribe link for anything bulk, and in line with the law. If a machine sends spam, we may block its email or stop it.
Your responsibilities
Keep your account credentials, API tokens and SSH keys private. Keep the software in your machines up to date and secure what you expose to the internet. If one of your machines is compromised, stop it or take it off the network, and tell us at help@fresh.dev. Don’t use a Fresh machine to strike back at an attacker.
Reporting abuse
Email help@fresh.dev with the subject “Abuse report”. Include the IP address or hostname, the date and time with time zone, and what happened, with evidence such as log lines or email headers. Please don’t send passwords, private keys or more personal data than the report needs. We reply during the support hours in our SLA and act on serious reports straight away.
What we do about a breach
We respond in proportion to the harm. We may warn you, ask you to fix a problem, limit traffic, block a port, stop a machine, app or database, or suspend or close the account. Where it is safe and lawful, we tell you first and give you time to fix it. For active attacks, illegal content, a compromised machine or a risk to other customers, we act immediately and tell you afterwards.
We may keep records related to a report and pass them to the police or other authorities when the law requires it or when people are at risk. We handle any personal data involved as described in our Privacy Policy.
Appeals
If you think we got it wrong, reply to our message or email help@fresh.dev with your account email, what you have fixed and any evidence. A person reviews every appeal and tells you the outcome.
Changes
We may update this policy as threats and the law change, and we email you about material changes.