Privacy Policy: Quietly
Last updated: June 3, 2026
The Quietly mobile application (package name com.leapps.quietly) is developed and owned by
Loop Europe Ltd and marketed under our software development brand L.E.Apps
(“we”, “us”, or “our”). This Privacy Policy explains how we handle information in connection with the app.
For questions about this policy, use the contact details in Section 15.
1. Who we are
Loop Europe Ltd is the data controller for personal data we process when you use Quietly and when you contact us directly.
Privacy contact: support@quietlydisconnect.app
2. Our approach: minimal data
We design Quietly to collect and process as little information as possible. We do not operate user accounts on our own servers inside the app,
we do not sell personal data, and we do not integrate third-party analytics or behavioural-tracking SDKs for marketing purposes.
Some information is still processed on your device, by Google when you use Google Play services
(subscriptions, in-app updates), or by us only if you email us. We describe each case below.
3. What Quietly does (context)
Quietly helps you run protected time sessions: you choose a mode and duration, and the app can apply Do Not Disturb rules,
show a session notification, and (with your permission) manage incoming notifications so that only VIP contacts you select
can interrupt you. During protected time, VIP incoming calls are signalled with an in-app alert on the countdown screen (not an audible ring through Do Not Disturb in most cases). When a session ends, the app may show a session summary listing missed calls, incoming calls, and incoming text messages from people matched in your device Contacts during the session.
Optional SMS auto-reply: If you enable SMS auto-reply in Settings, Quietly can send a courtesy message from your device to
people in your device Contacts when they call or text during protected time. VIP contacts are used for VIP-only notification handling and the in-app call alert; auto-reply matching uses your Contacts more broadly. Per-mode message text and a short fixed footer are described in
Section 4.6.
4. Information the app processes
4.1 Data stored only on your device
The app stores content and settings locally on your device, for example:
- Protected-time sessions (mode, start/end times, duration)
- Session summaries linked to completed sessions (missed calls, incoming calls, and incoming SMS from matched Contacts during the session)
- Per-mode auto-reply message bodies you edit in Settings (stored on device)
- VIP contacts and VIP groups you add (display name, Android contacts lookup key, and phone number when available from your address book)
- Custom modes (name, description, colour, Do Not Disturb strictness, VIP-only rules)
- App preferences (theme, onboarding state, last custom duration, subscription-related flags we cache locally after Play confirms entitlement)
This on-device data is used only to run the app. We do not receive this data on our own servers in the ordinary operation of the app.
Depending on your device and system settings, Android backup or device transfer features may copy some app data to your Google account
or another backup destination. That processing is governed by your device settings and
Google’s Privacy Policy
(or your device manufacturer’s policies), not by servers we operate.
4.2 Contacts (READ_CONTACTS)
When you add a VIP contact or group member, Quietly uses the Android contacts picker and, where needed, the READ_CONTACTS permission
to resolve the contact you selected. If you enable SMS auto-reply, Quietly also reads your device contacts to match incoming callers and texters during a session—we store only what is needed locally (see Section 4.1)—we do not upload your address book to our servers.
You can remove VIP entries in the app at any time; deleting app data or uninstalling removes locally stored contact references.
4.3 Notifications and Do Not Disturb
With your consent, Quietly may:
- Modify Do Not Disturb policy during an active session according to the mode you chose
- Post notifications about the active session and session summary
- Use a notification listener service during an active session to suppress non-VIP notifications, keep VIP call notifications where applicable, and record missed calls, incoming calls, and incoming SMS from matched Contacts for the session summary
While a session is active, notification handling uses metadata from notifications on your device (such as app package, title, and text snippets)
to decide whether a notification is from a VIP contact (for bypass and in-app call alert) or from someone in your Contacts (for auto-reply and session summary). That processing happens on your device. We do not routinely send notification contents to our servers.
If you choose Answer & end session when a VIP call alert is shown, protected time ends, Do Not Disturb is restored to its prior state, and the app may open your phone’s call UI using the system intent from the incoming-call notification. That action is initiated by you on the device.
4.4 Subscriptions (Google Play Billing)
Quietly offers optional paid access through a Google Play subscription (product ID quietly_pro, including a free trial where offered in Play Console).
When you subscribe, Google Play processes payment and subscription management. We do not receive your full payment card details.
We may receive limited purchase-related signals through Google’s billing APIs (for example whether a subscription is active) so we can unlock features in the app.
Google’s handling of payment and account data is described in:
Subscription cancellation and refunds are managed in Google Play (Settings → Subscriptions), subject to Google’s policies.
4.5 In-app updates (Google Play)
If you use Check for updates in the app, we use Google Play’s in-app update APIs to learn whether a newer version is available
and to download updates through Play. That interaction is between your device, Google Play, and Google’s systems—see Google’s privacy materials linked above.
4.6 Contact availability notifications
If you enable SMS auto-reply in Settings, Quietly can send a courtesy message during an active protected-time session. In general:
| Topic | How we handle it |
|---|---|
| Purpose | Let people in your device Contacts know you are in protected time and not ignoring them on purpose |
| Who receives messages | People whose phone number matches an entry in your device Contacts when they call or text during a session—not limited to VIP groups (VIP is for Do Not Disturb bypass only) |
| What is sent | A per-mode message body you can edit in Settings (or a default template), plus a fixed plain-text footer “Quietly for Android” (no hyperlink), sent from your device via SMS |
| How it is sent | Through Android SMS (including multipart messages when needed), using your mobile account and carrier—standard message rates may apply |
| What we store | Your enable/disable preference, per-mode message bodies, VIP call alert color preference, and session summary data on your device; we do not host message content or recipient lists on our servers |
| What recipients see | Your phone number as the sender, your message text, and the footer line identifying the app—no URL in the footer |
| Your control | Turn the feature on or off globally, edit per-mode message text, and stop auto-replies by ending the session or disabling the feature |
We request SEND_SMS only when you use this feature; the system permission prompt explains the purpose.
One auto-reply is sent at most once per contact per session.
Important: Automated messages are courtesy notices, not proof of delivery, and not suitable for emergencies.
See Section 11.
4.7 Support and legal requests
If you contact us by email, we process the information you send (for example your email address and message content) only to respond to you
and to meet legal obligations where applicable. We do not use support correspondence for advertising or resale.
5. What we do not do
We do not:
- Require registration or an in-app account on our own backend
- Use third-party analytics or advertising SDKs as part of the app
- Build advertising profiles about you from app usage
- Sell personal or sensitive user data
- Upload your full contacts database to our servers for normal app operation
6. How we use information
We use information only to:
- Provide and maintain app functionality (sessions, modes, VIP rules, session summaries, on-device storage)
- Validate and deliver subscriptions through Google Play
- Operate optional SMS auto-reply to device Contacts when you enable it
- Reply to your support or privacy inquiries
- Comply with applicable law and protect legitimate interests (for example security and fraud prevention), where permitted
7. Sharing of information
We do not share personal data with data brokers. We share information only as needed with:
- Google (and affiliates as applicable), when you use Google Play, Play Billing, Play in-app updates, or Android backup—subject to Google’s Privacy Policy
- Mobile network operators / messaging services, when you send an automated availability message from your device to a contact (carrier and platform terms apply)
- Professional advisers or authorities where required by law or to protect rights and safety
We do not sell your VIP contact list or session history to third parties.
8. Security
We protect information under our control with appropriate technical and organizational measures for the nature of the processing.
Communication with Google Play uses industry-standard secure connections where applicable.
Information in the app remains largely under your control on the device. Use a screen lock and protect device access to reduce risk if your phone is lost or shared.
9. Retention and deletion
| Data type | Retention |
|---|---|
| On-device app data | Until you clear app storage, uninstall Quietly, or use in-app controls where we provide them |
| Support emails | Only as long as needed to handle your request and for legitimate business or legal retention, then deleted or anonymized where appropriate |
| Google Play / Google account | Governed by Google; see Google’s help and privacy materials |
Because the app does not offer a separate “Quietly account” on our systems, there is no remote “delete my account” flow for app-specific cloud data we do not host.
Deletion of on-device data is managed as above.
10. Permissions and system access
Android may ask for permissions so Quietly can work reliably. Current or planned permissions include:
| Permission / access | Why Quietly may need it |
|---|---|
| POST_NOTIFICATIONS | Show active session and session-summary notifications |
| Do Not Disturb access | Apply mode-specific interruption filters during protected time |
| Notification listener | Hold non-VIP notifications during a session, handle VIP call notifications, and build the contact-scoped session summary |
| READ_CONTACTS | Let you pick VIP contacts and match device Contacts for auto-reply and session summary |
| FOREGROUND_SERVICE (special use) | Keep the session timer reliable with a visible ongoing notification |
| RECEIVE_BOOT_COMPLETED | Restore scheduling behaviour after device restart where applicable |
| SEND_SMS | Send optional SMS auto-replies to device Contacts during protected time |
We use permissions only for the related functionality described in the system prompt and in-app context—not to sell data or run cross-app advertising tracking.
Permissions may change as the app and Android evolve; we will update this policy when materially new access is introduced.
11. Not a substitute for emergency or medical services
Quietly is a productivity and wellbeing tool for managing interruptions during time you choose to protect.
It is not an emergency service, medical device, or guaranteed way to reach you in a crisis.
Do Not Disturb, notification suppression, and optional automated messages to contacts may delay calls, texts, and alerts—including from people not on your VIP list.
Always use normal emergency channels (for example local emergency numbers) when you need urgent help.
12. Children’s privacy
The app is not directed at children in the sense of collecting contact or profile information from them for our own marketing.
We do not knowingly solicit personal information from children under 13 (or the age required in your jurisdiction).
If you believe a child has sent us personal information, contact us and we will take appropriate steps.
13. International users
If you use the app from outside the country where Loop Europe Ltd is established, your information may be processed in accordance with this policy and applicable law,
including when you use Google services that may process data in multiple regions.
If you are in the European Economic Area, United Kingdom, or other regions with specific privacy rights, you may have rights to access,
rectify, erase, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority.
Contact us at support@quietly.app to exercise applicable rights.
14. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version on this page and change the Last updated date.
If changes are material—especially for contact notifications or new data collection—we will use reasonable means to bring them to your attention where appropriate
(for example an in-app notice or Play Store listing update).
15. Contact us
Loop Europe Ltd (L.E.Apps — Quietly)
Email: support@quietlydisconnect.app
16. Related Google policies (reference)
When you use Google services with Quietly, these Google documents also apply to Google’s processing:
- Google Privacy Policy
- Google Terms of Service
- Google Play Terms of Service
- Google Play Developer Distribution Agreement (for apps distributed via Play)
By using Quietly, you acknowledge that you have read this Privacy Policy.