LensLogic™

Trust & security

Plain answers to the questions you would ask.

Who built LensLogic, where it is hosted, what we will and will not do with your information, and how to reach a person. Written in plain words so anyone at the practice can read it.

Last reviewed October 5, 2026. If anything on this page stops being true, email kenzie@lenslogic.tech.

Who built it

An optician, from behind a counter.

LensLogic LLC is a privately owned Texas limited liability company. It is run by Kenzie Rogers, an ABO/NCLE-C certified optician who has worked in optical since 2017 and dispensed thousands of pairs of glasses on the floor. Every tool in the product exists because of a problem she met at the counter.

No venture capital, no outside investors, no board asking for growth-at-all-costs. That matters because it is why we can afford to never sell your data: our business model is the subscription, not your information.

What we hold, and what we do not

Not an EHR. No patient records.

LensLogic is a workflow tool for your staff. It is deliberately not an electronic health record and does not ask for patient names, dates of birth, member identification numbers, or any other patient-identifying information. The features that could touch a patient (Quote Builder, Kelle, the Rx read) are built around prescription values and benefit math, not identities.

What we do hold is the information you give us about your own business: your practice name, your prices, your vision-plan templates, your frame board, your playbook, your sales data if you upload it, your saved quotes, your redo log, and your team logins. That data belongs to your practice. We do not sell it, we do not share it with anyone outside the service providers listed in our Privacy Policy, and we do not use it to train AI.

Where it is stored

In the United States, on infrastructure built for it.

The application is hosted on Vercel. The database is Prisma Postgres. Email delivery goes through Resend. Billing, when you subscribe, goes through Stripe. Your card details never touch our servers; they go directly to Stripe.

The AI features in Kelle, the prescription tools, and the optional benefit-card scan send the specific values involved to Anthropic's Claude API for the purpose of generating that response. Those calls do not include patient identifiers and are not retained in our database.

We rely on these providers' own security practices rather than claiming our own, because that is honest. Every one of them is a mainstream US provider used by businesses that handle more sensitive data than optical settings.

How it is protected

Encrypted end to end, with a short list of who has access.

Every page of LensLogic is served over HTTPS. Vercel enforces TLS at the edge and redirects any plain HTTP request to the encrypted equivalent, so your session, your sales data and anything you upload travel to our servers encrypted in transit.

The database is Prisma Postgres. The connection between the application and the database is encrypted, and the stored data is encrypted at rest on disk by the provider.

Your password is never stored. The signup form hashes it with scrypt (Node's built-in password hash, with a per-password salt) before it reaches the database, so even we cannot read it. A sign-in session is a signed cookie, not a copy of your password, and signing out invalidates it.

On the LensLogic side, the founder (Kenzie Rogers) is the only person with access to the production database and the Vercel account that runs the application. Operational tasks happen through those providers' own dashboards, which require her login. There is no shared account and no third-party support team with blanket read access.

What we will not do

A short list, written down.

We will not sell your data, to anyone, for any reason.

We will not use your sales data, playbook, saved quotes, or any other practice information to train AI models.

We will not place third-party advertising pixels on the application, and we do not use Google Analytics or similar tracking tools inside the signed-in product.

We will not claim HIPAA compliance. LensLogic is not designed to hold protected health information, and claiming a compliance posture we have not been audited against would be the wrong kind of promise. Instead, we are built not to need it: no patient records, no patient identifiers.

We will not add features that make the product do things your patients would not want it to do with their information.

If you decide to leave

Cancel in two clicks, no hostage data.

A free trial does not take a credit card. If you decide not to subscribe, your access pauses when the trial ends and the practice data stays available if you come back later.

If you cancel a paid subscription, you can export your saved quotes, your playbook, your frame board and your redo log before access ends. Your data is yours. We will not hold it to get you to pay again.

If something is wrong

Email a person.

The founder reads every email that comes in to kenzie@lenslogic.tech. For a privacy or security question, support@lenslogic.tech also reaches the same inbox. There is no ticket queue to get through.

If you suspect something is wrong with the application, your account, or your data, say so and we will treat it as the first thing we are doing today. Security researchers can also find our disclosure contacts in the published security.txt file at /.well-known/security.txt.

A note from Kenzie

A small company does not get credit for its name. It gets credit for what it says in plain words and whether that stays true after you sign up. If anything on this page stops being true, or you find something that is, I want to hear about it. You can email me directly at kenzie@lenslogic.tech.

Trust & security · LensLogic