Effective date: September 23, 2026 · Operator Yapdev · Applies to the Yappliz Android app (com.yappliz.app) and the website yappliz.com.
Yappliz is a communication helper operated by Yapdev: you share or paste a message you're stuck on, pick an intent, and Yappliz drafts ready-to-send replies. This policy describes what we (and our service providers) access, collect, use, store, and share — including third-party AI providers and advertising/billing SDKs. It is written to align with Google Play's User Data and Data safety requirements.
We do not require a traditional login. Message text is sent over HTTPS to our backend and forwarded to AI providers only to generate your replies; we do not keep message content in our database by default. We do keep an anonymous app identity, quota/credit/Pro state, purchase-related records (via Google Play Billing and RevenueCat), and privacy-minimized usage events. If you choose Watch video, Google AdMob may collect advertising and device identifiers. Skipping the video never blocks buying credits, Pro, or Not now. We do not sell your personal data.
When you generate or translate, the incoming message text, optional context you type, and style/profile preferences you chose are sent over HTTPS to our Cloudflare Worker and forwarded to one or more third-party AI providers solely to produce replies or a translation. This is required for the app to work.
Yappliz does not store that message or reply text in our application database (D1) by default. AI providers process the text under their own terms as our processors for this request. Do not submit secrets, passwords, or content you are not allowed to share with a cloud AI service.
On first launch the app creates a random UUID (app_user_id), stores it on your device, and sends it to our backend (and to RevenueCat) so free quota, purchased credits, and Pro status can sync across sessions and reinstalls when you restore purchases. This is not your name or email; it is still an identifier tied to your usage and purchases.
We store on our servers (Cloudflare D1), keyed by app_user_id: free daily usage counters, credit balance, Pro expiry, and a ledger of credit purchases/spends needed for billing correctness and history. Preferences such as style, language, and tutorial state stay on your device unless also needed for a generate request.
Subscriptions and credit packs are sold through Google Play Billing. We use RevenueCat to validate purchases and notify our backend. Purchase history and related identifiers are processed so we can grant and restore Pro/credits. Payment card details are handled by Google, not by Yappliz. See also RevenueCat's privacy policy and Google Play's terms.
We record product events (for example share_received, generate_clicked, reply_copied, paywall and rewarded-ad events) with: event name, an anonymous per-launch session ID, chosen options (intent, plan, language), text length — never the text itself — and rough timing. These help us measure drop-off and usefulness. Events may be associated with your session and, for some server calls, your app_user_id.
Watching a short video is optional and only offered when free daily replies and credits are empty. Completing a video grants 1 extra reply set. Pro subscribers are not shown ads.
When you use Watch video, the Google Mobile Ads SDK (AdMob) may automatically collect and share data such as IP address (which can imply approximate location), advertising ID / other device or account identifiers, app interactions (including video views), and diagnostic information — for advertising, analytics, and fraud prevention. See Google's privacy policy. You can reset or delete your advertising ID in Android settings. Skipping the video never blocks packs, Pro, or Not now.
app_user_id.We do not sell personal and sensitive user data. Transfers to these parties are to operate the app (functionality, security, fraud prevention, advertising for optional rewarded video, and analytics as described).
Traffic between the app/website and our backend uses HTTPS (TLS). Secrets for AI providers and webhook authentication stay on the server, not in the mobile app. No security measure is perfect; please use the app accordingly.
app_user_id, credits, Pro, ledgers): kept while needed to provide the service, prevent abuse, and meet accounting/fraud needs.Yappliz does not use a traditional email/password account. You can still request deletion of data we can link to you:
app_user_id if you have it (or describe the Google Play order / restore situation). We will delete or anonymize server-side records we control for that identity and can remove the related RevenueCat customer record where applicable. Cleared local app data also removes the on-device ID (a new ID is created if you open the app again).Yappliz is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child provided data, contact us and we will delete it.
We and our processors may process data in the United States and other countries where Cloudflare, Google, RevenueCat, or AI providers operate. If you use the app from the EEA/UK/Switzerland, applicable data-protection laws may give you additional rights (access, correction, deletion, restriction, objection). Contact us to exercise them.
Paid features are also described in our Terms of Service (subscriptions, credits, cancellation).
If this policy changes materially, we will update the effective date above. Continued use of the app or site after a material change means you should review the new policy. For Play Store listings we will keep this URL current in Play Console and in the app.