bitpop privacy

The short version

bitpop does not collect, transmit, sell, or share personal data. It has no account, analytics, advertising, tracking, backend, or third-party SDK. Camera processing happens on your iPhone.

Camera and photos

Live camera frames are processed on the device to produce the preview, smart palette, and finished image. Source images, rendered images, and scene-derived palette data are not uploaded.

Camera permission is required to shoot. Photos add-only permission is used to save a capture directly to Apple Photos. bitpop does not request broad permission to read or browse your Photos library.

Data stored on the device

bitpop keeps your custom looks and a bounded local History of recent editable captures. A History item can contain a local identifier, timestamp, Photos save identifier or placeholder, rendering recipe, editing proxy, and thumbnail. History is limited to 32 captures and 256 MiB and removes older items as needed.

Custom looks remain on the device unless you explicitly use the system share sheet to export a look file. Import happens only after you choose a file with the system file picker.

Diagnostics and required-reason APIs

bitpop measures local elapsed time to help the camera manage frame performance. Those measurements are not used to identify you, are not persisted as analytics, and are not transmitted. The app's privacy manifest declares the system boot-time API reason used for elapsed-time measurement.

Deleting data

Deleting bitpop removes its local History and custom looks. Photos already saved to your Photos library are managed separately by you in the Photos app and are not deleted when the app is removed.

Children and changes

Because bitpop collects no personal data, it does not knowingly collect personal information from children. If this policy changes, the updated policy will be posted here with a new date.

Contact

Questions about privacy can be sent to bitpop@strangeloop.nl.