Privacy Policy
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
- Your audio and video files never leave your device. Noise removal runs locally.
- We do not collect, upload, sell, or share your media files.
- No account or sign-in required.
- We do not request runtime permissions for microphone, camera, location, contacts, photos, or storage.
- We collect anonymous diagnostic and usage data (crash reports, basic analytics) to keep the App stable.
- Our sole third-party data processor is Google Firebase.
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:
- are not uploaded to any server we operate;
- are not shared with any third party;
- remain in your device's local storage or temporary cache until you delete them or the OS clears the cache.
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).
| Service | What it collects | Purpose |
|---|---|---|
| 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:
| Event | Parameters |
|---|---|
probe_failed | error_kind (coarse category), file extension |
processing_started | input duration (seconds, rounded), sample rate, channel count, output format |
processing_succeeded | input duration, total processing seconds, denoise seconds, real-time-factor (×100), output format |
processing_failed | input duration, output format, error_kind |
processing_cancelled / processing_cancelled_tap | input 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
- Your name, email address, phone number, or contacts
- Your precise location (GPS) — only approximate country, derived from IP, via Firebase Analytics
- Photos, videos, or audio that you did not explicitly select for noise removal
- Microphone input outside of files you provide
- Login credentials for any service
- Payment information (in-app purchases, if any, are handled entirely by Apple or Google)
- Advertising identifiers (AdId, IDFA, SSAID — see Section 1.3)
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 #
- Your audio/video files: kept locally on your device until you delete them or clear the App's storage. We have no copy.
-
Picker cache copies: When you import a file, the OS file picker writes a sandboxed copy into the App's
temporary cache (
<cache>/file_picker/...on both platforms). After a successful denoise we delete our copy from the picker cache to minimize on-device footprint. The original file at its original location is never modified by NoisyNo. - Crash reports (Crashlytics): retained per Google's defaults (currently up to 90 days for detailed reports).
- Analytics events (Firebase Analytics): retained per Google's defaults (currently up to 14 months).
You can request deletion of diagnostic data tied to your installation by contacting us (see Section 8).
4. Third-Party Service Providers #
-
Google LLC (Firebase) — Crashlytics, Analytics, Remote Config. We have disabled Advertising ID and SSAID
collection in Analytics, so events are not used for ad personalization.
firebase.google.com/support/privacy -
Apple Inc. — When you install via the App Store, Apple collects standard installation and diagnostic data
per its own policy. The App also calls Apple's
SKStoreReviewController(via thein_app_reviewplugin) to show the standard rating prompt; Apple may collect standard interaction metrics for that prompt.
apple.com/legal/privacy -
Google LLC (Google Play) — When you install via Google Play, Google collects standard installation and
diagnostic data per its own policy. The App also calls Google Play's In-App Review API (via the
in_app_reviewplugin) to show the standard rating prompt; Google may collect standard interaction metrics for that prompt.
policies.google.com/privacy
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 #
- Stop file processing: close or delete the App.
- Limit analytics tracking on the OS level: on iOS, disable "Allow Apps to Request to Track" and personalized ads in Settings → Privacy & Security. On Android, reset your Advertising ID in Settings → Google → Ads. (Note: NoisyNo already opts out of AdId collection, so these toggles primarily affect other apps.)
- Delete local data: delete the App, or in device settings clear the App's storage/cache.
- Request deletion of diagnostic data: email grayforge.dev+noisyno@gmail.com with your device model and approximate date of use.
6. Children's Privacy #
NoisyNo is not directed to children. Specifically:
- We do not knowingly collect personal information from children under 13 (United States, COPPA), under 14 (South Korea, PIPA Article 22), or under 16 (European Economic Area, GDPR Article 8) — or the equivalent minimum age in your jurisdiction.
- The App displays the Apple App Store / Google Play standard age rating; please consult the listing for the rating that applies in your region.
- If you believe a child has provided us with personal information, please contact us and we will delete it.
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:
- access the diagnostic data we hold about your installation,
- request correction or deletion,
- object to or restrict processing,
- request data portability,
- withdraw consent at any time, and
- lodge a complaint with your local data protection authority.
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:
- on-device processing (so sensitive media never leaves your phone),
- HTTPS for all network communication with Firebase services,
- Apple's iOS App Transport Security and Android's network security configuration to block insecure HTTP fallbacks,
- Google's infrastructure security for Firebase data at rest.
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