Zapi Privacy Policy

Effective Date: September 17, 2026

Last Updated: September 17, 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
Detailed browser data Full URLs, paths, query parameters, fragments, page titles or content, bookmarks, tabs, detailed browsing history, and downloads Stored locally on your device, except that a website receives the request required to load it Provide browser and download functions
Search text Words or text entered in the address or search field Processed locally by Zapi; sent to the selected search engine when you initiate a search Perform the search you request
Optional domain-level browsing analytics Hostname or domain only, page-load result, entry source, event time; excludes paths, query parameters, fragments, page titles, page content, and search text Zapi servers after any required consent Understand feature use, reliability, and abuse
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

Signing in does not cause Zapi to upload your detailed browser history, bookmarks, tabs, downloads, full URLs, or search text to your Zapi account. Those items remain device-only in this version, except for the request sent to a website or search engine that you choose to use.

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

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.

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
Detailed browser data, bookmarks, tabs, downloads, and search text Stored on the device until you delete them, clear App data, or uninstall the App
Domain-level and whitelisted App event logs Up to 30 days, then deleted or irreversibly aggregated, unless a shorter period is configured
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. 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.

13. Contact Us