Privacy Policy

Flicker Meter by HighApps
Last updated: 15 September 2026

This policy describes how HighApps ("we") handles information in the Flicker Meter app for iOS (bundle identifier am.highapps.flickermeter). Flicker Meter measures LED and PWM light flicker frequency (Hz) and intensity (%) using the iPhone camera. It is free and supported by ads, with an optional Remove Ads in-app purchase.

We do not operate our own user database or login. We do not require an account, name, email, or phone number to use the app.

What the app does

• Captures high-speed camera frames (up to 240 fps on capable iPhones) and analyzes brightness over time to detect flicker frequency and intensity.
• Displays peak flicker frequency in Hz, flicker intensity as a percentage, and a confidence rating.
• Lets you optionally save a measurement locally with a title you type, then view or delete that history on the device.
• Shows AdMob ads on result and history screens when ads are allowed. An optional Remove Ads in-app purchase unlocks an ad-free experience.
• Uses Firebase Analytics and Firebase Crashlytics to understand usage and fix crashes.

Results are educational reference estimates only. The app is not a laboratory instrument or medical device and is not for legal, regulatory, compliance, or professional certification use.

Information we do not collect

Flicker Meter does not ask for, and the app does not read:

• Your name, email, phone number, or payment details (except Apple's in-app purchase for Remove Ads, which we do not see)
• Precise or approximate location
• Your photo library, microphone, files, or contacts
• Camera images or video. The camera is used to measure brightness and detect flicker — frames are analyzed in memory for luminance time-series, then immediately discarded. No photo or video is recorded, saved to your library, or uploaded anywhere.
• Account credentials (there is no sign-in)

We do not sell your personal information.

Data stored on your device

The following stays on the device unless you delete the app or your iCloud Backup includes it:

• Measurement history you choose to save: title, date, peak Hz, flicker intensity %, confidence rating. Titles are whatever you type (for example "Office LED — desk lamp"). We do not upload history to HighApps.
• App settings such as AE lock preference, white-balance lock preference, and whether you purchased Remove Ads.
• A random install ID used only to group analytics and crash reports from the same install.
• Counts of completed measurements and sessions, for analytics.

Deleting Flicker Meter removes this on-device data. If iCloud Backup is enabled, the app's container may be included in your iCloud backup and restored when you reinstall.

How the app uses the camera

Flicker Meter requires camera access to capture high-speed frames and analyze brightness over time. The camera captures frames at up to 240 fps (on capable devices) during a measurement. Each frame's luminance is extracted and the sequence is analyzed for periodic brightness variation (flicker frequency and intensity).

Frames are processed in memory and immediately discarded. No photo or video is recorded. Nothing is saved to your photo library. No image is uploaded to HighApps or any third-party service. No frame is analyzed for faces, objects, text, QR codes, or anyone's identity — only brightness values are extracted for flicker analysis.

Camera access can be refused or withdrawn at any time in iOS Settings → Flicker Meter → Camera. The app cannot measure without camera access and will prompt you to enable it.

Summary figures from a completed measurement (such as peak Hz, flicker intensity %, confidence rating, and frame rate achieved) may be sent to Firebase Analytics where analytics is present — see below.

Advertising (Google AdMob)

Ads are provided by Google AdMob and require internet access. The app asks for permission to track you through Apple's App Tracking Transparency prompt, shown once after a brief explanation. If you allow it, Google may use the advertising identifier (IDFA) to show ads that suit you better. If you decline, the IDFA is not available and ads are served without it. Measuring works exactly the same either way. You can change your answer at any time in iOS Settings → Privacy & Security → Tracking.

The app declares Apple's SKAdNetwork identifiers so Google can measure ad performance without identifying you. You may see:

• A banner on the result screen and history screen
• Occasional interstitials after a measurement (not after every measurement, and never during analysis)

An optional Remove Ads in-app purchase (processed by Apple, not by HighApps) removes all ads from the app. All measurement features remain available whether you purchase or not.

In regions where Google's consent messages apply (including the EEA, UK, and Switzerland), Flicker Meter shows Google's User Messaging Platform (UMP) form before requesting ads. Ads are loaded only when that form allows it (canRequestAds). Personalized advertising follows the choices you make there and in your device's ad settings.

Google and its partners may collect device identifiers, IP address, approximate location derived from IP, and interaction data to serve and measure ads. That processing is governed by Google's policies, not by a HighApps server.

AdMob / Google Privacy Policy: policies.google.com/privacy
How Google uses information from apps: policies.google.com/technologies/partner-sites
AdMob privacy: AdMob help

Analytics and crash reporting

We use Google Firebase Analytics and Firebase Crashlytics. Analytics collection is enabled for the app so we can keep the product stable and understand usage. Crashlytics is enabled so we can diagnose failures. The app also records whether the tracking prompt was allowed or declined, as a plain status value.

Typical events and properties include:

• Screens opened (home, measure, result, history, settings, info)
• Measurement flow (start, complete, abort, frame rate achieved, confidence level)
• Completed peak Hz, flicker intensity %, and confidence rating summaries for a finished reading
• Whether AE lock or white-balance lock was enabled, frame rate, app version
• Ad requests, fills, impressions, clicks, and paid-event values from AdMob
• Whether Remove Ads was purchased
• The anonymous install ID as the Analytics and Crashlytics user ID
• Crash logs, stack traces, and diagnostic keys (for example current screen or measurement step)

In code, analytics storage consent is granted so we can keep the product stable and understand usage. Ad storage, ad user data, and ad personalization follow the UMP / ads consent result; ad personalization is additionally granted only when you allowed tracking. Turning down personalized ads or tracking does not by itself turn off crash reporting or basic analytics.

Firebase privacy: firebase.google.com/support/privacy

Permissions

• Camera — required to capture high-speed frames for flicker analysis. Asked the first time you open the measure screen, and revocable in iOS Settings → Flicker Meter → Camera.
• Internet — ads, analytics, crash reporting, and opening this policy.
• Tracking — Apple's App Tracking Transparency permission, asked once through Google's consent SDK and used only for personalized ads; revocable in iOS Settings → Privacy & Security → Tracking.

Flicker Meter does not request location, microphone, contacts, or access to your photo library. Camera access is used only for live brightness analysis during measurements — no image or video is saved or uploaded.

In-app purchase

The optional Remove Ads in-app purchase is processed by Apple through your Apple ID. HighApps receives only a purchase receipt validation from Apple's servers; we do not see your payment details. The purchase unlocks an ad-free experience and is tied to your Apple ID, so it restores on reinstall or on other devices signed in with the same Apple ID.

Children

Flicker Meter is a light-measurement tool. It is not directed at children. We do not knowingly collect personal information from children under 13 (or under the digital-consent age in your country, such as 16 in parts of the EU). The ads SDK is not tagged for users under the age of consent, because we do not intend the app for that audience. If you believe a child has used the app in a way that sent data to Google, contact us and we will help as far as the third-party consoles allow.

Your choices

• Camera — refuse it, or withdraw it later in iOS Settings → Flicker Meter → Camera. The app cannot measure without it and will prompt you to enable it.
• Ads consent — complete or revisit the UMP message where it is shown. Also use Settings → Privacy & Security → Tracking to allow or withdraw tracking for Flicker Meter, and Settings → Privacy & Security → Apple Advertising to turn off personalized ads.
• Remove Ads — purchase it in the app to remove all ads. The purchase is tied to your Apple ID and restores on reinstall.
• History — delete a saved reading, or delete the app to remove all on-device data.
• This policy — linked from the app's info screen.

Security

Traffic to Google (ads, analytics, crashes) uses encrypted connections provided by those SDKs. On-device history is stored in the app's private container. No method of electronic storage or internet transmission is completely secure.

Changes

We may update this policy when the app's data practices change (for example new features, ads, or analytics). The "Last updated" date at the top will change. Continued use after an update means you accept the revised policy.

Contact

HighApps
Studio: highapps.am
Email: highapps2019@gmail.com

Questions about this policy, Flicker Meter, or a privacy request can be sent to that address.