Acceptable Use Policy
Last updated: October 9, 2026
This Acceptable Use Policy applies to anyone who accesses the Task Manager API (the "Service"), whether through the REST API directly, through an application you build on it, or through the home page playground. It is part of, and should be read together with, our Terms of Use. We may suspend or terminate access for a violation of this policy, as described in the Terms.
1. Prohibited activity
You may not use the Service to:
- violate any applicable law or regulation, or the rights of any third party, including intellectual property, privacy, or publicity rights;
- store or transmit content that is unlawful, defamatory, harassing, or that contains malware or other harmful code;
- access, or attempt to access, another user's account, tasks, or data without authorization;
- reverse engineer, decompile, or attempt to extract the source code of the Service, except to the extent such a restriction is prohibited by applicable law;
- misrepresent your identity, impersonate another person or entity, or falsify your affiliation with any person or entity; or
- use the Service to build a product or service that is substantially similar to, and competes directly with, the Service, using data or access obtained from it in a way not permitted by these policies.
2. Security testing and research
We welcome good-faith security research. However, you may not probe, scan, or test the Service for vulnerabilities, attempt to bypass authentication or rate limiting, or perform load testing against the production API, without our prior written permission. If you believe you have found a security issue, please report it to us directly at iamsupremedevelopers@gmail.com rather than disclosing it publicly, and give us a reasonable opportunity to address it before any public disclosure.
3. Automated use and rate limits
The Service applies rate limits to certain endpoints, in particular account registration, login, and password-reset requests, to protect user accounts and the availability of the Service for everyone. Rate limit values and the response headers used to signal them are described in the API documentation.
You agree not to:
- attempt to evade a rate limit, for example by rotating IP addresses, accounts, or identifiers for that purpose;
- send automated requests designed to guess passwords, enumerate registered email addresses, or otherwise attack user accounts;
- generate a volume of traffic to the Service that is disproportionate to genuine use and that risks degrading it for other users; or
- use automated means to scrape or bulk-extract data from the Service beyond your own account's data, accessed through the documented API.
If your intended use requires higher limits than those published in the documentation, contact us at the address above before building against the assumption of higher limits.
4. Responsible API integration
If you build an application on top of the Service, you are responsible for how your application and its users interact with the API, including obtaining any consent your own users need to give before you submit their data to the Service on their behalf, and for complying with applicable law in how you collect, use, and disclose data within your own application.
Because the API uses bearer tokens rather than cookies for authentication, you are responsible for storing tokens issued to your application securely and for not exposing them in client-side code, public repositories, or logs accessible to others.
5. Enforcement
We may investigate suspected violations of this policy and take action we consider appropriate, which may include issuing a warning, removing or disabling access to specific content, temporarily or permanently suspending or terminating an account, and reporting conduct to law enforcement where required or appropriate. Where practical, and where we do not believe doing so would create a security risk, we will give notice before taking action.
6. Changes to this policy
We may update this Acceptable Use Policy from time to time, in the same way and for the same reasons described in our Terms of Use. We will update the "Last updated" date above when we do.
7. Contact
To report a violation of this policy, or to ask about a use case not covered here, contact us at iamsupremedevelopers@gmail.com.