Request a pilot

Request a 3DPainMap pilot.

Start with one clinic, course, or study. Tell us about your use case and we will follow up about fit, access, and next steps.

Security & privacy

Data & trust, agreed up front.

Access

Open preview — your work stays in your browser.

The workspace is open while the product is in preview: there is no account system and no sign-in. Nothing you draw or type is transmitted to or retained on our servers — it is written to this browser, on this device, and nowhere else. That also means it is not protected by us: anyone with access to this device and browser profile can open it, and clearing browsing data deletes it permanently. Governance for a real pilot is agreed with each partner in writing before sensitive data is involved.

Data handling

Sensitive information, handled responsibly.

Records derive from one finding-level model and export only what a pilot needs. De-identified or simulated data is used for demos and education, and governance specifics are agreed with each pilot partner up front rather than asserted as a blanket claim.

Reporting a problem

Found something? Send it straight to us.

If you find a vulnerability, a way to reach data you should not, or anything that looks like a privacy problem, write to security@3dpain.app with enough detail to reproduce it. We will acknowledge that we received it and tell you what we are doing about it. Please do not include real patient information in a report — a description, a screenshot with the content removed, or a simulated case is enough to act on, and we would rather not receive the alternative. We will not pursue anyone who reports something in good faith.

Ownership

Your records, in portable formats.

Pilot partners keep ownership of their records. The canonical JSON tier is a lossless, versioned source of truth, and a vendor-neutral FHIR R4 DocumentReference is available for handoff.

Is 3DPainMap HIPAA compliant?

We do not make a blanket compliance claim. 3DPainMap is designed for responsible handling of sensitive information, and we agree the specific data-governance and any required agreements with each pilot partner before sensitive data is involved.

Does it use AI to interpret pain?

No. 3DPainMap captures what the patient reports and measures the painted surface. The derived metrics are deterministic calculations over that surface — there is no automated interpretation or prediction.

Are the measurements validated?

Not yet. The pipeline is built for validation — reliability, construct validity, and responsiveness studies are scoped on the roadmap — but we present metrics as derived symptom-burden measures, not validated clinical endpoints.

Where is my data stored, and who can see it?

During the preview, everything you create in the workspace stays in this browser on this device. There is no account system and no server-side record store, so it does not reach us and does not sync anywhere — but it is also unprotected: anyone who can open this browser profile can open your work, and clearing browsing data, private windows, or uninstalling the app deletes it permanently with no backup. The pilot-interest form is separate: it stores what you type in it so we can reply to you. A pilot agreement sets out storage, access, and retention before any patient data is handled.