Privacy Policy

1. Information used on your device

Widget settings and rewards

The app stores widget configurations locally, including clock styles, fonts, colors, date and time formats, chosen time zones and cities, calendar display options, and tap actions. It also stores reward unlocks, including the widget, reward type, and unlock time. These records let the app display your widgets and remember customization benefits. Earlier versions also used local preferences for font unlocks.

Choosing a city or time zone does not require the app to determine your physical location. The app can read your device's time zone and locale to format its display. Selected clock styles and widget counts are also measured through Analytics, and settings can be included in a support report, as described below.

Calendar and alarm information

If you grant Android calendar permission, the app reads event identifiers, titles, and times from the device's calendar provider to find and display an upcoming event and open it in your calendar app. This feature processes event details on your device; it does not upload your calendar contents to us or send them to advertising or analytics services. Your calendar provider may separately synchronize calendars under its own settings and privacy policy.

The app also reads the next alarm information supplied by Android to display it and open your alarm app. You can revoke calendar permission in Android settings and change whether alarm or event information is displayed in your widget settings.

Apps and shortcuts

The app queries compatible installed apps and shortcuts so you can choose what opens when you tap a widget. It stores your chosen action locally. Opening a shortcut or calendar event passes the information needed for that action to the app you open, which operates under its own privacy practices.

2. Advertising and partners

The app is supported by banner, native, and optional rewarded advertisements. It uses Google's AdMob / Google Mobile Ads service and mediation, which lets other advertising networks supply ads.

When these services operate, information is sent directly from your device to the advertising providers. Google's Mobile Ads SDK collects IP addresses (which can indicate approximate location), app and ad interactions such as launches, taps, and video views, performance and diagnostic information, and device or account identifiers, including the Android advertising ID and app set ID when available. These are used for serving and measuring ads, analytics, and preventing fraud. See Google's Mobile Ads data disclosure.

Other active mediation partners may process device and network information, advertising identifiers, approximate location, ad interactions, and privacy-choice signals when they participate in delivering or measuring ads. What a provider receives depends on the ad request, your device settings, your privacy choices, and the provider's role. Partners may use information for personalized ads where permitted and may combine it with information from other apps or services as described in their notices.

Our active advertising services and their privacy notices are:

• Google AdMob / Google Mobile Ads
• InMobi
• Liftoff Monetize (Vungle)
• LY Ads Network (LINE)
• Meta Audience Network
• Pangle (see its regional notices where applicable)
• Unity Ads

These services do not necessarily all receive information on every use of the app. Advertising disclosures can constitute a "sale", "sharing", or processing for targeted advertising under some privacy laws, even without an exchange of money for personal information. Use the controls below to exercise available choices.

3. Advertising privacy choices

The app uses Google's User Messaging Platform (UMP) to request consent information and display privacy messages where required by its configuration and your region. Advertising requests are gated by UMP's determination that ads may be requested, which can use choices from a previous session. The app forwards relevant consent and U.S. privacy signals to mediation partners.

Open Privacy in the app's settings or More options menu. When UMP makes a privacy-options form available, this opens the form so you can review or change your choices. Otherwise, it opens this policy. You can also use privacy controls provided within an ad or in a partner's notice. Contact us if you need help exercising a choice.

You can reset or delete your advertising ID, or use other available ad privacy controls, in Android settings. The controls and their names vary by Android version. Restricting personalized advertising does not necessarily remove ads or stop information needed for contextual ads, measurement, or fraud prevention. Watching a rewarded ad is optional.

The advertising Privacy option does not turn off Firebase Analytics or Crashlytics. The current app enables those services separately and does not provide an in-app switch for them.

4. Analytics and crash reports

Google Analytics for Firebase

We use Analytics to understand app usage, improve widgets and setup, and measure advertising performance. The release app sends screen views, widget setup status and counts, selected or active clock styles, and ad delivery, reward, error, timing, and revenue-related events. An ad revenue event describes advertising revenue, not a payment by you.

Analytics also collects information through its standard SDK behavior, including app-instance identifiers, sessions and engagement, app and device information, approximate location, and the Android advertising ID when available. See Google's Analytics data collection information. We do not ask you to sign in or assign an account-based user ID in the app.

Firebase Crashlytics

We use Crashlytics to identify and fix crashes and other reliability problems. It sends crash traces, recorded exceptions, diagnostic logs, app state, device and operating-system information, and installation identifiers to Google. App diagnostics can include widget update and rendering details, widget identifiers and styles, whether settings or ad initialization were opened, and the Android WebView version. See Firebase's Crashlytics disclosure.

Analytics and crash collection are enabled in release builds when the app process starts, including when Android starts it to update a widget. They are not dependent on opening an advertising consent form. Our calendar display feature does not add calendar event titles or contents to these reports.

5. Optional support emails

If you choose the app's support or issue-report action, it prepares an email to apps@ezi.am using an email app you select. It can attach a diagnostic file and a compressed copy of logs available to the app. This action does not automatically send the email to us.

The diagnostics can contain device model and manufacturer, Android and app versions, locale, time zone, display and launcher information, widget identifiers and settings, chosen cities, calendar display preferences, shortcut actions, calendar permission status, and next-alarm time and originating app. Logs and any screenshots or text you add can contain further personal information.

Review the message and attachments before sending; remove attachments or write directly to us if you prefer. If you send it, we receive your email address, message, and attachments to respond and investigate the issue. Your email provider and our email service also process that correspondence.

6. Recipients and processing locations

EZI STUDIO INC is responsible for the app's data practices and the decisions we make about processing. We receive usage and reliability information through Google Analytics and Firebase, and support information you send. Google processes service data under its applicable terms; advertising partners may also process information for their own purposes under their privacy notices. Their notices explain their recipients and controls. Those separate notices do not remove our responsibilities under applicable law.

We are based in the United States. Google, advertising providers, and email providers may process information in the United States and other countries where they or their service providers operate. See Firebase's privacy and security information and the partner notices above for their processing locations and safeguards.

Google documents encryption in transit for Mobile Ads and Firebase services. Local app data uses Android's app storage protections. Email and backups use the protections of the services handling them. No method of storage or transmission can be guaranteed completely secure.

7. Storage and retention

• Local settings and unlocks: these remain in the app's storage until changed or removed. Removing a widget can remove its associated configuration and unlocks. Clearing app storage or uninstalling can remove local data. Temporary support attachments are created in the app's cache, which Android or you can clear.
• Android backups: the app allows Android backup. Settings, databases, and preferences may be included in cloud backups or device transfers according to your Android version, device, and backup settings. This can move locally stored information off the device through your backup provider. Cache files and the app's widget-setup telemetry bookkeeping in Android's no-backup directory are excluded from standard Auto Backup. See Android's backup documentation. Restoration of individual settings or rewards is not guaranteed.
• Analytics: we follow Google's retention mechanisms. As of this policy's date, our property is configured for 2 months of event data and 14 months of user data, with user-data retention reset on new activity. These settings do not limit standard aggregated reports. Google explains its deletion cycles and exceptions in its Analytics retention documentation.
• Crashlytics: Google states that it retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems. See Firebase's retention information.
• Advertising and support correspondence: we follow the relevant services' retention schedules and settings. Advertising providers describe retention in their notices above. Support emails and attachments remain subject to the email service's retention and deletion settings; there is no app-controlled automatic email deletion period. You can contact us to request deletion of support correspondence.

Uninstalling the app does not itself delete previously transmitted analytics, advertising information, crash reports, support emails, or copies in backups. Deletion requests and backup controls apply separately.

8. Your controls and rights

You can manage calendar permission and app storage in Android settings, change widget settings in the app, manage device backups with your backup provider, and use the advertising controls described above. If you clear app storage, your settings and rewards can be lost. You can stop further app use by removing widgets and uninstalling the app.

Depending on where you live and the law that applies, you may have rights to access or obtain a copy of your personal information, correct it, request deletion, restrict or object to processing, withdraw consent, and opt out of sale, sharing, or targeted advertising. You may also have a right to appeal a decision on a request and to exercise rights without unlawful discrimination. Withdrawal of consent does not affect processing lawfully carried out before withdrawal.

Contact apps@ezi.am with a description of your request. We may need information to verify the request and locate the relevant records; the app has no user account connecting your email address to all SDK identifiers. You can also contact providers directly through their notices for information they control. You do not need to send a diagnostic attachment to make a privacy request.

You may complain to your local data protection or privacy authority. For example, the European Commission explains GDPR rights, and the California Attorney General explains California privacy rights. Nothing in this policy limits mandatory consumer or privacy rights. Where the law requires separate consent or another legal condition for processing, use of the app does not replace that requirement.

9. Children's privacy

Digital Clock Widget is available to users of all ages. The current app does not ask for age or provide an age-screening or parental-consent flow. The advertising, analytics, and crash-reporting practices described in this policy should not be assumed to be disabled because a child uses the app.

If you are a parent or guardian with a question about a child's information, or want to request access to or deletion of information associated with your child, contact apps@ezi.am. Please describe the concern without sending unnecessary information about the child. Applicable children's privacy rights and parental-consent requirements continue to apply; this policy and the app's content rating do not replace them.

10. Changes to this policy

We will update this page and its date when these practices change. Where applicable law requires additional notice or consent for a change, those requirements continue to apply.

11. Contact us