Privacy Policy – Safe Caller

First published: September 7, 2026

Last updated (this version applies from this date): October 2, 2026

Applies to: the Safe Caller app for Android and iOS

1. Who we are and scope

Safe Caller identifies calls, detects numbers used for spam, and helps you block unwanted calls. It is developed and operated by Wilmar Arango, an individual doing business under the trade name "WeDevTek", based in Colombia (referred to here as "we", "WeDevTek", or "the developer"), the party responsible for processing the data described below.

For anything related to your data, this policy, or the app, write to [email protected]. That is the address for all of your requests.

This policy is governed by Colombian data protection law (Law 1581 of 2012 and its implementing decrees) and is written to also respect the data protection and consumer laws of any other country where the app is available. If you live outside Colombia, in addition to what this policy says you have whatever rights the laws of your place of residence grant you, and those rights prevail to the extent they cannot be waived. It meets the requirements of Google Play's User Data policy and Apple's App Store privacy guidelines.

2. In short

3. Installation identifier (UUID)

When you install Safe Caller, the app creates a random installation identifier (UUID), unique to each installation and not tied to your identity, your phone number, or any personal data. You can view and copy it from the app's information screen.

The UUID is sent with the app's requests to our servers and is used to:

It is a pseudonymous identifier: it lets us tell one installation apart from another, but not who you are. It is not used for advertising or to track you.

4. Access to your contacts (optional, processed only on your phone)

Safe Caller may ask for permission to read your contacts. It uses them only to:

Your contacts never leave your device: the match happens on your phone; they are not transmitted, not stored on any server, not shared with third parties, we cannot see them, and the app never modifies them.

If you don't grant the permission, the app can't tell which calls come from your contacts, and what happens depends on how you use Safe Caller:

If someone in your address book has been reported by other users, you will see the name the community reported it under, not the one you gave them; Safe Caller is not responsible for that name or that report. Every other feature of the app keeps working normally, except the initial call-history check (section 8), which is only offered if you also grant this permission.

5. Lookup of unknown numbers

When you get a call from a number not in your contacts, or when you look up a number by hand, Safe Caller sends that number and your line's country code to our server to ask whether the community has reported it, and with what name and category. As with any internet service, each request also carries your installation identifier (section 3), your IP address, and standard technical data: app version, platform (Android or iOS), and device model.

We use this data to answer the lookup, operate the service and let you know when a newer version of the app is available. We do not keep a history of your lookups or build a profile of you; the request's technical data only remains in the temporary logs described in section 12. We keep aggregated usage statistics (for example, the number of lookups per day and country) with no link to whoever made the lookup.

On iOS, identification and blocking rely mainly on a list the app syncs to your device through CallKit's Call Directory extension: if the number is on that list, iOS identifies or blocks it without any server lookup during the call. If it is not, the lookup happens through a server using the PIR protocol (Private Information Retrieval), a cryptographic technique that resolves the query without the server being able to tell which specific number is being checked.

6. Reporting, voting, and blocking (community database)

Safe Caller lets you, on a voluntary basis, block and report numbers, mark a number as "not spam", and report a displayed name you consider incorrect. Doing so sends the following to the server:

By doing so you expressly authorize that data to be sent and stored in our community database for the sole purpose of warning other people. The stored number is the caller's, not yours, and your name, your email, and your contacts are not sent. If the number you block is already saved in your address book, the block applies only on your device and nothing is sent to the server.

The name you write is shown to other people exactly as you send it, save for minor formatting adjustments (such as trimming spaces or length). WeDevTek does not rewrite its content; it can only moderate or remove it under the Terms and Conditions (section 6).

We also keep a record of which installation (identified by its UUID, not by your identity) submitted each report or vote, to operate the service and the free-premium program. The community database is a helpful tool, not an absolute truth: it may contain errors. In section 19 we explain how to request a review or removal of a number.

7. Numbers verified by our team

A number can only be marked "Verified business" or "Verified user" after the community has reported it first: our team does not create these records on its own. When a reported number goes into review, someone on our team examines it using the information the community already provided and, when available, information supplied by whoever claims to be its owner, and decides whether it should be marked as verified instead of spam. We store the number, the confirmed name, the category (business or user), and internal review data, which is not shown to users.

This is different from the "Verified number" badge that can appear during a call (section 9): that one is an automatic technical check by the phone network and says nothing about who the number's owner is. Because the verification is based on information from a given point in time, we do not guarantee that it remains correct indefinitely: it can be corrected, withdrawn, or marked as spam again if the situation changes. Any user can still block or report a verified number, and you can ask us to review a verification (section 19).

8. Call history

With your permission, Safe Caller reads your phone's call history to:

The first two features happen on your phone. The initial check only runs if you tap "Check for Spam" and does not send your full history or the numbers you already have saved; it only looks up the most recent unknown numbers, the lookup is not stored tied to your installation, and the result is stored locally.

9. Network verification and spoofing detection (STIR/SHAKEN)

When your carrier supports it, Safe Caller may show a "Verified number" or "Verification failed" badge during a call. We do not compute it ourselves: it is generated by STIR/SHAKEN, a telephone industry standard carriers use to sign that a number was not spoofed along the call's path. Safe Caller only reads and displays that signal and receives no data of yours for this. This badge does not confirm who is calling or that they are trustworthy: you can receive a call showing "Verified number" from a number the community has reported as spam.

Additionally, on Android the app can analyze an incoming call's number on your device to detect other signs of caller ID spoofing. To do so it downloads a configuration from our server; your number and call data are not sent.

10. Premium and free-premium features

The premium subscription is managed through Google Play (Android) or Apple (iOS), with RevenueCat as a technical intermediary. Payment and billing data are handled by the store; we never see your card. To link your purchase to your installation we share your UUID with RevenueCat, which tells us whether you have premium active and until when.

If you report numbers that the community later confirms as spam, you can earn premium time without paying. To manage this we store, tied to your UUID, the numbers you reported within the program and the data needed to manage the reward, its status, and its validity period.

11. Data that stays on your device

Your block rules, your settings, your blocked and trusted number lists, the filtered-call history, your protection statistics and achievements (blocked calls, reports, streaks, experience), the lookup cache, and the synced list of your country's most-reported numbers are calculated and stored only on your phone. We never send them to our servers or share them.

You can turn off achievements and streaks from the settings: we stop showing them to you, but what was already stored is not deleted. All of this is deleted when you uninstall the app or clear its data from your device's settings. On Android, the app does not take part in automatic backups.

12. Technical logs and error reports

Technical logs. Our servers keep operation logs that may include the IP address, date and time, the requested resource (which may contain the number looked up), technical request data such as app version, platform, and device model, and error codes. They are used solely to operate the service, detect failures, and investigate security incidents, not to build profiles or for advertising. They are kept for at most 30 days and then deleted automatically.

Error reports. The app sends Sentry technical reports of crashes and usage sessions (error type, app version, device model and system version, random technical identifiers). These reports do not include phone numbers or data that identifies you. We use them only to fix bugs and keep the app stable.

13. What we use data for and legal basis

We use data only to:

Under the law that applies to you, we process it on these bases:

Regarding the content of the community database — including numbers marked "Verified business" or "Verified user", which also originate from a community report — WeDevTek acts as an intermediary and hosting provider: it does not create that content independently, it does not guarantee that a verification remains accurate indefinitely, and each reporting user remains responsible for their report.

14. Store summary (Data Safety / Privacy Nutrition Labels)

As Google Play and the App Store require, here is a summary of the data handling:

15. App permissions

Safe Caller requests operating-system permissions only when it needs them, with an explanation of why. You can revoke them anytime from your device's settings; if you revoke an essential permission, some features will stop working.

Common to Android and iOS

Android

iOS

16. Who we share data with and international transfers

We do not sell or transfer your data. The only third parties that may receive information as part of the app's normal operation, to perform their technical function, are:

We may also disclose information if a competent authority requires it by law or a valid court order, or if necessary to protect our rights, people's safety, or the integrity of the service.

Our servers and some of these providers may be located outside your country, including the United States and the European Union. By using Safe Caller, you understand that the information described in this policy may be processed in those countries, always with appropriate safeguards and only for the purposes stated here.

17. How long data is kept

18. Security

We encrypt communications between the app and our servers using HTTPS and apply technical and organizational protective measures. We do not store sensitive personal data or associate it with information that could identify you. No system is infallible, but we work to keep these measures up to date.

19. How to request the correction or removal of a number

If you believe a number — yours or your business's — appears reported by mistake, that a verification is no longer accurate, or you simply want it removed from the database, write to us at [email protected], stating the number in international format and, if you can, why you consider the record incorrect. You can also use the app's "Request number removal" option.

We may ask you for additional information to confirm that you are the number's owner or have standing to make the request. We will review the request and, where appropriate, correct or delete the record within a reasonable time. You do not need to be a Safe Caller user to make this request.

20. Your rights and data deletion

Under the data-protection law that applies to you (in Colombia, Law 1581 of 2012; and, depending on your country of residence, the equivalent law protecting you), you can:

To exercise any of these rights, write to us at [email protected]. Since we do not store data that identifies you, for some requests we will need to ask you for the specific data point you want to manage: the installation ID (you can view and copy it in the app), which lets us locate the data tied to your installation, or the reported number.

21. On the accuracy of spam information

Safe Caller gathers and displays reports made by its community of users. The names and categories you see on a reported number were written by other people, not by us. Although we work to reduce errors, we do not guarantee that the information is accurate, complete, or current: a legitimate number can appear flagged, or an annoying one may not be. This also applies to numbers marked "Verified business" or "Verified user" (section 7): our review starts from the same community information and is not infallible either. Safe Caller is a decision-support tool, not a verification service.

The Terms and Conditions have the details on WeDevTek's role as an intermediary and on the limits of liability. If a number affects you, the primary and required first step for resolving it is to write to [email protected] (see section 19 and section 8 of the Terms).

22. Children

Safe Caller is not directed at children under 13, and we do not knowingly collect data from children under that age. If you are a parent or guardian and believe a minor in your care has used the app in a way that involves data processing, write to us and we will resolve it.

23. Changes to this policy

We may update this policy when the app's operation or applicable regulation changes. We always publish the current version on this page, with its first-published date and last-updated date at the top; material changes are published here stating the date from which they apply.

Safe Caller has no accounts and we do not store your contact details, so we cannot notify you individually: we recommend checking this page periodically. If you disagree with a change, you can stop using the app and uninstall it.

24. Acceptance and contact

By downloading and using Safe Caller, you confirm that you have read and understood this policy and that you accept the data handling it describes. Using the app also implies accepting our Terms and Conditions. If you disagree with something, please do not use the app. For a shorter explanation, check our FAQ.

This policy is published in Spanish and English. In case of any discrepancy, the Spanish version prevails.

Data controller: Wilmar Arango (an individual), acting independently under the trade name "WeDevTek", Colombia.
Email for all of your requests: [email protected]