Skip to content
Menu
How it works Developers Use cases Pricing Security Docs Login Get API access

Terms

Terms of Service

These terms describe how customers may access and use exdata’s document extraction API, workspace, billing, support, and related services.

1. Agreement

These Terms of Service (“Terms”) apply to access to and use of the exdata product, including its website, API, API documentation, account workspace, document extraction service, billing flows, support, and related services (collectively, the “Service”). “Customer” means the organization or individual that creates an account, signs an order form, completes checkout, or otherwise uses the Service.

The Service is operated and provided by Outer Platforms Limited, with its address at Centris Business Gateway, Level 4/W, Triq Is-Salib Tal-Imriehel, Zone 3, Central Business District, Birkirkara, CBD 3020, Malta (“Provider”). exdata is a product of the Provider.

If Customer and Provider sign a separate written agreement or order form, that agreement controls where it expressly conflicts with these Terms.

2. Service

The Provider makes the Service available through an API and workspace for uploading documents, processing documents, viewing structured results, managing account access, configuring webhooks, handling credits and billing, setting retention, and reviewing account history.

Processing is asynchronous. A successful upload response means the document was accepted for processing, not that extraction is complete. Customers should poll document status or use webhooks to continue downstream workflows.

3. Accounts And Access

Customers are responsible for all activity under their accounts, API tokens, webhook endpoints, and workspace users. Customers must keep credentials secure, assign appropriate roles, revoke unused access, and notify the Provider if they suspect unauthorized access.

The Provider may suspend or restrict access if needed to protect the Service, prevent abuse, comply with law, investigate security issues, address unpaid invoices, or prevent harm to customers or third parties.

4. Customer Content

Customer remains responsible for the documents, text, metadata, webhook destinations, and other content submitted through the Service. Customer must have the rights and legal basis needed to upload and process that content through the Service.

Customer grants the Provider the rights needed to process customer content for the Service, including document extraction, previews, API responses, webhook delivery, support, security, abuse prevention, retention, backup, and legal compliance.

5. Acceptable Use

Customers must not use the Service to process unlawful content, violate privacy or intellectual property rights, submit malware, attack the Service, bypass rate limits, abuse test or billing paths, reverse engineer security controls, overload infrastructure, or process documents they are not authorized to submit.

Customers must not use extracted data in a way that violates applicable law or harms individuals, customers, suppliers, employees, or other affected parties.

6. Credits, Billing, And Taxes

Generic extraction uses one credit for each billable started 10-page band. A specialized extraction profile may use a different number of credits per started band, disclosed in the applicable product or API documentation and recorded for the processing run. The applicable rate is used to calculate the total from the page count, and that total is charged when a usable result or retrievable extracted fields remain. Each additional started 10-page band uses the same profile rate.

If processing ends in a terminal error and leaves neither a usable result nor retrievable extracted fields, the Service returns the credits automatically. A credit is not returned when the run produced extracted fields that remain retrievable, even if the run later failed. Files blocked before processing, including unsupported or unsafe files, do not consume credits. If an additional page band cannot be covered after analysis, the run is blocked and no net charge remains for that run. Reprocessing is charged once only if it first leaves a usable result or retrievable extracted fields; reprocessing an already charged usable result does not create another paid charge.

A commercial order form may define annual capacity in an account-wide pool and may also define a commitment rate, batch pricing, overage, platform fees, support fees, invoicing, and service commitments. The standard 10-page billing band and result-based pricing continue to apply. Where enabled in the order form, overage allows processing to continue after the committed allowance is used. The order form controls the commercial terms it expressly covers.

Prices are shown in the configured billing currency and are exclusive of tax unless stated otherwise. Stripe Checkout, Stripe Tax, and Stripe Customer Portal may be used for payments, receipts, invoices, tax IDs, billing details, and customer self-service.

Customer is responsible for maintaining accurate billing information, tax information, and payment methods. If payment fails or available credits or contracted capacity are exhausted, live processing may be blocked before extraction starts or when an additional page band is evaluated.

7. API Availability And Changes

The Provider aims to keep the API reliable and backwards-compatible within documented versions. Breaking API changes will be introduced under a new versioned base path where practical. The Provider may change non-breaking behavior, limits, supported file types, pricing, documentation, or Service features with reasonable notice when the change materially affects production customers.

8. Support

Support is provided through the customer’s onboarding or support contact path. Customers should include request IDs, document IDs, webhook delivery IDs, token prefixes, billing references, and affected timestamps when asking for service support.

9. Data Protection

Data protection terms are described in the Privacy Policy, Data Processing Addendum, Technical and Organizational Measures, and Subprocessor List.

10. Confidentiality

Each party may receive non-public information from the other party. The receiving party must protect confidential information with reasonable care and use it only for the relationship under these Terms, unless disclosure is required by law or authorized by the disclosing party.

11. Disclaimers And Liability

The Provider makes document extraction infrastructure available through the Service, but Customer remains responsible for reviewing extracted results before using them for payments, accounting, tax filings, legal decisions, employment decisions, or other high-impact workflows. No extraction system is guaranteed to be error-free.

To the fullest extent permitted by law, the Provider is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, loss of goodwill, or loss of data. Any liability cap or exclusion in a signed agreement or order form controls where applicable.

12. Termination

Customer may stop using the Service at any time. The Provider may suspend or terminate access for material breach, unpaid amounts, security risk, abusive use, legal risk, or discontinuation of the Service. After termination, Customer should export needed data before retention or deletion windows expire.

13. Contact