LocumView is an open-source project (Apache-2.0) run by Michael Olszewski. This policy explains what personal information is collected through locumview.com, the LocumView demo service at login.locumview.com, and the LocumView backup tool that connects to Google Drive, and what is done with it. It is written to be short and specific. If anything here is unclear, email [email protected].
The short version
- The website does not use analytics, advertising trackers or third-party scripts, and it does not sell or share personal information.
- If you contact us, we use what you send only to reply to you.
- The demo service keeps the account and session information needed to run and secure it.
- The backup tool only ever sees files it created itself in its owner's Google Drive.
1. The website (locumview.com)
What we collect. The website itself collects almost nothing:
- Contact requests. The contact form asks for your name, organization, role (optional), work email and what you are interested in. When you submit it, your own email program opens with a message addressed to [email protected]. Nothing is stored by the website; we receive what you choose to send by email. Mail to that address is forwarded to our inbox by Cloudflare Email Routing.
- One preference cookie. If you switch between the US and EU versions of the site, a cookie named
lv_regionremembers your choice for up to 12 months. It contains only "us" or "eu" and is not used for tracking. - Technical data handled by our hosting provider. The site is delivered through Cloudflare. Like any web host, Cloudflare processes your IP address and request details to deliver pages, protect the site from abuse and report errors. See Cloudflare's privacy policy.
What we do not do. No analytics, no advertising or social-media trackers, no fingerprinting, no sale or sharing of personal information, and no use of contact requests for marketing lists.
External links. Pages link to the LocumView source code on GitLab and to a LinkedIn profile. Those sites have their own privacy policies.
2. The demo service (login.locumview.com)
The demo service lets invited people try LocumView desktops. It uses accounts in LocumView's own identity system (Keycloak). Named accounts use multi-factor authentication; the shared guest account uses a password only.
- What we keep: your account name and email, sign-in and session records (for example times, the IP address you connected from and which desktop you used), and security logs.
- Why: to run the service, keep it secure, investigate misuse and fix problems.
- Your desktop session: demo desktops are for evaluation with synthetic or public data only. Do not enter real patient data or other sensitive personal data.
- How long: the shared guest password is rotated after each evaluation, and named accounts are removed on request. Logs are kept for up to 90 days unless needed longer to investigate a security incident.
3. The LocumView backup tool and Google user data
LocumView's backup tool is a private tool that stores encrypted backups of its owner's own systems in the owner's Google Drive. It is not offered to the public.
- Access requested: the Google Drive
drive.filepermission, which lets the tool see and manage only the files it has created itself. It cannot see, read or change any other file in the Drive. - How the data is used: only to create, read, list, update and delete those backup files. Backups are encrypted before they leave the owner's systems, so their contents are not readable in Google Drive.
- Sharing: Google user data is not shared, sold or transferred to anyone, and is not used for advertising or to train AI models.
- Storage and security: the access token is stored as a restricted credential on systems the owner controls, and is never committed to source code.
- Revoking access: the owner can remove the tool's access at any time at myaccount.google.com/permissions.
Limited Use. LocumView's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. How long we keep information
- Contact emails: as long as needed to handle your request and any follow-up, then deleted, normally within 24 months.
- Demo service: as described in section 2.
- Backup tool: backups follow a fixed retention schedule (daily, weekly and monthly copies, kept for at most six months) and are then deleted.
5. Your choices and rights
You can ask what information we hold about you, ask us to correct or delete it, or ask us to stop contacting you, by emailing [email protected]. We will respond within 30 days. If you live in the European Union, the European Economic Area or the United Kingdom, see the EU version of this policy for the rights the GDPR gives you.
6. Children
LocumView is a professional tool. It is not directed at children under 16, and we do not knowingly collect their personal information.
7. Security
Access to the systems that hold personal information is limited to the project owner and protected by strong authentication (access by the owner uses multi-factor authentication). No system is perfectly secure; if we learn of a breach affecting your information, we will notify you as the law requires.
8. Changes
If this policy changes, the new version will be posted here with a new effective date. Material changes will be highlighted on this page.
9. Contact
Michael Olszewski, LocumView. Email: [email protected].