Конфиденциальность

Privacy notice

Updated September 21, 2026. This notice describes data processing in the current version of ZapZip at zapzip.cc, app.zapzip.cc and the Telegram Mini App.

Sign-in and account information

For Google sign-in, ZapZip validates an identity token and stores your unique Google identifier, first and last name, picture URL and locale when provided. Your Google email address is not stored in your ZapZip profile. ZapZip does not request access to Gmail, Google Drive, Google contacts or other account documents.

For Telegram sign-in, ZapZip stores the user identifier, first and last name, username, picture URL and language when supplied by Telegram. Opening the Mini App does not itself give ZapZip access to your private chats.

How account data is used

Sign-in information creates and identifies your account. The server database stores your profile, saved search settings, balance, credit and debit history, opened contacts, referral relationships and sign-in timestamps. Search criteria, queries, results and technical search status may be retained when a search is performed.

This information supports account operation, access to previously opened contacts, balance accounting and error diagnosis. Authorized service administrators can access account information and operational history through administration tools.

Cookies and browser storage

Website sign-in uses a secure session cookie lasting up to 30 days. The server stores a hash of its identifier, its account association and expiry information. Short-lived cookies also protect the sign-in process. Session expiry does not delete your account.

Saved cards are kept on your device separately for each account; language and theme are stored locally in the browser. Unlocked contact details are not added to the locally saved card list. You can remove saved cards or clear site data through your browser. Signing out of the website invalidates the current server session and removes the current account’s local favorites from that device, but does not delete its server account or history.

Public information and contacts

The catalog uses information from public social profiles. Signals are intended to represent explicit investment and business intentions in public posts and discussions; signal collection is being prepared for launch. Private conversations are not a catalog source.

The app hides names, contact addresses, handles and links before opening a record. Opening reveals its available public contact. Public availability does not verify identity, establish permission for any kind of outreach or confirm current investment interest. Short descriptions can retain indirectly identifying details; absolute anonymity is not promised.

Technical processing and retention

Application hosting and server-storage infrastructure process the data. Google participates in Google sign-in, and Telegram in Telegram sign-in. Public information may be sent to a text-processing provider to prepare descriptions. Google sign-in information is not used as source material for investor descriptions.

The current version does not establish a fixed automatic deletion period for profiles, history or public records. Self-service server-account deletion is not yet implemented. Clearing browser data or revoking a Google connection does not automatically delete data already stored on the server.

You can manage your Google connection in your Google account settings. A subsequent ZapZip sign-in requires authorization again.

Questions and data requests

For privacy questions, data correction or deletion requests, contact @p_fintech on Telegram. Requests are reviewed manually; changes to account data may require confirmation that the account belongs to you. Do not send passwords, sign-in codes or authentication tokens.