Privacy Policy

Last updated: 25 October 2026

Zaspark is owned and operated by Torzwar Technova Ltd (Formerly - Suapkonnect Advanced Technology Ltd). Torzwar Technova Ltd (Formerly - Suapkonnect Advanced Technology Ltd) is the data controller responsible for the processing described in this policy; references to Zaspark, we, or us refer to that company in operating this service. This policy explains how we handle personal information across our website, accounts, social features, messaging, media, games, subscriptions, payments, and wallets. Contact us at [email protected] about privacy or your information. These pages are available without signing in.

1. Information we collect

This policy covers users and other people whose information is provided through Zaspark, such as someone mentioned in a post or a report. We collect information you provide, information generated when you use the service, and information from the sources described below.

• Account and profile information: information you provide, including your name, username, email address, profile images, biography, country, and date of birth.
• Content you provide: posts, replies, polls, quizzes, uploaded images and videos, captions, hashtags, locations you attach to content, messages as explained below, reports, and support correspondence. Content records may include the author, upload or publication time, file type, size, and other information needed to store and deliver it. Information about someone else may appear in content you submit.
• Security information: password verification records, sign-in and session records, device identifiers, two-factor authentication setup and recovery information, and messaging recovery records. Do not send passwords, passcodes, recovery codes, or one-time codes to support.
• Payment information: purchases, subscriptions, tips, rewards, balances, transaction references, payment and refund status, withdrawal destinations, and verification information required for the transaction. Payment providers collect payment credentials through their own flows; we receive the details needed to verify and reconcile payments.
• Technical information: IP address, approximate location, browser and device information, connection events, cookies, and diagnostic and security logs. If you allow a feature to access your device location, we receive the location you authorize.

Activity and inferred interests: we process views and interactions with content, follows, reactions, bookmarks, searches, game participation and answers, and transaction activity. We use relevant interactions and relationships to identify topics or interests and rank recommendations. These inferences may be incomplete or inaccurate and can change as your activity changes. Account and device identifiers help associate authenticated activity with your account across sessions and devices.

Information from others: we receive basic sign-in information from Google if you choose that option; payment confirmations, refund and payout results from payment providers; and delivery or diagnostic information from service providers. Other users may provide information about you in posts, mentions, messages, gifts, reports, or support requests. We use this information for the relevant service, safety, or transaction purpose described in this policy.

Media processing: when you submit media, we and the providers delivering it process the file and relevant technical information to validate, store, resize, transcode, generate previews, and display it as supported by the feature. Uploaded material and content included in a report may also be reviewed to investigate abuse or enforce service rules. Be careful with personal details, locations, and other information embedded in media you share. Encrypted chat attachments follow the separate protections described in section 4.

2. Google sign-in

If you choose Google sign-in, we receive your Google account identifier, verified email address, name, and profile image to authenticate you and create or connect your Zaspark account. This does not give us your Google password, Gmail messages, contacts, or Drive files. We do not store a Google refresh token for this integration. Removing access in your Google account settings does not itself delete your Zaspark account.

3. Why we process information

We process information to provide the features you request, manage accounts, deliver content and notifications, process payments and recovery requests, and respond to support enquiries. Where applicable, this processing is necessary to perform our agreement with you or take steps you request before a purchase.

We also use information for legitimate interests in securing the service, preventing fraud and abuse, resolving disputes, diagnosing faults, and improving feeds and recommendations, subject to your rights and interests. We process information to meet legal obligations, including applicable financial, consumer protection, and regulatory requirements. Where consent is required, such as for certain device permissions or optional tracking, we rely on that consent; you may withdraw it without affecting earlier lawful processing.

Automated systems may analyze public posts and interactions to classify topics, recommend content, identify trends, and detect abuse. Service providers may assist with this processing. This does not mean that ordinary encrypted chat content is available to our recommendation systems. You can contact us to question a restriction or request review of a decision affecting you, including protections applicable to solely automated decisions.

We use activity records to support social features, suggest relevant accounts and content, measure content performance, and administer games, tasks, promotions, coins, bonus, gifts, subscriptions, refunds, and withdrawals. Transaction and reward records help verify eligibility, credit the correct wallet, reconcile payments, and investigate duplicate or manipulated activity. Our Virtual Items Policy explains these features.

Service communications can include sign-in and verification messages, transaction updates, security notices, and notifications you enable. You can manage optional notifications using the available settings and your browser or device controls. Essential account, transaction, and security communications may still be needed to provide the service or meet legal obligations.

4. Messages, encryption, and history recovery

First-contact text requests are not end-to-end encrypted. Where a conversation is awaiting acceptance, the initial text introduction can be sent before the recipient sets up a messaging device. Zaspark stores this introduction with server-side protection and can access its text to deliver the request and address safety or legal concerns. Accepting a request does not retroactively encrypt the introduction.

Ordinary messages in accepted chats use end-to-end encryption between enrolled devices. Message and attachment content is encrypted on the sending device. We still process delivery information, such as participant and device identifiers, timestamps, message size, delivery and read status, and encrypted message or attachment data. Encryption does not hide these records or prevent recipients from copying, recording, reporting, or sharing a conversation. Game-room chat and public posts are separate features and are not covered by this end-to-end encryption description.

History recovery is account-assisted and is not protected from Zaspark in the same way as device-to-device delivery. Your six-digit messaging passcode authorizes recovery after account sign-in, subject to online attempt limits. We retain a protected passcode verification record and a server-protected recovery key. Backed-up history is encrypted, but Zaspark’s recovery service can release the key and can access the backed-up history. Do not treat these backups as encryption that excludes Zaspark from access.

Backups may include message text, replies, reactions, and attachment information and keys needed to recover locally saved history. A new device can restore only history successfully backed up or manually transferred; unsaved history and expired or unavailable attachments may not be recoverable. Restoring history does not clone the old device’s messaging identity. Changing your account password does not replace a forgotten messaging passcode.

Your browser keeps protected messaging keys and local history. If you choose to remember a private browser, a stored device key can unlock messages after sign-in for up to 30 days. Anyone with access to that browser profile may be able to read the local history. Lock messages or sign out on shared devices, and manage enrolled devices through messaging settings. Revocation prevents future authorized device access but cannot erase copies already obtained.

5. Visibility and disclosures

Public profiles and posts may be visible to visitors, search engines, and people outside Zaspark. Restricted content follows the available audience controls, but recipients can copy or share it. Avoid putting confidential information in public content.

Your username and other visible profile details may accompany posts, replies, reactions, and other interactions according to the feature and audience settings. Content owners may receive performance counts, analytics summaries, and details of interactions made visible by the feature. Gift and wallet transaction records identify the relevant parties where needed; an anonymous gift presentation does not remove Zaspark’s underlying transaction records.

If you share a link or content through another service, the information you choose to share becomes available to that service and your chosen recipients. External sites, embedded services, and payment-provider pages have their own privacy notices and controls. Check their notices before providing information to them.

We disclose information needed by providers supporting hosting, databases, storage, video delivery, authentication, email and push notifications, analytics, recommendations, security, and payments. These include Google, Cloudflare, Flutterwave, and Bachs where used. Payment providers may process information under their own privacy notices and legal obligations. Withdrawal or crypto refund details are shared with the relevant provider; blockchain transactions and wallet addresses can be publicly visible.

We may disclose relevant information in response to valid legal requirements, to protect rights or address fraud and security incidents, or in a business transfer subject to applicable safeguards. If you submit content in a report or support request, we can process the copy you provide, including content from an otherwise encrypted chat.

6. Cookies, analytics, and device choices

Essential cookies and browser storage maintain sessions, protect requests, remember linked accounts and preferences, and support messaging and offline features. Clearing storage may remove local message history, keys, remembered sign-ins, and preferences. Blocking essential storage can prevent features from working.

Where enabled, Google Analytics and Google Tag Manager support usage measurement and configured tags and may process device, interaction, and cookie information. These optional tools load only after you accept optional cookies. We remember your choice for 180 days. Use Cookie preferences below to change your choice at any time; withdrawing consent reloads the page to stop optional tags. You can also manage browser cookies and permissions or use Google’s analytics opt-out tools. Blocking optional analytics does not replace clearing essential account or messaging storage.

Browser permissions control features such as location access and push notifications. Choosing a file for upload gives the feature access to the selected file; copying a link uses the clipboard action you request. You can change permissions in your browser or device settings. Location attached to a post can be visible to its audience, and location you authorize for an account feature may be sent to Zaspark for that purpose.

Cookie, permission, and notification choices may be specific to a browser or device, so review them on each device you use. Revoking a permission stops future access governed by that permission but does not automatically erase information already received. You can separately request deletion where applicable.

7. Retention and deletion

We keep personal information for the purposes described here, taking account of account activity, legal requirements, disputes, security, and the type of record. Financial and fraud-prevention records may need to remain after account closure. When information is no longer needed, we delete or de-identify it, subject to required retention and backup cycles.

Encrypted relay messages and finalized chat attachments normally expire from the delivery service after 90 days, and first-contact introductions are scheduled for removal after 90 days. Scheduled cleanup is not instantaneous and these periods do not apply to all account, transaction, or safety records. Local copies and recovery backups have separate lifetimes: retained recovery snapshots may contain older history, and replaced or incomplete snapshots are cleaned up separately. The 90-day delivery period is not a promise that all message copies are erased.

Deleting or hiding a message, revoking a device, or clearing one browser does not necessarily delete a recipient’s copy or all recovery snapshots. Contact us for account or backup deletion assistance. We may retain information required by law or for a documented dispute or security need, and explain applicable limitations when handling your request.

8. Security and international processing

We use access controls, encryption, account verification, session management, and other technical and organizational safeguards. Two-factor authentication is available for additional account protection. No system guarantees absolute security. We address security incidents and provide notifications where required by applicable law.

Zaspark and its providers may process information outside your country. Where applicable, international transfers must use a permitted legal basis and appropriate safeguards, such as contractual protections or an adequacy determination. You may contact us for information about the safeguards relevant to your data.

9. Your rights and age eligibility

Depending on applicable law, including the Nigeria Data Protection Act, you may request information about processing, access, correction, deletion, restriction, portability, or objection, and withdraw consent where we rely on it. Some rights have legal exceptions. We verify requests proportionately and respond within applicable legal time limits. You can edit available profile information, manage permissions and notifications, block or report users, and manage sessions and messaging devices.

You can use available content and audience controls to manage what you publish and who can interact with it, and contact us for account closure or privacy assistance. If information is required for sign-in, payment verification, or another requested feature, declining to provide it may prevent that feature from working. Withdrawing consent does not affect the lawfulness of processing already carried out or processing supported by another applicable legal basis.

When making a privacy request, describe the information or action you are asking about and provide enough account details for us to verify the request. We may need to protect another person’s information or retain records under a legal exception. If we cannot fulfil all or part of a request, we will explain the applicable reason and available review or complaint options. You may ask us to reconsider by replying through the support channel; this does not limit a right to complain to a competent authority.

Send privacy requests to [email protected]. You may also complain to the Nigeria Data Protection Commission or another competent data protection authority; contacting us first is not a condition of that right.

You must be at least 18 years old to register on Zaspark. The platform is not intended for registration or use by anyone under 18, and parent or guardian permission does not remove this requirement. Financial and reward features may have additional eligibility checks. If you believe someone under 18 has registered or provided personal information, contact us so we can investigate and take appropriate action, including restricting the account and deleting information where required, subject to lawful retention obligations.

10. Updates and related policies

We will identify changes by updating the date above and communicate material changes where required. If a new processing activity requires consent or additional information under applicable law, we will obtain that consent or provide the required notice; continued use alone does not replace legally required consent. Read our Terms of Service, Virtual Items Policy, and Refund Policy for service and purchase conditions.