1. Introduction
This Privacy Policy applies to Fake Phone Call Prank (the “Application”), package fakecall.prank.app, operated by Monova Tech Pvt. Ltd. (“we,” “us,” “our,” or the “Service Provider”).
It addresses information handled through the Application's features, advertisements, integrated services, and communications you send to us. Information processed on your device is distinguished from information transmitted to us or another organisation.
Where applicable law uses the term “data controller,” we act as controller for processing whose purposes and means we determine. An external provider's role depends on its actual activities and the arrangements governing those activities.
2. Caller Details, Media, and App Preferences
Information used in a call display
Where caller-customisation features are available, information you enter is processed to create the selected display. This can include a caller name, a displayed telephone number, a caller image, and associated appearance or scheduling preferences.
A fictional name or number does not necessarily identify a real person. However, a real person's name, photograph, telephone number, or voice can be personal information. Use fictional details where possible and avoid entering another person's information without appropriate permission.
Displaying a number in a simulated interface is different from dialling that number, sending it to a lookup service, or accessing device contacts. These activities must not be treated as interchangeable.
Photos, recordings, and audio files
Where media customisation is supported, an image or audio file you provide may include identifiable people, voices, file names, or embedded metadata. Playback of a ringtone or existing sound file is different from microphone recording.
The description of a fake call does not, by itself, establish whether media is recorded, imported, uploaded, or kept exclusively on the device.
Complete the feature and data disclosure: [Identify the caller fields, photos, audio, scheduled events, history, and preferences actually processed. State which remain on the device, which are transmitted, the recipients, purposes, and storage locations.]
[Confirm whether the app only simulates calls or also initiates real calls, sends messages, contacts third parties, accesses device contacts, or reads call logs. Disclose any actual recording, transcription, voice processing, or remote content service. Do not infer these practices from the app's name.]
3. Permissions, Notifications, and Scheduling
Contacts and telephone access
Entering a name or number manually does not, by itself, require reading the device's contact list or call history. If a contact-selection function is implemented, the disclosure must identify what is accessed and whether only a selected contact or a broader set is processed.
Media and microphone access
Android's system picker can provide selected-photo access without opening the entire photo library. Direct camera capture and microphone recording have different permission requirements.
Any recording feature must clearly distinguish deliberate recording from playing an existing sound. This policy does not assume that a microphone or camera feature is present.
Scheduled displays and notifications
Where scheduled fake-call displays are supported, their timing and notification settings are used to trigger the requested event. Information shown on a notification, lock screen, or call-style display may be visible to someone nearby.
Dismissing an event, cancelling its schedule, and deleting its saved caller details are separate actions. Leaving the main app screen may not cancel a scheduled event.
Complete the permission inventory: [List only permissions and special access actually used, with a purpose for each. Confirm contact, phone, call-log, SMS, media, microphone, camera, notification, alarm, overlay, and full-screen access where applicable. Describe actual cancellation controls and any background processing.]
You can review available permissions in Android settings. Revoking access can affect the relevant feature but does not automatically erase previously stored or transmitted information.
4. Advertising, Measurement, and Other SDKs
The Application contains advertisements. Advertising software development kits, or SDKs, can communicate directly with their providers. This remains part of the Application's data practices even when information does not pass through our own servers.
Advertising-related information
Depending on the actual service and configuration, advertising processing can involve IP addresses, approximate location inferred from network information, advertising or installation identifiers, device characteristics, app versions, ad views, interactions, and diagnostic information.
These are examples to verify, not a confirmed inventory for this Application. Relevant purposes can include delivering advertisements, measuring performance, preventing invalid traffic, and personalising advertising where implemented and legally permitted.
Complete the advertising disclosure: [Identify the actual advertising network, all relevant mediation partners, and any analytics, attribution, or crash-reporting providers. Include their official privacy links, data categories, purposes, and retention arrangements.]
[State whether caller details, contact information, photos, audio, or other user-created content are accessible to or supplied to these providers. Describe the actual consent, refusal, withdrawal, and opt-out controls and how users reopen them.]
Consent and advertising choices
Where applicable law requires consent before advertising-related device access or processing, the relevant activity must wait until valid consent has been obtained.
Non-personalised advertising does not necessarily mean that no information is processed. Delivery, measurement, and fraud-prevention functions may still involve data, depending on the service.
Selecting an advertisement may open another app, website, or store listing. Information you independently provide there is handled by the relevant recipient. Its privacy policy does not replace our responsibility to explain processing within this Application.
5. Other Information
Support communications
If you contact us, we receive your email address, message, attachments, and ordinary email delivery information. You may voluntarily include your device model, Android version, or app version to explain a problem.
Remove real telephone numbers, private notifications, and unrelated personal information from screenshots before sending them. Do not send passwords, payment-card information, identity documents, or recordings that are unnecessary for the request.
Accounts, purchases, and remote services
Complete additional-service disclosures: [Confirm whether accounts, subscriptions, purchases, remote content downloads, or cloud synchronisation exist. For implemented features, identify the information processed, providers, storage, and deletion arrangements. Remove inapplicable provisions.]
6. Purposes and Legal Grounds
Feature information is used to provide the functions you select. Advertising and technical information must be limited to the verified purposes disclosed for the relevant services.
Information you send us is used to respond to your communication, investigate reported issues, handle privacy requests, and meet applicable legal obligations. Where necessary and lawful, it may also support legal claims.
Complete the processing-purpose mapping: [Identify each actual purpose and, where required, its legal basis. Specify any legitimate interests relied on and explain which processing is optional. Consent, contractual necessity, and legal obligations are not interchangeable justifications.]
You may withdraw consent for processing that relies on it without affecting earlier lawful processing. Installing the Application or continuing to use it does not replace affirmative consent where required.
8. Storage and Data Retention
Caller profiles, schedules, and media
Retention must distinguish saved caller profiles, pending events, event history, imported or recorded media, temporary files, and any server-side copies. Cancelling a scheduled event does not necessarily delete its saved profile or attachments.
Complete the retention schedule: [State the actual retention periods or meaningful criteria for feature data, uploaded media, advertising records, diagnostics, consent records, and any account or purchase information. Include backup deletion schedules, provider responsibilities, and specific lawful exceptions.]
Support correspondence
The proposed retention rule for correspondence is to keep identifiable information while resolving the request and necessary follow-up. Further retention is limited to a specific continuing need, such as an unresolved dispute or applicable legal obligation.
Information no longer needed for those purposes is to be deleted or irreversibly anonymised. A limited record of a privacy request and its outcome may be retained where necessary to demonstrate appropriate handling.
Device backups
Depending on app configuration, Android version, and your settings, backup or device-transfer services may preserve or restore local app data. These copies can have a separate lifecycle from the currently installed Application.
9. Your Choices and Data Deletion
Permissions and local information
Review permissions through Android settings. Use the controls implemented in the Application to cancel events or manage saved information. Confirm that a scheduled event is cancelled rather than merely dismissing its current display.
Android's app-storage controls can clear app-specific data. Preserve any information you need before clearing storage or uninstalling. Clearing only the cache is not necessarily the same as deleting saved profiles and preferences.
Manage original media, exported files, backup copies, and information already transmitted to external services separately. Revoking a permission does not automatically delete previously obtained copies.
Advertising controls
Supported Android devices provide controls to reset or delete the advertising ID. Available menus vary by device and Android version.
These controls do not necessarily remove ads, erase previously collected records, or replace consent and opt-out mechanisms required within the Application.
Submit a privacy request
Email
rajesh@monovatech.com
with the subject
Fake Phone Call Prank — Privacy Request.
Include the package name
fakecall.prank.app.
Explain the request without providing unnecessary sensitive information. Verification, where necessary and legally appropriate, will be proportionate. We will handle information under our control and coordinate with processors where required.
Where another organisation independently controls information, its applicable request procedure must also be identified. Involving an external provider does not remove our own responsibilities.
Uninstalling the app does not automatically delete remotely held records, previously sent emails, or accounts, and does not cancel a subscription.
Complete release-specific deletion instructions: [Provide the actual steps for deleting profiles, recordings, and remote data. If accounts exist, include the in-app account-deletion process and external deletion resource. Identify any justified retention exceptions.]
10. Your Privacy Rights
Your rights depend on your location, applicable law, and the processing involved. Legal conditions and exceptions may apply.
European data-protection rights
Where the General Data Protection Regulation applies, rights may include access, correction, erasure, restriction, portability, objection, and safeguards concerning certain automated decisions. You may withdraw consent where processing relies on it and complain to the competent supervisory authority.
California privacy rights
Where the California Consumer Privacy Act, as amended, applies, eligible residents may have rights to know and access information, correct inaccuracies, request deletion, opt out of sale or qualifying sharing, limit certain sensitive-information uses, and exercise rights without unlawful discrimination.
The final policy must identify the actual sale or sharing practices and any required opt-out methods, including handling of legally applicable opt-out signals.
Handling requests
Contact us using Section 15. We will respond within applicable legal time limits. Authorised agents may act where permitted. Verification will not be imposed where prohibited.
Where required, a refusal will include its reason and the available review or appeal procedure.
11. Children's Privacy
Names, photographs, voice recordings, and advertising identifiers can be personal information concerning children. An entertainment theme or app-store content rating does not establish compliance with children's privacy requirements.
A parent or guardian who believes a child's information has been handled unlawfully may contact us. We will review the concern and take the action required by applicable law.
Complete the audience disclosure: [Identify the actual intended audience and any justified age restriction. Confirm required age screening, parental authorisation, and child-related advertising settings. Do not copy an age threshold from another app.]
12. International Processing
Monova Tech Pvt. Ltd. is based in Nepal. Information you send us may be handled there and by providers involved in delivering or storing your communications.
Complete international-transfer details: [Identify relevant processing locations for advertising and other remote services. Where transfer restrictions apply, describe the safeguards actually used and how users can obtain information about them. Do not claim an unverified contractual mechanism, adequacy decision, or certification.]
13. Security and Personal-Data Incidents
Caller details and media may reveal information about users or other people. Their protection must cover relevant storage, access, transmission, and service-provider handling.
Complete the security disclosure: [Describe verified technical and organisational safeguards, including protection of any uploads and SDK traffic. Do not claim encryption, audits, certifications, or access controls that have not been established.]
No electronic storage or transmission method can be guaranteed completely secure. Protect access to your device and consider what caller information is visible on its screen.
If an incident involving information under our control requires notification, we will notify the relevant authorities and affected individuals as required by applicable law.
This privacy-policy page
This HTML document contains no scripts, tracking pixels, external fonts, or embedded advertisements. Its hosting server may separately process connection information and access logs. The document alone does not establish the hosting service's logging practices.
14. Changes to This Privacy Policy
We may revise this policy when the Application, its providers, our procedures, or applicable requirements change. The published version will show its last-updated date.
Where additional notice or consent is required for a material change, we will provide that notice or obtain consent before the relevant processing begins.
Updating this document does not replace a required in-app disclosure, permission, consent mechanism, or deletion control.
15. Contact Us
For privacy questions or requests concerning Fake Phone Call Prank, contact:
Monova Tech Pvt. Ltd.Birtamod Municipality-4
Jhapa, Nepal
Email:
rajesh@monovatech.com
Please include Fake Phone Call Prank
and package fakecall.prank.app
in your message.