Plain language, no legalese. Here is exactly what GLP1Safe does and does not do with data.
GLP1Safe does not store any patient-identifiable data. No names, dates of birth, medical record numbers, IP addresses, or device identifiers. No accounts are required. The tool is designed under HIPAA Safe Harbor (Section 164.514(b)(2)).
Nothing is currently stored. GLP1Safe does not retain any data you enter. In the future, we may offer an optional, de-identified clinician survey on switching outcomes — switch direction (drug A to drug B), reason for switch, dose mapping, and a 4-week outcome rating. If introduced, it will be strictly opt-in via a consent checkbox, will contain zero patient identifiers, will not be linkable to any individual patient, and will never be required to use any module.
Clinical inputs (age, BMI, medications, dose selections) are sent to a secure calculation service, processed, and returned in real time. No inputs are logged, cached, or retained after the response is delivered. The calculation service exists solely to protect proprietary clinical logic; it does not store data.
GLP1Safe does not collect, store, or transmit any patient-identifiable data. Specifically, GLP1Safe does not collect:
No accounts are required to use GLP1Safe. The tool is designed to comply with HIPAA Safe Harbor de-identification standards (45 CFR Section 164.514(b)(2)).
When you use GLP1Safe, the clinical parameters you enter (such as dose values, weight, medication selections, and time-since-last-dose) are sent to our server for processing and returned immediately as a calculated result. These parameters are de-identified, contain no patient identifiers, and are not stored on any server after the response is returned.
All user-entered data is cleared when you leave the page. No clinical parameters persist beyond your active session.
The tool does not log, record, or retain any input/output pairs from individual calculations.
GLP1Safe uses sessionStorage (not cookies) to remember whether you have completed the attestation gate during your current browser session. This data:
GLP1Safe does not use tracking cookies, analytics cookies, advertising cookies, or any third-party cookie-based tracking.
GLP1Safe uses the following third-party services:
GLP1Safe does not integrate with, or transmit data to, any advertising networks, analytics platforms, social media trackers, or data brokers.
If GLP1Safe introduces any new data collection features (such as the voluntary, de-identified switching outcomes registry described in the Terms of Service), this Privacy Policy will be updated before the feature is activated. The "Last Updated" date at the top of this document will reflect the most recent revision.
Material changes to data practices will be communicated through an updated notice on the GLP1Safe website.
Because GLP1Safe’s Quick Guide collects individualized health-related responses (users answer questions about conditions, contraindications, and medications), GLP1Safe is subject to the FTC Health Breach Notification Rule. In the event of a breach of security involving individually identifiable health information, MetaboLoop will comply with applicable notification requirements under 16 CFR Part 318.
GLP1Safe’s architecture is designed to minimize breach risk: no individually identifiable health information is stored on any server, and all user-entered data is cleared when the session ends.
For questions about this Privacy Policy, contact:
Email: contact@glp1safe.app
Website: glp1safe.app