Pixel Hollow legal notice
Last updated: 2026-10-01
Pixel Hollow should be understandable from its screens: if a control submits a note, photo, or identifier to a service you do not already expect, that control must say so. It is provided by Lior Friedmann.
Lior Friedmann
Israel
Information you enter is processed to provide the features visible in the app. Drafts, lists, settings and similar objects live in the app sandbox. Deleting an item in the UI removes that record from the live database. Uninstalling Pixel Hollow removes data stored only in its local container.
The app may make network requests to retrieve app content or configuration, communicate with Apple platform services, and open support or legal resources. A feature that sends user-entered information to an external service should identify that behavior in its interface. App Store privacy disclosures for the submitted version provide the applicable data categories.
Viewing this page in a browser is separate from using the app. The page does not require an Pixel Hollow account.
Pixel Hollow relies on the OS sandbox, transport security for any HTTPS calls, and Apple's signing/distribution channel. You still need a device passcode or biometric lock to protect local records at rest as well as the OS allows.
Use an available in-app deletion control to remove content created in the app. Uninstall the app to remove data stored only in its local container. If you believe a build is collecting more than this notice describes, include the build number from the app's about screen when you write to the contact address.
We may update this policy. Changes will be posted here with an updated date. The heading date is the publication date of this HTML, not necessarily the first day a binary used the same practices.
Email: licufugusic589@gmail.com
Lior Friedmann