Privacy Policy

Controller and contacts

Data controller: Francesco Abbadini.

Privacy and support contacts: hello@liftstyle.app.

Data processed

• data saved in the app: workout profile, places, equipment, calendar, plans, preferences, and progress;
• in native apps, data needed by the online planner: dates and activity types, custom place or sport names, target exercise count, including when derived on-device from the selected duration, existing exercises, level, the selected gender profile (man/woman), and planner priorities;
• if you choose an account: email address, password handled by Supabase as a protected sign-in credential, user and session identifiers, confirmation or recovery tokens and, if you use Google, name and profile-picture URL received from the provider;
• if you authorize cloud syncing: training profile, places and equipment, calendar, plans, completed exercises, preferences, goals, sports, muscle focus, exclusions, language, timer preferences, planner data, and technical synchronization metadata, including the date and version of the authorization recorded on this device;
• In earlier versions with Supabase aggregate statistics: if you enable usage statistics: platform, language, app area, type of feature used, technical outcome, and count; email address, account ID, device or session ID, profile, equipment, exercises, calendar, or workout-plan content are not included;
• IP address, approximate location inferred from the IP address, timestamp, user agent, API path, outcome, duration, and request identifiers processed by the infrastructure for operation, diagnostics, and security.

The payload used only to calculate the plan does not automatically add an email address, account identifier, date of birth, or advertising data. If you choose an account, your email address, password handled by Supabase as a protected sign-in credential, identifiers and, with Google, name and profile-picture URL are linked to the account. The password is not included in synchronized training data. Training data is linked to the account only if you authorize syncing. Custom names are free-text fields: do not enter people’s names, email addresses, diagnoses, injuries, or other unnecessary personal or health data. LiftStyle does not ask for medical records, diagnoses, or certificates.

Accounts and cloud sync are optional. Before the controls to create an account or sign in, we display a prominent notice about the synchronized data and possible health inferences. By pressing one of those controls, you give explicit consent to synchronization. Consent for the online planner and for usage statistics remains separate and is not enabled by the account or cloud sync. The automated newsletter is not active. The public frontend does not use Google Analytics, Meta Pixel, or advertising tracking.

Native versions and planner submissions

When you ask to generate, regenerate, substitute, or analyze a plan in the native app, the app sends the data described in this notice to the LiftStyle API. In versions that include the dedicated privacy control, before the first submission the transmitted categories are displayed, authorization is recorded separately, and it can be withdrawn in settings. If the control is not shown, data is submitted when you confirm the planner feature: to avoid new submissions, do not start these features and continue using plans already saved.

Timer alerts and reminders

Timer alerts and reminders, in versions that include them, are optional and non-promotional. They are scheduled on your device, without a remote notification delivery service. To manage reminders, LiftStyle locally uses your calendar, the last time you opened the app and the last time you started a workout.

Consent for alerts and reminder settings, including the time, are not synced to the LiftStyle cloud; sound and vibration preferences may be included in optional sync. Preferences remain until changed or deleted; recent technical data is updated, and scheduled alerts are replaced or cancelled when no longer needed. Any system backups follow your device settings.

You can manage or turn off alerts in the app and device settings. The exercise name may appear on the lock screen, depending on system settings. Notification permission does not enable an account, cloud services, analytics or advertising.

Optional measurement

This section describes measurement available in Settings in the version you use. If a feature is unavailable or has not been enabled for that version, its sends remain disabled, even with a saved preference. Aggregate statistics from earlier versions are described separately below.

You can use LiftStyle without sharing statistics, technical reports or ad measurement. The three choices are separate, off by default and available in Settings. They apply to this browser or device, independently of your account and cloud sync. Ad measurement is available only in enabled native apps.

If you accept usage statistics, PostHog EU receives steps in the app: initial setup, screen views, adding to the calendar, generation, opening a workout, saving progress and opening help. We send event time, random instance, session and action codes, app version, platform, outcome, duration and technical categories. We exclude diary content, exercises, weights, workout dates, entered text and contacts. The codes are pseudonymous: the events are not anonymous and reveal use of the app.

If you accept technical reports, Sentry EU receives error categories, code references, event time, version and platform. We exclude full error messages, user content, screenshots and the instance code. We do not record session videos or advertising identifiers. The network communicates the IP address needed for the connection to the providers.

The local statistics queue keeps pending events for no more than 72 hours and is excluded from exports, cloud sync and the app's native backups. Withdrawing consent stops new sends and clears the queue; it cannot recall a request already received by the provider. To request deletion of PostHog events, first copy the codes from Settings and email hello@liftstyle.app. Deleting local data before copying them may prevent us from finding the history.

We use PostHog statistics and Sentry reports to understand where app journeys stop and fix problems, based on optional consent (Article 6(1)(a) GDPR). We do not send these data to Meta or use them to infer health conditions or link people across devices. Refusal does not limit app features.

Retention for the new measurement system. The PostHog plan provides a one-year event query window: this window does not guarantee deletion of older data. Deletion requires a separate request and verification of completion; automatic removal after 90 days is not yet active. Rotating the local code after 90 days does not delete remote events. Sentry keeps reports for up to 90 days during the trial and on plans with that retention; the free Developer plan keeps new events for 30 days. Periods start on receipt: changing plans does not immediately delete earlier events. Private exports contain aggregate totals and indicators, without individual codes, and are kept while needed to compare app trends; they are deleted when that purpose ends.

PostHog and Sentry process data on the controller’s behalf in projects configured in the EU region, under signed data processing agreements. Support, subprocessors and security logs may involve processing outside the European Economic Area, with the safeguards in those agreements, including standard contractual clauses where applicable. Event retention periods do not promise simultaneous deletion from security logs and technical copies, which follow provider cycles and applicable obligations. You can ask the controller about safeguards and deletion status.

Android — Meta ads. Only with separate consent to ad measurement may LiftStyle send Meta the observed first opening and its time, an available Android advertising ID, connection IP address, random installation code, operating system version and app identifier. The send passes through LiftStyle’s server. It links the opening to ads; Meta may associate these data with activity on its services and also use them to optimize ads, personalize content and products, and keep them secure. This is not anonymous measurement. We exclude workouts, diary content, contacts and LiftStyle account data. An observed first opening is not necessarily a new download: reinstalling or clearing data may recreate it.

Android — abuse prevention. Only after the same optional choice do we use Google Play Integrity to verify app, licensing and device integrity. Google receives app metadata, certificates and technical device signals, licensing status and a digest of the request; LiftStyle’s server verifies the response. This proof is not sent to Meta and LiftStyle does not use it to identify or track the device. Google handles the data under Google Play terms and deletes it after a fixed service retention period, with no numerical duration published in its guide. This check does not enable recognition after reinstalling.

LiftStyle’s abuse-prevention ledger keeps only technical digests of the token for 24 hours and of the event and request for 90 days, followed by scheduled cleanup at least hourly. It contains no advertising ID, IP address, original token or workout content. These periods concern the ledger, not data already received by Meta or infrastructure logs. The path remains disabled until cleanup and other activation conditions are verified. We keep no offline queue and do not automatically retry the Meta send.

iPhone and iPad — Meta ads. With the separate choice, enabled app versions use Apple’s SKAdNetwork for a fixed-value first-opening signal. Apple handles attribution and aggregate reports, subject to delays and privacy thresholds. This path does not read IDFA, request ATT permission or send individual identifiers to Meta from the app. It sends no workout details. Withdrawing prevents new requests but cannot recall signals already submitted to Apple. The web does not send these signals to Meta.

These advertising sends rely on optional consent (Article 6(1)(a) GDPR). For transfers from Meta Ireland to Meta in the USA, the addendum specifies the Data Privacy Framework and, where applicable, other mechanisms such as standard contractual clauses; it does not guarantee EU-only processing. Advertising measurement recipients. For EEA users, Meta Platforms Ireland Limited handles data under Meta Business Tools Terms: it acts on LiftStyle’s behalf for matching and reporting; collection and transmission for the specified additional uses involve joint responsibility; subsequent uses are Meta’s responsibility. The terms allow up to two years for event data; LiftStyle’s ledger expiry does not apply to Meta. Meta may process data outside the EEA under applicable contractual safeguards. Roles and responsibilities are described at https://www.facebook.com/legal/controller_addendum and https://www.facebook.com/legal/technology_terms; uses, transfers and rights in Meta’s privacy policy: https://www.facebook.com/about/privacy. This integration remains disabled until agreements and release conditions are completed.

Remote deletion is asynchronous: we separately confirm receipt of a request and the verified outcome, within the applicable deadlines for rights requests. Codes copied from Settings identify PostHog events, not Sentry reports. For the latter, provide only approximate time, platform and version if available; we may be unable to distinguish a report without identifiers. Do not send your diary, passwords or unnecessary documents. For Meta measurement, PostHog codes do not identify the sends: contact hello@liftstyle.app to agree only the information needed for the request, or exercise your rights directly with Meta under its policy. Do not email advertising IDs, documents or workout data unless necessary. Withdrawing in the app does not automatically erase data already sent to Meta.

Purposes and legal bases

• local features: saving and displaying the calendar, plans, preferences, and progress on the device;
• native planner: creating, updating, or analyzing the requested plan through the online service;
• optional account and cloud: create and manage the account, authenticate access, sync the selected data, and complete a requested deletion;
• optional usage statistics: understanding in aggregate which features are used and whether they complete or encounter a technical error, in order to improve LiftStyle;
• security and abuse prevention: protecting the service, users, and infrastructure;
• support and legal requests: responding to the request and complying with applicable obligations.

When you ask to generate, update, or analyze a plan in the native app, the ordinary personal data listed above is processed because it is necessary to perform the requested online feature under Article 6(1)(b) GDPR. In versions that include the dedicated privacy control, if your choices may reveal health data, explicit consent under Article 9(2)(a) is also requested before submission. If the control is not shown, avoid new requests to the remote planner and update the app to the latest available version before using it. If you choose an account, the ordinary data needed is processed to create and manage the account. Immediately before the create or sign-in controls, we prominently explain the scope of synchronization; by pressing one of those controls, you give explicit consent to processing synchronized data that may reveal health information under Article 9(2)(a). This consent is recorded separately from the choices for the online planner and usage statistics. If you enable usage statistics, the general signals described above are processed on the basis of optional consent under Article 6(1)(a) GDPR. Technical metadata strictly necessary for security may be processed on the basis of the legitimate interest in protecting users and the service under Article 6(1)(f), subject to a balancing assessment.

When you voluntarily press Create account or Sign in, the data needed to create or use the account is processed to fulfill your request under Article 6(1)(b) GDPR; synchronization and possible health inferences follow the explicit consent described above. The same contractual basis applies to address confirmation, access recovery, and requested deletion.

The planner payload is not used for advertising, commercial profiling, diagnosis, or decisions with legal effects.

Where calculation takes place

On the web, the planner runs in the browser: its payload is not sent to the LiftStyle API. Hosting may still process the ordinary technical metadata needed to deliver and protect the page.

In the Android and iOS apps, the planner sends the request to the LiftStyle API over HTTPS. The calendar, plans, and progress stay saved on the device, but plan calculation is not entirely local.

Providers, recipients, and transfers

Vercel provides hosting, distribution, API execution, and security. In the native apps, it therefore processes the payload to perform the calculation, together with the IP address, approximate location inferred from the IP address, and technical request metadata such as API path, outcome, and duration. The planner function is configured in Vercel's fra1 region in Frankfurt, Germany.

Vercel Inc. is based in the United States and uses subprocessors outside the European Economic Area as well. Vercel is certified under the EU-U.S. Data Privacy Framework and states that it uses standard contractual clauses or other mechanisms provided by law for international transfers where necessary.

Supabase handles the creation, sign-in, confirmation, recovery, synchronization, and deletion of optional accounts. The LiftStyle project is configured in Supabase’s eu-west-3 region in Paris. If you choose Google, Google also sends Supabase the name and profile-picture URL associated with your account; Supabase stores them as account metadata, and LiftStyle does not use them to personalize workouts. For email sign-in, Supabase handles the password as a protected sign-in credential and does not include it in synchronized training data. If you choose Apple, Apple handles authentication under its own privacy notice. Supabase and its subprocessors may also process data outside the European Economic Area under the transfer safeguards set out in the applicable data processing agreement. In earlier versions with Supabase aggregate statistics: Only after the user enables them does Supabase receive small batches of usage statistics and add them to daily aggregates. Requests may generate technical network and security logs, including IP address, date, time, and request metadata, with retention periods determined by the provider’s plan.

Zoho Mail handles messages sent to hello@liftstyle.app and processes the email address, content, and any attachments so that we can respond. The mailbox uses Zoho's European infrastructure; support and subprocessors may involve transfers under the safeguards described by Zoho.

Cookies and technical logs

For local storage, sessions, and technical cookies used in account flows, see the Cookie Policy. The website uses no marketing cookies or advertising tracking; native apps follow the choices described above.

Retention

Local data stays until you delete it or reset the app.

The native request is processed to return the result, and LiftStyle does not intentionally store the request or result in an application database. Vercel's technical runtime logs are retained for one hour and do not intentionally contain the request body. Support messages remain in the mailbox for the time needed to respond, handle any complaints, and protect rights, then are deleted according to Zoho's technical windows and applicable obligations.

The synchronized copy remains in Supabase until you withdraw synchronization or delete the account; signing out does not delete it. Technical retention periods for sessions, authentication logs, backups, security, and applicable obligations remain unaffected.

In earlier versions with Supabase aggregate statistics: The selected usage statistics are stored in the application table solely as daily totals for a maximum of 180 UTC dates. Cleanup runs automatically after every accepted batch and through a daily process. Because the totals contain no user or device identifiers, LiftStyle cannot select an individual user’s contribution in the table in order to delete it. The provider’s technical logs follow the retention periods of the relevant plan and security requirements.

Choices and rights

You can use LiftStyle without an account. You may decline or withdraw authorization for the online planner under Settings > Privacy and security. After signing in, you can withdraw synchronization under Settings > Account and sync: new transfers from this device stop and LiftStyle attempts to delete the current cloud copy, while your account and local data remain available. Another still-authorized device may synchronize it again. If you sign out instead, synchronization is paused but the cloud copy remains and other devices continue according to their own settings. To delete the account as well, use Delete cloud account in the app or the deletion page. You can turn usage statistics on or off under Settings > Privacy and security: when you turn them off, events still pending on the device are deleted and no new events are queued. Account, cloud, statistics, and newsletter do not enable one another.

You may request access, rectification, erasure, restriction, objection, and portability within the applicable limits by writing to hello@liftstyle.app. Because the planner does not require an account, we may ask you for the minimum technical information needed to locate a request in the logs. For the account, you can use password recovery, in-app deletion, and the deletion page. You can also lodge a complaint with the Italian Data Protection Authority or the competent authority in your country.

Minors

LiftStyle is not intended for minors and does not collect dates of birth. If you believe data from a minor has been received, contact hello@liftstyle.app immediately.

Updates

This page is updated when data, purposes, providers, or applicable rules change. Material changes are brought to your attention and may require a new confirmation.