Privacy Policy

1. Core App Use and Local Data

The app does not require an account, login, registration, subscription account, or cloud account operated by Naladimarth.

Core features such as the Preview Box, Hue Wheel, Shade control, Strobe, Auto Color, Brightness control, Pixel Check, White, Full Screen, Fluid Colors, and Lock are designed to operate locally on your device.

You do not need to provide your name, email address, phone number, contacts, photos, files, camera content, microphone recordings, or precise location in order to use the app's core features.

Certain preferences and choices may be stored locally on your device so the app can remember them between sessions. These may include app settings, brightness-related preferences, first-use or guide state, safety acknowledgements, and your optional Usage Analytics choice.

Naladimarth does not operate a user-account database or a cloud-storage backend for the app's core functionality.

Network access is used by third-party services described in this Policy, including Firebase Crashlytics, optional Google Analytics for Firebase, Google AdMob, Google User Messaging Platform (UMP), external links, and email functionality.

2. Crash Reporting and Diagnostics

The app uses Firebase Crashlytics, provided by Google, to help identify crashes and serious technical failures, improve app stability, and diagnose compatibility problems.

Firebase Crashlytics may automatically process technical and diagnostic information associated with a crash or error, including:

• Crash stack traces and exception information
• Relevant application state at the time of a crash
• App package, version, and build information
• Android operating-system information
• Device model, CPU architecture, memory, and storage information
• Foreground/background state and crash timestamps
• Crashlytics installation identifiers
• Firebase installation and session identifiers used by Firebase services

The app does not set a user account identifier in Crashlytics and does not intentionally attach your name, email address, phone number, contacts, files, Advertising ID, or user-entered support text to Crashlytics reports.

Crash and diagnostic information is handled under Google's Firebase terms, security measures, and retention practices.

3. Optional Usage Analytics

The app includes Google Analytics for Firebase to help Naladimarth understand aggregate feature usage and improve the app.

When Usage Analytics is enabled, Google Analytics for Firebase may process standard automatically collected Analytics information such as app/session engagement, app and operating-system information, device characteristics, approximate geographic information, automatically collected events/properties, and app-installation or Analytics identifiers.

The app also sends a limited set of custom event categories when Analytics is enabled. These indicate which type of control, mode, guide, menu item, or feedback action was used. Examples include:

• Control categories such as Hue Wheel, Shade, Brightness, Strobe speed, and Auto Color speed
• Mode categories such as Full Screen, White, Fluid Colors, Lock, Pixel Check, Strobe, and Auto Color
• Quick Guide and How to Use actions such as opened, completed, or skipped
• Menu categories such as Report a bug, Request a feature, Rate us, More apps, Privacy Policy, Terms, and About
• Feedback-flow categories such as disclosure shown, accepted, cancelled, email composer opened, or composer failed

The app's custom Analytics implementation is designed not to send:

• Your name, email address, or phone number
• User-entered free text
• Device serial numbers
• Raw advertising-consent strings
• Exact RGB, hue, brightness, strobe-speed, or Auto Color values from normal control interactions
• Files, photos, contacts, camera content, microphone recordings, or precise GPS location

Firebase Analytics Advertising ID collection is disabled in the app's Android Analytics configuration.

Analytics ad-personalisation signals are also disabled by default in the app's Analytics configuration.

You can turn Usage Analytics off again at any time from Improve Experience. Turning it off stops future Analytics collection by the app on that installation. It does not necessarily erase information that was already processed or aggregated before the setting was disabled.

4. Advertising – Google AdMob

The app uses the Google Mobile Ads SDK (AdMob) to support advertising.

The app is designed to show at most one anchored adaptive banner on the normal Home control screen when the Home screen is eligible to display an ad.

The banner is designed not to appear in functional clean-display modes or modal/privacy flows, including:

• Pixel Check
• White
• Full Screen colour display
• Fluid Colors
• Strobe mode
• Locked clean-display mode
• Quick Guide and How to Use
• Feedback flows
• Improve Experience / Usage Analytics settings
• UMP consent or Ad privacy choices screens

According to Google, the Google Mobile Ads SDK may automatically collect and share certain technical information for advertising or marketing, analytics, and fraud prevention, security, and compliance purposes. Depending on the device, region, privacy choices, and applicable law, this can include:

• IP address, which may be used to estimate the device's general location
• User and ad interaction information such as app launches, ad views, taps, and related product interactions
• Diagnostic and performance information such as app/SDK performance, launch time, hangs, or energy use
• Device or app identifiers, which may include the Android Advertising ID, App Set ID, or other permitted identifiers

The app does not request precise GPS location for advertising. General location may still be inferred by Google from information such as an IP address.

Ads may be personalised, non-personalised, restricted, or limited depending on applicable law, your privacy choices, device settings, Google's advertising systems, and the configuration of the advertising services.

Android users can reset or delete the Advertising ID through supported Android privacy controls. Availability and behaviour depend on the Android version and device.

5. Advertising Consent and Privacy Choices

The app uses Google's User Messaging Platform (UMP) and Google Privacy & messaging to manage advertising-related consent and privacy choices where applicable.

The app requests updated consent/privacy information after startup so it can determine whether an advertising message is required and whether Google allows an ad request.

European regulations

For eligible users in the European Economic Area (EEA), United Kingdom, and Switzerland, Google's European-regulations message may be used to provide required disclosures and collect advertising-related consent.

Depending on the published message configuration and applicable law, users may be offered choices such as consenting, declining consent, or managing detailed purposes and advertising partners.

When UMP indicates that consent is required before advertising can be requested, the app is designed not to request an ad until UMP indicates that ad requests are permitted.

Google's European message may store and communicate consent choices using industry consent signals such as the IAB Transparency and Consent Framework (TCF), as applicable.

U.S. state privacy messages

For eligible users in U.S. states with applicable privacy laws, Google's U.S. state regulations message may provide privacy choices relating to the sale or sharing of personal information and targeted advertising, as those terms are defined by applicable law.

Where available, the Google message may provide a Do Not Sell or Share My Personal Information choice. Selecting an opt-out communicates that choice to Google and may limit advertising data processing according to Google's U.S. state privacy configuration and applicable law.

Google states that its U.S. state regulations messaging can use the IAB Global Privacy Platform (GPP) to store and transmit applicable privacy choices.

Google also states that, for users in certain applicable U.S. states, it may receive recognized Global Privacy Control (GPC) signals and apply Restricted Data Processing to relevant ad requests.

Changing advertising privacy choices

When Google UMP indicates that a privacy-options entry point is required, the app displays Ad privacy choices in its settings/menu so you can reopen the relevant Google privacy form and review or change available advertising choices.

Advertising choices handled through UMP remain separate from the optional Usage Analytics setting described in Section 3.

6. Information for the EEA, United Kingdom, and Switzerland

Where European data-protection law applies and Naladimarth determines the purposes and means of a processing activity, Naladimarth is responsible for that processing. Google's role may differ depending on the Google service, purpose, and applicable contractual terms.

Purposes and legal bases

Depending on the processing activity and applicable law, the relevant legal bases may include:

• Consent — for optional Usage Analytics and for advertising-related storage, personalisation, or processing where consent is required and obtained
• Legitimate interests — where permitted, for app stability, crash diagnostics, security, fraud prevention, compatibility, troubleshooting, and improving reliability
• Steps taken at your request / legitimate interests — when you choose to contact Naladimarth for support, report a bug, or request a feature
• Legal obligations — where processing is necessary to comply with applicable law or lawful requests

For Google advertising and consent processing, the European message displays the relevant purposes, partners, choices, and available legal bases according to Google's Privacy & messaging configuration.

Your rights

Subject to applicable law and exceptions, you may have rights to request access, correction, deletion, restriction, objection, or data portability, and to withdraw consent where processing is based on consent.

Withdrawing consent does not affect the lawfulness of processing that occurred before withdrawal.

You may also have the right to complain to the data-protection or supervisory authority in the country where you live, work, or believe a violation occurred.

Naladimarth does not use personal information collected directly by this app to make automated decisions that produce legal or similarly significant effects on users. Third-party advertising systems may use automated processing for ad selection or personalisation, subject to applicable privacy choices and their own policies.

7. U.S. State Privacy Information

This section is intended to provide additional transparency for residents of U.S. states with applicable comprehensive privacy laws, including California where applicable. The exact rights and legal definitions depend on the state and whether the law applies to the particular processing activity.

Categories of information

Depending on which services are used and your privacy choices, the app and its service providers may process categories such as:

• Identifiers — IP address, Advertising ID where available/permitted, App Set ID, Firebase installation identifiers, Crashlytics installation identifiers, and other app/service identifiers
• Internet or electronic activity — app/session activity, feature interactions when optional Analytics is enabled, ad views/taps, and related product interactions
• Approximate geolocation — general location inferred from an IP address by services such as advertising or Analytics; the app does not request precise GPS location
• Diagnostics and device information — crash data, performance data, app version, Android version, model, manufacturer, and other technical information
• Contact information and communications — only when you voluntarily send Naladimarth a support or feedback email

The app does not intentionally collect sensitive personal information such as government identification numbers, financial account credentials, health records, biometric identifiers, precise GPS location, or the contents of private files as part of its core operation.

Sources and purposes

Technical information is generally obtained from the device, app, Firebase SDKs, Google Mobile Ads SDK, UMP, or your interactions with those services. Support information is obtained from you when you choose to send an email.

The purposes include providing and maintaining app functionality, diagnosing crashes, security and fraud prevention, measuring optional usage, serving and measuring advertising, complying with privacy choices, and responding to support requests.

Disclosure and advertising

Advertising-related information described in Section 4, including approximate location inferred from an IP address, app interactions, diagnostic information, and device or other identifiers, may be collected and shared by Google Mobile Ads for advertising or marketing, analytics, and fraud prevention, security, and compliance purposes.

Crash logs are processed separately through Firebase Crashlytics for crash reporting, diagnostics, stability, and troubleshooting. Naladimarth does not intentionally use Crashlytics crash logs for advertising or targeted-advertising purposes.

Naladimarth does not sell personal information for monetary payment. However, disclosures of identifiers or activity information for interest-based or targeted advertising may be treated as a “sale,” “sharing,” or “targeted advertising” under certain U.S. state laws even when no money is exchanged for the information.

Where applicable, you can use the Google Do Not Sell or Share My Personal Information / Ad privacy choices described in Section 5 to submit an advertising opt-out choice.

State privacy rights

Depending on your state and applicable law, you may have rights to request access or confirmation, correction, deletion, a portable copy of certain information, or to opt out of sale, sharing, targeted advertising, or certain profiling. Some states also provide a right to appeal a denied request and a right not to receive unlawful discriminatory treatment for exercising privacy rights.

Because the app has no Naladimarth user account and much of the technical data is processed by Google using pseudonymous installation or advertising identifiers, Naladimarth may not always be able to identify or retrieve Google-managed information for a particular device from a general email request. Google and Android privacy controls may therefore be relevant for some requests.

To make a privacy request concerning information Naladimarth controls directly, email support@naladimarth.com .

8. Feedback – Report a Bug and Request a Feature

The app provides Report a bug and Request a feature actions using your device's email application.

Naladimarth does not use a separate feedback backend for these actions.

Before reading optional device details for a feedback email, the app asks whether you want to continue and include those details.

If you choose to continue, the app automatically prepares only the following app/device metadata:

• App name
• App version
• App build number
• Android version
• Device manufacturer
• Device model
• Device locale

The app does not automatically add:

• Android Advertising ID
• Device serial number
• Files or photos
• Contacts
• Location
• Crash logs
• Other user content

The email is opened in your email application for review. You decide whether to send it and can edit or remove its contents before sending.

If you send an email to Naladimarth, your email address, message, and any information you voluntarily add are transmitted through your email provider and received by Naladimarth for support or feedback purposes. Please avoid including sensitive information that is not necessary for your request.

9. Data Retention and Deletion

Local app preferences generally remain on your device until they are changed, app data is cleared, or the app is removed, subject to Android backup and restore behaviour.

Naladimarth does not maintain a server-side user profile for the app's core functionality.

Google states that Firebase Crashlytics keeps crash stack traces and associated Crashlytics/Firebase installation identifiers for approximately 90 days before beginning removal from live and backup systems. Google's retention practices may be updated over time.

Firebase Analytics information, when you have enabled Usage Analytics, is retained according to the applicable Google/Firebase Analytics property settings, product configuration, policies, and legal requirements.

Advertising and consent information processed by Google AdMob and UMP is retained according to Google's applicable service settings, policies, consent records, and legal requirements.

Turning Usage Analytics off stops future Analytics collection by the app on that installation but does not necessarily delete information that was already processed or aggregated.

Where Ad privacy choices are available, you can use them to review or change applicable advertising choices. Android Advertising ID controls may also be used where supported.

Support emails may be retained for as long as reasonably necessary to answer the request, troubleshoot the reported issue, maintain basic support records, prevent abuse, or meet legal obligations.

You may contact Naladimarth to request deletion of support emails or other information that Naladimarth directly controls and can reasonably identify from your request. Contact support@naladimarth.com .

This request mechanism does not mean that Naladimarth can identify, retrieve, or directly delete all information processed by Google AdMob, UMP, Firebase Analytics, or Firebase Crashlytics. Some Google-managed information is associated with pseudonymous installation, advertising, or service identifiers and is subject to Google's own controls, retention practices, contractual terms, and applicable law.

10. Data Security

Naladimarth limits the amount of information handled directly by the app and does not maintain a user-account backend for the core product.

Google states that data handled by the Google Mobile Ads SDK is encrypted in transit using Transport Layer Security (TLS).

Firebase states that covered Firebase SDK data is encrypted in transit using HTTPS, and Firebase Crashlytics data is also protected using Google/Firebase security infrastructure.

No method of electronic transmission, processing, or storage can be guaranteed to be completely secure.

Emails you choose to send are also subject to the security and privacy practices of your email provider.

11. Permissions and Device Access

The app uses Android and device capabilities required for its screen-light, brightness, display-mode, keep-screen-awake, networking, and advertising functionality.

The app does not request runtime access to sensitive device content such as:

• Precise or background location
• Contacts
• Camera
• Microphone
• Photos, videos, or general file storage
• SMS messages
• Call logs

Internet/network access is used by Firebase, Google AdMob, UMP, external links, and email-related actions.

The Google Mobile Ads SDK may add Android's Advertising ID permission to the final app manifest so the advertising SDK can access the Android Advertising ID where it is available, legally permitted, and not restricted by device or privacy settings.

The Advertising ID permission is not a runtime permission that provides access to contacts, files, camera, microphone, or precise GPS location.

Firebase Analytics Advertising ID collection is separately disabled in the app's Analytics configuration. That Analytics setting does not prevent the Google Mobile Ads SDK from using the Advertising ID for advertising where allowed.

12. Children’s Privacy

The app's Google Play target audience is adults aged 18 and over. The app is not designed or marketed primarily for children and does not require users to create an account or directly provide a name, email address, phone number, contacts, files, or similar personal information to use the core features.

Third-party services used by the app may process technical, diagnostic, analytics, consent, or advertising information as described in this Policy.

Naladimarth does not knowingly ask children to submit sensitive personal information through the app. If you are a parent or guardian and believe a child has sent personal information directly to Naladimarth in a way that should not have occurred, please contact us so the request can be reviewed.

13. International Data Transfers

Google, Firebase, advertising partners, and other service providers may process information on servers located outside the country where you live. Your information may therefore be transferred to or processed in countries with different data-protection laws.

Google describes the legal and contractual safeguards it uses for international data transfers in its privacy, data-processing, and service terms.

If you choose to email Naladimarth from another country, your email may also be transmitted or stored across borders by your email provider and by the systems used to receive and answer the message.

14. Third-Party Services

The app uses services provided by Google. Their processing of information is governed by their own terms, policies, configurations, and applicable law.

When you open an external website, Google Play page, or email application from the app, that third party's privacy policy applies to the information it processes.

15. No User Account; Sale, Sharing, and Targeted Advertising

Naladimarth does not require a user account for this app and does not operate a separate advertising-profile database built from user-entered content.

Naladimarth does not sell files, photos, contacts, private messages, or other user content collected by the app, because the app does not collect such content as part of its core operation.

Naladimarth also does not sell personal information for monetary payment.

However, Google AdMob and eligible advertising partners may collect, disclose, or use advertising and technical information as described in Section 4. Under some U.S. privacy laws, certain advertising-related disclosures can legally be considered a “sale,” “sharing,” or “targeted advertising” even when no money is paid in exchange for the information.

Where those laws apply, use the available Ad privacy choices / Do Not Sell or Share My Personal Information mechanism described in Sections 5 and 7.

16. Changes to This Privacy Policy

This Privacy Policy may be updated when the app's functionality, third-party services, privacy controls, advertising configuration, legal requirements, or data practices change.

The last-updated date shown at the top of this page will be changed when a revision is published. Material changes may also be communicated through the app, store listing, website, or another appropriate method when required.

17. Contact and Privacy Requests

If you have a question about this Privacy Policy, the app's privacy practices, or a privacy request relating to information Naladimarth controls directly, contact:

Naladimarth

Email: support@naladimarth.com

For a privacy-rights request, including a request concerning support information that Naladimarth directly controls, you can use the subject Privacy Request – RGB Screen & Pixel Check to help route the message.

Naladimarth may not be able to identify, retrieve, correct, or delete Google-managed information associated only with pseudonymous device, installation, advertising, or service identifiers. Requests are handled subject to applicable law and the information Naladimarth can reasonably identify and control.