Privacy Policy
This Privacy Policy explains how SpicyCall (“we”, “us”, or “our”) collects, uses, stores, and shares information when you use the SpicyCall mobile application (“App”) on Android via Google Play. By installing or using SpicyCall, you agree to this Policy.
1. Who we are
SpicyCall is a social entertainment app for browsing profiles, chatting, voice and video calls, live/party rooms, matching, gifts, and in-app coin (gem) purchases. The App is operated by SpicyCall.
Email: winkmeet.team@gmail.com
2. Age requirement
SpicyCall is intended only for users who are 18 years of age or older. We do not knowingly collect personal information from anyone under 18. If you believe a minor is using the App, contact us and we will take reasonable steps to delete related account data where applicable.
3. Android permissions we request
The App declares the following permissions in its Android package. Runtime permissions (Camera, Microphone, Phone) are requested only when needed for a feature. You can deny or revoke them in Android settings.
| Permission | Why SpicyCall needs it |
|---|---|
INTERNET |
Load profiles, media, configuration, authentication, and in-app store connectivity. |
ACCESS_NETWORK_STATE |
Detect network availability so features can work reliably when online or offline. |
CAMERA |
Show your local video preview and enable video call features. |
RECORD_AUDIO |
Capture microphone audio for voice and video call features. |
CALL_PHONE |
Support call-related phone actions used by the App’s call experience on Android. |
com.android.vending.BILLING |
Process Google Play in-app purchases of consumable gem/coin packs. |
The App does not currently declare notification, phone-state read, or modify-audio-settings permissions. Denying Camera, Microphone, or Phone permissions may limit or disable call features; browsing and other non-call features may still work.
4. Information we collect
4.1 Account and authentication data
- Guest / Fast Login: an anonymous Firebase Auth user ID.
- Google Sign-In: Google account identifiers and profile details provided by Google (such as display name, email address, and profile photo URL), linked through Firebase Authentication.
- An app-facing user ID derived from your Firebase UID for display in the App.
4.2 Profile and preference data
- Display name, age, country/region preference, language preference, and short intro text shown in your profile area.
- In-app preference toggles such as sound and vibration settings stored on the device.
- Blocklist entries you create in Settings.
4.3 Chat and interaction data (primarily on-device)
- Chat messages and related chat metadata stored locally on your device.
- Local wallet balance (gems/coins), free-starter status, premium flags, and purchase receipt records needed to avoid double-crediting Play purchases.
- Like / interaction counters and similar in-app activity stored on the device.
In the current build, chat conversations are designed to remain on the device. Do not share passwords, bank details, OTP codes, or other sensitive personal information in chats or calls.
4.4 Camera and microphone data
- When you use voice or video call features, the App may access your camera and/or microphone for the call experience (including local camera preview).
- Access is used while those features are active. We do not use camera or microphone access for unrelated background recording.
4.5 Purchase and billing data
- In-app purchases of consumable coin/gem packs are processed by Google Play Billing.
- We receive purchase product IDs, purchase/transaction identifiers, and delivery status needed to credit gems to your local wallet.
- Payment card details are handled by Google Play; we do not collect or store your full payment card number.
4.6 Device, network, and technical data
- Internet and network-state access to load profiles, media, configuration, and billing.
- App version and basic technical diagnostics needed to operate features.
4.7 Content and media loaded from our services / partners
To show discovery feeds, profile photos, and call/media clips, the App may request content from our configured API and media hosts. Those requests may include technical parameters needed to fetch the wall, profiles, or media (for example region/language/page parameters).
5. How we use information
- Create and manage your Guest or Google-linked account.
- Provide chat, matching, live/party room browsing, and voice/video call features.
- Display profile walls and media content.
- Operate the gem economy (message and call costs, rewards, sign-in bonuses).
- Process and deliver Google Play in-app purchases.
- Apply Remote Config values (for example free-call limits and premium prompts).
- Support account switching, logout, and account deletion.
- Maintain safety features such as blocklists and in-app safety notices.
- Improve reliability, prevent abuse, and comply with legal obligations.
6. Third-party services
We use trusted service providers to run the App:
- Google Firebase Authentication – Guest and Google sign-in.
- Google Sign-In – optional Google account login/linking.
- Firebase Remote Config – feature configuration such as free-call timing and premium prompts.
- Google Play Billing – in-app consumable purchases.
- Content / media hosts used by the App to load discovery and call media (configured API and CDN endpoints).
These providers process data under their own terms and privacy policies. Google’s policies apply to Sign-In, Firebase, and Play Billing.
7. How we share information
We do not sell your personal information. We may share information only:
- With service providers listed above, as needed to operate the App.
- With Google when you choose Google Sign-In or make a Play purchase.
- If required by law, regulation, legal process, or to protect users, the App, or our rights.
- In connection with a business transfer (merger, acquisition, or asset sale), subject to continued protection of your information.
8. Data storage and retention
- On your device: chats, wallet balance, local receipts, and many preferences are stored locally.
- Authentication: Firebase Auth retains account credentials/identifiers while your account exists.
- Purchases: Google retains Play Billing records according to Google’s policies; the App keeps local delivery receipts to prevent duplicate gem grants.
If you uninstall the App, local on-device data is typically removed with the app data. Server-side authentication records may remain until you delete your account or request deletion.
9. Your choices and rights
- Permissions: You can allow or deny Camera, Microphone, and Phone permissions in Android settings.
- Google linking: You may use Guest login or link a Google account in Settings.
- Logout / Switch accounts: Available in Settings.
- Delete account: Settings → Delete account removes your Firebase account on the device flow. Local app data is cleared on logout/delete as implemented in the App.
- Clean cache: Available in Settings for clearing cached files on the device.
Depending on your region, you may have rights to access, correct, or delete personal data, or to object to certain processing. Email winkmeet.team@gmail.com to make a request.
10. Security
We use reasonable technical and organizational measures appropriate to the App, including authenticated sessions via Firebase and local storage protections provided by the operating system. No method of transmission or storage is 100% secure. Please protect your device and never share sensitive personal or payment details inside chats or calls.
11. International processing
Your information may be processed on servers located outside your country (including by Google Firebase / Google Play infrastructure and content hosts used by the App). Where required, we rely on appropriate safeguards offered by those providers.
12. Children’s privacy
The App is not directed to children under 18. We do not knowingly collect personal information from children. If we learn that we have collected such information, we will delete it where feasible.
13. Changes to this Policy
We may update this Privacy Policy from time to time. The “Effective date” at the top will be revised when changes are posted. Continued use of the App after an update means you accept the revised Policy.