<J/> MisterJ.Devs

PRIVACY POLICY

Effective Date: August 3, 2026 Last Updated: August 3, 2026

This Privacy Policy applies to mobile, desktop, web-based, and other utility applications published by MisterJ Dev that display or link to this Privacy Policy, collectively referred to as the “Apps.”

MisterJ Dev is an independent software developer. In this Privacy Policy, “Developer,” “we,” “us,” and “our” refer to MisterJ Dev.

By installing, accessing, or using an App, you acknowledge that you have read and understood this Privacy Policy.

1. Privacy-First Approach

Our Apps are designed to operate primarily on the user’s device.

We do not operate remote servers for the purpose of collecting, profiling, tracking, selling, renting, or storing users’ personal information or device information.

Unless an App clearly states otherwise in an app-specific disclosure:

  • No user account is required.
  • No registration is required.
  • No advertising SDK is included.
  • No behavioral advertising is performed.
  • No analytics or tracking SDK is used.
  • No user profile is created.
  • No personal information is sold or rented.
  • No information is used for targeted advertising.
  • No personal information is stored on servers operated by the Developer.
  • User-requested actions are processed locally whenever technically practical.

Some Apps may require internet access, location information, device permissions, third-party services, or protected operating-system capabilities to perform specific functions.

When such access is required, the App will request the relevant permission through the mechanisms provided by Android, iOS, Google Play, the Apple App Store, or the applicable operating system and distribution platform.

The relevant permission, purpose, and data use will be disclosed when required by applicable law or platform policy.

2. Information We Generally Do Not Collect

Unless an App clearly states otherwise in an app-specific disclosure, the Apps do not intentionally collect or transmit to the Developer:

  • Names, postal addresses, telephone numbers, or dates of birth.
  • Contact lists or address books.
  • SMS messages or call history.
  • Financial or payment-card information.
  • Government-issued identification numbers.
  • Passwords or authentication credentials.
  • Advertising identifiers.
  • IMEI, IMSI, SIM serial numbers, or other persistent device identifiers.
  • Installed-app inventories.
  • Browsing history.
  • Biometric, health, or fitness information.
  • Photos, videos, audio, documents, or other files, except when the user intentionally selects them for a specific App function.
  • Clipboard contents, except when accessed following a direct user action or when clearly required by a disclosed App feature.
  • Usage analytics, behavioral profiles, or advertising data.
  • Automatic crash reports transmitted to servers controlled by the Developer.

Some Apps may require access to location information, device sensors, files, media, camera, microphone, Bluetooth, nearby devices, local networks, notifications, accessibility services, or other protected device capabilities.

Access to a protected device capability does not necessarily mean that the related information is collected by or transmitted to the Developer.

Any App that processes information differently from the general practices described in this Policy will provide an app-specific disclosure explaining the relevant data categories, purposes, processing, transmission, sharing, and retention practices.

3. Local and Feature-Based Processing

User-entered information, URLs, settings, selected files, generated results, location information, and other feature-related data are normally processed locally on the user’s device whenever technically practical.

An App may temporarily access information that the user intentionally provides or authorizes, including:

  • A URL pasted into or shared with the App.
  • Text shared through the operating system’s Share function.
  • A file, photo, video, audio recording, document, or folder selected by the user.
  • A destination selected for saving or exporting a file.
  • Approximate or precise location when required by a location-based feature.
  • Camera or microphone input required for a specific function.
  • Device-sensor information required for a specific function.
  • Bluetooth or nearby-device information required for communication with supported equipment.
  • Local-network information required to discover or communicate with supported devices.
  • Settings and preferences selected within the App.
  • Information required to complete an operation specifically requested by the user.

This information is used only for the disclosed feature or user-requested action.

Unless an App specifically states otherwise, the Developer does not receive this information, and the App does not upload it to servers operated by the Developer.

Some features may require information to be transmitted directly from the user’s device to a third-party service selected by the user or technically required to provide the feature. When this occurs, the relevant App will provide an appropriate disclosure explaining the nature and purpose of the transmission.

Temporary information may remain in device memory while an operation is being performed. Local preferences, cached information, downloaded content, generated results, location records, or history may remain on the device until the user deletes the relevant information, clears the App’s data, or uninstalls the App.

Uninstalling an App may not delete files saved outside the App’s private storage. Users are responsible for deleting downloaded or exported files stored in shared, removable, cloud-synchronized, or externally managed storage.

4. Internet Access and Direct Connections

Some Apps require internet access to perform their core functionality.

For example, an App may connect directly from the user’s device to a website or external service in order to:

  • Retrieve publicly available information.
  • Analyze a user-provided URL.
  • Download user-requested content.
  • Resolve redirects.
  • Verify whether a website, device, or content type is supported.
  • Retrieve maps, navigation information, weather data, or location-based results.
  • Check for application updates.
  • Open an external webpage.
  • Send feedback using the user’s email application.
  • Open a voluntary support or donation page.
  • Communicate with an external service required for a feature requested by the user.

Unless an App states otherwise, these network requests are initiated directly from the user’s device and are not routed through servers operated by the Developer.

When an App connects to an external website or service, that third party may automatically receive standard network information such as:

  • The user’s IP address.
  • Request date and time.
  • Requested URL or resource.
  • Browser or application user-agent information.
  • Device or operating-system information included in standard network requests.
  • Cookies or identifiers previously created by that third party.
  • Approximate location derived from the IP address.
  • Other technical information required to establish or maintain the connection.

The collection and use of that information are controlled by the relevant third party, not by the Developer.

Users should review the privacy policy and terms of every external website or service they choose to access through an App.

5. Permissions and Protected Device Capabilities

Depending on its functionality, an App may request access to one or more protected device capabilities.

These may include:

  • Approximate location.
  • Precise location.
  • Foreground location.
  • Background location.
  • Camera.
  • Microphone.
  • Photos, videos, audio, documents, files, or folders.
  • Bluetooth.
  • Nearby devices.
  • Local-network access.
  • Notifications.
  • Device sensors.
  • Calendar information.
  • Contacts.
  • Biometric authentication provided by the operating system.
  • Foreground services.
  • Clipboard access.
  • Accessibility services.
  • Battery optimization exceptions.
  • Display-over-other-apps permission.
  • Usage access.
  • All-files access, where permitted and essential.
  • Other permissions required for a specific and disclosed App feature.

The inclusion of a permission in this Policy does not mean that every App requests or uses that permission.

Each App will request only the permissions reasonably necessary for its functionality.

Permissions will be requested through the mechanisms provided by the applicable operating system and in accordance with applicable Android, Google Play, iOS, Apple App Store, and other platform requirements.

Where required or appropriate, the App will provide a clear explanation before requesting a sensitive or restricted permission. The explanation may describe:

  • Which permission or device capability is being requested.
  • Why the App needs access.
  • Which feature requires it.
  • Whether the information is processed locally.
  • Whether the information is transmitted externally.
  • Whether access occurs only while the App is in use.
  • Whether access may continue in the background.
  • Whether the information is retained.
  • Whether the information is shared with a third party.

Granting a permission does not authorize the App to use the related information for an unrelated or undisclosed purpose.

Permission approval also does not necessarily mean that information is transmitted to the Developer.

6. Location Information

Some Apps may request approximate or precise location when location is necessary for a user-requested or clearly disclosed feature.

Examples may include:

  • Displaying information relevant to the user’s current area.
  • Recording the location of an event, item, measurement, inspection, or user-created record.
  • Providing navigation, mapping, geographic, field-service, or nearby-device functionality.
  • Applying regional settings or location-based calculations.
  • Finding supported devices or services near the user.
  • Supporting a location-based feature that the user has explicitly enabled.

Where supported by the operating system, users may be able to provide approximate location instead of precise location.

An App will not request background location unless it is reasonably necessary for a core and clearly disclosed function.

When background location is required, it will be requested separately or through the process required by the operating system and applicable app-store policies.

Unless an app-specific disclosure states otherwise:

  • Location information is processed locally.
  • Location information is not transmitted to servers operated by the Developer.
  • Location information is not used for advertising.
  • Location information is not sold or rented.
  • Location information is not used to create a behavioral profile.

An App may transmit location information directly to a third-party mapping, navigation, weather, geographic, emergency, device-discovery, or other location-dependent service when necessary to provide a feature requested by the user.

Such processing will be disclosed within the App, this Policy, an app-specific notice, or the applicable app-store privacy declaration.

7. Special, Sensitive, and Restricted Permissions

Certain operating-system permissions may be classified as sensitive, restricted, special, high-risk, or subject to additional platform review.

Examples may include:

  • Background location.
  • Accessibility services.
  • All-files access.
  • Call or SMS permissions.
  • Usage access.
  • Display-over-other-apps permission.
  • Device administration.
  • Notification-listener access.
  • VPN service access.
  • Exact alarm permission.
  • Bluetooth and nearby-device permissions.
  • Health or biometric permissions.
  • Other restricted operating-system capabilities.

When an App requires such a permission, the Developer will seek to:

  • Limit access to the minimum scope reasonably necessary.
  • Use the permission only for its disclosed purpose.
  • Request the permission only when the relevant feature is used.
  • Provide any disclosure, demonstration, justification, or declaration required by the operating system or distribution platform.
  • Avoid using the permission for advertising, profiling, surveillance, or unrelated purposes.
  • Remove or reduce access when the feature no longer requires it, where technically possible.
  • Maintain app-store declarations that accurately reflect the App’s actual behavior.
  • Follow the applicable permission policies of Android, Google Play, iOS, and the Apple App Store.

A permission granted for one feature will not be treated as authorization for an unrelated feature.

The Developer will not intentionally attempt to bypass, defeat, obscure, or secretly circumvent an operating-system permission decision.

8. User Control Over Permissions

Users may deny a permission request or revoke a previously granted permission through their device settings.

Depending on the operating system and permission, users may also be able to:

  • Allow access only while using the App.
  • Allow access only once.
  • Provide approximate rather than precise location.
  • Select only particular photos, videos, files, or folders.
  • Disable notifications.
  • Prevent background access.
  • Disable camera or microphone access.
  • Disable Bluetooth or nearby-device access.
  • Disable local-network access.
  • Disable location services.
  • Remove accessibility or other special access.
  • Reset permissions automatically when an App is unused.

Denying or revoking a permission may prevent the associated feature from operating correctly.

The App should continue to provide unrelated functionality whenever reasonably possible.

Revoking a permission prevents future access but may not automatically delete information previously saved locally by the user or generated through the permitted feature.

9. Downloaded and User-Selected Content

The Developer does not monitor, inspect, approve, control, or retain copies of content downloaded, processed, created, selected, converted, or stored by users.

Downloaded or generated content remains under the user’s control on the user’s device or selected storage location.

Users are solely responsible for:

  • The URLs they submit.
  • The files they select.
  • The content they access or download.
  • The devices or services with which they connect.
  • Ensuring that they have permission to access, download, copy, convert, store, modify, distribute, or otherwise use content.
  • Complying with copyright, trademark, privacy, publicity, contractual, licensing, and other applicable rights.
  • Complying with the terms and policies of third-party websites and services.
  • Avoiding illegal, abusive, harmful, deceptive, or unauthorized activity.
  • Protecting downloaded files.
  • Checking downloaded files for malicious or unsafe content.
  • Backing up important information.

The Apps are provided as general-purpose tools.

They are not intended to encourage:

  • Copyright infringement.
  • Unauthorized access.
  • Circumvention of digital rights management.
  • Bypassing paywalls.
  • Evasion of authentication requirements.
  • Unauthorized monitoring or surveillance.
  • Violation of privacy rights.
  • Violation of any law or third-party agreement.

The availability of a technical function does not grant the user any legal right to access, download, modify, or distribute third-party content.

10. Third-Party Websites and Services

The Apps may interact with or provide links to third-party websites, applications, content platforms, map providers, cloud services, device manufacturers, app stores, email providers, payment processors, donation platforms, or other services.

These services are independent of the Developer.

We do not control and are not responsible for:

  • Their privacy practices.
  • Their security practices.
  • Their data-retention practices.
  • Their cookies or tracking technologies.
  • Their content or availability.
  • Their terms of service.
  • Changes made to their websites, software, services, or APIs.
  • Information they collect directly from users or devices.
  • Actions they take against a user account.
  • Compatibility changes.
  • Losses caused by relying on their services.
  • Errors, interruptions, or security incidents affecting their systems.

A link, integration, reference, or compatibility with a third-party service does not imply sponsorship, endorsement, affiliation, authorization, certification, or partnership.

Third-party brand names, service names, logos, and trademarks belong to their respective owners.

11. Third-Party Libraries and System Components

Apps may rely on:

  • Open-source libraries.
  • Operating-system components.
  • Google Play services.
  • Apple system frameworks.
  • Mapping or navigation providers.
  • Bluetooth or device-communication libraries.
  • Cloud-storage providers.
  • App-store services.
  • Payment or donation providers.
  • Other technical components required for functionality.

A feature involving location, camera, microphone, files, Bluetooth, nearby devices, notifications, authentication, payments, maps, cloud storage, or another protected capability may involve processing by:

  • The device operating system.
  • Google Play services.
  • Apple system services.
  • A device manufacturer.
  • A mapping or navigation provider.
  • A cloud-storage provider.
  • An email provider.
  • A payment or donation platform.
  • Another service intentionally selected by the user.

These services may process technical or personal information independently under their own privacy policies and terms.

The Developer seeks to avoid components that collect personal information unnecessarily.

However, third-party components may change over time or behave differently depending on:

  • Their configuration.
  • The operating-system version.
  • The device manufacturer.
  • The distribution channel.
  • The user’s system settings.
  • Updates released by the third-party provider.

When a third-party component processes information outside the user’s device, that behavior will be disclosed through one or more of the following, as applicable:

  • This Privacy Policy.
  • An app-specific privacy notice.
  • An in-app permission disclosure.
  • The Google Play Data Safety section.
  • Apple App Privacy disclosures.
  • The app-store listing.
  • A consent or configuration screen.

The Developer will make reasonable efforts to ensure that app-store privacy declarations remain consistent with the App’s actual behavior and included third-party components.

12. Advertising and Analytics

Our Apps are intended to remain free from third-party advertising.

Unless an App provides a separate and prominent disclosure:

  • We do not display behavioral or targeted advertisements.
  • We do not use advertising identifiers.
  • We do not integrate advertising SDKs.
  • We do not use third-party analytics SDKs.
  • We do not track users across applications or websites.
  • We do not sell or share personal information for advertising purposes.
  • We do not create advertising profiles.

An App may include an optional link that allows users to support its development voluntarily.

Opening such a link may take the user to a third-party donation, payment, subscription, crowdfunding, or support platform.

Any information provided to that platform is processed according to that platform’s own privacy policy and terms.

The Developer does not receive payment-card details when payment is processed entirely by a third-party provider.

13. Feedback and Support Communications

Users may voluntarily contact the Developer at:

misterj.dev@gmail.com

When a user sends an email or other support communication, the Developer may receive:

  • The sender’s email address.
  • The sender’s name, if included in the email account.
  • The contents of the message.
  • Attachments voluntarily provided by the sender.
  • Screenshots voluntarily provided by the sender.
  • Technical details voluntarily included in a bug report.
  • Device or operating-system information voluntarily included in the message.
  • Information automatically added by the user’s email provider.

This information is provided voluntarily and is used only to:

  • Respond to the inquiry.
  • Investigate a reported problem.
  • Consider a feature request.
  • Consider a request for support for a new website, service, device, or platform.
  • Protect the Apps and Developer from fraud, abuse, or security threats.
  • Maintain a reasonable record of support communications.
  • Comply with applicable legal obligations.

Users should not send:

  • Passwords.
  • Payment-card information.
  • Government identification numbers.
  • Authentication tokens.
  • Private keys.
  • Confidential third-party information.
  • Unnecessary sensitive personal information.

Support communications may be stored by the Developer’s email provider and are subject to that provider’s privacy practices.

Support emails are retained only as long as reasonably necessary for support, security, documentation, dispute resolution, or legal purposes.

A user may request deletion of a support communication by contacting the email address above, subject to any legal, fraud-prevention, or security-related retention requirement.

14. App Stores and Distribution Platforms

Apps may be distributed through:

  • Google Play.
  • The Apple App Store.
  • Another app store.
  • A code repository.
  • A software-distribution website.
  • A third-party distribution platform.

Those platforms may independently collect information relating to:

  • App downloads and installations.
  • App updates and removals.
  • Device compatibility.
  • App purchases or voluntary contributions.
  • Ratings and reviews.
  • Store interactions.
  • Crash or performance diagnostics.
  • Country, language, and general usage statistics.
  • Account and payment information maintained by the platform.
  • Subscription status.
  • Fraud-prevention information.

This information is collected and controlled by the distribution platform under its own privacy policy.

The Developer may receive reviews, support messages, transaction confirmations, aggregated statistics, or diagnostic reports made available by the platform.

We do not control the platform’s independent collection, processing, or retention practices.

15. Data Sharing and Sale

The Developer does not sell, rent, license, broker, or trade personal information.

Because the Developer does not generally maintain user accounts or a central user-data database, we normally have no App-user data to share.

Information may be disclosed only when:

  • The user intentionally sends it to the Developer.
  • The user directs the App to communicate with a third-party service.
  • Disclosure is reasonably necessary to respond to the user’s request.
  • Disclosure is required by valid law, court order, subpoena, or governmental process.
  • Disclosure is necessary to investigate fraud, abuse, a security incident, or a threat to the rights or safety of users, the Developer, or others.
  • Disclosure is necessary to establish, exercise, or defend legal claims.
  • The user has provided valid consent.

We will not voluntarily disclose information that we do not possess.

16. Data Retention and Deletion

The Developer does not generally maintain a remote database containing App users’ personal information.

Information stored locally by an App may include:

  • Settings.
  • Preferences.
  • Location records.
  • Selected files.
  • Downloaded content.
  • Cached information.
  • Generated results.
  • Connection history.
  • User-created records.
  • App configuration.

This information may generally be deleted by:

  • Using deletion controls available within the App.
  • Clearing the App’s cache.
  • Clearing the App’s storage or data.
  • Deleting files through the device’s file manager.
  • Removing records from the relevant operating-system service.
  • Revoking permissions.
  • Uninstalling the App.

Revoking a permission prevents future access but may not automatically delete information previously stored locally.

Files saved to shared, external, removable, or cloud-synchronized storage may remain after the App is uninstalled and must be deleted separately by the user.

When an App transmits information to a third-party service at the user’s request, retention and deletion may also be governed by that third party’s privacy policy and user controls.

For information voluntarily sent through email or another support channel, users may request deletion by contacting:

misterj.dev@gmail.com

We may retain limited support communications when reasonably necessary for:

  • Security.
  • Fraud prevention.
  • Legal compliance.
  • Dispute resolution.
  • Documentation.
  • Establishing, exercising, or defending legal claims.

17. Data Security

We apply reasonable administrative and technical measures appropriate to the limited information we process.

However, no application, device, internet transmission, wireless connection, storage system, email provider, app store, or third-party service can be guaranteed to be completely secure.

Users are responsible for:

  • Maintaining the security of their devices.
  • Installing operating-system and security updates.
  • Using trusted networks.
  • Protecting access to downloaded files.
  • Protecting access to connected devices.
  • Reviewing permissions granted to the Apps.
  • Avoiding suspicious links and malicious content.
  • Backing up important files.
  • Using device encryption and screen-lock protection where appropriate.

Information stored locally is subject to the security protections and limitations of the user’s device and operating system.

The Developer cannot guarantee the security of:

  • Third-party websites.
  • External networks.
  • Cloud-storage providers.
  • Email systems.
  • Mapping services.
  • Connected hardware.
  • Files obtained from third parties.
  • Services accessed or selected by the user.

18. Children’s Privacy

The Apps are general-purpose utilities and are not directed specifically to children under 13 or the minimum age required by applicable local law.

The Developer does not knowingly collect personal information from children through the Apps.

Parents or legal guardians who believe that a child has voluntarily sent personal information to the Developer may contact:

misterj.dev@gmail.com

The parent or guardian may request deletion of that information, subject to any applicable legal or security-related retention requirement.

Users who are not legally old enough to agree to this Policy should use the Apps only with the involvement and permission of a parent or legal guardian.

19. User Responsibility and Lawful Use

Users must use the Apps only for lawful and authorized purposes.

The user is solely responsible for determining whether a particular action is lawful and authorized:

  • In the user’s jurisdiction.
  • Under the terms of a third-party service.
  • Under any applicable license.
  • Under any applicable contract.
  • Under the rights of a content owner.
  • Under the policies of an employer, school, institution, or device owner.

The Developer does not provide legal advice and does not determine whether a user has permission to access, download, process, modify, monitor, communicate with, or distribute particular content, systems, devices, or information.

The Developer is not responsible for misuse of an App, including:

  • Copyright infringement.
  • Trademark infringement.
  • Privacy or publicity-right violations.
  • Unauthorized access.
  • Unauthorized monitoring.
  • Breach of contract.
  • Violation of website or service terms.
  • Account suspension or termination.
  • Loss or corruption of files or data.
  • Device damage caused by third-party content.
  • Distribution of unlawful or harmful material.
  • Actions performed without necessary rights or authorization.
  • Improper use of location or device information.
  • Use of an App in a dangerous, unlawful, or prohibited environment.

Users must stop using an App if its use would violate:

  • Applicable law.
  • A court order.
  • A third party’s rights.
  • A binding agreement.
  • An app-store policy.
  • An employer or institution policy.
  • A device-owner restriction.

20. Disclaimer of Warranties

To the fullest extent permitted by applicable law, the Apps are provided on an “as is” and “as available” basis without warranties of any kind, whether express, implied, or statutory.

The Developer does not warrant that:

  • An App will always be available.
  • An App will always be accurate.
  • An App will be compatible with every device.
  • An App will be uninterrupted or error-free.
  • Every website, service, device, or content type will remain supported.
  • A third-party website or service will continue to permit access.
  • Downloaded content will be safe, complete, lawful, accurate, or free from malicious code.
  • Location information will always be accurate.
  • Sensor or device information will always be accurate.
  • An App will meet every user’s requirements.
  • Errors or compatibility issues will always be corrected.
  • Third-party services will remain unchanged or available.

Nothing in this Policy excludes warranties or consumer rights that cannot legally be excluded under applicable law.

21. Limitation of Liability

To the fullest extent permitted by applicable law, the Developer will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages arising from or related to:

  • Use or inability to use an App.
  • User misuse of an App.
  • Content accessed, processed, or downloaded by a user.
  • Loss, corruption, disclosure, or deletion of files.
  • Incorrect location, mapping, sensor, or device information.
  • Third-party websites, applications, services, devices, or content.
  • Changes to a third-party website, API, device, service, or operating system.
  • Account restrictions, suspensions, or terminations.
  • Intellectual-property or privacy claims caused by user conduct.
  • Malware or unsafe content obtained from a third party.
  • Unauthorized access to a user’s device.
  • Decisions made based on an App’s output.
  • Loss caused by relying on an App in a critical, emergency, medical, safety, financial, legal, or operational context.

The Apps are not intended to replace professional, legal, medical, financial, emergency, engineering, navigation, safety, or regulatory advice unless an App expressly states otherwise.

This limitation applies only to the extent permitted by applicable law and does not exclude liability that cannot legally be limited.

22. Legal Requests

The Developer may respond to valid legal requests when required by applicable law.

Because the Developer does not generally operate a user-account system or central user-data database, we may be unable to identify a particular user or produce information that was never collected.

We may preserve information already in our possession when legally required to do so.

We may challenge requests that we reasonably believe are invalid, excessive, unlawful, or inconsistent with applicable rights.

23. International Users and Privacy Rights

Privacy rights vary by jurisdiction.

Depending on applicable law, users may have rights concerning:

  • Access.
  • Correction.
  • Deletion.
  • Restriction.
  • Objection.
  • Portability.
  • Withdrawal of consent.
  • Complaints to a data-protection authority.

Because the Developer generally does not collect or store App-user information on external servers, there may be no remotely stored personal information to access, correct, export, or delete.

Requests concerning voluntarily submitted support communications may be sent to:

misterj.dev@gmail.com

We may request reasonable information to verify that the requester is the person associated with the relevant communication.

Verification information will be used only to process the request.

Users may also have the right to contact the privacy or data-protection authority applicable to their location.

24. Changes to App Functionality and Permissions

Future versions of an App may add, remove, or modify features, permissions, integrations, or supported services.

Before introducing a feature that materially changes how personal information, location information, or a protected device capability is accessed, collected, used, stored, transmitted, or shared, the Developer will update the relevant disclosures and obtain any permission or consent required by:

  • Applicable law.
  • Android requirements.
  • Google Play policies.
  • iOS requirements.
  • Apple App Store policies.
  • Other applicable operating-system or distribution-platform rules.

Updates may include changes to:

  • This Privacy Policy.
  • An app-specific privacy notice.
  • In-app permission explanations.
  • Google Play Data Safety declarations.
  • Apple App Privacy disclosures.
  • App-store listing information.
  • Permission purpose descriptions.
  • Consent or preference controls.

A new permission will not be treated as authorization for an unrelated purpose merely because the user installs an App update.

Where applicable law or platform requirements require a new permission, disclosure, or affirmative consent, the App will request it before activating the relevant functionality.

25. Changes to This Privacy Policy

We may update this Privacy Policy to reflect:

  • Changes to an App.
  • Changes to permissions.
  • Changes to legal or regulatory requirements.
  • Changes to app-store policies.
  • Changes to third-party services.
  • Changes to operating-system requirements.
  • Security or privacy improvements.
  • Corrections or clarifications.

The updated version will be posted at the same public location and will display a revised “Last Updated” date.

Material changes may also be communicated:

  • Within the App.
  • Through the App’s store listing.
  • Through an app-specific notice.
  • Through a permission or consent screen.

Continued use of an App after a non-material update means that the updated Policy applies to future use.

Where applicable law requires affirmative consent, continued use alone will not be treated as consent.

26. App-Specific Disclosures

An App may display an additional privacy notice describing a feature, permission, third-party service, data category, or processing practice unique to that App.

An app-specific notice supplements this Privacy Policy.

When an app-specific notice conflicts with this general Policy regarding that App’s actual data practices, the more specific disclosure will control.

Users should review both this general Privacy Policy and any app-specific disclosures presented within the App or its store listing.

27. Severability

If any provision of this Privacy Policy is found to be unlawful, invalid, or unenforceable, that provision will be interpreted, modified, or limited to the minimum extent necessary.

The remaining provisions will remain in effect to the fullest extent permitted by law.

28. No Waiver

A failure by the Developer to enforce any provision of this Policy does not constitute a waiver of that provision or any other right.

29. Contact Information

Questions, privacy inquiries, deletion requests, feedback, and support requests may be submitted to:

Developer: MisterJ Dev Privacy Contact: misterj.dev@gmail.com

Please include:

  • The name of the App concerned.
  • A description of the request.
  • Enough information for us to understand and respond to the request.

Do not include passwords, payment information, identification numbers, authentication tokens, private keys, or other unnecessary sensitive information in your message.

30. Important Notice

This Privacy Policy describes privacy and data-handling practices.

It does not grant permission to use third-party content and does not replace any separate:

  • Terms of Use.
  • End-User License Agreement.
  • Open-source license.
  • App-store agreement.
  • Hardware-manufacturer agreement.
  • Third-party website terms.
  • Service-provider terms.
  • Applicable law or regulation.

Users remain responsible for reviewing and complying with all terms, licenses, laws, permissions, and restrictions applicable to their use of an App.