Smart Call Blocker
Get it onGoogle Play
EN

← Home

Smart Call Blocker

Privacy Policy

Last updated: October 2, 2026

How the app handles data on the device, in your account and on the opt-in network.

This Privacy Policy describes how the Smart Call Blocker app (“App”), developed by Sonsai (“Developer”), processes personal data in line with Brazil’s LGPD (Law No. 13.709/2018) and Google Play requirements.

Controller contact: support@sonsai.com.br

1. What data we process

1.1 On the device (local processing)

  • Phone numbers involved in call screening and allow/block lists
  • Call decision history (allowed, blocked, validated)
  • Device contacts, on-device only, when READ_CONTACTS is granted
  • App settings (theme, language, protection and schedule flags)

Call screening does not send numbers to decision servers. Filtering runs locally on Android.

1.2 Community spam network (optional, opt-in)

When you enable the community network and confirm “Report as spam”:

  • The App sends the reported number (normalized) only to a Supabase Edge Function, which computes a cryptographic identifier (HMAC) and does not store the plain number in permanent records.
  • We store your report linked to your account and device (device_id_hash), without sharing your identity with other users.
  • When the same identifier is reported by 3 or more distinct devices, the number enters an aggregated community spam list.
  • Other opt-in users may receive an informational alert (“spam detected”) after a locally blocked call. Blocking decisions remain on-device.
  • You can disable the network anytime in Settings. Deleting your account removes your reports.

Number holders who believe they were mislabeled may request review via the controller email (section 9).

1.3 Account and cloud (when you sign in with Google)

  • Name, email, profile photo and account identifier (Supabase Auth / Google Sign-In)
  • Plan (free, prata, ouro or master) and subscription metadata validated by Google Play
  • One active device per account (installation identifier, not IMEI)
  • Encrypted cloud backups (Supabase Storage) when Ouro/Master is active — the encryption password stays on the device

1.4 Ads and purchases

  • On the free plan, Google AdMob may process advertising identifiers, device data, ad interactions and IP address under Google’s policies
  • Applicable consent is requested via the User Messaging Platform (UMP) before the first ad request
  • Subscriptions and purchases are processed by Google Play Billing; the App does not store full card details

1.5 Voluntary support

  • Donations via PIX (Brazil) or Buy Me a Coffee (other locales) are optional, independent of Play plans and do not change App entitlements
  • The App does not receive the donation amount; payment happens on external channels (bank / Buy Me a Coffee)

1.6 Contacting support

Only when you send a message in Settings → Email support (Google sign-in required):

  • Name, email, phone (optional), subject, message and any images you attach
  • To help with the request, the account identifier, plan and App language are also included
  • This data is used only to answer your request. The message is delivered by email to the Controller via Mailjet (Supabase Edge Function)

2. Purposes and legal bases

  • Providing call filtering (contract performance / legitimate interest)
  • Community spam network, opt-in and explicit reports only (reporter consent; legitimate interest for reported numbers per internal LIA)
  • Account, backup and sync at your request (contract and consent when applicable)
  • Ads on the free plan (UMP consent / legitimate interest by jurisdiction)
  • Answering support messages you send (your request / legitimate interest)
  • Legal compliance and account security (one active device)

3. Sharing

We share data with:

  • Google (Sign-In, Play Billing, AdMob/UMP)
  • Supabase (Auth, database, backup Storage and Edge Functions: Play purchase validation, account deletion and the opt-in spam network)
  • Firebase (Analytics, Crashlytics and Cloud Messaging), without using Firebase Auth for login
  • Mailjet (email delivery of support messages and their attachments)

We do not sell phone numbers or call history. Contacts and numbers are not used for ad personalization.

4. Retention and deletion

  • Local data can be erased in Settings → Delete all local data
  • The cloud account can be deleted in Settings → Delete account (requires recent sign-in). This removes profile, backups, Storage objects and the device link
  • Deleting the account does not cancel Google Play subscriptions. The Ouro plan can be canceled in Plans → Cancel Ouro subscription, which opens Play Store subscriptions
  • Ouro users must confirm they have already canceled the subscription before deleting the account
  • Support messages stay in the Controller's mailbox for as long as needed to handle the request. You may request their deletion via the controller email
  • We may retain minimal records required by law or tax rules

5. Security

  • Server communication over HTTPS
  • Cloud backups may be encrypted with a password you choose (AES-GCM)
  • Backup password is never sent to the server
  • Access control via Supabase RLS policies

6. Your rights (LGPD)

You may request confirmation of processing, access, correction, anonymization, portability (when applicable), deletion and information about sharing, via the controller email. You may also use in-app options (delete local data and delete account).

7. Children

The App is not directed to children under 13. We do not knowingly collect children’s data.

8. Changes

We may update this policy. The date at the top will be revised. Continued use after publication may constitute awareness of the new text where allowed by law.

9. Contact

Privacy questions: support@sonsai.com.br

TermsDelete account