Sub-processors
Version 2026-10-25 · Effective 25 October 2026 · What changed ·
This page lists the companies Drasken Labs Private Limited uses to run Drasken Cloud that handle personal data for us or for you. It says what each one does, what personal data it handles, where it works, and how we tell you before the list changes.
On this page
The short version
This summary helps you find your way. The sections below give the detail.
- Your apps and databases run on OVHcloud servers in Mumbai, India.
- Cloudflare carries traffic to our sites, hosts the console and documentation, and stores backups, logs and support attachments. It may keep them outside India.
- Amazon Web Services sends our emails and runs Drasken Uptime's checks, in Mumbai.
- Razorpay takes payments in India. Google Analytics runs only if you allow it.
- We tell you here at least 14 days before we add a provider, and by email if you ask.
- Under our data processing addendum, part of every customer's agreement, you may object to a new provider.
1. About this list
In short
These providers handle personal data only on our instructions. We stay responsible to you for what they do.
1.1 Who we are
Drasken Cloud is run by Drasken Labs Private Limited (CIN U62091DL2025PTC453940), registered office 416, Block C (Old No. C-196), Gali No. 7, Om Nagar, Badarpur, South Delhi, Delhi 110044, India.
1.2 What a sub-processor is
A sub-processor is a company we use that handles personal data in the course of running Drasken Cloud. Some handle personal data about you, such as your account and billing details. Some handle personal data inside your content, such as the records in your databases and backups. For the second kind, we act for you under our data processing addendum.
1.3 Our responsibility
Each provider handles personal data only for the purpose we give it. We remain responsible to you for our duties under the terms when we use them. Our privacy policy explains how we handle personal data about you.
2. Providers that handle personal data
In short
Six providers. Apps and databases are in Mumbai; Cloudflare and Google may handle data outside India.
2.1 The list
| Provider | What they do | Personal data | Where | Used for |
|---|---|---|---|---|
| OVHcloud | The servers that run your apps and databases, the console's service and our own databases | Everything we store about you, and everything in your apps, databases and volumes | Mumbai, India | Apps, jobs, databases, volumes, the console's service, billing |
| Cloudflare | Carries traffic to our sites and to your apps' default addresses; hosts the console and documentation; receives emails sent to our support reply addresses; stores backups, logs, invoice files and support attachments | Network addresses, browser details, the content of requests passing through, logs, support emails and files, invoices, and the contents of your backups | Network: worldwide. Storage: Cloudflare's "Asia-Pacific" location, which may be outside India | Every site, backups, logs, invoices, support |
| Amazon Web Services | Sends our emails; runs Drasken Uptime's checks, schedules and results; keeps copies of our own databases | Email addresses and email contents; the addresses you monitor and their results; the records in our own databases | Mumbai, India | Account, alert and billing emails; Drasken Uptime; our database copies |
| Razorpay | Takes payments and runs payment mandates | Name, email address, mobile number, billing details and payment details. Card details stay with Razorpay | India | Billing and payments |
| Google Analytics on our website and documentation, and later the console, only if you allow it | Pages viewed, device and browser, approximate location | Outside India, including the United States | Website and documentation analytics | |
| Let's Encrypt | Issues certificates for your custom domains and some of our addresses | Domain names only | United States | Domains and certificates |
2.2 Where your data is
Your apps and databases run in our region in Mumbai, India. The console's own data and the billing records are also held there. Backups, logs, invoice files and support attachments are stored with Cloudflare. Cloudflare's storage is set to its "Asia-Pacific" location, which is a preference, not a promise of India, so these may be stored outside India.
Where a provider handles personal data outside India, it does so under its contract with us. We do not send personal data to a country the Government of India restricts.
2.3 What each provider sees of your content
Only OVHcloud and Cloudflare hold your content. OVHcloud holds it on the servers that run it. Cloudflare holds your backups and logs, and carries traffic to and from your apps' default addresses. Database backups are encrypted at rest by the storage service. Amazon Web Services receives only the addresses you ask Drasken Uptime to check, and Let's Encrypt only the domain names you connect. The other providers do not receive your content.
3. Providers that do not handle customer personal data
In short
We also use services that hold only our own code or business. They are listed so you know we checked.
| Provider | What we use it for | Why it is not a sub-processor |
|---|---|---|
| GitHub | Our source code and the software images we build for our own services | It holds no customer data and no personal data about our customers |
If we start to put customer personal data with one of these providers, we move it to section 2 and give notice as section 5 says.
4. How we choose and bind providers
In short
We choose providers for what they need to do, give them only the data they need, and use each under a contract that protects personal data.
4.1 How we choose
Before we use a provider for personal data, we check:
- that we need it, and what personal data it must handle;
- where it will handle the data, and whether that place is allowed under Indian law;
- what it says about security and how it handles personal data.
4.2 How we bind them
We use each provider under a written contract, including its data protection terms. The contract limits what the provider may do with personal data to the service it gives us. We give each provider only the access its job needs, and keep the keys that reach our systems to what that job requires.
4.3 When a provider has a problem
If a provider tells us about a breach that affects personal data, we act as our privacy policy and our data processing addendum describe.
5. How we tell you about changes
In short
We update this page at least 14 days before a new provider starts handling personal data. Ask us and we email you too.
5.1 Notice
Before we add or replace a provider in section 2, we update this page and add an entry to section 6. We do this at least 14 days before the provider starts handling personal data.
If a provider fails, or we must replace one quickly for security, we may give shorter notice. We tell you as soon as we can, and the same right to object applies.
Removing a provider, or correcting its details without changing what it does, needs no notice. We still record it in section 6.
5.2 Email notice
Organisation owners can ask to receive an email whenever this list changes. Write to privacy@draskencloud.com from the owner's address, naming the organisation.
5.3 Objecting
Our data processing addendum is part of every customer's agreement. Under it, you may object to a new provider on reasonable data protection grounds. Write to privacy@draskencloud.com within the notice period and say why. We will discuss it with you and look for a way to meet your concern. If we cannot, the addendum explains how you may end the affected service.
6. Changes to this list
In short
Every change to the list, with its date.
| Date | Change |
|---|---|
| 2026-10-25 | First published list. |
What changed
| Version | Effective | What changed |
|---|---|---|
| 2026-10-25 | 25 October 2026 | First published version. |