Back to Timezones: World Clock
Timezones: World Clock · Legal

Privacy Policy

Effective date: July 3, 2026

Contents

01

Introduction

This Privacy Policy explains how Timezones: World Clock handles your information. Timezones: World Clock is built and published by VTX Labs. It takes effect on July 3, 2026 and covers only the Timezones: World Clock mobile app.

02

The Short Version

  • Offline-first. No accounts, no login, no backend, no cloud sync, no server database.
  • No analytics, no crash reporting, no ad SDKs, no tracking, and no data brokers.
  • All notifications are local and scheduled on your device. There is no push server.
  • You own your data. Export and import is a local JSON file, with no cloud backup.
  • Two purpose-limited network calls only: RevenueCat for purchases, and Open-Meteo for the hero city's weather (coarse city coordinates, no personal identifiers).
03

What We Store and Where

Everything below is stored on your device only. There is no server copy.

Clocks & places

on-device
  • Saved city references and optional custom label
  • Created timestamp
  • Which city is set as home

Keep the list of cities you track.

Settings

on-device
  • Time format, theme, temperature unit, show-seconds, sort mode
  • Haptics, DST-alerts flag
  • Onboarding and review bookkeeping

Remember your preferences on this device.

Widget selection

on-device
  • The single city every widget displays

Choose which city appears in your widgets.

Widget & Siri shared data

on-device
  • A small JSON blob (city id, label, IANA timezone, offset, format) written to the iOS App Group group.com.vtxlabs.timezones

Lets widgets and Siri render without launching the app. Same device only, never uploaded.

Weather cache

on-device
  • Transient in-memory only (30-minute TTL), never persisted

Briefly cache the hero city's weather. No names, no accounts, no personal profile. Place ids are random local identifiers.

04

What Leaves Your Device

RevenueCat is the payment network surface, processing in-app purchases. RevenueCat receives purchase and subscription transaction data and an anonymous RevenueCat-generated customer ID. It never receives your tasks, pets, cities, names, photos, contacts, or any content. Purchases themselves are processed by Apple (App Store) or Google (Play) under their terms; we never see your card data.

Relevant policies: RevenueCat, Apple, Google.

Open-Meteo

What is sent: Approximate latitude and longitude of the selected city and the temperature unit. No API key, no personal identifier, no device id.

Why: Current temperature and condition for the hero city. Degrades gracefully offline. Open-Meteo policy.

05

Permissions We Request and Why

Notifications

both

“Local DST-change alerts only, requested when you enable the toggle.”

So we can warn you before a daylight saving change. All alerts are local.

App Group, Spotlight & Siri

ios

“App Group group.com.vtxlabs.timezones, Spotlight indexing, Siri App Intents, alternate app icons; ITSAppUsesNonExemptEncryption: false.”

So widgets, Spotlight, and Siri work. All data exchange stays on your device. No location permission: coordinates come from the chosen city record, not device GPS.

Vibrate

android

“VIBRATE”

So alerts can use haptic feedback.

06

Notifications

All notifications are local, scheduled on your device with expo-notifications. There is no push server.

07

Data Retention, Export, and Deletion

You own your data. Export and import is a local JSON file you control. There is no cloud backup and therefore no server-side recovery. Deleting the app removes all of its data from your device.

08

Children's Privacy

These apps are not directed at children under 13, and we do not knowingly collect any data from children.

09

Your Rights (GDPR & CCPA)

Because your data is device-local and not collected by us, you exercise access and deletion rights directly: reset from Settings, or delete the app. We hold no server copy to export or erase, so requests to us cannot surface data we never receive.

10

Changes to This Policy

We may update this policy from time to time. When we do, we will post the new version on this page and update the effective date. Continued use after a change means you accept the updated policy.

11

Contact

Questions about this policy? Email us at contact+timezones-world-clock@vtxlabs.dev.

Questions about Timezones: World Clock?

Contact Support