InPixel: HiLight Controller
InPixel: HiLight Controller
Last updated: September 29, 2026
App: InPixel
Google Play name: InPixel: HiLight Controller
Package name: com.krepelstudio.inpixel
Developer: Krepel Studio
Developer website: krepelstudio.com
Contact: Krepelstudio@gmail.com
InPixel is an Android application for compatible Google Pixel devices that provides configurable HiLight indications for calls, notifications, charging, reminders, media activity, camera and microphone activity, system events, and other supported device states.
InPixel is designed to perform its core HiLight processing locally on the user's device. The app does not require a Krepel Studio account and does not use a Krepel Studio cloud service to control HiLight.
Depending on which features the user enables, InPixel may access the following information on the device.
If the user enables app-notification HiLight features, InPixel requires Android Notification Access. Android may make notification information available to the notification listener service.
InPixel uses notification information only as needed to identify the source application, determine whether a relevant notification is active or removed, and trigger the configured HiLight behavior. Notification data is processed locally for this purpose and is not sent to Krepel Studio servers.
If the user enables contact-specific call colors or related caller features, InPixel may request access to contacts and call-state information and may use Android's call-screening role where required.
This information is used locally to match an incoming call or missed-call event with a configured contact or caller category and display the corresponding HiLight effect.
InPixel is not designed to upload the user's address book, phone numbers, or call information to Krepel Studio servers.
If the user enables calendar-event HiLight features, InPixel may request read access to the device calendar.
Calendar information is used locally to determine when a configured event is approaching and to trigger the selected HiLight indication. InPixel does not need write access to the calendar unless that functionality is explicitly added in a future version.
InPixel may store user-created reminder settings, selected colors, times, and related preferences locally on the device.
Where Android requires special alarm scheduling access for exact reminders, InPixel may request that access only when the related feature is enabled.
InPixel may read Android battery and charging information, such as battery level and charging state, to provide Charging Progress and configured battery alerts.
This information is processed locally.
If the user enables Music Visualizer behavior, InPixel may observe supported Android media-session or playback-state information to determine whether media is playing.
The approved design does not require recording the audio itself merely to determine whether music is active.
If Camera Active or Microphone Active indications are enabled, InPixel may observe supported Android system activity state indicating that the camera or microphone is in use.
The approved design is intended to detect activity state only. InPixel is not intended to capture photos, video, microphone audio, or the content being recorded merely to provide the HiLight indication.
For supported applications that expose ongoing progress through Android notifications, InPixel may read the available progress state to display a HiLight progress indication.
InPixel does not need access to the contents of the transferred files merely to display this progress. Availability and accuracy depend on the information published by the source application.
InPixel may observe supported system states such as volume changes and Ring, Vibrate, or Silent mode to trigger the selected built-in HiLight effect.
InPixel uses a local Wireless Debugging connection on compatible Pixel devices to enable HiLight control that is not available to an ordinary third-party application through a standard runtime permission.
The user completes the Android Wireless Debugging pairing process and enters the Android-provided pairing code into InPixel. The connection is local to the device/network environment and does not require a Krepel Studio server.
Pairing credentials and connection information are intended to be stored only in app-private device storage and protected using Android platform security mechanisms where applicable. They must not be transmitted to Krepel Studio servers.
If Android removes or revokes the Wireless Debugging authorization, the user may need to reconnect.
Depending on the enabled features and final implementation, InPixel may request or use Android permissions or special system access for:
local network and Wireless Debugging connectivity;
Notification Access;
posting InPixel's own notifications;
contact access for contact-specific caller features;
phone/call-state access and the Android call-screening role where required;
calendar read access;
exact alarm scheduling where required for user-created reminders;
network-state detection;
restarting supported scheduled behavior after device reboot where required.
InPixel requests optional access only when it is needed for the corresponding feature. Denying an optional permission may disable that feature without preventing unrelated features from working.
The final published policy must match the exact permissions present in the release build.
InPixel may store the following information locally on the device:
enabled or disabled feature settings;
selected applications and their HiLight colors;
selected contacts and their HiLight colors;
battery-alert preferences;
reminder, alarm, and calendar-related preferences;
theme and language preferences;
HiLight connection state and locally protected pairing credentials;
Pro entitlement state required for app functionality.
This information is used to provide the configured features. InPixel is not designed to upload these settings to a Krepel Studio server.
Users can remove locally stored app data using Android's application settings or by uninstalling InPixel.
InPixel uses Google Play Billing for an optional one-time Lifetime Pro purchase.
Purchases are processed by Google Play. Krepel Studio does not receive or store the user's payment-card details through InPixel. The app may receive and process purchase status and entitlement information necessary to unlock Pro features and restore purchases.
Google's handling of purchase and account information is governed by Google's own privacy terms and policies.
InPixel does not include advertising in the approved product design.
AdMob and the User Messaging Platform (UMP) included in the reusable development template are to be removed from the InPixel release build. InPixel is not intended to use advertising identifiers or advertising SDKs.
Krepel Studio does not sell personal information obtained through InPixel.
The approved architecture does not require notification content, contacts, call information, calendar information, HiLight commands, or Wireless Debugging credentials to be sent to a Krepel Studio server.
Google Play services involved in purchase processing operate under Google's own terms and privacy policies.
InPixel is designed to minimize access to data and process HiLight-related information locally whenever possible.
Sensitive local credentials should be protected using app-private storage and Android security mechanisms such as the Android Keystore where applicable.
No method of software or device storage can be guaranteed to be completely secure, but Krepel Studio aims to use reasonable safeguards appropriate to the data processed by the application.
Users control optional Android permissions and special access through Android system settings.
Users may:
enable or disable individual InPixel features;
revoke Notification Access, Contacts, Calendar, call-related access, local-network access, or other optional permissions through Android settings where supported;
remove configured applications, contacts, reminders, and other locally stored settings;
clear InPixel's application data;
uninstall the application;
contact Krepel Studio with privacy-related questions.
Revoking a permission may prevent the related feature from working until access is granted again.
Krepel Studio may update this Privacy Policy when InPixel functionality, permissions, third-party components, legal requirements, or data-processing practices change.
The current version will be published through Krepel Studio's official website or the Privacy Policy URL listed in Google Play.
For privacy questions related to InPixel, contact:
Krepel Studio
Website: https://krepelstudio.com
Email: Krepelstudio@gmail.com