Limitime Privacy Policy

Effective: 6 August 2026  /  Last updated: 21 October 2026

日本語

1. Introduction

This Privacy Policy explains how Limitime (the “App”) collects, uses, stores and transmits information relating to users.

The App records the usage of compatible heated-tobacco devices and provides features such as goals, waiting periods, device locking and unlocking to support users who want to reduce their tobacco use.

For users in the United Kingdom, this policy also explains the legal bases on which personal data is processed and the rights available under UK data protection law. Although the App uses anonymous authentication and does not require your name or email address to create an account, identifiers and usage records may still constitute personal data under applicable law.

2. Information We Collect or Generate

The App currently collects or generates the following information:

  • A user identifier issued through Supabase anonymous authentication and authentication-session information stored on your device.
  • Information obtained during Bluetooth scanning and connection, including compatible-device identifiers, display names, signal strength, connection status, advertising data, and supported Service and Characteristic information.
  • Cumulative usage counts, lock status and, for supported holder-type devices, holder insertion/removal status obtained from the connected device.
  • Bluetooth disconnection and reconnection times; for supported holder-type devices, holder removal and reinsertion times where a single increase in usage count is confirmed; previous and current cumulative counts and the times at which those counts were obtained; and the difference between those counts.
  • Your average daily use before reduction, daily target, minimum waiting period, price per pack and whether reduction features are enabled.
  • The time at which you use an early-unlock feature and, if provided, the reason you select. No reason is stored if you skip that step.
  • Your acceptance status for the Terms of Use and Privacy Policy, the version of each document, the time of acceptance and the App version at that time.
  • Setup and onboarding events, including screens and connection sub-steps shown, completion actions, success or failure of Bluetooth preparation, device search, connection and settings storage, setup completion, event timestamps, a setup-attempt identifier and App version.
  • Live Activities settings; random installation and lock-cycle identifiers; device type; lock start and scheduled unlock times; display status; and Apple Push Notification service (APNs) tokens used to start and end Live Activities.
  • Information required to maintain App state, such as onboarding completion, lock-cycle start time, the currently applied minimum waiting period and confirmed unlock-failure counts.

The App does not require your name, postal address, telephone number, payment details, contacts, photos, microphone data or precise or approximate location. It does not use IDFA or collect information for cross-app or cross-website advertising tracking.

3. How We Use Information

We use the information described above only for the following purposes:

  • Finding, connecting and reconnecting compatible devices, showing their status, and performing supported lock and unlock operations.
  • Recording and displaying usage counts, usage intervals, progress towards targets and estimated savings.
  • Providing reduction-support features configured by you, including minimum waiting periods and early unlocking.
  • Restoring local App state and synchronising relevant records between your device and Supabase.
  • Providing Live Activities that display waiting time on the Lock Screen and Dynamic Island and allow you to return to the App after the waiting period.
  • Maintaining records of acceptance of the Terms of Use and Privacy Policy.
  • Aggregating setup drop-off and failure points to improve the setup process.
  • Checking that the App operates correctly and investigating development issues such as connection failures or invalid device responses.

We do not use smoking-related usage records for advertising, cross-service tracking or medical diagnosis.

4. Bluetooth

The App uses Bluetooth Low Energy to discover and connect to compatible devices. During scanning, it may temporarily obtain advertising information such as a device identifier, display name, signal strength, connectability, transmission power, Service UUIDs, Manufacturer Data and Service Data. This information is used to identify compatible candidates, establish connections and verify behaviour during development.

After connection, the App checks supported Services and Characteristics and parses device notifications to obtain cumulative usage counts, lock status and, on supported holder-type devices, holder insertion/removal status. Raw holder status is used temporarily as a trigger for obtaining the cumulative usage count. Only where a single increase in cumulative usage is confirmed after holder removal are the removal and reinsertion times stored locally as an approximate usage interval and sent to Supabase.

The current App does not implement collection of battery information.

The identifier and display name of a successfully connected device are stored on your device to support later reconnection. When a usage-count difference is confirmed, the device display name is sent to Supabase with that event. Ploom display names are normalised to the model name “Ploom AURA” or “Ploom CUBE” without an individual-device suffix.

Signal strength, Manufacturer Data, Service Data, transmission power, connectability, Service UUIDs, Characteristic information and raw notification data are not normally stored as App data or sent to Supabase. In development builds, some of this information may appear in local diagnostic logs.

The App does not request location permission and does not implement location collection as part of its Bluetooth functionality.

5. Data Storage

The App stores different types of information locally on your device and in Supabase.

Local AsyncStorage may contain onboarding state, unsent setup-progress events and a setup-attempt identifier, legal-document acceptance information and pending acceptance, reduction settings and feature state, connected-device identifiers and display names, cumulative-use baselines, timestamps relating to disconnection/reconnection or confirmed holder removal/reinsertion, confirmed and pending usage-difference history, lock-cycle information, early-unlock times/reasons/pending events and the Supabase anonymous-authentication session. AsyncStorage is not an encrypted storage area.

Live Activities settings, the current lock cycle, deduplication identifiers and up to 64 cycle identifiers awaiting completion may also be stored locally. APNs tokens are not stored in AsyncStorage; they are managed on the server. Server-side Live Activities records do not include the individual Bluetooth device identifier or display name.

Supabase stores, in association with the anonymous user identifier, setup progress and result events, usage-count difference intervals and the previous/current count-observation times, early-unlock times and selected reasons, and acceptance history for the Terms of Use and Privacy Policy. Unknown usage times are not guessed. Where the App can identify an approximate start time for a single IQOS usage-count increase, it may use the Bluetooth disconnection time for ONE models or the holder-removal time for i / PRIME models and count that usage on the corresponding day.

6. External Services

The App uses Supabase for anonymous authentication, database storage and data synchronisation. Communications with Supabase use an authentication token stored on your device. Supabase may process network information such as an IP address as part of providing its service, but the App does not store IP addresses as a field in its own application database. Supabase’s own terms and privacy policy apply to its processing.

If Live Activities are enabled, the App sends to Supabase the relevant APNs start/end tokens, random installation and cycle identifiers, device type, lock start and scheduled unlock times and display status. Supabase then sends Apple APNs the token and the information required to display the Live Activity, including device type, relevant times, cycle identifier and a link back to the App. Apple’s terms apply to Apple’s processing.

The App sends setup-progress events to Supabase to improve the setup process. It does not currently include SDKs whose purpose is third-party advertising, crash-reporting or cross-service advertising tracking.

8. Sharing and Sale of Information

We do not sell user information. We do not disclose it to third parties for advertising purposes.

Information may be disclosed where required by law, where necessary to protect life, physical safety or property, or where otherwise permitted by applicable law. Sending information to Supabase and Apple as described above is necessary to provide relevant App functionality and is not a sale of information for advertising purposes.

9. Retention and Deletion

Confirmed usage-count difference history stored locally is limited to 2,000 records. Unsent usage-count difference history is limited to 500 records and is retained for up to 10 days from the reconnection-confirmation time. Unsent setup-progress history is limited to 100 records, unsent early-unlock history to 500 records and one pending consent record is retained until transmission succeeds. Other local settings are overwritten when changed or retained until the App is removed or the data is deleted through the App.

Supabase Live Activities cycle information and cycle-specific tokens are removed by an hourly deletion process after they have been ended for more than 24 hours. Cycles older than eight hours are treated as ended. Installation information and start tokens that have not been updated for 90 days are also removed by the hourly process.

You can use Settings → Delete all data in the App to delete App data stored on your device, server-side setup progress, usage-count differences, early-unlock events, consent history, Live Activities information and tokens, and the anonymous-authentication user. This action cannot be undone and requires a network connection. After deletion, the App returns to the beginning of onboarding.

If deletion fails, check your network connection and try again from Settings. Local data and the authentication session are not removed until server-side deletion succeeds.

10. Security

We take reasonable technical and organisational measures intended to prevent unauthorised access, disclosure, alteration or loss of information.

Live Activities tokens and cycle information cannot be directly registered or read from the application database by the App. They are operated through server-side processing that verifies requests from the authenticated user. APNs private keys are not included in the App.

Data stored in Supabase is associated with the anonymous user identifier and Row Level Security is used so that the App can register or read only data belonging to the currently authenticated user. No method of transmission or storage can, however, be guaranteed to be completely secure.

11. Your UK Data Protection Rights

If UK data protection law applies to our processing of your personal data, you may have rights including:

  • the right to request access to your personal data;
  • the right to request correction of inaccurate or incomplete personal data;
  • the right to request erasure of your personal data in applicable circumstances;
  • the right to request restriction of processing in applicable circumstances;
  • the right to object to certain processing, including processing based on legitimate interests;
  • the right to data portability where the legal requirements are met; and
  • the right to withdraw consent at any time where processing is based on consent.

You may exercise these rights by contacting us using the details below. We may need enough information to identify the relevant anonymous account or support ID before we can act on a request.

You also have the right to complain to the UK Information Commissioner’s Office (ICO). Information about making a complaint is available at ico.org.uk.

12. Age Restriction

Because the App contains functionality relating to heated-tobacco use, it is intended only for adults who are legally permitted to use such products in their jurisdiction.

In the United Kingdom, the App is not intended for persons under 18. The current App does not ask for a date of birth and does not perform identity-document age verification.

13. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in law, App functionality or our handling of information. Where a change is material, we will provide notice in the App or by another appropriate method.

14. Contact

For questions about this Privacy Policy, your information, data deletion or your UK data protection rights, contact the Limitime operator at limitime.support@gmail.com or use the contact option in the App’s Settings screen.

When you contact us from the App, your device’s mail application is opened and the draft body may contain the App and OS versions, a support ID based on your existing anonymous user identifier, and the selected device name. You control whether the email is sent and may edit or remove this information before sending. Authentication tokens, individual Bluetooth device identifiers and raw communication logs are not included in the draft.

If you send an email, we receive the sender email address and the contents of your message for the purpose of responding and investigating the issue. If you include the support ID, we may use it to locate relevant stored usage records. You may remove the support ID before sending if you do not wish to provide it.

15. Effective and Revision Dates

Original effective date: 6 August 2026

UK English version last updated: 21 October 2026