Acceptable-use policy
Version 2026-10-25 · Effective 25 October 2026 · What changed ·
This policy says what you may not do with Drasken Cloud and what we do when it is broken. It is part of our terms of service and you accept it together with them.
On this page
The short version
This summary helps you find your way. It is not part of the agreement; the sections below are.
- No mining, attacks, spam, phishing, malware or open proxies, and nothing the law does not allow.
- Do not get around the platform's limits or security, or use resources in a way that harms others.
- Outbound port 25 is closed. Send email through an email provider, only to people who asked for it.
- Unless harm is happening now, we tell you first and give you time to fix it.
- We act on the smallest scope we can: usually one app or job before the whole organisation.
- Suspension never deletes your data. If you think we got it wrong, tell us and we look again.
- Report abuse coming from Drasken Cloud to
abuse@draskencloud.com.
1. Who and what this policy covers
In short
Everything your organisation runs, stores or sends through Drasken Cloud, and everyone you let use it.
1.1 What it covers
This policy applies to everything you run, store or send through Drasken Cloud: apps, jobs, databases, volumes, domains and the console. It also applies to traffic your apps send to the internet and to anything your apps let other people do.
1.2 Who it covers
It applies to you and to everyone you let use your organisation, including its members and the users of your apps. You are responsible for their use as if it were your own, as 3.5 of the terms says.
1.3 Part of the terms
This policy is part of the terms of service (3.3). It has the same version as the terms and changes with them. Words defined in the terms mean the same here.
2. What is not allowed
In short
Nine kinds of use are not allowed on Drasken Cloud. Content the law does not allow is listed once, in 3.4 of the terms.
You must not use Drasken Cloud, or let anyone else use it, for any of the following:
- Cryptocurrency mining, in any form, including "idle" or browser-based mining.
- Attacks on any system: denial-of-service, flooding, port or vulnerability scanning, brute-forcing passwords, exploiting vulnerabilities, or sending traffic meant to disrupt. This applies to every target, Drasken Cloud and other customers included, unless the target's owner has authorised it in writing.
- Spam and unsolicited bulk messages: email, SMS or messages on any service. Section 4 says how to send email.
- Phishing, fraud and impersonation: pages or messages that pretend to be someone else, or that collect credentials, payment details or personal data under false pretences.
- Malware: hosting, distributing or controlling malicious software, botnets or command-and-control servers.
- Content the law does not allow: anything listed in 3.4 of the terms, "Content you must not host". That is the one list; this policy does not repeat it.
- Open proxies, open relays and anonymising services offered to the public, such as public VPN exit points or Tor exit relays.
- Getting around the platform's limits or security: evading quotas, rate limits, network separation or suspensions; trying to reach other customers' projects or the platform's own systems; or using several accounts to do so.
- Using resources in a way that harms others: work designed to exhaust the platform's capacity (CPU, memory, disk or network) beyond what your plan provides. Section 3 says more.
Security testing of your own apps is allowed. Testing anyone else's system, including the platform itself, needs that owner's written permission first.
3. Fair use of resources
In short
Stay within your organisation's limits and use shared resources fairly. Reaching a limit stops new resources; it does not stop what is running.
3.1 Limits
Every organisation has limits on what it can run at once and on the size of each resource. Your current limits are in the console, and our limits documentation lists the starting limits and how they grow. When a limit is reached, new resources and scale-ups are refused; what is already running is not affected. You can ask for a higher limit, as 3.6 of the terms describes.
3.2 Rate limits
The console has rate limits. When you reach one, the request is refused and the message says when to try again. Do not spread requests over several accounts or addresses to avoid them.
3.3 Shared resources
Your apps, jobs and databases share the platform's servers and network with other customers. You may use everything your plan provides, including heavy work for a while. You must not run work whose purpose is to use up capacity, or that slows the platform for others in a way your plan does not provide for.
4. Sending email
In short
Outbound port 25 is closed. Send through an email provider on port 587 or 465, and only to people who asked for your mail.
4.1 Port 25 is closed
Apps and jobs on Drasken Cloud cannot send email straight to mail servers on port 25. This is the same for every organisation and we do not open it on request.
4.2 How to send email
Use an email provider and connect to it on port 587 or 465. Send only to people who asked for your mail, and follow the provider's rules as well as this policy.
4.3 Bulk and marketing mail
Bulk or marketing mail must go only to people who agreed to receive it, and must let them unsubscribe easily. Mail that breaks this is spam under section 2, whichever provider sends it.
5. What we do
In short
We tell you first unless harm is happening now. We act on the smallest scope that deals with the problem, keep the evidence, and never delete your data by suspending.
5.1 How we find out
To protect the platform and other customers, we watch how resources behave: for example sustained full CPU use, unusual outbound traffic, or connections to known abusive addresses such as mining pools. We also receive reports from our providers and the public. This looks at how resources behave, not at the contents of your databases or files. When we investigate, we look at your content only as 4.3 of the terms allows.
5.2 Notice first, where we can
Unless harm is happening now, we tell your organisation's owners what is wrong and give a reasonable time to fix it before we act (8.2 of the terms). Our notice says what we found, which resource is involved and what you need to do.
5.3 When harm is happening now
When harm is happening or about to happen, we may act at once and tell the owners as soon as we can afterwards. This covers:
- an attack, malware, phishing, spam or mining;
- content the law does not allow;
- a risk to other customers, the platform or anyone else, for example a compromised app sending attacks;
- an order from a court or government authority that needs immediate action.
5.4 The smallest scope
We act on the smallest scope that deals with the problem, usually the resource involved before the whole organisation:
| Step | What it means |
|---|---|
| Stop one resource | We stop the app or pause the job involved. Everything else keeps running |
| Remove or disable content | We remove or disable access to content the law does not allow, as 3.4 of the terms says |
| Suspend the organisation | For serious or repeated abuse. Apps stop; jobs, scheduled jobs and databases pause; members can still sign in to contact us |
| End the agreement | For serious or repeated abuse, under 8.5 of the terms |
8.3 of the terms sets out exactly what suspension does. Suspension never deletes data, and storage is still charged while it is kept.
5.5 Evidence and reporting
We keep evidence of abuse. When we remove or disable content, we keep a copy of it and the related records for at least 180 days, as Indian law requires (4.10 of the terms). We report illegal activity to the authorities where the law requires it, and may report it in other cases.
5.6 Lifting the action
We lift an action when its cause is fixed and we are satisfied it will not happen again. Tell us what you changed by replying to our notice.
6. If you think we got it wrong
In short
Reply to our notice or write to support and we look again. If you are still not satisfied, you can go to our Grievance Officer and then to the Grievance Appellate Committee.
6.1 Ask us to look again
Reply to our notice, or write to support@draskencloud.com, and say why you think we got it wrong. We look at it again promptly and tell you the outcome.
6.2 Grievance Officer
If you are not satisfied, you can complain to our Grievance Officer at grievance@draskencloud.com. Their full details are on our grievance page. The Grievance Officer acknowledges a complaint within 24 hours and resolves it within 15 days.
6.3 Grievance Appellate Committee
If you are not satisfied with the Grievance Officer's decision, you may appeal within 30 days to the Grievance Appellate Committee set up by the Government of India. Your rights under 10 of the terms, including going to a Consumer Commission, are not affected.
7. Reporting abuse
In short
Report abuse coming from Drasken Cloud to abuse@draskencloud.com.
If you see spam, phishing, malware, attacks or other abuse coming from Drasken Cloud, write to abuse@draskencloud.com. Our report abuse page says what to include and what happens next. To complain about content under Indian law, write to our Grievance Officer at grievance@draskencloud.com, as our grievance page explains.
8. Changes to this policy
In short
This policy changes with the terms, under the same rules: at least 30 days' notice for a change that affects you.
This policy has the same version as the terms of service and changes with them, under 11 of the terms. If a change reduces your rights or adds to your duties in a meaningful way, we tell your organisation's owners by email and in the console at least 30 days before it takes effect. When it takes effect, the console asks each user to accept the new version before they continue. If you do not agree, you can delete your resources and close your organisation before that date. If you do not accept, you can still sign in to export your data and close your organisation.
Once a year we remind every organisation's owners of this policy and of 3.4 of the terms.
What changed
| Version | Effective | What changed |
|---|---|---|
| 2026-10-25 | 25 October 2026 | First published version. |