Eyecon Privacy Policy

Eyecon Privacy Policy

Effective 29 July 2026 · Last updated 21 August 2026

Eyecon for Android (com.glivy.eyeconpro), published by Glivy. Questions or requests: glivyapps@gmail.com

1. The short version

Eyecon watches for one thing: whether your eyes are on the screen. When they are not, it pauses what you were watching. When they come back, it resumes.

That requires the camera. It does not require a copy of what the camera sees. Each frame is examined on your phone, by code running on your phone, and is gone a fraction of a second later. Nothing is recorded, and there is no server of ours that could receive it if it were.

There are no accounts in Eyecon. We never ask for your name, your e-mail address, your phone number or your location, and the app carries no advertising or tracking code of any kind.

Nothing at all leaves the phone, and the reason is stronger than a promise: Eyecon does not hold Android's INTERNET permission. It cannot open a network connection, so there is no route by which anything it sees could reach us or anyone else. Eyecon is bought once on Google Play, Google confirms that purchase before the app is installed, and the app itself never has a question to ask a server.

A few small things do stay on your phone: your settings, the counters behind the statistics screen, and, if you switch Sleep mode on, a single note of where you had got to the last time you fell asleep watching something. They live in Eyecon's private storage and uninstalling the app erases them. We never receive any of it, and could not receive it if we wanted to. If you have Android's backup switched on, your settings and the statistics ride along in it to your Google account, the way they do for the other apps on your phone; the sleep note is deliberately left out, so it stays on the phone and nowhere else. Section 4.4 gives the detail.

The sections below explain all of this properly. Where the summary and the detail differ, the detail governs.

2. What this policy covers

This policy applies to the Eyecon Android app published by Glivy, in every form it is distributed: through Google Play, as a beta, or installed manually.

It does not apply to the apps Eyecon controls. If Eyecon pauses a video for you, that video app is still governed by its own privacy policy, not this one. Nor does it apply to Google Play, Google Play services, or anything else Google operates; those are covered by Google's policy at https://policies.google.com/privacy. Links that take you out of the app take you out of the scope of this policy too.

3. How the app actually works

Understanding two mechanisms will make the rest of this document clearer.

Detecting your gaze. While Eyecon is running, it opens the front camera through Android's CameraX API and hands frames to Google's ML Kit face detection library. That library is bundled inside the app and runs on your device; it does not consult a server. What it returns is not a picture but a handful of numbers: whether a face is present, how likely each eye is to be open, and the angles of your head. Eyecon compares those numbers with your calibration, decides whether you are looking, and lets the frame go. To spare your battery and keep the phone cool it examines at most about ten frames a second and ignores the rest entirely, fewer still while your gaze is steady, and where the device allows it the camera is asked to produce frames more slowly than it otherwise would.

Controlling playback. Eyecon asks Android's MediaSessionManager which apps are currently playing media, and sends ordinary transport commands (pause, play, seek backwards) to whichever one is active. This is the same machinery your lock screen and your headphone buttons use.

So no image, video, photograph, face template, faceprint or biometric record is ever created or kept by Eyecon. The measurements described above exist in memory for the moment it takes to make a decision and are then overwritten.

4. What Eyecon processes

4.1 Camera images

The camera exists in Eyecon for a single purpose: working out whether you are looking at the screen so that playback can pause and resume. Frames are analysed on your device, in memory, by the bundled ML Kit model. They are not written to disk, not cached, not uploaded, and not attached to any diagnostic report. They are not shared with anyone, for any purpose, because they never exist anywhere they could be shared from.

Under the GDPR we rely on your consent, which you give through Android's own camera permission prompt. To the extent any of this analysis is treated as special-category data, that consent is our basis under Article 9(2)(a) as well.

The camera only opens while Eyecon's foreground service is running, and Android tells you so twice over: with a permanent notification and with the system camera indicator. You can stop the service from the app, from that notification, or from the Quick Settings tile, and you can withdraw the permission entirely in Settings → Apps → Eyecon → Permissions. Gaze detection stops working if you do; nothing else breaks.

4.2 What is playing

To pause the right app, resume the right app, and rewind by the number of seconds you chose, Eyecon needs to know which app is playing and what state it is in. It reads the app's package name (com.google.android.youtube, for instance), its playback state and, where the app publishes one, the title of what is playing. When you ask for a rewind it also reads how far into the item you are and how long the item is, at that moment and for that purpose alone.

The title does two jobs, both of them immediate. It appears in the Now playing list inside Eyecon, so that you can see what the app has a hold of, and it is how Eyecon notices you have moved on: a different title in the same media app means a different video, which is not one Eyecon paused and not one it should resume. All of this is live information, held in memory, replaced as it changes and gone when the app stops.

Eyecon reads no artist names, no artwork and no URLs, and it builds no history. There is no running record of what you watched and when, in this app, on your device or anywhere else, and none of what this section describes is sent anywhere. Of it all, only the package name is written down, in the local statistics described in 4.4, with no title beside it.

One narrow exception exists, and only while Sleep mode is switched on. When Eyecon concludes you have fallen asleep in front of a video, it saves a single note so that it can tell you the next morning where you had got to: the media app, the video's title exactly as that app published it, how far into the video you were, and the time. Only the most recent note is ever kept, a new one replaces the old, so there is never more than one on your device. Dismissing the card that shows it deletes it. It is stored in Eyecon's private storage described in 4.4 and, like everything else there, it never leaves your phone.

Deciding that you are asleep rather than simply away also involves your phone's motion sensor, and only in that same narrow window. Once Sleep mode has stopped playback, Eyecon reads the accelerometer for a while to notice whether the phone is picked up, which tells it you are awake and that no note should be saved. It reads a single number, the overall strength of the movement, several times a second; it does not record where you are, how you move or what you do, and the readings are compared against a threshold and immediately discarded. Nothing is written down and nothing is sent anywhere. This watch never runs while Sleep mode is switched off, and even with it on it runs only in that window, ending as soon as the phone is picked up or the decision is made. Android requires no permission for this, so there is no prompt to accept and none to withdraw; switching Sleep mode off stops it.

For a different and much duller purpose, Eyecon also reads which way up the phone is being held, and it does so whenever the camera is open. Android's own OrientationEventListener supplies this and draws on the accelerometer to do it, around five readings a second. Eyecon uses only the answer, the quarter turn the phone is currently in, and uses it to decide which way round the camera frame is handed to the face detector. That reading is a starting point rather than the last word: when the detector finds no face at all, the frame is offered at the other quarter turns as well, which is what keeps detection working when you watch lying on your side. Either way the correction is applied to the frame before it reaches the detector; no additional reading is taken and nothing further about you is measured. It runs only while the camera does, which is only while there is playback to control, and it stops when the camera closes. As above, the readings are used for that comparison and discarded: nothing is written down, nothing is stored and nothing is sent anywhere. This needs no permission either.

Our basis here is straightforward: this processing is what makes the feature you asked for work (Article 6(1)(b)), and we have a legitimate interest in it functioning correctly (Article 6(1)(f)).

4.3 App names and icons

Rather than showing you raw package names, Eyecon asks Android for the apps in your launcher and reads their names and icons for display. The same list is what the app-exclusion screen shows you, so that you can pick which apps Eyecon should leave alone. This happens locally and on demand, and Eyecon deliberately avoids the broad QUERY_ALL_PACKAGES permission: it can only see apps that appear in your launcher.

Three lists of package names are kept on the device as a result, and 4.4 covers them: the apps you excluded; the ones the app has already checked against its built-in guess about music players, so that a choice you undo is not silently made again; and the ones that have actually played something on this phone, which is what lets the exclusion screen show you a handful of relevant apps instead of everything you have installed. That last list holds package names only, with no titles, no times and no counts. None of the three is sent anywhere, and no inventory of your installed apps leaves the phone.

4.4 What is stored on your device

Eyecon keeps a modest amount of data in its own private storage, which Android prevents other apps from reading:

Your preferences, meaning automatic mode, rewind and its duration, Sleep mode and its threshold, the display language you picked, whether you chose the light, the dark or the system theme, and the package names of the apps you told Eyecon to leave alone along with the ones it has already offered a guess about. Separately, the package names of the apps that have played something on this phone, described in 4.3. Markers for the one-time screens you have already been through and for whether you added the Quick Settings tile. The statistics: how many times playback was paused and for how long, broken down by day for the past week and by media app in total. And, if Sleep mode is on and you have fallen asleep watching something, the single note described in 4.2.

Nothing in that list has a counterpart anywhere else. There is no account it belongs to, no server it mirrors and no copy of it beyond your phone.

Eyecon transmits none of it. Android itself, however, backs some of it up for you, and you should know which: your preferences and the statistics take part in Android's own backup, so that a new phone can restore them along with everything else it restores. That backup goes to your Google account under Google's terms, not to us, and we can neither read it nor reach it. Two items are deliberately kept out of it, in both the cloud and the phone-to-phone channel: the sleep note, because it is the most revealing thing the app holds and the promise in 4.2 is that it stays on your phone; and the list of apps that have played something, because it says which media apps you use, it exists only to shorten a screen, and it rebuilds itself within days on the new phone anyway. If you would rather nothing were backed up at all, Android's own backup switch turns it off for every app including this one.

All of it disappears when you uninstall the app or clear its data, and the statistics can be wiped from inside the app at any time.

4.5 What Eyecon never asks for

Eyecon does not collect or request your name, e-mail address, phone number, postal address, date of birth or any government identifier. It never asks your age, and nothing in the app behaves differently depending on it. It does not read your photographs, contacts, calendar, call logs, messages or files. It does not determine your location by any means, precise or approximate. It holds no advertising identifier and no identifier that could follow you between apps.

5. Why the app asks for notification access

This is the permission users ask about most, so it deserves a direct answer.

Android will only tell an app which media sessions are active if that app is registered as a NotificationListenerService. There is no narrower permission that grants media access alone; the platform bundles the two together.

Eyecon therefore registers such a service and leaves it all but empty. Of the callbacks Android offers, it implements two, and neither of them is about a notification: one runs when the system connects the service and one when it disconnects, and each writes a line to the device log saying so, which is how we diagnose phones that never connect it. The callbacks that deliver notifications, onNotificationPosted and onNotificationRemoved, are not implemented at all. So no notification content reaches Eyecon: with no callback implemented, Android has nowhere to deliver it. Beyond those two log lines, the service's only function is to satisfy Android's check so that pausing works.

We word that carefully, because Android's own consent screen says the permission lets an app read every notification, and it is right. That is a property of the permission, which Android defines; what we can tell you about is the code we ship, and in the code we ship there is no path a notification can travel down. The app also holds no internet permission at all, as Section 6 sets out.

Granting it is your decision, made on Android's own settings screen, and you can take it back at any time under Settings → Notifications → Device & app notifications → Eyecon. Without it, Eyecon cannot see or control playback.

6. The permissions, one by one

CAMERA is what detects whether you are looking; refuse it and gaze detection cannot run. FOREGROUND_SERVICE and FOREGROUND_SERVICE_CAMERA let detection continue while you are in another app, with the ongoing notification Android insists upon. POST_NOTIFICATIONS shows that notification; without it Android may limit how visible the service is. Notification access, described in Section 5, provides the list of media sessions, and nothing can be paused without it. The launcher query in the app's manifest supplies app names and icons for display, and the list you choose from when you tell Eyecon which apps to leave alone; it is read on the device and goes nowhere, as Section 4.3 sets out. The motion and orientation readings described in 4.2 require no permission under Android and Eyecon requests none; nor does it request location, storage, microphone, or the ability to draw over other apps.

The app also reads one thing about your device settings: whether Android has exempted Eyecon from battery optimisation. It matters because without the exemption the system ends the app's process while it waits in the background, and detection silently stops. Reading it needs no permission, and Eyecon does not ask for the restricted one that would let it show the exemption dialogue itself; the card in the app opens your system settings so that you make the change. The answer is a single yes or no, read while the app is on screen, used only to decide whether to show that card. It is not stored and not sent anywhere.

INTERNET is absent, and its absence is the load-bearing fact in this document. Eyecon does not declare it, so Android will not let the app open a network connection at all. Every claim above about data staying on your phone rests on that rather than on our word: there is no route out. Earlier versions of Eyecon were free and sold a subscription inside the app, which required the permission in order to verify purchases; Eyecon is now bought once on Google Play, the store handles that entirely, and the permission was removed.

A consequence worth stating: the app works with no connection at all, including in flight mode.

7. The third parties involved

Google ML Kit face detection does the actual analysis, bundled into the app and running on your device. Eyecon sends it nothing over any network, because the library works locally. Google's own terms and privacy policy govern the library itself.

Google Play and Google Play services distribute and update the app and provide platform services. Google independently collects the standard store telemetry it collects for every app, such as install counts and aggregated crash data, under its policies rather than ours.

Buying the app is a transaction with Google, from beginning to end. Eyecon is paid for once on Google Play before it is installed; the store verifies the purchase and only then allows the download and any later reinstall. We never see, receive or store your card number, bank details or billing address, and the app itself contains no purchase code, no billing library and no licence check that would need to reach a server.

Beyond these, nothing. Eyecon contains no advertising SDK, no attribution or tracking SDK, no general-purpose analytics SDK and no third-party crash reporter. Google Play shows us the ordinary aggregate sales and install figures every publisher sees, which is a consequence of selling something rather than a tracking layer, and it reaches us from Google rather than from your phone.

8. Selling, sharing and disclosure

We do not sell your personal information and we do not share it for cross-context behavioural advertising, in the sense the California Consumer Privacy Act and comparable state laws give those terms. We have not done so in the past twelve months, including for anyone under sixteen.

Since the information in Section 4 never leaves your device, there is nothing for us to hand over. The only material we could ever hold is what you send us yourself, such as a support e-mail. We may disclose that where we genuinely believe it necessary to comply with the law or a valid legal process, to enforce our terms, to address fraud or a security problem, or to protect someone from harm, as the law requires or permits.

If Glivy is ever acquired, merged or reorganised, information we hold may pass to the new owner. We would require them to honour commitments no weaker than these, and you would be told through the app or this page before anything became subject to a materially different policy.

9. How long things last, and how to erase them

Camera frames and the measurements taken from them last milliseconds, in memory, and are never written down. The same is true of the motion and orientation readings described in 4.2, which exist only for the comparison that consumes them. The live playback state lasts as long as the service runs. Your calibration is held in memory only and is gone the moment the service stops. Your preferences last until you change them, clear the app's data, or uninstall it. Statistics are pruned automatically after seven days for the daily figures, while the totals stay until you reset them or remove the app. The sleep note described in 4.2 lasts until you dismiss it or until the next one replaces it, whichever comes first. Anything you write to us we keep as long as handling and recording your request requires, and afterwards for as long as the law obliges us to.

To erase everything, uninstall Eyecon or go to Settings → Apps → Eyecon → Storage → Clear data. Either one permanently removes every trace of Eyecon's local data. One caveat belongs here rather than in the small print: if Android's backup is switched on, the items listed in 4.4 as taking part in it may already sit in your Google account, and a later restore can bring them back. Google's own backup controls are where that copy is managed and removed. You can also reset just the statistics from within the app, leaving your settings alone. No request to us is needed for any of that, and none would help: we hold no copy that could be deleted, and none that could be restored. Your purchase itself lives in your Google Play account, and Google's own records and refund process govern it.

10. Security

Eyecon's data sits in the app-private area that Android isolates from other applications at the operating system level. Because the processing is local and the app holds no network permission, the risks that attach to data in transit and to data sitting on servers do not arise here at all: nothing travels, and we operate no server that could hold anything of yours.

Your device is the other half of this. A rooted, compromised or malware-infected phone, or one left unlocked in reach of others, can expose data belonging to any app, Eyecon included. No form of electronic storage is perfectly secure, and while the app is designed so that there is very little to expose, we cannot promise absolute security.

11. Children

Eyecon's target audience on Google Play is declared as thirteen and over. The app is not directed to children under thirteen, nothing about it is designed to appeal to them, and we do not knowingly collect personal information from anyone under that age. If you believe a child under thirteen has sent us something, write to us and we will delete whatever we hold.

Age changes nothing about how the app behaves. Camera images are examined on the device and never leave it, whoever is in front of the lens; there is no account, no profile, no advertising identifier and no tracking code. Nothing reaches a server of ours, because there is none and the app could not reach it.

In the European Economic Area and the United Kingdom the age of digital consent ranges from thirteen to sixteen depending on the country. That range changes nothing here, because we collect nothing to which consent could attach; the only consent in play is Android's camera permission, which you give and withdraw on your own device. Buying the app is a transaction with Google Play, and where the buyer is under eighteen we expect the parent or guardian who controls that Google account to have given permission, as our Terms of Service require.

12. Your rights in Europe, the UK and Türkiye

If you are in the European Economic Area, the United Kingdom or Switzerland, you may ask for access to your personal data, for it to be corrected or erased, for processing to be restricted, or for your data in portable form; you may object to processing; and you may withdraw consent at any time, which does not affect processing that already lawfully took place. Withdrawing consent for the camera takes one action: revoke the permission in Android settings.

Eyecon's design has an unusual consequence for these rights. We hold no copy of your data whatsoever, so there is nothing for us to retrieve, correct, transfer or delete on your behalf. What the law gives you as a request to a company, the app gives you as a switch on your own device, and Section 9 explains how to use it. Write to us all the same if you want to; we will answer, and we will tell you plainly that we hold nothing.

The processing described in Section 4 happens on your device, wherever you happen to be. There is no international transfer of your data to describe, because there is no transfer of any kind: the app holds no network permission and we operate no servers for it to reach.

You may complain to your data protection authority. In Türkiye that is the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu), and users there have equivalent rights under Law No. 6698.

13. Your rights in the United States

Residents of California, Colorado, Connecticut, Virginia, Utah and other states with comprehensive privacy laws have the right to know what personal information is collected, used, disclosed or sold, to delete it, to correct it, to opt out of its sale, sharing or use for targeted advertising, and not to be treated worse for exercising any of these. We do none of the things you would be opting out of, and we offer no financial incentive in exchange for your information.

In CCPA terms, Eyecon's processing touches one category, and only in a technical sense: biometric information, because camera imagery is analysed. It is examined on your device, never collected, never retained and never disclosed. We collect no personal information of any category, so there is none we could use or disclose beyond the purposes permitted by Cal. Civ. Code § 1798.121(a).

To exercise a right, write to the address in Section 16, yourself or through an authorised agent. We will reply within the time the law allows, though the answer will be that we hold nothing about you.

14. What we tell Google Play

Our Data Safety declaration on Google Play matches this document: no data collected and no data shared. Camera images are declared as processed but not collected, handled ephemerally on the device and never sent off it. Nothing else is declared as collected, because the app has no network permission and therefore no way to send anything. Users can delete everything held on the device by clearing the app's storage or uninstalling it.

15. What Eyecon is not

Eyecon is a convenience. It is not a safety device, a medical device, a security device, or something to depend on where attention genuinely matters. It infers attention from camera images using statistical models, and those models are imperfect by nature. It will sometimes miss the moment you look away and sometimes pause when you have not. Poor light, awkward angles, glasses, hats, face coverings and individual facial differences all affect it, as do phones whose camera or media handling departs from Android's usual behaviour. Some apps publish no usable media session and cannot be controlled at all.

To the fullest extent the law allows, Eyecon is provided as is and as available, without warranty of any kind, express, implied or statutory, including any implied warranty of merchantability, fitness for a particular purpose, accuracy or non-infringement.

To the fullest extent the law allows, Glivy is not liable for indirect, incidental, special, consequential, exemplary or punitive damages, nor for lost data, profits, revenue, goodwill or content, arising from your use of Eyecon or your inability to use it. That includes content you missed, playback that paused or resumed when it should not have, battery consumption, any effect on your device's performance, and any reliance you placed on the app in a situation that required your attention. Where liability cannot lawfully be excluded, it is capped at whichever is greater: what you paid for Eyecon, or ten US dollars.

None of this excludes liability that the law does not permit us to exclude, including for death or personal injury caused by negligence, for fraud, or any consumer right that cannot be waived.

This section restates, for convenience, the disclaimer and the cap set out in Sections 10 and 11 of our Terms of Service. Those Sections are the operative ones and govern if the two are ever read differently.

16. Contact

Glivy, publisher of Eyecon glivyapps@gmail.com

We aim to answer privacy requests within thirty days, and always within whatever period the law sets. Tell us enough for us to act on. Please do not send us sensitive personal information we have not asked for.

17. Changes

We will update this policy when the app changes, when our practices change, or when the law requires it, and the date at the top will change with it. If an update materially affects how the app handles your information, you will see prominent notice in the app before it takes effect, and we will ask for your consent where the law requires it.

Continuing to use Eyecon after an update means you accept the revised policy, except where the law requires your active agreement instead.

18. Governing law

This policy is governed by the laws of the Republic of Türkiye, without regard to conflict-of-laws rules, and the Turkish courts have jurisdiction. This does not take away the protection of mandatory provisions of the law where you live, including any right you have to bring proceedings in your own country's courts under consumer law.

Eyecon is not affiliated with, endorsed by or sponsored by Google LLC, YouTube LLC, or any other service whose playback it may control. All trademarks belong to their respective owners.