BeatDesign Terms of Use
Terms for using the BeatDesign open-source workspace and its connection to BeatAPI.
Last updated: 2026-08-22
These Terms of Use govern your use of the official BeatDesign website, distribution, and open-source workspace. By using BeatDesign, you agree to these Terms. If you do not agree, do not use the official website or services.
BeatDesign is an open-source, local-first AI canvas maintained by BeatAPI. In these Terms, “BeatDesign” means the workspace software and official BeatDesign surfaces. “BeatAPI” means the separate hosted API service available at beatapi.io.
1. Open-source software
The BeatDesign source code is provided under the Apache License 2.0. Your rights to use, copy, modify, and distribute the source code are governed by that license. If these Terms conflict with the Apache License 2.0 with respect to the source code, the license controls.
The open-source license does not grant permission to use the BeatDesign or BeatAPI names, logos, domains, or other brand identifiers in a way that suggests sponsorship, endorsement, or an official hosted service. See docs/TRADEMARKS.md in the repository.
2. Local-first workspace
The open-source distribution is designed to run locally or in an environment you control. It does not include BeatAPI account creation, payment processing, subscriptions, a local credit ledger, or an API-key issuing service.
You are responsible for your installation, device, database, backups, network exposure, access controls, and deployment security. If you make BeatDesign available to other people, you become the operator of that deployment and are responsible for the notices, permissions, security, data handling, and legal compliance required for your users.
3. BeatAPI services
BeatDesign can connect to BeatAPI for image, video, and other supported generation workflows. BeatAPI accounts, API keys, credits, billing, files, hosted outputs, logs, webhooks, and model access are separate hosted services governed by the BeatAPI Terms of Service and BeatAPI Privacy Policy.
These Terms do not replace the BeatAPI Terms of Service. When you use a BeatAPI API key through BeatDesign, both these Terms and the applicable BeatAPI terms apply to their respective services.
4. Credentials and security
You are responsible for protecting API keys, storage credentials, encryption keys, devices, and any other credentials connected to BeatDesign. Do not expose permanent API keys in client-side code, public repositories, screenshots, shared projects, or untrusted deployments.
You are responsible for activity performed with your credentials. If you believe a credential has been exposed or used without authorization, revoke or rotate it promptly and contact the relevant provider.
5. Inputs, uploads, and outputs
You retain your rights in prompts, images, videos, audio, project data, and other material you provide to BeatDesign (“Inputs”). You must have all rights, permissions, and consents required to use and submit those Inputs.
When you request a generation, BeatDesign may transmit the selected Inputs and generation settings to BeatAPI, configured storage, and the upstream model providers needed to complete your request. You authorize that processing solely as needed to provide the requested workflow.
To the extent permitted by applicable law and relevant provider terms, you may use the outputs generated for you. AI outputs may be inaccurate, incomplete, delayed, unavailable, or similar to outputs generated for other users. You are responsible for reviewing outputs before publishing, distributing, or using them commercially.
6. Acceptable use
You may not use BeatDesign or its official integrations to:
- Violate applicable law, regulation, contractual obligations, or third-party rights.
- Upload or generate unlawful, abusive, exploitative, deceptive, infringing, or harmful content.
- Use a person's face, voice, likeness, identity, or private material without the rights and consent required for that use.
- Create fraudulent impersonation, deceptive deepfakes, non-consensual intimate content, sexual content involving minors, harassment, or content intended to mislead people about a real person's actions or statements.
- Submit malware, stolen credentials, or material that creates an unreasonable security or privacy risk.
- Bypass safety, authentication, billing, usage, storage, or rate-limit controls.
- Probe, attack, overload, disrupt, or gain unauthorized access to BeatDesign, BeatAPI, model providers, or connected infrastructure.
- Use third-party models or services in violation of their applicable terms.
We may restrict access to official BeatDesign services or integrations when we reasonably believe their use creates legal, safety, security, payment, or operational risk. Your rights to independently use the open-source code remain governed by the Apache License 2.0.
7. Third-party models and services
BeatDesign may depend on BeatAPI, upstream AI models, storage services, hosting providers, and other third-party services. We do not control their availability, processing time, output quality, retention practices, or terms. Your use of those services may be subject to additional agreements between you and the relevant provider.
Third-party names and trademarks belong to their respective owners. References to them do not imply affiliation or endorsement.
8. Availability and changes
BeatDesign and its integrations may change over time. Features, model availability, limits, storage behavior, or provider compatibility may be added, modified, suspended, or removed. We do not guarantee uninterrupted operation, permanent compatibility with any provider, exact processing times, or continued availability of any model.
9. Self-hosting and modified versions
If you self-host, fork, or redistribute BeatDesign, you are responsible for your changes and operation. You must preserve notices required by applicable open-source licenses and must not represent a modified or third-party deployment as an official BeatDesign or BeatAPI service without written permission.
Operators who provide BeatDesign to other users must publish their own terms and privacy notice that accurately describe their deployment, data practices, providers, billing, and contact details.
10. Disclaimers
To the maximum extent permitted by law, BeatDesign is provided “as is” and “as available,” without warranties of any kind. We do not warrant that BeatDesign or AI outputs will be accurate, lawful, non-infringing, secure, uninterrupted, error-free, or fit for a particular purpose.
You are responsible for deciding whether BeatDesign, its providers, and generated outputs are suitable for your intended use. Nothing generated through BeatDesign is professional, legal, medical, financial, or other regulated advice.
11. Limitation of liability
To the maximum extent permitted by law, BeatDesign and its maintainers will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages; loss of profits, revenue, data, credits, goodwill, or business opportunity; provider failures; unauthorized credential use; or claims arising from Inputs or outputs.
Some jurisdictions do not allow certain exclusions or limitations, so parts of this section may not apply to you.
12. Ending use
You may stop using BeatDesign at any time. In a local installation, you control deletion of the local application data and files. Ending use of BeatDesign does not automatically close a BeatAPI account, revoke an API key, delete provider data, or resolve an outstanding BeatAPI balance; those actions must be completed with the relevant service.
13. Changes to these Terms
We may update these Terms as BeatDesign evolves. We will update the date above when changes are published. Material changes may also be announced through the project repository or official website. Your continued use after an update means you accept the revised Terms to the extent permitted by law.
14. Contact
For questions about BeatDesign or these Terms, contact support@beatapi.io or open an issue in the official BeatDesign repository. Questions about BeatAPI accounts, billing, or API processing should be directed to BeatAPI support.