1. Who is responsible
PE Hazem Saker, a registered sole trader in Kyivska Oblast, Ukraine, is the controller of personal data processed through Laytimetech. Contact: support@laytimetech.com
2. What we collect
Your account: name, company name, email address, and your password stored only as an irreversible cryptographic hash — we never see or store the password itself.
Subscription records: which plan you are on, and the date it is paid until. Payments are handled by our bank's payment gateway — we never see or store your card details.
Statements you choose to save: when you press "Save to my statements" we store the extracted values and the result — vessel, ports, parties, dates, laytime terms, rates and figures. If you do not save a statement, none of it is kept.
Voyages you choose to keep: when you press "Keep as a voyage" we store the voyage as you built it — the vessel and her particulars, the values read from each document (its name, its kind, and the terms and facts extracted from it), the laytime terms on each tab, the statements produced, and what you record about the claim: its status, the agreed figure and any notes you add. This is what lets a voyage be reopened months later without uploading the documents again. The documents themselves are still never stored — only the values read out of them. If you do not keep a voyage, none of it is kept.
Transcripts you ask for: on the Team plan you can have a document typed out in full. We keep that transcript — the text of the document, page by page — against your account, so that you can download it again without paying for a second read. The file it was made from is still not kept. Deleting the document from My documents deletes its transcript with it, and so does deleting your account.
Technical records: we keep short-lived server logs for security and fault diagnosis.
3. What we do not collect
We do not store the documents you upload. They are held in memory while being read and then discarded. They are never written to disk, to our database, or to any backup.
So that the same file is never read — or charged — twice, what was read from a document is held against your account and reused if you upload the identical file again. The file is not kept; what was read from it is — including, where you have asked for one, the full typed-out text.
We do not use tracking cookies, advertising cookies or third-party analytics. We use one essential cookie to keep you signed in.
The mobile apps. The Laytimetech app is the same service in a window of its own. It contains no advertising code and no third-party analytics, and it reads no device identifier — not the advertising ID, not the Android ID. It asks for three things: access to the internet; the fingerprint or face unlock you choose to switch on; and, on Android, Google Play’s billing permission, which lets the store take a payment for a voyage pack and tells us nothing about you. A laytime statement you export from the app is written to your own device and is not copied anywhere.
How we count use of the free calculator. So that we know whether the free calculator is being used at all, we record that it was opened, that a calculation was performed, that a statement was exported as a PDF or as a spreadsheet, and that someone signed in to save one. Each record is a date, one of those words, and a random identifier your browser generates for itself and keeps in its own storage. That identifier is not a person and is not linked to your account — the same person on a phone and on a laptop is two of them. Clearing your browser storage erases it.
Each record also carries two single words, so that we can tell whether our guides and posts reach anybody: roughly where the visit came from — one of direct, search, LinkedIn, Facebook, Instagram, YouTube or other — and which of our own pages it began on, such as home or guide/what-is-laytime. The address of the page you came from is never sent to us. Your browser works out which of those seven words applies and discards the address; the word is all that is transmitted and all that is stored. There is no referring URL, no search term, no campaign tag and no link between one visit and the next.
We record no IP address, no location, no device information and nothing at all about your voyage: not the vessel, not the ports, not the terms, not any figure. This is our own counting, on our own servers; nothing is sent to anyone else.
4. Why we process it
- To provide the Service and let you reopen your saved statements and voyages — performance of our contract with you
- To operate accounts, billing and support — performance of our contract
- To keep the Service secure and diagnose faults — our legitimate interest
- To send service emails such as verification and account notices — performance of our contract
We do not send marketing email and do not sell or rent your data.
5. Who else is involved
We use a small number of providers, each only for what is necessary:
| Provider | Purpose | Data involved |
|---|---|---|
| Anthropic | reading uploaded documents | document contents, transiently; not used for training |
| Railway | hosting and database | account and saved statements |
| Resend | sending service emails | name, email address |
| Raiffeisen Bank | processing subscription payments | handled by the bank; we never see or store your card details |
We do not share your data with anyone else except where the law requires it.
6. Where it is held
Our servers are in the European Union. Document reading is performed by Anthropic, which may process content outside the EU under appropriate safeguards.
7. How long we keep it
Saved statements, kept voyages and account data are kept until you delete them. Deleting your account removes your account, every saved statement, every kept voyage, every stored reading and every transcript permanently and immediately. Server logs are kept for a short period and then deleted.
8. Your rights
You may access, correct, export or delete your data. Export and deletion are both available directly in Settings — you do not need to ask us. You may also object to processing, ask us to restrict it, or complain to your data protection authority.
9. Security
Passwords are hashed. Sessions are protected and revocable. Traffic is encrypted in transit. No system is perfectly secure, but we do not retain the files you upload, which limits what could be exposed. We do retain what was read from them, including any transcript you have asked for.
10. Children
The Service is for commercial use and is not directed at anyone under 18.
11. Changes
We will notify material changes in the Service or by email.