Privacy Policy
This policy explains what the Quietext iPhone app (including its Message Filter, share extension, widgets and Shortcuts action) and this website do with your data. Quietext is provided by CODE MAGNET YAZILIM LTD, a company registered in Turkey ("we", "us"). We are the controller of the data described here. Contact: support@quietext.com.
The short version
- Your texts stay on your iPhone. The message filter and Scam Check analyze text on the device. Message text and anything you check are never sent to us or to any other company.
- No access to iMessage or contacts. Quietext cannot read your iMessages, your contacts or your message history.
- No name, email or phone number needed. The app identifies you only by a random id it creates on your device.
- No advertising and no tracking. We don't show ads, don't use the advertising identifier and don't track you across other companies' apps or websites.
1. What stays on your iPhone
Message filter
When you turn on Quietext in Settings, iOS gives the filter the sender and text of incoming SMS, MMS and RCS messages from unknown senders only. iOS decides which messages these are; it never passes iMessages, messages from your contacts, or conversations you have replied to several times. The filter compares each message with your allow-list, your rules, the pattern lists stored on your device and a small on-device classifier, then tells iOS which folder to use. The filter has no network connection, cannot store the messages it sees and cannot report them back to the app. We never receive them.
Scam Check
Text, links or phone numbers you paste, type, share to Quietext or send through the Shortcuts action are analyzed on your iPhone. The content is not sent to our server. Your check history is stored only on your device.
Apple Intelligence explanation (iOS 26 and later)
On supported devices with Apple Intelligence turned on, Quietext can ask Apple's on-device Foundation Models to explain a verdict in plain language. This runs on your iPhone through Apple's framework, under Apple's own terms and privacy commitments. We receive nothing from it.
Rules and settings
Your rules, allow-list, language choices and setup status are stored on your device, in storage shared only between the Quietext app and its extensions.
2. What our server receives
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| A random app user id. The app generates it on first launch, stores it in your Keychain and, if you use iCloud Keychain, Apple syncs it across your devices. It works like a password for your app, so the app never shows it. Instead it shows a support id (for example QT-1A2B-3C4D-5E6F-7A8B), a one-way code made from the app id that we also store, which you can share with us safely. | To recognize the app without an account, keep your subscription working and let you restore purchases. | Performance of our contract with you |
| App language, time zone and app version | To show content in your language, time things sensibly and keep the app compatible. | Performance of contract |
| Push notification token, only if you allow notifications | To send the billing notice described below. | Your consent (the iOS permission); you can withdraw it in Settings at any time |
| Scam Check usage counts (how many checks, never their content) | To apply the free tier limits. | Performance of contract |
| Purchase and subscription status, received from RevenueCat | To unlock Quietext Pro and to apply first-purchase offer rules. | Performance of contract |
| Counters for the paywall, the offer and review prompts (for example when an offer was last shown) | So these screens appear rarely and at most as often as our rules allow. | Legitimate interest in running the app fairly |
| IP address and request details in server logs | To deliver responses, protect the service against abuse and fix errors. | Legitimate interest in security |
Our server sends the app pattern lists (known spam sender patterns, link domains and phrases). The app downloads them and the filter reads them locally; nothing about your messages is sent in return.
Notifications. If you allow them, we only send a notice when there is a billing problem with your subscription (for example an expired card), so you can fix it before Pro stops. You can turn them off in iOS Settings.
3. Analytics and crash reports
We use Google Firebase Analytics and Firebase Crashlytics to understand how the app is used and to fix crashes. They receive usage events (for example "setup confirmed", "rule saved", "Scam Check done" with the verdict category, never the checked content), crash reports with device model and iOS version, a Firebase app instance id, and your support id (set as the user id for analytics events and crash reports, so we can count unique users and match a crash to a support request; it is not linked to your name, email or phone number, and the random app id itself is never sent to them). Firebase Analytics also derives a general location (country or region) from your masked IP address; it doesn't use Location Services. We don't collect the advertising identifier, don't use App Tracking Transparency tracking, and have turned off ad personalization and Google Signals. The legal basis is our legitimate interest in keeping the app stable and improving it; you can object by emailing us.
4. Service providers
We share data only with providers that process it on our behalf:
- Apple: App Store downloads, payments and subscriptions; push notifications (Apple Push Notification service); iCloud Keychain sync of the random app id.
- RevenueCat, Inc. (USA): subscription management. Receives the random app user id, your App Store purchase and subscription transactions, and these attributes: app language (locale), time zone, app version and the Firebase app instance id. We don't send it your IP-based or device advertising identifiers for attribution.
- Google (Firebase Analytics and Crashlytics): usage events and crash reports as described above.
- Hetzner Online GmbH (Germany): hosting of our server, database and this website, in Hetzner's data center in Finland (EU).
- Cloudflare, Inc. (USA): DNS, network proxy and caching for this website and our API (it sees IP addresses and request details in transit), and forwarding of email sent to our support and privacy addresses.
We don't sell or rent your data. Where a provider processes data outside the EU/EEA, it relies on safeguards such as the EU Standard Contractual Clauses or the EU-U.S. Data Privacy Framework.
5. How long we keep data
- Server account data (the random id, settings, counters, push token): until you delete your account in the app, or when you ask us to.
- Purchase history: we keep a minimal record even after account deletion, keyed by the random app id: whether it has purchased before, the Pro entitlement with its product, store, environment and expiry date, and the ids, types and dates of purchase events from RevenueCat and Apple. It prevents abuse of first-purchase offers and keeps the subscription working if it continues. It contains no name, email or message content. On deletion we erase the full RevenueCat event details (which include the attributes listed in section 4); if the subscription keeps renewing after that, new events are stored in full until you cancel it.
- Free-tier usage counts and review-prompt counters: kept with the random app id after account deletion, so deleting doesn't reset the free limits or bring rating prompts back. They are numbers and dates, never message content.
- Server logs: up to 14 days.
- Firebase Analytics: event data is kept for 2 months. Crashlytics: crash reports are kept for 90 days.
- RevenueCat and Apple keep their own purchase records under their policies.
- Data on your iPhone (rules, check history, pattern lists) stays until you delete it in the app or delete the app.
6. Deleting your data
In the app, go to Settings › Delete account. This deletes or anonymizes the data our server holds about you. Your subscription is not cancelled automatically; manage it in your Apple ID settings. More details, and how to ask by email, are on the account deletion page.
7. Your rights
Depending on where you live (for example under the GDPR or UK GDPR, or US state laws such as the CCPA), you may have the right to access, correct, delete or export your data, to restrict or object to processing, and to withdraw consent. Write to support@quietext.com and include your support id (shown in the app under Settings › Your support ID), because it is the only way we can find your data. We answer within 30 days. You can also complain to your local data protection authority.
8. Children
Quietext is not directed to children under 13 (or the minimum age required in your country), and we don't knowingly collect data from them. If you believe a child has used the app and you want their data removed, contact us.
9. Security
Data travels over encrypted connections (HTTPS). The random id and the app's sign-in token are kept in the iOS Keychain. Our server is hosted in the EU and access is limited to the people who run it.
10. This website
This website uses no cookies, no analytics and no trackers. Our host keeps standard access logs (IP address, time, requested page) for security, for up to 14 days. Headings use the Fraunces font from Google Fonts, so your browser connects to Google's servers, which receive your IP address.
11. Changes
If we change how Quietext handles data, we will update this page and its effective date. For significant changes we will also tell you in the app.
12. Contact
CODE MAGNET YAZILIM LTD, a company registered in Turkey
Email: support@quietext.com