Android app · com.vivek.chatzip

Privacy Policy

Last updated: 17 August 2026 · Contact: chatzip.official@gmail.com

This Privacy Policy explains what ChatZip collects, why we collect it, where it is stored, who can see it, and how you can delete it. It matches what the app actually does. Please read it before you sign in.

1. Who we are

ChatZip is a messaging app for Android. You sign in with Google, find people with a ChatZip ID (not your phone contacts), then chat, share photos and videos, make audio or video calls, and share location only when you choose.

Questions: email chatzip.official@gmail.com. In the app: Profile → Help & Support (email only).

2. What we do not do

We do not:

• Read your phone contacts, SMS, call log, or files outside what you pick
• Sell your data to advertisers
• Use your location, messages, or photos for ads or marketing
• Track you in the background when you are not sharing location
• Record the audio or video of calls on our servers
• Require a phone number to create an account
• Collect data from children under 13

3. How you create an account (Google Sign-In)

Use case: so you can log in and your friends can recognise you.

When you tap Continue with Google we receive from Google your account name, email, Google profile photo URL (if any), and a sign-in ID token used only to create your Firebase Auth session.

We then create your ChatZip profile in Google Firebase (Cloud Firestore collection users), including Firebase user ID, name, email, photo URL, a ChatZip ID/token so others can find you without uploading contacts, optional fields you type later (bio, status/mood, phone, gender, birthday), online/typing state for the chat list, blocked user IDs, and an FCM device token for notifications.

Why: authentication, showing your name and photo, finding friends by ChatZip ID, delivering messages and calls. We do not get your Gmail inbox, Drive, or Google contacts.

4. Where your data is stored

ChatZip uses Google Firebase / Google Cloud. Data is sent over HTTPS. Google encrypts Firebase data in transit and at rest as part of their service. ChatZip does not sell this data. Content is stored so the app can deliver it to the people you chat with.

Cloud Firestore (database)

• users — profile, ChatZip ID, FCM token, blocked users
• messages — chat text, media links, location pins, location requests, live-location cards, call event text
• conversations — chat members, last preview, archive, profile-visit notes
• calls — ringing / accept / end signalling (not the media)
• call_history — who called, audio or video, time, duration (not recordings)
• user_reports — reports you send
• account_deletion_requests — your delete-account request
• admin_location_requests — Admin location request; coordinates are saved only if you approve

Firebase Storage (files)

• Profile photos: ChatApp/{your-uid}/profile/
• Chat photos: chat_images/{conversationId}/
• Chat videos: chat_videos/{conversationId}/
• Video thumbnails: chat_thumbnails/{conversationId}/

Files are uploaded only when you send a photo/video or change your profile picture. We use the Android photo/video picker or camera with your permission. We do not scan your gallery.

Firebase Realtime Database

• status/{uid} — online/offline while the app is connected
• live_sessions/{sessionId} — live location and trail only while you are sharing

On your device

Recent chats may be cached so a conversation opens quickly. Unsent messages may be queued until you are online. Appearance (Light/Dark/System) stays on the device. Chat cache is excluded from Android cloud backup.

Who can access cloud data

• You, on your signed-in device
• The other person in that 1:1 chat — only what you send or approve
• Google, as the Firebase infrastructure provider
• ChatZip Admin, only for safety and support: reports, deletion requests, and location only if you approve an Admin request

We do not publish chats publicly. We do not give advertisers access to your messages or media.

5. Chats (text)

Use case: send and receive messages. Each message stores sender, receiver, conversation ID, text, time, read/delivery status, and optional reply fields, so both people can see the thread after sign-in and so notifications can summarise it.

Delete options:

• Delete for me — hides that message from your account. The other person still sees it unless they delete it too.
• Delete for everyone — clears the text and media links on that message for both sides.
• Delete all chat — hides the whole conversation for you only. The other person’s copy stays. Local cache for that chat is cleared on your device.

Archive only hides a chat on your home list. It does not delete messages.

6. Photos and videos

Use case: share a picture or video, or set a profile photo. Chat uses the Android Photo Picker (or camera if you capture). Profile uses Photo Picker. CAMERA is asked only for capture or video calls. We do not request all-files / full media-library access.

We store the file in Firebase Storage (paths above) and a download URL on the Firestore message so the receiver can open it. Videos also get a small thumbnail. Recipients may save a copy on their device.

If you delete a message for everyone, the message record is cleared. Recipients may still have a copy they already saved.

7. Audio and video calls (WebRTC)

Use case: talk live with someone who has your ChatZip ID.

We store a short-lived signalling document in calls (offer/answer, ICE candidates, ringing/connected/ended), a call-history row, and a small text line in the chat. We do not record or upload call audio or video. Media is peer-to-peer via WebRTC. Firestore is used only to connect the two devices.

8. Notifications

We store an FCM token on your user profile so Cloud Functions can send a high-priority data alert for a new message or incoming call. POST_NOTIFICATIONS can be denied; chat still works while the app is open. Incoming calls may use vibrate, wake lock, full-screen intent, and a short foreground service so you can accept or decline on a locked phone. Notifications are not used for ads.

9. Location

ChatZip never reads your location until you choose a location action and grant permission. We request fine and coarse location because a map pin needs coordinates. We do not use background location. We do not use location for ads.

Before Android asks, ChatZip shows a disclosure: location is only for sharing a current pin or live location in a chat.

In every case except “you send your own pin”, the other side gets coordinates only after you approve.

9.1 You share your current location

After permission, we read GPS/network position once, attach an address label, and send one chat message with latitude, longitude, and address. The receiver opens it in a maps app. We do not keep streaming GPS after that message.

9.2 Someone requests your location

Another user can send a location request (status starts as pending). No coordinates are sent then. You see Approve or Decline.

• Approve — we read your current position once and send a location message.
• Decline — we send no location.

Until you approve, the requester cannot see where you are.

9.3 Live location

You may share live location for 15 minutes, 1 hour, or 8 hours, or accept a live-location request (same approve/decline rule). While sharing, a visible notification stays on screen, a foreground location service updates the session, and coordinates/trail go to Realtime Database live_sessions so the other person can see the live map. You can stop anytime. Sharing also stops when the timer ends. We use foreground location service only for this visible share — not silent background tracking.

9.4 ChatZip Admin location request

Rare safety/support case. You get a screen: “ChatZip Admin wants your current location.” Share saves lat/lng/address on that request. Decline stores no location for Admin.

10. Finding people, profile visits, block and report

Search uses ChatZip ID or name — not your address book. Opening a profile may store a “visited your profile” note for Profile Visits. Block saves the blocked user ID on your profile. Report saves reporter ID/email, reported user, optional conversation ID, reason, and time so Admin can review abuse. The official ChatZip account cannot be reported.

11. Account deletion

To delete your account, open ChatZip → Profile → tap Delete account and send the request. You may add an optional reason. ChatZip Admin reviews the request and deletes the account within 7 days.

You can also email chatzip.official@gmail.com from the same address used on ChatZip. We complete the same deletion within 7 days. Full steps: delete-account.html.

When deletion is completed we delete your Firebase Auth login, delete files under ChatApp/{your-uid}/ (profile photos), clear personal fields (email, photo, FCM token), and mark the account deleted.

You may delete chats for yourself at any time before that. Messages already delivered to other users can stay on their devices. If a deleted account tries to sign in again, ChatZip blocks it.

12. Android permissions — why each one exists

Denying a permission disables that feature. The rest of the app still works.

Not used: contacts, SMS, call log, background location, body sensors, nearby devices.

13. Third-party services

Google processes data to run ChatZip: Google Sign-In, Firebase Authentication, Cloud Firestore, Storage, Realtime Database, Cloud Messaging, Cloud Functions, Play Services location, and Maps (live map in-app; current pins can open a maps app you choose). We do not sell personal information. ChatZip does not include AdMob or advertising SDKs.

14. Security

Login uses Google and Firebase Auth. Traffic uses HTTPS/TLS. Do not share your ChatZip ID with people you do not trust. You can block, report, and delete chats. No transmission is 100% secure.

15. Children

ChatZip is not directed at children under 13. You must be 13 or older. If a child under 13 created an account, email us and we will delete it after review.

16. Data retention

Profile and messages stay until you delete them for yourself, delete for everyone, or Admin completes account deletion. Call signalling lasts only as long as needed to connect. Live location lasts only while the session is active. Reports and deletion requests are kept as needed for safety.

17. Your choices

• Deny camera, mic, location, or notifications in Android Settings
• Stop live location from the notification or map
• Decline any location request (user or Admin)
• Delete messages or the whole chat for you
• Block or report a user
• Request account deletion from Profile → Delete account (completed within 7 days)
• Email chatzip.official@gmail.com to ask what we hold or to request deletion

18. International processing

Firebase may process data in Google Cloud regions. By using ChatZip you understand data may be processed outside your country under Google’s infrastructure.

19. Changes

We may update this policy when the app changes. The date at the top will change. Material updates also appear in the in-app Privacy Policy screen.

20. Contact

ChatZip support — email only: chatzip.official@gmail.com
Subject example: ChatZip privacy