Privacy Policy

Effective date: October 30, 2026

White Noise Station is an app for playing ambient sound for sleep, focus and relaxation, free to use with an optional paid upgrade, White Noise Station Pro. It is made by one person, Yaniv Hadar ("I", "me"). This policy explains what the app and the website, whitenoisestation.com, collect, and why.

The short version

• No accounts and no sign-in. I never ask for your name, email address or phone number.
• Your likes, history, settings and the sounds you make in the Studio stay on your device.
• The app sends anonymous usage statistics and crash reports to Google's Firebase, not tied to your name, email or any account. You can turn them off in the app.
• If you buy Pro, Apple takes the payment and RevenueCat checks the purchase. Neither gives me your name, card or Apple ID.
• The app has no ads, doesn't use Apple's advertising identifier and doesn't track you across other companies' apps or websites.
• The website uses Google Analytics and the Meta Pixel only if you accept cookies there, to count visits and measure and target my ads.
• I never sell your data.

Who is responsible

Yaniv Hadar is the "controller" of the personal data described here, for laws such as the GDPR. Contact: [email protected].

What stays on your device

The app keeps your liked sounds, your 50 most recently played sounds, your 10 most recent searches, your settings, the sounds you save in the Studio, downloaded sound files, the date you first opened the app (so a sound that later becomes Pro stays free for you), and the Pro status last confirmed by the App Store. The Home Screen widget reads the playing sound and time left from storage shared only with the app. Alarms and reminders are scheduled on your phone; no notification server is used. None of this is sent to me or anyone else, though it may be included in your own iCloud or computer backups.

What leaves your device, and why

1. Downloading sounds (Cloudflare)

Sounds, cover images and the sound catalog are delivered by Cloudflare from cdn.whitenoisestation.com. Like any web server, Cloudflare receives your IP address, the file requested, the time and basic technical details. I use this only to deliver the files and see total traffic; I keep no request logs. See https://www.cloudflare.com/privacypolicy/.

2. Usage statistics (Google Analytics for Firebase)

To decide what to build next, the app sends short event records: the app was opened; a sound was played (which catalog sound, and from where; a Studio sound is reported only as "a My Sounds sound"); a listening session started or ended (its duration and why it ended); a duration was set or extended; a sound was downloaded, liked or unliked; a search was made (only whether it found anything, never what you typed); the Pro screen was shown or closed, and purchases (section 4).

Firebase adds a random identifier for this installation, device and app details (model, iOS version, app version, language), your approximate location derived from your IP address (the app doesn't use location services), and its own standard events such as sessions and updates.

It never sends your name, email, a user ID, your search text or your Studio creations. It does not use Apple's advertising identifier (IDFA) or identifier for vendors (IDFV); Google Signals and ad personalisation are off. Google processes this data on my behalf: https://policies.google.com/technologies/partner-sites, https://firebase.google.com/support/privacy.

3. Crash reports (Firebase Crashlytics)

If the app crashes, Crashlytics sends the app's technical state at the crash, device and iOS details, the app version, a random installation identifier and the latest usage events above. No name, email, searches or Studio creations.

4. Buying Pro (Apple and RevenueCat)

Apple takes the payment under its own terms; I never receive your card details or Apple ID. RevenueCat checks App Store purchases on my behalf. The app sends it a random identifier for this installation, the App Store's record of your purchases in this app (plan, dates, trials, renewals, cancellations, refunds), the app's identifier for vendor (IDFV, not the advertising identifier), device, app, language and App Store country details, and your IP address. RevenueCat uses this to confirm purchases, prevent fraud, unlock Pro and give me aggregate sales reports; nothing in it tells me who you are. See https://www.revenuecat.com/privacy.

The app also tells Firebase (section 2) which plan was bought, whether it started a trial and whether it was at the Founding Supporter price; Firebase may record the App Store's price and currency for the purchase.

The website (whitenoisestation.com)

The site is hosted by Railway and delivered through Cloudflare, which receive your IP address, the page requested and your browser's technical details in order to serve it. I keep no request logs.

Cookies only with your consent. Until you tap Accept on the site's banner, nothing is loaded from Google or Meta. A Global Privacy Control signal counts as Decline. Your choice is kept in your browser for 13 months, and "Cookie settings" at the bottom of every page changes it; declining after accepting removes their cookies. If you accept:

• Google Analytics receives page views, which sound previews you play, and taps on the App Store button and the support email, in the same Analytics property as the app. Its cookies (_ga, _ga_…) hold a random identifier for up to 2 years. Google Signals and ad personalisation are off.
• Meta (Facebook, Instagram) receives the same visits and actions through the Meta Pixel and may link them to your Facebook or Instagram account. Its _fbp cookie lasts 90 days. I use it to measure my ads and to show ads to people who visited the site. Meta and I are jointly responsible for this collection; Meta's use is covered by https://www.facebook.com/privacy/policy/. Under some US state laws this counts as "sharing" personal information; declining stops it.

Legal bases (EEA, UK and Switzerland)

• Delivering sounds, checking purchases, serving the website: necessary to provide what you asked for, and my legitimate interest in running the app and preventing fraud.
• App usage statistics and crash reports: my legitimate interest in improving the app and keeping it stable. You can object at any time with the in-app switch.
• Google Analytics and the Meta Pixel on the website: your consent.

How long data is kept

• On your device: until you remove it or delete the app.
• Usage statistics (app and website): event data 2 months, then deleted; reports without identifiers may be kept longer.
• Crash reports: 90 days.
• Purchase records (RevenueCat): while I use RevenueCat, so purchases can be restored and refunds and disputes handled.
• Meta Pixel data: under Meta's policy.

Your choices and rights

• Stop app statistics and crash reports: Profile › "Share usage & crash data". The app stops sending them and resets its analytics identifier.
• Website cookies: "Cookie settings" at the bottom of any page.
• Subscriptions: Settings › your name › Subscriptions, or Profile › Manage subscription.
• Delete everything on your phone: delete the app.

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict its processing, and to withdraw consent. Email me to use them. Because there are no accounts, I usually can't tell which records are yours, but I'll help where I can. You can also complain to your data-protection authority.

Children

The app and website are for a general audience and not directed at children under 13 (or the minimum age in your country). If you believe a child has given me personal information, contact me and I'll help remove it.

International transfers and security

Google, Meta, Cloudflare, Railway and RevenueCat may process data in the United States and other countries, relying on safeguards such as the EU-U.S. Data Privacy Framework and Standard Contractual Clauses. Everything the app and website send travels over encrypted connections (HTTPS/TLS).

Changes

If this policy changes, I'll update it here and change the effective date. If a change materially affects what is collected, I'll also say so in the app or its release notes.

Contact

Yaniv Hadar — [email protected]