Refund Policy

You pay for SitePDF at the beginning of every billing period, and we keep that payment once it clears. Only three billing situations, set out below and verified against our logs, lead to money coming back. Stopping future payments is up to you: renewal can be switched off from your account at any moment.

What a subscription is for

Each plan, monthly or yearly, gives you the HTML to PDF and archiving API with the render allowance and features listed on the pricing page. The price buys a window of time in which your API keys answer and your allowance is ready, not a bundle of conversions, and the window opens completely on its first day. An integration that sends ten renders pays exactly what one that exhausts the allowance pays.

The in-browser converter lets you judge the PDF output before any payment. Subscribing asks us to activate the API at once. The moment your keys go live, any statutory withdrawal or cooling-off right you might have had is spent, and you agree to that.

Exceptions

• Two payments for one period. Our billing system collected twice by mistake.
• A charge you never approved. Your card paid for SitePDF without your consent, the report reaches us inside 14 days of the charge, and our API and billing logs together with the payment operator's data confirm it. We may also ask for evidence that your bank has a fraud report on file.
• An API that produced nothing. Because of a fault we confirmed on our side, every render request returned nothing usable for an uninterrupted stretch, your report came in while requests were still failing, and output was never restored. Slower renders, scattered errors and problems in your network, code or source pages are not covered.

Any refund is capped at the amount paid for the affected period, goes back to the charged card only, and ends our liability for that charge. One refund does not lead to another.

What does not qualify

• A change of plans, a home grown renderer, or a switch to another provider.
• Few or no renders in a paid period, or an integration that was never finished.
• PDFs that look different from the browser view because of print CSS, fonts that were not loaded, slow external assets or missing page break rules.
• Source pages that block automated visits, sit behind a login you did not supply, or change after capture.
• Failed renders. They are logged as failed and do not use any allowance, so nothing was paid for them.
• A renewal nobody remembered to cancel, or a cancellation made just after it.
• A renewal that cleared after earlier card attempts were declined, as described further down.
• Reading the plan as a single payment, although the pricing page, checkout and receipt email all mention renewal.
• Picking the wrong plan or term, or needing more renders halfway through a period.
• A capability not shown on the pricing page.
• Leftover days after cancelling. Keys work until the period ends, with no partial credit.
• Renders made with keys you shared, or keys that leaked from your own repository.

Renewal, declined cards and cancellation

A subscription renews automatically. You can cancel in your account within seconds, with no message to us, and every later renewal stops right then. Your keys remain active until the end of what you paid for, and money already collected stays collected.

Each period starts with full access, and its fee is owed from that moment. When a card is declined, the fee is still owed and our payment operator retries the same invoice over the next few days, which is a collection attempt, not a second charge. Cancelling during the retries turns off later periods, while the current one remains payable and is not refunded once collected. If another period is not wanted, the renewal date in your account is the deadline for cancelling.

Asking for a refund

Write from the email address of your SitePDF account to [email protected], no later than 14 days after the charge, quoting its date and amount and the exception you rely on. Messages from another address or after the 14 days are not considered, and a refusal is not reopened.

Going straight to a chargeback without emailing us first breaches our Terms of Service, and the account is closed permanently together with every API key on it.

Logs we keep

Registering means you accept our Terms of Service, which contain this policy and our Privacy Policy. Plan, amount, billing term and automatic renewal all appear at checkout before you pay, and the receipt email confirms all four.

For every subscription we retain the moment of purchase, the plan and amount displayed, your agreement to the terms, our emails and renewal reminders, and the account log: sign-ins, keys issued and revoked, and every render request with its status, page count and technical metadata. The payment operator separately records each charge with the issuing country of the card, where the payment originated and the result of 3D Secure checks. Claims that a charge was not authorised are tested against these logs, which we share with the bank if a chargeback is filed.

Before 14 October 2026

Plans paid before that date keep the terms in force at purchase. If you signed a separate service agreement for the API, that agreement governs the plan it covers.