Security and data
Security and data: what we store, where, and who sees it
In short, for the laboratory’s security team: Kosandis holds no patient data, organisations are isolated, servers are in Ukraine, backups are daily and encrypted.
Names, codes and dates in the illustration are an example.
What we store, and what we do not
Where the data is
- Servers are in Ukraine.
- Encrypted backups are made daily.
- Each organisation’s data is isolated: a staff member sees only their own organisation.
Sign-in and access
- Sign-in is by work email: a one-time code is sent to the mailbox. The code emails are sent by Brevo — a data processor in the EU.
- Roles and effective permissions are assigned by the organisation itself. On a shared phone the user is switched with a PIN.
- Access to an organisation opens after registration and manual approval by the operator following a conversation — there are no random organisations in the system.
- DNS and proxy — Cloudflare, also a data processor.
Action log and export
All actions on packs are recorded with author and time; entries are never edited or deleted. The organisation can get an export of its data in an open format at any time. Exit terms are in the contract.
We hold no security certifications (ISO 27001, SOC 2) yet — we are at the stage of the first pilots. Details are in the privacy policy and the terms of use.
Frequently asked questions
Does Kosandis hold any patient data?
No. Only reagents, locations and actions on them. There is no field in the system for patient data or test results.
Who can see our organisation’s data?
Your organisation’s staff — under the roles you assign. The service operator has technical access for support and backups; its limits are described in the contract and the privacy policy.
Can we take our data out?
Yes. There is an export of the organisation’s data in an open format; exit terms are in the contract.
Where is the data physically stored?
On servers in Ukraine. Encrypted backups are made daily.
Other topics
- Reagent inventory for laboratoriesThe unit of record is the pack, not the product name: code, lot, expiry, location, log.
- Reagent expiry trackingManufacturer’s expiry and opening date on one card; “≤ 7 days” and “Expired” switch on their own.
- Lot records and verificationA new lot stays in quarantine until verified; the record says who and when; a recall shows every pack.
- QR labels and the phone as a remoteThermal print 40×25 and 50×50 mm, camera scanning, one or two taps per action, works offline.
- Reagent records before an auditReceipt, lot verification, opening date, write-off — with author and time, in one log.
- Kosandis and the LISThe LIS keeps patients and results, Kosandis keeps reagents. Alongside, not instead; integrations are planned.
Write to us — we’ll show it on your own example.
We are looking for 3–5 laboratories for a paid pilot of 60–90 days. We start with a short conversation about how you track reagents today.
After you apply, we will get in touch to agree the pilot terms; access opens once the application is approved.