AccountCloud
NLGet a test key

Terms of service

What you can expect from us, and what we expect from you, when you use AccountCloud. We've written it as plainly as we could.

Version
1.0
Effective
4 November 2026
Status
DraftThis text is still being reviewed by our lawyers before AccountCloud opens to everyone.
Contracting party
Informer Online Nederland B.V., trading as AccountCloud
Language
This English version is a translation, for your convenience. Where the two differ, the Dutch text prevails.
Also read
Privacy policyData processing agreement

1. Who we are and what these terms cover

  1. AccountCloud is a trade name of Informer Online Nederland B.V., based in Rijswijk, the Netherlands, registered with the Dutch Chamber of Commerce under number 63388928, VAT number NL855214569B01. Your agreement is always with Informer Online Nederland B.V. In these terms, that company is “we” or “us”.
  2. These terms apply to every use of AccountCloud: the API at api.accountcloud.io, the portal at app.accountcloud.io, the documentation at docs.accountcloud.io, and every agreement you make with us. You accept them when you create an account.
  3. Your own purchasing or other terms do not apply, even if you refer to them.
  4. The data processing agreement is part of these terms. Where it concerns personal data and the two conflict, the data processing agreement prevails. How we handle the data of the people who use your account is in the privacy policy.
  5. If we’ve agreed something different with you in writing, such as paying by invoice, that agreement prevails.

2. Definitions

  • Account: your space with us, with your company details, users, API keys and credit.
  • API key: the key you make calls with. A live key (ac_live_…) works with real data and costs credit. A test key (ac_test_…) returns fixed test values and costs nothing.
  • Call: one request to the API. An operation is what a call does, such as ocr.extract or company.profile. An integration is a group of operations around one subject, such as OCR and UBL.
  • Credit: the amount you’ve paid us in advance, from which we deduct your usage.
  • Base subscription: the fixed monthly amount for an account that goes live (section 8).
  • Source: a register, government service or supplier we get data from, such as a business register or VIES, the VAT system of the European Commission.
  • Documentation: the guides, the API reference and the changelog at docs.accountcloud.io.

3. Businesses only

  1. AccountCloud is for businesses and organisations only. When you sign up, we ask for a VAT number, which we check in VIES, or a business register number. Consumers cannot create an account.
  2. Whoever creates an account declares that they are authorised to act on behalf of the business.
  3. You get live keys only after we’ve verified your business. We may refuse a sign-up, for example if we cannot verify the business.
  4. Keep your company details in the portal up to date. They appear on your invoices and determine the VAT.

4. Your account, users and API keys

  1. You are responsible for everything that happens with your account and your API keys. Keep a key secret: don’t put it in code that others can see, such as a website or a public repository.
  2. We only store a hash of a key, so you see a key once, when you create it.
  3. You can restrict each key: to certain operations, IP addresses, an end date and a monthly amount. We recommend you do.
  4. If you think a key has leaked, revoke it in the portal straight away and let us know. We may block a key ourselves if we see it has leaked or is being misused.
  5. You can invite colleagues and give them a role. Some actions, such as stopping the base subscription, require two-factor authentication.

5. Test mode

  1. Test keys are free. They touch no source and no credit. They return fixed test values, listed in the documentation, the error paths included.
  2. Test values show how the API behaves. They are not real data, and a live call may give a different result.
  3. We delete documents sent with a test key after 24 hours.

6. Prices

  1. Our prices are on our website, in the portal and in GET /v1/pricing. All prices are in euros and exclude VAT.

  2. You pay the base subscription (section 8), and on top of it per call or, for some integrations, per unit per month. The price says which.

  3. Every response states in the AccountCloud-Charged and AccountCloud-Balance headers what the call cost and how much credit is left. The portal shows what each call cost.

  4. These cost nothing:

    • a call that fails because of an error on our side;
    • a call with invalid input;
    • a call with a test key;
    • a repeated call with the same Idempotency-Key;
    • sending the same document again within the same account: you get the existing document back.

    If a source finds nothing, we only charge if the source charges us for that call, and then at our cost price.

  5. A call costs the price that applied at the time of the call.

  6. We may change our prices. We announce an increase at least 30 days in advance, by email and in the portal. A decrease may take effect immediately. If you don’t agree with an increase, you can terminate before it takes effect, and we refund your unused credit (section 7.7).

  7. High volumes, or a different price? Get in touch. We put such an arrangement in writing.

7. Credit and payment

  1. You pay in advance: you top up your credit in the portal, with one of the payment methods offered there. Payments go through Mollie. The credit is added as soon as Mollie confirms the payment.
  2. You can set up automatic top-ups. When your credit drops below a threshold you choose, we charge the amount you choose. By setting this up, you authorise those charges. You can switch it off in the portal whenever you like.
  3. When your credit runs out, live calls get status 402 and do nothing. Test keys keep working.
  4. You receive an invoice for every paid top-up. We charge VAT on it: 21% if you’re in the Netherlands, reverse-charged to you if you’re in another EU country and have a valid VAT number, and no Dutch VAT if you’re outside the EU.
  5. If a payment is reversed or charged back, we deduct the related credit from your balance again. If that credit has already been used, the amount remains due, and we may block your live keys until it’s paid.
  6. Once your business is verified, you may receive a starting credit to try the API live. That starting credit, and any other credit we give you (for example as compensation), is a bonus: it doesn’t start the base subscription, and it isn’t paid out.
  7. Credit doesn’t expire while your account is in use. Only after 24 months without any activity (no call and no top-up) can it expire, and we’ll warn you by email at least 30 days beforehand. Unused credit that you paid for yourself is refunded on request, minus bonuses. Ask via [email protected].
  8. Paying afterwards, by invoice, is only possible if we agree it with you in writing. The credit limit we agree and the payment term on the invoice then apply.

8. The base subscription

  1. An account that goes live pays a small fixed monthly amount: the base subscription. The amount is listed with the prices. It includes no calls.
  2. It covers access to the live environment and all integrations, the portal, webhooks, the request log and support by email.
  3. It starts with your first paid top-up, not with the starting credit. The checkout tells you so before you pay.
  4. We deduct it every day as a daily portion: the monthly amount divided by the number of days in that month. So you only pay for the days it runs.
  5. If your credit runs out, the subscription runs for 3 more days and then pauses. A paused subscription costs nothing. It resumes after a top-up.
  6. You can stop the subscription in the portal whenever you like, as the owner or with the billing role. From the next day nothing more is deducted, and automatic top-ups stop. Live calls then get 403 subscription_ended. Test keys keep working. Your credit stays, and you can ask for it back under section 7.7. A new paid top-up starts a new subscription.
  7. An integration priced per unit per month, such as a connected bank account in the future, is charged the same way: per day, and paused after 3 days without credit. What’s included per unit is listed with the price.

9. What you can expect from the service

  1. We do our best to keep the API available at all times, but we don’t guarantee availability unless we’ve agreed an SLA with you in writing. The current status is at status.accountcloud.io.
  2. Where possible, we announce planned maintenance on the status page in advance.
  3. The API has a version in its path (/v1). Changes that break an existing integration go into a new version, or we announce them at least three months in advance in the changelog and by email. New fields, operations and error codes may be added without notice. Build your integration to allow for that.
  4. An operation with the status preview may still change or disappear, without that notice period. While the API is in pre-release (see the changelog), this applies to the whole API.
  5. Limits per key and per account apply, as described in the documentation.
  6. A document you have checked by a member of our staff (processing: verified) is usually processed within 24 hours on working days. That is a target, not a guarantee. If we reject a document, you only pay the OCR price.
  7. Support is by email, at [email protected].

10. Data from sources

  1. Many answers come from sources: business registers, VIES, postal operators and other suppliers. We pass on what the source gives. We don’t check its content, and we don’t vouch for its accuracy, completeness or timeliness.
  2. For current information with legal effect, always consult the register itself, such as the Dutch Business Register of the KvK.
  3. Each source may have its own conditions, for example about reuse or attribution. They are listed on the integration’s page and in the documentation, and they apply to you too. As a result, some data isn’t available to everyone.
  4. You use data from sources only for your own business and for the service you provide to your own customers. You don’t use it to build your own copy of a register, you don’t offer it to others as a separate dataset, and you don’t make it searchable by natural person.
  5. OCR results are produced automatically and can contain errors. Check them before you base your bookkeeping or a tax return on them. You remain responsible for your own records and tax returns.

11. What’s not allowed

You don’t use AccountCloud:

  • in breach of the law or of the rights of others;
  • for documents or data you’re not allowed to have processed;
  • to get around our limits, caps, test mode or security, or to access other people’s data;
  • to overload the service, for example with a load test without our permission;
  • to send malware or other harmful code;
  • to resell the API as a standalone service, unless we’ve agreed it in writing. Using AccountCloud in your own product, for your own customers, is fine. That’s what the AccountCloud-Entity header is for.

12. Suspension and blocking

  1. We may suspend your access in whole or in part (one key, one operation or your whole account) if:
    • you don’t pay an amount you owe us;
    • you breach these terms;
    • there’s a security risk, or we suspect misuse;
    • a law, a government or a source requires it of us.
  2. We tell you in advance where we can, and otherwise straight afterwards, with the reason. Once the reason is gone, we lift the suspension.
  3. We may switch off an operation for everyone temporarily, for example when a source has an outage or stops supplying. A live call then gets an error and costs nothing.

13. Your data and documents

  1. Your data and documents remain yours. We use them only to provide the service, as described in the data processing agreement.

  2. How long we keep them:

    • documents: 7 days after processing. In the portal you can set this per account to anything from 0 to 30 days;
    • documents sent with test keys: 24 hours;
    • the data per call (time, operation, status and cost, without content): 13 months;
    • usage totals, without personal data: as long as we need them for our figures.

    Database backups still contain deleted data for up to 14 days.

  3. We don’t store request or response bodies in our logs.

  4. If you report an OCR error with POST /v1/documents/{id}/feedback and allow_training: true, you allow us to use that one document to test and improve our recognition: the original, our result and your corrections. We are responsible for that use ourselves, and we keep it for up to 12 months. With allow_training: false we only keep your report, without the document. In the portal you can switch sharing off for your whole account. We don’t train an AI model of our own on your documents.

  5. We may use usage data, without the content of documents, to measure, improve and secure the service, and to report on it anonymously.

14. Intellectual property

  1. All rights to AccountCloud, the software, the API, the documentation and the brand remain with us or our licensors. While the agreement runs, you get a non-exclusive, non-transferable right to use AccountCloud under these terms.
  2. You may freely use and adapt the code samples in the documentation in your own software.
  3. If you give us ideas or feedback, we may use them freely.

15. Liability

  1. If we are liable, it is only for direct damage, and per event up to at most the amount you paid us in the 12 months before that event. A series of related events counts as one event.
  2. We are not liable for indirect damage, such as lost profit, lost savings, damage to reputation, business interruption, fines or tax assessments.
  3. Nor are we liable for damage because data from a source was incorrect, incomplete or out of date, or because you used an OCR result without checking it.
  4. These limitations don’t apply in case of intent or deliberate recklessness on the part of our management.
  5. Report damage in writing within 30 days of discovering it. A claim lapses 12 months after the event that caused the damage.
  6. We are not liable if we cannot meet our obligations because of circumstances beyond our control (force majeure), such as an outage at a source, a hosting provider, a payment provider or an internet provider, an attack on our network, or a government measure.

16. Indemnity

You indemnify us against claims by others that arise from your use of AccountCloud in breach of these terms or the law, for example because you had documents processed that you weren’t allowed to have processed.

17. Confidentiality

We each keep the other’s confidential information confidential, and use it only for the agreement. Our staff, including those who check documents, are bound by confidentiality.

18. Term and termination

  1. The agreement starts when you create an account and runs for an indefinite period.
  2. You can terminate at any time. Stop the base subscription in the portal, and ask us via [email protected] to close your account.
  3. We can terminate with 30 days’ notice, by email. In case of serious or repeated misuse, or if the law requires it, we may terminate immediately.
  4. After termination, unused credit you paid for yourself is refunded on request, minus bonuses. We delete documents according to the retention periods in section 13. We keep invoices, and the data they require, for as long as the law prescribes: 7 years in the Netherlands.
  5. Whatever by its nature should survive termination, such as the sections on liability and confidentiality, survives it.

19. Changes to these terms

  1. We may change these terms. We announce a change at least 30 days in advance, by email and on this page.
  2. If a change is to your disadvantage, you can terminate before it takes effect, and we refund your unused credit as in section 18.4. If you keep using AccountCloud after that date, the new terms apply.
  3. A change required by law, or one that is only to your advantage, may take effect sooner.

20. Law and disputes

  1. These terms and the agreement are governed by Dutch law. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply.
  2. We’ll first try to resolve a dispute together. If that fails, the competent court of The Hague District Court (rechtbank Den Haag) decides.
  3. These terms exist in Dutch and in English. Where the two differ, the Dutch text prevails.

21. Contact

Questions about these terms? Email [email protected].