Privacy Policy for Magic Window

Effective Date: July 28th 2026

Developer: David Diggles

1. Core Operating Principle

Magic Window operates strictly as a local orchestration engine. To function, the application requires situational awareness of its operating environment. Any sensitive data or device state accessed via Android permissions is consumed entirely on-device to execute local calculations.

No user data, device data, or permission-derived telemetry is ever shared, sold, or transmitted to third-party servers.

2. Data Access and Usage

The application requests access to specific device data streams solely to maintain geometric continuity and execute the local pilot engines. All of this sensing happens live on the device.

• Camera (Visual Sensing): The app uses the camera lens strictly as a light and motion sensor to measure visual activity. It does not take photographs, record video, or save any images.
• Microphone (Acoustic Sensing): The app uses the microphone to measure the general noise level and acoustic energy of the room. It does not record conversations, save audio files, or listen to spoken words.
• Nearby Devices (Bluetooth Sensing): The app senses Bluetooth radio waves to count nearby smart devices and measure signal strength to understand room density.
• Location (Wi-Fi Sensing): The app looks at invisible Wi-Fi signals to measure network density. Because reading Wi-Fi states can technically reveal proximity, the Android operating system requires the "Location" permission. The app does not track your physical geographic location or map data.
• Phone (Cellular Sensing): The app requires standard Android telephony permissions (e.g., READ_PHONE_STATE) to measure the strength and geometry of local cellular towers. The app does not read your phone number, look at your contacts, or monitor your phone calls. It only reads raw radio frequency energy.

3. Zero External Transmission and Sharing

This application operates within a strictly decoupled architecture:

• We do not integrate third-party advertising SDKs.
• We do not use external crash-reporting or telemetry analytics.
• Data accessed by the application never leaves the physical device boundary unless explicitly routed by the user to their own self-hosted infrastructure.

4. Data Retention and Deletion

Because no data is transmitted to external servers, no user data is retained by the developer. All configuration data and permission states remain on the physical device.

Data Deletion: There are no remote accounts associated with this application. Users can instantly purge all application data, configurations, and historical states by utilizing the standard Android system tools: navigating to Settings > Apps > Magic Window > Storage > Clear Data, or by uninstalling the application.

5. Contact Information

For legal notices, compliance audits, or privacy inquiries, contact the developer at:

• Email: diggles@bincrow.net
• Address: 2/33 Sarah St, Annerley, QLD 4103, Australia