Legal

Privacy Policy

This policy covers the WatchFaceKit watch faces you install on your Garmin device and the WatchFaceKit website. The short version: the watch faces do not collect, store, or transmit personal data to us. They only read on-device Garmin data when needed to display selected fields on your watch. The website keeps data to the minimum needed to run and protect it. The only exception is the optional Custom Photo feature: faces that support it exchange a pairing code and the background you choose with our server, as described below.

Who operates this site

The WatchFaceKit watch faces and this website are operated by Nadzeya Yashchuk (sole proprietor), Wals-Siezenheim, Austria, who is also the data controller. Full legal details are available on our Impressum page. For any privacy question, contact contact@nadzeyayashchuk.com.

The watch faces on your Garmin

Our watch faces are Connect IQ apps that run on your Garmin device. To display the fields you choose, a watch face may read on-device Garmin data such as time and date, heart rate, steps, calories, battery level, altitude, sunrise/sunset, location-derived information, weather, notification count, or similar activity metrics, depending on the face and enabled settings.

This data is used only to render the watch face on your device. We do not collect, store, log, transmit, sell, or share this information. The watch faces do not send this data to our servers, do not use advertising SDKs, do not create user accounts, and do not include our own analytics.

Some fields require Garmin Connect IQ permissions, such as Sensor History, Positioning, User Profile, or Complication data. These permissions are used only for the selected watch face features.

Your settings, such as accent color or selected data fields, may be saved as app settings by Garmin Connect on your device or Garmin account. These settings are handled by Garmin under Garmin's own privacy policy, not by us.

Removing a watch face removes its access to device data.

The sections below describe the separate, minimal data handling for the WatchFaceKit website.

Custom Photo

Some watch faces let you use your own photo as the background. This is the only case in which a watch face communicates with our server, and it never sends health, activity or location data.

Pairing. On first start the watch face creates a random installation identifier and, through Garmin Connect on your phone, sends it to our server with the screen size and shape, the device part number (used to show your watch model) and the watch face name. The server replies with a 6-character pairing code. No name, email address or Garmin account is involved.
Editing happens on your phone. On watchfacekit.com/photo/ you choose and frame a photo in your browser. The original photo is never uploaded, only the finished background sized to your watch screen (typically 50–150 KB, split into small tiles).
Deleted after delivery. The watch face checks our server about every five minutes, downloads the background and confirms receipt. On confirmation the uploaded image is permanently deleted from our server immediately. An image that is never picked up is deleted automatically within 6 hours.
What we keep. The installation identifier, pairing code, screen size and shape, part number, watch face name and timestamps (first pairing, last check-in, last upload and delivery), so you can change the photo later without pairing again. The code shown on the watch works once and changes every 30 minutes. Your browser keeps a random session key for your watch in local storage; Forget this watch on the Custom Photo page removes it and ends that session.
On your watch. The background is stored in the watch face's own storage on your device and is removed when you choose Remove photo or uninstall the watch face.
Abuse protection. To limit automated requests we use a daily keyed hash of your IP address. The raw IP address is not stored, and these records are deleted after two days.

Images are stored in Cloudflare R2 and are deleted permanently, with no backup copy kept. Pairing records are stored in Cloudflare D1, whose automatic point-in-time backups can retain deleted records for up to 30 days. Please upload only images you have the right to use. To have a pairing record deleted, email us with the pairing code shown on your watch.

If you sign up for our newsletter, for example in the watch face catalog, we process your email address, the language of the page you signed up on and the time of sign-up to send you news about new watch faces and updates. Sign-up uses double opt-in: you first receive an email with a confirmation link and join the list only after clicking it; unconfirmed addresses receive no newsletters. The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with the unsubscribe link in every newsletter or by writing to us, and your address is then removed from the list.

Emails are sent through Resend (Resend, Inc., USA), which stores the address on our behalf as a processor under its data processing agreement, including the EU Standard Contractual Clauses for transfers outside the EU. With the address we store the language of the page, the version of the sign-up text you agreed to and the time you confirmed. Addresses that are not confirmed within 48 hours, and addresses that unsubscribe, are deleted automatically shortly afterwards. To prevent abuse of the form and to make each confirmation link single-use, we keep one-way hashes of your IP address and email address, with the time of the last attempt or confirmation, for up to two days; they cannot be turned back into the original values.

Buying on this site

Some watch faces and packs can also be bought directly on this website. The checkout is run by Lemon Squeezy (Lemon Squeezy, LLC, USA), which sells them to you as our reseller (Merchant of Record). Lemon Squeezy collects your name, email address, billing details and payment information and processes them under its own privacy policy as a separate controller; we never see your card or account details.

What we receive. From Lemon Squeezy we receive your order number, email address, what you bought, the amount, currency and tax, whether it is a test order, and later changes such as a refund. We use them to give you access to your watch faces (Art. 6(1)(b) GDPR) and keep the order records for as long as the purchase is available to you or the law requires.
Sign-in by email. After payment, and whenever you ask for it, we send you a sign-in link through Resend (see Newsletter). The link works once and for 24 hours; we store only a one-way hash of it. Signing in sets one cookie, wfk_s, which keeps you signed in for 30 days. It is strictly necessary for the page you asked for and is used for nothing else; signing out removes it. The «My watch faces» page remembers the watch model you picked in your browser's local storage.
Downloads. When you download or install a file, we record the watch face, the watch model, the file version and size, your email address and the time, to apply fair-use limits and to help if something goes wrong. These records are deleted after 90 days.
Abuse protection. To limit automated requests we keep keyed hashes of your IP address and email address, with the time of the attempt, for up to two days.
No tracking in your account. The sign-in and «My watch faces» pages load no analytics, no feedback widget and no third-party scripts. On a pack page the checkout script and the checkout window come from Lemon Squeezy, so your browser connects to Lemon Squeezy when you open such a page.
Payment notifications. The notifications Lemon Squeezy sends us about an order are deleted after 30 days; only the reference that stops an order from being processed twice is kept.

Information the website collects

The website does not require accounts and does not ask you to submit personal profiles. Only if you buy on this site do you sign in, with a link sent to your email address (see Buying on this site).

When you visit the website, our infrastructure may process standard technical data in access logs, such as IP address, browser type, device information, referring page, requested pages, timestamps, and similar technical request data. This is used for security, troubleshooting, and keeping the service running.

How information is used

Technical data is used only to operate, secure, debug, and improve the website. This includes serving pages, preventing abuse, diagnosing errors, and understanding broad usage trends.

We do not sell your data. We do not build advertising profiles.

Cookies and local storage

The site does not use advertising cookies. Analytics cookies from Google Analytics (see below) are used only where analytics is on: in the EU/EEA, the UK and Switzerland only after you accept them in the cookie banner. Your browser's local storage may also hold lightweight preferences (such as display settings and your cookie choice) on your device. You can clear it at any time through your browser settings. If you use Custom Photo, it also keeps a random session key for your paired watch.

Third-party services

Hosting & delivery: the site is served through Cloudflare, which processes standard technical request data to deliver and protect the site.
Analytics: we use Google Analytics 4 (Google Ireland Limited; Google LLC, USA) to understand aggregate usage, such as which pages and watch faces are viewed and which store links are clicked. Visitors in the EU/EEA, the UK and Switzerland see a cookie banner: analytics cookies are set only after you accept. Until then, or if you decline, Google receives only cookieless signals (for example that a page was viewed) without identifiers stored on your device (Google Consent Mode). Elsewhere analytics is on by default. Advertising storage and features are always off. In the EU the legal basis is your consent (Art. 6(1)(a) GDPR); you can withdraw it by clearing this site's data in your browser, after which the banner appears again. Google may process data in the USA under the EU–US Data Privacy Framework.
Fonts: all web fonts are served from our own domain; your browser does not contact a third-party font service.
Feedback button: the feedback button on every page is our own tool. If you send feedback, we store your rating, the options you picked, your message and, only if you enter it, your email address, together with the page address, the page language, your browser's user-agent string and a keyed hash of your IP address that limits spam (the IP address itself is not stored). It is stored on Cloudflare, read only by us to improve the site and to answer you, and deleted on request.
Connect IQ Store: when you choose to install or purchase a watch face, you leave this site and the transaction is handled by Garmin's Connect IQ Store under Garmin's own privacy policy. We do not receive your payment details.
Lemon Squeezy: purchases made on this site — see Buying on this site.

Children's privacy

This site is intended for a general audience and is not directed at children. We do not knowingly collect personal data from children.

Your rights

If you are in the EU/EEA, the GDPR gives you the right to access, rectify, or erase your data, to restrict or object to processing, and to data portability. You also have the right to lodge a complaint with the Austrian Data Protection Authority (Datenschutzbehörde). To exercise any right, email contact@nadzeyayashchuk.com.

Policy updates

We may update this policy as the site evolves. Material changes will be reflected here with a new date below.

Contact

Questions about this policy: contact@nadzeyayashchuk.com.

Effective date: 14 June 2026 · Last updated: 21 October 2026

Watch face ratings

If you rate a watch face, we store your 1–5 score, the watch face identifier, a random browser voter identifier and timestamps in Cloudflare D1. Your browser stores the voter identifier and your selected scores in local storage so you can update a vote without adding another. Ratings are shared across language versions of the same face. Only the average and count are public; individual voter identifiers are not published. We use a daily keyed hash of your IP address to limit automated submissions; the ratings database does not store your raw IP. Old rate-limit records are removed during subsequent submissions. Ratings remain until removed; contact us at the address above to request removal and include your browser voter identifier if available.