Español · English · Português

Legal

Privacy Policy

Effective date and last update: October 11, 2026

In short: we keep the minimum needed for your account to work and to warn you about risky calls. We never read your contact list or the content of your calls, and we never sell your information or share it for advertising. The full detail is below.

1. Scope

This policy covers the RingShield app — published in other countries as Bloquea.do and Bloqueou, and the same app under any of those names — and this website. It describes what information we collect when you create an account, use the app or visit this site, what we use it for, and what rights you have over it.

This site uses no cookies or analytics tools: it is a static page and collects nothing on its own. Everything described below happens inside the app.

2. What information we collect

When you create your account

  • With Google: when you sign in with Google, we receive your Google name, email and profile photo — Firebase (Google's authentication service) uses them to confirm your account is real. We don't store that name, email or photo in our database. If you join a family group, we also use your name to show it to whoever invited you and to the other members, without storing it (see "Your name, if you join a family group", below); if you own one, to show it to the members (see "Your name, if you own a family group"). Google is the only way to create an account and sign in: we don't ask for your phone number.
  • If your account is from before October 2026: when it was created, we verified a phone number by SMS. We no longer keep that number: we used it one last time, to link your account to your Google account, and deleted it from our database and from Firebase's sign-in records.

When you use the app

  • Numbers you look up or that call you: when you type a number to look it up, or when a call comes in and the app automatically checks it against our reputation database, we store that number along with the result of the lookup, linked to your account. From those automatic checks we also count how many different people each number called in the last two weeks without being in their contacts, to warn about numbers that call a lot of people. That count keeps only the number and how many, never who received the call.
  • What your carrier says about each call: since Android 11, the phone tells the app whether the carrier checked that the caller's number is genuine, and what it found. The app sends that along with the network the call came in on (4G, 5G, Wi-Fi or 2G/3G) and the code of your line's carrier (for example, 310260). If the number isn't in your contacts, it goes with the lookup of that number and is stored with it. If it's in your contacts or comes in hidden, it's sent without the number and only adds one to a count by hour and by carrier, which keeps neither the number nor who received the call. If the app isn't allowed to see your contacts, it can't tell who is in them: it looks up every number, as it already did without that permission, and what the carrier says goes with that lookup, marked as possibly someone in your contacts.
  • Reports: if you report a number, we store the number, the category you choose (e.g. "scam", "telemarketing"), how long the call lasted if the app knows it and, if you type them, the name of the institution the caller pretended to be (up to 100 characters) and any details you add (up to 500). The report stays linked to your account to prevent repeated false reports, but your identity is never shown to other users — what others see is the number and the categories it was reported under, never who reported it or what they wrote. The only exception is your family group, while you share your blocks (see "Your blocks, if you're in a family group", below).
  • Calls we block: when automatic protection stops a call, we record that fact along with the number, so we can show you your own count and, if you have a family plan, the group's total. Of those calls, the group sees the count, not each person's numbers.
  • Which calls worry you: during the introduction we ask you, once, what kind of calls bother you most (scams, sales, wrong numbers, other). Answering is optional and doesn't change how the app works: it helps us know what to build. Your answer stays on your phone until you create your account, and only then reaches us.
  • Invitations to your family plan: if you have the Family plan, inviting someone means sharing a code with them. We don't ask for anyone's phone number, and we don't store it.
  • Your name, if you join a family group: if you agree to join a family group, other users will see your first and last name as they appear on your Google account: whoever invited you (the group's owner) and the other members of the group. The app tells you before you join. We don't store that name: our server reads it from Google, through Firebase, every time the Family screen is shown. If you leave the group or the owner removes you, the group stops seeing it. If you joined before October 2026, or from a version of the app that didn't tell you, the group doesn't see your name: it sees "Member".
  • Your name, if you own a family group: if you have the Family plan and invite someone, the members of your group will see your first and last name as they appear on your Google account. The app tells you next to the invitation code, before you share it: nobody can join without that code. We don't store that name either: we read it from Google every time a member opens the Family screen. Until you invite someone from a version of the app that tells you this, members don't see your name: they see "Plan owner".
  • Your blocks, if you're in a family group: while you share them, the numbers you report are also blocked on the phones of the other members of the group, and they see them on the Blocked screen with the category and who blocked it: your name if you agreed to show it, and otherwise "the plan owner" or "a member". They don't see what you wrote in the report or the institution. They're shared from the moment you join the group, or from your first invitation if you're the owner, and the app tells you beforehand: right above the button when you join, and next to the invitation code, before you share it, if you're the owner. You can stop sharing them at any time, and start again, with the "Share my blocks" switch on the Family screen. If you were already in the group before the app told you about this, your blocks remain yours alone until you turn it on. They stop being shared if you leave the group, if the owner removes you or if the Family plan stops being active. And each member can choose, on the same screen, to block only the numbers they reported themselves. Verified lines of banks and services that aren't sales lines aren't shared: if you report one, it's blocked only for you.

If you buy a plan

  • Your subscription: which plan you have, when it expires, whether it renews and whether it's in a trial period. We don't see or store your card details: Google Play processes the payment and we only receive confirmation that the purchase exists, through RevenueCat (see "Who we share it with").

Automatically

  • A device identifier: after you sign in with Google, we give you a long-lived credential so the app can talk to our server without asking you to sign in on every call. We store it as a hash (an irreversible fingerprint), not the real value — the same way a password is stored.
  • A notification token: if you agree to receive alerts, Google gives us an identifier for this installation of the app so we can send you notifications — for example, to tell you before a trial period ends, or to update your plan on the phone when it changes. The identifier itself doesn't say who you are, but we store it with your account, along with the app's language, so we know which phone to send each notice to and in which language. It stops working if you uninstall the app or revoke the permission.

3. What we don't collect

  • Your contact list: so as not to interrupt calls from people you already have saved, the app checks — only inside your own phone — whether the calling number matches a saved contact. Your contact list never leaves the device: we don't read, copy or upload to our servers either the list or the number of a contact who calls you. All that comes out of that check is that a call came from someone in your contacts, without their number, to count what the carrier said (see the previous section).
  • The content of your calls: the app only sees the caller's number and what the carrier says about it; it never listens to or records what is said.
  • Your location, photos, text messages, or any other data on your phone not described in the previous section.

4. How we use your information

  • To check, with Google Play, that the app is the original one and is installed on an unmodified phone, and so give your reports more weight.
  • To warn you, before you answer or right after you hang up, whether a number has scam or telemarketing reports.
  • To calculate and publish a number's aggregate reputation (how many reports it has, of what kind, and whether it calls a lot of people) — that reputation is public and doesn't identify who reported it or who it called.
  • To find out whether carriers check the caller's number, and to recognize numbers someone is spoofing, so that reports don't punish their real owner.
  • To review reports and understand which scams are going around, for example who callers pretend to be. Only we read the details and the institution name you type: they aren't shown to other users.
  • To prevent abuse of the system: each account can report a given number only once, and new accounts or accounts with suspicious patterns count for less in the reputation calculation.

5. Who we share it with

  • Google / Firebase: handles sign-in, and is who sees your Google name, email and profile photo, under its own privacy policies. It also checks, with Play Integrity (through Firebase App Check), that the app is the original one and on an unmodified phone, and delivers notifications (Firebase Cloud Messaging).
  • Supabase (our database provider): hosts the information described above, and only our own server can read it. The database has an internet address, but its own access rules don't let anything be read without authenticating except the aggregate reputation of numbers, with no names or data about who reported them. So not even a configuration error on our server would expose personal data.
  • Railway (our server provider): runs the service the app talks to. It processes information in transit in order to respond; it doesn't store it on its own.
  • RevenueCat (subscription management): if you buy a plan, it receives your account's internal identifier — not your phone number or email — and the purchase status Google Play reports, to tell us which plan should be active.
  • Vercel: hosts this website and the legal pages. It receives nothing from your account or your use of the app.
  • The people in your family plan: if you agree to join a family group, whoever invited you (the group's owner) and the other members see your Google first and last name, just as you see the other members' names. We read that name from Google every time the Family screen is shown, we don't store it, and the group stops seeing it if you leave or the owner removes you. If you're the owner, members see your Google first and last name once you invite someone after the app tells you, and we don't store it either. The owner also sees pending invitations, which are only a code, without anyone's number or name. Everyone in the group sees the group's total of blocked calls. No one in the group sees your lookups. Your reports, only while you share your blocks: then they see which numbers you reported, under which category and that it was you, never what you wrote (see "Your blocks, if you're in a family group").
  • We don't sell or rent your information, or share it with advertising networks. Apart from the providers named here — who process it on our behalf and only to make the app work — we don't share it with anyone.

These providers run servers mainly in the United States, where your information is processed under contract with us.

6. How we protect it

  • All communication between the app and our servers is encrypted (HTTPS).
  • Your device identifier is stored encrypted on the phone itself (Android secure storage), not as plain text.
  • The identifier we store in our database is a hash, not the real value.
  • Database-level access rules limit what each part of the system can read, even in the event of a configuration error.

7. How long we keep it

For as long as your account is active. We don't use your information for anything after the account stops existing.

8. How to delete your account

From the app: Settings → Delete my account. We ask you to confirm twice because it can't be undone, and the deletion happens right away; it isn't queued.

What is deleted: your Firebase sign-in record, with the name, email and photo of your Google account; your lookup history, your device identifier, your notification token, your personal blocks, the record of calls we blocked for you, your answer about which calls worry you; the subscription record RevenueCat keeps; your place in someone else's family group, if you were in one, and, if you had a family plan, the whole group with its invitations.

What isn't deleted, and why: your reports stay in the community database, but unlinked from you — they stop being associated with your account and there's no longer any way to know they were yours. What you wrote in them, the institution and the details, is deleted. The numbers you reported keep helping to protect others; deleting them would punish the community for your departure.

Deleting your account doesn't cancel an active subscription: that's done from Google Play. If you'd rather not do it from the app, email us at info@bloquea.do and we'll do it.

The detailed steps, and what to do if you already uninstalled the app, are in Delete your account.

9. Your rights

You can ask us to access, correct or delete your personal information, or tell you what we hold about you, by emailing info@bloquea.do. Before answering, we check that the account is yours.

Deletion doesn't require writing to us: you can do it yourself from the app, in a couple of taps — see "How to delete your account".

10. Children

RingShield isn't directed to minors, and you must be 18 or older to create an account. We don't knowingly collect information from children under 13. If you believe a child gave us personal information, email us and we'll delete it.

11. Do Not Track

We don't track you across other websites or apps, and this site has no cookies or analytics, so a browser's Do Not Track signal doesn't change anything we do.

12. Changes to this policy

We may update this policy as the app changes. If the change is important, we'll tell you inside the app. The date of the last update appears at the top.

13. Contact

Questions, requests about your data, or something that wasn't clear? Email us at info@bloquea.do.

Responsible for your data: Carey Solutions.