Terms of Service

1. Operator and Scope

These Terms of Service (the "Terms") are a legally binding agreement between you and BladePDF, operated by Karel Talich, a sole proprietor established in the Czech Republic, Identification Number: 19409516, registered address: Nálepkova 298, 405 05 Děčín, Czech Republic ("BladePDF", "we", "us", or "our").

These Terms apply to the BladePDF website, dashboard, API, PDF generation service, Laravel and Composer integrations, documentation, support channels, and related services, features, and software (collectively, the "Service").

The Service is made available worldwide, including to users in the United States, the European Union, and other jurisdictions. Your use of the Service must comply with all laws that apply to you, your business, your users, your content, and your PDF generation use case.

2. Acceptance of Terms

By accessing or using the Service, creating an account, generating a PDF, using an API key, installing or using a BladePDF integration, or purchasing a subscription, you agree to these Terms.

If you use the Service on behalf of a company, organization, client, employer, or other legal entity, you represent and warrant that you have authority to bind that entity to these Terms. In that case, "you" and "your" refer to both you personally and that entity.

If you do not agree to these Terms, you must not access or use the Service.

3. Key Definitions

• "Account" means your registered BladePDF user account, whether created using email and password, Google sign-in, or another supported authentication method.
• "API Key" means a credential issued by BladePDF that allows programmatic access to the Service.
• "Customer Content" means any HTML, CSS, JavaScript, text, images, fonts, assets, data, URLs, files, templates, metadata, or other material you submit, reference, or transmit to the Service for PDF generation or support.
• "Generation Payload" means the request body, submitted rendering data, and related Customer Content used for a specific PDF generation request.
• "Generated PDF" means the PDF output produced by the Service from a Generation Payload.
• "Concurrency" means the number of PDF renders that may run at the same time for your Account or plan.
• "Queue" means the number of PDF generation requests that may wait for an available Concurrency slot.
• "Payload Limit" means the maximum permitted Generation Payload size as measured by our systems after decompression, decoding, or other normal request processing, excluding the final Generated PDF unless otherwise stated.
• "Fair Use" means the usage rules described in these Terms, including bandwidth, abuse-prevention, and resource-protection limits.
• "Stored Content" means content you choose to save in your Account for reuse, including dashboard-managed Blade templates, uploaded assets such as logos, fonts, images, and stylesheets, and any Generated PDFs you elect to store through the Service.
• "Storage Space" means the storage allowance available to your plan for Stored Content, as described in these Terms or the dashboard.
• "Webhook" means an HTTP callback the Service sends to an endpoint you configure to notify your application about render events such as successful or failed generations.

4. Service Overview

BladePDF is a SaaS platform for generating PDFs from HTML and related web content. It is primarily designed for Laravel developers and includes a Composer package for easier Laravel integration. The Service may also be used directly through an API route or other documented interfaces.

The Service also includes dashboard features for managing document workflows. These may include dashboard-managed Blade templates that you can create, edit, version, and publish; hosted assets such as logos, fonts, images, and stylesheets that you can upload once and reuse across templates; optional storage of Generated PDFs; and Webhooks that notify your application about render events. These features are subject to your plan, Storage Space, Fair Use, security controls, technical limits, and available capacity. Availability of specific features may change over time.

BladePDF is an independent product and is not affiliated with, endorsed by, or operated by Laravel or the Laravel framework maintainers.

You are responsible for your application, Laravel implementation, templates, Blade-rendered HTML, API requests, Customer Content, Generated PDFs, end-user communications, compliance obligations, and business processes.

BladePDF does not provide legal, accounting, tax, compliance, archiving, document-retention, or professional advice. Generated PDFs may be used for invoices, reports, documents, receipts, labels, forms, or other use cases only if your use is lawful and suitable for your own requirements.

5. Eligibility

You must be at least 18 years old, or the age of legal majority in your jurisdiction, and capable of entering into a binding contract. You must not use the Service if you are legally prohibited from doing so, including under applicable export-control, sanctions, consumer-protection, data-protection, or technology laws.

6. Account Registration and Authentication

To use the Service, you must create an Account. You may register using email and password or, where available, a supported third-party sign-in method such as Google sign-in.

• You must provide accurate, current, and complete account, contact, and billing information.
• You must keep your Account information up to date.
• You are responsible for all activity under your Account, including activity by your employees, contractors, users, clients, systems, and API integrations.
• You must promptly notify us if you suspect unauthorized access, API key leakage, credential compromise, or any security incident involving your Account.
• If you use a third-party authentication provider, your use of that provider is also governed by that provider's own terms and privacy rules.

We may refuse registration, close duplicate accounts, require additional verification, or restrict access where necessary to prevent abuse, fraud, security risks, or violations of these Terms.

7. API Keys and Security

API Keys are confidential credentials. You are responsible for protecting them and for all requests made using them.

• You must not publish API Keys in public repositories, client-side code, browser code, mobile apps, screenshots, logs, support tickets, forums, documentation, or other places where unauthorized parties may access them.
• You must use reasonable security practices, including secret management, access control, environment variables, rotation, and least-privilege access where appropriate.
• You must immediately rotate or revoke API Keys that may have been exposed.
• We may revoke, rotate, disable, or restrict API Keys if we reasonably believe they are compromised, abused, or causing harm to the Service.

To the fullest extent permitted by law, BladePDF is not responsible for unauthorized usage, loss, exposure, charges, service disruption, or data disclosure caused by your failure to secure API Keys, credentials, systems, repositories, logs, or deployment environments.

8. Plans, Limits, and Fair Use

BladePDF offers free and paid plans. Plan limits are technical and operational limits designed to keep the Service stable, secure, and fair for all users. The current plan structure as of the effective date is described below.

"Unlimited" means that the plan does not have a fixed monthly generation count, but it does not mean unlimited bandwidth, unlimited compute, unlimited queueing, unlimited request rate, unlimited payload size, unlimited output size, unlimited rendering time, or permission to abuse the Service. Unlimited usage is always subject to these Terms, Fair Use, security controls, technical limits, and available capacity.

The Free plan includes static HTML/CSS rendering only. It does not include JavaScript execution, internet access, or external asset fetching. JavaScript execution and external asset fetching are available only on paid plans and remain subject to these Terms, Fair Use, security controls, technical limits, and available capacity.

The monthly bandwidth Fair Use threshold for paid plans is 1 terabyte (1 TB) per month per Account or customer, unless we agree otherwise in writing. Bandwidth may include inbound request data, remote assets fetched for rendering, Generated PDF output, API responses, retries, and related transfer as measured by our systems.

Each plan includes a Storage Space allowance for Stored Content such as dashboard templates, uploaded assets, and any Generated PDFs you elect to store. The Storage Space for each plan is shown in the table above and in the dashboard. Storage usage is measured by our systems. If you reach your Storage Space limit, we may prevent new uploads, prevent new stored renders, or ask you to remove content or upgrade before storing more. Storage Space is not additional bandwidth, compute, or generation allowance, and it remains subject to these Terms, Fair Use, security controls, technical limits, and available capacity.

You must not create multiple accounts, split workloads, rotate payment methods, share API Keys, or otherwise attempt to avoid plan limits, Fair Use limits, rate limits, or abuse controls.

9. Queueing, Concurrency, and Request Handling

Concurrency slots determine how many renders may run at the same time. If all Concurrency slots are busy, eligible paid-plan requests may wait in your Queue until a slot becomes available. If your Queue is full, if your plan has no Queue, or if a request exceeds applicable limits, the request may be rejected, delayed, throttled, or terminated.

• Queue position, render start time, and render completion time are not guaranteed.
• Requests may time out or fail because of payload complexity, external assets, JavaScript behavior, CSS complexity, memory limits, renderer limits, network issues, or protective controls.
• We may impose undocumented protective limits, including maximum render time, output size, page count, asset count, memory use, CPU use, request rate, URL-fetch limits, and JavaScript restrictions.
• Free-plan requests are handled on a best-effort basis and may be rejected when capacity is unavailable.

10. Billing, Subscriptions, and Paddle

Our order process for paid subscriptions is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all paid orders. Paddle provides customer service for payment, billing, tax, invoice, refund, chargeback, subscription cancellation, and return-related inquiries connected with Paddle transactions. BladePDF provides the software service, API access, technical support, and product support under these Terms.

Paddle's Buyer Terms, Refund Policy, Privacy Notice, and buyer support processes may also apply to your transaction. If there is a conflict between these Terms and Paddle's transaction terms for payment, tax, refund, chargeback, or billing processing, Paddle's transaction terms and mandatory law control for that transaction.

• Paid subscriptions are billed in advance.
• Subscriptions automatically renew unless canceled before the next renewal date.
• Prices, currencies, taxes, discounts, billing intervals, and available payment methods are shown at checkout or in the billing portal.
• You must keep billing information accurate and up to date.
• Failure to pay may result in downgrade, suspension, cancellation, or loss of paid-plan access.
• Taxes are calculated and handled through Paddle where applicable.

If there is a conflict between a price displayed in these Terms and a price displayed during checkout, the checkout price controls for that purchase.

11. Cancellation and Plan Changes

You may cancel your paid subscription through the dashboard, billing portal, Paddle-managed billing flow, or by contacting support where self-service cancellation is unavailable. Cancellation stops future renewals but does not automatically refund charges already paid, except as stated in these Terms or required by mandatory law.

If you cancel, your paid-plan access may continue until the end of the then-current billing period, unless your access is suspended or terminated for breach, abuse, non-payment, fraud, or security risk. After cancellation or expiration, your Account may be downgraded to the Free plan or disabled.

Deleting your Account or stopping API usage does not necessarily cancel an active subscription. You are responsible for canceling through the appropriate billing channel before renewal.

12. Refund Policy

Unless required by applicable law, subscription fees and other charges are non-refundable.

You may request a refund by contacting BladePDF support or Paddle Buyer Support. Refund requests are reviewed on a case-by-case basis and are not guaranteed. We may, at our discretion, support a refund request where there has been a duplicate charge, a billing error, a technical issue that prevents reasonable use of the Service, or another exceptional circumstance.

For purchases processed by Paddle, refunds are processed by Paddle as Merchant of Record and are subject to Paddle's Buyer Terms and Refund Policy. BladePDF does not issue direct refunds outside Paddle for Paddle-processed transactions.

For payment, receipt, tax, subscription cancellation, and refund support for Paddle transactions, you may contact BladePDF support or Paddle Buyer Support via paddle.net. You may also use the "View receipt" or "Manage subscription" link in your Paddle transaction confirmation email where available.

Nothing in this Refund Policy limits any mandatory consumer rights, statutory withdrawal rights, chargeback rights, or other rights you may have under applicable law.

13. Consumers and Mandatory Rights

If you are a consumer, you may have mandatory legal rights under the laws of your country of residence. Nothing in these Terms limits rights that cannot legally be limited or excluded.

The Service is a digital service that may be made available immediately after purchase. Where required, checkout or billing flows may ask you to consent to immediate performance and to acknowledge how this affects any statutory right of withdrawal. Our Refund Policy is intended to supplement, and not unlawfully restrict, any non-waivable consumer rights.

If mandatory law gives you a right to withdraw, cancel, receive information, receive a refund, use an online withdrawal function, or receive a different remedy, those mandatory rights remain unaffected. You may contact us through the dashboard ticket system, the contact page, email, Paddle support, or any mandatory withdrawal mechanism made available for your jurisdiction.

14. Generation Payloads, Stored Content, and Storage

BladePDF processes Generation Payloads only for the purpose of rendering the requested PDF, operating the Service, securing the Service, preventing abuse, and providing support where you voluntarily give us relevant information.

14.1 Ephemeral generation payloads

We do not permanently store the Generation Payloads you submit for a render, and we do not permanently store a Generated PDF unless you explicitly choose to store it. HTML, assets supplied for the request, submitted payload data, and non-stored Generated PDFs are used for the specific render and then deleted from our systems after completion, failure, rejection, timeout, or queue expiration, subject only to transient technical processing required to provide the Service.

Because paid plans include Queue functionality, a Generation Payload may be held temporarily while it waits for an available Concurrency slot. Temporary render files, buffers, and queued job data are used only as needed for the requested render and are deleted after the request is completed, fails, times out, is rejected, or expires.

14.2 Stored Content you choose to save

Some features let you save content in your Account for reuse. This Stored Content may include dashboard-managed Blade templates, uploaded assets such as logos, fonts, images, and stylesheets, and any Generated PDFs you choose to store through the Service. Unlike ephemeral Generation Payloads, Stored Content is retained in your Account until you delete it, it is removed under these Terms, or your Account is closed. Stored Content counts toward your plan's Storage Space.

You are responsible for your Stored Content, including its legality, accuracy, security, and your rights to upload, store, and use it. You must not store content you do not have the necessary rights to, content that violates these Terms, or content prohibited under the Acceptable Use section. We may remove, restrict, or refuse Stored Content that violates these Terms, exceeds your Storage Space, or creates legal, security, or operational risk.

If your plan changes or is downgraded, canceled, suspended, or terminated, Stored Content that exceeds your then-available Storage Space or plan features may become inaccessible, be restricted, or be deleted. We may delete Stored Content after Account closure, after extended inactivity, or as otherwise described in these Terms. You should keep your own copies of anything you cannot afford to lose.

14.3 Not a backup or archive service

Even where storage features are available, BladePDF is not an archive, backup system, document-management system, or general-purpose file-storage service, and Stored Content features are provided as a convenience only. You remain responsible for maintaining your own authoritative copies of templates, assets, and Generated PDFs you need. We do not guarantee that Stored Content will be retained indefinitely, remain recoverable, or be restorable, and we may set reasonable limits on file size, file count, file types, and retention.

For ephemeral renders, after a render completes we generally cannot retrieve, inspect, reproduce, or restore your Generation Payload or a non-stored Generated PDF unless you submit it again or provide it to us through a support channel.

We may retain non-content metadata such as account ID, request ID, timestamps, plan usage, approximate payload size, approximate output size, storage usage, status codes, error categories, rate-limit events, security events, and billing or usage counters. This metadata is used for billing, analytics, debugging, security, abuse prevention, service improvement, and support, and does not intentionally include the substantive contents of your Generation Payload.

14.4 Retention windows and automatic deletion

Operational records and certain Stored Content are retained only for a limited period and are then deleted automatically. As of the effective date of these Terms, the standard retention windows are:

• Render history records (status, timings, request id, your reference and metadata) — 13 months (400 days);
• Per-render logs — 30 days;
• Webhook delivery logs — 90 days;
• Dashboard notifications — 90 days;
• Stored Generated PDFs — until you delete them, until an optional workspace retention window you configure removes them, or until an optional storage-limit cleanup you enable removes the oldest files; in every case a stored Generated PDF is deleted automatically no later than when its associated render history record expires (13 months after the render).

Dashboard-managed templates and uploaded assets are not subject to these windows and remain in your Account as described in Section 14.2. Automatically deleted records and files cannot be recovered. Aggregated, non-content usage counters (for example monthly render counts used for billing and plan enforcement) may be retained beyond these windows.

We may adjust these retention windows for operational, security, or legal reasons. The current values are published in the documentation; where a change materially shortens a window that affects you, we will provide reasonable advance notice as described in these Terms. If you need render outcomes or documents beyond these windows, you must export or record them in your own systems — see also Section 14.3 (Not a backup or archive service).

15. Privacy and Data Protection

Your use of the Service is also governed by our Privacy Policy. The Privacy Policy explains how we process account information, billing-related information, support communications, authentication data, usage metadata, cookies, and other personal data.

Our main application and rendering servers are located in the European Union. However, some related services, such as payments through Paddle, authentication providers, email delivery, analytics, support tools, security providers, or infrastructure subprocessors, may process data in other locations in accordance with their own terms, our Privacy Policy, and applicable data-transfer rules.

If your Generation Payload contains personal data, you are responsible for ensuring that you have a lawful basis, required notices, permissions, and rights to submit that data to BladePDF for rendering. You are also responsible for honoring requests and obligations owed to your own end users, customers, employees, contractors, and data subjects.

Unless we have agreed otherwise in writing, you must not submit highly sensitive, regulated, or special-category data to the Service, including health information, payment card data, full financial account credentials, government identification documents, children's data, biometric data, criminal offense data, trade secrets that require special handling, or data subject to sector-specific security obligations that BladePDF has not expressly accepted in writing.

Where data-protection law requires a data processing agreement, you must request and enter into an appropriate data processing agreement before submitting personal data that requires one. If a separate data processing agreement applies, it controls over these Terms for the processing of personal data.

16. Customer Content and Generated PDFs

You retain ownership of your Customer Content and Generated PDFs. You grant BladePDF a limited, worldwide, non-exclusive, royalty-free license to process Customer Content solely as necessary to provide, secure, troubleshoot, and improve the Service; generate PDFs at your request; prevent abuse; comply with law; and enforce these Terms.

You represent and warrant that you have all rights, permissions, licenses, and legal bases necessary to submit Customer Content to the Service and to create, use, store, send, publish, or distribute Generated PDFs.

You are solely responsible for the accuracy, legality, suitability, accessibility, formatting, retention, delivery, and use of Generated PDFs. BladePDF does not review, validate, approve, certify, or guarantee the legal effect, tax treatment, regulatory compliance, accounting validity, evidentiary value, or suitability of any Generated PDF.

17. Acceptable Use

You must use the Service responsibly, lawfully, and only for legitimate PDF generation. You must not misuse the Service, attack the Service, degrade the Service, interfere with other users, or use the Service in a way that creates legal, security, operational, or reputational risk for BladePDF.

You agree not to:

• use the Service for illegal, fraudulent, deceptive, harmful, abusive, infringing, or unauthorized purposes;
• generate meaningless, repetitive, artificial, or intentionally wasteful PDF requests designed to consume bandwidth, compute, queue capacity, storage, network resources, or rendering capacity;
• attempt to overload, benchmark-abuse, stress-test, degrade, disable, disrupt, damage, or break PDF generation or any part of the Service;
• attempt to bypass plan limits, Fair Use rules, rate limits, Payload Limits, queue limits, Concurrency limits, security controls, billing controls, or access controls;
• create multiple accounts or use multiple identities to evade limits, suspensions, refund restrictions, abuse controls, or billing obligations;
• submit malware, viruses, worms, trojans, ransomware, spyware, exploit code, malicious documents, credential harvesters, or harmful payloads;
• submit dangerous JavaScript or browser behavior, including infinite loops, excessive memory or CPU use, cryptocurrency mining, exploit attempts, sandbox escapes, renderer exploits, data exfiltration, unauthorized network calls, or attempts to access local files or internal networks;
• use the Service for SSRF, port scanning, internal network probing, metadata-service probing, localhost access, private IP access, file-system access, or unauthorized URL fetching;
• use external resources, URLs, fonts, scripts, images, stylesheets, or assets in a way that violates third-party rights, terms, robots rules, security controls, authentication boundaries, or applicable law;
• reverse engineer, decompile, disassemble, scrape, crawl, copy, frame, or reproduce the Service except as expressly permitted by law;
• test, fuzz, scan, probe, exploit, or search for vulnerabilities in the Service, renderer, queue, API, infrastructure, or sandbox without our prior written permission;
• remove, obscure, or alter proprietary notices, trademarks, service marks, or security notices;
• use the Service to generate phishing materials, spam, malware instructions, fraudulent invoices, fake official documents, impersonation materials, or content that violates third-party rights;
• use the Service in a way that violates privacy, intellectual-property, consumer-protection, anti-spam, export-control, sanctions, or data-protection laws;
• resell, sublicense, white-label, or provide the Service to third parties as a competing PDF generation service without our written permission.

We may block, throttle, reject, inspect metadata for, or suspend requests that appear to violate these Terms, threaten the Service, or create security or operational risk.

18. Security Testing and Vulnerability Reports

You must not perform vulnerability testing, penetration testing, scanning, fuzzing, stress testing, exploit attempts, sandbox escape attempts, renderer exploit testing, queue abuse, or PDF generation abuse without our prior written permission.

If you accidentally discover a potential vulnerability, you must stop testing, avoid accessing or modifying data, avoid causing service impact, avoid public disclosure, and report the issue to support@bladepdf.com with enough information for us to investigate. We do not authorize any testing that affects availability, confidentiality, integrity, or other users.

19. API, Laravel, and Composer Package

BladePDF may provide a Laravel integration, Composer package, SDK, examples, documentation, or API helpers to make integration easier. You are responsible for installing, configuring, updating, securing, and using integrations correctly.

References to Laravel in the Service, package, documentation, or examples describe compatibility only and do not imply sponsorship, partnership, endorsement, or other affiliation with Laravel.

• You must use integrations only with supported versions and in accordance with documentation.
• You are responsible for your Laravel application, server configuration, queue workers, dependencies, framework version, deployment environment, and secrets management.
• The Composer package may depend on third-party package managers, open-source dependencies, or runtime environments that BladePDF does not control.
• Documentation, examples, and sample code are provided for convenience and may not cover every edge case, security requirement, or production scenario.

We may update, change, deprecate, or remove API endpoints, SDK behavior, package features, examples, or documentation. Where reasonably possible, we will try to avoid unnecessary breaking changes or provide migration guidance, but we do not guarantee backward compatibility indefinitely.

19.1 Webhooks and callbacks

The Service may send Webhooks to endpoints you configure so your application can react to render events. You are responsible for the endpoints you register, for keeping them secure and available, for verifying webhook signatures, and for processing deliveries safely and idempotently.

• Webhook delivery is provided on a best-effort basis and is not guaranteed. Deliveries may be delayed, retried, duplicated, reordered, or fail, including because your endpoint is unavailable, slow, or rejects the request.
• You must not make the success of a render depend on your webhook endpoint being reachable; webhook delivery happens after a render event is recorded.
• Webhook signing secrets are confidential credentials. You must keep them private, verify signatures before trusting a payload, and rotate secrets that may be exposed. The API Key security terms apply to webhook secrets as well.
• You are responsible for the security, lawfulness, and behavior of any system that receives Webhooks, and for any data your endpoint stores or forwards.
• We may change, throttle, retry, deduplicate, disable, or discontinue webhook events, payload formats, retry schedules, or delivery behavior, and we may pause or disable endpoints that repeatedly fail.

20. Third-Party Services and External Resources

The Service may depend on third-party services such as hosting providers, payment processors, authentication providers, email providers, analytics providers, error monitoring providers, security providers, DNS providers, package registries, and support tools. These third-party services are not controlled by BladePDF.

Your Generation Payload may reference external resources such as images, stylesheets, fonts, scripts, or URLs. You are responsible for ensuring that those resources are lawful, accessible, secure, and permitted for rendering. We may restrict, block, cache transiently, or reject external resources for security, abuse prevention, availability, or performance reasons.

21. Rendering Results and Output Quality

PDF rendering depends on your HTML, CSS, fonts, images, scripts, assets, page settings, browser or renderer behavior, external resources, and technical constraints. We do not guarantee that every page, stylesheet, font, image, script, layout, animation, chart, or browser feature will render exactly as expected.

You are responsible for testing your templates and output before using Generated PDFs in production. We do not guarantee pixel-perfect rendering, identical output across time, identical output across render engines, legal validity, accessibility compliance, invoice compliance, archival compliance, or suitability for a specific business, legal, tax, or regulatory purpose.

22. BladePDF Intellectual Property

BladePDF, the Service, website, dashboard, API, software, infrastructure, documentation, design, trademarks, service marks, logos, trade names, and related technology are owned by BladePDF or its licensors and are protected by intellectual-property and other laws.

Subject to these Terms and your plan, we grant you a limited, revocable, non-exclusive, non-transferable, non-sublicensable right to access and use the Service for your internal business or personal purposes. No rights are granted except as expressly stated in these Terms.

If you send us feedback, ideas, suggestions, bug reports, or feature requests, you grant us a perpetual, irrevocable, worldwide, royalty-free license to use them without restriction or compensation to you.

23. Support

Support is available through the ticket system in the BladePDF dashboard and by email at support@bladepdf.com. We aim to provide practical support, but support availability, response time, and resolution time are not guaranteed unless we agree to a specific support commitment in writing.

Because BladePDF does not permanently store Generation Payloads or Generated PDFs, we may need you to provide a minimal reproducible example, request metadata, screenshots, error messages, or a sanitized sample payload to investigate rendering issues.

24. Availability, Downtime, and Service Remedies

We aim to keep the Service available and reliable, but the Service is provided on a best-effort basis and outages, delays, degraded performance, bugs, maintenance, failures, queue delays, and interruptions may occur. We do not provide an uptime guarantee or service-level agreement unless we expressly agree to one in writing.

If you are on a paid plan and experience unplanned downtime that materially affects your production use of the Service, you may submit a remedy request within thirty (30) days after the incident. Your request must include enough information for us to verify the incident and its impact, such as timestamps, request IDs, error messages, affected endpoint, and production impact.

If we verify that the downtime was caused by BladePDF and was not excluded under these Terms, we may, at our discretion, offer one of the following remedies for the affected billing period:

• a prorated refund for the affected period; or
• a free extension or service credit on your current plan.

Downtime remedies do not apply to Free-plan usage, scheduled maintenance, beta features, unsupported integrations, customer-side errors, invalid payloads, third-party outages, Paddle outages, authentication provider outages, network providers, DNS failures, force majeure events, misuse, abuse, excessive load, security incidents caused by you, API key leakage, plan-limit enforcement, Fair Use enforcement, or suspensions under these Terms.

This section states your sole and exclusive remedy for downtime, interruption, unavailability, queue delay, degraded performance, or service failure, except where mandatory law provides otherwise.

25. Changes to the Service, Plans, and Limits

We may modify, improve, update, suspend, discontinue, replace, or remove parts of the Service at any time. We may also change plan features, prices, limits, Fair Use thresholds, payload restrictions, queue behavior, API behavior, renderer configuration, integrations, or documentation.

Material changes to paid plan prices normally apply at the next renewal or when you change plans, unless the change is required sooner for legal, tax, security, abuse-prevention, or operational reasons. We may make immediate changes where necessary to protect the Service, users, infrastructure, security, or legal compliance.

26. Suspension and Termination

We may suspend, throttle, block, downgrade, cancel, or terminate your Account, API Keys, subscription, Queue, requests, or access to the Service immediately and without refund if we reasonably believe that:

• you violated these Terms;
• you abused or attempted to abuse the Service;
• you performed prohibited security testing or attempted to find, exploit, or trigger renderer errors or infrastructure weaknesses;
• you intentionally generated meaningless, excessive, malicious, or destructive requests;
• your use threatens the security, integrity, availability, performance, or reputation of the Service;
• your API Key, Account, application, or infrastructure is compromised;
• your payment fails, is disputed, is reversed, is fraudulent, or is subject to chargeback abuse;
• your use creates legal risk or violates applicable law or third-party rights.

For serious misuse, abuse, fraud, attacks, dangerous JavaScript, malicious payloads, or attempts to disrupt or break PDF generation, we may cancel your subscription, block access, revoke API Keys, delete queued jobs, and deny refunds or credits to the fullest extent permitted by law.

You may stop using the Service at any time. Termination does not relieve you of payment obligations incurred before termination.

27. Service Provided "As Is"

The Service is provided on an "as is" and "as available" basis. To the fullest extent permitted by law, BladePDF disclaims all warranties, representations, guarantees, and conditions, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, uninterrupted operation, error-free operation, availability, security, accuracy, compatibility, and reliability.

We do not warrant that the Service will meet your requirements; that all PDFs will render correctly; that all content, CSS, JavaScript, fonts, images, URLs, or assets will work; that the Service will be uninterrupted, secure, or error-free; or that defects will be corrected.

Some jurisdictions do not allow certain warranty exclusions, so some exclusions may not apply to you. In those cases, exclusions apply only to the maximum extent permitted by law.

28. Limitation of Liability

To the fullest extent permitted by law, BladePDF and its operator, suppliers, contractors, licensors, and service providers will not be liable for indirect, incidental, special, consequential, exemplary, punitive, or enhanced damages; lost profits; lost revenue; lost business; lost goodwill; lost savings; business interruption; loss of data; loss of PDFs; loss of payloads; loss of API Keys; cost of substitute services; or damages arising from rendering errors, failed renders, downtime, delays, security incidents, third-party services, or unauthorized access.

Except for liabilities that cannot legally be limited, our total aggregate liability arising out of or relating to the Service or these Terms will not exceed the greater of:

• the amount you paid to BladePDF for the Service during the twelve (12) months before the event giving rise to the claim; or
• US $100.

The limitations in this section apply whether the claim is based on contract, tort, negligence, strict liability, warranty, statute, or any other legal theory, even if a remedy fails of its essential purpose.

Nothing in these Terms excludes or limits liability where liability cannot be excluded or limited by applicable law, including liability for intentional misconduct or other non-excludable liability where applicable.

29. Indemnification

To the fullest extent permitted by law, you agree to defend, indemnify, and hold harmless BladePDF, its operator, suppliers, contractors, licensors, and service providers from and against claims, demands, damages, losses, liabilities, penalties, fines, costs, and expenses, including reasonable legal fees, arising out of or related to:

• your use or misuse of the Service;
• your Account, API Keys, application, integrations, or systems;
• your Customer Content or Generated PDFs;
• your violation of these Terms;
• your violation of applicable law or third-party rights;
• your failure to secure credentials, API Keys, infrastructure, repositories, or logs;
• your end users, customers, clients, employees, contractors, or other third parties.

30. Export Control and Sanctions

You must comply with applicable export-control, sanctions, anti-terrorism, and trade-compliance laws. You must not use, access, sell, export, re-export, or provide the Service in violation of such laws or for restricted parties, restricted territories, prohibited end uses, or unlawful purposes.

31. Confidentiality

You may receive non-public information about the Service, including API behavior, security information, beta features, technical implementation details, or support responses. You must protect confidential information and use it only for your authorized use of the Service.

We treat non-public Customer Content submitted to the Service as confidential to the extent described in these Terms and our Privacy Policy, but you acknowledge that no internet-connected service can be guaranteed to be perfectly secure.

32. Notices

We may send notices to the email address associated with your Account, through the dashboard, through Paddle where billing-related, or by posting notices on the website. You are responsible for keeping your email address current.

Legal notices to BladePDF must be sent by email to support@bladepdf.com and should clearly state that they are legal notices. Notices may also be sent to the registered address listed in these Terms where required by law.

33. Consumer Complaints and Alternative Dispute Resolution

Please contact us first if you have a complaint, billing dispute, refund request, or service issue. You can reach us through the dashboard ticket system, the contact page, or by email at support@bladepdf.com.

If you are a consumer and a dispute cannot be resolved directly, you may have the right to use an applicable consumer alternative dispute resolution body. For Czech consumer disputes where applicable, the competent ADR entity may be the Czech Trade Inspection Authority (Česká obchodní inspekce): https://coi.gov.cz/en/information-about-adr/.

This section does not limit any mandatory consumer rights available in your country of residence.

34. Governing Law and Disputes

These Terms are governed by the laws of the Czech Republic, without regard to conflict-of-laws rules.

If you are a business user, professional user, or other non-consumer, the courts of the Czech Republic will have jurisdiction over disputes arising out of or relating to these Terms or the Service, unless we agree otherwise in writing.

If you are a consumer, this governing-law clause does not deprive you of mandatory protections or mandatory jurisdiction rules available under the laws of your country of residence.

Where permitted by law, disputes must be brought individually and not as a plaintiff or class member in any purported class, collective, representative, consolidated, or private-attorney-general action. This paragraph does not limit rights that cannot be waived under applicable law.

35. General Terms

• Entire agreement. These Terms, together with any referenced policies, order details, Paddle checkout terms, and any written agreement signed by us, form the entire agreement between you and BladePDF regarding the Service.
• Severability. If any part of these Terms is found invalid or unenforceable, the remaining parts remain in effect.
• No waiver. Our failure to enforce a provision is not a waiver of our right to do so later.
• Assignment. You may not assign or transfer these Terms without our prior written consent. We may assign or transfer these Terms as part of a merger, acquisition, reorganization, sale of assets, change of operator, or by operation of law.
• Force majeure. We are not liable for delay or failure caused by events beyond our reasonable control, including internet failures, hosting failures, third-party service failures, labor disputes, natural disasters, war, terrorism, civil unrest, government action, power failures, attacks, security incidents, or major infrastructure outages.
• No third-party beneficiaries. These Terms do not create rights for third parties, except where expressly stated or required by law.
• Survival. Sections that by their nature should survive termination will survive, including payment obligations, ownership, confidentiality, disclaimers, limitation of liability, indemnification, dispute terms, and general terms.
• Language. These Terms are written in English. Translations may be provided for convenience only. If there is a conflict, the English version controls to the fullest extent permitted by law.

36. Changes to These Terms

We may update these Terms from time to time. The updated Terms will be posted with a new effective date. If changes are material, we may provide additional notice through the dashboard, email, website, or billing flow.

Continued use of the Service after updated Terms take effect means you accept the updated Terms. If you do not agree to the updated Terms, you must stop using the Service and cancel any paid subscription before the next renewal.

37. Contact

For support, legal notices, billing questions, refund requests, downtime remedy requests, privacy questions, complaints, or abuse reports, contact BladePDF:

• Operator: Karel Talich
• Identification Number: 19409516
• Registered address: Nálepkova 298, 405 05 Děčín, Czech Republic
• Email: support@bladepdf.com
• Dashboard: ticket system available inside your BladePDF account
• Contact page: /contact