Privacy policy

This policy explains what data may be used when using the site, payment, activation, license checks and InvoiceLint support.

1. Local document validation

InvoiceLint works as a local program. During normal validation, XML/PDF files are not sent to the InvoiceLint server. Structure, required fields and rules are checked on the user’s computer.

2. What data may be processed

• purchase email and contact email if the user provides it during payment or support;
• selected plan, billing period, subscription status, end date of the paid period;
• license key, activation status and technical installation identifier;
• service payment identifiers: transaction/customer/subscription id if passed by the payment flow;
• diagnostic information, error text, work log or support package if the user sends them to support;
• selected site language if the browser saves this setting locally.

3. What the data is used for

• issuing, activating, checking and restoring paid access;
• processing payment, renewal, cancellation, refunds and disputed transactions;
• responding to support requests and investigating technical problems;
• protection against abuse, unjustified repeated access grants and license bypass;
• fulfilling obligations related to the sale of a digital product.

4. Payment data

Payment is handled through Paddle. Bank card number, CVV and full payment credentials are entered in the Paddle payment form and are not stored in InvoiceLint. Paddle may process payment data, taxes, receipts, refunds, disputes and data needed to follow its payment rules.

5. Support package and client files

The support package is created only by user action. By default it should include service information about version, settings without passwords or access keys, connected validation rules and recent logs. Source XML/PDF, corrected copies and full reports with document contents must not be added automatically; such materials are sent only if the user decides to attach them for review.

6. Sensitive information and masking

The program and support should mask license keys, passwords, access keys, email and sensitive paths in diagnostic materials where possible. The user must still check materials before sending if they may contain commercial, personal or tax information.

7. Retention period

Payment, license and support data is stored as long as reasonably necessary to provide access, support, abuse protection and payment or legal obligations. Data passed to Paddle is stored under Paddle’s rules.

8. No advertising tracking

No advertising pixels or external analytics counters are connected in the current public site build. If such tools are added later, this policy must be updated before they are enabled.

9. Data requests

For access, correction, deletion or clarification of data, write to [email protected]. In the request, provide purchase email and license key if the question is related to paid access.