Privacy Policy

Last updated: October 10, 2026

Savvy Time provides time zone, calendar, timer, and related tools through Savvytime.com, browser extensions, and the Savvy Time mobile apps for iOS and Android. This privacy policy explains how information is collected, used, and shared when you use those services.

Website information

We collect information you choose to send us, such as your name, email address, subject, and message when you use the contact form.

We also collect information automatically when you use the site, including device and browser information, pages visited, approximate location derived from network information, referring pages, and interaction data. Some site preferences, such as time format, theme, calendar week start, and calendar display options, may be stored in your browser using cookies or local storage.

If you choose to send a feedback report from a converter or local-time page, we receive your message, an optional reply email, an optional screenshot you explicitly include, and bounded page and technical context needed to reproduce the page state. Feedback is delivered to [email protected] and kept as one support email record in Zoho Mail. Feedback lifecycle analytics use the event, page type, entry point, and bounded failure class. Google Analytics also associates the current page URL and its standard site analytics fields. The feedback message, email, screenshot, report identifier, converter or local values, and detailed diagnostic context are not sent to analytics.

Browser extension feedback

The Chrome and Edge extensions keep saved places and preferences in your browser. Send feedback opens a form inside the extension with a required message, an optional reply email, and an optional screenshot you choose and review. The form includes the browser name, extension and time-zone data versions, capture time, and, when available, a frozen comparison of the first two displayed places using only time-zone identifiers, the selected instant, displayed times, and offsets. You can view these details before sending. Automatic context excludes private place names, saved-location identifiers, browsing URLs, device or installation identifiers, logs, and unrelated saved places. Review your message and screenshot for personal information before sending.

No report is sent until you press Send. Network access to Savvytime.com is optional and requested when you use Send. Draft messages, reply emails, and screenshots remain in the feedback tab's memory and are not saved or synced. Reports are delivered to [email protected] as support email in Zoho Mail and retained for 12 months under the feedback retention policy below. Feedback content and comparison details are not sent to analytics. Feedback is available in the Chrome and Edge extensions; the Firefox and Safari extensions make no feedback network requests.

Mobile app information

The mobile apps do not require a Savvy Time account. Saved locations, custom location names, display order, time format, theme, and other app preferences are stored locally on your device. Savvy Time does not automatically upload this saved configuration to our servers. If you send feedback, the limited context described below is included only when you submit the report.

When device backups are enabled, your saved places and preferences may also be included in a backup you manage, such as iCloud, Finder on a Mac, backups on a Windows computer, Google device backup, or a backup service offered by your device manufacturer. This backup data is not sent to Savvy Time.

If you choose Add to Calendar, the app requests access to calendars through the operating system and sends the event details you selected to the calendar on your device. Savvy Time does not receive or store your calendar contents on our servers. You can change calendar permission at any time in your device settings.

Mobile feedback

Where Settings > Send feedback is available, it lets you send a message, an optional reply email, and an optional screenshot you choose. The form also includes app and build version, operating-system version, time-zone data version, capture time, and, when available, a limited snapshot of the first two places in the committed Home comparison when you open the form. This comparison is frozen while you write your report. You can inspect these details before tapping Send. The automatic context excludes saved names, saved-location identifiers, coordinates, logs, and unrelated saved places. A screenshot or message you choose to include may contain personal information; review it before sending.

Reports are sent to Savvy Time and delivered to [email protected]as support email in Zoho Mail. We use them to investigate issues and reply when requested, and retain the complete report for 12 months under the feedback retention policy below. A report identifier helps recognize retries. The mobile feedback feature does not send feedback content, email, screenshots, or comparison details to analytics. No report is sent unless you tap Send.

Mobile crash reports

The mobile apps send crash reports to Sentry, a service of Functional Software, Inc., which acts as our service provider. Sentry stores these reports in its EU data region in Frankfurt, Germany. We use crash reports to find and fix problems in the apps. Learn more in the Sentry Privacy Policy.

When the app crashes or runs into an error, a crash report can include the error type and message, where in the app's code the error happened, labels for the part of the app that failed and for some earlier app events, and technical details such as the app and build version, operating-system version, and device model. The app does not attach your saved places or their names or time zones, text you enter, web addresses, screenshots, calendar details, or your settings.

Crash reports are stored without an account, device, or installation identifier. Where Sentry would otherwise use an installation ID to identify the user, the app sets the same fixed user ID, unlinked, for everyone. The app does not add your IP address to crash reports. Sentry receives it as part of the network connection, but our Sentry project is set not to store IP addresses. Sentry retains crash reports for 30 days.

Crash reporting is on by default. You can turn it off at any time under Settings > Privacy > Share Crash Reports in the app. While it is off, the app does not send crash reports.

Mobile subscriptions and purchases

Savvy Time offers one optional auto-renewing subscription service in the mobile apps, called Savvy Time Pro in iOS version 1.2.7 and later and Android version 1.2.9 and later, and Ad-Free in earlier versions. Where offered on iOS, Lifetime Pro is an optional one-time purchase of the same Pro benefits, without a subscription or trial. Apple processes purchases made through the iOS app, and Google processes purchases made through the Android app. Savvy Time does not receive your full payment-card or bank-account details.

We use RevenueCat as a service provider to validate purchases and manage Pro and Ad-Free access, including Lifetime Pro ownership. When the app communicates with RevenueCat, RevenueCat may process a RevenueCat-generated app user ID; product and transaction identifiers; the App Store receipt or Google Play purchase token; subscription and entitlement status; device and operating-system technical details; locale or currency; IP or network information; and service timestamps such as the last time the app checked purchase or subscription status.

We use this information to validate purchases, unlock and restore Pro and Ad-Free access, apply confirmed refunds or revocations, prevent fraud, troubleshoot support issues, and understand purchase performance. The same purchase-validation data practices apply whether you choose monthly or annual billing, a one-time Lifetime Pro purchase, or an introductory offer. Verified lifetime ownership is retained locally for offline access; it is checked again when the app can successfully verify with the store.

On iOS, the RevenueCat SDK sends Apple's vendor identifier (IDFV) with requests and reports the app's current tracking-permission status (App Tracking Transparency). IDFV is scoped to apps from the same vendor on that device. It differs from Apple's advertising identifier (IDFA), which is used for advertising across apps from different companies.

Savvy Time does not add an email address, advertising ID, or custom account identifier to data sent to RevenueCat. The app does not have an account system. Learn more in the RevenueCat Privacy Policy.

Analytics and advertising

We use Google Analytics to understand site usage and improve the service. We also use Google advertising services, including Google AdSense and Google Ad Manager, together with advertising technology partners such as Publift and Ad-Shield, to show and measure ads. Ad-Shield supports ad-block recovery and states that it processes IP addresses and browser user-agent information for that service. These services may use cookies, device identifiers, and similar technologies to deliver ads, measure performance, prevent fraud, and comply with advertising rules. Learn more in Ad-Shield's Security & Privacy information.

Google and its partners may process information from your browser or device for ad personalization, ad measurement, audience research, and related advertising purposes. You can learn more about how Google uses information from sites and apps at policies.google.com/technologies/partner-sites.

The mobile apps use Google Mobile Ads (AdMob) to display and measure banner ads. Google states that its Mobile Ads SDK may automatically collect and share an IP address (which may indicate general location), app interactions, diagnostic and performance information, device or account identifiers, and advertising data such as ads viewed. Google uses this information for advertising, analytics, service performance, and fraud prevention, and states that SDK data is encrypted in transit.

The Android app does not request the Android advertising ID or Android Privacy Sandbox advertising, attribution, or topics permissions. The iOS app does not request App Tracking Transparency permission and therefore does not access the iOS advertising identifier. Google Mobile Ads may still use app- or developer-bounded identifiers as described above. The apps do not request precise location for advertising.

On iOS releases that enable customer-level ad-revenue measurement, the app also sends banner load, impression, click, failure, and paid events to RevenueCat. These include the ad unit and placement, AdMob's response ID for a loaded ad when available, and any reported revenue amount, currency, and precision. RevenueCat associates these ad events with the existing RevenueCat-generated app user ID to measure ad proceeds alongside purchase performance, including Lifetime Pro purchases. This does not send your email address, device advertising ID, saved places, or calendar details to RevenueCat. The response ID is not sent to Savvy Time's first-party ad telemetry endpoint. Android does not use this RevenueCat ad reporting in this release.

To diagnose and improve mobile advertising delivery, the mobile apps also send bounded mobile ad delivery events to Savvy Time's first-party endpoint at /api/telemetry/mobile-ads. These developer analytics and diagnostics events include the event category (request, loaded, failed, impression, or paid), app and build version, platform, consent-mode category, failure category, adaptive ad size (ad_size), loaded adaptive dimensions, and paid-event value, currency, and precision when Google reports a paid event. This delivery is best effort and does not affect whether an ad loads or how the app works. This telemetry does not send a device or install identifier, raw ad error, user input, or precise location. Normal nginx access logging is disabled for this endpoint so those delivery requests do not add IP address, user-agent, or location-derived fields to this telemetry record.

How we use information

We use information to operate and improve Savvy Time, respond to contact requests, remember preferences, measure performance, serve and measure ads, detect fraud or abuse, protect the services, and comply with legal obligations.

How information is shared

We may share information with service providers that help us operate the website and apps, provide analytics, deliver advertising, host infrastructure, prevent abuse, or process contact form messages. The mobile apps share advertising-related information with Google, purchase-related information with RevenueCat and the applicable app store, iOS device identifiers and tracking-permission status with RevenueCat, iOS banner ad events and revenue with RevenueCat, and crash reports with Sentry as described above. We may also disclose information if required by law or to protect the rights, safety, and security of Savvy Time, users, or others.

Your choices

You can control cookies and local storage through your browser settings. Blocking cookies or storage may affect some site preferences or ad features. Where required, we may show privacy or consent messages that let you manage advertising and privacy choices.

You can manage Google ad personalization at adssettings.google.com. You can also learn about Google Analytics opt-out options at tools.google.com/dlpage/gaoptout.

Where required, the mobile apps use Google's User Messaging Platform before requesting ads to present applicable consent choices. When Google indicates that a privacy-options entry point is required, you can reopen it from the app's Privacy settings. Non-personalized or limited ads may still process information needed to deliver ads, measure performance, and prevent fraud. You can also manage app permissions, tracking permission, and advertising identifiers in your device settings.

You can turn off mobile crash reports at any time under Settings > Privacy > Share Crash Reports in the app.

You can manage or cancel a Pro or Ad-Free subscription through the App Store or Google Play account that processed the purchase. Refund requests and billing disputes are also handled by that store. Deleting the app or asking us to delete RevenueCat data does not cancel an active subscription.

You may request deletion of purchase and subscription data, iOS banner ad-event data, and iOS device-identifier and tracking-permission data controlled by Savvy Time through the contact form. We will coordinate applicable requests with RevenueCat. A deletion request cannot erase transaction records that Apple, Google, RevenueCat, or Savvy Time must retain for security, fraud prevention, tax, accounting, dispute resolution, or other legal obligations.

Advertising privacy choices

Data retention

We retain each feedback report for 12 months so we can investigate the report, respond when requested, and recognize retry duplicates. At the end of that period we delete the whole feedback record, including any optional reply email, screenshot, and attached diagnostic context.

We keep information for as long as needed to provide the services, respond to requests, maintain security, comply with legal obligations, and support ordinary business records. Website preferences remain on your device until you clear them. Local mobile app locations and preferences remain until you reset the app, clear its storage, or uninstall it. Existing device backups may retain a copy. On iOS, this copy may be restored as part of restoring a device from a backup or setting up a new device from that backup. On Android, it may be restored when you reinstall the app or set up a device from a backup. You manage these backups through the backup provider, device manufacturer, or computer that holds them. Purchase and subscription information is retained for as long as needed to provide or restore access, resolve billing or support issues, prevent fraud, maintain required business records, and comply with legal obligations. Sentry retains mobile crash reports for 30 days. Advertising, analytics, payment, and subscription providers apply their own retention practices.

Mobile-ad diagnostics are written as bounded records to the production server log, not to a user profile or analytics database. Access is limited to authorized Savvy Time operators for service diagnostics and security. The production log system retains records under its configured host log-retention and security controls, and we delete or restrict records when they are no longer needed for those purposes or retention is required by law.

Children

Savvy Time is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

International visitors

Savvy Time may be accessed globally. Information may be processed in countries where we or our service providers operate, which may have different data protection laws than your country.

Changes to this policy

We may update this privacy policy from time to time. The updated version will be posted on this page with a revised date.

Contact

If you have questions about this privacy policy, contact us through the contact form.