Creepy Eyes · Privacy
Privacy policy.
This policy describes the current Creepy Eyes iPhone app and its direct Bluetooth Low Energy interaction with compatible Creepy Eyes hardware.
Effective date: September 10, 2026
What the app does
Creepy Eyes is a native iPhone application used to discover, connect to, and control compatible Creepy Eyes hardware over Bluetooth Low Energy (BLE). Nearby device names, identifiers, connection state, and command state may be processed locally on the iPhone as needed to perform discovery and control.
Accounts and cloud services
The current app does not require user registration, login, or an Arroyo Cooperative cloud account for normal operation. The current control architecture does not require a remote command server or web service to send normal control commands to Creepy Eyes hardware.
Settings stored on the iPhone
Motion and performance settings are stored locally on the iPhone using Apple's local app-storage mechanisms. These settings include values such as blink timing, wink timing, Creepy motion timing and speed, and performance duration.
Analytics and advertising
The current Creepy Eyes architecture does not depend on an analytics backend for app operation and does not require an advertising service to control the hardware.
Bluetooth
Bluetooth access is necessary for the app's core purpose. Creepy Eyes uses Apple's CoreBluetooth framework to find and communicate with compatible nearby hardware. Bluetooth-related information is used for device discovery, connection, and command delivery.
Team Creep Mode
Team Creep Mode allows the app to connect to and control multiple compatible hardware units during the current app session. Enabling Team Creep Mode does not create an account or unlock a paid service.
External websites
The Creepy Eyes project, support, and GitHub links may open websites outside the app. Those sites may have their own logging and privacy practices. This policy is scoped to the Creepy Eyes iPhone app itself.
Changes to this policy
This policy will be updated if the shipping app's data handling or service architecture changes. The goal is to describe what the released app actually does rather than make broader claims than the implementation supports.