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 launch principle: screenshot image files stay on your device. Bloop uses local text recognition first, then uses extracted text when you choose AI processing.
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 may be analyzed
When you tap Bloop it or automatic screenshot processing runs, Bloop may send extracted text and lightweight metadata to Bloop's server. That text is used to create summaries, categories, and actions such as calendar events, reminders, notes, links, and draft replies.
Why extracted text matters
Extracted text is smaller and more focused than an image. It lets Bloop understand the useful parts of a screenshot without sending the image file itself.
Text can still be personal if the screenshot contains personal information. That is why Bloop's privacy policy explains what is processed, which providers are used, and what operational records may be stored for credits, rate limits, subscriptions, and abuse prevention.
Security and safety
Bloop uses practical safety boundaries: screenshot images stay on device in the launch build, OCR starts locally, AI processing uses extracted text when needed, and calendar or reminder actions can be checked, edited, or undone after creation.
Operational systems may keep non-content records for reliability, rate limits, subscriptions, credits, usage guardrails, and abuse prevention. Bloop's server is designed not to store screenshot images, OCR text, AI prompts, or AI responses as product data.
What users can control
- Photos permission for screenshot discovery and local text recognition;
- Calendar and Reminders permissions only when those actions are used;
- automatic processing settings;
- 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.