Terms of Service

These Terms of Service ("Terms") govern your access to and use of the online service made available by Byte Imagination Roger Zacharczyk (trading as Byte Imagination; "we", "us", "our" or "Provider") through the domain on which these Terms are published (the "Service").

By creating an account, generating an API key, or otherwise using the Service, you ("Customer", "you") agree to these Terms. If you do not agree, do not use the Service.

1. Provider identity

• Legal name: Byte Imagination Roger Zacharczyk
• Registered seat: Ludwika Kondratowicza 59/21, Warsaw, Poland
• Tax ID: PL7551870628
• Contact: contact@byteimagination.com

2. Definitions

• API — the application programming interface exposed by the Service.
• API Key — a secret credential issued to you that authenticates calls to the API.
• Customer Data — data you submit to the Service through the API or web panel.
• Documentation — the user-facing documentation published on the Service's domain.
• Merchant of Record or MoR — the entity that sells the Service subscription to you and acts as the seller for tax and consumer-protection purposes. The MoR is Paddle.com Market Ltd (United Kingdom). See Section 5.
• Additional Terms — terms that supplement these Terms with provisions specific to the Service, published alongside these Terms on the Service's domain. Additional Terms form part of these Terms.
• Subscription — your right to use the Service under a paid plan, governed by Section 6.

3. Eligibility and accounts

• You must be at least 18 years old and able to enter into a binding contract under the law of your jurisdiction.
• You must provide accurate registration information and keep it current.
• You are responsible for all activity under your account and for safeguarding your API Key. You must notify us at contact@byteimagination.com immediately upon discovering any unauthorised use.
• One natural person or one legal entity per account; account sharing across organisations is prohibited.
• The Service, its documentation, and these Terms are offered in English. By creating an account, you confirm that you have sufficient knowledge of the English language to read, understand, and evaluate these Terms and the documents they reference. This confirmation does not limit any mandatory right you have under the law of your country of habitual residence as described in Section 17.

3a. Customer category: business vs consumer

The Service is offered to both businesses (B2B) and consumers (B2C). Some provisions of these Terms apply differently depending on your category:

• Business Customer means a natural or legal person who acquires the Service wholly or mainly for purposes related to that person's trade, business, craft, or profession, and who declares so at checkout (typically by providing a company name and, where available, a tax identification number).
• Consumer Customer means a natural person who acquires the Service wholly or mainly for purposes outside that person's trade, business, craft, or profession.

Your category is determined at checkout based on the information you provide. You may not retroactively change category after a Subscription has begun. The Additional Terms may further refine how each category is treated.

Where a clause of these Terms differs by category, the difference is stated explicitly. In all other clauses, the same rule applies to both categories.

Mandatory consumer rights apply. Nothing in these Terms limits or excludes any right you have as a Consumer Customer under mandatory law of your country of habitual residence.

4. Service description; no SLA

• The Service is provided on an as-is, as-available basis. We do not guarantee uninterrupted availability, error-free operation, specific throughput, or fitness for any particular purpose beyond what is expressly stated in these Terms or in the Documentation.
• Quotas, rate limits, and feature scope per plan are described on the Service's pricing page and in the Additional Terms.
• We may modify, add, or remove features at any time. Material reductions in features that affect your active Subscription will be notified at least 30 days in advance.
• A formal Service Level Agreement ("SLA") is not provided on standard self-service plans and is available only under separately negotiated Enterprise agreements.

5. Merchant of Record; payment

• All payments for Subscriptions are processed by Paddle.com Market Ltd, registered in England and Wales, acting as the Merchant of Record. Paddle is the seller of record to you for tax purposes and for consumer-protection purposes in the relevant jurisdiction.
• Paddle's Buyer Terms and refund handling apply to the transaction between you and Paddle.
• These Terms govern your use of the Service itself and the supply relationship between you and us.

6. Subscriptions, fees, taxes

• Subscriptions are sold per plan as published on the Service's pricing page. Prices are stated in EUR or your local currency as displayed by Paddle at checkout.
• Subscriptions billed monthly or annually in advance. Annual subscriptions are non-cancellable for refund within the paid period; the Subscription continues until the end of that period and then does not renew if cancelled.
• Trial periods, where offered, are described on the pricing page. A valid payment method is required to start a trial. Conversion to a paid Subscription occurs automatically at the end of the trial unless cancelled before then.
• Taxes (VAT, GST, sales tax) are calculated, collected, and remitted by Paddle according to your jurisdiction.
• See the Refund Policy for refund handling.
• Non-payment and suspension. If your subscription becomes past due (a payment attempt fails and is not promptly recovered by Paddle's retry process), your API access continues during a short grace period. If payment is not recovered by the end of the grace period, API access is suspended until the subscription returns to good standing. Suspension does not constitute termination; your account and Customer Data are retained and access is restored automatically once the payment issue is resolved.

7. Quotas, fair use, overage

• Each plan has a quota measured in the unit defined for the Service (as further described in the Additional Terms). Calls in excess of your quota are rejected with an error response and are not billed.
• What counts toward your quota. A call counts against your quota if it was made with a recognised API Key, passed quota and rate-limit checks, and reached the Service's request handling — regardless of whether the Service's response was a success or a validation error. Calls that fail authentication (missing or unrecognised API Key, no active Subscription), calls rejected because your quota is already exhausted, calls rejected by the per-second rate limit, and calls that fail due to a fault on our side do not count against your quota.
• Sustained or systematic attempts to circumvent quotas, including by creating multiple accounts, sharing API Keys, or rotating IPs, constitute a breach of these Terms and the Acceptable Use Policy.

8. Acceptable use

You agree to comply with our Acceptable Use Policy, which is part of these Terms.

9. Customer Data; ownership and licence

• You retain all rights in Customer Data.
• You grant us a non-exclusive, worldwide, royalty-free licence to host, process, transmit, display, and otherwise use Customer Data solely as necessary to provide the Service, support, security, and to comply with law.
• You represent and warrant that you have all rights necessary to submit Customer Data to the Service and that Customer Data does not infringe any third-party rights or violate applicable law.
• We process personal data contained in Customer Data as a processor on your behalf under the Data Processing Agreement.

10. Confidentiality

Each party will protect the other party's non-public information disclosed under these Terms with the same degree of care it uses for its own confidential information, and at least reasonable care. This obligation does not apply to information that is or becomes publicly available without breach of these Terms, was known to the recipient before disclosure, is independently developed, or is rightfully obtained from a third party.

11. Customer warranties and indemnification

• You represent and warrant that (a) your use of the Service will comply with these Terms and applicable law; (b) Customer Data is lawful and you have all necessary rights and consents to submit it; (c) you will not use the Service to send unlawful, harmful, infringing, or harassing content.
• You will indemnify, defend, and hold us harmless against any claim, damage, loss, or expense (including reasonable legal fees) arising out of your breach of the warranties in this Section, your breach of the Acceptable Use Policy, or any claim by a third party in connection with Customer Data or your use of the Service.

12. Disclaimer of warranties

To the maximum extent permitted by law, the Service is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, reliability, or quiet enjoyment. We do not warrant that the Service will be uninterrupted, secure, or error-free, that defects will be corrected, or that any data will not be lost.

This disclaimer does not apply to warranties that cannot be excluded under mandatory law of your country of habitual residence.

13. Limitation of liability

To the maximum extent permitted by law:

• Indirect damages excluded. Neither party is liable for any indirect, consequential, incidental, special, exemplary, or punitive damages, including loss of profit, loss of revenue, loss of business, loss of data, loss of goodwill, or business interruption, arising out of or in connection with these Terms or the Service.
• Cap on total liability — Business Customers. For a Business Customer, our total aggregate liability arising out of or relating to these Terms, the Service, or your use of it, regardless of the form of action and whether in contract, tort, statute, or otherwise, will not exceed the fees paid by you to Paddle for the Service in respect of the calendar month in which the event giving rise to the claim occurred. The Additional Terms may further reduce this cap (for example by expressing it as a service credit) and prevail to the extent of the conflict.
• Cap on total liability — Consumer Customers. For a Consumer Customer, our total aggregate liability arising out of or relating to these Terms, the Service, or your use of it will not exceed the lower of (i) the total amount paid by you to Paddle for the Service in the twelve (12) months preceding the event giving rise to the claim, or (ii) one hundred euros (€100). This cap does not limit any liability that cannot be limited under mandatory consumer-protection law.
• Sole remedy for unavailability. For any claim arising specifically out of unavailability or downtime of the Service, your sole and exclusive remedy is a service credit equal to the pro-rated fees for the period of unavailability, applied against your next invoice. This service credit counts against (and is not in addition to) the aggregate cap above. No additional damages, refund in cash, or compensation of any kind is payable for unavailability except where required by mandatory law.
• Sole remedy. Subject to the preceding paragraphs, the remedies available under this Section are your sole and exclusive remedy for any liability arising out of these Terms or the Service.
• Duty to mitigate. Each party must take reasonable steps to mitigate any loss it suffers. Loss that could reasonably have been avoided is not recoverable.

The limitations in this Section do not apply to (a) liability for intentional misconduct or gross negligence; (b) liability that cannot be limited or excluded under mandatory law of your country of habitual residence; (c) liability under Article 82 of the GDPR.

13a. Notice of claim and opportunity to cure

Before commencing any legal action arising out of or related to these Terms or the Service, the claimant must give the other party written notice (email to contact@byteimagination.com is sufficient) describing the alleged breach or loss and the remedy sought, and allow the other party thirty (30) days to cure or to propose a reasonable resolution. This requirement does not apply to claims for injunctive relief, claims based on intellectual-property infringement, or where mandatory law allows immediate court action without prior notice. For Consumer Customers, this requirement is a contractual courtesy and does not bar the customer from contacting consumer-protection authorities or alternative dispute-resolution bodies at any time.

14. Term and termination

• These Terms apply from your first use of the Service and continue until terminated.
• Termination for convenience. Either party may terminate the relationship at any time on thirty (30) days' written notice (email is sufficient). Cancellation of an active Subscription before the end of the paid period does not entitle you to a pro-rata refund; access continues until the period ends.
• Immediate self-service closure. Notwithstanding the 30-day notice above, you may close your account immediately at any time using the self-service deletion option in your account settings. Deletion is immediate and irreversible: your access ends, your API Keys are revoked, any active Subscription is cancelled at our payment processor at the same moment, and your Customer Data cannot be recovered afterward. Records we are legally required or permitted to retain are kept as described in the Privacy Policy (see "Effect of termination" below).
• Termination for cause. We may suspend or terminate your access immediately, without notice, if we reasonably determine that you have materially breached these Terms or the Acceptable Use Policy, or if continued provision of the Service would expose us to legal or regulatory risk.
• Data export. You may export your Customer Data at any time while your account is active via the self-service export mechanism in your account settings, in a structured, commonly used, machine-readable format (typically JSON or CSV). Exporting before initiating account closure is recommended, as deletion is immediate and we cannot recover Customer Data after deletion.
• Effect of termination. Upon termination your access ends, your API Keys are revoked, and your Customer Data is deleted immediately. Certain records are retained after closure where we are legally required or permitted to keep them — billing records under accounting law and proof-of-acceptance records for the defence of legal claims — as described in the Privacy Policy and DPA. Sections that by their nature survive (Confidentiality, Indemnification, Limitation of Liability, Governing Law) survive termination.
• Discontinuation of the Service. We may discontinue the Service at any time on at least thirty (30) days' written notice. In that case, the export window in this Section applies, and Paddle will refund any unused prepaid period for active Subscriptions in accordance with its Buyer Terms.

15. Claim window

Any claim arising out of or related to these Terms or the Service must be brought within thirty (30) days after the event giving rise to the claim becomes known to you. Claims brought after this period are barred. This Section does not extend or limit any mandatory statutory limitation period that applies for the benefit of a consumer.

16. Modifications to these Terms

We may modify these Terms from time to time. Material changes will be notified by email at least thirty (30) days before the effective date. To continue using the Service after the effective date, you must explicitly accept the updated Terms when prompted in the Web Panel. The same gating applies to API access: until acceptance is recorded through the Web Panel, API requests will be rejected with an error response indicating that legal acceptance is required. If you do not accept by the effective date, access to the Web Panel and the API will be suspended until you do. If you do not agree to the updated Terms, you may terminate under Section 14 before the effective date — without the thirty (30) day notice period otherwise required by Section 14 — and request export of your Customer Data; nothing in this Section limits any mandatory rights you have as a Consumer Customer under the law of your country of habitual residence.

17. Governing law and venue

• These Terms are governed by the law of the Republic of Poland, excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods.
• For disputes with a Customer that is not a consumer, the courts competent for the registered seat of the Provider have exclusive jurisdiction.
• Disputes with consumers are subject to the mandatory rules of the consumer's country of habitual residence and to the jurisdiction rules of EU Regulation 1215/2012 (Brussels I bis) where applicable.
• EU consumers may also use the European Online Dispute Resolution platform: https://ec.europa.eu/consumers/odr.

18. Consumer rights (B2C)

Consumer rights vary by country. The Service is a digital service supplied without a tangible medium and made available to you immediately after your subscription is activated.

If you are a consumer in the European Union:

• You have a fourteen (14) day right of withdrawal from a distance contract under EU consumer-protection law. Because Paddle is the Merchant of Record (see Section 5), the withdrawal procedure — including any consent to begin performance during the withdrawal period and the corresponding acknowledgement that the right of withdrawal may be lost once the Service has been fully performed — is operated by Paddle in accordance with Paddle's Buyer Terms and applicable consumer-protection law.
• Where you withdraw within the withdrawal period and have already begun to use the Service, you may be charged an amount proportionate to the use you have made of the Service up to the point of withdrawal, in accordance with Paddle's refund process.

If you are a consumer outside the European Union:

• Where mandatory withdrawal, cancellation, cooling-off, or similar rights exist under the law of your country of habitual residence, they apply unaffected by these Terms, and any related refunds are operated by Paddle in accordance with applicable law.

This Section does not limit any other mandatory consumer right under the law of your country of habitual residence.

19. Additional Terms

The Additional Terms published alongside these Terms on the Service's domain form part of these Terms. In case of conflict between these Terms and the Additional Terms, the Additional Terms prevail to the extent of the conflict.

20. Miscellaneous

• Assignment. You may not assign these Terms without our prior written consent. We may assign these Terms to a successor in connection with a merger, acquisition, or sale of substantially all assets.
• Entire agreement. These Terms, together with the Privacy Policy, DPA, AUP, Refund Policy, Cookie Policy, and Additional Terms, constitute the entire agreement between the parties regarding the Service.
• Severability. If any provision is held unenforceable, the remaining provisions remain in full force and effect.
• No waiver. A failure to enforce a right is not a waiver.
• Notices. Notices to us must be sent to contact@byteimagination.com. Notices to you may be sent to the email associated with your account.
• Force majeure. Neither party is liable for failure to perform due to circumstances beyond its reasonable control.
• Language. These Terms are concluded in English. Translations, if any, are for convenience only; the English version controls.

Additional Terms — Invaro

These Additional Terms supplement the Terms of Service for the Invaro Service. Capitalised terms not defined here have the meaning given in the Terms.

In case of conflict between the Terms and these Additional Terms, these Additional Terms prevail to the extent of the conflict.

1. Service description

Invaro is an API for issuing invoices into, and retrieving invoices from, the national e-invoicing / clearance systems operated by tax authorities. It acts as an intermediary between your systems and the relevant national system: you call our API, and we relay the operation on your behalf, converting between your data and the format the system requires.

Invaro currently supports Poland's National e-Invoice System (KSeF — Krajowy System e-Faktur), which is the only national system implemented at this time. Additional country modules, if implemented, will be covered by updated Additional Terms.

The Service exposes:

• a REST API for issuing invoices to, and retrieving invoices from, the supported national e-invoicing system (currently KSeF) on your behalf;
• a web panel for managing API keys and your Subscription.

2. Data we process

This is the most important section to understand before using Invaro. Read it carefully.

Your e-invoicing credentials are used in transit only and are never stored. To authenticate to the national system on your behalf, you supply your authentication credentials — for KSeF, a certificate and its private key, or a short-lived session handle derived from them — with each request. These credentials are used in memory only, for the duration of that single request, solely to carry out the operation you asked for. They are never stored and never persisted, and our logging is configured to redact credentials supplied through the designated request fields. You must supply credentials only through the API fields documented for that purpose; credentials placed elsewhere — query strings, URL paths, or custom headers — may not be subject to the same redaction. When the request completes, the credentials are gone from memory.

Invoice content is processed in transit only and is not retained. Invoice content you submit for issuance, and invoice content we retrieve on your behalf, is processed only while your request is being handled — converted to or from the format the national system requires, encrypted as it requires, and relayed. We do not retain invoice content. The national system itself (for KSeF, the official, legally-mandated archive) is the system of record for the documents you issue and receive.

Invoice content routinely contains personal data of your counterparties — for example their name, address, tax identification number (which may identify a natural person), and bank account number. You are the controller of that data; we process it only in transit, on your instruction, to relay it to the national system (see "Roles under GDPR / RODO" below).

The only data the Service stores is:

• your account record and authentication data (as described in the Privacy Policy);
• usage and billing records (as described in the Privacy Policy);
• if you use the built-in invoice-numbering feature: your numbering series, their counter state and configuration, and the associated activity log for that feature;
• operational records of the KSeF operations performed on your behalf — the type of operation, its outcome, KSeF-assigned reference numbers, timestamps, the source IP address, and operational parameters. These records do not contain your invoice content, your e-invoicing credentials, your counterparty's identifying information, or your own invoice numbers.

The platform Privacy Policy governs how the account, usage, numbering, and KSeF-operation data above is processed and retained.

Roles under GDPR / RODO. You are the controller of the invoice data you issue and receive through Invaro. Each national e-invoicing authority you transmit invoices to (for KSeF, Poland's Krajowa Administracja Skarbowa) is an independent controller for the data held within its own system; it determines the purposes and means of that processing under its national law, and it is not our sub-processor. When you transmit invoice data to a national authority through Invaro, you — as controller — are making a disclosure to that authority acting under its applicable national law. The lawful basis for that disclosure is typically your legal obligation as a taxpayer under the applicable national e-invoicing or VAT legislation (Art. 6(1)(c) GDPR). You are responsible for ensuring that your use of Invaro to fulfil your e-invoicing obligations is consistent with your own obligations as a controller toward the individuals whose personal data appears in your invoices. For the transient, in-transit handling described above, we act as a processor on your documented instructions — the instruction being the API call you make. We keep operational records of the KSeF operations you perform through Invaro (described under "The only data the Service stores" above). We process those records as controller, for support, dispute resolution, and security monitoring, on the basis of our legitimate interest (Art. 6(1)(f) GDPR); the platform Privacy Policy describes how they are retained. This processing introduces no new sub-processor. Questions about this processing can be directed to privacy@byteimagination.com.

Do not treat Invaro as your archive. You must not rely on Invaro as a record-keeping or archival system. We do not retain your invoice content, and the national system is the system of record for issued invoices. Keep your own copies as your business and tax obligations require.

3. Quotas, rate limits, and overage

• Quotas per plan are published on the Service's pricing page.
• Every API call counts. Each call to an Invaro API endpoint counts against your monthly quota if it was made with a recognised API Key, passed quota and rate-limit checks, and reached the Service's request handling. Issuing an invoice, retrieving an invoice, and managing a numbering series each count as a call.
• The following do not count against your quota: calls that fail authentication (missing or unrecognised API Key, no active Subscription); calls rejected because your monthly quota is already exhausted; calls rejected by our per-second rate limit; calls that fail due to a fault on our side; and calls that fail because the national system is temporarily unavailable (national-system outages, transport failures, or national-system server errors) — these surface to you as a service-unavailable response and consume no quota.
• A request the Service authenticated and then rejected for a reason within your control (for example a malformed invoice or a missing required field) does count — the Service performed work to process and reject it.
• Calls in excess of your quota are rejected with an error response and are not charged.
• Quotas reset at the start of each monthly usage window. For monthly subscribers this coincides with each billing period. For annual subscribers, the annual period is divided into monthly usage windows anchored to your subscription start date, and your quota resets at the start of each such monthly window — not once per year.
• Per-key short-burst rate limits may apply on our side to protect the Service; current values are documented in the API Reference.
• The national system imposes its own rate limits. KSeF (and any future national system) enforces per-taxpayer rate limits that are independent of ours. If the national system rate-limits one of your operations, that limit is surfaced back to you as a rate-limit response. Because such a limit reflects a restriction on your taxpayer account rather than a fault on our side, those calls do count against your quota (in contrast to national-system unavailability, above). Those are the national system's limits, not ours, and they apply regardless of your plan with us.

The web panel does not consume your API quota. The web panel for managing your account, API Keys, and Subscription uses session-based authentication and does not count against the monthly call quota.

4. Service availability

• The Service is provided on an as-is, as-available basis. No formal SLA is offered on Solo, Starter, or Pro plans. Enterprise SLAs are negotiated individually.
• Invaro depends on the national e-invoicing system, which we do not operate or control. The Service can only function when the national system (currently KSeF) is available and accepting requests. Its outages, scheduled maintenance windows, throttling, schema changes, or rejections are not failures of our Service for the purposes of availability and any SLA, and are excluded from any availability expectation or service credit owed for downtime. Where the national system is unavailable, our API returns an error reflecting the upstream condition, and such calls do not consume quota (see Section 3). This exclusion concerns the national system's own failures — it does not exclude defects in our Service itself (see Section 6a).

5. Issuance, idempotency, and numbering

• When you use a numbering series to assign the invoice number, supplying an idempotency key makes a retried issuance reuse the same number rather than consume a new one, within the idempotency window. This protects you from accidentally burning a number on a network retry.
• The national system performs document-level duplicate detection based on the content of each submission. This does not prevent two distinct but economically identical invoices from both being accepted if they differ in any way (such as timestamp or an internal identifier). Using an idempotency key on retry is your primary protection against duplicate issuance; the national system remains authoritative for what was ultimately issued.
• We validate the invoice against the national system's format schema before submission, but we do not verify the business or tax correctness of its contents. A request that passes our schema validation is not a representation by us that the invoice is correct, complete, or compliant with the applicable tax law of the relevant jurisdiction. That responsibility is yours (see Section 6).

6. Customer responsibilities

You are responsible for:

• keeping your e-invoicing credentials and session handles secret. They grant access to your taxpayer account and the ability to issue invoices in your name; treat them as you would any production credential. Supply them only through the API fields documented for that purpose, and do not embed them in query strings, URL paths, custom headers, or anywhere else they could be exposed or logged;
• safeguarding your Invaro API Keys and rotating them on personnel changes;
• the accuracy, legality, and timeliness of every invoice you issue. You are the taxpayer of record. You are solely responsible for ensuring that each invoice is correct, that it is issued when the law requires, and that it complies with the applicable tax law of the relevant jurisdiction and the requirements of the relevant national e-invoicing system. We do not validate business or tax correctness beyond the format schema (see Section 5);
• complying with the terms of use of the relevant national e-invoicing system and with applicable tax law;
• keeping your own copies of issued and retrieved invoices as your records require, since we do not retain invoice content (see Section 2).

You must not use Invaro to:

• submit invoices that do not reflect genuine transactions;
• issue invoices using credentials that are not legitimately yours, or otherwise impersonate another taxpayer's identity in the national e-invoicing system;
• probe, stress-test, overload, or attempt to disrupt the national e-invoicing system or any connected government system.

All invoice submissions must comply with applicable tax law and the rules of the relevant national e-invoicing system. This supplements, and does not limit, the platform Acceptable Use Policy.

6a. Liability — service-credit cap for Business Customers

The Service is intended for use in the course of a business or professional activity — issuing invoices in a national e-invoicing system presupposes that you act as a taxpayer. The allocation below reflects that context; it does not exclude or limit any mandatory right of a Customer who nonetheless qualifies as a consumer.

For a Business Customer, the cap on aggregate liability under §13 of the Terms of Service is further refined as follows for this Service:

• Our total aggregate liability for any claim arising out of or related to Invaro is limited to a service credit equal to the fees paid for the calendar month in which the event giving rise to the claim occurred, applied against the next invoice after the claim is resolved. Where no fees were paid for that month (for example during a free trial), no service credit accrues — but the good-faith cooperation below still applies, and for a Consumer Customer any mandatory consumer right applies unaffected by this limitation.
• A Business Customer's sole and exclusive remedy under this Service is the service credit described above. No cash refund is payable in lieu of service credit except where required by mandatory law.
• Defects in our Service are not excluded by Section 4. The exclusion of national-system failures in Section 4 does not extend to errors caused by the Service itself — for example, transmitting an invoice you did not intend to issue, or transmitting an invoice twice due to a fault on our side despite a correctly supplied idempotency key. Where a confirmed defect in our Service results in an invoice being incorrectly issued into the national system, we will, in addition to the service credit above, cooperate with you in good faith in any correction procedures the national system makes available under applicable law. Our liability for such cases remains subject to the cap in §13 of the Terms and to the exclusion of indirect and consequential damages.

For a Consumer Customer, the standard cap in §13 of the Terms of Service applies (lower of 12 months of fees or €100), without limitation of any mandatory consumer right.

7. Data retention specific to Invaro

Data	Retention
E-invoicing credentials (certificate, private key, or session handle) you supply with a request	Used in memory for the duration of that request only; never stored; redacted from our logs when supplied through the designated API fields
Invoice content you submit for issuance or that we retrieve for you	Processed in transit only; never retained by us. The national system is the legal archive
Numbering series, counter state, and the numbering-feature activity log (only if you use the built-in numbering feature)	As described for the numbering feature — for the lifetime of your account; deleted on account closure
KSeF operation records (operation type, outcome, KSeF-assigned reference numbers, operational parameters)	5 years from the date of the operation, then the record is deleted in full. The IP address and KSeF session reference attached to each record are cleared after 365 days; the record itself is kept for the remainder of the 5-year retention period
Account, authentication, usage, and billing records	As described in the platform Privacy Policy

8. No archival guarantee; changes to the Service

• No archival guarantee. We do not archive your invoices. The national e-invoicing system is the official archive and system of record for issued invoices. Do not rely on Invaro to recover an invoice you did not keep a copy of and that is not retrievable from the national system.
• Changes to the Service. We may add, change, or remove features. Material changes that affect interoperability with your integration are notified at least 30 days in advance, in accordance with the master Terms of Service.

Questions about these Additional Terms can be directed to contact@byteimagination.com.