Effective date:10 July 2026
Contact email: jp0916780@gmail.com
PrivyMark is a privacy screenshot editor that helps users hide private information in screenshots and images before saving or sharing a new edited copy.
This draft must be reviewed before release and hosted at a public URL for Google Play. The final version must match the exact build that is submitted to Google Play, including any advertising, analytics, crash reporting, or other third-party SDKs included in that build.
PrivyMark processes selected images on the user's device.
PrivyMark does not upload selected images to a developer server for editing.
Original images are not deleted, replaced, or modified by default.
Edited outputs are saved as new copies unless the user explicitly chooses to overwrite an app-exported copy.
Export history is stored locally on the device.
If advertising is enabled in the version installed by the user, third-party advertising partners may collect or receive limited device, app activity, and ad interaction data as described below.
PrivyMark can access images only when the user chooses an image through the Android Photo Picker, opens a supported image from the system file/photo interface, or shares an image from another app into PrivyMark.
Selected images are used to provide editing features, including redaction, annotation, enhancement, preview, saving, and sharing. The app stores temporary imported copies and exported edited copies as needed to provide these features.
PrivyMark does not use selected images for advertising targeting, user profiling, or training machine learning models.
PrivyMark may use on-device text recognition and face detection to suggest areas that may contain private information, such as:
Faces
Phone numbers
Email addresses
URLs
Possible ID-like text
Detection results are suggestions only. Users should review the image before saving or sharing because automatic detection may miss private information or mark non-private content.
By default, saving an edit creates a new image copy and leaves the original image unchanged.
If a user opens an image that was previously exported by PrivyMark and then edits it again, the app may offer a choice between:
Creating a new copy.
Overwriting that app-exported copy.
PrivyMark should not overwrite the user's original source image unless the user explicitly chooses an overwrite flow that applies to an app-exported copy.
PrivyMark may store local export history records on the device, including:
Export time.
Output image URI or file reference.
Output type, such as new copy or overwritten app-exported copy.
Original image status, such as original unchanged.
A short summary of edit actions.
History records are stored locally in the app database. They are not uploaded by PrivyMark.
Users may clear history records in the app. If the app offers a separate delete-exported-images action, that action may delete exported image files referenced by history records. Clearing only the history records does not necessarily delete exported images.
Debug or test versions of PrivyMark may include local diagnostics to help troubleshoot image import, decoding, saving, or device compatibility issues. Diagnostics are stored locally on the device and are intended for testing. Release builds should not expose debug diagnostics unless the feature is intentionally included and disclosed.
When the user chooses to share an edited image, PrivyMark sends the exported image to the Android system share sheet. The destination app or service selected by the user handles the image according to its own privacy policy.
PrivyMark may include advertising in a future or specific release version. If the version installed by the user contains ads, the app may display a "Contains ads" label on Google Play.
If ads are enabled, third-party advertising partners, such as Google AdMob or another ad network selected before release, may collect, receive, or process data needed to show ads, measure ad performance, prevent fraud and abuse, and comply with legal requirements. Depending on the ad SDK and the user's device settings, this data may include:
Advertising ID or other device identifiers.
Approximate location derived from IP address or ad network signals.
App interactions related to ad display, views, clicks, and frequency capping.
Device and app information, such as device model, operating system version, app version, language, and network information.
Crash, diagnostic, and performance data related to ad delivery.
Advertising partners may use this data for advertising or marketing, ad measurement, fraud prevention, security, compliance, and personalization where allowed by law and user consent settings.
PrivyMark does not send the user's selected images to advertising partners for ad targeting. Ads should not require access to the user's selected screenshot or edited image content.
Where required, the app may ask for consent before showing personalized ads. Users may also be able to reset, delete, or limit use of the Android Advertising ID through device settings, depending on Android version and region.
If the released version does not include an advertising SDK or display ads, this Advertising section may not apply to that version. The Google Play Data safety form and Ads declaration must be updated to match the actual release build.
The current intended first release does not include a separate analytics SDK or cloud crash reporting SDK.
If analytics or crash reporting is added later, this policy and the Google Play Data safety form must be updated before release to describe the data collected, the purpose of collection, whether data is shared, retention, and deletion options.
PrivyMark avoids broad or sensitive permissions where possible.
The app does not request access to contacts, SMS, call logs, precise location, microphone, camera, accessibility services, or background gallery scanning for its core editing features.
On older Android versions, the app may request storage-related permission only when needed to save edited images to device storage.
If advertising is added, the app may require network access for loading ads. Any permission changes must be reviewed before release.
Local temporary files, local history records, and exported images may remain on the user's device until the user deletes them, clears app data, uninstalls the app, or uses in-app deletion features where available.
Uninstalling the app or clearing app data may remove app-private files and app database records. Exported images saved to shared media storage may remain on the device unless the user deletes them from the system gallery/file manager or uses an in-app delete-exported-images action, if available.
Data processed by third-party advertising partners, if ads are enabled, is handled according to those partners' policies and controls.
PrivyMark is intended as a general utility app and is not directed specifically at children. The app should not be listed as targeting children unless the final product, store listing, ads configuration, and content rating are reviewed for the applicable child-directed app requirements.
Privacy rights and consent requirements may vary by country or region. If PrivyMark is distributed in regions that require additional disclosures or consent controls, such as the EEA, UK, California, or other regulated markets, the release build and privacy policy should be updated to meet those requirements.
This policy may be updated from time to time. The updated version should be posted at the privacy policy URL, and the effective date should be changed when updates are made.
For privacy questions, contact:jp0916780@gmail.com