Partner inquiry details
- Name
- Work email
- Company
- Role
- Interest area
- Asset or disease context
- Message
- Consent confirmation
- Hidden anti-spam honeypot value
Privacy
Privacy disclosures
This page explains what MedInsights collects through the partner form, how privacy-light analytics stays disabled without reviewed and approved configuration, how a display preference stays local to this browser, which processors are disabled or pending by default, and how privacy contact details come from deployment configuration.
Partner form
Data collected and why
MedInsights uses partner-form details to respond to partnership inquiries, route BD/licensing conversations, and maintain a consent-backed record of the request.
BD/licensing follow-up
MedInsights uses partner-form details to respond to partnership inquiries, route BD/licensing conversations, and maintain a consent-backed record of the request.
The hidden honeypot value is used only to identify automated spam-like submissions and is not intended for human visitors.
Analytics, local storage, and cookies
Privacy-light analytics uses approved configuration
Analytics is disabled by default, so the site does not emit visitor analytics, load a third-party analytics script, or set analytics cookies in the default build.
Analytics data categories
- Page views
- Partner CTA clicks
- Partner form starts
- Partner form submission outcomes
- Product detail opens
- Active motion variant
Cookies
The default site build sets no nonessential cookies. Cookie-consent complexity should be added only if a future approved processor or marketing stack requires nonessential cookies.
Functional theme storage
medinsights.theme: This local browser key is used only to remember a manual display preference.
It contains only "light" or "dark". System is the default and does not store a value.
The theme preference is never included in analytics events or sent to MedInsights.
A manual preference remains in this browser until System is selected or site data is cleared.
Processors
Processor status
Launch review note: Analytics and email providers remain off until the team approves the processor setup and deployment config.
Partner email delivery
Scaleway TEM in fr-par (recommended adapter)
No external email processor is active by default. The server-side adapter remains disabled unless approval status, EU hosting, DPA, retention, security-review evidence, destination inbox, sender identity, privacy contact, and provider credentials are configured outside source control.
Analytics
Plausible Cloud EU (recommended adapter)
Analytics provider is disabled.
Retention and contact
Retention basics and privacy contact
Personal data is retained only as long as needed for partnership follow-up, operational records, legal obligations, and documented processor-review requirements.
Partnership inquiries
Partner inquiries should be reviewed periodically and removed or anonymized when follow-up, audit, and legal needs no longer require identifiable details.
Analytics retention remains pending processor approval; no analytics retention clock starts while analytics is disabled.
Contact route
Launch review note: Add the public privacy contact before using this build outside QA or internal review.