Privacy Policy
The short version. Rippstr collects your email address and a user ID so you can sign in, the audio you record so the app can identify it, a device identifier so the app works reliably on your device, and anonymous product-interaction data so we can see which features get used.
We do not sell your data. We do not track you across other companies' apps or websites.
Who this policy covers
This policy covers the Rippstr iOS app. When we say "Rippstr," "we," or "us," we mean the Rippstr app and the servers that run it.
What we collect and why
Email address
Collected when you create an account. Used to sign you in, reset your password, and send you service messages such as security notices. We do not use your email for marketing.
Audio you record
Recordings you make in the app are uploaded to our servers (hosted on Google Cloud) so the app can identify them and prepare them for playback. Every accepted recording is added to the app's public "Theirs" feed, where other users can play it back, rate it, and view its metadata (such as its classification tags and rating). Your account's screen name is displayed alongside recordings you upload. Anyone using the app can also generate a shareable web link to any recording in the feed, and that link is accessible to anyone it is sent to. By recording and uploading audio in the app, you are publishing that audio to other users of the service.
Before a recording is retained in our storage, it is screened by an automated voice-detection filter. Recordings identified as containing human speech are rejected at submission and are not persisted to our storage systems. This filtering is performed on a best-effort basis using automated detection and, while we take reasonable measures to make it effective, we cannot guarantee that every recording containing voice will be detected and rejected with 100% accuracy.
User ID
An account identifier generated by our authentication provider (Firebase Authentication). Used to tie your recordings and settings to your account across sessions. Used only for app functionality — it is not sent to our analytics.
Device identifier
A random identifier tied to your installation of Rippstr — not your Apple advertising identifier, not a hardware serial, not linkable to other apps. It is used for two narrow app-functionality purposes: counting unique installs so we can size the audience, and enforcing free-trial limits so a single device can't recycle accounts to bypass the trial. It is not used for advertising and is not shared with data brokers.
Rippstr does not request or use Apple's advertising identifier (IDFA), which is why the app does not show the App Tracking Transparency prompt.
Product-interaction data
Anonymous events describing which screens you open and which features you use — for example "recording started," "toot processed," "share completed." Sent to Google Analytics. Not linked to your account or your email. Used to understand which parts of the app are useful and which need work.
What we do not collect
Rippstr does not collect your name, physical or postal address, phone number, precise or coarse location, contacts, photos, health data, financial information, browsing history, or search history. We do not request the Apple advertising identifier.
Who else sees your data
We use the following third parties to run the app. They act as service providers on our behalf and only receive what they need to do their job:
| Service | What it receives | Purpose |
|---|---|---|
| Firebase Authentication (Google) | Email, user ID | Sign-in and account management |
| Google Cloud Storage & Cloud Functions (Google) | Audio recordings, user ID | Hosting and audio identification |
| Cloud Firestore (Google) | Account metadata, device identifier, library contents | App data storage |
| Google Analytics for Firebase (Google) | Device identifier, product-interaction events | Product analytics |
Each third party listed above — and any parent, subsidiary, or affiliated entity with access — is contractually required to provide the same or equal protection of your data as described in this policy. These parties may use the data only to perform services on our behalf and may not use it for their own purposes or share it further.
Tracking
Rippstr does not track you as Apple defines the term. We do not link your data with data collected by other companies for advertising or ad measurement. We do not share your data with data brokers. We do not enable Google Ads linking or Google Analytics remarketing on our analytics property.
How long we keep it
Account data, your library, and your recordings are retained for as long as your account is active. When you delete your account (see below), we begin deletion of the data associated with it. Analytics data is retained per Google Analytics' default retention (currently 14 months) after which it is deleted automatically.
How to delete your data
Open the Rippstr app and go to Settings → Account → Delete Account. This permanently deletes your account, your library, and the recordings we hold for you. There is no separate web dashboard — deletion happens in the app.
To remove the app itself from your device, delete it from the iOS home screen. Deleting the app does not delete your account on our servers — use the in-app control above for that.
California
Rippstr does not respond to Do Not Track browser signals — no browsers are involved in the iOS app. Rippstr does not track you across other companies' apps or websites, and our analytics provider (Google) operates only within the Rippstr app; we do not enable Google Ads linking or remarketing audiences. We do not sell or share personal information for cross-context behavioral advertising as those terms are defined by the California Consumer Privacy Act.
Children
Rippstr is not directed at children under 13 and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, delete the account from within the app to remove it.
Changes to this policy
If our data practices change, we will update this page and revise the effective date above. If we begin collecting a new category of data, we will disclose it here and update our App Store privacy details before the change takes effect.