Privacy Policy

Your sounds never leave your device. Opening files, extracting a video’s audio, recording, trimming, fades, loudness and the final ringtone file all happen on the device. Ringsy has no server to receive audio and no account system.

Three kinds of data are sent automatically: purchase data, so the app knows whether you have unlocked Ringsy Unlimited; anonymous usage statistics (which features and screens are used — never your sounds or their names); and crash reports (what went wrong when the app crashed — never your sounds or anything you type). A fourth, feedback, is sent only if you write it and tap Send yourself. Details below.

When you pick a file through the iOS file picker, Ringsy receives only that file. The app copies it into its own private storage on the device so you can edit it, and has no access to any other file.

Ringsy may ask for access to your photo library so you can pick a video and use its sound.

Only the video you pick is read, and only its audio is kept — on your device. The original video is not modified, not deleted and not sent anywhere.

Ringsy asks for the microphone so you can record a sound for a ringtone. The microphone is on only while you are recording on the Record screen.

Recordings are saved on your iPhone and are not sent to Apple, to me, or to anyone else. Ringsy does not transcribe or analyse what you record.

Ringsy uses RevenueCat to manage the Ringsy Unlimited purchase. When the app starts and when you buy or restore, RevenueCat’s SDK sends to its servers:

• An anonymous app user ID generated by RevenueCat. It is not your name, email or account — the app has no account system to tie it to.
• The device identifier Apple gives developers (identifier for vendor).
• Your purchase history: whether you have bought Ringsy Unlimited.

This data is used for one purpose only: deciding whether Ringsy is unlocked for you. It is not linked to your identity and is not used for advertising or tracking.

Payment itself is handled by Apple. Ringsy never sees your card details.

From version 1.2 (build 12), Ringsy sends anonymous usage statistics to Google Analytics for Firebase, a service of Google, so I can see which features are used and where people get stuck. Usage statistics are sent by the App Store version of the app and have no on/off setting: they are anonymous, limited to what is listed below, and part of how Ringsy is kept working. (Versions 1.2 to 1.2.2 had a “Share anonymous usage statistics” switch in Settings; later versions do not, and send statistics for everyone, including people who had turned that switch off.)

What is collected: app interactions (for example “a sound was imported from Files”, “a fade was set”, “a ringtone was exported”, “the paywall was shown or closed”, “a purchase succeeded or failed” with the store’s error code), which screens of the app are opened (screen names only), whether Ringsy Unlimited is unlocked, the app’s language, and coarse device information Google Analytics collects automatically: device model, iOS version, app version, and country/region derived from the IP address. Each installation gets a random app-instance ID from Firebase; it is not your name, email or Apple ID.

What is never collected: your sounds, songs, videos or recordings; file names, song titles, tone names or anything you type (including caller names); contacts; precise location or GPS coordinates; the advertising identifier (IDFA). Ringsy does not ask for App Tracking Transparency because it does not track you: ad storage, ad personalization and ad-network attribution are switched off.

Retention: Google Analytics keeps this event data for 2 months (its default retention setting) and then deletes it; only aggregated reports remain after that.

Google acts as a processor for this data under the Google Analytics terms. Google’s own privacy policy: https://policies.google.com/privacy — and how Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites

From the version after 1.2.2, when Ringsy crashes or one of its screens fails with an error, a crash report is sent to Firebase Crashlytics, a service of Google, so the bug can be found and fixed. Crash reports are only sent by the App Store version of the app.

What a report contains: where in Ringsy’s code the problem happened (a stack trace) and the error message — with file paths, web addresses and quoted text removed before it leaves the device — plus technical details Crashlytics collects automatically: device model, iOS version, app version, orientation, free memory and storage, whether the device is jailbroken, and the time of the crash. Each installation gets a random Crashlytics installation ID; it is not your name, email or Apple ID.

What a report never contains: your sounds, songs, videos or recordings; file names, song titles, tone names or anything you type; contacts; location; the advertising identifier (IDFA). Ringsy attaches no user ID and no custom data to its reports.

Retention: Crashlytics keeps crash reports and installation IDs for 90 days, then deletes them.

Google acts as a processor for this data under the Firebase data processing terms. How Firebase handles data: https://firebase.google.com/support/privacy

• Your songs, videos, recordings or the ringtones you make
• Name, phone number, contacts — or your email, unless you choose to enter it in feedback you send
• Precise location or GPS coordinates
• The advertising identifier (IDFA)

Ringsy includes no advertising SDK and does not track you across other apps or websites. Its only analytics are the anonymous usage statistics and crash reports described above. If that ever changes, this policy and the App Store privacy label will be updated before that build ships.

When you tap “Set as ringtone”, “Save to Files” or “Share”, iOS opens its share sheet or file saver and the ringtone file goes where you choose. If you email support, the email goes through your own Mail app.

Your tones, their source sounds, how many free exports you have used and your settings are kept in the app’s private storage on the device. None of it is synced anywhere.

Deleting a tone, using “Delete all tones” in Settings, or deleting the app removes that data. Ringtones you already set in iOS stay in your iPhone’s Sounds settings.

Ringsy has an optional “Feedback & bug report” form. Nothing is sent unless you open it and tap Send — the app never sends feedback on its own.

When you tap Send, we receive:

• The message you type.
• Your email address, only if you enter one — used only to reply to you.
• A screenshot, only if you attach one.
• Your app version, iOS version, device type (iPhone or iPad) and app language.
• A random install identifier generated by the app. It is not linked to your Apple ID or any account, and is used only to limit spam.

Feedback is stored on our own backend, hosted by Supabase in Singapore (ap-southeast-1), and a notification with your message is forwarded to the developer's private Telegram chat. Your network IP address is kept only as a one-way hash, for at most one hour, to rate-limit submissions.

Feedback is never used for tracking, advertising or analytics, never sold or shared, and not linked to your identity.

We keep feedback until the issue is handled, then delete it; any screenshot is deleted along with the message. To have anything you sent deleted, email vanthuong.dao2004@gmail.com with roughly when you sent it and what it said (or the email address you used).

Ringsy has no content from other users and no built-in web browser. The app does not knowingly collect data from children.

Since there is no account, there is no personal profile on our side for you to request or delete. If you sent feedback, you can have it deleted — see “Feedback you send us”.

If you want the anonymous RevenueCat user ID deleted, email me and I will take care of it.

Ringsy has no setting to stop usage statistics or crash reports. Deleting the app stops them and removes its app-instance and installation IDs from your device; what was already sent expires after the retention periods above.

When this policy changes, the date at the top changes with it. Material changes will be called out in the App Store release notes.

This website, not the app, uses Google Analytics 4 to count visits and to see which pages and links are used, so the site can be improved. Google processes this data on our behalf as a service provider.

What is collected: the pages you open, the site you came from, clicks on links that leave this site (such as the App Store button), and coarse device, browser, language and country or region information. Google Analytics sets first-party cookies in your browser to tell one visit from another.

What is never collected: your name, your email address, or anything you type on this site. This data is not used for advertising and is not shared with data brokers.

Google Analytics keeps this event data for 2 months (its default retention) and then deletes it. To opt out, block Google Analytics with a browser extension or turn off cookies for this site; the website and the app keep working. This section covers the website only; the app is covered in the sections above.

Google's own privacy policy: https://policies.google.com/privacy