Effective date: October 10, 2026
We are the independent developer of the EZTools applications ("EZTools", "we", "our", or "us"). This is our shared developer privacy policy for the applications we publish that link to this page, including EZScanner, PixCompress: Photo Compressor, EZStatus: Status Saver - Video ("EZStatus", Android package com.eztools.status.saver), Handfont: Handwriting to Font ("Handfont", Android package com.eztools.handfont.fontmaker), and Songlet: AI Ringtone Maker ("Songlet", Android package com.eztools.airingtone.songlet) (the "Apps"). Our privacy and support contact is eztoolsupport@icloud.com.
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.
PixMagnify users: PixMagnify has a separate Privacy Policy. PixMagnify's data practices are described there and are not covered by this shared policy.
The core tools in these Apps do not require you to register a personal EZTools account. Content you scan, create, select, or send to support may nevertheless contain personal information, which we handle as described below.
EZStatus users: read the product-specific details below. For the EZStatus 1.0.0 release configuration covered here, advertising, in-app purchases, notification-listener message history, and automatic replies are disabled. Optional Google Analytics for Firebase and Firebase Crashlytics are included, with separate in-app choices that are off by default. Sections about other Apps' advertising, cloud photo processing, Performance Monitoring, or Remote Config do not describe this EZStatus release. We will update this policy and provide any required disclosures and consent before introducing different data practices.
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. 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. Songlet does not enable Google Analytics for Firebase collection and does not include Firebase Crashlytics or Performance Monitoring. Sections about other Apps do not automatically describe Songlet.
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.
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 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. This release does not integrate advertising or cloud media-processing SDKs. 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.
In the production App, you may independently enable Usage analytics and Crash reports in Settings > Privacy & terms. First-use setup links to this policy and explains that these optional features are off. Both choices are off by default and neither is required to use the available tools. Enabling a choice is your consent to the corresponding processing below. You can withdraw that consent at any time in the same settings without losing access to the tools. Production Firebase is not included in the separate Debug test package.
Turning usage analytics off disables further Analytics collection and requests a reset of local Analytics data and the app-instance identifier. 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. We do not promise that an identifier reset, uninstall, or local cleanup deletes previously uploaded data.
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, and app-instance or installation identifiers. 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. Handfont disables Firebase Analytics advertising-ID collection and advertising personalization. Its Android manifest declares the advertising-ID permission to match its Play Console declaration. When an eligible ad request is made, Google's advertising services may access the advertising ID where available and permitted by your device settings; these advertising data practices are separate from Firebase Analytics settings.
The optional online font library contacts the Google Fonts provider in Google Play services only after you choose a font. The request names the font family; Google receives normal connection information, such as your IP address, when Google Play services downloads it. Your text and handwriting are not sent. 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 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 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.
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.
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.
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 only optional Analytics and Crashlytics under the separate choices described above; 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; it does not include Performance Monitoring, Remote Config, or cloud media processing. 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, does not enable Analytics collection, and does not include Crashlytics or Performance Monitoring; its account, generation, and purchase processing is described in the Songlet sections above. Technical reports and SDK data remain subject to the handling described in this policy and the relevant provider's policy.
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.
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.
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.
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:
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 eztoolsupport@icloud.com. 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.
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.
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 eztoolsupport@icloud.com 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.
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.
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 eztoolsupport@icloud.com.