Bitcoin HashNova AI-X in Privacy Policy

Bitcoin HashNova AI-XZIPEX LOGISTICS · PRIVACY

Privacy Policy

Bitcoin HashNova AI-X
Developer / operator: ZIPEX LOGISTICS
Privacy contact: zipexlogistics7@gmail.com
Draft prepared: 11 September 2026

DRAFT FOR DEVELOPER REVIEW — This document proposes privacy practices based on the supplied dependency catalog and app screens. The released app, backend, advertising configuration and operating procedures have not been inspected. Confirm the practices and resolve the marked sections before publishing. Set an effective date when this policy is adopted.

1. About this policy

ZIPEX LOGISTICS ("we", "us" or "our") operates Bitcoin HashNova AI-X (the "App"). This policy explains how information is handled when you use the App, sign in, interact with advertisements, purchase access, or contact us. Different information is involved depending on the features you use and the services enabled in your version of the App.

2. Information handled by the App

Account information. If you sign in with Google, the sign-in service can provide an account identifier, email address, display name and profile image, according to the permissions you approve. Authentication credentials or tokens help establish your session. Firebase Authentication also processes technical information such as IP addresses and user-agent information to operate sign-in and prevent abuse.

App activity and preferences. The App may store your selected plan, subscription entitlement, session progress, virtual balance, reward activity, language and notification preferences. Information synchronized with your account is stored through the configured backend. Information stored only on your device remains local unless a feature sends it to a service.

Service and device information. Firebase services can process app and operating-system versions, installation identifiers, IP addresses and service-request information. Remote Config uses details including language, country code and time zone to deliver suitable configuration. Realtime Database stores the account-linked information that the App sends to it. See Firebase's data disclosures.

Notifications. When Firebase Cloud Messaging is enabled, installation identifiers and messaging tokens support message delivery. Turning off notification display in Android settings does not necessarily remove an existing token or stop all messaging-service processing.

Advertising information. When Google Mobile Ads is enabled, Google reports collecting and sharing IP addresses, interactions such as taps and video views, diagnostic information, and device or account identifiers. An IP address can indicate approximate location. Advertising-ID availability depends on device settings and the App's configuration. This information supports advertising, measurement and fraud prevention. See Google Mobile Ads data disclosures.

Purchase information. If you purchase through Google Play, the App can receive a purchase token, product or plan identifier, purchase time, order reference when available, and purchase or subscription status. This information supports access verification, restoration and purchase support. Google Play handles the payment flow; payment-card details are not part of the purchase-token record described here.

Support messages. If you email us, we receive your email address, the information in your message and any attachments you choose to send. Please share only what is needed to resolve your request. Do not send passwords, wallet seed phrases, private keys or full payment-card details.

3. Virtual balances and wallet features

Activity shown as a virtual BTC balance or simulation progress is treated as App activity. A virtual balance label does not by itself establish that a real cryptocurrency transaction has occurred.

PUBLISHER ACTION — The supplied screens also show wallet and withdrawal features. Confirm whether these are functional. If users can submit a wallet address or request an actual payout, add the precise information collected, purposes, payment or blockchain providers, public-ledger implications, and retention practices here. Do not publish this draft as a complete wallet or payout disclosure until that is resolved.

4. Why information is used

We use the information relevant to each feature to maintain accounts, save progress and settings, provide and restore purchased access, deliver notifications, respond to support requests, prevent misuse, and maintain the App. Advertising providers use the advertising information described above to deliver and measure ads and detect invalid activity. Configuration services help us make features available and adjust their operation.

Where processing requires your consent, we request it before that processing. Other processing may be necessary to provide a feature you request, protect the service, or meet an applicable legal obligation. Contact us for information about the basis for processing your information in your location.

5. Services and recipients

The following services are covered by this draft when enabled in the released App:

Service	Role
Google sign-in and Android Credential Manager	Account sign-in and credential exchange
Firebase Authentication and Realtime Database	Account services and synchronized App records
Firebase Cloud Messaging and Remote Config	Messaging and App configuration
Google Mobile Ads / AdMob	Ad delivery, measurement and fraud prevention
Google User Messaging Platform (UMP)	Advertising privacy messages and choices
Meta Audience Network, through Google mediation where configured	An additional advertising source
Google Play Billing	Purchases, subscriptions and restoration

If Meta receives an advertising request through mediation, its handling is subject to its applicable terms and privacy disclosures. The ad sources receiving requests depend on the active mediation configuration and privacy choices. Provider information is available in the Google Privacy Policy, Firebase privacy information and Meta Privacy Policy.

Providers can process data to supply their services and, where their terms provide, for their own stated purposes. We may also disclose information when necessary to comply with a valid legal requirement, address fraud or security incidents, or protect legal rights. Any disclosure must be limited to its purpose. This policy does not promise that all provider processing ends merely by uninstalling the App.

6. Advertising choices and permissions

Where required, an advertising privacy message explains available choices. Google UMP can present this message and let you revisit your choices through the App's privacy-options control. We apply the choices to the relevant advertising integrations. Declining personalized advertising does not necessarily stop every ad or all processing needed for permitted advertising, measurement or fraud prevention.

You can manage notification permission and other granted permissions through Android settings. Android also provides advertising-ID controls, depending on the device and OS version. A permission choice affects the relevant device feature; it does not automatically delete account records already stored by a service.

PUBLISHER ACTION — Verify that the privacy-options control exists where required and that consent or opt-out signals reach every enabled advertising partner. UMP's presence in Gradle does not establish that this has been implemented.

7. Retention and deletion

Our proposed retention approach is to keep information only for the purpose for which it is needed. Account and synchronized progress records remain while the account is maintained, subject to a deletion request. Support records remain as needed to resolve and follow up on a request. Limited purchase, security or dispute records may need to remain for an applicable legal obligation or a documented fraud-prevention purpose. When no longer needed, information should be deleted or de-identified.

Providers can have separate live-system and backup deletion schedules. Firebase publishes service-specific details in its privacy information. Local data can remain until it is cleared from the device; clearing local data does not itself erase server records.

PUBLISHER ACTION — Replace the proposed wording with your actual retention practice. Specify the deletion completion period, backup-removal schedule, and the categories, reasons and periods for any records retained after deletion. No retention period has been verified from the supplied files.

8. Requesting access or deletion

You can contact zipexlogistics7@gmail.com with a privacy inquiry, correction request or account-deletion request. For deletion, use the subject "Delete my Bitcoin HashNova AI-X account" and provide the email or user ID associated with the App. Do not include your password or wallet secrets. We may need to verify that the request belongs to you using proportionate information.

Under the proposed deletion procedure, we delete the App account and its associated records under our control, ask applicable service providers to delete associated records they process for us, and explain any information that must be retained. Removing only the sign-in account is not a substitute for deleting the related App records. Deleting an App account does not delete your Google account.

Manage an active subscription separately through Google Play; do not assume that uninstalling the App or emailing a deletion request cancels billing. You can manage subscriptions at Google Play subscriptions.

Depending on the law applicable to you, you may also have rights to access, correct, obtain a copy of, restrict or object to processing of your information, withdraw consent, or complain to a competent privacy authority. Contact us to make a request. We will explain any identity-verification requirement or legal exception that applies.

PUBLISHER ACTION — Confirm that the contact inbox is monitored and that this deletion process is operational. Add the actual in-app deletion path, public deletion-request page and expected completion time. This document does not create a backend deletion function or a live web request service.

9. Security and processing locations

Our proposed safeguards include encrypted network connections, access restricted to authorized personnel and services, and controls on account and database access. No storage or transmission method is completely secure. We do not promise that security incidents are impossible.

Service providers may process information in countries other than your own. For example, Firebase states that its Authentication service processes data in the United States. Other locations depend on the service and deployment configuration. See Firebase's processing-location information.

PUBLISHER ACTION — Confirm the safeguards, hosting locations and any required international-transfer arrangements. A dependency list does not verify encryption, database access rules or staff access controls.

10. Children's privacy

PUBLISHER ACTION — Specify the intended audience and minimum age for this App, any age-screening or parental-consent process, and the handling of children's data. These facts were not supplied, so this draft does not invent an age threshold or claim that the App is child-directed or adult-only.

If you believe a child has provided information that should not have been collected, contact zipexlogistics7@gmail.com so the situation can be reviewed and the appropriate action taken.

11. Changes and contact

When this policy changes, we will update the version date and provide additional notice or request consent when required. Please review the current policy to understand the practices applicable to your use of the App.

For privacy questions or requests, contact:

ZIPEX LOGISTICS
Bitcoin HashNova AI-X
zipexlogistics7@gmail.com

Draft prepared 11 September 2026 · zipexlogistics7@gmail.com