Magic Text Repeater App

 Privacy Policy — Magic Text Repeater App

Effective date: August 19, 2026

Android package: com.text.repeater.emojitranslator.cloudvaultifyapps

Contact: haseeburrahman47@gmail.com


This Privacy Policy explains how Text Repeater (“we”, “the app”) handles information, including data collected by Google Play services, Firebase, and AdMob. It is written to comply with Google Play User Data and Data Safety requirements.


1) Data processed on your device

You do not need an account. Text you type, generate, copy, or save is processed on your device to provide features (repeat, styles, emoji, presets, history, theme, language, and premium unlock status).

We do not upload that content to our servers for transformation.


2) Data collected off your device

Some data leaves the device through Google SDKs. For Google Play Data safety, this may include:

• Device or other IDs (including Google Advertising ID and Firebase installation ID)

• App activity (screens viewed, button taps, crashes/performance)

• App info and diagnostics

• Purchase history and product identifiers when you buy or restore premium

This data is used for app functionality, analytics, advertising, and fraud prevention. Collection is required for ads, analytics, and Play Billing to work.


3) Advertising

The app shows ads via Google AdMob (banners, native ads, interstitials, and app-open ads) unless you unlock premium.

AdMob and its partners may collect and share Advertising ID, device identifiers, IP address, and app activity to display, personalise, and measure ads.

You can reset or opt out of ads personalization in Android Settings → Google → Ads. Premium removes ads in this app; it does not change Google account ads settings.


4) Analytics and Firebase

We use Firebase Analytics (Google) for anonymous usage insights such as screen views and feature taps. Event data does not include the text you type.

Cloud Firestore is used only to read remote ad settings (for example, whether ads are enabled and interstitial frequency). It does not store your messages.

Missing UI translations may be fetched from a translation service; only interface labels are sent, not your generated content.


5) Purchases

Premium is sold through Google Play Billing. Google processes your payment, Google account, and purchase token. We store a local unlock flag on the device so ads stay off.

We do not receive your full credit-card number. Restore purchases uses your Play account on this device.


6) Data sharing

We share data with Google (AdMob, Firebase, Play Billing, Play in-app review) as described above.

We do not sell your personal information.

If you use Share, Copy, widgets, or open a store/email link, content or requests go only to the app or service you choose.


7) Security

Data sent to Google services is encrypted in transit (HTTPS/TLS).

Local preferences use Android storage; we do not claim independent encryption-at-rest beyond the operating system.

No method of storage or transmission is 100% secure.


8) Your choices and data deletion

This app has no user accounts on our servers, so there is no online profile to delete.

You can delete local data by clearing the app’s storage or uninstalling Text Repeater.

You can clear the on-device translation cache from Menu → Privacy dashboard.

To request help deleting residual data or ask privacy questions, email us. We will respond within a reasonable time (typically 30 days).


9) Children

Text Repeater is not directed at children under 13 and is not designed for the Google Play Families policy as a children’s app.

We do not knowingly collect personal information from children under 13. If you believe a child provided data, contact us, and we will delete it where feasible.


10) Policy changes

We may update this policy when our practices or Google Play requirements change. The effective date at the top will be revised.

Continued use of the app after an update means you accept the revised policy. Material changes will be reflected in the in-app Privacy Policy and should be mirrored on the Play Console privacy policy URL.


Contact us

haseeburrahman47@gmail.com

```

Comments

Post a Comment

Popular posts from this blog

Street View Maps Live Camera

  Privacy Policy Cloud Vaultify Apps developed the Street View Maps Live Camera app, which is supported by advertisements. This SERVICE is offered by Cloud Vaultify Apps free of charge and is meant to be used as is. This page is used to inform visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decides to use our Service. If you choose to use our Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy. The definitions used in this Privacy Policy are consistent with those in our Terms and Conditions, which can be accessed at Street View Maps Live Camera , unless otherwise specified in this Privacy Policy. Information Collection and Use To enhance your experience with our Service, we may need you to provide ...
Read more

Smart Language Translator App

 Privacy Policy Last updated: August 14, 2026 Introduction Smart Translator ("we", "our", or "the app") is committed to protecting your privacy. This policy explains how we collect, use, and safeguard information when you use our translation, notes, to-do list, camera, and related features. Information we collect • Text you translate: Source and translated text may be sent to translation and dictionary services to provide the feature. We do not use this content for advertising or profiling. • Voice input: Speech is processed on-device or via platform services for speech-to-text. We do not store or share voice recordings. • Images: If you take a photo, the app uses the Camera permission. If you choose an existing photo or screenshot, the app uses the Android Photo Picker (or the iOS system picker). We do not access your full photo or video library, and we do not use READ_MEDIA_IMAGES or READ_MEDIA_VIDEO. Selected images are processed on-device (OCR) and ext...
Read more