A private-first approach to organizing screenshots
Screenshots can contain almost anything: appointments, addresses, receipts, messages, health details, names, and account information.
That is why Bloop is designed around a simple principle: screenshot image files and extracted text stay on your device. Recognition, categorization, and summaries run locally.
What stays on device
In the launch build, screenshot image files are used locally for previews, thumbnails, and text recognition. Bloop does not upload screenshot image files to Bloop's analysis server.
What is processed
When you tap Bloop it, Bloop reads the selected screenshot locally. Extracted text stays on the device and is used to create deterministic summaries, built-in categories, and actions such as calendar events, reminders, notes, and links.
Why extracted text matters
Extracted text makes screenshots searchable and lets local rules identify useful dates, links, and category keywords without sending either the text or image to a server.
Text can still be personal if the screenshot contains personal information. Bloop's privacy policy explains what is processed locally and how Apple handles subscription purchases and restoration.
Security and safety
Bloop uses practical safety boundaries: screenshot images and extracted text stay on device, and calendar or reminder actions can be checked, edited, or undone after creation.
Bloop does not use a screenshot analysis server. Apple handles subscription purchases and restoration, while the app stores the local trial date and cached entitlement needed for offline access.
What users can control
- Photos permission for screenshot discovery and local text recognition;
- Calendar and Reminders permissions only when those actions are used;
- which screenshots or batches to process manually;
- local Bloop data deletion;
- which writable iOS calendar receives new event actions.
For the detailed policy, read the Bloop Privacy Policy, or the Bloop security and safety guide.