Deep Horizon

Privacy Policy - Deep Horizon: Pixel Black Hole

Effective date: 2026-09-27

This Privacy Policy applies to 'Deep Horizon: Pixel Black Hole' (package name: 'com.pixelpond.watchface.deephorizon'), developed by Pixelpond. That Google Play package has two parts: the watch face, and a small phone app, “Setup”, which has its own section below. The watch face runs only on your watch. It does not collect, store, transmit, or share any personal user data, usage analytics, location data, sensor data, or device identifiers with the developer or any third parties.

The watch face reads the following information only to render itself:

• Current system time (local clock) to display the custom digital or analogue clock.
• Device battery level to draw the optional battery arc and its low-battery warning tint, only when you switch it on.
• Your configuration selections (colourway, theme, clock mode, and digit font) to render your chosen look.
• Active and ambient state transitions of your Wear OS device to switch between normal and Always-On Display (AOD) modes.

Because the watch face is built using the declarative Watch Face Format, it contains no executable code (android:hasCode="false"), and all rendering is handled locally on your watch by the Wear OS operating system. The watch face sends nothing to Pixelpond, and it contains no advertisements, in-app purchases, analytics or crash reporting.

Phone Setup app. Everything above describes the watch face. The same Google Play package also installs a small phone app, “Setup”, that helps you install and apply the face, and Setup does use the internet. It has no ads, no analytics or crash reporting of its own, and no Pixelpond account. Here is what it does:

• Update check. It downloads our public list of current versions from watchfaces.pixelpond.au. The request carries no account, settings or watch details. Like any web request, it shows our host (Vercel) your IP address and standard request details, which include your Android version and phone model. Our hosting configuration retains runtime logs and request observability data for 30 days. Request records can include your IP address, the country inferred from it, your user agent, the requested path and the response result. We use hosting records to monitor service health, diagnose problems and protect the service.
• Purchase check. Setup asks Google Play for a signed answer about whether your Google account holds this face, and sends it to our purchase checker (Google Cloud, Sydney). The checker asks Google to read it and replies “confirmed” or not. The checker’s log also records Google’s answer for each check, which we use to diagnose problems. Like any web request, it shows Google Cloud your IP address and standard request details, which Google Cloud’s standard request logs record. Google Cloud keeps these request logs and the checker’s log for 30 days, then deletes them. Our checker’s database (Neon, Sydney) keeps a one-time check code with the face’s package name and version, and a hashed form of your IP address (not the address itself), used to limit repeated checks. Each code expires after two minutes and later checks clear expired codes out. We also keep a daily count of checks per face. We never receive your name, email or payment details. Your phone keeps a confirmed result in memory for up to five minutes.
• Google Play. It asks Google Play whether a newer Setup is available, and opens the face’s Play listing when you tap Install or Update.
• Your watch. It uses Google Play services to find your connected watch and, if the Pixelpond app is installed, asks it which version of the face your watch has. That stays between your phone and watch and is not sent to us.
• On your phone. Setup remembers your setup step and your Reduce Motion choice. The Help email button opens a draft in your own email app; nothing is attached or sent until you send it.

If you have questions, contact: support@pixelpond.au

This policy may be updated. The latest version will live at the URL provided in the Google Play listing.