Nunes Technologies Ltd
Nunes FaceLight — Privacy Policy
1. Who we are and how to contact us
Nunes FaceLight is provided by Nunes Technologies Ltd. We are responsible for the personal information we handle in connection with this app. For privacy questions, rights requests or support, email [email protected]. Our website is nunestechnologies.co.uk.
FaceLight does not create its own user account and V1 does not need a Nunes-operated server. Google services used for purchases, advertising and SDK operation have their own data processing, described below. This policy covers the app; it does not describe the separate hosting practices of every website you may visit.
2. Auto Face Light: camera and facial analysis
If you choose Auto Face Light and grant camera permission, the app uses the front camera while its analysis screen is open, before a call. CameraX supplies a live preview and temporary frames; the bundled ML Kit face detector locates a face so the app can estimate overall and left/right lighting and recommend brightness, zones and colour temperature.
This is on-device processing. FaceLight does not save photographs, record video or audio, recognise identity, create a biometric identity template or send facial images or facial results to Nunes servers or advertising services. Temporary image buffers are released after processing; a chosen lighting configuration may be saved as settings, not as an image. Auto is not a system for accessing another app’s video call or sharing its camera.
Local image analysis does not mean that every SDK is offline. ML Kit can exchange technical service metrics with Google; these are separate from camera images and facial outputs. See section 7.
3. Ambient light and optional call detection
Adaptive Light reads the device’s ambient-light sensor locally, where available, to adjust the lighting. Current lux readings are held in memory rather than uploaded or kept as a sensor history.
Notification access is optional. Android may make notifications available to the listener; FaceLight filters supported calling apps and uses technical signals such as app package, call category/style, ongoing status, event times and hashed notification keys to infer call activity. Message bodies, notification titles and contact names are not used as call-detection rules, stored or uploaded. Call-state information is used in memory to manage the floating control; it is not sent to advertisers.
Production releases do not enable the optional developer notification recorder. In debug builds only, a manually started diagnostic session can keep limited technical events in memory, with hashed tag/group identifiers, a 200-event limit and a 15-minute session expiry. It does not include message text or contacts and is not a server log.
4. Information stored on your device
FaceLight saves settings such as language, active profile, adjusted light levels, selected Auto recommendations, exposure target, Adaptive preference and floating-button position. It also stores the remaining Auto allowance, identifiers used to prevent duplicate rewarded credits, optional call settings, and brightness recovery information when you enable physical-brightness control.
For Pro access, the app caches a signed Google Play purchase record and signature. These records can contain purchase identifiers, product, purchase time and state; they are not your card details. FaceLight does not send this cache to a Nunes backend.
5. Permissions and system access
| Access | Purpose |
|---|---|
| Camera | Optional front-camera preview and local Auto analysis. Denying it leaves manual lighting available. |
| Draw over other apps | Show the floating control and light borders over other apps. It does not grant screen recording or access to their contents. |
| Notification access | Optional detection of supported calls, as described above. Revoke it in Android settings to stop this detection. |
| Modify system settings / brightness | Optional temporary physical-brightness adjustment. The prior value is saved locally for restoration and recovery. Force-stopping the app or revoking this permission can prevent immediate restoration; reopening the app with the permission allows recovery. |
| Foreground service and app notifications | Keep user-enabled lighting running with a system notification and controls. Permission to show FaceLight’s own notifications is distinct from notification-listener access. |
| Boot completed | Recover brightness/session state after restart; not for background face recording. |
| Google Play Billing | Find the Pro product, launch the Play purchase interface, verify entitlement and restore purchases. |
| Internet, network state and advertising permissions | Google purchases, ads, consent and SDK communications. The release manifest includes advertising ID and applicable Android ad-services permissions supplied by the ads SDK. |
The ambient-light sensor does not require a camera or location permission. FaceLight does not request contacts, SMS, call-log, microphone, photo-library, or precise/coarse device-location access. Not using location permission does not prevent an advertising provider from inferring a general area from a network address.
6. FaceLight Pro and Google Play
FaceLight Pro is a one-time, non-consumable purchase, not a subscription. Google Play processes the transaction. The app queries the product and purchase status, verifies the signed purchase, acknowledges completed purchases and restores eligible Pro access using the purchasing Google account. No FaceLight account is created.
Nunes Technologies Ltd does not directly receive card numbers, bank credentials or payment authentication details from the app. Google manages payment information and purchase history under its terms. Google may make developer order/accounting information available through Play Console. Purchase identifiers used by the app are distinct from payment credentials. Clearing app data does not cancel or delete your Google Play purchase.
7. Advertising, consent and Google SDKs
The Free version may show Google AdMob banners within the app and optional rewarded ads. A rewarded analysis is offered only when you choose to watch an ad and is credited after the SDK confirms the reward. Pro does not show ads. Ads are not placed on the floating overlay or mini panel, and the app blocks ad presentation during its lighting/call/analysis sessions.
Advertising is not data-free: Google may use network addresses, advertising/service identifiers, ad interactions and technical performance information to provide and measure ads and prevent misuse. Do not interpret the local-camera statements as a claim that AdMob collects nothing. See how Google uses information from partner apps and Google’s Privacy Policy.
The Google User Messaging Platform (UMP) manages applicable privacy choices. The app checks the consent status before requesting ads and requests ads only when UMP permits them. UK/EEA consent requirements apply where relevant; personalised ads and access to identifiers must respect the applicable choices. Declining personalisation does not necessarily remove all advertising or technical processing. In the Free version, use Settings → Ad privacy when available; stop lighting or a call before opening privacy options. Android and Google advertising controls provide additional options. Pro stops ad presentation, but does not erase earlier Google records.
ML Kit’s on-device face processing is separate from its technical telemetry. Google documents SDK diagnostics and usage measurements, including installation/service identifiers and device/app characteristics. Camera images and facial outputs are not part of that telemetry. The app does not add Firebase Analytics, Crashlytics or a Nunes analytics backend. Google SDK telemetry is still relevant even without those products.
8. Retention, deletion and backups
- Transient local processing: image buffers, live sensor values and current call signals are used for the feature and released or reset as processing/session lifecycle ends. No photo, video or call-content archive is created.
- App preferences and Pro cache: retained on the device until changed, cleared, revoked by a purchase refresh, or removed with app data/uninstallation. Selected numeric lighting settings may persist until you replace or clear them.
- Android backups: eligible preferences may be backed up or transferred according to Android/device settings and can return after reinstallation. The app excludes its signed Pro/access cache, call settings and physical-brightness recovery/consent store from its configured backup/transfer rules. Uninstalling does not itself delete a platform cloud backup.
- Google Play: Google controls retention of payment/purchase records. Requests concerning that history must be handled through Google’s account/Play processes, subject to its obligations.
- Ads and SDK metrics: Google controls service-side retention under its policies. Clearing FaceLight does not automatically delete Google-held records; use Google’s privacy controls or request assistance.
- Support: if you email us, we handle your address and the information you choose to provide to answer you and resolve the request. We retain it for that purpose and any applicable legal need, not as a face-analysis database. Do not send payment credentials or unnecessary facial images.
9. Your choices, legal bases and rights
You can stop Auto or Adaptive, turn off call detection, revoke permissions, review advertising choices and clear local app data. Where UK GDPR/GDPR applies to processing for which we are responsible, we rely on the basis relevant to the activity: providing requested features/purchase support, legitimate interests in security and responding to support, legal obligations where applicable, and consent for advertising/device access where required. An Android permission is not a substitute for every required data-protection or advertising consent. Google explains its own processing bases in its policies.
Depending on the circumstances, you may request information/access, correction, deletion, restriction or portability, object to processing, and withdraw consent without affecting earlier lawful processing. These rights are subject to applicable conditions and exemptions. Contact [email protected]. We may need proportionate information to locate a support/order record; we cannot retrieve camera images that were never retained.
You may complain to the UK Information Commissioner’s Office or your relevant EEA supervisory authority. Lighting recommendations are not identity decisions or decisions with legal/significant effects. Google may process service data internationally; its privacy information describes locations and applicable safeguards.
10. Children
FaceLight is not specifically designed or marketed as an app for children. This policy does not claim a child-directed service or an age-verification system. If you are a parent/guardian with a concern, contact us so we can address the information we control and direct you to relevant Google controls where needed.
11. Third-party information and updates
- Google Play terms and Google Privacy Policy
- Google advertising information and AdMob SDK data disclosure
- ML Kit terms/privacy and ML Kit SDK data disclosure
- CameraX documentation
These links explain the relevant providers’ practices; a link does not mean FaceLight uploads facial images to them. We may update this policy when the app or its providers change. The date above identifies the latest revision; material changes will be communicated as required. Privacy and support contact: [email protected].