Privacy Policy

This Privacy Policy applies to the LOCKR mobile application on both iOS (distributed via the Apple App Store) and Android (distributed via the Google Play Store). Where a practice differs by platform, that difference is called out.

1. Information Collection

Required Permissions (iOS):

• Family Controls / Screen Time access: To monitor and manage your device usage patterns and enforce app blocking schedules
• Notifications: To send you reminders and alerts
• App blocking permissions (ManagedSettings / DeviceActivity): To enable blocking and shielding functionality

Required Permissions (Android):

• Usage Access (PACKAGE_USAGE_STATS): To read app usage statistics so we can monitor and manage your device usage patterns and enforce app blocking schedules
• Accessibility Service: To detect when blocked apps are launched and apply LOCKR's blocking and shielding overlays
• Display over other apps (SYSTEM_ALERT_WINDOW): To present LOCKR's blocking screens on top of restricted apps
• Notifications (POST_NOTIFICATIONS): To send you reminders and alerts
• Foreground service / Battery optimization exemption: To keep blocking active reliably in the background
• Health Connect (optional, read-only): To read your Steps, Active Calories Burned, and Distance so LOCKR can automatically track progress on personal goals you choose to set in those categories. Health Connect access is optional and only requested if you create an auto-tracked goal

2. Data Usage and Protection

Your detailed screen time, blocking, and other sensitive in-app data is:

• Used to provide usage insights, coach interactions, and blocking schedules
• Processed primarily on your device for core blocking and screen time functionality
• Supplemented by limited subscription, configuration, and analytics telemetry described below
• Not shared with third parties for advertising purposes
• Not sold to any parties

The telemetry described in this policy is used to:

• Operate the App and its subscription features
• Understand setup completion, feature adoption, and product usage
• Improve reliability, performance, support, and fraud prevention

3. Data Collection and Usage

3.1 Data Linked to Your Identity

The following data may be collected and linked to your identity:

• First name (used to personalize your coach experience)
• Chat messages sent to your AI coach
• Subscription-related timestamps and status associated with your account or app instance, such as first seen, trial start, and subscription start

Coach conversation data:

• Your messages to the AI coach are sent to a third-party AI processing provider to generate responses
• Messages are used solely to generate coach responses
• Third-party provider terms apply to that processing
• No conversation history is stored on our servers

3.2 Data Not Linked to Your Identity

The following product interaction, subscription, and operational data may be collected and is generally not linked to your identity:

• Subscription lifecycle data, including trial start, subscription start, renewal or expiration status, refund-related events, and related timestamps
• Onboarding and setup completion status
• Permission and authorization status, including whether device activity and blocking permissions were granted and whether notifications were enabled
• Feature configuration status, including whether a coach was configured, blocked apps count, whether blocking is enabled, and protected days count
• Engagement metrics, including conversations opened count, messages sent count, unlocks granted count, total minutes granted, total minutes used, app open count, and last app use timestamp
• Paywall and purchase flow metrics, including transaction abandoned timestamp and timer-related paywall state
• Anonymous analytics data for app improvement

Product interaction and operational data is collected and used solely for:

• App functionality, subscription management, entitlement verification, fraud prevention, and security
• Enabling or disabling features based on permission state and user setup
• Understanding usage of blocking, coach, and unlock features to improve the App
• Understanding paywall performance and abandoned purchase flows
• Ensuring server uptime, minimizing app crashes, and improving scalability and performance
• Providing customer support

3.2.1 Refund Request Data Sharing

By using LOCKR and making in-app purchases, you consent to LOCKR sharing limited purchase and usage data with Apple (for App Store purchases) or Google (for Google Play purchases) if you request a refund, solely to help process and evaluate the refund request. This may include whether purchased features were used, your subscription status, and related app usage associated with the purchase. We do not share unrelated personal content with Apple or Google for this purpose.

3.3 Third-Party Services

LOCKR uses third-party service providers for limited functions such as AI response generation and subscription or paywall operations.

Apple:

• May receive limited purchase, subscription, refund-related, and related usage data in connection with App Store distribution, in-app purchase and subscription processing, fraud prevention, and, if you request a refund, refund request evaluation
• Processes data under Apple's own platform terms and privacy practices

Google (Google Play / Android):

• May receive limited purchase, subscription, refund-related, and related usage data in connection with Google Play distribution, Google Play Billing in-app purchase and subscription processing, fraud prevention, and, if you request a refund, refund request evaluation
• May receive limited install, crash, and diagnostic information through Google Play services
• Processes data under Google's own platform terms and privacy practices

AI processing provider:

• Processes coach chat messages to generate AI responses
• Your first name and chat messages are transmitted for processing
• Used solely for coach conversation functionality
• Subject to the provider's applicable processing terms

Subscription and paywall provider:

• Manages paywall, purchase, and subscription experiences
• May process subscription lifecycle events, renewal or expiration status, refund-related events, transaction abandonment events, and timer-related paywall state
• Collects product interaction data needed for paywall optimization, subscription management, and analytics
• Does not receive your coach message content or raw device activity history for advertising purposes

Infrastructure and analytics providers:

• Support app reliability, crash reduction, performance monitoring, and analytics
• Used solely to support app functionality, performance, and improvement

3.4 Advertising and Marketing Measurement

LOCKR runs paid marketing campaigns on Meta platforms (Facebook and Instagram) and on TikTok. To measure the performance of those campaigns, attribute installs and subscriptions, optimize ad delivery, and build advertising audiences, LOCKR uses the Meta and TikTok measurement tools described below. These tools operate on the LOCKR website and within the LOCKR mobile apps (iOS and Android).

Meta (Facebook / Instagram):

• The Meta Pixel runs on the LOCKR website to record events such as page views, content views, leads, and other conversion events
• The Meta SDK and/or App Events API runs in the LOCKR mobile apps to record events such as app install, app open, onboarding completion, trial start, subscription start, and subscription renewal
• Data shared with Meta may include event names and timestamps, hashed identifiers (such as hashed email or device identifier where available), IP address, user agent, device and platform information, advertising identifiers (IDFA on iOS where you have allowed App Tracking Transparency, or AAID on Android subject to your device settings), referrer URLs, and aggregated subscription/conversion values
• Meta uses this data to attribute conversions, measure ad performance, deliver and optimize ads, build lookalike and custom audiences, and detect fraud, in line with Meta's own terms and privacy policy

TikTok:

• The TikTok Pixel runs on the LOCKR website to record events such as page views, content views, and conversion events
• The TikTok SDK and/or Events API runs in the LOCKR mobile apps to record events such as app install, app open, onboarding completion, trial start, subscription start, and subscription renewal
• Data shared with TikTok may include event names and timestamps, hashed identifiers (such as hashed email or device identifier where available), IP address, user agent, device and platform information, advertising identifiers (IDFA on iOS where you have allowed App Tracking Transparency, or AAID on Android subject to your device settings), referrer URLs, and aggregated subscription/conversion values
• TikTok uses this data to attribute conversions, measure ad performance, deliver and optimize ads, build custom and lookalike audiences, and detect fraud, in line with TikTok's own terms and privacy policy

Important limits on what advertising partners receive:

• We do not share your AI coach conversation content with Meta or TikTok
• We do not share the specific apps you have blocked, your raw device activity history, or your individual screen time content with Meta or TikTok
• Advertising events are limited to install, install attribution, subscription lifecycle, and high-level funnel events used to measure marketing performance

Your choices regarding advertising data:

• iOS: When prompted by App Tracking Transparency, you can choose "Ask App Not to Track" to prevent the IDFA from being shared with Meta and TikTok. You can also change this in Settings > Privacy & Security > Tracking
• Android: You can reset or delete your Advertising ID and opt out of personalized ads in Settings > Google > Ads (or your device's equivalent setting)
• Web: You can use your browser's cookie controls or "Do Not Track" / Global Privacy Control settings, and you can manage Meta and TikTok ad preferences in your account settings on those platforms
• You can adjust ad preferences directly in your Meta account (Accounts Center > Ad preferences) and TikTok account (Settings > Ads)

All other third-party data collection (outside of the Meta and TikTok advertising measurement described above) is:

• Used only for app functionality and improvements
• Not used for advertising or marketing
• Not sold or shared with other parties

Your raw device activity content and detailed blocking configuration remain:

• Stored primarily on your device
• Separate from the aggregate counts, timestamps, and subscription telemetry listed above
• Not transmitted to third parties for advertising
• Private and protected subject to the limits described in this policy

4. Health Connect Data (Android)

On Android, LOCKR optionally integrates with Health Connect to support personal goals that are automatically tracked (for example, a daily step goal). Health Connect access is only requested if you choose to create a goal in a category that is auto-tracked. You can decline, and LOCKR remains fully functional — goals you set in those categories will simply require manual progress entry.

4.1 What data is accessed

If you grant Health Connect permissions, LOCKR reads only the following data types, read-only:

• Steps (android.permission.health.READ_STEPS)
• Active Calories Burned (android.permission.health.READ_ACTIVE_CALORIES_BURNED)
• Distance (android.permission.health.READ_DISTANCE)

LOCKR does not write any data to Health Connect, and does not request any other Health Connect data types (such as heart rate, sleep, weight, nutrition, menstrual, or medical records).

4.2 Why this data is read

Health Connect data is used solely to display your current progress against the personal goals you have configured in LOCKR (for example, "7,500 / 10,000 steps today"). It is not used for advertising, profiling, sale, or any purpose beyond surfacing your progress within the app.

4.3 How the data is used and stored

• Health Connect data is read on-demand on your device and aggregated locally (for example, summed for the current day or week)
• Aggregated progress values are kept only in memory for display, or in local app storage to render goal progress between app launches
• Raw Health Connect records are not uploaded to any LOCKR server
• Raw Health Connect records are not sent to our AI coach provider, subscription provider, analytics providers, or any advertising partner (including Meta and TikTok)
• Health Connect data is not sold or shared with third parties

4.4 Retention and deletion

LOCKR does not retain a separate copy of raw Health Connect records. Locally cached aggregate values used for goal progress remain on your device until you (a) revoke Health Connect permissions for LOCKR, (b) clear LOCKR's app storage, or (c) uninstall the app. To revoke access at any time, open Settings > Security & privacy > More privacy settings > Health Connect > App permissions > LOCKR (the exact path varies by Android version) and turn off the permissions, or open the Health Connect app directly and manage LOCKR's permissions there.

5. Your Rights

You have the right to:

• Delete all local data by uninstalling the app
• Control app permissions through device settings
• Opt out of notifications in device settings

6. Data Retention

Local app data remains until you uninstall the app. Operational analytics and subscription telemetry may be retained for as long as reasonably necessary to operate the App, manage purchases, provide support, prevent abuse, comply with legal obligations, and analyze product performance. Coach conversations are not persisted on any external server.

7. Changes to Privacy Policy

We will notify users of any material changes to this privacy policy through the app.

8. Contact Us

If you have any questions about privacy or data protection, please contact us at lockrappdev@gmail.com.