Appendix E Privacy ← Back to the findings

Where your data can and cannot go, item by item.

A folder ajar: cream paper showing inside, a green tab on the cover: nothing leaves it.

Here is where your data can reach and where it cannot. The first sections cover the tools you run yourself: the tests that keep the network shut, the folder that never enters a repository, the scrubbing on what travels, and each mechanism's limit. Each limit listed there is one the source itself states. The sections after them cover what reaches us: who we are, what we hold about clients, site visitors and people we write to first, why, for how long, who handles it for us, and how to use your rights.

No telemetry, and a test enforces it

Telemetry is code that reports usage to a vendor. Searching the sources for each telemetry pattern returns exactly one hit, the comment of the test that forbids them. That test goes through each source file and requires each network destination to be local or on an allow‑list of three entries. The three entries are the local model host, the public benchmark download, and the OCR language files that npm run tessdata -- --prime fetches once; none of the three runs during a measurement. A test enforces this, so it does not depend on a policy.

This test has a stated limit. It finds calls by pattern, so code built another way to send data out would escape this test. That is why the behavioral check below watches the running process and reads no source text.

Verify the allow-list test

The suite fails if any source file gains a network destination outside the list of three entries.

run it yourself
npm testfails on any new outbound destination

Where it livessrc/crusetra.test.ts:1066 · src/crusetra.test.ts:1094

Where your measurements live and stay

Each measurement on your data lands in a folder that git ignores, on purpose. The code spells this out in as many words, so no measurement can travel into a repository. The detailed attempt journals, which do hold extracted values, live under that same folder. For client cases they exist only on an explicit flag, and by default there is no journal. The tool also writes exactly one local marker, the date of its own first use, in a file you can read (~/.crusetra/premiere-utilisation.json; an earlier date under ~/.cascade, the former name, still counts). The thirty‑day evaluation clause reads that date to tell you where you stand. That file holds one labeled date, plus the former file's path when the date was carried over from it, and it is never transmitted.

A journal header records the CPU model, the platform and the load. The hostname, username and path never enter it.

What travels is scrubbed first

The only network record kept under version control is the egress observation, which lists what the measuring process connected to. Each path argument becomes a placeholder before that file is written, and the committed file shows it: the observed command reads --cases=<file>. Its answer, over 21 samples of one pass (one full measurement run), is no connection observed for the whole pass. The same file records its own limit, that sampling gives a lower bound and no kernel capture.

The local screen, served by npm start, puts its error messages through path‑scrubbing at both return points, and a dedicated test checks this. The source also names one assumed weakness: the scrubbed roots come from a fixed list, so a path under an unusual root would pass through.

Watch a measurement pass

The egress command watches the measuring process and publishes the hosts seen, its answer and its own limit.

run it yourself
npm run egresssamples connections during a pass, with the record committed and paths scrubbed

Where it livessrc/egress.ts:343 · egress.json:12

The screen stays on this machine

The local screen listens on this machine's loopback only, an address only this machine reaches. A test holds this in place. It sweeps each server in the repository and keeps no list of names. Any write request carrying a foreign origin, an origin other than the screen's own, is refused before it reaches the handler. The server keeps no request log at all. Its only console output is the startup line and port errors, so no body, no address and no access is written anywhere.

Verify the screen

Start it and probe it. It listens on loopback only and refuses writes from a foreign origin.

run it yourself
npm startserves on localhost only, no request log

Where it livessrc/server.ts:728 · src/server.ts:530

Two production dependencies, swept for telemetry too

The tool has two production dependencies, the model runtime library and tesseract.js, the OCR engine. A telemetry sweep across each of their installed packages finds hits only in a development tool's editor protocol, and none in the production path. Each library has one remote destination it could reach: the public weights host for the runtime, used once on first run, and the public language-file host for tesseract.js, which the tool never lets it reach: the engine is pointed at the folder npm run tessdata -- --prime filled once, with its cache off, and the egress check holds that no connection opens while it reads. The offline flag turns even that off by telling the library never to reach the network. The library disobeys for one public metadata file on each load. The tool now names that file and does not let it pass in silence. Sweeping the dependencies themselves found one more address. A package inside the runtime embeds a CDN host for WebAssembly (WASM) artifacts, on a code path this tool never exercises. It is named here because the allow‑list in our sources cannot see inside a dependency.

One limit is stated as well. Native binaries cannot be read by a text sweep, so a text search (grep) cannot verify that corner. The lower bound for that corner is the behavioral egress record above.

The report you receive

The measured report is written beside your CSV, and none of it goes into the tool's folders. It contains rates, confidence intervals (the range a true rate is likely to sit in) and the questions asked. The values extracted from your documents never enter it. It closes with the sentence it earns: measured on this machine, nothing left it.

A second file is written beside it, the sealed record (hashed, then frozen: its content hash is checked before a figure is shown), and it is the one file the extraction cost audit asks you to send us. It holds counts, a right, wrong or blank verdict per case and field, your file's name and its SHA-256 hash, and the prices and volume you declared. A declared price can be under a vendor contract: replace it with a list price before sending if it is. No document and no value read from one is in that file.

Who is responsible, and how to reach us

HS Industries LLC, a Wyoming limited liability company (file no. 2026-002073840), decides why and how the personal data described below is used: it is the controller. Its postal address is 1550 Wilson Blvd, Ste 700 PMB 599, Arlington, VA 22209, USA. For any question or request about your data, write to contact@crusetra.com.

The company is run from Athens, Greece. So the EU General Data Protection Regulation (GDPR) and the Greek data protection law (Law 4624/2019) apply to everything this page describes, wherever you are. Our lead supervisory authority is the Hellenic Data Protection Authority (dpa.gr). Because the company is established in the EU, it has no separate EU representative. It has no UK representative: it does not need one for what it does in the United Kingdom today, and it will name one here before that changes.

What you send us for a report

Two services run on our side, and for them you do send us something. For a Screening report, you email a list of company and vessel names, with the IMO number of a vessel when you have it: a CSV, a spreadsheet, or names in the body of the mail. For a Routing free test, you email the measured record the tool wrote beside your CSV, the file ending in -measured.json: counts, a right, wrong or blank verdict per case and field, your file's name and its SHA-256 hash, and the prices and volume you declared. In both cases nothing else is asked for, and no document of yours is.

Whose data it is. If your list names people (a sole trader, a ship owner, a contact), we screen it for you and on your instructions only: you are the controller of that list and we are your processor.

Why, and on what basis. We use what you send, and your email address, only to produce the report or test you asked for. For your own contact details the basis is the contract, or the steps you asked us to take before one (GDPR, Art. 6(1)(b)).

How long. Once the report is sent, your file and the mails that carried it go to the trash and are deleted within 30 days of going there. A weekly re-screen subscriber's list is kept for the re-screen and goes the same way when the paid period ends.

When you buy

When you pay by card, the payment runs through Stripe, which processes it for HS Industries LLC. The checkout asks for your email, your company name and your billing address, and a tax ID if you want it on the invoice. Stripe keeps your card details: we see the card brand and its last four digits, never the full number. When you pay an invoice by bank transfer, our bank, Mercury, sees the payer's name and account. We keep your name, email, company, billing address, invoices, payments and any signed engagement letter.

Sanctions check of every buyer. HS Industries LLC is a US company, and US sanctions law forbids it to provide a service to, or take a payment from, a person on a US sanctions list. So before we start an order we screen the buyer's company name, the payer's name and the billing country against the same public lists as our reports, and we keep a record of that check.

Why, and on what basis. To deliver what you bought and invoice you, under the contract (Art. 6(1)(b)); to keep our accounts and to check buyers against the sanctions lists, on our legitimate interest in meeting the US tax, accounting and sanctions rules that bind the company (Art. 6(1)(f)).

How long. Invoices, payment records and signed letters: as long as US tax and accounting rules require. The sanctions check of a buyer: 10 years, the period US sanctions rules set for transaction records. Other mails about an order go the same way as the files you send for a report.

Visiting this site

This site sets no cookies, runs no analytics or tracking, and no form on it sends us anything. It is static files served by GitHub Pages. Like any web host, GitHub receives your IP address and browser details when you load a page and keeps them in its own logs, under its own privacy statement; we do not see those logs. If you arrive through an older address of ours, Cloudflare handles the redirect and sees the same details. The basis is our legitimate interest in serving the site and keeping it secure (Art. 6(1)(f)). GitHub and Cloudflare keep those logs under their own rules.

If we wrote to you first

We write to people at companies that may need what we make: customs brokers, ocean freight forwarders and NVOCCs, payment and crypto firms, and companies that read receipts and invoices at volume. If you got a mail from us before you ever wrote to us, this is what we hold and why.

  • Who we are. HS Industries LLC, run from Athens, Greece; contact@crusetra.com.
  • Where we got your address. From a public source: the company's entry in a public register (the US Customs and Border Protection list of permitted customs brokers, or the Federal Maritime Commission list of licensed ocean transportation intermediaries), or the company's own website. We buy no address lists and use no people‑search tools.
  • What we hold. Your work email address; your name and job title when the source gives them; your company's name, city and phone; the page where we found the address; one line on what the company does; our mails and your replies.
  • Why, and on what basis. To offer you a service that fits your work, on our legitimate interest in offering our services to businesses (Art. 6(1)(f)). We weighed it against yours: we write only to work addresses that a company or a public register published, about your job, three times at most (a first mail and two short follow‑ups), with no tracking pixel and no tracked link, and we stop when you ask. We do not write to addresses in the EU.
  • Who sees it. Only us and the providers listed under “Who handles it for us”.
  • How long. 12 months after our last mail if you do not reply. If you reply and do not buy from us, 12 months after our last exchange. If you ask us to stop, we keep only your address, on a stop list, so that we never write to it again. For an address in Canada, we keep the record of where it was published, and our mails, for 3 years after our last mail, to prove the basis of our mail under Canadian law.
  • Your right to object. You can object to these mails, and to our keeping your details, at any time and without giving a reason. Reply “stop” to any of our mails or write to contact@crusetra.com. We stop the same day we read it, and within 5 business days at the latest.
If you are named on a sanctions list

Our screening compares the names our clients send with the official public sanctions lists: the US Treasury's OFAC lists, the US Consolidated Screening List, the UN Security Council list, the EU financial sanctions list and the EU list of designated vessels, the UK Sanctions List, and the lists of Australia, Canada and New Zealand. Writing to each person on those lists is not possible, so this section is how we inform them.

  • Where the data comes from. From those lists, as their publishers publish them, and, for a few entries the EU list does not carry yet, from the Official Journal of the European Union.
  • What we keep. We download each list whole, as its publisher publishes it, and keep that file. So our copy holds what the publisher prints about a person, which can include aliases, date and place of birth, addresses, nationality, identity numbers and the reasons for listing. For the few Official Journal entries we copy by hand, we keep the name, the alias in the original script, the date of birth and the entry number. Our screening compares names, aliases and vessel IMO numbers only; it does not compare or use dates of birth, addresses or other identifiers. From an entry it reads the name and aliases, the list, the program, the entry's reference, the date of listing as the list writes it, and the parties the list itself names for the entry, such as a vessel's owner.
  • Why, and on what basis. So that our clients can check whether they are about to deal with a listed person, which the sanctions laws that bind them forbid. The basis is the legitimate interest of our clients and ours in meeting those laws (Art. 6(1)(f)). A match we report is a candidate for the client to check, never a decision.
  • Who sees it. A list entry appears in a report only when a client sent a name close to it, and only that client receives the report. The report shows the list, the program, the entry's reference, the name matched, the type of entry, the IMO number of a vessel, the date of listing and the parties the list names, and no date of birth, address or identity number. We do not publish list entries about people on this site.
  • How long. As long as the publisher lists the person. Our working copy of each list is replaced when the publisher updates it, so an entry the publisher removed leaves it at the next update. We also keep an earlier dated copy of the lists, to compare what changed between two releases; a removed entry can stay in that copy until we delete it.
  • Your rights. You can ask what we hold about you, ask us to correct our copy where it differs from the publisher's, and object to our use of it. A listing itself can only be changed by its publisher, through the publisher's own procedure. Write to contact@crusetra.com.
Who handles it for us
  • Proton (Switzerland): our mailbox. Your mails, attached lists, and the invoices and letters we send.
  • Stripe (United States): card payments.
  • Mercury (United States): our bank, for payments by transfer.
  • GitHub (United States): hosts this site and our public code. No client or prospect list is ever put there.
  • Cloudflare (United States): our domain names, and the redirect from older addresses.
  • Apple iCloud (United States): a dated backup of our own working files. No client list, client record or signed letter is put there.
  • Anthropic (United States): a language model provider we use only through its API, under its Commercial Terms and the Data Processing Addendum they incorporate, and only when a step of the work needs a model to read personal data. The screening itself runs offline on our own machine.
  • Google Gmail (United States): an earlier mailbox that sent some first mails in September 2026 and receives the replies to them.
  • Zoho (EU service, zoho.eu): the mailbox of our earlier mail address, which sent first mails and receives the replies to them.

We sell no personal data. We disclose it to an authority only where the law requires it.

Transfers outside the EU

We work from Greece, and most of the providers above are outside the European Economic Area, so your data leaves it. Here is what each transfer rests on, as we checked it on 21 October 2026.

  • Stripe, GitHub, Google and Cloudflare are certified under the EU-U.S. Data Privacy Framework, which the European Commission found adequate (Decision (EU) 2023/1795). The list of certified companies is public at dataprivacyframework.gov.
  • Proton is in Switzerland, which the Commission recognizes as adequate.
  • Mercury, our US bank, receives the payer's name and account from the payer's bank and handles them as a bank, under its own privacy policy, which says it relies on standard contractual clauses for transfers from the EEA and the United Kingdom. Mercury is not on the Data Privacy Framework list, and we have no transfer contract of our own with it.
  • Anthropic is used only through its API, under its Commercial Terms. The Data Processing Addendum those terms incorporate contains the EU standard contractual clauses (Module Two, controller to processor), which cover that transfer. Anthropic is not on the Data Privacy Framework list.
  • Apple iCloud holds our backup under Apple's consumer terms, with no data processing agreement and no transfer safeguard of our own; that is why no client data goes there. Apple is not on the Data Privacy Framework list.
  • Zoho holds the mailbox of our earlier mail address on its EU service (zoho.eu). We have not confirmed whether Zoho moves that data outside the EEA, and Zoho is not on the Data Privacy Framework list.
Your rights

Under the GDPR, the Greek data protection law and, in the United Kingdom, the UK GDPR, you can ask us for a copy of what we hold about you, and ask us to correct it, delete it, limit its use, or send it to you in a portable form. You can object to any use based on our legitimate interest, and to direct marketing at any time, without giving a reason: we then stop. Write to contact@crusetra.com or to the postal address above. We answer within one month.

To complain about how we handle your data, write to contact@crusetra.com with the word Complaint in the subject: we acknowledge it within 30 days and tell you the outcome. You can also complain to a data protection authority at any time: our lead authority is the Hellenic Data Protection Authority (dpa.gr), Athens; you can also go to the authority of the EU country where you live or work, or, in the United Kingdom, to the Information Commission (ico.org.uk).

This page

Version 2026-10-23 (v4). This version corrects two lines under "Who handles it for us" and "Transfers outside the EU": Anthropic is used only through its API, under its Commercial Terms and Data Processing Addendum, and only when a model must read personal data; no client list, client record or signed letter is put in Apple iCloud.

Version 2026-10-21 (v3). This version says the company is run from Athens, Greece, and names its lead supervisory authority; it adds the notice for people named on sanctions lists, what each transfer outside the EU rests on, and how to complain to us; and it shortens the time to stop our mails to 5 business days.