Privacy policy

Account signup and authentication

When you create an account, ezGLP collects your verified email address, name, and any optional alias you provide. Authentication may use emailed links or codes, passkeys, an authenticator app, or a configured Google or Apple identity provider. A dedicated review account may use an operator-provisioned password, stored as a salted hash rather than readable text. Password sign-in is not available for general accounts.

Information the service may process

• Account and security data, such as email address, authentication methods, sessions, and access status
• Medicine records, including prescriptions, schedules, dose logs, preparations, inventory, purchases, and reminders
• Wellness and health-related records you choose to enter, including measurements, events, activities, and laboratory results
• Contact-form details, including the reason, name, reply email, and message you submit; when you are signed in, the submission is also linked to your account ID and account email
• Technical data needed to operate the service, such as timezone, display preferences, notification subscriptions, audit records, and security logs
• Data returned by optional services or integrations enabled for the service or your account

How information is used

We use information to maintain your records, track your progress, provide schedules and reports, manage your account, protect the service, make backups, deliver enabled reminders, and carry out imports or integrations you request. We also use contact details and messages to respond to support and privacy requests. We do not sell personal information or use it to build advertising profiles.

ChatGPT and other connected assistants

Connecting an assistant is optional. When you connect ChatGPT and approve access, records returned by ezGLP are shared with OpenAI so ChatGPT can respond to your requests. Other assistants receive records through their own providers. Shared information can include your wellness measurements, meals, schedules, history, inventory, laboratory results, and notes, depending on the tools used and the permissions you approve.

With write access, an assistant can send information you ask it to record to ezGLP and can update or delete records within its permissions. We receive the information supplied in those tool requests and store resulting changes in your account. The integration uses individual tool requests and responses; it does not request your complete conversation history. Only include information needed for the task, and avoid unrelated personal information in optional notes.

Information sent to an assistant provider is handled under that provider's terms, privacy policy, and your account settings. Disconnecting an assistant or deleting information in ezGLP does not delete copies already held by OpenAI or another provider. Use that provider's privacy controls to manage those copies.

Connection permissions and your choices

• Review the requested permissions before connecting an assistant. You can deny the connection, choose read-only access when offered, or allow access that includes creating, updating, and deleting records.
• Manage connected applications in ezGLP settings. You can disconnect an application or revoke an integration key. Disconnection removes its saved authorization and prevents renewal of access; an already-issued access token may remain usable until it expires.
• Choose which optional wearable connections, imports, and reminders to enable. Manage an assistant's own connection and privacy settings with that provider as well.
• Use available record-editing and export tools to review, correct, or obtain your information. You can request account and data deletion from settings or by contacting [email protected].

Optional usage analytics

If the service operator enables optional usage analytics, the operator's self-hosted Umami instance receives privacy-reduced page paths and referrers, browser and device metadata, a daily rotating pseudonymous identifier for signed-out visitors, a stable internal account ID for signed-in visitors, and coarse MCP metadata such as protocol method, recognized tool name, credential scope, outcome, and latency. The visitor IP address and available Cloudflare country, region, and city headers are forwarded only so Umami can derive location and session information; Umami does not store the raw address.

Dynamic record identifiers, query strings, page titles, email addresses, names, aliases, other contact details, prompts, tool arguments or results, and medicine or wellness record values are not sent as analytics properties. These analytics help us understand usage and application performance.

Optional analytics are enabled or disabled by the service operator. There is currently no per-account analytics switch in the app. Contact [email protected] with questions, objections, or requests concerning analytics associated with your account. Disabling reminders or disconnecting an assistant does not by itself disable website analytics.

Storage and service providers

Records are stored on infrastructure used to operate ezglp.app. Email, push notification, self-hosted analytics, anti-abuse, wearable, reverse-proxy, backup, and AI-assistant providers may receive the information needed for an enabled function. The public contact form uses Cloudflare Turnstile to reduce automated abuse. These providers' own terms and privacy practices also apply.

Sensitive record fields are encrypted by ezGLP where supported. Encryption does not eliminate every security risk, and no internet service can guarantee absolute security.

How long we retain information

Account and tracking records remain stored while you use your account unless you delete individual records or request deletion of your account and associated data. These records do not automatically expire just because you stop using the service.

We complete deletion requests within 15 business days. You can submit a request in ezGLP settings, through ezglp.app/contact, or by emailing [email protected]. Submitting a request does not erase information immediately. Requests submitted in settings can be cancelled before processing begins; contact us if a request is already being processed.

Backups are retained for 30 days. Deleted information may remain in a backup made before deletion until that backup reaches the end of its retention period. The backup retention period is separate from the 15-business-day period for completing deletion requests in the active service.

Integration retry records store identifiers, a request fingerprint, and a saved result to prevent duplicate writes. Records older than 30 days are removed when the application's startup cleanup runs; they can remain longer if the application has not restarted. Deleting an individual entry does not itself clear an existing retry record.

Analytics, infrastructure and security logs, and support correspondence are managed separately from your tracking records and database backups. Contact [email protected] to request access or deletion of information associated with you, including information held in these systems. Information already shared with an assistant or other external provider follows that provider's retention and deletion practices.

Cookies and local device storage

The app uses security and session cookies plus local browser storage for functions such as theme, timezone, offline support, and update handling. These are operational features rather than advertising trackers.

Children and policy changes

ezGLP is not directed to children. This policy may change as the service changes; the effective date above identifies this version.