Acceptable Use Policy

This Acceptable Use Policy (“AUP”) is part of the Terms of Service. It applies to everyone who uses NamiDB Cloud: account holders, organization members and anyone who uses an organization’s API keys, including the end users of applications built on the Service. Customers are responsible for making their users comply.

It exists to keep the Service lawful, secure and fast for everyone sharing it. The examples below are not exhaustive; we apply the policy according to its purpose.

Do not use the Service to store, process, distribute or link to:

• child sexual abuse material, or anything that sexualises minors. We report such material to the National Center for Missing & Exploited Children (NCMEC) and the authorities, and terminate the account;
• content that infringes or misappropriates intellectual property, privacy or publicity rights;
• personal data collected or processed unlawfully, including data obtained through breaches, credential dumps, scraping in violation of law or terms, or covert surveillance; or data used for doxxing, stalking or harassment;
• content that promotes or facilitates terrorism, violent extremism, human trafficking or non-consensual intimate imagery;
• content or activity that is fraudulent, deceptive or otherwise illegal where you or we operate.

Do not:

• access, or try to access, data, accounts, organizations or systems you are not authorised to, including other customers’ databases and NamiDB’s internal endpoints;
• probe, scan or test the vulnerability of the Service, except under our vulnerability disclosure policy;
• use the Service to host or coordinate malware, botnets, command-and-control infrastructure, phishing, credential stuffing or attacks against others;
• send spam or unsolicited bulk messages, including invitations to people who did not ask for them;
• overwhelm or degrade the Service on purpose (denial of service), or run load tests that exceed your plan’s limits without asking us first;
• circumvent rate limits, plan limits, metering, the spend cap, pauses, suspensions or access controls, for example by creating multiple accounts or Free organizations, rotating keys to evade limits, or sharing an organization across unrelated parties to stay on the Free plan;
• share, publish or sell API keys or credentials, or embed read-write keys in client-side code where untrusted people can extract them;
• interfere with other customers’ use of the Service.

These uses need our written agreement first:

• storing protected health information subject to HIPAA, or payment card data subject to PCI DSS;
• high-risk uses where a failure could lead to death, personal injury or severe environmental damage, such as controlling medical devices, aircraft, vehicles or critical infrastructure;
• reselling the Service as a database-hosting product without substantial functionality of your own.

Sanctions and export controls

Do not use the Service from, or on behalf of anyone in, a country or region subject to comprehensive U.S. sanctions, or on behalf of any person on a U.S. restricted-party list, or for any purpose prohibited by export laws, as described in the Terms.

The Service is shared by many customers. Every plan has rate, concurrency, session, timeout and size limits that the Service enforces automatically. Workloads that are legitimate but still degrade the Service for others, such as sustained use at the limits that exhausts shared capacity, will be raised with you first; we may ask you to move to a higher plan or adjust the workload, and we may throttle it while we talk.

If we reasonably believe this AUP has been violated, we may, depending on severity:

1. contact the organization’s owners and ask them to fix the issue within a stated time;
2. throttle requests, revoke API keys, or block writes or reads;
3. remove or disable access to specific content;
4. suspend the organization or the account, as described in the Terms;
5. terminate the account for serious or repeated violations, and report illegal activity to the authorities.

We act proportionately and, unless there is an emergency or the law prevents it, we warn first. We do not monitor Customer Content proactively; we act on reports, on signals from our automated protections and on what we learn while operating the Service. If you think we got it wrong, reply to our notice and a person will review it.

Report suspected violations to info@namidb.com with the subject “Abuse report”. Include what you observed, when, and any identifier that helps us find it: the URL of the application involved, the NamiDB request ID (the x-request-id response header), the source IP address or the organization name. We acknowledge reports within three business days.

Copyright complaints follow the procedure in the Terms. Security vulnerabilities go through the disclosure policy.

Changes. We may update this AUP as the Service and abuse patterns change; material changes follow the notice process in the Terms.