Block-Spam Privacy Policy

    Last updated: 28 July 2026

    Who we are (Data Controller)

    Pamiesolutions β€” Albert PΓ mies Pau Vila 2B, 43850 Cambrils, Spain Contact for privacy matters: info@block-spam.com This policy applies to the Block-Spam mobile application on both Android and iOS (the "App") and to our backend services. Where a practice applies to only one platform, it is expressly marked (Android) or (iOS); everything else applies to both. This policy describes the latest version of the App available on each platform at the date above; earlier versions may behave differently, so we recommend keeping the App up to date. It replaces the previous version dated 23 February 2023.

    What stays on your phone β€” and what doesn't

    Your contact list never leaves your device. Block-Spam reads it locally (with your permission) to identify callers and enable the "block everyone not in my contacts" mode. We do not upload, store, or share your contact list. We never collect your own phone number β€” the App does not ask for it and does not read it: the only phone numbers we process are the numbers that call you and the numbers you choose to report. On Android, to power community spam detection, the App does send to our servers the phone numbers that call you, together with basic call-handling signals (whether the call was answered, not answered or blocked, its duration, and your spam feedback), your country, and a pseudonymous device identifier. We never access or transmit the content of your calls or messages β€” no audio, ever. We cannot tell who is receiving those calls. Block-Spam has no user accounts and holds no name, email address or phone number of yours. The call signals are stored organized by the calling number β€” not by user β€” and are only ever used in aggregate (for example, "this number called many users who never answer") to compute spam indicators. The pseudonymous device identifier attached to each signal exists solely to prevent abuse of the reporting system and to de-duplicate signals; it cannot be linked back to your identity with the data we hold.

    What data we process, why, and on what legal basis

    β€’ Core call blocking (both platforms): contacts (Android), call log (Android), incoming call numbers and, on iOS, the blocking and identification lists used by the system β€” processed only on your device. Legal basis: contract performance (Art. 6(1)(b) GDPR). β€’ Community spam database β€” downloading (both): your country (to send you the relevant spam list) and a pseudonymous device identifier. Legal basis: contract performance. β€’ Community spam database β€” your reports (both): the phone number you report, its category, country, your optional comment, and a pseudonymous identifier of the reporting device. Legal basis: legitimate interest (Art. 6(1)(f)) in protecting users against spam and fraud calls (Recital 47 GDPR). β€’ Spam detection β€” community call signals (Android only): incoming call numbers, country, call-handling signals (answered / not answered / blocked, duration, spam feedback), timestamp, pseudonymous device identifier. Legal basis: legitimate interest in detecting spam campaigns from aggregated community call patterns. β€’ Number lookup (both): the number you choose to look up, sent to our servers to return community information about it. Legal basis: contract performance. β€’ Advertising in the free version (both): advertising ID (subject to App Tracking Transparency on iOS), device data, coarse location derived from IP; shared with Google AdMob and, where you consent, its certified advertising partners. Legal basis: consent for personalised ads; legitimate interest for limited, non-personalised ads. β€’ App stability and analytics (both): crash data, diagnostic logs, device model, OS version, usage events (Firebase Crashlytics / Google Analytics for Firebase). Legal basis: legitimate interest in keeping the App working. β€’ SMS spam filtering (iOS only): messages from unknown senders are checked entirely on your device by the system's Message Filter; nothing about your messages ever leaves your phone. Legal basis: contract performance. β€’ Push notifications (both): Firebase Cloud Messaging token. Legal basis: contract performance / consent. β€’ Premium subscriptions (both): handled entirely by Google Play / Apple App Store billing; we never see your payment details. Legal basis: contract performance. Platform note: on iOS the operating system does not allow apps to observe incoming calls the way Android does β€” identification and blocking happen through Apple's CallKit system using lists stored on your device, and no community call signals are collected from iOS devices. The pseudonymous device identifier is the Android ID on Android and an app/vendor-scoped identifier on iOS. We do not collect precise location, and we do not sell personal data.

    Advertising and your consent choices

    The free version of Block-Spam shows ads served by Google AdMob. In the European Economic Area, the United Kingdom and Switzerland we ask for your consent through Google's certified consent form (IAB TCF) before showing personalised ads: β€’ If you consent, Google and the certified partners listed in the form may use your advertising ID to personalise ads. β€’ If you decline, you will still see ads, but non-personalised or limited ads. β€’ You can change your choice at any time in the App: Settings β†’ Ad privacy options. β€’ On iOS, personalised ads additionally require the system App Tracking Transparency permission, which you can change in iOS Settings β†’ Privacy β†’ Tracking. How Google uses data: https://policies.google.com/technologies/partner-sites Premium subscribers see no ads.

    The community ("cooperative") spam database

    Block-Spam's protection is powered by its community: when a user reports a phone number as spam, the number (with category, country and an optional comment) is stored in our database and distributed to other users so their phones can warn about or block it. When you look up a number, the number you query is sent to our servers to return the community information available about it. β€’ Reported numbers may belong to companies or to individuals. Where a number identifies an individual, it is personal data and we process it under our and our users' legitimate interest in preventing spam, scam and fraud calls. β€’ The reliability of a listing is corroborated by reports from multiple independent users before other users are warned. β€’ Please do not include personal information about yourself or others in comments; we may remove comments that do, and you can request the removal of any comment at info@block-spam.com. β€’ We store a pseudonymous identifier of the reporting device (to fight abuse of the reporting system), never the reporter's name or phone number. Community call signals (Android). In addition to manual reports, the App sends to our servers the numbers that call our users together with basic call-handling signals (answered, not answered or blocked; call duration; spam feedback given by the user; timestamp; country) and a pseudonymous device identifier. We aggregate these signals across the community β€” for example, a number that calls many users who never answer or immediately hang up β€” to detect spam numbers and to improve our spam-detection models. These signals never include the content of any communication, are linked to a pseudonymous device identifier rather than to your name or phone number, and numbers not identified as spam are not published anywhere β€” they are only used internally for detection. You may object to this processing at any time (Art. 21 GDPR) by writing to info@block-spam.com. Disputing a listing ("Not spam"). The App includes a "This number is not spam" form: you can open it from a listed number (for example in your call history) or enter a number manually, explain why it is not spam, and the form is sent to us at info@block-spam.com so we can correct the listing. On your own device, marking a number as not spam also stops it from being blocked immediately. If you submit the form or contact us by email, we process the contact details you provide only to handle your request. If your number is listed and you believe it should not be: use the form above or email info@block-spam.com from a verifiable contact, indicating the number. We will review and, where the report is not justified or you exercise your rights under Articles 17/21 GDPR, remove it. Numbers that continue to be reported by the community may be re-listed after review.

    Support and bug reports

    If you contact us through the in-app "Report a bug" form, we receive your message together with technical details of your device (model, operating system and app version) and your current app settings and permissions, which help us diagnose the problem. Providing your email address is optional: if you choose to enter it, we ask for your consent first and use it only to reply to your report β€” never for marketing, and we never share it with anyone. You can ask us to delete it at any time; otherwise we keep it only for as long as needed to resolve your report.

    Who we share data with

    β€’ Google AdMob and its certified ad partners (ads, only as described above). β€’ Google Firebase (analytics, crash reporting, push notifications, and the call-signal database used for spam detection) β€” Google Ireland Ltd. / Google LLC. β€’ Bluehost (Newfold Digital Inc.) β€” hosting of our community spam database and web services, with servers located in the United States. β€’ Authorities, where the law requires it. No other third parties receive personal data, and we never sell it. Where our providers process data outside the European Economic Area (Google and Bluehost operate servers in the United States), the transfer is protected by the safeguards they provide as processors β€” the EU Standard Contractual Clauses and, for Google, its certification under the EU–US Data Privacy Framework.

    Retention and security

    β€’ Spam reports and community call signals: kept for as long as they remain necessary for detecting and blocking spam and fraud calls. Delisting requests are processed as described above. β€’ Device identifiers and push tokens: while the App is installed (they rotate or expire when you uninstall or reset your advertising ID). β€’ Crash and analytics data: per Firebase's standard retention (up to 14 months). β€’ Ad data: per Google's advertising policies. All communication between the App and our servers is encrypted in transit (HTTPS/TLS). Access to our databases is restricted, and community data is keyed to pseudonymous identifiers as described above.

    Your rights

    You can exercise, free of charge: access, rectification, erasure, restriction, portability, objection, and withdrawal of consent (withdrawal does not affect prior processing). Write to info@block-spam.com. You may also lodge a complaint with the Spanish supervisory authority (AEPD, www.aepd.es) or your local authority. If you reside in a US state with a consumer privacy law (e.g., California), you may exercise equivalent rights β€” access, deletion, correction and opt-out β€” through the same contact. We do not sell personal information.

    Children

    Block-Spam is not directed at children under 16 and we do not knowingly process their data.

    Changes to this policy

    We will post any changes on this page and update the date above. Material changes will be announced in the App.