Documentation
Legal

Acceptable Use Policy

What may and may not be done on HiveOps

Last updated: September 14, 2026

This policy says what may not be done with HiveOps. It is part of the Terms of Service, and it applies to everything run on or reached through your account, including by your own users and customers.

Agencies and freelancers may run databases for their clients from their own organization, and remain responsible for them under this policy.

1. Illegal and harmful content

Do not use HiveOps to store, send or support:

  • child sexual abuse material, or anything that sexualizes or exploits minors, which we report to law enforcement and to Cybertip.ca;
  • content or activity that is illegal where you are, in Canada, or where it is sent;
  • content that infringes someone else's copyright, trademark or other rights;
  • content that threatens, harasses or incites violence against a person or a group;
  • personal information you have no right to hold, including information collected without the consent the law requires.

2. Abuse of networks and other systems

Do not use HiveOps to:

  • send spam or unsolicited messages, or to power a service that does;
  • host or distribute malware, phishing pages or command and control infrastructure;
  • scan, probe or attack another system, including denial of service attacks and password guessing;
  • reach another customer's database or data, or try to.

3. Abuse of the Service itself

Do not:

  • use a database for anything other than being a database, including cryptocurrency mining or running unrelated workloads through it;
  • hold more than one free organization, or create accounts by automation or with other people's cards or phone numbers;
  • get around a plan's limits, a suspension or a sign-up check;
  • place sustained load on the Service that is designed to degrade it for other customers;
  • resell the free plan, or offer the Service as your own hosting product without a written agreement with us;
  • test the security of HiveOps except as section 5 allows.

4. Data that needs certification we do not have

HiveOps does not sign HIPAA business associate agreements and is not certified under PCI DSS. Do not store data that requires either, such as protected health information under HIPAA or full payment card numbers.

5. Reporting a vulnerability

If you find a security vulnerability in HiveOps, tell us at [email protected] before telling anyone else, and give us a reasonable time to fix it. While looking, use only your own accounts and data, do not degrade the Service for others, and stop as soon as you have shown the problem. We will not take action against research done in good faith within these limits.

6. What we do about a breach

Depending on how serious it is, we may warn you, limit a database, remove the content, suspend the organization, or close the account. We act without warning when there is a risk to the Service, to other customers or to anyone else, or when the activity is illegal. We may report illegal activity to the authorities and keep what the law requires us to keep.

If you believe we have acted in error, write to [email protected] within 30 days, and a person will review it.

7. Reporting abuse

To report abuse of HiveOps, email [email protected] with what you saw, where, and when.

8. Changes

We may update this policy, and the date at the top shows the latest version. We will email the owners of every organization about any change that restricts what was allowed before.

On this page