WATCH LUX

Privacy Policy

Effective: August 5, 2026
Last updated: September 26, 2026

WatchLux Faces ("we," "our," or "the app") is published by Frame Sixty Labs LLC. We respect your privacy and are committed to being transparent about how we handle your data.

This policy covers WatchLux Faces for iPhone and Apple Watch, and WatchLux for Android phones and Wear OS watches. Where a practice applies to only one platform, the section says so.

Information We Collect Directly

We do not ask you for personal information. WatchLux Faces does not require you to create an account, and we do not ask for your name, email address, phone number, or any other directly identifying information.

Some information is collected automatically by the third-party services built into the app, including our analytics provider and, for users without WatchLux+, our advertising provider. These are described below.

This applies equally to the Android and Wear OS app.

Device Permissions

WatchLux Faces may request the following optional permission:

  • Notifications: Used to tell you about new watch faces and collections. You can turn notifications off at any time in Settings → Notifications → WatchLux.

This permission is optional. The app works fully without it. WatchLux Faces does not request access to your location, contacts, photos, camera, or microphone, and it does not ask for App Tracking Transparency permission.

On Android and Wear OS

The Android app does not request location, contacts, photos, camera, or microphone access. It may request:

  • Notifications (phone): Used to tell you about new watch faces and collections. Optional. You can turn notifications off at any time in your phone's settings.
  • Watch face installation (watch): Lets the WatchLux watch app install the watch faces you choose on your phone, and, if you allow it, make the newly installed face your active watch face. Your watch asks for this once. The app works without the "set as active" permission; you can then select the face yourself on the watch.

Subscription & Purchase Data

If you purchase WatchLux+ (the annual subscription, the weekly subscription, or the one-time Lifetime purchase), the transaction is processed entirely by Apple through the App Store. We do not have access to your payment information, credit card number, or Apple ID. From Apple, we only receive confirmation that a valid entitlement exists. When you start, complete, cancel or restore a purchase, the app also sends an event to Firebase Analytics with the product, the plan and whether it is a free trial (and, if a purchase fails, a short error description). These events are tied to the identifier for your installation of the app described under Analytics below.

On Android and Wear OS

On Android, WatchLux+ purchases are processed entirely by Google through Google Play Billing. We do not have access to your payment information, card number, or Google account details.

To confirm that a purchase is valid, the app sends the Google Play purchase token to our server, which checks it with Google Play. Our server keeps a record of the verified purchase: a hashed form of the purchase token, the product, its status, and its expiry date. This lets refunds, cancellations, and renewals take effect in the app. After verification, the app stores a short-lived access grant on your phone in encrypted storage. The grant contains no personal information.

Device Integrity

On Android and Wear OS

To protect the watch face catalog from abuse, requests from the Android app to our server are checked with Firebase App Check using Google Play Integrity. This sends signals about the integrity of your device and of the app to Google, which returns a token that our server verifies. It does not identify you personally, and we do not receive device identifiers from it.

Analytics

WatchLux Faces uses Google Firebase Analytics to help us understand how the app is used so we can improve it. All data is handled under Google's privacy practices as a data processor on our behalf; we never combine it with other personal data.

Firebase Analytics (usage analytics)

We use Firebase Analytics (provided by Google) to collect usage data, tied to an identifier for your installation of the app, so we can improve the app. This includes:

  • App events, such as which watch faces you view or add to your Apple Watch and whether adding succeeds, onboarding steps and the choices you make there (including the watch model and styles you pick), when the subscription offer is shown or closed, the purchase events described above, notification prompts and opens, and which Home banners you open
  • Error information, such as a short description of why adding a watch face or a purchase failed
  • Device information (iOS version, device model, language, country)
  • Approximate location (such as your country or city, derived from your IP address)
  • Identifiers for your installation of the app: the Firebase app instance ID and Apple's identifier for vendor (IDFV). They are not used to track you across other companies' apps or websites.
  • Session metrics (when the app is opened and for how long)

Firebase Analytics cannot obtain the IDFA (Apple's advertising identifier): WatchLux Faces never asks for App Tracking Transparency permission, so iOS provides an all-zero value instead. Firebase Analytics also does not use Google Signals in WatchLux Faces. We use analytics data only to understand and improve the app: we do not use it for advertising and do not share it with advertisers. The ads shown to users without WatchLux+ are served separately by Google AdMob, as described in Advertising (Google AdMob) below.

On Android and Wear OS

The Android app uses Firebase Analytics in the same way. On Android it collects:

  • App events (for example, which watch faces are viewed or installed and in which style, whether the subscription offer was shown or dismissed, and the outcome of a purchase, such as the plan type and whether a free trial started)
  • Device information (Android version, device model, app version, language, country)
  • Approximate location (such as your country or city, derived from your IP address)
  • An identifier for your installation of the app (the app instance ID, not used for cross-app tracking)
  • Session metrics (when the app is opened and for how long)

On Android, Firebase Analytics data is not used for advertising. Advertising in the Android app is handled separately by Google AdMob, described below.

Crash reporting

WatchLux Faces for iPhone and Apple Watch does not use Firebase Crashlytics.

On Android and Wear OS

The Android and Wear OS app does not use Firebase Crashlytics.

How to opt out

Firebase Analytics is enabled by default, and WatchLux Faces does not have an in-app setting to turn it off. iOS does not offer a system-wide switch that turns off Firebase Analytics for an individual app: the Share iPhone Analytics setting only controls what your device shares with Apple. Deleting the app stops all collection on your device. To ask us to delete the analytics data linked to your app installation, email us at the address below.

On Android and Wear OS

Android does not offer a system-wide switch that turns off Firebase Analytics for an individual app. Uninstalling the app stops all collection on your device. To ask us to delete the analytics data linked to your app installation, email us at the address below.

Advertising (Google AdMob)

If you do not have an active WatchLux+ subscription or a Lifetime purchase, WatchLux Faces shows banner advertisements. WatchLux+ removes ads: subscribers (including during a free trial) and Lifetime owners do not see them. Ads are served by Google AdMob (provided by Google LLC) through the Google Mobile Ads SDK included in the app. We do not choose the individual ads you see, and we do not receive information from Google that identifies you personally.

What the Google Mobile Ads SDK may collect

To serve and measure ads, limit how often you see the same ad (frequency capping), and prevent fraud, the Google Mobile Ads SDK may collect:

  • Device identifiers, such as Apple's IDFV and other app- or developer-scoped identifiers. The IDFA (Apple's advertising identifier) is not available to the SDK: WatchLux Faces never asks for App Tracking Transparency permission, so iOS returns an all-zero value in its place, and the SDK does not send the IDFA with ad requests.
  • Approximate location, derived from your IP address
  • Advertising data (for example, which ads were shown and whether they were tapped)
  • Product interaction data (for example, app launches and taps)
  • Diagnostic and performance data (for example, how long ads take to load and crash logs)

Your ad privacy choices

In the European Economic Area, the United Kingdom and Switzerland, Google's User Messaging Platform asks for your consent before personalized ads are shown. You can review or change your choice in the app under Settings → Ad privacy options whenever ads can be shown to you.

For users without WatchLux+, the app checks with Google's User Messaging Platform which ad privacy choices apply where you are. To do this, the User Messaging Platform uses your approximate location (derived from your IP address), records how you interact with its privacy messages, and collects basic performance data. Your choices are stored on your device.

The Ad privacy options entry appears in the app's Settings only when Google's User Messaging Platform determines that privacy laws in your region require it, such as in the European Economic Area, the United Kingdom, Switzerland and certain US states, and only while ads can be shown to you: it is hidden for WatchLux+ subscribers. If you live in one of those US states, you can use it to opt out of the sale or sharing of your personal information for advertising ("Do Not Sell or Share My Personal Information").

On any iPhone, you can also turn off Settings → Privacy & Security → Tracking → Allow Apps to Request to Track, which keeps the IDFA unavailable to all apps, and turn off Settings → Privacy & Security → Apple Advertising → Personalized Ads for ads delivered by Apple. Subscribing to WatchLux+ removes ads from the app entirely.

Google's use of this data is described in the Google Privacy Policy and in How Google uses information from sites or apps that use our services.

On Android and Wear OS

The Android app shows banner advertisements to users who do not have an active WatchLux+ subscription or a Lifetime purchase. Subscribers never see ads. Ads are served by Google AdMob (provided by Google LLC). To serve and measure ads, the AdMob SDK may collect:

  • The Android Advertising ID (a resettable identifier you control in your device settings)
  • Device information (Android version, device model, app version, language)
  • Approximate location (such as your country or city, derived from your IP address)
  • Ad interaction data (which ads were shown and whether they were tapped)

In the European Economic Area, the United Kingdom and Switzerland, we ask for your consent before personalized ads are shown, and you can change your choice at any time in the app. You can also opt out of ad personalization or reset your Advertising ID in your Android settings under Google > Ads. Google's use of this data is described in the Google Privacy Policy and "How Google uses information from sites or apps that use our services".

Push Notifications

If you allow notifications, Apple's push notification service and Firebase Cloud Messaging (provided by Google) assign your device a registration token so we can send announcements about new watch faces and collections to everyone who has opted in. To deliver notifications, Firebase Cloud Messaging also collects basic device information (such as device model, iOS version, language and time zone) and diagnostic data. The token is not linked to your name or any account. Turning notifications off stops these messages.

On Android and Wear OS

If you allow notifications, Firebase Cloud Messaging (provided by Google) assigns your phone a registration token so we can send announcements about new watch faces and collections. The token is managed by Google's messaging service and is not linked to your name or any account. Turning notifications off stops these messages.

Data Storage

Your in-app preferences (synced watch faces, filter settings, selected watch model) are stored locally on your device using Apple's standard storage mechanisms. The preferences themselves are not uploaded to our servers, but some of the same choices are also sent to Firebase Analytics as the usage events described above: the watch faces you add, and the watch model and styles you pick during setup.

On Android and Wear OS

On Android, your in-app preferences (the styles you picked when you started, your chosen watch face styles, your selected watch model, notification choices, and a record of the faces you have installed) are stored locally in the app's private storage on your phone. The access grant described above is stored in encrypted storage. The app also keeps a few recently downloaded watch face packages on your phone so they don't need to be downloaded again. None of this is transmitted to a server, except as described in this policy.

Watch Face Syncing

When you add a watch face, the face data is transferred directly from your iPhone to your Apple Watch using Apple's native APIs. The watch face catalog and artwork are downloaded from our servers (hosted on Google Firebase) on demand; no personal data is sent along with that request.

On Android and Wear OS

When you add a watch face on Android, your phone asks our server for a short-lived download link for that face and style. That request contains the face and style, your access grant, and the App Check token described above. Your phone then downloads the watch face package and sends it to your paired Wear OS watch over Bluetooth using Google's Wear OS APIs, and the watch installs it. The watch face catalog and preview images are loaded from Google Firebase. No personal data is sent with these requests.

Third-Party Services

WatchLux Faces interacts with the following third parties:

On Android and Wear OS

The Android and Wear OS app interacts with Google only:

Data Retention

Analytics event data is retained by Firebase for up to 14 months. Data collected by the Google Mobile Ads SDK is retained by Google in accordance with Google's Privacy Policy. Notification tokens are kept while notifications are enabled. Because no user account exists, we do not hold a user record tied to your name or email address. Deleting the app stops future analytics collection, and subscribing to WatchLux+ stops ads from being requested. To ask us to delete the analytics data linked to your app installation, email us at the address below.

On Android and Wear OS

Analytics event data from the Android app is also retained by Firebase for up to 14 months. Purchase verification records are kept for as long as the purchase exists, and afterwards for the period required by tax and accounting law. The access grant on your phone expires within 24 hours and is renewed while you use the app. Notification tokens are kept while notifications are enabled.

Children's Privacy

WatchLux Faces does not knowingly collect personal information from children under 13. The app does not require any personal information to use, and we do not combine the analytics or advertising data described above with personal identifiers.

This applies equally to the Android and Wear OS app.

Your Rights

We do not ask for directly identifying information and have no user accounts, so we cannot look up an individual record by name or email address. Device identifiers and approximate location collected by Firebase Analytics and Google AdMob, described above, may be personal information under laws such as the GDPR and US state privacy laws. To ask us to delete the analytics data linked to your app installation, or if you have questions about the analytics data Firebase processes, contact us using the address below.

Where privacy laws in your region require it (such as in the European Economic Area, the United Kingdom, Switzerland and certain US states), your advertising choices, including consent to personalized ads and opting out of the sale or sharing of personal information, are available in the app under Settings → Ad privacy options whenever ads can be shown to you. For data Google collects for advertising, you can also use the controls described in Google's Privacy Policy.

On Android and Wear OS

You can manage or cancel a WatchLux+ subscription at any time in Google Play under Payments & subscriptions. To ask us to delete a purchase verification record, or the analytics data linked to your app installation, email us at the address below. Some purchase records may need to be kept where tax or accounting law requires it.

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be reflected in the app with an updated effective date.

Contact

If you have questions about this privacy policy, contact us at:
[email protected]