1. Controller and contact
The controller of personal data processed through BanCaller is WISE Group Sp. z o.o., ul. Poznańska 64, 05-850 Jawczyce, Poland, KRS 0000957362, NIP 1182237693. This policy covers bancaller.com and the BanCaller apps for iOS and Android.
For personal data matters, write to odo@wise.pl. For questions about the app or your account, write to support@bancaller.com. You may also write to the company’s postal address. Full operator details are available in the Legal notice.
2. What data we process and where it comes from
- Account, if you create one: nickname, email address, secured password hash, selected language and time zone, account state and service dates, associated devices, report and point history, rank and badge history with award dates, and an optional note and avatar. Signed-in community members can see your nickname, time zone, rank, bio, avatar and earned badges. The “Hide detailed information” setting hides your bio, avatar and badges from other people, including friends. Your email, point balance, devices and report history are not part of your community profile. We store only the cropped avatar without photo metadata; the original is not sent to the server. You can change your nickname, edit or remove your note, and replace or remove your avatar. Your email address remains unchanged. Your nickname is public and need not be your real name. An account is optional, but using the service without one does not mean that no technical device data is processed.
- Invitations and friends: The sender provides the recipient’s email, a suggested nickname and an optional message. We store these details encrypted, along with invitation status and dates, friendships, notifications and email/PUSH delivery information. The recipient sees the sender’s profile and invitation message. The message is not included in PUSH alerts. A new account referral is tied to the selected link; when its conditions are met, we record a reward event and points for both people.
- Community safety: the reason and optional details of an abuse report, a private snapshot of content visible to the reporter, an optional copy of the visible avatar, administrator decisions, user blocks and operation history. Details, snapshots and image copies are encrypted. Authorised administrators handling the case can access them. We review new and changed avatars before showing them to other users.
- Sign-in with Apple or Google: If you choose this method, the provider shares an account identifier and a verified email address, including an Apple relay address if you select one. A shared name is used to suggest a public nickname, which you can change before registering. We store the confirmed nickname, a cryptographic hash of the identifier and its link to your BanCaller account. The Apple token needed to revoke authorization is encrypted. We do not request your contacts, files or provider password. Account deletion removes the link and queues Apple authorization revocation; the information needed for this task remains encrypted until the task is handled.
- Device and security: installation and device identifiers used by BanCaller, platform, device name, public key, access and verification information, attestation results, timestamps and IP address. App and device authenticity checks use Apple or Google services. On Android, anti-abuse mechanisms may use a hash of the Android ID; on iOS, identifier signals may include IDFV. The device private key is never sent to BanCaller.
- Checking or reporting a number in the app: phone number, selected category, operation identifier and time, and its technical link to the device and, once the device is assigned, to the account. A manual online number check sends the checked number to the server. It does not automatically submit a report. Public website searches and comments are described separately below.
- Number database: numbers, categories, statuses, report and moderation history, and names or labels entered by the operator. Sources include user reports and entries added manually by WISE Group. The data may concern someone who does not use BanCaller.
- Protection and notifications: selected numbering zones, synchronisation settings, database update information, access identifiers, and a PUSH token and notification history when notifications are used.
- Website and contact: session data, preferred language, IP address and technical request information, security events, email address and the content of correspondence you send. Do not send passwords, tokens or other people’s data that is not needed to resolve the matter.
On public website pages, we use Google Analytics 4 only after voluntary consent to visitor statistics. We do not use advertising or third-party error monitoring. Security features and technical logs are not used to build advertising profiles.
2a. Public number pages and comments
The “Check a number” form processes the number you enter and the date of its most recent check. The number receives a permanent public page URL, and the list shows the 10 most recently checked numbers. We do not publish the identity, IP address or account of the person who checked it. A check does not create a mobile report.
The comment form collects a display name, text, number rating, submission identifier and date, and an IP address for security and moderation. We record the comment’s status and administrator decision details, including the time and reason. The comment record does not contain the author’s account identifier and may be submitted without signing in. The display name may be a pseudonym and is not a verified identity. A separate, temporary limit register stores the number, next permitted comment time and latest submission identifier: with an account identifier for a signed-in user, or pseudonymous browser and IP keys for a guest. Guest keys are created using a cryptographic function separately for each number and purpose; this register does not contain the raw IP address or cookie identifier.
After administrator approval, any visitor may read the phone number, comment, rating, display name and submission date. Search engines may index and store this content. The IP address, non-public moderation reason and technical submission details are not part of the public comment. Do not include information you do not wish to disclose or unnecessary data about other people in the display name or text.
The source of the checked number and comment is the person who used the form; number labels come from the BanCaller reports database and moderation. The information may concern someone who does not use the service. Rules for reporting violations and challenging comments are in the Terms of Use; data rights are described in sections 8 and 9 below.
3. What happens on your phone
Call identification relies on a downloaded database on the phone. An incoming call alone does not send a report to BanCaller. The app does not upload your address book or full system call history. It does not record calls or send SMS content.
On iOS, the system reporting extension receives the call or message data selected by the user. BanCaller uses the sender’s number and the selected category, not the message content. A deliberately prepared report may be delivered through Apple’s system to the server as a proposal and confirmed using the app’s mechanism.
On Android, the call-screening role allows the system to pass handled-call data to the app. Matching against the database and the handling decision occur locally. The app may retain local call context so the user can later report a selected number. Submitting the report requires user action.
System settings let you disable identification, blocking and notifications. Revoking a permission may limit the related feature but does not erase data previously sent to the server. Uninstalling the app does not delete the account.
4. Purposes and legal bases
- Providing requested features: operating accounts and devices, search, database updates and reports — necessary to perform a contract or take steps before entering into one, Article 6(1)(b) GDPR.
- Handling a comment at the author’s request: receiving, moderating and publishing the display name and text as part of the requested service — Article 6(1)(b) GDPR. Accepting the terms is not separate consent to unrestricted use of the data.
- Limiting abuse and maintaining security: device verification, limits, prevention of false reports and incident handling — the legitimate interests of the controller and users, Article 6(1)(f) GDPR.
- Comment IP addresses and moderation: detecting spam and repeated posts, enforcing limits and investigating abuse — the legitimate interests of the controller and users in protecting the service, Article 6(1)(f) GDPR.
- Creating and sharing number information: helping identify unwanted calls and updating and moderating the database — the legitimate interests of the controller and users, Article 6(1)(f) GDPR, with due regard for the rights of people whose numbers are involved.
- Public number pages and information about others: sharing experiences of calls and information that helps assess an unknown number — the legitimate interests of the controller and users, Article 6(1)(f) GDPR. We take account of the rights of the people concerned, who may object and ask us to assess whether further processing is necessary. A contract with a comment’s author is not a legal basis for processing another person’s data.
- Contact, complaints and claims: performance of a contract or the legitimate interest in responding and protecting rights — Article 6(1)(b) or (f) GDPR. Compliance with a legal obligation is based on Article 6(1)(c) GDPR.
Providing data is voluntary, but we cannot provide a feature without the data it requires. System consent for notifications or access to phone features is not consent to arbitrary data processing and does not replace a legal basis.
A number’s status is calculated automatically from reports and moderation rules and may be changed by the operator. Depending on the recipient’s settings, this may result in a call being labelled, silenced or rejected. It is not a finding that the number owner committed a crime. You can challenge the result and request human review.
5. Recipients and data location
WISE Group operates hosting, the database, mail and backups itself on infrastructure in Poland. Administrative access is limited by role and by the responsibilities of people operating the service.
Other users’ apps receive the data needed to identify numbers: a number, its label, category and status. We do not distribute your email address, password or the identity of a particular report’s author with the database.
Public number pages, display names, dates and approved comments are also accessible to people without accounts and to search engine crawlers. Comment IP addresses are not published; panel access is restricted to administrators. Hiding or deleting content from BanCaller does not guarantee immediate updates to copies held by independent search engines.
Under section 7 of the Terms of Use, copying all or a substantial part of the number database, or using programs, bots, robots or scripts to scrape or systematically reconstruct it, is prohibited without the Operator’s prior knowledge and express permission. Public availability of data or downloading the database through the official app does not constitute such permission. The permitted app features, ordinary number checks, search engine indexing and statutory rights described in the terms remain unaffected.
Making information available in BanCaller does not constitute consent by the people concerned to unrestricted further processing of their personal data by others. The Operator’s permission to use the database does not replace a required legal basis for processing personal data. The prohibition on copying the database does not restrict your rights to access your own data, receive a copy or exercise data portability under the conditions described in section 8.
- Apple: iOS app distribution, app and device verification, system reporting and APNs notifications. These services may process identifiers, authenticity evidence and technical data needed to perform an operation.
- Google: Android app distribution, Play Integrity and Device Recall, and Firebase Cloud Messaging notifications. These features use verification data, installation identifiers, tokens and other technical data required by the service.
- Google Fonts: the website downloads fonts from Google servers. In doing so, the browser connects to Google and transfers an IP address and technical request data, among other information.
- Google Analytics: after consent, Google receives public page visit data, pseudonymous cookie identifiers and technical browser and device data. The connection also sends Google the IP address. We send page categories instead of full page URLs and titles, and restrict the referrer to its domain. We do not send phone numbers, account details, form contents, URL parameters or tokens. Measurement does not run on sign-in pages or private panels. Advertising features and Google Signals remain disabled.
- Authorised authorities: data may be disclosed where and to the extent required by law.
The Polish location of WISE servers does not mean that all Apple and Google operations take place in Poland or the European Economic Area. These providers operate globally. They describe data transfers and safeguards in the Apple Privacy Policy, Google Privacy Policy and Firebase privacy information. Information about safeguards applicable to a particular transfer by BanCaller and how to obtain a copy is available from odo@wise.pl.
6. How long we retain data
The following describes how the service currently operates. Account deletion and backup retention are separate matters.
- Google Analytics: detailed event data is configured to be retained for 2 months, and user data for 14 months. The user retention period resets on new activity. These settings do not limit most standard reports based on aggregated data. Consent choice and cookie lifetimes are described in section 10.
- Account data: until account deletion, with parts of the history retained as described below.
- Report, number, moderation, point, rank and badge history: currently retained without a set automatic deletion date. After account deletion it remains in pseudonymised form and should not be treated as fully anonymous.
- Invitations and friendships: a pending invitation expires 30 days after sending and disappears from the lists. When it ends, we clear the recipient address, nickname suggestion, message and tokens; an hourly task cleans up expired entries. The address hash used to limit repeat invitations remains until 30 days after sending. The invitation status and reward audit may remain without that content. Accepted friendships do not expire after 30 days. Account deletion removes its friendships and private invitation and notification data.
- Community abuse reports: we retain details, content snapshots and avatar copies while reviewing the case and for up to 90 days after resolution. An hourly task clears them after this period. Deleting either the reporting or reported account clears this private content regardless of case status. An audit remains without text or images: identifiers, reason, status, dates and the administrator decision; there is currently no separate automatic deletion period for this audit. Account deletion removes its community blocks and block-operation history.
- IP address recorded with a comment: for up to 90 days from submission, unless the comment is deleted earlier. After that time it is no longer displayed in the administrator panel, and a task scheduled hourly removes it from the active comments table. This period applies to that copy of the IP address, not to separate logs or historical backups, whose retention is described below.
- Temporary comment-limit data: the link between an account or pseudonymous browser key, a number and the latest submission identifier enforces a 30-day limit from acceptance of the comment. The additional guest IP key enforces a one-hour limit. A task scheduled hourly removes expired entries; account deletion immediately removes entries assigned to that account. Retrying, rejecting or deleting a comment does not extend or shorten the period. Once these data are removed, no permanent assignment of the comment to an account is retained. These periods are separate from the 90-day retention of the IP address recorded with the comment.
- Public pages and comments: numbers and check dates are used to maintain number pages and the list of recent checks. Comment text, display names and moderation data are retained during publication and, where necessary, to handle complaints and appeals or establish, exercise or defend legal claims. There is currently no general automatic deletion schedule for this data, including rejected or hidden comments. An administrator may delete a comment and its display name, IP address and moderation data from the live service; historical backups follow the separate retention rules described below. This does not create a right to retain it indefinitely without a need; you may request a review of continued retention, erasure or restriction of processing.
- Application and server logs and support correspondence: the operator does not currently apply a general deletion schedule. Cleanup of certain data associated with a deleted account is described in the next section.
- Backups: cover up to five years. A backup created before account deletion may contain earlier data until that backup expires. Account deletion does not retroactively modify every historical backup.
- Short-lived data: activation tokens, authentication challenges and synchronisation files have their own expiry periods or cleanup mechanisms. This does not delete source reports or the entire history.
The absence of an automatic deletion period does not remove your GDPR rights or mean that every type of data may be retained without limit. You may ask us to assess whether continued processing is necessary, erase the data or restrict its processing.
7. How to delete your account and data
You can delete your BanCaller account on the website without having the app installed: open the account deletion form, sign in and confirm deletion with your current password or a fresh identity confirmation using your linked Apple or Google account. Deletion is also available in the app. If you cannot sign in, write to odo@wise.pl. We may need suitable identity verification before completing a request — do not send us your password.
Account deletion is permanent. In the active database, the email address, preferred language, time zone and note are removed, the avatar is no longer accessible, the nickname is replaced with a neutral label, and the existing password, sessions, tokens and assigned-device access are revoked. Some associated cleanup runs in the background and includes all avatar files for the account and, among other things, IP addresses in linked application logs, names from registration attempts and selected notification content.
We do not automatically delete the entire history. Reports, points, rank and badge-award history, status history and identifiers needed to preserve technical relationships remain. This is pseudonymisation, not a guarantee of irreversible anonymisation. Numbers that were reported do not disappear merely because the reporter’s account was deleted.
Deleting an account immediately removes its temporary comment-limit data. Comment records are not permanently linked to an account, so the comments and their display names are not automatically deleted with it. You may make a separate request about a comment by identifying the number page and comment. The display name and text remain public while the comment is published; they are not automatically replaced when a deleted account’s nickname is changed.
Signing out or uninstalling the app does not start account deletion. Deleting the account does not automatically remove correspondence from a separate mailbox, every infrastructure log or data independently processed by Apple and Google. You can submit a request concerning additional data to the data protection contact address.
8. Your rights
Subject to the GDPR, you have rights of access and to a copy of your data, rectification, erasure, restriction of processing and data portability when the relevant conditions are met. You may object to processing based on legitimate interests by explaining your particular situation. If processing is based on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Send your request to odo@wise.pl. You do not need a BanCaller account to make a request about your data. We should respond without undue delay, generally within one month; any extension requires a legal basis and notice to you under the GDPR.
You may lodge a complaint with the President of the Polish Personal Data Protection Office — information is available at uodo.gov.pl — or another competent supervisory authority. You do not have to exhaust the operator’s complaint procedure first.
9. If your number is in the database
Information may come from other users or be added by WISE Group. A number and its label are shared through search and the protection database. This does not mean that we have confirmed the identity of the person who actually made every call — a number may be spoofed or reassigned.
If you believe an entry is wrong or infringes your rights, write to odo@wise.pl with the number and a description of the matter. You may request information about the data source, rectification, erasure or restriction, or object to the processing. Verifying your entitlement to a number should not require unnecessary data.
Resetting a spam label in the app is a technical feature. It does not replace a GDPR request and does not erase historical reports.
11. Minors
BanCaller is intended for people aged 13 and over. We do not target younger children. Requirements for parental consent or involvement under the applicable law still apply to minors.
During registration, users declare that they are at least 13. We do not collect dates of birth or verify age or parental consent. If you believe we are processing data about a child under 13, contact odo@wise.pl so that we can investigate and remove data where required.
12. Changes to this document
The document version is shown at the top of the page. Changing the privacy description does not itself constitute consent to a new processing purpose. If a new feature requires separate information or consent, it must be provided in accordance with the law.