Privacy Policy

Summary

BlurPOV is built so your video never has to leave your device. We don't run a server, we don't have an account system, and we don't collect a profile of you. Detection, identification, and rendering all happen locally on your iPhone. This page explains the details.

What we process

BlurPOV processes the following categories of data only on your device, only for as long as needed to deliver the feature you asked for:

• Camera frames. When you use live mode, the camera feed is analyzed in memory to detect and blur faces. Frames are not recorded unless you tell the app to capture them.
• Videos you import. When you pick a clip from Photos or Files, BlurPOV reads the video, scans it for faces, and writes a redacted output back to a file you choose to keep.
• Face crops and embeddings. While scanning, BlurPOV creates small thumbnail images and numeric face embeddings to cluster appearances of the same person. These exist in memory and in temporary files for the duration of your session.
• Manual blur regions. If you record drag-while-playing blurs, the rectangles and timestamps you draw are stored alongside your in-progress edit.

Face data

Because BlurPOV's purpose is to detect and blur faces, this section spells out exactly how the app handles face data.

• What face data is collected. While you are scanning a clip or using live camera mode, BlurPOV generates face bounding boxes, small face thumbnail crops, and numeric face embeddings (feature vectors used to tell appearances of the same person apart). It does not collect names, identities, demographic information, or any biometric template intended to identify a specific real-world person.
• How face data is used. Face data is used solely to (1) detect faces so they can be blurred, (2) cluster appearances of the same person across a video so you can make one redact-or-reveal decision per individual, and (3) render a blurred output video. It is never used for advertising, analytics, profiling, model training, or identification against any external database.
• Sharing and disclosure of face data. Face data is not shared with any third party. It is not transmitted off your device. The app contains no networking code that uploads face data, and no third-party analytics, advertising, or identity-matching SDK has access to it.
• Where face data is stored. Face data exists only on your iPhone — in memory while you are editing, and in your device's temporary directory for intermediate files created while scanning or rendering. There is no server, no account, and no remote storage of face data.
• How long face data is retained. Face data is retained only for the duration of your editing session. Bounding boxes, thumbnails, and embeddings are released from memory when you finish or dismiss the edit or close the app. Temporary files are removed by iOS or when you close the project or reinstall the app. The only artifact that persists is the rendered output video you choose to save to your Photos library, which contains blurred faces — not raw face data.

What we don't do

• We do not upload your videos, frames, faces, or embeddings to any server.
• We do not maintain a face database or attempt to match your faces against any external identity service.
• We do not require an account, email address, phone number, or login.
• We do not sell, rent, or share data with advertisers or data brokers.
• We do not include third-party analytics, advertising, or tracking SDKs in the app.

Permissions BlurPOV asks for

• Camera. Required for live redaction mode. The feed is processed locally and is not transmitted.
• Photo library (read). Required to import a video you select for redaction. Only the asset you pick is read.
• Photo library (add). Required to save a rendered, redacted video back to your library.

You can change these permissions at any time in iOS Settings → BlurPOV. Denying a permission disables the feature that uses it but does not affect anything else in the app.

Storage and retention

Source clips you import and intermediate files BlurPOV creates while scanning or rendering are written to your device's temporary directory. iOS may delete this directory on its own; you can also clear it by closing the app or reinstalling. Output videos saved to your Photos library remain there until you delete them — they're yours.

Children

BlurPOV is intended for general audiences. Because the app does not collect personal data, there is no children's data to protect against misuse on our side. If you are a parent or guardian using BlurPOV to redact footage that includes a minor, the redacted output stays under your control on your device.

Security

Because data does not leave your device, the practical security of your BlurPOV content depends on the security of your device — your passcode, Face ID or Touch ID, iCloud settings, and how you choose to share any rendered videos. We recommend keeping iOS up to date.

Crash reports and diagnostics

If you have opted in to share diagnostics with Apple in iOS Settings, Apple may collect anonymized crash logs that include the BlurPOV process. Those logs are governed by Apple's privacy policy, not ours, and they do not contain your video content.

Changes to this policy

If we change how BlurPOV handles data — for example, by introducing an optional cloud feature — we will update this policy and change the effective date at the top. Material changes will be surfaced inside the app before they take effect. Continuing to use BlurPOV after a change means you accept the updated policy.

Contact

Questions about this policy or how BlurPOV handles data? Email support@blurpov.app.