Privacy Policy for Quessia: App Blocker & Focus Timer (Android)

Effective Date: September 20, 2026 · Version 1.0

This Privacy Policy describes how Quessia ("the app", "we", "our") handles information when you use our Android application (package com.appkadag.quessia) to block distracting apps, run focus sessions, and track your own screen time. Quessia stores your rules, tasks, and usage data locally on your device. There is no account and no server that receives this data.

The Short Version: Quessia stores your block rules, focus sessions, tasks, and screen-time stats in a local database on your Android device. We do not operate any servers that receive this data, and we do not have access to it. The Android accessibility service Quessia uses to detect which app you've switched to is configured so it cannot read what is on your screen, only which app's window is in front. Quessia has no ads and nothing to buy: there is no advertising SDK and no in-app purchase. The one thing that leaves your device is a crash report, sent to Firebase Crashlytics only if the app crashes — see Section 6.

What we collect from you: Nothing automatically, except a crash report (stack trace plus OS/device/app-version info) if the app crashes — see Section 6.
What you create stays where: On your device only (local database, never transmitted to our servers).
No accounts, no analytics SDK, no ads, no in-app purchases.
Third parties involved: Firebase Crashlytics (Google), for crash reports only. That's it.

1. Information You Provide

The following data is stored locally on your Android device only, in the app's own on-device database. It is never transmitted to our servers, because we do not operate any servers that receive this data.

Block Rules: Which apps you choose to block, the schedule, and any quota you set for them
Focus Sessions: Start and end times and planned duration of sessions you run
Block-Attempt Log: Which rule fired, when, and how many times, so the app can show you your own counters
Tasks, Projects, and Daily Plans: Anything you type into the productivity side of the app
App Settings: Your preferences and theme

Android-Specific Storage: All of the above is stored in a local Room (SQLite) database, sandboxed within the Quessia app. Android's app sandboxing prevents other apps from reading this database. No cloud sync is performed by the app.

2. The Accessibility Service: What It Can and Cannot See

This is the permission most worth explaining plainly. Quessia's accessibility service is configured with canRetrieveWindowContent="false" and is only allowed to listen for one event type, typeWindowStateChanged. In practice this means the service can only ever see which app's window just came to the front (its package name, e.g. com.instagram.android): it cannot read text, images, or any other content on your screen, in this app or any other app, at any time.

Quessia uses this service for exactly one purpose: to detect when you've switched into an app covered by one of your active block rules, so it can show the block screen. The package name it reads is compared against your rules on-device and is not transmitted anywhere. When a block fires, the service either draws an overlay on top of the blocked app or returns you to the Home screen: it never types into, taps, or otherwise controls any other app.

3. Screen-Time Statistics (Usage Access)

To show you your own "Top apps" and screen-time numbers, and to double-check which app is in the foreground, Quessia uses Android's Usage Access API (PACKAGE_USAGE_STATS / UsageStatsManager). This requires a one-time grant from the Android system's "Usage access" settings screen, separate from a normal runtime permission prompt. The usage data this reads is processed and stored entirely on your device, purely to power the app's own stats screens, and is never transmitted anywhere.

4. What We Do NOT Collect

Specifically, the app does not collect or transmit any of the following:

❌ Screen content: the accessibility service cannot read text, images, or content in any app (see Section 2)
❌ Your rules, tasks, sessions, or screen-time history: these never leave your device
❌ Account information: Quessia does not require sign-up, email, or any account
❌ Advertising data: no advertising SDK, no advertising identifier, no ad personalization
❌ Payment or purchase data: Quessia has no in-app purchase or subscription
❌ Precise location data (we do not request GPS or fine location)
❌ Contacts, Camera, or Microphone
❌ Analytics or usage-tracking: no event tracking of what you tap, which screens you visit, or how you use the app

The one exception is a crash report, sent only if the app crashes — see Section 6.

5. Android Permissions

Quessia requests the following Android permissions:

Accessibility Service (BIND_ACCESSIBILITY_SERVICE): lets Quessia detect which app is in front so it can enforce your block rules. See Section 2 for exactly what it can and cannot see.
SYSTEM_ALERT_WINDOW: used to draw the block screen on top of a blocked app.
PACKAGE_USAGE_STATS (Usage Access): used to show your own screen-time stats and confirm the foreground app. See Section 3.
POST_NOTIFICATIONS: used for reminders and status notifications generated on your device. Optional; the app works without it.
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: lets you exempt Quessia from battery optimisation so its background blocking service keeps running reliably. Optional.
Internet access: used only by Firebase Crashlytics to transmit a crash report if the app crashes. See Section 6.

6. Crash Reporting

Quessia uses Firebase Crashlytics, a Google service, so that if the app crashes, we receive a crash report: a stack trace, plus your device model, OS version, and the Quessia app version. Crashlytics is deliberately configured for crash reports only — no analytics, no custom event logging, and no custom keys or breadcrumbs are attached to a report. This is a deliberate choice: it means a crash report can never include which apps you've chosen to block, or anything else about your rules or usage, even if the app happened to crash while showing a block screen. A crash report is the only data Quessia transmits off your device.

7. Data Sharing

We share data with the following party only:

Firebase Crashlytics (Google): receives crash reports as described in Section 6. Google's use of this data is governed by Google's Privacy Policy and Firebase's data processing terms.

We do not sell your personal data. We do not share your rules, tasks, sessions, or screen-time data with any third party, because that data never leaves your device.

8. Your Choices

Notifications: Disable any notification at any time in Android Settings > Apps > Quessia > Notifications.
Accessibility service: Turn it off at any time from Android's own Accessibility settings; doing so simply stops app-blocking from working until you turn it back on.
Delete your data: Uninstall the app from your device to permanently remove all locally stored data (subject to the backup note in Section 10).

9. Children's Privacy

Quessia does not knowingly collect personal information from children. The app does not require any account, sign-up, or personal information from any user regardless of age.

10. Data Retention, Backup, and Deletion

Rules, tasks, focus sessions, and settings can be deleted individually from within the app, on the screens that manage them.
There is currently no single "erase everything" button. Uninstalling the app deletes its local database along with it.
Android Auto Backup: Quessia currently has Android's system-level allowBackup setting turned on, with no exclusion rules. This means Android's own Auto Backup feature may include Quessia's local database in the encrypted backup Android already makes to your own Google account, the same way it does for most apps. We do not control, receive, or have access to that backup; it lives in your Google account, governed by Google's own backup terms, not by us.
Because nothing is sent off-device by the app itself, there is no server-side copy of your data for us to separately delete on request. If you believe we hold data about you elsewhere (for example, a support email you sent us), contact us using the details below and we will delete it.

11. Your Rights (GDPR / CCPA)

Right to access: All your data is on your device, accessible at any time inside the app.
Right to deletion: Delete individual rules, tasks, or sessions, or uninstall the app: your data is gone from your device immediately, subject to Section 10's backup note.
Right to opt out of sale: We do not sell data; nothing to opt out of.
Rights related to Google's processing of crash reports: contact Google via their Privacy Policy.

12. Changes to This Policy

If we change how Quessia handles data — for example, if advertising or in-app purchases are reintroduced, or if we add a new third-party service — we will update this Privacy Policy and update the "Effective Date" at the top. For material changes, we will surface a notice within the app on your next launch.

13. Contact

Questions or concerns about this Privacy Policy?

Email: appkadag@gmail.com