1. Scope

This Privacy Policy explains how PrivacyCam (the “App,” “PrivacyCam,” “we,” “us,” or “our”) handles information when you use the PrivacyCam mobile application, its share extension, in-app camera, photo, video, PDF, batch-processing, purchase features, and this legal website.

PrivacyCam is designed for on-device privacy review of photos, short videos, and PDF documents. It can help locate faces, visible people, readable text, email addresses, phone numbers, addresses, website links, payment card numbers, CVV/CVC security codes, QR codes, barcodes, and possible vehicle number plates. It also provides manual blur, pixelation, blackout, rectangle, brush, tracking, and correction tools.

2. Photos, videos, and PDF content

When you choose or capture supported content, PrivacyCam creates working files in the App’s private storage. Detection, review, redaction, preview generation, video-frame analysis, PDF-page rendering, and export rendering occur on your device. PrivacyCam does not upload content or detection results to a server operated by us.

Your original file remains under your control. PrivacyCam creates a separate exported copy rather than modifying the original. A privacy-safe PDF is rebuilt from flattened page images so original selectable text and removable overlay layers are not carried into the new document.

If you share supported content into PrivacyCam from another app, the operating system and PrivacyCam’s share extension temporarily pass the files into the App’s private container so they can be processed.

3. Device permissions

PrivacyCam may request the following permissions only when needed:

• Camera: to take a photo inside PrivacyCam.
• Selected photos and videos: to open media you choose through the system picker.
• Selected documents: to open PDF files you choose through the system document picker.
• Add to photo library: to save an exported privacy-safe copy.
• Local storage: to keep working copies, rendered PDF pages, edits, batch progress, settings, and generated previews on your device.

You can change permissions in your device settings. Some features will not work without the corresponding permission.

4. Information stored locally

PrivacyCam may store the following only on your device:

• working copies of selected photos and videos and rendered PDF pages;
• detected regions, manual marks, video tracks, effect styles, and batch progress;
• optional exact private-data terms you ask the PDF tool to remember, encrypted using platform-provided secure storage;
• generated previews and exports awaiting save or share;
• preferences such as automatic-hide categories, blur strength, pixel size, save format, and onboarding status; and
• a local flag indicating whether PrivacyCam Pro has been unlocked.

When temporary-edit retention is disabled, PrivacyCam attempts to delete obsolete working previews and exports as you replace, discard, or complete work. Some files may remain until you discard the batch, start over, clear the App’s data, or uninstall the App. Device backups managed by Apple, Google, or your device vendor may include app data according to your backup settings.

5. Face data

PrivacyCam processes face data only when you deliberately select or capture a photo or video, open a PDF, or send supported content to the App and initiate a privacy review. Face data consists of pixels in that content that may depict a human face. Detection results retained by PrivacyCam are limited to rectangular coordinates describing where a possible face appears. For video, PrivacyCam also creates timestamped face-location rectangles that allow a redaction area to follow a possible face across sampled frames.

PrivacyCam uses face data only to provide its core privacy-redaction function: showing you where possible faces appear and allowing you to review and apply blur, pixelation, or blackout before exporting a separate copy. PrivacyCam does not use face data to identify or recognize a person, authenticate a user, create a faceprint or biometric template, infer identity or demographic characteristics, build a user profile, track a person between unrelated files, advertise, market, or train machine-learning models. PrivacyCam does not retain or use facial landmarks, facial-expression classifications, or identity information.

Face detection is performed on your device using Google ML Kit. PrivacyCam does not transmit photos, videos, PDF pages, sampled frames, face-location coordinates, or other face-detection results to us, Google, or any other third party. Google states that ML Kit input data and resulting detection output are processed on-device and are not sent to Google servers. ML Kit may separately send limited SDK performance and utilization metrics as described in Section 6, but those metrics do not include the input media or face-detection output.

Face-containing working copies and face-location coordinates are stored only in the App’s private storage so you can review and redact them and, where supported, resume unfinished work. Temporary sampled video frames and detector retry images are deleted after analysis. PrivacyCam does not store face data on developer-operated servers, so server-side retention is zero days.

“Keep temporary edits” is disabled by default. When it is disabled, PrivacyCam attempts to delete obsolete working files as you replace, discard, or complete work. Remaining local project data can be removed by discarding the project or batch, starting over, clearing the App’s data, or uninstalling the App. If you enable “Keep temporary edits,” working data may remain locally until you clear it or uninstall PrivacyCam. Copies you save or share remain at the destination you selected until you delete them. Device backups managed by Apple, Google, or your device vendor may include App data according to your backup settings.

PrivacyCam does not sell, rent, disclose, or share face data. It does not provide face data to advertising platforms, analytics providers, data brokers, information resellers, or other third parties. You can avoid face processing by not selecting content for review, revoke photo or camera permissions in device settings, discard current work, delete saved exports, clear App data where supported, or uninstall PrivacyCam.

6. On-device machine learning and limited diagnostics

PrivacyCam uses on-device components, including Google ML Kit for features such as face, text, QR-code, and barcode detection, plus an embedded number-plate model. Google states that ML Kit input data such as images and text, and the resulting detection output, are processed on-device and are not sent to Google servers.

Google also states that ML Kit sends limited performance and usage metrics to Google. Depending on platform and SDK version, these metrics may include device and application information, a per-installation identifier, performance data, API configuration such as image format or resolution, feature event types, and error codes. Google uses these metrics for diagnostics, analytics, maintenance, improvement, and abuse prevention. Google states this diagnostic data is encrypted in transit and is not transferred to third parties by ML Kit.

These diagnostics are handled by Google under the Google Privacy Policy. Learn more in Google’s ML Kit Terms & Privacy disclosure.

7. Purchases

The optional PrivacyCam Pro lifetime purchase is processed by Apple through the App Store or by Google through Google Play. We do not receive or store your full payment-card details. The App receives product information, transaction status, and store verification data so it can unlock Pro access. A local entitlement flag may also be stored on your device.

Apple and Google handle purchase information under their own privacy policies and store terms.

8. Metadata and exported copies

PrivacyCam is designed to create new rendered exports without carrying forward common original metadata. PDF exports are flattened and checked for a remaining selectable text layer. The App may stop an export when this process cannot be verified. However, operating systems, destination apps, file formats, screenshots, cloud services, and sharing platforms may create or attach their own metadata. Review the final file and destination before sharing sensitive content.

9. What we do not do

PrivacyCam does not require an account and does not include developer-operated advertising, behavioral profiling, or cross-app tracking. We do not sell personal information. We do not use your content or face data to train our models. We do not have access to the private working copies stored inside the App on your device.

10. This website

This is a static website. It does not contain a contact form, advertising scripts, or developer-operated analytics cookies. If it is hosted through GitHub Pages, GitHub may process technical information such as IP addresses, browser information, and server logs under the GitHub General Privacy Statement.

If you contact us by email, we receive the email address and information you choose to provide. We use it to respond, investigate issues, prevent abuse, and keep necessary support records. Do not send unredacted sensitive images or payment credentials.

11. Sharing and disclosures

We do not share your content or face data because we do not receive it. Limited technical or transaction information may be processed directly by platform and SDK providers as described above. We may disclose support communications if required by law, necessary to protect rights or safety, or involved in a business transfer, subject to applicable law.

12. Security and your choices

We design PrivacyCam to minimize data movement, but no device, software, or storage system is completely secure. Keep your device updated and protected with a passcode. Carefully review every automatic detection and final export. You may revoke permissions, discard batches, delete exported copies, clear app data, or uninstall PrivacyCam at any time.

13. Children

PrivacyCam is a general-audience utility and is not directed to children under 13. We do not knowingly collect personal information directly from children. A parent or guardian should supervise a minor’s use where required by local law.

14. Privacy rights

Depending on where you live, you may have rights concerning personal information. Because we do not operate accounts or receive your content or face data, we generally cannot access, export, correct, or delete content stored only on your device. For support emails or other information we directly hold, you may contact us to request access, correction, or deletion, subject to legal exceptions.

15. Changes to this policy

We may update this policy when PrivacyCam’s features, vendors, legal obligations, or distribution methods change. We will change the effective date and, when appropriate, provide notice in the App or on this website. Continued use after an update means the revised policy applies to future use.

16. Contact

Questions or privacy requests can be sent to: