Terms of Service
1. Introduction
Welcome to Authlance. By accessing, installing, or using the software (including self-hosted/on-premise deployments), you agree to these Terms of Service on behalf of yourself and the organization you represent.
2. License and Permitted Use
Authlance grants you a non-exclusive, non-transferable right to install and run the software in your own environment for your internal business purposes and to provide services to your end users. You may not resell, sublicense, or offer the software as a hosted service to third parties, and you must not reverse engineer, circumvent security controls, or use the software in violation of applicable law.
3. Deployment Responsibilities (On-Prem)
You are solely responsible for deploying, configuring, securing, monitoring, backing up, and operating the software in your own infrastructure. Authlance does not operate or access your environment and is not responsible for downtime, data loss, or security incidents in your deployment.
4. Updates and Patches
You are responsible for applying updates, patches, and configuration changes. Failure to stay current may expose you to security or functional issues. Authlance has no obligation to deliver updates on a schedule.
5. Not a Payment Processor
Authlance integrates with third-party payment processors such as Stripe. Authlance is not a payment processor and does not handle, store, transmit, or control funds.
6. Stripe and Financial Liability Disclaimer
All financial transactions, payouts, refunds, chargebacks, disputes, and compliance obligations are handled solely through your connected Stripe account or other third-party processors you choose. Authlance is not liable for any processor-related issues, including failed payments, delayed payouts, chargebacks, fraud, API outages, or webhook failures. Authlance does not act as a Merchant of Record and does not participate in the financial chain of your business operations.
7. Third-Party Services
Authlance may rely on third-party providers (e.g., Stripe for billing integrations). Authlance is not responsible for the performance, availability, security, or downtime of these services.
8. Support and SLA
Authlance is provided as-is with no support or SLA. Requests or bug reports may be filed via GitHub issues, but responses or resolutions are not guaranteed and may be declined or closed at Authlance’s discretion.
9. Warranties and Disclaimers
The software is provided “as is” and “as available,” without warranties of any kind, whether express, implied, or statutory, including merchantability, fitness for a particular purpose, title, non-infringement, or uninterrupted/ error-free operation.
10. Limitation of Liability
To the maximum extent permitted by law, Authlance will not be liable for indirect, incidental, special, consequential, or punitive damages, loss of profits, revenue, data, or business interruption. Any direct liability is capped at the greater of (a) amounts you paid to Authlance for the software in the 12 months preceding the claim.
11. Compliance and Acceptable Use
You must comply with all applicable laws, including data protection, consumer protection, export controls, and anti-abuse requirements. You are responsible for how you and your end users use the software.
12. Governing Law and Disputes
These Terms shall be governed by and construed in accordance with the laws of México, without regard to conflict of law principles. Any disputes arising out of or relating to these Terms or the use of Authlance shall be exclusively resolved in the courts located in Jalisco, unless both parties mutually agree to arbitration.
13. Changes to Terms
Authlance may update these Terms periodically. Continued use of the software after changes become effective constitutes acceptance of the revised Terms. A change log is maintained via the tos_version field.
14. Acceptance Tracking
Authlance tracks acceptance via tos_version and accepted_at. You are responsible for ensuring your users have authority to accept on behalf of your organization.
Privacy Policy
1. Deployment Data Scope (On-Prem)
Your production data remains in your environment. Authlance does not collect or process your production data unless you choose to share logs, diagnostics, or example data for troubleshooting. Telemetry is off by default unless you enable it.
2. Data Collected by Authlance Cloud Components (if used)
Authlance collects only the minimum information required to create an account and complete a purchase:
- Account registration data you provide (e.g., name, email, password) when creating an account to buy Authlance or related services
- Billing-related identifiers needed to process payments through Stripe (e.g., Stripe customer ID)
- Optional issue reports, support requests, or logs that you voluntarily submit through GitHub Optional telemetry remains off unless you explicitly enable it.
3. Third-Party Subprocessors (if features are enabled)
- Stripe (billing integrations)
- Any other third-party service you connect within your deployment
4. Cookies and Tracking
Authlance uses session cookies for authentication when applicable. No cross-site tracking is performed by Authlance.
5. Data Retention
Data provided to Authlance (e.g., issue reports or logs) is retained only as long as necessary for operational or legal purposes, after which it may be deleted or anonymized.