1. Introduction
Spamlix (“we”, “our”, “us”) provides a cross-platform spam call blocking and Caller ID application (the “App”). This Privacy Policy explains what information we collect, how we use it, and the choices you have. By using Spamlix, you agree to this Policy.
We design Spamlix so that raw contacts and call history stay on your device for screening. Cloud features (accounts, reports, sync, optional AI insights) do send limited data to our servers as described below.
2. Information We Collect
2.1 Account & profile information
You may sign in with:
- Phone number + OTP (Firebase Authentication / SMS)
- Google Sign-In (email and basic profile)
- Sign in with Apple (email and name, subject to Apple’s privacy options)
If you edit your profile, we may store details you provide such as display name, first/last name, phone, email, job title, company, website, address fields, gender, preferred app language, and an optional profile photo uploaded to Firebase Storage.
2.2 Device permissions (on-device processing)
Depending on your platform, Spamlix may request:
- Phone / Call Log (Android): To screen incoming calls and optionally scan recent call history for known threats. Call logs are processed on-device for these features and are not uploaded as a full call history dump.
- Contacts: To recognize saved contacts (so they are not treated as unknown spam) and to show contact names on Caller ID where applicable. Your contact book is not uploaded to build a global contacts database.
- Display over other apps / Overlay (Android): To show the Spamlix Caller ID banner during calls.
- Battery optimization exemption & OEM AutoStart (Android, optional): To reduce the chance the OS kills protection after reboot or in the background.
- Notification access / Deep Network Scanner (Android, optional): To read dialer or carrier spam-related notifications and improve local threat detection. Content is processed for spam keywords; it is not used to scrape personal message threads.
- iOS Call Directory / Call Blocking & Identification: To block or identify numbers through Apple’s Call Directory extension using local/community spam lists.
Local-first rule: Screening against your personal rules and local spam database happens on your device. We do not sell contact lists or call histories.
2.3 Data you submit to the community / cloud
When you use cloud-connected features, we may collect:
- Spam reports: reported phone number, spam category, caller type (e.g. Business/Personal), optional suggested name, optional comment, and your account ID so we can moderate abuse and attribute community contributions.
- Block rules you create: phone number/pattern, rule type, country context, and timestamps associated with your account.
- Name suggestions: crowdsourced display names for numbers that are not in your contacts.
- Number search / lookup activity: numbers you search in Global Lookup and related spam/community results.
- Leaderboard / impact stats: contribution metrics (such as rules created or score) and your display name or anonymized identifier.
- Aggregated spam intelligence: community spam counts and country-level threat lists synced to devices for offline protection.
2.4 Local device storage
The App stores preferences and protection data locally (for example SharedPreferences / local databases), including active rules, screening toggles, recent blocks, country selection, app language preference, recent searches, personal name overrides, and offline spam databases used by the native screening engine.
For authentication abuse prevention, the App may also store on-device OTP rate-limit state such as recent OTP request counts for a phone number, cool-down timestamps, unusual-activity warning counts, and a temporary device OTP block expiry (for example up to about one month after repeated unusual-activity warnings). This data stays on the device for security controls and is not sold or used for advertising.
2.5 Diagnostics & optional AI insights
- Firebase Crashlytics: crash and stability diagnostics to improve App reliability.
- Firebase App Check: helps protect our backend from abuse.
- Firebase Analytics (SDK present): may collect standard app usage analytics events as configured by Firebase.
- AI pattern insights (optional feature): summarized metadata about recent blocked events (such as number patterns, times, and categories) may be sent to our secure Cloud Functions and processed with Google Gemini to generate protection insights. Do not expect this channel to include your full contact book.
2.6 Advertising
Spamlix integrates Google Mobile Ads (AdMob). Ads may be enabled or disabled by configuration. When ads are shown, Google may use advertising identifiers and contextual signals under Google’s policies. We do not sell your personal data to advertisers.
3. How We Use Information
- Provide call screening, blocking, Caller ID, and spam lookup
- Sync community threat intelligence and personal rules across your account
- Apply your preferred app language and profile settings
- Moderate spam reports and prevent abusive reporting
- Limit OTP abuse with cool-downs and temporary device OTP restrictions
- Show leaderboards / community impact (where enabled)
- Improve reliability (crashes, abuse prevention) and, if enabled, generate AI insights
- Communicate about account or security issues when necessary
4. How We Share Information
We share data only as needed to operate Spamlix:
- Google Firebase (Authentication, Firestore, Storage, Cloud Functions, Crashlytics, App Check, Analytics)
- Google Sign-In / Apple Sign-In for authentication
- Google Gemini (via our Cloud Functions) for optional AI insights
- Google AdMob when ads are enabled
- Community users may see aggregated spam signals, suggested names, and limited leaderboard identity (display name or anonymized ID)—not your contact book
We do not sell your personal information. We may disclose information if required by law or to protect users from fraud or abuse. On-device OTP rate-limit and unusual-activity controls are not shared with advertisers.
5. Data Retention & Deletion
- On-device data: clearing App data or uninstalling removes local preferences (including language preference), OTP abuse-control state, local spam DBs, and cached state on that device.
- Account deletion: you can delete your account from the App (Settings / account controls) or by emailing hello@spamlix.com. Deleting your Auth account removes sign-in access. Related cloud records (profile, rules, reports, suggestions) may be deleted or anonymized according to our retention and moderation needs; community spam aggregates derived from reports may remain in de-identified form for network protection.
- Requests: for access, correction, or deletion under applicable law (including India’s DPDP Act where relevant), contact us using the details below.
6. Children’s Privacy
Spamlix is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided data, contact us and we will take appropriate steps.
7. Security
We use industry-standard cloud security controls (including encrypted transport to Firebase and App Check). No method of transmission or storage is 100% secure; please protect your device and account credentials.
8. International Processing
We operate from India and use global cloud providers (including Google Firebase). Your information may be processed in regions where those providers maintain infrastructure.
9. Your Choices
- Deny or revoke permissions in system settings (some features will stop working)
- Change app language in Profile / Settings
- Disable optional features such as Custom Caller ID, Deep Network Scanner, battery/autostart helpers, community sync, or AI insights where offered in-App
- Avoid submitting reports, comments, or profile details you do not want stored in the cloud
- Sign out or delete your account
10. Changes to This Policy
We may update this Privacy Policy as the App evolves. The “Last Updated” date above will change when we do. Continued use of Spamlix after updates means you accept the revised Policy.
11. Contact Us
Questions about privacy or data requests:
Email: hello@spamlix.com
Address: Dehradun 248002, Uttarakhand, India
Related pages: Terms of Service · Contact