1. Who handles your data
Sync App Studio is the developer’s operating name. The developer is based in Türkiye. For questions, access requests or deletion requests, contact support@syncappstudio.com. You do not need to create an app account to use the clock.
This policy describes the app and website. Apple, Google and the service providers below also process information under their own policies.
2. Clock settings and photos stay on your device
Clock designs, colors, fonts, favorites, language, main-clock choices, timer settings and other preferences are stored in the app’s local storage.
If you choose a photo background, the app uses the system photo picker and copies the selected image into its own local folder. This feature does not upload your photo or your photo library to Sync App Studio. It does not use the camera. Device backups may include local app data according to your Apple or Google backup settings.
Local preferences and copied backgrounds remain until app data is cleared or the app is removed, subject to your device’s backup and restore behavior. Replacing a background does not necessarily erase earlier local copies.
3. Weather and location
Weather features let you enter a city manually or choose to allow device location access. The app requests a low-accuracy location for local weather; the precision actually provided depends on the operating system and your permissions. It does not continuously track your location in the background.
Your selected city or latitude and longitude are stored locally and sent to OpenWeather when a weather request is made. OpenWeather also receives network information such as your IP address. Your device’s geocoding service may process coordinates to find a city name. Weather results are cached locally.
You can deny or revoke location permission in device settings and enter a city instead. Entering a manual city replaces the stored automatic coordinates. These requests and their service-provider logs are subject to the provider’s retention rules.
4. App usage analytics
Some app versions use Google Analytics for Firebase to understand app use and improve the product. Events can include onboarding, clock selection and favorites, sound selection, purchase-screen interactions, and purchase or restoration outcomes. Event fields can include a clock or feature identifier, screen or source, and access tier.
The analytics SDK can process an app-instance identifier, app and operating-system version, device characteristics and usage information. Pseudonymous identifiers are not the same as fully anonymous data. Clock-background photos and weather coordinates are not intentionally included in our analytics events.
In versions that offer the Share usage analytics control, analytics stays off until you explicitly allow it. You can decline without losing free or paid features, or withdraw consent in Settings at any time. Turning it off stops future analytics collection and resets locally stored analytics data and the app-instance identifier; it does not by itself delete data already held by Google. Advertising storage, ad personalization and advertising user-data consent remain disabled. Older releases may enable analytics automatically and may not have this control. Contact support@syncappstudio.com about your version or to request deletion of data we can identify. Operating-system permission controls may have a different scope and do not necessarily disable Firebase Analytics.
Analytics retention depends on the settings of the Google Analytics property and Google’s processing and deletion rules. We do not promise that uninstalling the app immediately deletes data already sent to a provider.
5. Purchases and clock recovery
Apple App Store or Google Play handles payments. Sync App Studio does not receive your payment-card number. The app reads store purchase results and keeps access rights locally to provide purchased features and restore eligible purchases.
For individual-clock recovery, our Firebase Cloud Functions service verifies an Apple signed transaction or a Google Play purchase token. Firestore stores the relevant store, app and product identifiers, transaction identifier or purchase token, purchase time, clock identifier, recovery key and its hash, verification timestamps and redemption count. Network requests and server logs can also contain technical connection information.
These records support purchase verification, recovery and prevention of duplicate or invalid claims. They are retained while needed to maintain or verify the purchased access, handle refunds or disputes, or meet applicable recordkeeping obligations. Contact us to request deletion. Removing a recovery record may prevent that recovery key from working; it does not remove records held independently by Apple or Google.
Keep recovery keys private. A person who has a valid key may be able to restore its clock. Do not publish keys or include them in public screenshots.
6. Sounds and music
When you play an online sound or music channel, the app requests an audio file from its host. Hosts can receive your IP address, requested URL and ordinary connection information. Sources vary by channel and can include Wikimedia, WNoise, OpenGameArt, Freesound, rainsoundsforsleeping.com and oceansoundsforsleeping.com.
The clock app does not need microphone permission for these channels and does not record audio. Each external host controls its own network logs and retention.
7. Notifications and live activities
Stopwatch, timer and Pomodoro alerts use the operating system’s notification features. On supported Apple devices, Live Activities can display session information. You can manage notification and Live Activity permissions in device settings. Clock or session information used by these features is processed on the device; these functions do not require us to upload your session history.
8. This website and support messages
The website uses local browser storage to remember your language choice. It has no advertising or analytics script added by Sync App Studio. Firebase Hosting processes technical request information, including IP addresses, to deliver the site and protect it from abuse. Google states that Hosting retains IP data for a few months.
If you email support, we receive your email address, message and any attachments you choose to send. We use these to answer your request and investigate the issue. Send only information needed for the request, and avoid passwords, card details or unnecessary sensitive information.
Support correspondence is retained while needed to resolve and follow up on your request, handle a purchase dispute, or satisfy a legal obligation. You can request deletion by email. There is no automatic support-mail deletion schedule currently stated in this policy.
10. Your choices and requests
You can change app preferences, select a manual weather city, manage device permissions, and clear local app data. The website’s saved language can be removed through browser site-data settings.
You may request access, correction, deletion or withdrawal of consent by emailing support@syncappstudio.com. Depending on your jurisdiction, you may have additional rights, including objection, restriction or a complaint to a competent data-protection authority.
Tell us which app and platform you use and what data or request is involved. We may ask for limited information to locate a record and verify your request. Do not send your Apple or Google password. Some records must be retained for a legal obligation or an unresolved purchase dispute; we will explain applicable limits.
11. Children
The apps are general-purpose clock tools and are not specifically directed to children. We do not knowingly ask children to provide personal information. If you believe a child has provided information that should be removed, contact us so we can investigate. App-store content age ratings do not replace parental choices or privacy protections.
12. Changes to this policy
We update this page when our data practices change and revise the date above. Material changes will be communicated through the app or another appropriate channel. We will seek any additional permission required before introducing a new data use. Reading or continuing to use this policy is not a substitute for an operating-system permission or consent where one is required.