Terms of Service

Terms of Service

These terms explain the rules for using Licenzy, including account access, workspace and API responsibilities, billing, test and live mode use, and general service limitations.

Last updated: May 2026

Back to home

Written for a real API product

These terms are intended to be practical, understandable, and aligned with Licenzy's current authentication, billing, runtime, and operational model.

Licenzy is built for developer teams working with subscriptions, usage-based billing, entitlements, checkout, access checks, and operational tooling. The terms below are written to be clear without becoming unnecessarily dense.

AccountsAPI keysBillingRuntime API

On this page

Use these anchors if you want to jump directly to a section.

Terms of Service

These Terms of Service describe the rules that apply when you access the site or use the Licenzy service.

They are intended to explain, in practical terms, how account access, workspace control, runtime API usage, billing, cancellations, acceptable use, and service limitations work for Licenzy's current product surface.

1. Introduction and agreement to terms

Licenzy provides software, APIs, documentation, and related tools for subscriptions, usage-based billing, entitlements, checkout workflows, access control, runtime operations, and related monetization infrastructure.

These Terms of Service govern your access to and use of the Licenzy website, documentation, portal, runtime API, billing surfaces, and related services. By accessing or using Licenzy, you agree to these terms.

If you do not agree to these terms, do not use Licenzy.

2. Eligibility and authority

Licenzy is intended for business, professional, and developer use. You may use Licenzy only if you are legally able to enter into a binding agreement and only in compliance with these terms and applicable law.

If you use Licenzy on behalf of a company, organization, or other entity, you represent that you have authority to bind that entity to these terms.

3. Accounts and workspace ownership

You are responsible for maintaining accurate account information and for controlling who has access to your account, workspaces, projects, and connected environments.

The person or organization that creates and administers a workspace is responsible for the configuration, integrations, billing choices, API keys, webhook settings, and runtime usage associated with that workspace.

You are responsible for activity that occurs under your account or workspace, including activity performed by team members, integrations, automated systems, or connected services.

4. Authentication and account security

Licenzy supports email and password authentication, Google OAuth authentication, session-based portal access, email verification, and password reset flows.

You are responsible for maintaining the confidentiality of your account credentials, protecting access to your email account and sign-in methods, and promptly notifying Licenzy if you believe your account, session, or authentication method has been compromised.

You may not share account credentials in a way that bypasses intended account or workspace controls, and you may not attempt to interfere with authentication, recovery, verification, or session management systems.

5. API keys and credentials

Licenzy API keys and other credentials must be kept confidential and used only by authorized systems and personnel.

You must not expose runtime API keys in client-side code, public repositories, browser code, mobile app bundles, or other publicly accessible environments. Runtime keys are intended for secure server-side use.

You are responsible for using the correct key for the correct project and mode, including test mode and live mode. If a key or credential is compromised or suspected to be compromised, you must rotate or revoke it promptly.

6. Using the runtime API

You may use the Licenzy runtime API only in compliance with these terms, applicable law, and the product documentation.

You are responsible for the correctness of the requests you send to Licenzy, including the customer or subject identifiers you choose to send, the product codes you reference, the environments or modes you target, and the way your systems handle checkout, access, entitlement, and usage-related responses.

Where the Licenzy API or documentation requires idempotency or similar request-safety behavior, you are responsible for implementing it correctly. You may not use runtime endpoints in a way that is abusive, misleading, fraudulent, or operationally unsafe.

7. Customer data and configuration responsibility

You are responsible for the data, identifiers, configuration, and operational choices you submit to Licenzy, including customer identifiers such as subject_ref, project configuration, product mappings, billing settings, webhook destinations, and support or operational inputs.

You represent that you have the rights, permissions, and legal basis necessary to submit and process that information through Licenzy and that your use of the service does not violate applicable law or the rights of others.

8. Stripe and billing integration responsibilities

Licenzy depends on customer-configured billing infrastructure, including Stripe credentials, products, prices, and related subscription or checkout configuration.

You are responsible for providing valid Stripe credentials, maintaining correct product and price mapping, using the correct test or live configuration, and setting up the required tenant webhook flows correctly for the mode you operate.

Licenzy is not responsible for failures caused by incorrect Stripe configuration, mismatched environment setup, missing or invalid Stripe inbound webhook or outbound webhook configuration, or customer-side billing logic outside the intended Licenzy flow.

9. Webhook responsibilities

If you use outbound Licenzy webhooks, you are responsible for maintaining endpoint availability, securing receiving systems, and designing your systems to handle retries, duplicate deliveries, and related operational behavior safely.

You are also responsible for processing outbound webhook data lawfully and appropriately within your own systems and for maintaining any operational controls needed to protect that data after it leaves Licenzy.

10. Plans, billing and subscriptions

Licenzy offers free and paid plans. Paid plans generally renew automatically according to the billing cycle selected at checkout unless canceled before renewal.

Stripe handles payment collection for Licenzy billing flows. Failed payment, invalid billing state, or unresolved account issues may restrict or suspend paid or live functionality until the issue is resolved.

If you cancel a paid plan, cancellation generally prevents future renewal and may take effect at the end of the current billing period unless a specific billing flow states otherwise.

Payments are generally non-refundable except where required by applicable law or where a specific offer, checkout flow, or written agreement expressly states otherwise.

11. Free plan, test mode and evaluation use

Licenzy's free or test-oriented plan is intended for evaluation, testing, development, and non-production validation of integrations and workflows.

Test mode is intended for setup and evaluation. It is not a commitment that the free plan or test mode is appropriate for live commercial use, production deployment, or uninterrupted operational availability.

12. Live mode and production use

Live mode and production use generally require an eligible paid plan and correct production-ready configuration.

You are responsible for ensuring that your live setup is correctly configured, including valid credentials, correct mode selection, correct product mapping, and correct webhook setup before relying on Licenzy for production billing or access-control workflows.

13. Acceptable use and abuse prevention

You may not use Licenzy to:

  • Violate law, regulation, or the rights of others.
  • Interfere with the service, its infrastructure, or the experience of other users.
  • Attempt unauthorized access to accounts, workspaces, credentials, or systems.
  • Misuse API keys, credentials, authentication flows, runtime endpoints, or webhook systems.
  • Submit fraudulent, misleading, unauthorized, or unlawful customer identifiers or operational data.
  • Abuse rate limits, security controls, anti-abuse protections, or operational safeguards.
  • Use Licenzy in a way that creates security, compliance, fraud, or operational risk to Licenzy or others.
  • Reverse engineer or extract underlying code or systems where that is disallowed by law or contract.

14. Service availability, changes and beta nature

Licenzy is an evolving software service. Features, limits, product behavior, and service interfaces may change over time.

Unless separately agreed in writing, Licenzy is provided without any service level agreement. We do not guarantee uninterrupted availability, error-free operation, or that every feature will remain unchanged indefinitely.

Availability may be affected by Licenzy infrastructure and by third-party services such as Stripe, Render, Resend, Google, and related providers that support authentication, billing, hosting, email delivery, and other operational functions.

15. Suspension and termination

We may suspend, limit, or terminate access to Licenzy if we reasonably believe there is abuse, fraud, misuse of the API or webhook systems, payment failure, security risk, legal or compliance risk, or other operational risk to Licenzy or others.

We may also suspend or terminate access if you violate these terms or use the service in a way that is materially harmful, unauthorized, or unlawful.

16. Intellectual property and license

Licenzy, including the software, website, APIs, branding, documentation, and related materials, remains the property of Licenzy or its licensors.

These terms give you a limited right to use the service, not ownership of the product or its underlying intellectual property.

17. Confidentiality and sensitive information limits

You should not provide Licenzy with sensitive information beyond what is reasonably necessary to use the service as intended. You are responsible for handling your own secrets, credentials, customer data, and receiving systems appropriately.

Licenzy may process credentials, identifiers, and operational data as part of providing the service, but you remain responsible for minimizing unnecessary exposure of sensitive information in your own configuration, payloads, and downstream systems.

18. Disclaimers

Licenzy is provided on an "as is" and "as available" basis. To the extent permitted by applicable law, we disclaim warranties not expressly stated, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

19. Limitation of liability

To the extent permitted by applicable law, Licenzy will not be liable for indirect, incidental, special, consequential, or similar damages arising from or related to your use of the service.

Our overall liability under these terms will be limited to a reasonable amount connected to the fees paid for the service during the period directly related to the claim.

20. Indemnity

To the extent permitted by applicable law, you agree to defend, indemnify, and hold harmless Licenzy from claims, liabilities, damages, losses, and costs arising from or related to your misuse of the service, your data or configuration, your violation of these terms, or your violation of applicable law or the rights of others.

21. Governing law and dispute resolution

These terms are governed by the laws of Italy, without regard to conflict-of-law principles.

Unless applicable law requires otherwise, the competent courts in Italy will have exclusive jurisdiction over disputes arising out of or related to these terms or your use of Licenzy.

22. Changes to terms

We may update these Terms of Service from time to time to reflect changes in the product, operations, or legal requirements.

The latest version will always be posted on this page together with the updated revision date.