Acceptable Use Policy

Last updated: 6 September 2026

This policy sets out what you may and may not do with VPNDetection, operated by Mslm Dev. It forms part of our Terms of Service, and the definitions there apply here. Using the Service means accepting it.

Most of it is what you would expect. The section that is specific to what we sell is section 2, on what our data may be used for, and it is the one worth reading even if you skip the rest.

1. Lawful use

You must use the Service lawfully, and not in a way that breaches any applicable law or regulation, infringes anyone's intellectual property, privacy or publicity rights, or exposes us to liability. You are responsible for what is done with your account and your API keys.

The Service is not tailored to industry-specific regimes such as HIPAA, FISMA or GLBA. If your use would be subject to those, do not use the Service without agreeing separate terms with us in writing.

2. What our data may be used for

Our datasets describe network infrastructure - which ranges belong to VPN operators, proxy networks, hosting providers and the like. They are built to answer a question about an address, not about a person, and that is the line this section draws.

You must not use the Service:

To harass, stalk, intimidate or discriminate against any individual or group, or to build a profile of an identifiable person.
To make a decision about a person with legal or similarly significant effects for them - credit, employment, housing, insurance, or access to essential services - where our classification is a material input and no human reviews it.
In a way that breaches data protection law in your jurisdiction or your users'. Where an address is personal data where you are, you are its controller and we process it as your processor for the purpose of answering your query.
To infer, or to represent that we infer, an individual's identity, location, household, employer, or membership of any protected class.

A classification is a probabilistic statement about infrastructure and can be wrong about any particular address. Treating it as proof of anything about a person is a misuse of it as well as a mistake.

3. Redistribution

What you may do with the data beyond your own use is set by your licence type, which is shown against every database in your account. Unless your licence says redistribute, you must not resell, republish, sublicense or otherwise pass our data to a third party, or use it to build a competing classification dataset.

An evaluation licence is narrower still: limited internal testing only. Integrating it across a product, or serving real customer use cases with it, needs our written permission first.

Showing a result to your own end user as part of your product is normal use, not redistribution. Handing over the underlying data, in bulk or as a feed, is redistribution. If you are unsure which one you are doing, ask us before you ship it.

4. Limits, keys and access

Do not circumvent rate limits, quotas or authentication, or systematically extract data beyond the limits of your plan.
Do not share API keys with third parties, or use credentials that are not yours. A key identifies your organization and everything done with it is attributed to you.
Do not run automated access designed to disguise its volume or origin - rotating keys or addresses to defeat a limit is circumvention.
Do not reverse engineer, decompile or attempt to derive the source of the Service, except to the extent that restriction is unenforceable where you are.

5. Security and integrity

Do not probe, scan or test the vulnerability of the Service or its infrastructure, or breach or circumvent any security or authentication measure.
Do not transmit malware, or anything designed to interfere with, damage or gain unauthorised access to a system or network.
Do not interfere with anyone else's use of the Service, including by overloading it.

Good-faith security research is welcome and is not a breach of this section. Tell us at security@vpndetection.io before you start, keep the testing to your own account, and give us a reasonable chance to fix what you find before you publish it.

6. Content and conduct

Where the Service lets you submit content - a support message, an organization name, a webhook target - do not submit anything unlawful, defamatory, obscene, threatening, or that advocates violence or hatred against a group. Do not impersonate another person, misrepresent your affiliation, or send unsolicited bulk messages through anything we operate.

7. Reporting a breach

If you believe someone is using the Service in breach of this policy, tell us at support@vpndetection.io with enough detail to identify what you saw. We investigate what is reported to us; we do not monitor how customers use the data, and we are not responsible for a breach by a customer beyond acting on it once we know.

8. What happens if you breach it

We may suspend or terminate access for a breach of this policy, and we may do so without notice where continued access presents a risk to the Service, to other customers, or to us. A period during which an account was suspended for a breach is not refunded - see the Refund Policy.

Where the law requires it, or where there is a credible risk to someone's safety, we may report a breach to the relevant authorities.

Suspension is not our first move for something that looks like a mistake. If we think you have wandered over a line, we would rather email you about it.

9. Changes

We update this policy as the Service and the law change. The "Last updated" date above shows the current version, and material changes are notified to account holders.

10. Contact

Mslm Dev
195-B Jasmine Block Sector C Bahria Town
Lahore, Punjab 53720, Pakistan
support@vpndetection.io