Acceptable Use Policy

ACCEPTABLE USE POLICY This Acceptable Use Policy ("AUP") protects Got2Dev Business Manager (the "Service"), GOT2DEV, INC. ("GOT2DEV," "we," "us," or "our"), businesses, users, infrastructure, service providers, and third parties from misuse. It applies to all users of the Service, including authorized business users and customer-portal users, as applicable. This AUP should be read together with the published Terms of Service and Privacy Policy. A violation of this AUP may result in action under Section 11 and the Terms of Service. 1. LEGAL AND AUTHORIZED USE Users must use Got2Dev Business Manager only for lawful purposes and only within the authority granted by the business that controls the workspace or other applicable account. Users must comply with applicable laws, regulations, court orders, contractual obligations, and third-party rights. 2. SECURITY ABUSE Users must not probe, scan, test, bypass, defeat, or interfere with authentication, authorization, tenant isolation, rate limits, anti-forgery controls, access controls, monitoring, or other security mechanisms without express authorization. Credential theft, session hijacking, unauthorized account access, and attempts to obtain another tenant's data are prohibited. Security testing against GOT2DEV-controlled systems requires our prior written authorization except to the extent applicable law protects conduct that cannot lawfully be prohibited by this AUP. A report of a suspected vulnerability does not itself authorize intrusive testing. Good-faith vulnerability reports may be sent to the address in Section 12. 3. MALICIOUS CODE AND DISRUPTION Users must not introduce malware, ransomware, destructive payloads, credential-harvesting tools, malicious scripts, denial-of-service activity, or other content or conduct intended to disrupt, damage, overload, or impair the Service or another system. Users must not knowingly cause unreasonable interference with the availability, security, or integrity of the Service or another user's access. 4. FRAUD, DECEPTION, AND IMPERSONATION Users must not use Got2Dev Business Manager to facilitate fraud, theft, phishing, identity misuse, false authorization, deceptive billing, fabricated transactions, unlawful financial activity, or impersonation of another person or business. 5. UNLAWFUL OR ABUSIVE CONTENT Users must not knowingly use the Service to create, store, transmit, or facilitate content or conduct that is unlawful, threatening, exploitative, harassing, unlawfully defamatory, or that violates intellectual-property, privacy, publicity, or other legal rights. This restriction does not eliminate legal rights or protections that cannot lawfully be waived. 6. CUSTOMER AND PERSONAL DATA Users must not upload or process information they are not authorized to collect, use, disclose, or store. This includes photos or images containing customer, employee, property, location, health, financial, identification, or other sensitive information. Users must not enable customer visibility or include an image in a customer-facing document unless they are authorized to share that media with the intended recipient. Businesses are responsible for notices, permissions, and legal bases applicable to the Customer Data they place in Got2Dev Business Manager. 7. COMMUNICATIONS AND SPAM Users must not use the Service for unlawful, deceptive, abusive, or unauthorized bulk communications. Where communications functionality is enabled, users are responsible for applicable consent, sender-identification, message-content, opt-out, and other legal requirements, including honoring opt-out requests when required. Sending an operational or transactional message does not automatically exempt unrelated promotional content from applicable marketing-message requirements. 8. AUTOMATION AND RESOURCE ABUSE Automated activity must not materially degrade Service performance, circumvent product limitations, create unreasonable load, scrape protected information, or interfere with other customers. Where APIs or integrations are made available, they must be used only within authorized access scopes, documented limits, and applicable provider permissions. 9. REVERSE ENGINEERING AND CIRCUMVENTION Users must not reverse engineer, decompile, disassemble, or attempt to derive protected source code or security-sensitive implementation details except to the extent such restriction is prohibited by law. Users must not circumvent subscription, licensing, or feature controls. 10. HIGH-RISK OR REGULATED USE A business is responsible for determining whether its intended use is subject to specialized regulatory, licensing, recordkeeping, professional, safety, or industry requirements. Use of Got2Dev Business Manager does not by itself establish compliance with those requirements. The Service is not represented by this AUP as certified for any particular regulated or safety-critical use. 11. ENFORCEMENT Subject to the Terms of Service, applicable law, and any separately binding written agreement, GOT2DEV may investigate suspected violations and may restrict features, suspend access, preserve relevant security evidence, or terminate access when reasonably necessary to protect the Service, users, or third parties or to comply with law. Enforcement should be proportionate to the circumstances where practicable. Where practical and appropriate, GOT2DEV may provide notice and an opportunity to address a violation, but immediate protective action may be necessary for serious security, fraud, or legal risks. Collection, access, preservation, disclosure, and retention of relevant evidence remain subject to the Privacy Policy and applicable law. 12. REPORTING Suspected abuse or security concerns involving Got2Dev Business Manager may be reported to support@got2dev.com; suspected security vulnerabilities may also be reported to security@got2dev.com. Reports should describe the issue and its impact without including passwords, full payment credentials, unnecessary personal information, or other sensitive secrets. Reporting a concern does not authorize access to another user's data or testing beyond the reporter's permissions. 13. POLICY CHANGES Published revisions identify their version and effective date. Material changes will be communicated where required by applicable law or a binding agreement. A revised version may require renewed acceptance when configured or required by law. A published version is preserved as its own legal record and is not silently rewritten by subsequent configuration changes.