EZTools Privacy Policy

Signal Deck: Ham Radio Logbook (Android package com.eztools.hamradio.signaldeck, EZTools) uses this shared policy and its general advertising, purchasing, security, retention and contact provisions. This clarification was added October 12, 2026; sections explicitly named for other apps do not describe Signal Deck.

Signal Deck keeps logbooks, callsigns, contact times, frequencies, modes, signal reports, user-entered grid locators and notes on your device. It has no product account, business server, App Check, cloud log synchronization or device-location access. Local grid/antenna tools process entered values. Android's document picker handles files and export destinations you choose; those providers may be cloud services. Backups and ADIF exports are not encrypted by the app and can contain your records. Removing local data does not remove exported copies, and we cannot remotely recover local logs.

The production Signal Deck app uses Google Mobile Ads through EasyAds; the distribution includes InMobi and Liftoff/Vungle mediation components, whose processing depends on active advertising configuration. Applicable data and purposes are described in the general advertising provisions below. Active Pro removes ads. Google UMP provides regional privacy choices and an available in-app entry to revisit them. Saved refusals and withdrawals remain effective for the purposes declined.

Signal Deck uses standard Firebase Analytics by default, with an opt-out in Settings, including app/session and screen events, technical app/device information, app-instance identifiers, Android Advertising ID when available, approximate location derived from masked IP addresses and standard purchase/subscription events containing product and price information. Analytics consent follows applicable UMP choices and platform settings. Crashlytics is separate and off until you enable crash reporting; it can process crash/ANR diagnostics, stack traces and installation/app/device information. Our custom events use fixed action categories and do not include callsigns, grid locators, coordinates, notes, filenames, document URIs or purchase tokens. Automatic exception details may contain runtime information. Turning reporting off stops later collection and requests the relevant local Analytics reset or deletion of unsent crash reports; it cannot recall completed or in-progress uploads. The separate development test package is isolated from production Firebase. For privacy requests email [email protected] and identify Signal Deck. General retention/deletion provisions below apply.

EarCue: Earbud Finder — product-specific information

EarCue

This section applies to EarCue (Android application ID com.eztools.earbud.finder) and supplements the general privacy information on this page. EarCue does not require an EarCue account. It does not use Firebase Authentication, Firebase App Check, a product-operated account service, or a cloud database.

Bluetooth and nearby devices

EarCue uses Android Bluetooth access to show paired audio devices, check their connection state, play a sound through a verified connected output, and run time-limited scans for nearby Bluetooth signals. Information about a paired device you select, including its name, type, Bluetooth address, and connection state, is processed in the app and stored in this phone's local app database. Results that have not been verified as one of your paired devices remain in memory only for the current scan and are discarded when that scan ends. EarCue does not continuously track unknown devices or keep background logs about them.

On Android 11 and earlier (API level 30 and below), Android requires location permission for Bluetooth scanning. EarCue uses that permission only to perform Bluetooth discovery; it does not use scan results to calculate or record your physical location.

Optional location recording

Location recording is off by default. If you turn on location guard, EarCue obtains one location for this phone when a selected device disconnects, first trying a recent system location and otherwise making one time-limited location request. If you also enable the optional away reminder, EarCue waits 60 seconds after disconnect and makes one additional, one-time phone-location check to compare with the saved disconnect point. That second check is transient, is not saved, and may only trigger a local notification; it is canceled if the device reconnects or the service stops. EarCue does not continuously track your location and does not request background location permission. The saved record can include the phone's coordinates, accuracy, time, and an address, and is stored in the phone's local app database. A saved place describes where the phone was at disconnect, not where the earbuds are now. You can clear these records in the app, clear the app's data, or uninstall it.

Android's Geocoder may use a network service to turn coordinates into address text. If you choose to open a record in a maps app, its coordinates are passed to that app. Those system and map providers apply their own privacy practices. EarCue does not add Bluetooth addresses, device names, saved coordinates, or address text to its Firebase event parameters or advertising requests.

Background guard

Time-only guard listens for Bluetooth connection and disconnection events; it does not actively scan, request location, start a foreground service, or show an ongoing notification. Location guard uses an Android foreground service with an ongoing notification while it is enabled. It obtains a phone location at disconnect to create the optional local record; if you separately enable the away reminder, it makes one additional transient phone-location check 60 seconds later as described above. You can stop either guard in EarCue's settings; stopping location guard ends its service and cancels pending location work.

Analytics and optional crash reporting

Analytics is enabled by default in a configured EarCue build unless you have saved an opt-out; you can turn it off in Settings, and a saved opt-out is retained. Crash reporting is a separate opt-in and remains off unless you enable it. When enabled, Firebase Analytics may process its SDK installation identifier, Android Advertising ID (AAID), app and device information, IP-derived approximate location, automatically collected session and screen events, and EarCue's predefined category-level feature events. For completed Google Play purchases, Analytics may also automatically collect an in_app_purchase event with details such as the product ID and name, price or value, currency, and quantity. These purchase details are separate from EarCue's category-level feature events. Saved Google UMP privacy choices, including refusal of advertising measurement or personalization, are honored and retained for the purposes declined. EarCue does not send Bluetooth addresses, device names, coordinates, address text, user notes, or a user ID. Crashlytics may process app and Android version details, device diagnostics, and stack traces for crash and ANR investigation. Custom non-fatal reports use fixed error categories and exclude raw exception messages, arbitrary logs, user input, and EarCue's local device or location records. Automatic Crashlytics submission is disabled. A prior-session report is explicitly submitted at startup only if crash reporting was enabled for the prior session and is still enabled at the current startup. The first time you enable crash reporting, previously stored reports are cleared; reports created afterward wait for a later startup at which you have kept crash reporting enabled. Turning Analytics off stops later Analytics collection; turning crash reporting off stops later report submissions and requests deletion of unsent crash reports. Neither choice can recall data already submitted or in transit.

Advertising and privacy choices

When an advertising request is allowed, the current EarCue integration uses Google Mobile Ads and Liftoff/Vungle mediation. Those SDKs may process information such as an IP address (which can indicate general location), advertising or app-set identifiers, ad and app interactions, and technical diagnostics for ad delivery, measurement, and fraud prevention, subject to the build and consent settings. The InMobi adapter and SDK are excluded from this app. EarCue does not attach Bluetooth identifiers or saved precise coordinates to advertising requests. Where required, Google's consent flow presents advertising privacy choices before eligible requests. You can revisit available choices through EarCue's Ad privacy choices setting and reset or delete the Android Advertising ID in Android settings. Information already transmitted to a provider may not be withdrawn by changing a later choice.

Purchases and support

If EarCue purchases are enabled, Google Play handles checkout and payment details. EarCue does not receive payment-card information. Google Play manages purchase and subscription records. For EarCue-specific support, email [email protected].

Request deletion of EarCue data

To request deletion or help with EarCue data, email [email protected] with the subject EarCue data deletion and describe the data concerned. Do not send passwords, payment-card details, or precise location records. EarCue has no product account. Saved devices, location records, and settings are stored on your phone: clear the relevant records in EarCue, clear Android app storage, or uninstall to remove local app data. We cannot remotely erase your phone or copies you exported.

We review requests concerning support correspondence and data already sent to service providers, and may need further information to identify the relevant records and verify the request. Anonymous Analytics or advertising records cannot always be linked to a support email. Provider data follows the relevant service's retention and deletion controls; we do not promise that uninstalling or resetting an identifier removes prior uploads. Limited records may be retained where required for legal obligations, purchase or refund issues, or fraud prevention. We explain applicable limitations and retention when handling the request. Deleting app data does not cancel Google Play subscriptions; manage subscriptions in Google Play.

Effective date: October 11, 2026

1. Who We Are and Where This Policy Applies

We are the independent developer of the EZTools applications ("EZTools", "we", "our", or "us"). This shared policy applies to EZTools apps that link to this page, including Signal Deck, EZScanner, PixCompress, EZStatus, Handfont, Songlet, PixMagnify, Field Notes, Car Code Guide, Nyra, Beestead, and EarCue. Product-specific details below apply only to the named app and the version or configuration described. Our privacy and support contact is [email protected].

The Apps have different features. A section about scanning, photo editing, cloud processing, advertising, analytics, or purchases applies only to an App and version that provides that feature or uses that service. Sharing this policy does not mean every App collects every category of data.

Product details: EZStatus · Handfont · Songlet · PixMagnify · Field Notes · Car Code Guide · Nyra · Beestead · EarCue.

The core tools in these Apps do not require you to register a personal EZTools account, although some named apps provide optional online accounts. Content you scan, create, select, or send to support may nevertheless contain personal information, which we handle as described below.

Privacy and data deletion requests

For a privacy or deletion request, email [email protected]. Name the EZTools app and the data category or account you are asking about; if the app provides a non-sensitive installation or account identifier, you may include it to help us locate records. Do not send passwords, private logs, precise location records, or payment credentials. We review requests product by product, verify the requester as needed, and check whether the records can be linked to them. Some aggregated or provider-held information may not be identifiable or removable through us; use the relevant third-party provider's request channels for data it controls. We may retain limited records where applicable law or an unresolved transaction or security matter requires it, and will explain relevant limits when handling a request. Local-only files and copies in storage or sharing services you selected must be managed there.

EZStatus users: read the product-specific details below. EZStatus supports Google advertising and Google Play purchases; ad requests remain subject to UMP privacy choices and in-app eligibility, and purchase options are shown only when Google Play returns them as available. Production Google Analytics for Firebase uses its standard collection baseline unless you have saved an opt-out; actual recorded UMP purpose choices are applied without treating an unknown refresh as a user refusal. Crashlytics has a separate off-by-default control. Notification-listener message history, automatic replies, and direct-chat or linked-device handoffs are not available. Sections about other Apps' cloud photo processing, Performance Monitoring, or Remote Config do not describe this EZStatus release.

Handfont users: read the product-specific details below. Handfont creates fonts, images, and documents from your handwriting on your device and does not upload your handwriting to EZTools servers. The production release uses Google Analytics for Firebase and Firebase Crashlytics by default for usage measurement and crash diagnosis, as described below. Its Firebase defaults include AAID collection and personalized-ad signals where available; recorded consent choices and device settings determine applicable processing, and technical defaults do not mean you clicked a consent button. Eligible free users may see a Google AdMob banner in the font library after the App checks advertising consent and Play membership status. The separate development test package uses Google's sample ad units. Handfont does not include cloud processing, Firebase Performance Monitoring, or Remote Config. It uses Google Play services for document scanning and optional online font downloads, and Google Play for optional purchases and rating prompts. Sections about other Apps do not automatically describe Handfont.

Songlet users: read the product-specific details below. Songlet creates short songs and ringtones with AI. Its online features use an automatically created anonymous account, and generation inputs are sent through our Firebase backend to fal for ACE-Step music generation or to Google Cloud for AI lyric writing. Generated songs are downloaded to your device and kept there; our backend does not store the audio files. Importing, editing, playing, exporting, and setting sounds as ringtones happen on your device. Songlet uses Firebase Authentication, Cloud Functions, Cloud Firestore, App Check with Google Play Integrity, and Remote Config. It uses Google Play for optional credit purchases and subscriptions, and Google AdMob with the User Messaging Platform for advertising and privacy choices as described below. Production Google Analytics for Firebase uses the standard collection baseline, including automatic app-use events and identifiers such as AAID where available; saved consent choices and device settings affect applicable processing, and defaults do not mean you clicked a consent button. Songlet does not include Firebase Crashlytics or Performance Monitoring. Sections about other Apps do not automatically describe Songlet.

2. Content and Permissions Used by the Apps

Camera, photos, and documents

Where needed, we ask for camera access for scanning or magnification, and access to the photos, documents, or folders you select for processing, saving, importing, or backing up. Older Android versions may require storage permission to save files. You can manage these permissions in your device settings; denying a permission may prevent its related feature from working.

In EZScanner, camera-image recognition, barcode and QR-code generation, recognition of selected images and PDF pages, and optical character recognition (OCR) are performed on your device. We do not upload the images or PDF pages for these recognition operations. Online book and product lookups are described separately in Section 3.

In PixCompress, compression, resizing, format conversion, cropping, duplicate scanning, metadata cleanup, manual refinement, and final export are performed locally. We do not upload photos for these local workflows.

Where an App uses Google ML Kit, recognition or segmentation of the input image happens on-device. ML Kit may contact Google for model downloads and updates, compatibility information, and performance or usage metrics; this does not mean the image is uploaded for recognition.

Scan history, code content, clipboard, and backups

EZScanner stores scan and creation history on your device, including code content, format, timestamps, and any names, notes, tags, folders, or other fields you add. Code content can include contact details, messages, Wi-Fi credentials, payment identifiers, or location coordinates. Processing information contained in a code does not by itself grant access to your contacts, messages, payment account, or current GPS location.

Clipboard features read text for pasting; the Plain Text creation screen also checks clipboard text to decide whether to show its Paste action. Copy commands and the automatic-copy setting can place result text on the system clipboard. Operating-system clipboard access rules then apply.

Private scan mode skips saving that scan to history and disables its automatic copying and automatic opening. It is not a network-anonymity mode: book or product previews and the technical service communications described in this policy can still occur.

Library imports and exports, including optional automatic backups, use files or folders you choose. A selected document or backup provider may synchronize them with your own cloud storage under that provider's settings and policy. Backups can contain scan content and Trash records. We do not operate an automatic cloud-sync service for EZScanner's library, and its JSON/ZIP backups do not add their own encryption.

EZStatus: status media, local tools, and notifications

EZStatus accesses status media through folders you explicitly select in Android's system folder picker (Storage Access Framework). It retains the folder authorization so you can browse the folder again and, if you separately enable automatic saving, check it in the background. It reads only accessible media in the selected sources; it does not gain unrestricted access to your device storage, contacts, private chat databases, or WhatsApp account. It cannot retrieve statuses that are not available in the selected folder. The release version covered here does not capture or recover messages.

Browsing, thumbnails, manual saving, duplicate checks, video splitting, and sticker-image import and export are processed on your device. EZStatus keeps local records such as folder and file references, file names, media types, sizes, modification and save times, content hashes for duplicate detection, favorites, copy results, settings, and consent choices. Imported sticker images are stored in the App's private library; saved status media and exported videos or sticker images are written to your device's media storage. EZStatus does not upload these media files or local records to EZTools servers. The production configuration includes Google advertising services; ad requests are handled separately from local media processing and are described in Section 5. EZStatus does not use cloud media processing. Optional analytics and crash diagnostics are described below; local media processing does not mean that the whole App never communicates online.

Automatic saving is optional. You must select the source folders, review the in-app explanation, allow the required App notifications, and explicitly start the feature. This release uses periodic background checks scheduled by Android, rather than continuous real-time monitoring; checks can be delayed by the system and may miss media that disappears between checks. You can pause or stop automatic saving in the App and disconnect a source to revoke its retained folder access. If required notifications are disabled, automatic saving stops until the required setup and user action are completed again.

Notification permission lets EZStatus display its own automatic-saving status and save summaries. It does not authorize reading notifications from other apps. These notifications do not display media thumbnails, source file names, or inferred contacts, and the App provides a lock-screen visibility setting. Notification access for message history and automatic replies is not requested or used by this release.

When you choose Share or Repost, Android passes the selected media to the app you choose; that app may upload or further share it under its own privacy policy. Copying a caption places the selected text on the system clipboard. Direct-chat and linked-device browser handoffs are disabled in this release. EZStatus is an independent utility and is not affiliated with or endorsed by WhatsApp or Meta. Save and share only content that you own or have permission to use. Android folder access and an in-app confirmation do not grant rights from a content creator or from WhatsApp. Read the EZStatus Terms of Use. Opening policy links uses your browser, whose network and privacy settings apply.

EZStatus: usage analytics and optional crash reports

In the production App, Google Analytics for Firebase uses its standard collection baseline when no saved opt-out is present. You can turn Usage analytics off in Settings > Privacy & terms; a saved opt-out remains effective. Actual recorded UMP purpose choices are applied, while an unknown or failed consent refresh is not treated as a user refusal. Crash reports are separate and off by default; you can enable or withdraw them independently in Settings. Neither setting is required to use the available tools. Production Firebase is not included in the separate Debug test package.

Turning usage analytics off saves an opt-out and applies it through Analytics collection and consent settings; the App does not reset local Analytics data or the app-instance identifier as part of this action. Crash-report changes take full effect after restarting the App. Turning crash reports off requests that automatic uploads stop and that unsent reports be deleted; an upload already in progress may complete. Newly enabling reports applies on the next launch, after the App has requested cleanup of reports stored before consent. These controls do not retroactively delete data already sent to Google. Information about provider processing is available in Firebase Privacy and Security and Google's Privacy Policy. See Section 7 for retention and Section 9 to request help with access or deletion. Local cleanup does not delete previously uploaded data.

Handfont: handwriting, fonts, and creative tools

Handfont does not request camera, microphone, contacts, location, or broad storage permissions. You add handwriting by writing on the screen, by scanning pages with Google's document scanner, or by choosing images in Android's photo picker. The scanner runs in Google Play services, which operates the camera and returns only the scanned pages you confirm; Google Play services may need to download the scanner module first. Handfont receives only the pages and photos you select.

Stroke smoothing, page straightening and grid detection, outline extraction, TrueType (.ttf) font generation, handwriting pages, signatures, and image and PDF rendering are processed on your device. Handfont keeps font projects in App-private storage, including your strokes, original imported pages and photos, derived character images, correction and review records, font settings, and creative drafts with private copies of photos you add. This content can include personal information you choose to write or photograph, such as your name or signature. Handfont does not upload it to EZTools servers and does not use an EZTools account or cloud-sync service.

Content leaves the App only when you choose to save or share a PNG, JPG, PDF, or .ttf file, print a template, or export a backup. Printing passes the template to the print service you choose, which handles it under its own policy. A single-project or library backup contains the full editable projects, including original handwriting and imported images with any metadata those files contained, and Handfont does not encrypt it. Keep backups that contain your signature or other personal handwriting in a place you trust.

The production Handfont App enables Google Analytics for Firebase and Firebase Crashlytics by default. Analytics receives automatically generated app-use and session events and our fixed events for completed project creation, font generation, file saving, backup restoration, and paper import, plus membership screen views and purchase stages. Membership events use fixed entry, plan, stage, and failure-category values, without purchase tokens or user content. Firebase may receive app and operating-system versions, device details, language, approximate region derived from connection information, app-instance or installation identifiers, and the Android Advertising ID (AAID) where available. The configured Analytics defaults allow personalized-ad signals, subject to applicable consent choices and device/account settings; these defaults are not evidence that you clicked a consent button. Crashlytics receives crash and application-not-responding diagnostics, including stack traces, app/device details, identifiers, and session information. Google receives connection information such as IP address when these services communicate. We use these services to understand usage and fix reliability problems. We do not intentionally attach handwriting, scanned pages, photos, text you type, project or file names, document URIs, purchase tokens, or saved clipboard content to our custom events or crash reports; exception details may nevertheless contain runtime diagnostic information. The separate local test package does not include this production Firebase client. When an eligible ad request is made, Google's advertising services may access the advertising ID where available and permitted by your device settings.

Starting with Handfont 1.3.0, selecting a free font for download can fetch its file from handfontasset.eztoolapp.com. Cloudflare delivers the file for EZTools and receives the requested font path and standard connection information, including your IP address. Handfont checks the file and stores it on your device for offline use. Your text, handwriting and projects stay on your device during a font download.

Google Play delivers full font language packs, including Handfont's original PRO fonts. Some optional fonts in the editing tools use the Google Fonts provider in Google Play services. When you request one, Google receives the font family name and standard connection information, such as your IP address. The five included reference fonts work offline, and font favorites are stored on your device.

Text styling tools process text on your device. Text you share to Handfont, or select in another app and open with Handfont, is used to show styled versions and is returned to that app only if you choose to replace the selected text. If you enable the optional Handfont keyboard, Android displays its standard warning that a keyboard may be able to collect what you type. The Handfont keyboard does not save, log, or send the keys you type, does not connect to the network, and types ordinary, unstyled text in password and other secure fields. It reads the clipboard only when you tap Save clipboard, keeps up to 10 saved items on your device, and lets you clear them.

After you have successfully saved files several times, Handfont may ask Google Play to show a rating prompt; Google Play decides whether to show it and handles any rating you submit. Handfont opts out of Android's automatic cloud backup, although a device-to-device transfer on some Android versions can still copy App data to a new device. Read the Handfont Terms of Use.

Songlet: AI songs, account, and credits

Songlet does not ask you to register. When the App first connects to its online features, such as loading prices and your credit balance, it creates an anonymous Firebase Authentication account identified by a random user ID. Our backend keeps an account record linked to that ID: your credit balance and credit history (such as daily gifts, rewarded-ad grants, generation charges, refunds, and purchases), daily check-in and usage counters, subscription status and expiry where applicable, and account creation and last-activity times. We use this record to provide credits, apply daily limits and fair-use rules, and restore purchased access.

Where the App offers it, you can choose to link a Google account so that you can restore the same Songlet account later. Google Sign-In through Android's Credential Manager gives Firebase Authentication your Google account identifier and the basic profile information that Google includes, such as your email address, name, and profile photo. Our backend can retain a record of account linking for account recovery and abuse prevention; the current version does not grant a linking bonus. Linking is optional. If you have not linked an account, uninstalling the App, clearing its data, or changing devices can make the anonymous account and its credits inaccessible.

When you create a song, Songlet sends what you enter for that request—the style or mood description, lyrics or hook, selected style tags, duration, the instrumental setting, and a random request ID—to our backend. If you use a template that includes a name, our backend checks the name before use and it becomes part of the song request. Our backend checks requests against content rules (for example, real artist names and prohibited phrases), deducts credits, and stores a generation record linked to your account ID. That record contains the request text, its status, the credits charged, the AI provider and model used, the provider's request reference, and a temporary link to the result. Our backend then sends the generation inputs to the third-party AI music provider we use. We do not send your Firebase user ID or Google account details to the provider. The provider processes the inputs to produce the audio and may retain request and output data under its own terms and privacy policy, and it may process them in other countries.

AI lyric writing, where available, works the same way: the topic you enter, the selected language, and the section type are sent to our backend and to the AI provider used for that feature, and the request and the resulting lyrics are stored with your account ID so that a retried request is not charged twice. Until our backend confirms a song or lyric request, the App keeps that request's inputs in App-private storage so that it can safely retry it.

Do not enter sensitive personal information, such as health, financial, or government identification details, in prompts, lyrics, names, or reports. Include another person's name or other personal information only when you have the right to do so.

When generation finishes, the App downloads the audio from the provider's temporary link and saves it in App-private storage on your device. Our backend does not store generated audio files. If a generation fails, credits are returned to their original source when still valid, without extending expired daily grants; the record shows the failure and refund result.

You can report a song you generated. A report sends the song's generation reference, the reason you choose, and any description you enter to our backend, where it is stored with your account ID. We use reports to review AI-generated content, improve content safeguards, and enforce our rules. A report does not upload the audio file.

To protect the service and the credit system from abuse, Songlet's requests to our backend include an App Check token based on Google Play Integrity, which Google generates from information about the App installation and the device's integrity. Firebase and Google Cloud receive connection information such as your IP address, and our backend can record operational logs, such as request times and error details, to keep the service running. Songlet uses Firebase Remote Config, which uses a Firebase installation identifier, to receive display settings; these settings do not decide credit charges.

Where Songlet offers credit packs or a subscription, Google Play processes the payment and we do not receive your full payment-card details. To add credits or Pro access to your account, the App sends the product ID and purchase token to our backend, which verifies the purchase with Google Play and records a hashed form of the purchase token, the product, the purchase or subscription state, the credits granted, and subscription periods and expiry. The App attaches a one-way hashed form of your account ID to the purchase so that we can confirm that it belongs to your Songlet account.

Songlet uses fal's ACE-Step endpoints for music and Google Cloud Gemini for optional lyric writing. We request that fal disable long-term request-payload storage and expire generated audio after 24 hours. Temporary delivery and provider operational records can still exist under their policies. See fal's Privacy Policy and Google Cloud's Privacy Notice. Generation inputs and bookkeeping remain in our Firebase records as described in Section 7; a provider-file expiry is not a deletion of your Songlet account records.

Songlet: audio on your device, ringtones, and sharing

Songlet does not request microphone, contacts, or location permissions. You can import audio by choosing a file in Android's system file picker; Songlet receives only the files you choose. Generated songs and imported audio, editing drafts, and library details such as titles, original file names of imported audio, style labels, durations, favorites, and creation times are kept in App-private storage and a local database. Audio editing, including trimming, fades, volume, speed, splitting, joining, and mixing, runs on your device and does not use our backend or credits.

Audio leaves the App only when you choose. Saving to your phone's music writes a copy to the device's shared media storage; on Android 9 and earlier this uses the storage permission. To set a ringtone, notification sound, or alarm, you allow Songlet to modify system settings on Android's settings screen, and Songlet then saves the sound to device media storage and sets it as the selected default sound. Sharing passes the selected audio to the app you choose through Android's share sheet; that app handles it under its own policy.

Songlet opts out of Android's automatic cloud backup, although some device-to-device transfers can still copy App data to a new device. Songs are stored only on your device: uninstalling the App or clearing its data deletes songs that you have not saved to your phone's music or shared elsewhere, and we cannot restore them.

PixMagnify: local magnification and reading

Effective date: November 17, 2026

This Privacy Policy explains how EZTools handles information when you use PixMagnify, an Android camera magnifier and reading aid.

PixMagnify uses your device camera to magnify nearby objects and text. It also reads images you choose in the system picker or explicitly share from another app. It offers zoom, camera lighting where supported, focus and exposure controls, visual enhancement filters, region selection, and image/text reading.

Information processed on your device

PixMagnify does not require an account. Live camera frames, frozen or imported pages, and text recognized from those pages are processed on your device. PixMagnify does not send camera images, imported images, frozen pages, or recognized text to EZTools or its service providers for OCR, advertising, or analytics. When you choose Save, an image is written to your device's gallery. When you choose Share, the image is handed to the app you select; that app handles the image under its own terms and privacy policy.

Images you import

Image import and reading do not require camera permission or permission to browse your entire photo library. The app reads only the image URI you select or share. A system picker or file provider may offer cloud content under that provider's own policies; PixMagnify does not operate a download or upload service.

A temporary reading session holds up to 60 frozen or imported pages, with an image long edge of at most 2048 pixels. Compressed page copies are kept in private app storage on this device; working page order and reading state are held for the current process. An unsaved session is not a saved reading project and is not restored after the app process ends. The app attempts to remove temporary images when they are no longer used; an interrupted process may leave files until a later cold start cleans them, or you clear app storage or uninstall. Explicitly saved reading projects are described below. During import, a bounded temporary copy of the chosen image is placed in private cache for decoding and orientation handling. It is removed after the import attempt; an interrupted process may leave a copy until the app next cleans its import cache, Android clears the cache, or you clear app storage/uninstall. Rotating or selecting a region changes the temporary reading page and does not modify the source file. Reset can restore the original session page, which is a compressed reading copy rather than the full-resolution source.

Reading projects, PDFs and external displays

Reading projects are saved only when you choose a name and confirm saving. They contain up to 60 compressed original and edited reading images, page order, recognized text and its image coordinates, added bookmarks, notes and annotations, and the selected page/reading position. Projects are stored in private app storage excluded from Android system backup; the app does not automatically create a cloud backup. They remain on this device until permanently deleted, app storage is cleared or the app is uninstalled. A project moved to Recently deleted remains on the device until you permanently remove it. Saving changes replaces the project atomically; unsaved changes are not retained after the process ends. Deleting a project does not remove files previously exported to the gallery, a document provider or another app. Batch-recognition and export tasks can also keep private local working copies and completed results for continuation, retry or saving; these do not create an EZTools cloud backup.

Local PDFs are opened only through a system file choice. A bounded private cache copy supports one-page-at-a-time rendering; it is deleted when the reader closes. An interrupted process may leave a copy until a later PDF operation cleans the cache, Android clears it, or you clear app storage/uninstall. Image-PDF export creates a file without a searchable text layer. The VIP searchable-PDF option also includes recognized text as a searchable text layer. PDFs include the selected reading images and export options; reading-guide overlays and OCR highlight boxes are excluded. Saving or sharing a PDF hands the output to the document provider or app you select, which may offer cloud storage under its own policies.

Stand mode can show the reading image on an external display you explicitly select. Other people near that display may see the image. The app stops its external image display while inactive, and stopping this mode does not delete the reading session. Camera frames used for display and approximate center-color sampling are processed temporarily on the device and are not saved by these features. Approximate color results are affected by lighting and camera settings.

Text recognition, speech and reading guides

Text recognition runs on a frozen or imported image, or the region you select, using bundled ML Kit models for Latin, Chinese, Devanagari, Japanese and Korean scripts. No model download is required. Recognition can be inaccurate and should be checked against the original text. Text search operates only on the current recognized result, and paragraph display does not certify reading order or accuracy.

You can select a speech language/installed offline voice independently of the interface language and OCR script, try a sample, refresh available voices, or open system speech settings. PixMagnify does not download voice packs. Changes or downloads performed in another app follow that app's policies.

Reading guides are display overlays. Their lines and dimming are never included in saved or shared images.

Translation, private AI and code values (October 14 development update)

Translation uses Google ML Kit on the device. You choose the source and target languages and confirm downloading missing models, approximately 30 MB per non-English language. Downloads use Wi-Fi by default unless you change that choice. You can cancel the current operation and delete downloaded translation models; an SDK transfer already started may continue after cancellation. Original and translated text remain separate. Translations are temporary and are not added to saved reading projects or exported files.

On supported devices, optional AI summaries and image descriptions use Google's on-device AICore service. The app checks actual feature availability and asks before requesting missing models. AICore manages shared models and their storage; canceling an app operation does not guarantee that a shared system download stops. Images, recognized text and generated results are processed on the device, and the app does not send them to a cloud inference service. Generated results are temporary and excluded from project storage and exports.

Barcode and QR-code reading uses a bundled on-device model. Values are displayed only after you request reading, and are copied only when you choose Copy. PixMagnify does not automatically open code links, join encoded Wi-Fi networks or look up products. Copied values are marked sensitive for Android's clipboard preview; clipboard handling still follows Android and receiving apps' rules.

Google states that ML Kit processes input and results on the device, while it may contact Google for model updates and compatibility information and send API performance and usage metrics. See ML Kit Terms and Privacy. These SDK activities are separate from the app's Firebase usage-statistics choice. Word highlighting uses timing information from the installed offline speech engine and does not add a voice-recording permission.

Copying, sharing and saving text

Copying a recognized line or all text writes that text to the Android clipboard. Android and apps allowed to access the clipboard may handle it under their own rules. Text sharing sends the recognized text to the app you select. Save TXT writes UTF-8 text to the document location you choose through Android's file creator. Such files remain with that provider until you remove them and may be synchronized by the provider. Canceling creation does not save a text file. These explicit outputs are separate from the temporary reading session and do not create a reading-history library inside PixMagnify.

Selected text, local audio and calendar editing

You can select part of a recognized line to copy, read aloud, translate or find it. Choosing another text-processing app sends only the selected text with a read-only instruction, without the rest of the page or its image. The receiving app follows its own policies. OCR word positions, available confidence values and separate local image-detail measurements, original recognition order and your chosen table/reading order can be included in a reading project you explicitly save; these stay in private local storage.

Audio export uses an installed offline speech voice to synthesize existing recognized text from the current page or current project into a local M4A file. It does not record the microphone and does not include images, translations or AI results. Temporary WAV/M4A files are held in private cache; cancellation or closing cleans unshared working files, and interrupted/shared remnants can remain until a later export cleanup, Android cache removal or uninstall. Saving uses your chosen document provider; sharing grants the selected app access to the audio. Those outputs follow the receiving provider's policies and are not deleted by deleting a reading project. Background synthesis can continue while the app process and export screen remain available; process termination does not create a completed export.

Unit conversions and date choices are calculated on the device. Add to calendar opens a pre-filled editor in your chosen calendar app, which may sync under that provider's policies. PixMagnify does not request calendar read/write permission and does not save an event itself. Nothing is saved by this feature until you confirm in the calendar app.

Preferences

Display adjustments, default zoom, freeze options (sharpest-shot and timer), control preferences, reading size/spacing/layout/theme, speech choices/rate, named scene presets and completed first-use tips are stored locally. Presets store display settings and their user-entered names, not images or recognized text. The app excludes its preference storage from Android's app backup and device-transfer rules. Clearing app storage or uninstalling removes these local preferences. The app also keeps a small local count of completed copies and saves, and the time it last asked Google Play to offer a rating card; it stores no image or text for this. Whether a rating card appears, and any rating you give, is handled by Google Play under Google's terms.

Details such as dates, model numbers, phone numbers and web addresses are picked out of recognized text on the device. They are copied to the clipboard, sent to the phone's dialer or opened in a browser only when you choose Copy, Dial or Open; a web address is shown in full for confirmation first.

Advertising and consent choices

The production version of PixMagnify displays advertising provided through Google Mobile Ads and its advertising partners. To provide and measure ads and prevent fraud, the Google Mobile Ads SDK may process your device's IP address, general location inferred from that address, interactions with the app or ads, diagnostic information, and device or account identifiers. Google describes the SDK's data handling in its Google Play data disclosure for the Mobile Ads SDK and privacy and messaging guide.

Google's User Messaging Platform (UMP) presents consent messages when required for your region and the configured message types. You can reopen the advertising privacy form from Settings > Ad privacy options when Google indicates that a privacy-options entry point is required. Your choices affect whether and how ads may be requested. See Google's UMP guidance for details.

Optional usage statistics

In the production version, Firebase Analytics is available as an optional setting. Usage statistics is on by default when no choice is saved; an existing opt-out is preserved. You can turn it off in Settings > Usage statistics. While enabled and permitted by the applicable consent state, Firebase Analytics may process app-usage events, app and device information, and identifiers as described in Google's Firebase privacy information, Android SDK data disclosure, and Analytics data-collection documentation. PixMagnify's own events use fixed page names and fixed event/result values to understand feature use and the ad and purchase flows. They are not designed to include camera images, recognized text, image URIs, purchase tokens, or free-text error messages. The Analytics setting is separate from advertising consent; advertising consent cannot override a saved usage-statistics opt-out. Firebase advertising-ID collection and advertising measurement follow the actual advertising-purpose choices.

In addition to the app's fixed events, Firebase Analytics may automatically collect standard app-use events, session information, and technical app/device fields. Google describes these in its automatically collected Analytics events and Firebase Android data disclosure.

Optional crash reports

In the production version, Firebase Crashlytics is available as a separate optional setting. Crash reports is off by default. If you turn it on in Settings > Crash reports, Crashlytics may process crash stack traces, app state, device and app technical information, and identifiers to diagnose failures. Stack traces and exception messages are generated by the app or Android and may contain technical details that were not deliberately added for reporting. PixMagnify does not intentionally attach camera images, recognized text, image URIs, purchase tokens, or custom free-text logs to reports. If you turn crash reporting off, PixMagnify requests deletion of unsent reports on the device. See Google's Firebase privacy information and Crashlytics documentation.

Purchases

Basic magnification, single-page text recognition, translation, standard scanning and image-PDF export remain available without VIP. Optional VIP purchases remove advertising and unlock batch text recognition, searchable-PDF creation, read-aloud audio export and on-device private AI on supported devices. Membership expiry does not lock previously saved reading results or completed output files. New weekly and yearly subscriptions renew automatically unless canceled through Google Play, and the lifetime option is a one-time purchase that does not renew. Existing monthly subscriptions remain restorable and manageable. Google Play displays the applicable price, currency, billing period, and other purchase terms before checkout and processes payment. Google Play's subscription management help explains how to manage or cancel a subscription. PixMagnify has no account or business server; the app checks purchase status with Google Play and processes purchase verification on the device.

Service providers, security, and retention

Google provides the advertising and optional analytics and crash-reporting services described above. Google may process information under its own terms and privacy practices, including the Google Privacy Policy. Google states that data from the Mobile Ads and Firebase Android SDKs is encrypted in transit; consult the linked service documentation for the applicable details. Service providers may retain information according to their service settings and policies. We do not state a fixed retention period for provider data; Google's documentation and service controls describe the relevant retention and deletion options.

Exported images, PDFs and text files are managed by Android and the gallery, document provider or other app where you save or share them. PixMagnify does not control copies handled by those apps.

Your choices and contact

You can control advertising privacy choices through the UMP form when its entry point is required, and you can separately turn usage statistics and crash reports on or off in Settings. You can also stop using the camera or deny camera permission; camera features then become unavailable, while reading an image you select or share remains available. To ask a privacy question or make a request about information handled by EZTools, contact [email protected]. Requests about information handled by Google can also be made through Google's privacy tools and account controls.

We may update this policy when PixMagnify's features, service providers, or data practices change. The effective date above identifies the current version. The current public page is the PixMagnify section of the shared EZTools Privacy Policy.

EMF Detector: Ghost Hunt (Field Notes)

This section covers Android package com.emfdetector.ghosthunt.emfmeter, provided by EZTools. Field Notes records real magnetic-field or motion sensor readings supported by your device and lets you keep local investigation notes. Entertainment interpretations do not establish the presence of supernatural entities. There is no account, cloud backup, business backend, App Check, or continuous background sensor collection.

Local measurements, recordings, photos, and location

Sensor samples, baselines, session summaries, replay envelopes, notes, checkpoints, and preferences are processed or stored locally. Microphone and camera access are requested for user-initiated recording or photos. Imported photos can retain their original metadata. Recordings and photos are kept in app-private storage; we do not automatically upload them. Optional approximate-location recording is off until you enable it; a rounded location is requested for a session and saved locally. Optional place-name lookup may send that rounded location to the device's location-name service. Opening a map or sharing a file passes selected information to the app you choose under its own policy.

Reports and shared copies can contain session information and the notes or location details you chose to record. Review them before exporting or sharing. You can delete sessions and attachments, clear history or saved locations, and reset a baseline in Settings. Uninstalling or clearing app storage removes local records; Android app backup is disabled. We cannot remotely recover or erase copies you exported or shared.

Advertising, analytics, and crash reports

The production app uses Google Mobile Ads and UMP. Advertising services may process IP address and approximate region inferred from it, device identifiers, app/ad interactions, and diagnostics for ad delivery, measurement, and fraud prevention. Consent messages and privacy choices are provided through the existing UMP flow where required. Active Plus members do not see ads. Optional rewarded ads only grant the temporary in-app benefit described before the ad after a successful reward callback.

The production app includes Google Analytics for Firebase and Firebase Crashlytics for usage measurement and reliability, enabled by default. Analytics receives standard app/session events, app-instance identifiers, app/device information, and approximate region derived from network information. Our custom events use a closed vocabulary of device tiers, feature names, categories, and duration/count buckets; they do not contain raw sensor values, coordinates, addresses, user notes, recordings, photos, or filenames. The production manifest allows AAID collection and personalized-ad signals where available; these technical defaults do not mean that you clicked a consent button. Where applicable, Google UMP passes your recorded choices to Google consent mode for Analytics and advertising. Permission to request an ad does not mean that every Analytics or advertising purpose was granted.

Crashlytics receives crash/ANR diagnostics, stack traces, app and device information, and installation identifiers. We do not deliberately attach user content, file paths, purchase tokens, or free-text logs. Automatic exception details can contain runtime technical information. Google processes these service records under its privacy and Firebase policies; service retention and deletion controls apply. The separate development test package is not connected to production Firebase.

Purchases and contact

Google Play handles optional Plus monthly/yearly subscriptions and a one-time lifetime purchase. The app checks purchase signatures and status and stores a limited local entitlement cache. It does not receive your payment-card details or send purchases to an EZTools business server. Subscriptions renew until cancelled in Google Play; uninstalling does not cancel them. Prices and included benefits are displayed before purchase. For privacy requests or support, email [email protected] and identify Field Notes. Read the Field Notes Terms of Use.

Beestead: beekeeping records and local business tools

Beestead: Beekeeping Log stores apiary, hive, colony and queen details; inspection, mite, treatment, feeding and harvest records; tasks and reminders; and optional business details such as customers, orders, sales, expenses and site-access notes in its local app database. It has no Beestead account or hosted record-sync service, does not read your address book, and is designed not to send beekeeping record fields to EZTools servers or Analytics events. Android system backup may copy the database and preferences when backup is enabled; the App also keeps up to seven local recovery snapshots and can export a ZIP to a destination you choose in Android's file picker. A chosen storage provider applies its own practices. Weather is not available in the current build.

The production App uses Google Mobile Ads through EasyAds, UMP, Firebase Analytics and Crashlytics, Google Play Billing when purchases are offered, and bundled ML Kit QR/barcode recognition. Analytics follows the production SDK default baseline when there is no saved purpose choice, which can include automatic screen-view events, AAID, app-instance identifiers, and purchase events; eligible signals may be used for personalized advertising subject to account/device settings. These technical defaults do not mean you clicked consent. The App applies actual UMP choices for Analytics purposes and retains saved refusals or withdrawals; an unknown or failed refresh is not treated as a user refusal. Crashlytics is separately enabled only when actual Analytics-storage choice permits it; denial stops collection and requests deletion of unsent reports. ML Kit may send app/device and installation identifiers, performance, feature-size and diagnostic metadata to Google; recognition runs on-device and the App does not intentionally upload the scanned code or image as a beekeeping record. In the atest build, production Firebase collection is deactivated. Local records can be deleted in the App; the Recently Deleted area may retain deleted records for up to 30 days. Review exports and backup destinations separately.

Car Code Guide: offline vehicle references and repair records

Car Code Guide (Check Engine Light: OBD2 Codes, package com.eztools.obd2.codeguide) is an offline reference and does not connect to a vehicle, diagnose a fault, read a VIN, or request a plate, camera, microphone, contacts, or device location. Garage, mileage, observations, quotes, notes, search history, saved codes, preferences and video-reward state are stored locally and are not uploaded to an App cloud service. Product Analytics uses fixed events; the code_not_found event may include only the normalized trouble-code string, not raw search text or local repair records.

Production advertising uses Google Mobile Ads and UMP. Firebase Analytics uses the standard production collection defaults, including AAID and personalized-ad signals where available, automatic screen views, and actual stored UMP purpose choices; unset, not-required, or unknown consent signals are not converted into a grant or denial. These defaults are technical configuration, not evidence of a user clicking consent. Crash reports are held on the device until the app has refreshed your privacy choices and confirmed the required consent. Reports are not uploaded while a privacy form is open; declining the relevant purposes stops reporting and requests deletion of unsent reports. There is no separate report-upload button. Google controls its service data and request channels. No Firebase App Check is used.

Nyra: local and network media playback

Nyra (Android package com.eztools.video.player) plays media you select from your device and network streams you provide. Library entries, playback history, bookmarks, playlists and app preferences are handled by the app on your device. The current Android project does not configure a Nyra account or service backend and does not include Firebase Analytics, Crashlytics, or AdMob. When you open a network stream, your request, IP address and any information included in the stream URL are sent to the server that hosts that stream; that provider controls its own logs and privacy practices. Use streams and media you are authorized to access. No fixed provider retention period is stated.

3. Features That Communicate With Online Services

Book, product, search, and web features

When EZScanner displays a recognized book or product result, it can automatically send the ISBN to Google Books or the product barcode (GTIN) to Open Food Facts to retrieve a preview. These services receive the lookup identifier and normal connection information, such as your IP address. The camera image is not sent with these preview requests.

If you use a search, map, website, email, calling, contact, payment-link, or sharing action, the relevant content is passed to the service or application that handles that action. Depending on your link-review setting, EZScanner may also automatically open a recognized web address after a scan, sending the web request to the destination site. Enabling link review lets you inspect the destination before opening it. Websites opened in the in-app browser can use cookies, including third-party cookies, and local web storage. Those websites and the applications you choose have their own privacy practices.

Optional cloud background removal

Some PixCompress versions offer cloud-based automatic background removal. When you explicitly start this operation, the App prepares a temporary working copy of only the selected photo. It applies the photo orientation, limits the longest side to 1600 pixels, and re-encodes the copy without the original EXIF metadata, including embedded GPS metadata.

The App uploads the working copy to Firebase Storage and sends a processing request to Firebase Cloud Functions. The request includes a generated request identifier, storage location, a cleaned version of the original filename, file type, size, and dimensions. The App downloads the generated PNG foreground mask and performs manual refinement and final export locally. These uploads are used to provide the requested background-removal result.

The App requests deletion of the temporary input and generated mask after download and also attempts cleanup when processing fails. It retries failed deletion requests a limited number of times. A network or service failure can delay deletion; we do not promise a fixed automatic-deletion deadline. You can contact us to request assistance with deletion. Manual cutout and versions that use on-device segmentation do not upload the photo for background removal.

4. Usage, Diagnostics, and Configuration Data

In Apps and versions that integrate Firebase, we use the relevant services to understand feature usage, diagnose problems, measure performance, and provide configuration updates. Depending on the service, the data can include:

EZStatus uses Google AdMob with UMP for advertising and Google Play Billing for optional premium features; ad requests depend on privacy choices and App eligibility, while purchase options depend on Play catalog availability. It uses Analytics with the standard production baseline unless opted out and separate off-by-default Crashlytics; it does not include Performance Monitoring, Remote Config, or cloud media processing. EZScanner uses Analytics, Crashlytics, and Remote Config. PixCompress also uses Performance Monitoring in versions where it is enabled. Handfont uses Analytics and Crashlytics by default in its production package and may request Google AdMob ads for eligible free users; its production Analytics configuration permits AAID and personalized-ad signals where available. The separate development test package uses Google sample ad units. Custom Handfont events use fixed names for completed operations and have no content parameters. Songlet uses Remote Config for display settings and the standard production Analytics collection baseline, and does not include Crashlytics or Performance Monitoring; its account, generation, and purchase processing is described in the Songlet sections above. PixMagnify and Beestead use the product-specific Analytics defaults and controls described in their sections. Car Code Guide's Firebase and UMP behavior is described in its section. Field Notes uses UMP privacy choices for advertising and, where applicable, Google consent mode; its standard Analytics defaults do not override recorded purpose choices. Nyra currently has no Firebase Analytics, Crashlytics, or AdMob integration. Technical reports and SDK data remain subject to the handling described in this policy and the relevant provider's policy.

5. Advertising and Purchases

Ad-supported Apps use Google AdMob and, depending on the App and advertising configuration, mediation partners such as InMobi and Liftoff/Vungle. Their SDKs may collect IP address, approximate location, device and App details, advertising or App-scoped identifiers, ad interactions, and diagnostic information. They use this information to deliver and measure ads, support personalization where applicable, and detect fraud or abuse.

You can use the advertising-ID and privacy controls provided by your device, together with any consent or privacy controls available in the App. Removing an advertising ID does not stop every category of technical data collection. An ad-free purchase removes the ads included in that offer; it does not necessarily disable diagnostics or other online features.

Where purchases or subscriptions are available, Google Play processes the payment. The App receives product and purchase information, such as the purchase token, purchase state, and entitlement status, to acknowledge purchases and provide or restore access. We do not receive your full payment-card details. Google Play manages payment methods, subscriptions, and its transaction records.

EZStatus uses Google AdMob advertising through the EZTools ads SDK and Google User Messaging Platform (UMP). The App may request configured ads only when UMP's advertising-request check and the App's placement, privacy, and entitlement rules allow it; no particular ad is guaranteed to be available or shown. Ad providers may process connection, device and App information, advertising identifiers where available, ad interactions, and diagnostics to deliver, measure, and protect advertising, as described above. EZStatus offers optional premium features through monthly and yearly subscriptions and a one-time lifetime purchase; options are presented only when Google Play returns them as available, with price and applicable billing terms shown by Google Play before purchase. Google Play processes payment, while EZStatus uses purchase and entitlement status to provide or restore access. A pending purchase does not grant the paid entitlement.

In the production Handfont configuration, eligible free users may see one Google AdMob banner within the font library after the App's Google User Messaging Platform check permits ad requests and a successful Google Play purchase query confirms that no membership is active. The App may preload configured interstitial and App Open ads, but has no display scene for either format or for MREC. Active membership removes eligible in-app ads; the membership and purchase screens do not show ads. If the consent flow requires it, Settings provides an entry to reopen advertising privacy options. The separate development test package uses Google's sample ad units. Handfont offers a monthly and a yearly auto-renewing subscription and a one-time lifetime product when Google Play returns them as available. The Play purchase screen presents the current price and applicable offer terms before you confirm. The App uses purchase information to grant, restore, or end membership access; a pending purchase does not grant membership. Creating and previewing fonts and basic PNG image export remain available without purchase.

Songlet: ads, daily points, and verified rewards

Eligible free users may see a banner in the library and an interstitial after a successful export or ringtone action. Rewarded video is optional and begins only when you choose it. Google User Messaging Platform checks the applicable privacy requirements before ad requests; when required, you can reopen advertising privacy options in Settings to change or withdraw your choices. Active Songlet Pro removes banners and interstitials; an optional rewarded ad can still be requested. The separate development package uses Google's test ad units. Songlet does not request precise location permission or send your prompts, lyrics, or audio to its advertising SDK.

To validate a rewarded ad, Songlet sends AdMob an opaque Songlet account identifier (Firebase UID) and a random, short-lived reward nonce. AdMob sends our backend a signed verification containing that identifier, nonce, ad-unit reference, transaction ID, reward metadata, and event time. We store reward transactions and daily counters to prevent duplicate grants and enforce the displayed limit. We do not rely on a client's claim that an ad was completed. Google may collect advertising identifiers where available and permitted, IP address, approximate location, app/device details, ad interactions, and diagnostics for ad delivery, measurement, and fraud prevention as described in Section 5. Declining personalization does not eliminate all technical advertising processing.

Our server tracks daily gift claims, credit sources, expiration times, and spending/refunds. Daily gifts and rewarded-ad points expire at the next 00:00 UTC; subscription gifts also expire when the relevant paid entitlement ends. Purchased credit-pack points have no scheduled expiry. Failed generation returns credits to their original source without extending an expired grant. The App shows the current amounts and limits before the related action.

6. Support, Purposes, and Sharing

If you email us, we receive your email address, message, and any attachments you send. The App may prefill information such as its version, device model, operating-system version, language, or a rating you selected. You can review the message before sending it.

We use the information described in this policy to provide the requested tools and cloud operations, maintain purchase entitlements, answer support requests, diagnose and improve the Apps, deliver and measure ads where applicable, protect the services from abuse, and meet legal obligations. We do not sell your personal information.

Information is shared with the service providers involved in the relevant feature, with the applications or destinations you use to open or share content, and where required by applicable law or valid legal process. The applicable providers include:

7. Retention and Deletion

Local history and settings are kept on your device, subject to any history limits, cleanup rules, or Trash-expiry rules provided by the App. You can also delete records, clear the App's data, or uninstall the App. Where Trash is available, moving an item there is not permanent deletion. Saved gallery images, exported files, shared copies, and backups can remain outside the App and must be removed separately from their locations; deleting a history record does not delete those copies. Your device, gallery, or chosen storage service may also back up or synchronize saved files according to your settings and that service's policy.

For EZStatus, local settings, source references, history, and imported sticker images remain until you remove them using the available controls, clear App storage, or uninstall; temporary records may also be removed during routine cleanup. Storage cleaner offers separate actions for temporary cache, status history, and the Saved index. Clearing cache does not delete the private sticker library or saved gallery media, and clearing history or the Saved index does not delete the corresponding gallery files. Imported stickers can be deleted from the library. Disconnecting a folder ends its retained access but does not erase the original folder or exported copies. Delete those copies separately in your gallery, file manager, chosen sharing app, or backup service. EZStatus's Android backup rules exclude its databases, shared preferences, and private sticker library from system cloud backup and, where supported by the rules, device transfer. This does not prevent your gallery or storage provider from backing up exported media under your settings.

For EZStatus diagnostics, Google's Firebase documentation states that Crashlytics keeps crash stack traces and associated identifiers for 90 days before starting removal from live and backup systems. Analytics retention depends on the Google Analytics property settings and the data category; this policy does not assert an unverified fixed retention period. We use these services for the purposes described above and handle privacy requests through the contact in Section 9. Local data cleanup does not delete cloud diagnostics already transmitted.

For Handfont, font projects, original handwriting and imported images, creative drafts and photo copies, favorites, saved keyboard clipboard items, and settings remain on your device until you delete them in the App, clear App storage, or uninstall the App. Deleting a font project removes it and its original handwriting from the App. Exported images, PDFs, font files, printed pages, and backups remain wherever you saved, shared, or printed them and must be deleted there.

Handfont's Firebase usage and crash data is retained according to the settings and policies of the associated Google Analytics and Firebase services. Clearing local App data or uninstalling does not necessarily delete information already sent to Google. Contact us using the address below for privacy requests. See Firebase Privacy and Security for provider processing.

For Songlet, songs, imported audio, editing drafts, library details, pending request inputs, and settings stay in App-private storage until you delete them in the App, clear App storage, or uninstall the App. Copies saved to your phone's music, set as ringtones, or shared remain where they were saved and must be deleted there. Uninstalling does not delete your online account or server records. Back up songs you want to keep before deletion or uninstalling.

Request deletion of your Songlet account and associated personal data through Songlet account and data deletion or [email protected]. The page is available after uninstalling, without reinstalling. For a Google-linked account, send from the linked email address and include the Songlet user ID if available; anonymous users can use the ID prefilled in Settings or contact support for ownership verification. A user ID alone is not proof. Support verifies ownership and handles requests manually; opening the page or email does not immediately delete an account. Deletion removes the Firebase Authentication account, linked profile and ordinary associated account, credit, prompt, lyric, generation, support/report and advertising reward records. Active provider requests and files are reviewed using available provider controls or support. Deletion is irreversible; local files are managed separately. Cancel subscriptions in Google Play: account deletion does not cancel automatic renewal.

For Songlet deletion requests, limited purchase, subscription, payment verification, refund or security records may be retained where necessary for legal obligations, resolving orders and refunds, or fraud prevention. Their use is restricted to those purposes. The retention period depends on the applicable obligation or unresolved issue; support explains which records remain, why, and for how long, including any provider limitations. We delete or anonymize retained records when the reason for retaining them ends.

Cloud background-removal files follow the deletion-request process in Section 3. Analytics, advertising, diagnostic, and transaction data are retained according to the relevant service, its configuration, and its retention policies. We retain support correspondence for as long as needed to handle the request, resolve related issues, and satisfy applicable legal obligations. You can request deletion of information we hold about you using the contact below.

8. Security and International Processing

We use reasonable safeguards appropriate to the data, including App-private storage for internal records and HTTPS/TLS for built-in cloud requests. Exported files and content you share are controlled by their destination and may not be encrypted. No storage or transmission method provides an absolute security guarantee.

Online service providers may process information in countries other than your own, including countries where Google and the advertising providers operate. Their privacy and data-processing terms describe their international processing arrangements and safeguards.

9. Your Choices and Privacy Requests

You can manage device permissions, remove local records and files, adjust the App settings that are available, avoid optional cloud operations, and manage advertising preferences and Google Play subscriptions through the relevant controls.

Depending on the law that applies to you, you may have rights to request access, correction, deletion, restriction, or portability of personal information, object to certain processing, or withdraw consent where processing is based on consent. You may also have the right to contact your local data-protection authority.

To make a request, email [email protected] and identify the App and the information or operation concerned. We may need limited additional information to identify the relevant data and verify the request. We cannot directly access or erase files that exist only on your device or copies held by a service you selected; we can explain how to manage them.

10. Children's Privacy

The Apps covered by this policy are general-purpose tools and are not directed to children under 13. We do not knowingly collect personal information from children under 13. If a parent or guardian believes a child has provided us with personal information, please contact us so we can investigate and take appropriate deletion steps.

11. Changes and Contact

We may update this shared policy as the Apps and their data practices change. We will publish the updated policy on this page with a revised effective date and provide any additional notice or consent request required for a material change.

For privacy questions, support, or deletion requests, contact the EZTools developer at [email protected].