Privacy Policy

2026-11-pa-v3 · Updated 18 November 2026

This Privacy Policy explains what information Pex Protocol collects, how it is used and protected, and the choices you have.

1. Who operates the Service

Pex Protocol is the operating name of the service described in this policy. It is not currently presented as a registered company. The identity of the legally responsible person or entity will be updated when established. For privacy requests, use corp@pexprotocol.com once the mailbox is operational.

This policy describes actual and intended data practices; it is not a claim of certification or of complete compliance with every applicable law. Panama's Law 81 of 2019 and its implementing framework may apply, including additional requirements for sensitive personal data and cross-border processing.

2. Information we collect

Account and contact information: name, date of birth, email address, required mobile number, optional WhatsApp number, password stored as a hash, account role, and account settings.

Profile information: goals, reason for using Pex, experience level, and any additional profile details you choose to enter, such as location, sex, height, weight, target weight, timezone, and preferences.

Health and protocol information: protocols, inventory, vials or lots, doses and administration history, check-ins, symptoms, body measurements, lab results, reference ranges, notes, and related records that you submit. These records may be sensitive health-related personal information.

Security and recovery information: session and authentication records, password-recovery requests, limited contact snapshots associated with recovery, identity-verification method/evidence categories, outcomes, administrator identity, timestamps, and hashed reset tokens. We do not request identity-document uploads for password recovery.

Operational information: minimal information needed to operate and secure the Service, including limited time-in-app information. The described application does not use advertising identifiers, advertising trackers, or analytics cookies. When public registration is open, the sign-up form runs a Cloudflare Turnstile bot-protection check, which causes a limited set of technical signals to be processed by Cloudflare (see Section 5). If browser push notifications are enabled in the future, notification preferences and push-subscription technical data may also be processed after the feature and policy are updated.

Clinic presentation requests: if you ask to receive our clinic presentation from the public homepage, we collect the professional contact details you submit — your name, clinic name, phone number, email address, and the language of the request. These details are used only to deliver and follow up on that presentation request; they are not used for marketing and are not linked to any patient or health record. They are stored in a table separate from accounts and health data, and the presentation file is delivered directly by Pex through a single-use, short-lived download link (no external email provider; see Sections 5 and 8).

3. Why we use information

We process information to provide and secure accounts; display and organize records; perform user-requested calculations and reminders; support account recovery; allow appropriately assigned Doctor or Clinic accounts to view and suggest information; support administrative functions; maintain security and audit trails; and respond to requests and legal obligations.

Health-related data is processed to deliver features that users choose to use, not to sell health profiles or target advertising. We do not sell personal information or share it with advertisers. Phone and WhatsApp numbers are not used for marketing or automated messaging without appropriate authorization. No automated email, SMS, or WhatsApp delivery is currently active.

The applicable legal basis—including any required express consent for sensitive information—must be confirmed for each processing purpose under relevant law. The app records versioned policy acknowledgment; that record does not, by itself, resolve every legal-basis question.

4. Who can access information

Users can access their own records. Doctor and Clinic accounts can access only information permitted by the platform and the relevant user assignments. Administrators may access information for authorized support and operations; health-record access is subject to recorded reasons and auditing. Historic Referrer accounts cannot access client protocols.

Access is controlled by account roles and server-side authorization, but no technical system can guarantee absolute security. We do not publish user health records or contact numbers on public profiles.

5. Hosting, service providers, and international processing

Data is held in a MySQL database on infrastructure used by Pex and its hosting provider. The application is self-hosted on third-party server infrastructure; the exact hosting region and legally relevant service-provider disclosures should be confirmed before final publication. Depending on server and support locations, information may be stored or processed outside Panama. Any applicable requirements for international transfers and processor arrangements must be assessed and met.

The platform does not send user data to advertising networks or to connected automated email/SMS/WhatsApp providers. Cloudflare is used as a service provider for bot protection on the public registration form, as described below. If other processors or communications providers are enabled, this policy will be updated to describe their purposes and data access.

Bot protection — Cloudflare Turnstile. When public account registration is open, the sign-up form uses Cloudflare Turnstile, a service of Cloudflare, Inc., to tell real people apart from automated bots and reduce fake or abusive sign-ups. According to Cloudflare's Turnstile Privacy Addendum, when the challenge runs Cloudflare processes a limited set of technical signals — your IP address, a TLS fingerprint, your browser's User-Agent, and the site key and its origin. Cloudflare states these signals are strictly necessary to detect and block bots and to improve the service, that they are not used to identify, profile, or target individuals, and that it cannot directly identify individuals from them. For running the challenge Cloudflare acts as our processor; for improving its own bot-detection capabilities it acts as an independent controller. Cloudflare is a global provider, so this processing may take place on infrastructure located outside Panama. The challenge is invoked only on the public registration form, and Pex does not intentionally submit the contents of your health, protocol, or account records to Turnstile for verification; the check operates on the technical signals described above. Depending on Cloudflare's configuration, Turnstile may use cookies or similar browser technologies to carry out the check (see Section 6); Cloudflare states it does not use them for advertising or cross-site tracking. More information is available in Cloudflare's Turnstile Privacy Addendum (cloudflare.com/turnstile-privacy-policy), Cloudflare's Privacy Policy (cloudflare.com/privacypolicy), and Cloudflare's Cookie Policy (cloudflare.com/cookie-policy).

6. Cookies, browser storage, and communications

The Service uses a necessary session cookie to maintain authentication. Production authentication cookies are designed to be secure and inaccessible to client-side scripts. Limited browser local storage is used for preferences such as language and theme. We do not use advertising or cross-site tracking cookies in the described implementation. When the Cloudflare Turnstile bot-protection check runs on the registration form, Cloudflare may use cookies or similar browser technologies to carry out the security check, depending on its configuration; these are not used for advertising or cross-site tracking. See Cloudflare's Cookie Policy (cloudflare.com/cookie-policy) and Section 5.

Contact information supplied at signup is not independently verified merely because it was entered. For account recovery, staff must use an independently trusted verification process; contact details alone are insufficient.

7. Security

The platform uses access controls, password hashing, protected session cookies, login rate limiting, and security auditing. Staff-only Professional Resources are intended for authorized viewing without exposing original documents to ordinary viewers. Database backups are maintained on the server; an encrypted off-site backup system has been proposed but is not currently activated.

We do not claim encryption at rest, a particular security certification, or perfect protection. If a suspected personal-data incident occurs, we will investigate and take action consistent with applicable notification obligations. Specific regulatory notification procedures and timelines require confirmation under Panamanian law.

8. Retention and account deletion

Active account information and records are generally kept while the account is active and the information is needed to provide the Service. Standard Users can delete their account from Account settings. The implemented deletion process removes account-linked records through database relationships, but certain independently maintained security or administrative audit records and operational backup copies may remain after deletion. Some historical records may be retained where legally necessary or proportionate for security and accountability.

Important limitation: The system does not yet have a fully approved, category-by-category retention schedule or automatic expiration for every audit category. We will not claim fixed deletion deadlines that have not been implemented. Requests for further deletion or clarification may be sent to corp@pexprotocol.com; we will review them in accordance with applicable obligations and technical constraints. Backup copies are not ordinarily edited record by record; restoration processes should respect previously completed deletions where feasible.

Clinic presentation requests are kept for up to 12 months from the date you submit them and are then deleted automatically by a scheduled process; the single-use link that delivers the presentation expires shortly after it is issued. These records hold professional contact details only, never health information.

9. Your privacy rights and choices

Subject to applicable law, you may request access to your personal data, correction of inaccurate information, deletion or cancellation, objection to certain processing, and portability where required. Within the application you can view or correct certain account information, export Labs & Monitoring records, and delete a standard User account. A complete export of every account record is not currently available as a self-service feature.

For requests not supported directly in the app, email corp@pexprotocol.com. We may need to verify your identity before disclosing or changing private records, using proportionate methods that do not require unnecessary identity-document collection. We will evaluate requests and respond under applicable law; this policy does not invent a response deadline that has not been confirmed. You may also raise concerns with the relevant Panamanian data-protection authority, where applicable.

10. Children

The Service is intended only for people aged 18 or older. Signup requests date of birth and age confirmation. If we discover an account belongs to someone under 18, we may restrict the account and address its data in accordance with applicable law.

11. Changes to this policy

We may update this policy when the Service, processing activities, legal operator, or applicable requirements change. We will identify the version and effective date, and request renewed acknowledgment when appropriate. A new policy version is not deemed accepted before a valid acknowledgment is recorded.

12. Contact

Pex Protocol (operating name). Privacy, account, and legal inquiries: corp@pexprotocol.com.