Privacy

What this website does with information, described plainly, and what the product does with a practice’s records.

Last updated 31 July 2026

This website

The site is a marketing site. It has no accounts and no login. Two things on it send anything anywhere, both described below and both only when you press their button: the contact form, and the updates signup at the foot of the home page. Nothing else you do here is recorded. Where a subscribe button is shown it sends you to Stripe’s own checkout, on Stripe’s domain — this site never handles a payment or sees a card.

What we store on your device

One thing: your light or dark theme choice, saved in your browser's local storage under nexometry-theme. It never leaves your device and we cannot read it. Clearing your browser storage removes it.

The site sets no cookies. It runs no advertising scripts, tracking pixels, session replay, or visitor profiling. When operational monitoring is enabled, the site sends page-category performance measurements and fixed error categories to Nexometry. It does not send page text, form values, full URLs, query strings, error messages, or contact details.

What leaves your browser

Two third parties, and only one of them on an ordinary visit. Typefaces are loaded from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). Google receives the request and therefore your IP address, as it does for any site using their font service. We receive nothing from it. Everything else on the page — icons, styles, the product demo — is served from this site.

Nothing else leaves your browser on an ordinary visit. The two exceptions are deliberate and are yours to trigger: submitting the contact form, or the updates signup, sends what you typed to our own server, never to a third party. Both are described in full below.

The contact form

The form on the contact page is sent to our own server when you press Send enquiry. What we receive is what you typed: your name, your practice, your email address, the topic you picked and your message. We also record the network address the request came from, which is a routine part of receiving one and is what lets us block abuse. It is stored so we can answer you, and it reaches the sales team by email as well.

Nothing is sent while you are typing, and nothing is sent if you never press the button. If your enquiry cannot get through — our end being down, or too many attempts in a short spell — the page offers you a pre-filled draft in your own mail application instead. That path transmits nothing from the page: it hands the text to your mail app and stops, and it only sends when you press send there. The handover form on the welcome page you land on after paying still works that way for everything — it is a mail draft, not a submission.

The updates list

The signup at the foot of the home page is sent to our own server when you press Keep me posted. What we receive is the email address you typed and nothing else — no name, no practice — plus the network address the request came from, for the same reason as the contact form: it is part of receiving one, and it is what lets us block abuse. It is stored to send you the updates the form describes, and for nothing else. We do not sell or share the list, and it does not reach any third party.

Alongside your address we store a random code of our own — the one that goes in the unsubscribe link, and the only thing that link carries. It identifies your entry on this list and nothing else: it is not a password, it unlocks nothing, and it cannot be used to read anything back. When you unsubscribe we keep the date you did, so we can answer for it later if you ever ask why mail stopped or did not.

Two things worth stating plainly, because they are unusual. Every update we send carries an unsubscribe link of its own, which opens a page on this site with a single button on it — the page does nothing until you press it, deliberately, because mail scanners and preview tools open links without a person being involved. And an address already on the list is accepted again without telling you so; that is on purpose, because answering otherwise would tell anyone who asked whether a given address had subscribed. The unsubscribe page answers the same way for the same reason: it confirms, whatever the link turns out to point at. If you would rather not use it, or you have no link to hand, write to hello@nexometry.com and we take you off by hand.

The product demo

The interactive demo in the page header is a mockup. The names, prescriptions, orders and figures in it are invented. It is not connected to any system and sends nothing anywhere.

The Nexometry product

Nexometry is practice-management software that will hold patient records, prescriptions and commercial data. That is a serious responsibility and it deserves precise commitments rather than reassuring language. Below is what is built today and what is not — stated separately, because the difference is the part that matters to you.

What is in place

Each of these is something a buyer's own IT reviewer can ask us to demonstrate.

• Access rules are enforced in the database, not only in the application. Records carry row-level security policies, so a mistake in the interface cannot return rows a user is not entitled to — the check does not depend on the screen asking for it.
• Records are scoped to a practice, and to a branch within it. A user's reach is bounded by the practice they belong to and the branch they work at.
• Sign-in requires a second factor from an authenticator app.
• A sign-in from an unfamiliar location is verified by email before it is allowed. Password resets go through email confirmation for the same reason.
• NRIC numbers are masked for every role. No user of the system sees a full NRIC — not administrators, not practice owners.
• Traffic is encrypted in transit between your browser and the service.

What is not in place

These are gaps, described as gaps. We would rather you knew now than found out later.

• Backups are not yet in place, and no restore has been tested.
• Deletion on request is not yet implemented. Under the PDPA that is an expectation, not an optional feature.
• We are not claiming anything about encryption at rest. Nexometry runs on self-managed infrastructure, so this is our responsibility rather than a hosting provider's default, and we have not verified or documented it. When we have, this page will say so precisely.

The first two are commitments, not intentions, and they are sequenced ahead of any risk. Subscribing puts no patient data anywhere. Migration is a separate step we run with you afterwards, and it does not begin until backups, a tested restore and deletion on request are in place. If you are migrating and they are not yet done, we will tell you so rather than start.

This page also does not yet tell you where data will be hosted, how long records are kept, who our sub-processors are, or who on our side can access a practice's records. We would rather leave those blank than publish a claim we have not verified — a privacy policy you cannot rely on is worse than an honest gap.

These will be documented, and reviewed by someone qualified to review them, before any real patient data is entered. If you are evaluating Nexometry and need these answers now, ask us directly and we will tell you exactly where we have got to.

Subscriptions & payment

If you subscribe

Payment is taken by Stripe, on Stripe’s own pages. Your card details go to Stripe and never to us — we receive the billing name, email and the fact of a successful payment, which is what we need to contact you and to run the subscription. Stripe is the processor for that payment and keeps its own records under its own policy. The handover form on the page you land on afterwards opens a draft in your mail app and transmits nothing from the page — unlike the contact form, it is never submitted to us.

Your rights

Singapore's Personal Data Protection Act gives you rights over personal data organisations hold about you, including access and correction. For a visitor who has not subscribed, the only personal data we could hold is an email you chose to send us — through the contact form, the updates signup, or both. If you have subscribed, add the billing name and email described above. To ask what we have, or to have it deleted, write to hello@nexometry.com — noting that deletion on request is one of the gaps listed above, and that it applies to practice records rather than to a billing email we can remove by hand today.