Privacy for Noise Traffic Light / Semáforo de Ruido

Last updated: October 26, 2026

This policy covers the Android application Noise Traffic Light / Semáforo de Ruido and this informational website. The owner is Adrián Muñoz Perera. Privacy contact: odd.kernel.sl@gmail.com.

Summary

The app does not create accounts, has no proprietary backend and uses no proprietary telemetry.
Microphone audio is processed locally in memory. It is not recorded, stored or sent.
Necessary settings stay on the device until app data is cleared. Android backup is disabled.
A Google Mobile Ads (AdMob) banner may process data under Google policies, with consent choices handled beforehand where applicable.

Microphone and audio

The microphone is requested so that you can authorize detection. After permission is granted, listening starts automatically while the activity is visible in the foreground; it pauses in onPause and restarts in onResume while permission remains granted. There is no persistent service. Audio samples are used only to calculate the current noise level. They remain in RAM and are not turned into recordings, files, backups or transmissions to this owner or a proprietary server.

Optional tutorial voice

The tutorial can read its instructions if you enable it. Only the fixed guide text is passed to the voice engine installed on Android, never microphone audio. The app selects voices that declare no network requirement; if none is compatible, the visual guide remains available. The engine is a device component with its own terms.

Local app data

The app keeps the settings needed to work on the device, such as tone, volume, duration and interval settings, tutorial state, local session data and the state of rating prompts. They are not synchronized with an account or sent to a proprietary backend. They remain until you clear the app data or uninstall the app; see the deletion instructions.

Google Mobile Ads (AdMob)

The app may display a footer banner through Google Mobile Ads / AdMob. Google, as a third party, may process advertising-related data, including device identifiers, IP address (from which approximate location can be derived), ad interactions, diagnostics, performance information and crash logs, for advertising, analytics and fraud prevention under its own policies and configuration.

On opening, the app updates consent information and uses Google’s User Messaging Platform (UMP) to request or show a consent form when available. Ads may only be requested when Google indicates that this is allowed. Privacy options are made available when Google requires that they can be reopened. This static website sets no cookies, loads no ads, has no analytics and uses no external fonts.

See Google Mobile Ads privacy documentation and Google’s Google Play data-disclosure guidance. Those pages and their descriptions can change and can refer to SDK versions other than the one included in a particular app release; this page does not represent a SDK-specific review.

Website, server and technical logs

This is a static website: it has no forms, accounts, database, crash API or proprietary analytics. The proxy or web server may create technical access logs to operate and protect the service, for example IP address, date and time, requested path and response status. Project configuration does not set a retention period for those logs, so this policy does not invent one.

Retention and recipients

No audio is retained. Local preferences are retained until you delete them. Data processed by Google for ads is governed by Google’s policies, controls and retention periods, not by this app’s proprietary storage. This app does not sell data or send audio data to third parties.

Your rights and contact

Where applicable law allows it, you may ask about data under the owner’s responsibility and request access, correction, erasure, objection, restriction or portability. Because there is no account or proprietary backend, the app has no remote profile to identify. For Google data, use Google’s privacy controls and channels. For local preferences, the effective method is to delete them in Android as described on the deletion page. You can contact odd.kernel.sl@gmail.com with questions about this policy or possible server logs.

Changes

If relevant data processing, SDKs or app behaviour changes, this page, its date and, when applicable, Google Play declarations will be updated before the affected release is published.

Leer esta política en español.