Privacy Policy

Introduction

Jilpy ("we", "our") is a mobile application designed to help users track their GLP-1 medication therapy and monitor related health parameters.

This Privacy Policy describes how we collect, use, store, and protect your personal and health data when you use Jilpy.

IMPORTANT: Jilpy collects and processes sensitive health data: the data you enter yourself and, if you authorize it, the data read from Apple Health or Health Connect (section 1.3). How we collect your consent is explained in section 2.

1. Data Collected

The following are required to complete registration: email (or an Apple or Google account), name, date of birth, gender, height, starting weight and goal weight, medication, pen dose and number of clicks. Without this data you cannot use Jilpy. All other data you enter is optional.

1.1 Account Information

• Email: Used for signing in and for essential communications
• Full name: To personalize the app
• Profile photo: Optional, to personalize your account
• Password: If you sign in with email and password, stored only as a non-reversible hash, via Supabase Auth
• Apple or Google account: If you sign in with "Continue with Apple" or "Continue with Google"
• Date of birth and gender: Your date of birth is used to verify that you are at least 18 years old; date of birth and gender complete your profile (Profile → Personal Data)
• Subscription: Type, expiry date, platform, store purchase identifiers and history of subscription events

1.2 Health Data (Special Category, GDPR Art. 9)

Jilpy collects the following health data, which you enter yourself:

GLP-1 Therapy:

• Medication, dosage and frequency of your therapy
• Injection date and time
• Dose administered (mg)
• Pen dose and number of clicks
• Body area and position of the injection
• Perceived discomfort level (from 0 to 5)
• Perceived fear or anxiety level (from 0 to 5)

Body Parameters:

• Body weight (kg), starting weight and goal weight, height (cm), BMI (automatically calculated)
• Circumferences: waist, hips, chest, arms, thighs, calves and ankles (right and left)
• Body composition: body fat, lean mass, body water, protein and bone mass (as percentages)

Blood Glucose:

• Blood glucose value (mg/dL), measurement date and time, meal context, notes

Symptoms and Conditions:

• Daily symptoms with their intensity (on scales from 0 to 5 or from -5 to +5)
• Energy and appetite levels
• Descriptive notes

Medications and Supplements:

• Name, day and time of day of intake (morning, afternoon or evening)

Menstrual Cycle:

• Cycle dates and related information you enter

My Doctors:

• Name, facility and contact details of the doctors you choose to add. Name, city and facility go into a shared directory that other members can see; email, phone numbers and medical register number, and the link between you and your doctor, stay visible only to you

1.3 Integration with Apple Health and Health Connect

Only if you authorize it, Jilpy can read the following data from Apple Health (iPhone) or Health Connect (Android):

• Body weight (kg)
• Body fat percentage
• Lean mass (kg, converted to a percentage)
• Blood glucose (mg/dL)

Important:

• The integration is optional and disabled by default
• You can turn synchronization on or off from Profile → Data Management (Premium feature). In any case, you can remove the read permission at any time from the Apple Health or Health Connect settings: from that moment on, Jilpy no longer reads anything
• If you have chosen CGM in Profile → Blood Glucose Mode, blood glucose is read every time you open the chart. On Android, the Health Connect permission is enough, even with synchronization turned off; on iPhone, synchronization must be turned on. To stop it, choose another mode or remove the permission
• Data is read when you open the app, when you enable or sync the integration and, for blood glucose, when you open its chart
• The weight and body composition data we read is saved to your Jilpy account; the blood glucose data we read is only displayed in the app and is not saved on our servers
• We do not write data to Apple Health or Health Connect

1.4 Usage Data

• When you send a report from Profile → Support Center → Open a Report, along with your text we receive the device model, the operating system and app version, the device language and the technical log of the app's activity (not just errors). Similar technical data also reaches Sentry with crash reports, as explained below. Reports and their attachments can be seen only by you and by authorized members of the Jilpy team. We keep each report, with its attachments, for 24 months from when it was opened, then we delete it
• Along with the notification identifier, we store the platform (iOS/Android), the app version and the date and time the app was last launched
• When you use the community, we store the date and time you were last seen, to show how many people are online
• Access log: when you sign up, sign in, refresh your session, sign out or delete your account, the authentication system records the type of operation, the date and time, your identifier, email and name, and the sign-in method (Apple, Google or email). We keep it for 12 months for security reasons, after which it is deleted automatically
• Sign-in sessions: as long as you stay signed in, the authentication system keeps, for each open session, the IP address and the technical data of the app and the phone (user agent). They are deleted when you sign out of your account or delete it
• Like any online service, our server provider (Supabase) records in its technical logs the requests the app sends to the service, including network information such as the IP address, and keeps them for a limited period (currently up to 90 days)
• Crash reports (Sentry): if the app closes because of an error, or encounters an unexpected error, it sends a technical report to Sentry, the service we use to find and fix faults. The report contains:
  • the type of error and the point in the program where it occurred;
  • the app version;
  • technical characteristics of the device, for example model, operating system, language, time zone and free memory;
  • a random identifier of the app installation, which is not linked to your account.
• Sentry also records the start and end of each usage session, without knowing what you do in the app: this is used to measure how many sessions end without a crash. On Android, it also records when the app freezes
• The report does not contain: name, email, your Jilpy account identifier, health data, texts you write, screenshots or screen recordings, the list of actions you take in the app, or requests to our servers. The IP address is not stored, nor is the approximate location that can be derived from it. For errors in the app's code, before sending, numbers, email addresses and identifiers found in error texts are replaced with symbols. Other reports are cleaned by Sentry when it receives them, removing the data it recognizes as sensitive
• Sentry is active only in the versions of the app distributed to users. Crash reports remain on Sentry for a maximum of 90 days; session data for the period set by Sentry
• We do not use external services for behavioral analysis (analytics) or for profiling. Internal statistics on app usage are described in section 3.1

1.5 Photos and Images

• Profile photo (optional), images you post in the community and screenshots attached to reports sent to the Support Center
• Stored on secure servers. Images posted in the community are visible to other members. Community images and profile photos are stored as public files: anyone who has the link to an image can open it, even without being a member
• Report screenshots are private: they can be seen only by you and by authorized members of the Jilpy team
• You choose the images to upload yourself, from your phone's picker. Access to the camera and to your entire photo library requires your permission

1.6 Notifications

• Reminders for injections, daily symptoms, weekly weight and blood glucose; community notifications (comments on your posts, replies to your comments, mentions and quotes in chat)
• You can turn each reminder and community notifications on or off from Profile → Notifications
• For push notifications we use Firebase Cloud Messaging (Google), which receives a device identifier and, for community notifications, the name of the person writing and a preview of the message. On iPhone, notifications are delivered through Apple's notification service

1.7 Community

• Messages, posts, comments, reactions and images you post are visible to other members
• Your name, your profile photo, a check mark if you are Premium and any labels we assign to you (for example "doctor") appear next to your content
• If you write in anonymous mode, the app does not show your name and photo to other users: a pseudonym appears in their place. The content nonetheless remains associated with your account in our systems, for moderation and deletion purposes. Community moderators and the Jilpy team can see who wrote it (name and email), solely for security and moderation reasons
• Before publication, the text of chat messages is checked by an automated moderation system (see section 4.1). The automated system can only hide a message: any other decision, such as sanctions, is made by the moderators or the team
• Messages hidden by automated moderation remain stored. Community moderators and the team can see them, together with content reported by other users and sanctions
• If content contains a link, the app downloads the preview directly from that website (see section 4.3)

Your progress. In Profile → Community there is the "Show my progress" switch. It stays off until you turn it on. If you turn it on, your starting weight, current weight, goal weight and the date of your first injection become accessible to other registered users. Next to your signed posts, they will see how long you have been on therapy, how much your weight has changed and how far you are toward your goal. They never appear in anonymous posts. You can turn the switch off at any time: from that moment on, the app no longer shows your progress to others. We record the date and time of the last change to the switch, so that we can demonstrate your consent.

2. Legal Basis for Processing (GDPR)

• Consent (Art. 6(1)(a) and Art. 9(2)(a)): For health data, including the data you choose to write in the community. How we collect it today: on the sign-in screen, the app informs you that by continuing you accept the Terms of Service and this Privacy Policy. During registration, you read the "Important Notice" about using the app (for example: Jilpy is not a medical device and does not replace your doctor's advice) and tick the "I have read and accept the notice" box: we record the date and time. To read data from Apple Health or Health Connect, your phone asks you for a separate permission. To show your progress in the community, you must turn on the switch described in section 1.7, and we record the date and time. On the same basis, we calculate the internal statistics described in section 3.1.
• Contract performance (Art. 6(1)(b)): To provide the app's core services
• Legitimate interest (Art. 6(1)(f)): To improve the app, handle reports sent to the Support Center and keep them for 24 months, protect access, prevent abuse and add our affiliate code to links to Amazon and VitaStrong (sections 4.2 and 4.3). On the same basis, we send crash reports to Sentry.

3. How We Use Your Data

3.1 Primary Purposes

• Provide you with the GLP-1 therapy tracking service
• Generate personalized charts and statistics
• Save your recording history
• Send you reminder notifications (if enabled)
• Sync data from Apple Health or Health Connect (if you authorize it)
• Find and fix app crashes and errors
• Internal, aggregate statistics on app usage (for example, how many people use each medication or remain active over time), calculated also from your records. Only the team sees them, and they show only overall figures, from which individual people cannot be identified

3.2 What We Do Not Do

• We do not sell your data to third parties
• We do not pass your health data on to third parties: it is processed on our behalf only by some of the providers listed in section 4.1 (Supabase and, for community texts, Firebase Cloud Messaging and Google Gemini; on iPhone, notifications also pass through Apple's service). Other users see only what you choose to show or publish in the community (section 1.7)
• We do not use health data for profiling
• We do not use advertising SDKs or services and do not share data with advertisers (for recommended products and Amazon links, see sections 4.2 and 4.3)
• We do not use data for research without separate consent
• We do not write data to Apple Health or Health Connect

4. Data Sharing with Third Parties

4.1 Essential Service Providers

Supabase: the app's servers and database, in the European Union, with TLS and AES-256 encryption (Privacy Policy)

Firebase Cloud Messaging (Google): sends community push notifications. It receives the device identifier and the content of the notification. On iPhone, notifications also pass through Apple's notification service (Privacy Policy)

Google Gemini API: automatically moderates chat messages. It receives the text of the message and, as context, the text of the latest messages in the group (up to three, plus the one you are replying to), with the names of their authors ("Anonymous" for anonymous messages). Paid service; the data is processed on our behalf: Google does not use it to improve its products and keeps it for a limited period (up to 55 days) solely to prevent abuse and to meet legal obligations (Terms)

Google Places (Google Maps Platform): when you search for the address of your doctor's facility, your phone sends Google only the text you type, with no location data. Google also receives your phone's IP address and processes this data as an independent controller, in accordance with its privacy policy (Privacy Policy)

Sentry (Functional Software, Inc.): reports on app crashes and errors, stored in the EU region (Frankfurt, Germany). No health data, no name, email or identifier of your account; the IP address is not stored (see section 1.4) (Privacy Policy)

Google Play and App Store: handle subscription payments as independent data controllers, in accordance with their privacy policies; we do not see your card details

Apple Health / Health Connect: read-only, with your permission

4.2 Advertising and Recommended Products

We do not use any advertising SDK or service and do not share data with advertisers. In the "Shop" tab you will find products we recommend, for example VitaStrong supplements. If you tap "Buy on VitaStrong", the seller's website opens in your browser with our affiliate code: the seller knows that you came from Jilpy and, if you make a purchase, Jilpy receives a commission. From that moment on, the seller processes your data in accordance with its privacy policy. For Amazon links, see section 4.3.

4.3 External Links in the Community

Amazon (affiliate program): when you open an Amazon link from the community, the app adds Jilpy's affiliate code to the link (and replaces any code already present). Amazon receives your visit with that code, so it knows that you came from Jilpy, and processes it in accordance with its privacy policy. As an Amazon Associate, Jilpy earns from qualifying purchases.

Link previews: if a message, post or comment contains a link, the app downloads the preview (title and image) directly from that website as soon as the content appears on the screen, without you tapping anything. That website receives your phone's IP address, just as when you visit it.

4.4 No Other Sharing

Apart from what is described in this Privacy Policy, we do not share data with other third parties, social networks, data brokers, or aggregators. We disclose data to authorities only when required by law.

5. Data Storage and Security

• Supabase database on servers in the European Union (Frankfurt, Germany)
• Encryption in transit (TLS) and at rest (AES-256)
• Passwords hashed with bcrypt (non-reversible)
• In the app, each user sees only their own personal and health data. Of other users, they see only what those users have chosen to share in the community.
• Community moderators also see what is needed for moderation (section 1.7)
• Your records (injections, weight, measurements, body composition, blood glucose, symptoms, cycle, medications and supplements) are protected by access rules in the database (Row Level Security) and in the app are accessible only to you, except for the progress you choose to show (section 1.7)
• Session tokens with automatic expiration
• Server provider (Supabase) with ISO 27001 certification

Retention: Your account data is kept as long as the account is active. The exceptions are reports sent to the Support Center, which are kept for 24 months from when they are opened and then deleted, and the access log, which is kept for 12 months for security reasons and then deleted automatically. What happens when you delete your account is explained in the Account Deletion section.

Account and Data Deletion

From the app: open Jilpy → Profile → Delete Account (at the bottom of the page). Deletion is immediate.

Without the app (for example, if you have already uninstalled it): email info@jilpy.app from the email address of your Jilpy account and ask for your account to be deleted. We complete the deletion within 30 days and confirm it by email. If you signed in with Apple and hid your email, write to us from any address, stating the name you use in Jilpy: we will ask you for confirmation at the hidden address linked to your account.

Subscription: deleting your account does not cancel your subscription. Cancel it first from Google Play (Subscriptions) or from your iPhone Settings (Subscriptions). For help, email info@jilpy.app.

What is deleted: profile, login credentials (email, password, link with Apple or Google), sign-in sessions with their IP address, subscription data and its history, all health data (therapy, injections, weight, measurements, blood glucose, symptoms, cycle, medications and supplements), profile photo, images posted in the community, screenshots and technical logs attached to your reports, group memberships, reactions, notifications and device identifiers.

What remains:

• The text of messages, posts and comments published in the community remains visible for as long as the community exists, but is no longer linked to your account. Your name may remain in mentions made by other users and in notifications they have already received. If you want us to remove your texts or the mentions, email info@jilpy.app
• The title and text of reports sent from Profile → Support Center → Open a Report, with their technical data (category, app version, device model and operating system), remain without any link to your account for up to 24 months from when they were opened, then they are deleted. If you want us to delete them sooner, email info@jilpy.app, preferably before deleting your account: afterwards, you will need to tell us which ones they are (for example, title and date), because they are no longer linked to you
• Doctor entries you added remain in the doctors directory for as long as the directory exists, with no link to you
• The authentication system's access log (type of operation, date and time, account identifier, email and name, sign-in method) remains until 12 months have passed from each entry, then it is deleted automatically. It is used to protect access
• Crash reports sent to Sentry, which are not linked to your account, remain until they expire (90 days at most)
• The server provider's technical logs (up to 90 days) and the copies of messages that Google keeps for moderation (up to 55 days) remain until they expire
• Database backup copies are overwritten within 90 days

6. Your Rights (GDPR)

To exercise these rights, email info@jilpy.app.

• Access (Art. 15): Receive a copy of all your data
• Rectification (Art. 16): Correct inaccurate data
• Erasure (Art. 17): Delete your account and data (Profile → Delete Account, or without the app)
• Restriction (Art. 18): Ask for the processing of your data to be restricted
• Portability (Art. 20): Receive your data in a readable format
• Objection (Art. 21): Object to processing based on legitimate interest (section 2)
• Withdraw Consent (Art. 7(3)): You can withdraw it at any time, without affecting processing carried out before. For your progress in the community, turn off "Show my progress" (Profile → Community); for Apple Health or Health Connect, remove the permission from your phone's settings. You withdraw consent to health data in general by deleting your account (Profile → Delete Account) or by emailing info@jilpy.app, because without that data Jilpy cannot work
• Complaint (Art. 77): File a complaint with the Italian Data Protection Authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it)

7. App Permissions

8. Minors

Jilpy is reserved for people who are at least 18 years old: during registration we ask for your date of birth, and you cannot proceed if it shows a lower age. If we discover that a minor has provided personal data, we will delete it immediately.

9. International Transfers

Your data is stored on servers in the European Union (Supabase, a service provided by Supabase Pte. Ltd., Singapore). Supabase and its providers may also access it from countries outside the European Economic Area (EEA), for example from the United States or Singapore, including for technical support, under standard contractual clauses.

The Google services listed in section 4 (notifications, moderation, address search) may also process data outside the EEA, with the safeguards required by the GDPR (standard contractual clauses and the EU-U.S. Data Privacy Framework, in which Google participates). Apple's notification service, used on iPhone, may process data outside the EEA under standard contractual clauses.

Crash reports are stored by Sentry in the European Union (Frankfurt, Germany). Sentry (Functional Software, Inc.) is a U.S. company and may also access them from countries outside the EEA, with the safeguards of the EU-U.S. Data Privacy Framework, in which it participates, and of standard contractual clauses.

10. Changes to the Privacy Policy

We may update this Privacy Policy. The date at the top indicates the last change. We also point out significant changes in the app's update notes.

11. Cookies and Tracking Technologies

• Session tokens for authentication
• Local preferences saved on the device
• A random installation identifier, saved on the device, for crash reports (not linked to your account)

We do not use third-party cookies for cross-site advertising tracking.

12. Contact

Data Controller: Leonardo Toro

Email: info@jilpy.app

App: Profile → Support Center → Open a Report

Response time: within one month (GDPR Art. 12). In complex cases, this period may be extended by a further two months: in that case, we will let you know within the first month.

13. Jurisdiction

This Privacy Policy is governed by Italian law and EU Regulation 2016/679 (GDPR).