Effective: July 20, 2026
How these terms fit togetherThe platform-wide terms apply to every Handlebe service you enable now or later. A service-specific section adds rules for that service and wins only when it clearly says something different.
1. Terms for every Handlebe service
Eligibility and agreement
You must be at least 13 years old and able to agree to these terms. By creating an account, enabling a service, or using Handlebe, you agree to these Terms and the Privacy Policy.
Accounts and security
Give accurate account information, protect passwords, API keys, recovery codes, and sessions, and tell us promptly about unauthorized access. You are responsible for activity performed through credentials you control.
Acceptable use
Do not use any service for unlawful, fraudulent, deceptive, abusive, infringing, or harmful activity. Do not distribute malware, phishing material, sexual content involving minors, or content that violates another person's rights. Do not disrupt the platform, bypass limits or safety controls, probe private systems, or use automation outside the published API and its limits.
Your content
You keep ownership of content you submit. You give Handlebe a worldwide, non-exclusive, royalty-free license to host, process, reproduce, and deliver it only as needed to operate, secure, and support the enabled service. You promise that you have the rights needed for that content.
Plans, usage, and payment
Each service has its own plan, monthly credit, usage price, spending controls, and renewal rules. Credits have no cash value, do not transfer between services, and do not roll over. Cards and receipts may share one billing home. Taxes, refunds required by law, and provider processing rules may also apply.
Suspension and termination
You may stop a service or delete your account through the available account controls. We may restrict content, a service, or an account when needed to enforce these terms, protect people or the platform, comply with law, or address unpaid amounts. Existing data follows the retention and deletion rules described in the Privacy Policy.
2. Additional Short Links terms
Short Links is an authenticated publishing and routing service. Anonymous short-link creation is not available.
- You are responsible for every primary and targeted destination, public path, subdomain, webhook, masked page, and hosted content version you publish.
- Safety checks reduce known risk but do not endorse a sender, message, destination, product, or transaction. You must not describe a passed check as a guarantee.
- Published destinations become immutable. Create a new link when a destination must change.
- Targeting rules, analytics, and webhooks must not be used for unlawful surveillance, discrimination, or evasion of user choice.
- Branded domains, masking, and hosted content remain subject to review and may be removed or disabled when unsafe or noncompliant.
5. New and future services
These platform-wide terms automatically cover services added to the Handlebe catalog. Before using a new service, you will be shown its material plan, usage, content, and data rules. Enabling one service does not silently enable another or move credit, capabilities, or permissions between them.
6. Warranties, liability, and changes
Service availability
To the maximum extent permitted by law, Handlebe is provided “as is” and “as available,” without implied warranties of merchantability, fitness for a particular purpose, or non-infringement. We do not promise uninterrupted or error-free operation.
Limitation of liability
To the maximum extent permitted by law, Handlebe is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, goodwill, use, or data arising from the service.
Changes
We may update these terms as the platform changes. We will post the new effective date and provide reasonable notice of material changes when required. Continued use after the effective date means the updated terms apply.
Questions
Use the Support page for questions about these terms. Safety concerns belong in the separate public report queue.