Legal & Compliance

1. Use of the Service

The Service provides license-key issuance, customer-management, and Stripe-Connect-backed checkout for paid plugins, extensions, and similar software products. You agree to operate your workspace in a lawful manner and to take responsibility for the products you sell through it.

2. Your customers, your relationship

You remain the seller of record for your plugins. The Service helps you issue, validate, and manage licenses, but the sales contract, the Stripe account, and the support relationship sit between you and your customer.

• You own the customer relationship, including refund policy and support obligations.
• We do not contact your customers directly, except to deliver licensing-related transactional emails on your behalf.
• You must publish your own terms, privacy policy, and refund policy to your customers.

3. Stripe Connect & payment processing

Customer payments flow through your own Stripe account, connected via Stripe Connect Standard. The Service never holds funds on your behalf. By connecting your Stripe account you agree to Stripe's terms in addition to these terms; Stripe handles tax remittance, payouts, refunds, and chargebacks per their service.

You are responsible for making sure your Stripe account remains in good standing and complies with the rules of the jurisdictions where your customers reside.

3.1 What we use your Stripe access for

The Connect Standard OAuth scope grants the Service a broad set of API permissions in the abstract. In practice the Service only ever uses these capabilities on your account:

• Create Stripe Checkout Sessions when a buyer clicks “Buy” on a storefront page we render for you.
• Read your product and price catalog so the storefront can list what you sell.
• Listen to payment and subscription events from your account (such as checkout.session.completed and customer.subscription.*) via our Stripe Connect integration, so we can issue licenses and keep subscription status in sync.
• Open a Stripe Customer Portal session when one of your buyers asks to manage their subscription or update their payment method.

3.2 What we never do

• Issue refunds without an explicit click in your admin UI.
• Edit, archive, or delete the products and prices you already have on your account.
• Charge cards directly outside the Stripe Checkout flow.
• Read or modify your payout schedule, bank account, or business details.
• Move money off your account. Stripe Connect Standard, by design, gives no platform any ability to debit a connected account or change its payout destination.

3.3 Revoking access

You can revoke the Service's access to your Stripe account at any time from your Stripe Dashboard under Settings → Connected applications. After revocation the storefront for that workspace will return an error on the next checkout attempt; existing licenses keep working until you cancel them in our admin UI.

3.4 Mercado Pago (Latin America)

In countries where Stripe is unavailable, you may instead connect your own Mercado Pago account. Mercado Pago is a “bring-your-own-credentials” integration: you create your own Mercado Pago application and provide the Service with your access token and webhook signing secret, which we store encrypted and use only to create checkouts, issue refunds you trigger, and reconcile payment and subscription webhooks for your account. As with Stripe, you are the seller of record, funds settle to your own Mercado Pago balance, the Service never holds funds, and you remain responsible for compliance with the laws and tax rules of your local jurisdiction. You can disconnect Mercado Pago at any time from the admin UI. Your Licensr platform subscription itself is always billed in USD via Stripe, independent of the payment provider you use for your own storefront.

3.5 PayPal (worldwide)

You may instead connect your own PayPal account for buyer trust and the long tail of markets where Stripe cannot onboard merchants. PayPal is also a “bring-your-own-credentials” integration: you create your own PayPal REST application and provide the Service with your client ID, client secret, and webhook ID, which we store encrypted and use only to create orders and subscriptions, issue refunds you trigger, and verify and reconcile webhooks for your account. As with Stripe and Mercado Pago, you are the seller of record, funds settle to your own PayPal balance, the Service never holds funds, and you remain responsible for compliance with the laws and tax rules of your local jurisdiction. You can disconnect PayPal at any time from the admin UI. Your Licensr platform subscription itself is always billed in USD via Stripe, independent of the payment provider you use for your own storefront.

3.6 Razorpay (India)

In India, where Stripe has no general merchant onboarding, you may instead connect your own Razorpay account. Razorpay is also a “bring-your-own-credentials” integration: you create your own Razorpay API keys and provide the Service with your Key ID, Key secret, and webhook signing secret, which we store encrypted and use only to create payment links and subscriptions, issue refunds you trigger, and verify and reconcile webhooks for your account. As with Stripe, Mercado Pago, and PayPal, you are the seller of record, funds settle to your own Razorpay balance in INR, the Service never holds funds, and you remain responsible for compliance with the laws and tax rules of your local jurisdiction. You can disconnect Razorpay at any time from the admin UI. Your Licensr platform subscription itself is always billed in USD via Stripe, independent of the payment provider you use for your own storefront.

4. Platform fees & payments

• The Service operates on a per-workspace subscription billed by us through our own Stripe account, with a free tier available without a payment method.
• Paid tiers (Indie, Studio, Agency) cap how many plugins you can ship and how many active licenses you can hold; current tiers, prices, and limits are listed on the public pricing page.
• We may update plan limits, prices, or feature availability with reasonable notice. Existing subscriptions retain their current price until the end of the billing period during which we notify you.

Subscription charges are non-refundable except where required by law or in case of a verified technical issue on our side that prevented use of the Service.

5. Acceptable use

Licensr is built for legitimate software products. You agree not to use the Service to distribute, license, or monetise any software or content that is harmful, deceptive, or illegal.

5.1 Prohibited software categories

The following are strictly forbidden. Using the Service to issue licenses for them is grounds for immediate termination:

• Malware, ransomware, spyware, adware, or trojans: any software whose primary or secondary purpose is to damage, hijack, surveil, or extort users or their systems without explicit informed consent.
• Hacking, cracking, or exploitation tools: software designed to gain unauthorised access to systems, networks, or data; this includes keyloggers, credential harvesters, exploit kits, remote-access trojans (RATs), and similar offensive security tools offered outside of clearly-disclosed, lawful penetration-testing contexts.
• Stalkerware or covert surveillance tools: software that tracks, monitors, or records a person's activity, location, communications, or device without that person's knowledge and explicit consent.
• DDoS or stress-testing tools aimed at third parties: any tool intended to disrupt, degrade, or disable systems, services, or networks that the user does not own or have explicit written authorisation to test.
• Cheats, aimbots, or game-exploit software: tools that manipulate, bypass, or exploit game clients, anti-cheat systems, or other users in multiplayer environments in ways that violate those platforms' terms of service.
• Software that infringes third-party intellectual property rights, including circumvention tools that bypass DRM or license-enforcement mechanisms of other products.
• Products that violate the rules of the platform they ship into (e.g. browser-extension store policies, DAW marketplace policies).
• Any activity that violates Stripe's restricted-business list or the laws of the jurisdictions involved.

5.2 Enforcement

We reserve the right to investigate, suspend, or permanently terminate any workspace we reasonably believe is in violation of these rules. We may also report activity to the relevant authorities where required by law. Suspended workspaces remain billable through the current period unless terminated by us for cause. If you believe your workspace was suspended in error, contact support@licensr.app.

6. Privacy & data protection

We collect only the data needed to operate the Service: workspace settings, plugin metadata, license records, customer email addresses, and webhook event payloads from Stripe.

• We do not sell or rent customer or workspace data.
• Customer data we hold on your behalf may be exported or deleted upon written request from you.
• We rely on Google Cloud (hosting), Firebase (auth), Stripe (payments), and Postmark (transactional email) as sub-processors. Their respective data-protection terms apply.
• Where you operate as a controller of personal data under GDPR (or equivalent), we act as a processor on your behalf for the data we hold about your customers.

7. Service availability

The Service is provided "as is" and "as available". We aim for high availability but do not commit to uptime targets outside of explicit custom-plan agreements. Maintenance windows, third-party outages (Stripe, Firebase, Postmark, Google Cloud), and bugs may temporarily disrupt the Service.

8. Liability

To the maximum extent permitted by law, we are not liable for:

• Lost revenue, lost customers, or lost data resulting from use or unavailability of the Service.
• Refunds, chargebacks, or disputes that arise between you and your customers.
• Damage caused by the plugins or content you ship through the Service.
• Indirect, consequential, or punitive damages.

9. Contact

For account, billing, abuse, or legal inquiries: support@licensr.app