01 About this policy
Hush FM is operated by Jayanth Gopu, based in India. You can contact us at support@hushfm.app.
This policy covers hushfm.app, our support correspondence, and the Hush FM app, including its Staging test version. The app is currently in private testing. Features and availability differ between test builds; public registration and general paid access are not open.
02 Information we use
- Account and sign-in information. Guest access uses an anonymous account identifier and session. If you sign in with Google, Google and our authentication provider process your sign-in, and we receive an account identifier, email address and profile information made available through that sign-in. We do not receive your Google password.
- Age confirmation and preferences. We record confirmation that you meet our age requirement and keep settings such as selected languages and playback preferences. The birth-year selector is used to determine eligibility; it does not submit your selected year as a date of birth to our backend.
- Listening and access records. We process episode activity, playback sessions, resume positions, followed stories, unlocks, timers and, where enabled, download permissions. These let the app resume listening, maintain your library and check access.
- Purchases and rewards, where enabled. App stores and our purchase provider process transactions. We receive purchase identifiers, product and entitlement status, balances, benefit and refund records needed to deliver and reconcile access. We do not receive your full payment-card details. Staging uses test transactions and test ads.
- Device, connection and diagnostic information. App and service providers process installation or device identifiers, app versions, IP addresses, request times and error or security information to deliver the service and investigate problems.
- Support information. If you contact us, we receive your email address, message and attachments. Please do not send passwords, one-time codes, access tokens, full card details or identity documents in an initial enquiry.
03 Website & device storage
Our website serves its own pages, fonts, images and videos. It has no advertising or analytics tags, social embeds or payment forms. The website code does not set application cookies or browser storage. Hosting and network providers still process connection information to deliver and protect the site.
Our website access log records time, hostname, response status and response size, without IP addresses, requested URLs, browser agents or referrers. Error and infrastructure diagnostics may contain additional connection information.
The app stores session information, preferences and cached content on your device. Downloaded content, where available, also uses device storage. Signing out, clearing a cache or uninstalling the app does not by itself delete server records or information held by providers.
The sign-in callback page does not exchange or display your authorization code. Sign-in URLs can still appear in browser history or be processed by sign-in providers; do not share URLs containing a code.
04 Optional rewarded ads
Where offered, you choose whether to watch an ad for a reward such as an extra temporary timer slot. The Staging Android app is configured to request test ads only. Rewarded ads are not enabled in the Production app at this time.
We use Google AdMob and its consent tools. Google's ad SDK can process IP addresses (including to estimate general location), device or account identifiers, ad interactions and diagnostic information for ad delivery, measurement and fraud prevention. Test ads do not mean that the SDK processes no data. See Google's privacy policy and how Google uses information from apps and sites.
Our app checks Google's consent status before loading an ad. Where a consent message is required, you can make your choices in that message and revisit the available ad privacy options in the app. You can also choose not to request an ad.
To award a reward, we send Google a random reward reference and test-environment marker. Google returns a signed completion record, which we associate with your account to verify the reward and prevent duplicate grants. We do not put your email address or story title in that reward reference.
05 Service providers & sharing
We use providers for specific parts of Hush:
- Supabase for authentication, the app database and backend services.
- Cloudflare for domain and network services, media delivery and support-email forwarding.
- DigitalOcean for website hosting.
- Google for Google sign-in, Google Play services and purchases where used, AdMob where enabled, and support email.
- RevenueCat and the applicable app store for purchase verification and subscription or entitlement management where those features are enabled.
Support replies may display our Hush Gmail sender with support@hushfm.app as the reply address. Providers may process information outside India. Their locations, roles and safeguards differ by service; contact us for information about the services relevant to your request.
We do not sell your account details or listening history. We may disclose necessary information to meet a legal requirement, address fraud or security incidents, or protect users and the service. Optional advertising has the provider processing described above.
06 Why we use information
We use information to provide the features you request, remember your place and preferences, verify access and rewards, reconcile transactions, answer support requests, and keep Hush secure and reliable.
Where applicable law requires a legal basis, we rely on providing the service you request for account, playback and access processing; our legitimate interests in operating a secure service and responding to support for necessary diagnostics and fraud prevention; consent for optional processing where required; and legal obligations for records or disclosures required by law. You can withdraw consent for optional processing without affecting processing that was lawful before withdrawal.
07 How long we keep information
Retention depends on the information and its purpose:
- Account, preferences, progress and access records support your account and library. Closure requests and the end of their purpose require review, including any records needed for security or a legal obligation.
- Purchase, balance and reward records may need to remain to reconcile benefits, prevent duplicate grants, investigate refunds or disputes, and meet applicable record-keeping requirements.
- Support correspondence is used for the request and necessary follow-up. A specific complaint, investigation or preservation requirement may justify keeping relevant material longer.
- Security and diagnostic records have service-specific retention and may be held for a particular incident or legal requirement. Backups are separate from live records and follow provider recovery cycles.
During the current private test, automatic cleanup of older listening-session and request records is not active. These records can remain for the duration of testing and until reviewed or removed. A timer finishing or downloaded content expiring does not mean the related account records are erased. We do not promise a fixed automatic deletion period that is not operating.
08 Your choices & requests
You can change available preferences in the app, choose whether to sign in for account features, and decline optional rewarded ads. Where relevant, you manage or cancel a store subscription through that store; an account-closure request does not cancel it automatically.
Depending on the law that applies, you may have rights to access, correct, delete or receive a copy of your information, restrict or object to processing, withdraw consent, and complain to your local data-protection authority.
To ask a question or make a request, email support@hushfm.app. Tell us what you need and which app version you use. We may need to verify your authority through the original account or sign-in route before releasing or changing account information. We will explain any information we need and the outcome or limits of the request.
Automated in-app account deletion and complete local/provider erasure are not available in the current private test. You can still contact us about closure or deletion. We will explain what can be completed and what remains, including any records that must be retained. A received or queued request is not confirmation of completed erasure. This does not remove rights under applicable law.
09 Age requirements
Hush is intended for people aged 18 and over. The app asks for age confirmation before listening. If you believe someone under 18 has provided personal information to Hush, contact support so we can investigate.
10 Contact & updates
For privacy questions or requests, contact Jayanth Gopu, Hush FM, India at support@hushfm.app.
We will update this page as the service or our practices change and show the revised date above. Where required, we will provide additional notice or ask for consent before a material change takes effect.