NoisyNo

Privacy Policy

Developer: grayforge · Contact: grayforge.dev+noisyno@gmail.com
Last updated: May 28, 2026 · Effective: May 28, 2026

This Privacy Policy explains how the NoisyNo mobile application ("NoisyNo", "the App", "we", "us") handles information when you use it. We designed NoisyNo to do as much as possible on your device, so the App collects very little from you.

TL;DR

1. Information We Process #

1.1 Audio and Video Files (Processed Locally Only)

When you select a file in NoisyNo, the App reads it from your device's storage to apply noise removal. This processing happens entirely on your device. The original file, the cleaned output, and any intermediate data:

1.2 Files You Choose to Share

If you tap the "Share" button, the operating system's standard share sheet is invoked. Where the resulting file is sent (e.g., Messages, Mail, AirDrop, Google Drive) is your choice, and the receiving service's own privacy policy applies. NoisyNo itself does not transmit the file anywhere.

1.3 Diagnostic, Crash, and Usage Data

To keep NoisyNo stable and to understand which features users actually use, we send anonymous diagnostic and usage data to the following Google Firebase services. Each is enabled by default; you can limit some of this collection at the operating-system level (see Section 5).

ServiceWhat it collectsPurpose
Firebase Crashlytics Crash stack traces; device model, OS version, app version; a randomly generated installation ID; custom debugging keys we attach to each session — currently the input file's duration, sample rate, and the output format. Identify and fix crashes
Firebase Analytics Anonymous app events (see list below); approximate region (country only, derived from IP); device language; device type / model class; app version. We have disabled the Android Advertising ID (AdId) and SSAID collection so events cannot be used for ad personalization or attribution. Understand which features are used and how the App performs
Firebase Remote Config No user data collected; the App fetches configuration values we publish from our project. Adjust App behavior (e.g., feature flags) without a new build

Concretely, the App emits the following Analytics events. Each event carries only the parameters listed — no file names, no file contents, no audio data:

EventParameters
probe_failederror_kind (coarse category), file extension
processing_startedinput duration (seconds, rounded), sample rate, channel count, output format
processing_succeededinput duration, total processing seconds, denoise seconds, real-time-factor (×100), output format
processing_failedinput duration, output format, error_kind
processing_cancelled / processing_cancelled_tapinput duration, output format
file_renamed(no parameters beyond the standard event metadata)
feedback_email_copied(no parameters)
app_review_*(in-app review prompt outcome, no identifying data)

This data is pseudonymous — tied to a randomly generated Firebase installation identifier, not to your name, email, phone number, or audio content. We never combine this data with your media files.

1.4 What We Do Not Collect

2. Permissions (None Required) #

NoisyNo requests zero runtime permissions. No permission dialog ever appears — not for microphone, camera, location, contacts, photos, storage, or background activity.

You pick a file through the operating system's standard file picker (Apple UIDocumentPicker on iOS, Storage Access Framework on Android), which grants access to just the file you tap without showing a permission prompt. The cleaned output is written into the App's own sandboxed storage, which also requires no permission. You can verify this in the App Store listing's "App Privacy" section and Google Play's "Data safety" section.

3. How Long We Keep Data #

You can request deletion of diagnostic data tied to your installation by contacting us (see Section 8).

4. Third-Party Service Providers #

Other client-side packages bundled in the App (such as the file picker, share sheet wrapper, URL launcher, path provider, wakelock, state management, and routing libraries) only call platform APIs locally and do not send any data to us or to third-party servers.

5. Your Choices and Controls #

6. Children's Privacy #

NoisyNo is not directed to children. Specifically:

7. International Data Transfers #

If you use NoisyNo outside the United States, the diagnostic data described in Section 1.3 may be processed on Google Firebase infrastructure located in the United States or other countries where Google operates.

For users in the European Economic Area, the United Kingdom, and Switzerland, we rely on the European Commission's 2021 Standard Contractual Clauses (Module 2: Controller to Processor) with Google as the legal basis for cross-border transfers, together with the supplementary measures Google publishes at the URL in Section 4. For users in jurisdictions that recognize them, we also rely on Google's certifications (such as ISO/IEC 27001 and the EU–U.S. Data Privacy Framework).

By using the App, you understand that diagnostic data may be transferred and processed as described above.

8. Your Rights (GDPR / CCPA / Korea PIPA, etc.) #

Depending on where you live, you may have the right to:

Legal basis (GDPR). We process Crashlytics and Analytics data under the legitimate interest basis (Article 6(1)(f) GDPR) — specifically, the legitimate interest in keeping the App stable, secure, and improving over time. This basis is appropriate because (a) the data is pseudonymous, (b) we have disabled advertising identifiers, and (c) we do not combine it with your media or any other personal data. You can object to this processing at any time using the contact below; on objection we will delete diagnostic records associated with your installation.

South Korea (PIPA / 정보통신망법). Korean users have the additional rights set out in the Personal Information Protection Act and may file complaints with the Personal Information Protection Commission (개인정보보호위원회, pipc.go.kr). For minors under 14, processing requires parental consent — NoisyNo does not knowingly process data for users under 14 (see Section 6).

California (CCPA / CPRA). We do not "sell" or "share" personal information as those terms are defined under the CCPA/CPRA.

To exercise any of these rights, contact us at grayforge.dev+noisyno@gmail.com. We will respond within the period required by applicable law (typically 30 days).

9. Security #

We rely on:

No method of transmission or storage is 100% secure. We do our best, but we cannot guarantee absolute security.

10. Changes to This Policy #

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date at the top, and where required by law we will provide additional notice (such as an in-app prompt). Continued use of the App after changes take effect constitutes acceptance of the revised policy.

11. Contact #

Questions about this Privacy Policy or our data practices:
grayforge
Email: grayforge.dev+noisyno@gmail.com