FreightParse Cloud Reading: Trial Terms

Version 2026-10-14

These Trial Terms say what a free self-serve trial of FreightParse Cloud Reading is. The Cloud Reading Addendum printed below, the FreightParse Licence Terms (version 2.1, 14 October 2026) and the Data Processing Agreement for FreightParse Cloud Reading (version 1.1, 9 October 2026) apply to the trial.

T1. Free. The trial costs nothing (Addendum C10).

T2. 14 days. The access key works for 14 days after the day of the sign-up, through the last day shown on the confirmation page (UTC). We may end the trial earlier by written notice (Addendum C11).

T3. About 20 pages a day. The access key reads about 20 pages a day. The count starts again at midnight UTC. All trials together also have a daily limit, so on a busy day a document may be refused until the next day. Cloud Reading is provided as it is, without a guaranteed availability or response time (Addendum C8).

T4. No obligation. Nothing is owed during or after the trial, and the trial does not turn into a paid service by itself. A fee applies only if an Offer that the Customer has accepted in writing states one (Addendum C10).

T5. The results are the Customer's. We claim no rights in the Customer Documents or in the results. The Customer may use the results freely in its business (Licence Terms clause 12.2).

T6. Check every value before filing. Before the Customer lodges a declaration, a competent person working for the Customer checks every value against the documents (Licence Terms clause 7.2; Addendum C7). The Customer remains solely responsible to the customs and tax authorities for every declaration (Licence Terms clause 7.3).

T7. How documents are read. The trial gives the Customer its own access link to the FreightParse reading page. Each document is sent only after the Customer agrees on that page, and is read as the Cloud Reading Addendum and the Data Processing Agreement describe (Addendum C2 to C6).

T8. Accuracy and liability. Clauses 8 (warranty) and 9 (limitation of liability) of the Licence Terms apply. We do not warrant that Cloud Reading reads every value correctly or completely (Addendum C9).

T9. Businesses only. The trial is for businesses that act in the course of their trade or profession (Licence Terms clause 2.2).

T10. Stopping. The Customer can stop at any time by no longer using the access link (Addendum C11).

Cloud Reading Addendum to the FreightParse Licence Terms

Version 1.3, 14 October 2026

Parties

1. The Customer:
   • Legal name: ________________________________________
   • Legal form: ________________________________________
   • Registered in ____________________ under number ____________________
   • Address: ________________________________________
   • Represented by (name and function): ________________________________________
2. Danil Sysenko, sole proprietorship (eenmanszaak) trading as FreightParse, registered with the Netherlands Chamber of Commerce (KVK) under number 42184908, Mathenesserweg 122B01, Rotterdam, the Netherlands, danil@freightparse.com (we or us).

C1. What this Addendum is.

• It applies only to a Customer Document that the Customer has read by Cloud Reading.
• The FreightParse Licence Terms (version 2.1, 14 October 2026) apply to Cloud Reading, as a service related to the Software (clause 2.1). For Cloud Reading, this Addendum amends clauses 10.1 and 10.3 and Annex 1 (A1.5, A1.6, A1.9 and A1.11) of the Licence Terms, as set out below.
• Everything else in the Licence Terms applies unchanged. That includes the Software that runs on the Customer's PCs, which still sends nothing to us.
• The Data Processing Agreement for FreightParse Cloud Reading (the DPA), signed with this Addendum, applies to Cloud Reading. Annex 1 of the Licence Terms applies to Cloud Reading as amended here, and the DPA prevails over both where they differ.

C2. The service. Cloud Reading works as follows:

• The Customer sends a document (PDF) in one of two ways: it uploads it through the FreightParse web page with its own access link, or it e-mails it to docs@freightparse.com, an address of our mailbox danil@freightparse.com. We may confirm other channels in writing.
• We save a document that arrives by e-mail on our computer, and submit it from there to the same service. Transport documents (bills of lading, air waybills, CMRs and transit documents) are read on our computer by our own software and are not sent to Google.
• Our server passes the document, in the request, to Google's Gemini model on Vertex AI, in Google's EU multi-region, which returns the document's fields and goods lines. Each document is read twice, the second time as a check.
• Our code puts the figures into one form, checks any country of origin given for all goods against the document's text, and compares the two readings.
• The Customer receives the goods lines, an import file for its declaration software, a list of the mandatory data that was not read, and the values to check first.
• The result of a document sent by e-mail goes back without a person at FreightParse checking it. The Customer checks it, helped by the page and printed text given for every value and the values marked to check. A document the service cannot read is held and answered by a person.

C3. Instruction per document.

• Upload: each upload with Cloud Reading selected is the Customer's documented instruction (A1.3) to process that document in this way. Before each upload, the page states what is sent, to whom and where, and sends the document only after the Customer agrees.
• E-mail: each document that the Customer e-mails to us for reading, after signing this Addendum, is the Customer's documented instruction to read it with Cloud Reading, unless the e-mail says that the document must not be read by Cloud Reading. Such a document stays under Annex 1 of the Licence Terms and is not sent to Google.
• An e-mail that reaches docs@freightparse.com from a domain that has not accepted these terms is held unopened for at most 7 days; we fetch only its headers and the list of its attachments (their types, names and sizes), and, for an attachment of the size of one of the public sample invoices on freightparse.com/dms/, its bytes, only to compare their fingerprint (SHA-256) with the sample's, without reading it. If someone at that domain accepts these terms through the link we send in reply within that time, that acceptance is the Customer's documented instruction to read with Cloud Reading every document e-mailed from its domain in those 7 days, as if it had been e-mailed after the acceptance.
• The Customer sends only what is needed (clause 10.4).

C4. Retention.

• Upload: we keep no copy of the document or of the result after we have returned the result. Our software holds them in working memory while the request is handled and does not write them to a file. For an uploaded document, this replaces A1.9.
• E-mail: we delete the document, its copies on our computer, its result and the e-mails within 30 days after we return the result, or earlier at the Customer's request, as A1.9 and clause B.11.2 of the DPA provide. An e-mail held under C3 that is not followed by an acceptance is not read, and we delete it within 30 days after it arrived.
• Our logs record only the date and time, the status, the size, the number of pages, the time taken and the access key used, not the content or the file name.

C5. Sub-processors for Cloud Reading.

• Google, Vertex AI. In addition to A1.6, the Customer authorises Google, as the provider of Vertex AI on Google Cloud, as a sub-processor for Cloud Reading. This is the Google entity that provides Google Cloud to us under Google's terms; we name it on request. Google acts under the Google Cloud Platform Terms of Service (cloud.google.com/terms), with its Service Specific Terms, and the Cloud Data Processing Addendum (cloud.google.com/terms/data-processing-addendum).
  • Under those terms Google does not use the data to train its models.
  • Google's Gemini model reads the document in Google's EU multi-region. The data cache that Vertex AI keeps by default, in memory for up to 24 hours, is switched off for our project.
  • If Google's automatic abuse checks flag a request, Google may keep it for up to 90 days, in the EU, to monitor abuse. Google does not train its models on it.
• Google, Google Workspace. The provider of our business e-mail service under A1.6, which holds the e-mails of the e-mail route, is Google (Google Workspace).
• Contabo. Contabo GmbH (Germany) hosts our server, which is in Lauterbourg, France. It is a sub-processor for the time a document passes through that server.
• Security. For Cloud Reading, A1.5 is amended accordingly: a document read by Cloud Reading also passes through our server and Google's Vertex AI, as described here, and the measures in Annex 3 of the DPA apply.
• Changes.
  • We inform the Customer at least 30 days before we add or replace a sub-processor for Cloud Reading. Changes in Google's or Contabo's own sub-processors we pass on as soon as they notify us.
  • The Customer may object. It may then stop using Cloud Reading and keep using the Software locally, without any change to its fees for the Software.

C6. Transfers outside the EEA.

• For Cloud Reading, A1.11 is replaced by this clause and by clause B.8 of the DPA.
• Google reads the document in its EU multi-region, and any flagged request it keeps stays there (C5). Google's terms do not exclude other processing of the data outside the EEA by Google or its sub-processors. For any such transfer we rely on the transfer terms in Google's own data processing terms: for Vertex AI, those of the Cloud Data Processing Addendum.
• We do not transfer the data outside the EEA ourselves, except to return the result to a Customer established outside the EEA (clause B.8.3 of the DPA).
• For a Customer subject to the UK GDPR, clause B.8.4 of the DPA applies.

C7. The Customer's check.

• Clause 7 applies in full: the Customer checks every value against the documents before it lodges a declaration.
• The report that comes with each result lists first the values on which the two readings disagree, and the values that rest on a country of origin the document's text does not state.
• On the review screen of the web page, values read by the cloud model are marked as such.

C8. Availability.

• Cloud Reading is provided as it is, without a guaranteed availability or response time, including during a test.
• If it is unavailable, the Customer can key the data by hand or, if it has a Licence, use the Software locally.

C9. Accuracy and liability.

• Clauses 8 (warranty) and 9 (limitation of liability) apply to Cloud Reading.
• We do not warrant that Cloud Reading reads every value correctly or completely.

C10. Fees. Cloud Reading is free of charge, unless an Offer that the Customer has accepted in writing states a fee for it. Clause 6 applies to any such fee.

C11. Stopping.

• The Customer can stop using Cloud Reading at any time: by not selecting it on the web page, and by telling us in writing for documents it e-mails.
• No Customer Document is then sent to Google.
• We may end Cloud Reading for the Customer by written notice, for example at the end of a test.
• Ending Cloud Reading does not end the Licence for the Software.

C12. Precedence. For Cloud Reading, this Addendum prevails over clauses 10.1 and 10.3 and over Annex 1 where they differ. On the processing of personal data, the DPA prevails over this Addendum.

Signatures

Signed by the parties on the dates below.