Terms of Service

1. Acceptance of Terms

By accessing and using the LaTeXLite API service, you accept and agree to be bound by the terms and provision of this agreement.

2. Service Description

LaTeXLite provides a REST API service for converting LaTeX templates into PDF documents. The service is provided "as is" without warranty of any kind.

3. Service tiers and API limits

LaTeXLite offers a Demo tier and a Pro tier. The numeric limits below match our product defaults (from the same configuration we use for the public site and API enforcement); your account may store different per-user caps that we apply in practice.

3.1 Demo tier

• No charge.
• Demo access period: 30 days from when demo access is first assigned to your account.
• Up to 10 API requests per minute.
• Up to 50 API requests per month.

3.2 Pro tier

• Recurring subscription billing (reference list price $7/month); the price and terms in effect at checkout and in Stripe govern your subscription.
• Up to 60 API requests per minute.
• Up to 10,000 API requests per month.
• Email support.
• You may cancel your subscription according to the billing options we provide (e.g. via Stripe customer portal). Cancellation will take effect at the end of the current billing period.

3.3 Limits applying to all tiers

• Maximum template size: 1MB
• Maximum compilation time: 30 seconds per request (configurable in deployment).

3.4 Payments and refunds

Subscription and other paid fees are non-refundable. We do not offer refunds or account credits for partial billing periods, unused usage, or change of mind, except where applicable law requires otherwise.

4. Prohibited Uses

You may not use the service to:

• Generate illegal, harmful, or malicious content
• Attempt to overwhelm or abuse the service
• Reverse engineer or attempt to extract the underlying LaTeX infrastructure
• Violate any applicable laws or regulations

5. Data Privacy

Generated PDFs are not kept as ordinary persistent files on our application servers after each request is fulfilled. Templates and input you send are used to fulfil each request; we do not keep them as ordinary persistent files or shared caches on our application servers in a way that could expose one customer’s content to another.

We record API activity in our database, which may include request and response bodies (for example templates, JSON input, and related metadata), for operation, security, debugging, rate limits, and usage enforcement. Logs are kept for a limited period and are subject to access controls so that other accounts cannot retrieve your records; our operators may access log data only as needed to run and secure the service. Retention may change over time; material updates will be reflected in our Privacy Policy, which governs these practices in detail.

6. Service Availability

We strive for high availability but do not guarantee uninterrupted service. Maintenance windows will be communicated when possible.

7. Changes to Terms

We reserve the right to modify these terms at any time. Continued use of the service constitutes acceptance of modified terms.