← Back to Lazely
Legal

Privacy policy

Last updated · November 12, 2026

Overview

Lazely ("we", "our", "the app") helps you build healthier digital habits. Most settings and detailed Screen Time information stay on your device. Some data is processed by our service providers to run subscriptions, generate AI conversations, secure the service, and understand how the app is used. This policy explains those differences.

You do not need to create an account. We do not sell your personal data or use it for advertising or tracking across other companies' apps and websites.

Lazely does not include advertising or attribution SDKs, does not access your device's advertising identifier, and does not ask for Apple's App Tracking Transparency permission. If this ever changes, we will update this policy and ask for your permission in the app first.

Screen Time, goals and preferences

Lazely uses Apple's FamilyControls, ManagedSettings and DeviceActivity frameworks to manage the apps you select and display usage reports. App selection uses opaque tokens. We do not send those tokens, app names, bundle identifiers, detailed per-app duration reports, or browsing history to our backend, Google Gemini, or Mixpanel.

Your onboarding answers, goals, focus sessions, intervention history and preferences are stored on your device. Onboarding answers include the first name you choose to give, how you heard about Lazely, your age range, the challenges you recognise, your estimated daily phone hours, your main reason for wanting to use your phone less, how you feel after scrolling, what you have already tried, when you most want to use your phone less, and the goals you pick. Your first name stays on your device. Some of these answers are also sent to our analytics provider, as explained below.

When you use an AI guardian, the app may send your active goal's title and category, your target duration, the reason you chose during onboarding (one of five fixed options, such as "sleep better" or "take back control"), and whether the app you are trying to unlock has crossed certain daily usage thresholds (30, 60, 90, 120, 150 or 180 minutes). The guardian uses your reason to remind you why you wanted to change. These threshold signals do not identify the app or disclose its exact usage duration. Analytics also include threshold events, as explained below.

AI guardian conversations

When you send a message to a guardian, whether from a blocked app or from a conversation you open in Lazely, your message is sent through our backend hosted on Cloudflare to Google's Gemini API to generate a reply. During an ongoing conversation, previous messages and replies are included to provide context. The guardian chat can also include the limited goal, reason and usage context described above. Earlier versions of Lazely also offered a short AI demo during onboarding; that demo did not include your actual Screen Time history.

Our backend processes conversations to return replies and check generated content for safety. We do not store conversation text, or the goal, reason and usage context sent with it, in our backend databases, and we do not include them in our analytics or operational logs. That context is part of the request sent to Google, so the Google retention described below also applies to it. Text you choose to type can nevertheless contain personal information, so please avoid sending sensitive information or information about other people.

We use the paid Gemini API. Under Google's paid-service terms, prompts and replies are not used to improve Google's products or train its models. Google may retain them for a limited period for abuse prevention, security and legal obligations. This is different from saying that no provider ever retains a message. See the Gemini API terms.

Subscriptions and service security

Apple processes payments through the App Store. RevenueCat manages purchase history, subscription status and access to paid features using a randomly generated app user ID and transaction information, such as the product, expiration and renewal status. We do not receive your payment card details or Apple ID credentials. See RevenueCat's Privacy Policy.

Our backend uses Apple App Attest to verify requests from the app, and RevenueCat to verify subscription access where required. It stores an attested public key, verification counters and the app user ID, along with rate-limit and demo-usage state, to authenticate requests and prevent abuse.

Analytics and operational records

We use Mixpanel to understand onboarding completion, feature use, subscription conversion and intervention outcomes. Events can include timestamps, guardian or intervention mode, subscription tier, number of selected apps, usage thresholds crossed, and basic app, device and language information. Network requests also expose an IP address to the receiving provider, which may derive approximate location. We configure Mixpanel to use its EU collection endpoint.

Onboarding events record which screens you reach and the option you select on each question, using fixed answer choices. Your first name is never sent, only the fact that one was entered, and a goal you write yourself is recorded only as "custom", without its text. Five answers are also saved on your analytics profile so we can compare groups of users: how you heard about Lazely, your age range, your main reason for using your phone less, the moment you most want to use it less, and your estimated daily phone hours.

When a shield appears over a protected app, when you choose to step away, or when you tap to negotiate with a guardian, Lazely records that event with the protection mode, the time and, for negotiation, whether notifications are enabled. These events never include the name or identifier of the protected app. When you protect a whole category of apps and iOS provides its name, the category name (for example "Social") may be included. These events are stored on your device and sent the next time you open Lazely, only if analytics are enabled.

When a negotiation with a guardian ends, Lazely records whether access was granted or refused, how many minutes were granted, and a general category for the reason you gave: a practical need, boredom, or habit. The guardian assigns this category from the conversation. The words you wrote are never sent to our analytics provider.

A stable, randomly generated identifier links events from the same installation. The same identifier is used by RevenueCat and our backend, allowing us to relate app usage, subscription status, AI operating costs and problem reports. These records are pseudonymous, not anonymous: they do not require your name or email, but can be linked together. We do not send chat text, goal text, problem report contents or the identities of your selected apps to Mixpanel. When you send a problem report, Mixpanel only receives that a report was sent, where from, its approximate length and whether it included a screenshot. See Mixpanel's Privacy Policy.

Our backend retains technical records including request timestamps, device-key identifiers, app user IDs, model names and input/output token counts for cost monitoring. Safety incident records contain categories and actions such as a blocked or regenerated reply, not the message text.

In Lazely v2, the analytics switch in the app's Profile tab disables product analytics, including onboarding answers and shield events, from both the main app and its Screen Time extensions. Events from the disabled period are not sent if you turn analytics back on. This does not delete previously collected records or stop subscription processing and the backend security and operational records needed when you use AI chat or send a problem report. Contact us to object to processing or request deletion of existing records.

Notifications and support

With your permission, reminders use local notifications generated on your device. If you contact support, we receive your email address and the information you include, and use them to answer your request.

You can also use "Report a problem" in the app. A report contains the text you write, a screenshot if you choose to attach one, your app version and build, your iPhone model, your iOS version, your language and region setting, the screen you sent it from, and your installation's stable identifier. The report form tells you that these technical details are added automatically. Reports are sent through our backend, verified with Apple App Attest, and stored in our Cloudflare-hosted storage. So that we see it promptly, a copy of each report, including any screenshot, is also emailed to our support mailbox through Resend, our email delivery provider. That mailbox is hosted by Google (Gmail). We use reports only to investigate and fix problems and to reply to you, and they are not shared with our analytics provider. Please avoid including sensitive information in the text or the screenshot.

If a report cannot reach our backend, the app offers to send it by email instead. Your mail app then opens a prefilled message containing your text and the same technical details, without the screenshot, and we receive it as a support email together with your email address.

Service providers and international processing

These services process data for the purposes described above. Their infrastructure and support operations may involve countries outside your country or the European Economic Area. Use of an EU analytics endpoint does not mean that every Lazely service processes data exclusively in the EU. Provider terms describe their processing locations and applicable transfer safeguards.

This website is hosted by Vercel and loads fonts from Google Fonts. Visiting it sends ordinary connection information, including your IP address and browser request details, to those providers. See Vercel's Privacy Policy and Google Fonts' privacy information.

Data retention and deletion

Local settings and history remain on your device until you remove them or delete the app. Device backups are managed separately through your Apple settings. Deleting the app does not automatically delete records already held by our backend, Mixpanel or RevenueCat.

Our backend does not maintain a saved conversation history. Its authentication, usage-cost and safety records, and problem reports including any attached screenshot, currently have no automatic time-based deletion schedule: they are kept until we delete them, including at your request. The emailed copies of reports, and reports you send by email yourself, are kept in our support mailbox on the same basis; our email delivery provider keeps its own delivery records under its retention rules. You can contact us to request deletion of records associated with your installation. Subscription, analytics and provider-side records are also subject to the relevant providers' retention rules and any applicable legal requirements. Google's limited safety retention is described in the AI section above.

Children's privacy

Lazely is designed for adults and is not directed at children under 13. If you believe a child has provided personal information through Lazely, contact us so we can investigate and address it.

Your privacy rights

Depending on applicable law, including the GDPR, you may request access, correction, deletion, restriction or portability of your personal data, and object to certain processing. Where processing relies on consent, you may withdraw it. You can also lodge a complaint with the CNIL or your local data protection authority.

Contact lazely.app@gmail.com to exercise these rights. When possible, include the User ID available in the app's Profile tab before uninstalling, so we can locate pseudonymous records. We may need additional information to verify and handle your request. We normally respond within one month, subject to the extensions allowed by applicable law.

Changes to this policy

We may update this policy from time to time. Changes will be posted on this page with an updated date.

Contact

If you have questions about this privacy policy, contact us at lazely.app@gmail.com.

🦥