Terms of Service

Effective date: September 2026

1. Acceptance of Terms

By accessing or using the getpeppr API, SDK, dashboard, or website (collectively, the "Service"), you agree to be bound by these Terms of Service ("Terms"). If you are using the Service on behalf of an organisation, you represent that you have authority to bind that organisation.

These Terms are between you and Zero Loop Labs Ltd, a company registered in England & Wales (Company No. 17035492), 17 Heronsforde, London W13 8JE, UK ("Zero Loop Labs", "we", "us").

Your use of the Service is also governed by our Privacy Policy, which describes how we collect and process personal data.

2. Description of Service

getpeppr provides a developer-first SDK and API gateway for sending and receiving Peppol e-invoices. The Service translates JSON invoice data into Peppol-compliant UBL XML and delivers documents to the Peppol network via our access point provider.

3. Account Registration

To use the Service, you must create an account. You are responsible for maintaining the confidentiality of your API keys and account credentials. You must notify us immediately at hello@getpeppr.dev if you suspect unauthorised access to your account.

You must not share your sk_live_ or sk_sandbox_ API keys in client-side code, public repositories, or any context where they may be exposed to third parties.

4. Acceptable Use

You agree not to use the Service to:

We reserve the right to suspend or terminate accounts that violate these restrictions without prior notice.

5. Peppol Network Obligations

By sending invoices through the Service, you acknowledge that:

6. Identity Verification and Attestation

6.1 Attestation requirement

Before invoices can be sent to the Peppol network via the Service in production, the legal entity must be declared and the person acting for it must confirm that they are authorised to use its Peppol identifier. For a standard account, an organisation admin gives that confirmation via a checkbox when registering the identifier. For a platform sub-tenant, the customer attests directly through a signed, single-use link; the platform cannot attest on the customer's behalf. A sub-tenant's attestation is an authorisation given to the platform; it does not make the sub-tenant a party to these Terms.

6.2 Verification process

We verify the declared name or identifier validity against public verification sources. Which source we query depends on the Peppol scheme of the identifier you register:

Where a fallback registry is queried, our Privacy Policy describes what is transmitted to it and what we retain.

Automated registry verification typically completes within one minute of registration. If automatic verification is unavailable, production sending remains unavailable until identity is verified; Contact support to arrange verification. Our public documentation at /docs/onboarding/verification describes each verification state and how to resolve a failure.

6.3 Retention of verification records

We retain a minimized audit record of each verification — provider, verdict, similarity score, country, the last four characters of the identifier, and the verification timestamp — for six years from the verification date. We align that period with the six-year time limit for bringing a claim on a simple contract under the Limitation Act 1980, so that we can establish and defend claims about who we admitted to the network. Raw registry names and addresses are not stored in the default audit record. Once the six years have elapsed the record is purged by a monthly job, so it may persist for up to a further month.

6.4 Re-attestation

We may require re-attestation when these Terms are materially updated. Continued access to production invoice sending may require you to re-confirm the attestation in §6.1. The dashboard will display a non-dismissible banner when re-attestation is required.

6.5 Legal basis

We process verification data under UK GDPR Article 6(1)(b) (performance of this contract — §6.1 attestation and §6.2 verification are pre-conditions for production invoice sending) and Article 6(1)(f) (legitimate interest in preventing impersonation on the Peppol e-invoicing network and in preserving its integrity). Our duties under the OpenPeppol Integrator agreement are contractual rather than statutory, so we do not rely on Article 6(1)(c) for this processing. You may therefore object to it and ask us to erase the record; we will do so unless we have compelling legitimate grounds to continue, or need it to establish or defend a legal claim.

7. Fees and Payment

Fees follow the plan you subscribe to (see pricing at getpeppr.dev/pricing): a fixed monthly subscription, a per-document charge for documents exchanged in production — both sent and received — and, on the Platform plan, a monthly charge per registered customer Legal Entity beyond those included (your own Legal Entity is never counted). Billing is managed via Stripe. You authorise us to charge your payment method on file. All fees are exclusive of VAT. The subscription is charged at the start of each billing period; usage is charged as it accrues — on the Platform plan once it reaches the threshold shown on the pricing page, otherwise at the end of the period. Where your Order Form states different fees, thresholds or terms, the Order Form prevails.

We reserve the right to change pricing with 30 days' notice. Continued use of the Service after a price change constitutes acceptance of the new pricing.

8. Service Availability

We aim for high availability but do not guarantee uninterrupted service. The Service is provided "as is" without warranty of any kind, express or implied. We will endeavour to provide notice of planned maintenance where practicable. Current service status is available at status.getpeppr.dev.

9. Intellectual Property

The getpeppr SDK (@getpeppr/sdk) is published under the MIT licence, declared in the package manifest on npm. The getpeppr API, dashboard, and all associated proprietary software remain the exclusive property of Zero Loop Labs Ltd.

You retain all rights to the invoice data you submit. You grant us a limited licence to process that data solely to provide the Service.

10. Confidentiality

Each party agrees to keep confidential any non-public information disclosed by the other party in connection with the Service, and to use such information only for purposes of these Terms.

11. Limitation of Liability

To the maximum extent permitted by applicable law, Zero Loop Labs Ltd shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including loss of profits, revenue, data, or business opportunities, arising out of or in connection with the Service, even if advised of the possibility of such damages.

Our total aggregate liability to you shall not exceed the greater of (a) the amounts paid by you to us in the 12 months preceding the claim, or (b) £100.

Nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, fraud, or any other liability that cannot be excluded under English law.

12. Indemnification

You agree to indemnify and hold harmless Zero Loop Labs Ltd, its officers, directors, and employees from any claims, damages, or expenses arising from your use of the Service, your violation of these Terms, or your violation of any applicable law or third-party rights.

13. Termination

Either party may terminate these Terms at any time. You may close your account via the dashboard or by emailing hello@getpeppr.dev. We may suspend or terminate your access for breach of these Terms, non-payment, or if required by law.

Upon termination, your right to use the Service ceases immediately. Your data will be retained for 30 days after account deletion to allow recovery — and up to 30 days more while a signed contract is still being secured with our e-signature provider — after which it is permanently removed, except the records our Privacy Policy lists as surviving. Billing records are retained for 7 years: HMRC requires company records to be kept for six years from the end of the accounting period they fall in, and VAT records for at least six years — longer if a return was filed late, if a compliance check is open, or if the record still bears on an open period. Because the company-records clock starts at our 28 February year end rather than at the document, we keep each billing record for seven years from its own date, and longer where that obligation runs longer. Contracts you have signed with us are kept on a different basis: our own copy for a period measured from the day you ask us to delete your account rather than from the document. See our Privacy Policy for both, and for the copy our e-signature provider keeps.

14. Governing Law and Disputes

These Terms are governed by the laws of England and Wales. Any dispute arising from these Terms shall be subject to the exclusive jurisdiction of the courts of England and Wales.

We encourage you to contact us first at hello@getpeppr.dev to resolve any dispute informally before commencing legal proceedings.

15. Changes to These Terms

We may update these Terms from time to time. We will provide at least 14 days' notice of material changes by email or by posting a notice on the dashboard. Continued use of the Service after changes take effect constitutes your acceptance of the revised Terms.

16. Contact

For questions about these Terms, contact us at hello@getpeppr.dev.