Zapi Privacy Policy

Effective Date: November 14, 2026

Last Updated: November 14, 2026

Kaeson Technology Limited (“Zapi,” “we,” “us,” or the “Operator”) respects your privacy. This Privacy Policy explains how information is processed when you use the Zapi mobile application (the “App”), create or manage a Zapi account, use synchronized features, receive notifications, or interact with sharing and advertising functions.

Where consent or permission is required, Zapi will ask before the relevant collection or device access begins. Declining an optional permission does not prevent you from using unrelated features.


1. Who We Are

Item Details
Operator Kaeson Technology Limited
Privacy Contact [email protected]
Website https://www.zapiapp.com

2. Information We Process

The information processed depends on the features you use and the choices you make.

Category Examples Where it is processed Purpose
Account and profile data Zapi account identifier; linked sign-in method; email address; Google or Apple provider identifier; limited profile fields authorized by you Zapi and the relevant identity provider Create, identify, secure, and manage your account
Authentication and session data Login time, session token, active-device state, IP address, authentication result, security events Zapi and the relevant identity provider Sign you in, enforce one active session, prevent abuse, and protect the account
Email verification data Email address, verification-code record, delivery result, attempts, expiry time, and risk-control information Zapi and our email-delivery provider Send and verify the six-digit sign-in code
Synchronized account data My List, watch history, playback position, update time, and synchronization status Zapi servers and your signed-in device Provide account features and restore the latest available account data
Device and notification data Device or installation identifier, operating system, App version, language, distribution channel, Firebase app-instance identifier, push token, and current account-device binding Zapi and our notification provider Compatibility, security, analytics, and delivery of device or account-related notifications
Local browser data Bookmarks, tabs, local browsing history and downloaded files Stored on your device; visiting a website sends the requests needed to load it Browsing, local records and downloads
Browsing URLs and search terms Complete URLs visited, including URL parameters, and text entered for search Zapi and analytics service providers; your chosen websites or search engines also receive the requests needed for your actions Browsing and search, security, troubleshooting, usage analysis and product improvement
App analytics and diagnostics Whitelisted events, feature interactions, app version, language, session state, success or failure categories, crash and performance data Zapi and our analytics or diagnostics provider after any required consent Operate, measure, troubleshoot, and improve the App
Advertising data, when advertising is enabled Ad request, placement, display or completion status, frequency data, limited device or advertising identifiers, IP address processed in transit, and fraud-prevention signals Zapi and the disclosed advertising provider Deliver, limit, measure, and protect advertising-supported features
Sharing and link data Shared item or campaign identifier, link code, channel, click/open result, installation status, server-time usage count, and destination application selected by you Zapi, the relevant link service, and the sharing destination Create shares, route links, enforce limits, and measure successful opens
iOS clipboard link code A Zapi-formatted link code detected during an eligible first launch after installation Read locally on the device only after iOS permission; used to resolve the intended in-App page Complete deferred routing on iOS
Information you submit Feedback, support messages, contact details, images, and logs you choose to send Zapi and any support provider Respond to requests and diagnose issues
Local tool content Selected photos/Word files, OCR text, QR content and results On-device; separate user-initiated sharing, opening or feedback passes content to the chosen recipient Translation, conversion, recognition, saving and sharing
AI translation and photo uploads Confirmed text, languages, follow-ups, necessary context and selected AI photos Selected photos uploaded to Cloudflare R2 and sent to MiniMax for parsing; text and necessary context also sent to MiniMax AI text/photo translation and follow-ups
Tool allowance and reward data Necessary account/device identifiers, counter date, AI reply count, ad completion and reward results Zapi and the disclosed advertising provider, as required for the chosen reward Apply tool allowances, issue rewards and prevent duplicate rewards

Signing in does not synchronize your local bookmarks, tabs or downloaded files to your Zapi account. Browsing URLs and search terms are sent to Zapi or analytics service providers for the purposes above. This operational processing is separate from account synchronization.

Zapi does not receive your Google or Apple password. If you use email sign-in, Zapi verifies the code you enter rather than collecting an email password.


3. How Information Is Collected and Your Choices

We collect information:

Where applicable, the App provides controls for optional analytics, notifications, clipboard access, and other device permissions. You can change many permissions in your operating-system settings. Withdrawing permission stops future access but does not automatically delete information already lawfully processed.


4. How We Use Information

We use information to:

Depending on your location, our legal basis may be your consent, performance of a service you request, compliance with law, or our legitimate interests in security, reliability, fraud prevention, and product operation.


5. Service Providers and Disclosures

We do not sell personal information. We disclose information only as needed for the purposes described below.

Recipient Purpose Information that may be disclosed
Google Google sign-in; Firebase analytics, diagnostics, push notifications, or Android link functions that are enabled in the distributed build Authorized Google profile fields, provider identifier, App/device data, push token, whitelisted events, diagnostics, and link results as applicable
Apple Sign in with Apple and iOS platform functions Authorized Apple account fields, provider identifier, authentication result, and device permission result as applicable
Alibaba Cloud Direct Mail or another disclosed email-delivery provider Deliver email verification codes and report delivery status Email address, message template, delivery metadata, and security information needed for delivery
Zapi hosting and infrastructure providers Account storage, synchronization, link resolution, security, backups, and support Account, synchronized, technical, sharing, and support data needed to provide the service
Advertising providers enabled in the distributed build Display, limit, verify, and measure advertisements Ad request and result, limited device or advertising identifier, IP address in transit, frequency, and fraud signals as disclosed in the App
Websites, search engines, and applications selected by you Complete a visit, search, sign-in, share, or external-app action you request The request and content needed to complete your chosen action
Authorities, courts, or professional advisers Comply with law and protect rights, safety, and security Information reasonably necessary for the lawful request, investigation, or claim
Google ML Kit (Android standard translation) Local models and SDK operation Model requests and API performance/usage metrics, not content sent for standard translation
Apple system translation (iOS) Standard translation through iOS system capabilities Selected translation content and necessary system information processed through Apple’s translation capabilities under its privacy rules; see Section 12.3
Cloudflare (R2 object storage) Upload and storage of AI photos Selected AI images and necessary storage metadata; images are automatically deleted one day after upload
MiniMax AI translation, image parsing and follow-ups Confirmed text, selected AI photos, language choices and necessary conversation context; photos processed only for the request and not retained by MiniMax

Providers process information under their own privacy terms and, where acting for Zapi, under contractual or other safeguards appropriate to their role.


6. Advertising

Some distributed versions of Zapi may include advertising-supported playback or continuation features. When advertising is enabled, the App will identify the relevant provider and request any permission or consent required by law before personalized advertising or access to protected device identifiers begins.

If you choose a sharing option instead of watching an advertisement, Zapi may record the completion result and a server-time counter to apply the daily limit. The receiving application controls whether and how the content is ultimately posted or delivered.

For optional rewarded tool ads, Zapi may also process ad completion, reward delivery and AI reply counters to verify the reward you choose to claim.


7. Clipboard, Deep Links, and Deferred Links

7.1 If Zapi is already installed, a valid Zapi link may route directly to an in-App page. On supported Android devices, a deferred-link service may pass the intended destination after installation.

7.2 On iOS, Zapi may use a link code copied from our landing page for eligible first-install routing. After other required first-run prompts, iOS may ask whether Zapi can access the clipboard. If you allow access, Zapi checks locally for a valid Zapi-formatted code and may open the related page. If no valid code is found, or if you decline, Zapi continues to the regular entry page.

7.3 Zapi does not store or upload unrelated clipboard content for this function. The first-install check is not used for routine App launches. Zapi does not clear or modify the clipboard as part of this check.


8. Storage, Security, and Retention

Data General retention approach
Account and linked-method data Kept while the account is active; deleted or de-identified after account deletion, except for limited legal, security, fraud-prevention, or backup retention
My List, watch history, and playback progress Kept until you remove the item, clear the available history, or delete the account
Email verification code Valid for up to 30 minutes; code, delivery, rate-limit, and security records may be retained for a limited operational period to prevent abuse and resolve delivery issues
Session and account-device notification binding Kept while valid; replaced or invalidated when another device signs in, the account changes, you sign out, or the account is deleted
Local browser data, bookmarks, tabs and downloaded files Stored on the device until you delete them, clear App data or uninstall the App
Browsing URLs, search terms and App event logs Kept for no more than 30 days, then deleted or de-identified
AI photos uploaded to Cloudflare R2 Automatically deleted one day after upload
AI photos sent to MiniMax Processed only for the requested image parsing and translation; not retained by MiniMax
Firebase Analytics event-level data Configured for up to 2 months when Firebase Analytics is enabled
Support and feedback records For the request and up to 180 days after closure, unless law or an active dispute requires longer retention

We use safeguards appropriate to the nature of the information, including encrypted transmission, access controls, credential separation, and session revocation. No system is completely secure, and we cannot guarantee absolute security.

Backup copies may take additional time to expire. During that period, they are isolated from ordinary use and retained only for restoration, security, or legal needs.


9. Account Deletion and Your Rights

9.1 You may delete your account in Settings & Help > Account information > Delete account. After you review and confirm the deletion notice, Zapi will process the request and end active sessions.

9.2 Account deletion removes or de-identifies the Zapi profile, linked sign-in methods, My List, synchronized watch history, and synchronized playback progress, subject to limited retention described above. It does not delete your Google, Apple, or email account.

9.3 Local downloads, bookmarks, detailed browser history, tabs, and other device-only information are not part of the Zapi cloud account. Delete them through the App or device, clear App data, or uninstall the App if you also want them removed.

9.4 Where applicable, Zapi will revoke or remove its Sign in with Apple authorization relationship when the Zapi account is deleted.

9.5 Depending on your location, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, and to withdraw consent. Contact [email protected]. We may need to verify your identity and will respond within the time required by law. You may also complain to your local data-protection authority.


10. International Processing

Zapi and its providers may process information outside your country or region. Where required, we use contractual, organizational, and technical safeguards for international transfers. The specific processing location may depend on the provider, feature, and region in which the App is offered.


11. Children’s Privacy

Zapi is not directed to children under 13 or the higher minimum age required in a user’s location. We do not knowingly create accounts for or collect personal information from children without the authorization required by law. If you believe a child has provided information, contact [email protected].


12. Tools and AI Translation Data

12.1 Selected content and permissions. We process the photos you take, photos/Word files you select, text you enter and QR content only for the function you request. Camera access enables capture/scanning; system pickers provide the selected files; saving uses the available system method. Declining permission affects only dependent functions. Paste reads the clipboard when you choose it, and Copy writes the selected result; tools do not continuously monitor unrelated clipboard contents.

12.2 Local tools and exceptions. Photo OCR, Android language-pack translation, images-to-PDF, Word-to-PDF and QR scanning/creation process content on-device, without uploading original images, Word files or QR content to Zapi for those local functions. Exception: choosing AI photo translation uploads the selected image to Cloudflare R2 and also sends it to MiniMax for parsing; see 12.4. For iOS standard translation, see 12.3. Opening URLs, sharing or feedback are separate choices; recipients receive necessary information.

12.3 Android and iOS standard translation. Android uses Google on-device language models without sending source text or translations to Google for translation. Model downloads and updates require a connection, and Google ML Kit processes API performance and usage metrics; see ML Kit Terms & Privacy and Google Privacy. iOS uses Apple system translation capabilities. Language downloads and the processing of content selected for system translation are subject to your system settings and Apple Translation & Privacy.

12.4 AI text and photo processing. After disclosure and your express permission, Zapi sends the text you submit or confirm, language choices, follow-ups and necessary current conversation context to MiniMax to generate translations and replies. For AI photo translation, the selected image is uploaded to Cloudflare R2 object storage and also sent to MiniMax for image parsing and translation. MiniMax processes the image only to fulfill this request and does not retain it. Unrelated files and your full gallery are not sent. If you decline, Zapi does not upload the image or send the AI request; standard translation remains available.

12.5 Training and history. AI translation content is not used to train models. Zapi conversation history is stored locally, with no Zapi cloud-history sync; uninstalling removes App-local history. Copies you export, copy, capture or retain through system backups must be managed separately. Local history is distinct from server processing: MiniMax receives requests to return replies. Necessary service, security and abuse-prevention processing is governed by the applicable API arrangement and MiniMax API Privacy Policy. Deleting local history does not mean every third-party record is immediately deleted. Contact Zapi for relevant data requests.

Images uploaded to Cloudflare R2 are automatically deleted one day after upload. Deleting a local conversation or uninstalling Zapi does not itself trigger immediate deletion of the cloud image. For a deletion request or other data rights, contact [email protected].

12.6 Allowances, metrics and feedback. Necessary metadata such as request result, time, counters, task state and account/device identifiers supports AI allowances, ad rewards and error diagnosis. The daily base allowance is 10 AI replies; each valid optional ad reward adds 5 replies. Text, photos and follow-ups share these replies. Both base and ad-reward allowances reset at 00:00 UTC daily, without carry-over. Translation bodies, whole images and document contents are not routine product-analytics event payloads. Feedback sends only the text, reply or attachments you choose to submit. Do not submit personal information you lack permission to disclose, passwords, payment credentials or confidential material.

12.7 Results and temporary files. Conversion caches, language packs, local conversations and files saved to a gallery/file manager are separate. Word conversion does not restore previous conversion records on a new visit; saved PDFs are not automatically removed when the tool closes. Manage local data using available deletion controls, system file management, clearing App data or uninstalling. Backup and shared copies are managed by the relevant systems or recipients.


13. Changes to This Policy

We may update this Policy when our product, providers, or legal obligations change. Material changes will be communicated through the App, our website, or another appropriate channel. Where a change requires consent, the relevant new processing will not begin until consent is obtained.


14. Contact Us