Acceptable Use Policy

Version 2026-09-14-draft-1

BOXOPS — ACCEPTABLE USE POLICY (DRAFT — REQUIRES ATTORNEY REVIEW)

Effective date: to be set on release. Version: 2026-09-14-draft-1.

This Acceptable Use Policy (the "AUP") is part of the BoxOps Terms of
Service and describes conduct that is not permitted on the BoxOps
platform (the "Service"). Words used with capital letters that are not
defined here have the meanings given in the Terms of Service.

You agree that, in connection with your access to or use of the Service,
you and your Authorized Users will not, and will not attempt to, permit any
other person to:

1. REVERSE ENGINEERING, ETC.
   Reverse engineer, decompile, disassemble, translate, or otherwise seek
   to derive source code, algorithms, models, weights, structure,
   organization, trade secrets, or the underlying ideas of any part of the
   Service, except to the minimum extent applicable law expressly permits
   and cannot waive by contract.

2. NO UNAUTHORIZED AUTOMATED EXTRACTION.
   Access, index, collect, extract, scrape, harvest, clone, mirror,
   crawl, spider, or bulk download any part of the Service, its user
   interfaces, its screens, its data, or its documentation by any
   automated or scripted means (including headless browsers, bots, or
   third-party scraping services). We may block or throttle any traffic
   we believe violates this Section.

3. NO COMPETING PRODUCT.
   Use the Service, any data, documentation, or output obtained through
   it, or any of our Confidential Information, to develop, train,
   benchmark, evaluate, market, or sell a product or service that
   competes with the Service in whole or in part, or to assist any third
   party in doing so.

4. NO CREDENTIAL SHARING.
   Share your username, password, API token, kiosk token, webhook
   secret, session cookie, or any other authentication material with any
   other person; use another person's credentials; or permit multiple
   individuals to use a single set of credentials. Each individual who
   uses the Service must have their own account.

5. NO UNAUTHORIZED API ACCESS.
   Access the Service through any interface other than the web, mobile,
   or kiosk applications we publish and the APIs we document at
   boxops.dsio.io, or exceed documented rate limits, or misuse any published
   API key, kiosk token, or webhook secret, or otherwise use undocumented
   endpoints. We may revoke keys and tokens without notice for these
   reasons.

6. NO COPYING OF PROPRIETARY DOCUMENTATION.
   Copy, redistribute, republish, translate, or otherwise reproduce any
   of our documentation, help articles, in-product tooltips, training
   material, templates, screenshots, screen recordings, or user-interface
   designs, in whole or in part, whether inside your organisation for
   users who are not Authorized Users or outside your organisation, except
   for fair-use quotation with attribution.

7. NO MISUSE OF BETA FUNCTIONALITY.
   Access, use, disclose, discuss publicly, screenshot, benchmark, or
   otherwise reveal the existence, functionality, performance, or
   documentation of any beta, preview, dark-launch, or otherwise
   non-generally-available feature (a "Beta Feature") that has not been
   publicly announced by us. Beta Features are our Confidential
   Information; you may use them only to evaluate them for your own use
   and must delete any related Confidential Information on our request
   or on withdrawal of the Beta Feature.

8. NO CIRCUMVENTION OR SECURITY MISUSE.
   Interfere with, disable, defeat, or circumvent any security,
   access-control, metering, rate-limiting, watermarking, audit, or
   integrity mechanism of the Service. Probe or test the vulnerability
   of the Service, or breach any security or authentication measure,
   without our prior written consent. Introduce any virus, worm, ransomware,
   trojan, back door, or other malicious code.

9. NO PROHIBITED CONTENT OR CONDUCT.
   Upload, transmit, store, or otherwise process through the Service any
   content that (a) infringes any third party's intellectual-property or
   privacy rights; (b) is unlawful, defamatory, harassing, hateful,
   sexually explicit involving minors, or promotes violence; (c) is
   spam or unsolicited bulk messaging in violation of anti-spam laws
   (including CAN-SPAM, TCPA, and CASL) or without the required consent;
   (d) violates biometric-privacy laws (including BIPA, CCPA/CPRA, or
   equivalents) in the jurisdictions where your members are located; or
   (e) impersonates any person or entity or misrepresents your affiliation
   with any person or entity.

10. NO OVERBURDENING.
    Take any action that imposes an unreasonable or disproportionately
    large load on our infrastructure, including denial-of-service attacks
    and volumetric abuse of any endpoint.

11. NO FALSE OR MISLEADING USE.
    Use the Service to send falsified sender information, to spoof a
    domain, to forge a signature, or otherwise to deceive a recipient
    about the identity of the sender.

12. ENFORCEMENT.
    We may investigate any suspected violation of this AUP. We may
    suspend or terminate any account, revoke any credential, remove any
    content, or take any other action we consider appropriate,
    including reporting the matter to law enforcement. Nothing in this
    AUP limits the remedies available to us under the Terms of Service
    or applicable law.

13. REPORTING.
    Report a suspected violation of this AUP or any security issue to
    abuse@boxops.dsio.io. Report suspected intellectual-property
    infringement to dmca@boxops.dsio.io.

END OF AUP.

Related: Terms of Service · Privacy Policy