ZapBlur Privacy Policy

Developer: grayforge · Contact: grayforge.dev+zapblur@gmail.com · Last updated and effective: October 23, 2026 (version 1.0)

0. Plain-language summary

Stays on your device
Photos, face positions, areas you cover by hand and your other edits. They never leave your device.
Sent to Google Firebase
Usage stats and crash reports (app version, device model, OS version, etc.) go to Google Firebase. They do not include photos, faces or location.
Sent by ML Kit (Android)
Google ML Kit, which finds the faces, may send device and app information, performance metrics and a per-installation ID to Google on its own. The app cannot turn this off.
Not used
Ads, accounts, watermarks, advertising identifiers

Your photos and face data never leave your device. Usage stats and crash reports (app version, device model, OS version) are sent to Google Firebase. Areas you cover by hand, and what is inside them, are not sent to a server either.

On Android, the face detection library (Google ML Kit) may send device information, app information, performance metrics and per-installation identifiers to Google on its own. The app cannot turn this off. According to Google's public documentation, photos and face data are not part of it. The iOS app does not use this library.

1. Who we are

ZapBlur is made by grayforge, an independent one-person studio. grayforge decides how the information described here is handled (the controller), and one person handles all of it. Privacy contact: grayforge.dev+zapblur@gmail.com. This policy covers the ZapBlur app (iOS, Android) and its information web pages.

2. What we process

a. On your device only: the photos you pick, the faces found in them, the areas you cover by hand (their position, size and the content inside them), your other edits (effect, strength) and temporary working copies. We do not receive them. App settings (such as the default effect) also stay on your device.

Picking and saving: you pick photos with your phone's own photo picker, so the app gets only the photos you select and does not ask for access to your whole library. On iPhone and iPad the app asks only for permission to add the finished photo to your library. If a photo you pick is kept in iCloud Photos, iOS may download it to your device first; Apple does that under your iCloud settings, not us. The saved photo is a new file and your original is not changed. It is written afresh from the pixels and carries no location, camera or other shooting information. If you tap Share, your phone's share sheet sends the photo wherever you choose, and that app's own policy applies; ZapBlur sends it nowhere.

b. Sent to Google Firebase (Analytics and Crashlytics): an install ID that the Firebase SDKs create (Firebase app instance ID, Crashlytics installation ID); feature-use records in coarse form, such as a range for the number of faces, the effect type and how long an edit took, plus the standard events Firebase records itself, such as first open and session start; crash information (the crash and its stack information, the app version, the step the app was on, and the same coarse traits of the photo, such as its format and size and resolution ranges); device information (device model, OS version, language and region, memory class, thermal state, low-power mode, and on Android a free-storage range); and the approximate country that Google works out from your IP address. Not included: photos, faces, location, coordinates, the position or content of areas you cover by hand, names or contact details. The app cannot tell what you cover by hand (a face, a license plate, a document, text) and does not record it. Only how you added an area (tap detect or shape), its shape (oval or rectangle) and whether tap detect found a face (yes or no) may be included.

c. May be sent (Android app only): device information (manufacturer, model, OS version), app information (package name, app version), per-installation identifiers, and performance and usage metrics (processing time, settings such as image format and resolution, error codes), sent by Google ML Kit. According to Google's public information, photos and the faces it finds are not part of it. The app cannot turn this off. The iOS app does not use ML Kit; it finds faces with Apple's on-device Vision framework.

d. Information you send: the sender address and body of an email. Settings > Contact / feedback opens a sheet where you choose Bug report, Question, Suggestion or Other, and then an email draft. A bug report's draft ends with items pre-filled (app version and build, OS, device model, language, memory size, remaining storage space, and whether the phone was hot or in battery saver) that you can read, edit or delete before sending; the other kinds add nothing. No photos, location or analytics IDs are attached. The sheet also has a button that copies our email address.

e. The "More apps" page: Settings > More apps shows grayforge's page of apps (grayforge.app/products/) inside the app. Opening it makes ordinary web requests to grayforge.app, which GitHub Pages hosts, and to Google Fonts, which serves the page's fonts, so those services see your IP address and device type as they do for any web page, under their own privacy statements. Scripts are turned off in this view, and the app sends no photo, face data or install ID with the request. Links on that page to a store open in the store app or your browser, not in the app.

f. Web pages: no cookies, analytics or requests to other sites. The pages are hosted on GitHub Pages, which may keep ordinary server logs (such as IP address and time of request) under GitHub's own privacy statement.

g. Not processed: name, contact details (apart from an email you send us), accounts, precise location (GPS), advertising identifiers (IDFA, Android advertising ID) and payment information. Version 1.0 has no purchases and shows no ads.

3. Purposes and legal basis

Purposes: understand feature use to improve the app, diagnose and fix crashes, answer your messages. Basis for item 2b: our legitimate interest in diagnosing crashes and improving the app, weighed against your privacy: the data is coarse, tied to a random install ID and never includes photos, faces or location, and you can object at any time by emailing us (section 10). Item 2c is sent by Google itself as part of providing the library; Google's own policies govern it. Support emails are processed because you sent them. The app works the same if you decline.

4. Retention and deletion

On device: until you delete the app. Temporary files are deleted when you save or exit, and any left over on the next launch. Firebase Analytics events: up to 14 months. Crashlytics crash data: 90 days. After that, Google deletes it from its systems. Support emails: kept only as long as needed to deal with your message, then deleted. Electronic files are deleted so they cannot be recovered or reproduced; where the law requires us to keep something, we keep it for that period.

The app has no setting to stop usage stats and crash reports at the moment. Deleting the app ends use of the install ID on the device, and you can ask us to stop or delete by email (section 10). Data already sent is deleted when its retention period ends. The data is tied to a random install ID, not to your name or email, and the app does not show you that ID, so we usually cannot tell which data is yours. If you want to ask about deletion anyway, email us (section 10) and we will tell you what is possible.

5. Processors and international transfers

Google LLC (Firebase Analytics, Crashlytics) processes the items in 2b for us. Data may be processed in the United States and other countries where Google operates. It is sent over the network, encrypted in transit, while you use the app. Purpose: usage stats and crash diagnosis. Retention: section 4. To stop it, see section 7. https://firebase.google.com/support/privacy

Google ML Kit (Android only) is described in 2c: https://developers.google.com/ml-kit/android-data-disclosure

Transfer basis: disclosed processing and storage by a processor (Korean PIPA Art. 28-8). For EU/EEA/UK residents, see Appendix B. We do not sell personal information, and we do not provide it to third parties except as the law requires.

6. Identifiers

The app creates an install ID and sends it with events and crashes. No web cookies. Deleting the app ends use of the ID on the device. We do not use advertising identifiers and do not show an App Tracking Transparency prompt.

7. Stopping it and your rights

Stopping: the app has no setting for usage stats and crash reports at the moment; deleting the app ends use of the install ID on the device. You may request access, correction, deletion, restriction or objection by email (see section 10); a legal guardian may do so too. We answer within the period the law requires (10 days under Korean law). Because there are no accounts, we usually cannot match data to a person; we will tell you what we can find and what we need from you to check it is yours. Korean remedies: Personal Information Infringement Report Center privacy.kisa.or.kr (118), Personal Information Dispute Mediation Committee kopico.go.kr (1833-6972).

8. Children

ZapBlur is not directed to children under 14 (Korea), 13 (US) or 16 (EU, as applicable), and we do not ask for or verify age. We do not knowingly process their information and will delete it if we learn of it. Photos and face data, including children's faces in photos, never leave the device. Contact us by email (section 10).

9. Security

Photos and faces are processed on the device, and the app never uploads them by itself. The app uses the network only for: the Firebase and ML Kit libraries described above; iOS downloading a photo you picked from iCloud Photos (item 2a); the "More apps" page (item 2e); and the links you tap (this policy, a store page, an email draft), which open in your browser or email app. Firebase traffic is encrypted in transit. Photos, faces, location, coordinates and areas you cover by hand are never put into analytics or crash data; the project's automated checks look for this. One person handles personal information and has access to the Firebase project. No method of transmission or storage is completely secure, so we cannot promise absolute security.

10. How to contact us

To: grayforge.dev+zapblur@gmail.com. Feedback - Settings > Contact / feedback, subject "[ZapBlur] [Bug]", "[ZapBlur] [Question]", "[ZapBlur] [Suggestion]" or "[ZapBlur] [Other]"; a bug report's body ends with app version, OS, device model, language and the phone's memory, remaining storage, heat and battery saver state. Privacy request - subject "[ZapBlur] Privacy request", body: request type (access, correction, deletion, restriction, objection), app version and OS, details. You do not need to send photos.

11. Changes

This is version 1.0, effective October 23, 2026. We post changes at the top of this page with the effective date, and announce important changes, such as a new kind of information being collected, at least 7 days before they take effect.

Appendix. Features that will not become paid (as of 2026-10-09)

(1) Safety features that will not become paid even if paid features appear later: blocking very weak strengths, covering detected faces by default, removing shooting info when saving. (2) The photo features in version 1.0 (automatic detection, per-face on/off, cover by hand, three effects and strengths, zoom, undo, save and share) are not planned to become paid at present. If that changes, we will announce it in advance in the app and on this page. (3) Every change to this list or to the plan in (2) is logged with a date.

Appendix B. EU/EEA/UK residents

Controller and contact: section 1. Legal basis: our legitimate interest (GDPR Art. 6(1)(f)) in diagnosing crashes and improving the app; you can object at any time by emailing us (section 10). Recipient: Google LLC as processor. Transfer to the United States and other countries: Google relies on the European Commission's Standard Contractual Clauses and, where it applies, its certification under the EU-U.S. Data Privacy Framework. Rights: access, rectification, erasure, restriction, objection, portability; you may lodge a complaint with your supervisory authority. The data in item 2b is collected automatically while you use the app; it is not required by law or by a contract with you. No automated decision-making.