Acceptable Use Policy
Effective date: August 1, 2026 · Last updated: July 27, 2026
1. Purpose and Scope
This Acceptable Use Policy ("AUP") applies to everyone who accesses any Burdenoff product, the shared platform layer (identity, billing, notifications, developer portal, and marketplace), our GraphQL APIs, or our websites (together, the "Service"). It supplements, and is incorporated by reference into, our Terms of Service. Violating this AUP is a material breach of those Terms and may result in warning, content removal, feature restriction, suspension, or termination, at our discretion and proportionate to the severity and recurrence of the violation.
2. Prohibited Activities
You must not use the Service to, or to allow or enable any third party to:
- violate any applicable law, regulation, or the intellectual property, privacy, publicity, or other rights of any third party;
- attempt to access another tenant's or workspace's data, or otherwise attempt to bypass tenant isolation, authentication, or access-control mechanisms;
- upload, store, or transmit malware, ransomware, or other malicious code, or attempt to gain unauthorized access to the Service, other accounts, or our infrastructure;
- send or facilitate unsolicited bulk communications (spam), phishing, or other deceptive messaging through or using the Service, including through the notifications or newsletter features;
- interfere with or disrupt the integrity, availability, or performance of the Service, including through denial-of-service activity, excessive automated load, scraping outside documented and permitted API use, or circumvention of rate limits, quotas, or access controls;
- reverse engineer, decompile, or attempt to derive the source code of the Service, except to the extent applicable law expressly permits;
- resell, sublicense, or provide the Service to third parties as a managed or hosted service without a separate written reseller or partner agreement with Burdenoff;
- use the Service to generate, store, or distribute content that is unlawful, fraudulent, defamatory, obscene, or that exploits or endangers minors;
- misrepresent your identity, impersonate any person or entity, or falsely state or imply an affiliation with Burdenoff;
- use an AI-assisted feature to generate content that violates this AUP, or attempt to extract, probe, or reverse the underlying model, prompts, or safety configuration beyond documented, permitted API use; or
- violate export control, sanctions, or similar laws applicable to your use of the Service.
3. Marketplace and Developer Conduct
If you publish an application, integration, or listing through the developer portal or app marketplace, you must additionally comply with our Marketplace & Developer Agreement, including its listing-content, moderation, and takedown provisions. We may remove a listing, suspend a developer or publisher account, or withhold a pending payout where we reasonably believe this AUP or that Agreement has been violated.
4. Reporting Violations
To report a suspected violation of this AUP, a security vulnerability, or abuse of the Service, contact security@burdenoff.com (security issues) or contact@burdenoff.com (all other reports). We investigate reports in good faith and take action proportional to the evidence and severity.
5. Enforcement
We may investigate suspected violations of this AUP and take any action we deem appropriate, including issuing a warning, removing or disabling access to content, suspending API keys or accounts, or terminating the Service under Section 12 of our Terms of Service. We may also report unlawful activity to relevant law enforcement authorities.
6. Changes to This Policy
We may update this AUP from time to time to reflect changes to the Service or applicable law. Material changes take effect no sooner than 30 days after we post the updated policy on this page with a new "Last updated" date. Continuing to use the Service after that date constitutes acceptance of the updated AUP.
7. Contact
Questions about this Acceptable Use Policy: contact@burdenoff.com
Effective date: August 1, 2026 · Last updated: July 27, 2026