1. Who we are and what this policy covers

IVKApps ("we", "us" or "our") develops Veypix, an Android app for redacting screenshots and other images. This Privacy Policy explains how information is handled when you use Veypix. It covers the features in version 1.0.20, including text recognition, face and code detection, automatic import scanning, editing, saving, sharing and the pre-share review.

Developer: IVKApps
App: Veypix
Android package: com.ivkapps.veypix
Privacy and support contact: support@ivkapps.com

The current app is free, with no advertisements, subscriptions, in-app purchases, accounts, watermarks or scan limits. We do not operate a server that receives your images for analysis or maintains an image history for you.

2. Images and information you choose to process

Veypix accesses images you choose using Android's system image picker, or explicitly open or share into the app. An image may contain personal or sensitive information, including faces, names, messages, phone numbers, email addresses, account details, identification numbers, payment information, locations, QR codes or barcodes.

The app accesses image pixels and may read file type, dimensions and orientation metadata to load and display the image correctly. It processes those pixels, recognition results, selected areas and editing instructions on your device to suggest redactions, apply effects, display previews and create an output image.

Veypix does not monitor your gallery, capture your screen, access your camera or continuously inspect other apps. Automatic scanning, when enabled, applies only to an image you import. You can change import scanning and detection preferences in Settings. An operation you start may continue while its editing session remains active, including briefly while the app is in the background.

3. On-device text recognition and possible private information

Text recognition uses bundled Google ML Kit recognition resources for supported Latin-script text. Optional experimental Hebrew recognition uses Tesseract with bundled Hebrew language data. Interface language availability does not mean that every script or language is supported by OCR.

Local rules look for supported patterns such as phone numbers, email addresses, payment-card-like numbers, possible identification numbers, IP addresses, URLs, account handles and order or booking references. Some rules use checksums or surrounding labels, such as an ID or passport field. These checks suggest possible matches; they do not establish a person's identity, verify a document or validate every country's identification format.

Recognized text is used transiently for the editing and detection workflow. Veypix does not write recognized private text to its settings, a permanent image-history database, developer analytics or application logs. Images and recognition outputs are not uploaded to IVKApps or a cloud recognition service for analysis. Separate information about third-party SDK technical diagnostics appears below.

4. Face detection and face-shaped masks

Face detection runs locally to locate possible faces for redaction. Where available, outer-face contour points help shape a mask around a face; an alternative shape may be used when refinement is unavailable. Temporary region geometry may remain in the active editing session, suggestions and undo/redo history.

Veypix does not identify who a person is, compare faces against identities, enrol people in a recognition system or build a face-identity database. It does not use this feature to infer a person's age, gender or emotions. Face tracking and expression classification are not enabled by the app.

Mask geometry is rendered into output pixels. Veypix does not export a separate facial template, editable face-geometry layer or underlying original-image layer. A covered face may still be identifiable from hair, clothing, surroundings or other visible context.

5. QR codes and barcodes

Code detection uses a bundled on-device barcode scanner. Veypix uses the location and format of detected codes to suggest areas to redact. Detection does not automatically open a link, visit a website, execute a code's contents or contact a destination encoded in a code.

The scanner may internally decode a code while processing it. Veypix's detection workflow does not read, display, persist or transmit decoded payload fields such as links, contact details or payment contents. Detection locations and formats are used transiently for review and editing.

6. Checking the protected image before sharing

When you choose Share, Veypix prepares a new flattened PNG in app-private temporary storage and checks that output locally for supported text patterns, faces, QR codes and barcodes. This final review checks supported categories even if you disabled those categories for normal editing scans. Optional Hebrew recognition follows its separate setting.

If the check finishes without matches, the Android sharing interface opens directly. Potential matches or an incomplete check show a review or warning, with options to return to editing or explicitly continue. The sharing interface waits until the export screen is active if you leave the app while checking.

The check does not automatically apply additional redactions or send an image to a recipient. The file offered for sharing is the same newly generated file that was checked. Review findings retain category counts and region geometry in memory, not recognized private text or decoded code contents.

A result with no matches is not a guarantee of complete privacy. Detection may miss information, misclassify content or fail on unsupported scripts, unusual layouts, low contrast, image scaling or other conditions. Always review the actual protected image before sharing.

7. Saving, sharing and other apps

Saving is a separate action that creates a new flattened image in your gallery or a document location you choose. On supported Android versions, gallery images are saved in Pictures/Veypix/. Veypix does not overwrite your imported original.

Exports are freshly encoded PNG images. The export does not copy original EXIF metadata or include an editable original-image layer beneath the redactions. Information you leave visible remains visible in the output. Redaction does not remove information from your separate original image or other existing copies.

Sharing uses Android's sharing interface and a content URI with temporary read access for receiving apps. Veypix offers the new flattened output rather than attaching the imported original URI as the protected image. You choose the receiving app or destination.

A gallery, cloud-backed document provider, messaging service or other receiving app may upload, retain, back up or further share an image under its own policies and your settings. IVKApps does not control those external copies or delete them remotely.

8. Local storage, retention and deletion

• Editing session: imported pixels, previews, suggestions, mask geometry and undo/redo history are held in memory for the active workflow. They may remain while the app is in the background. Veypix does not create a permanent gallery or database of your imported screenshots.
• Settings: language, appearance, editing defaults, detection choices, secure-editor settings and onboarding/guide preferences are stored in app-private storage until changed, cleared through Android app settings or removed with the app.
• Recognition resources: bundled language/model resources may be installed in app-private storage. These are model files, not a history of your images or recognized text.
• Temporary sharing output: newly prepared PNGs are stored in app-private cache. The app attempts to discard pending output when a check is cancelled or you return to editing. Files offered for sharing may remain so receiving apps can read them. Cleanup attempts, Android cache management, clearing app storage or uninstalling may remove these files; we do not promise an exact deletion deadline.
• SDK technical storage: third-party libraries may maintain model state, configuration, technical identifiers or diagnostic records in app-private storage as described by their documentation.
• Saved or externally shared copies: these remain in their selected locations until removed through those apps or services. Clearing Veypix data or uninstalling it does not delete external copies or your original images.

You can use the app's temporary-file cleanup control and Android's app settings to clear cache or app storage. Clearing all app storage also resets app preferences. Deletion is best effort and does not guarantee forensic erasure from flash storage, backups or another provider's systems.

Veypix disables Android app backup in its app configuration. Device manufacturers, device transfer tools, external gallery backups and other services may have their own behaviour outside the app's control.

9. Permissions, security and redaction limits

Veypix uses image access granted by the system picker or by an explicit open/share action. The current app does not request broad photo-library/storage access, camera, microphone, contacts, location, SMS or call-log permissions. It does not request Android's INTERNET permission, and core image processing does not require an internet connection.

Temporary sharing images are kept in app-private storage and exposed through a restricted FileProvider content URI when sharing. Secure editor mode, when enabled, applies Android's secure-window protection to private editing/export screens to restrict ordinary screenshots and screen recording on supported devices. These measures are not guarantees on every device or on compromised systems.

Opaque coverage permanently replaces the covered pixels in the exported image. Blur and pixelation are visual effects and may leave information readable, identifiable or inferable. Small masks, missed edges, uncovered context and false negatives can also reveal information. None of these features guarantees anonymity or complete removal of every private detail.

10. Third-party libraries and technical diagnostics

Veypix uses Android/AndroidX components, Google ML Kit and Tesseract/Tesseract4Android for local functionality. It does not include developer-operated advertising, behavioural analytics or remote crash-reporting services. We do not sell your image content, create advertising profiles from it or use your images to train our own models.

Google ML Kit: Google's documentation states that input images/text and recognition outputs are processed on-device rather than sent to Google for recognition. Its SDK documentation also describes technical diagnostics and usage metrics, including device/app information, installation identifiers, API configuration, event/error information and performance measurements. Such SDK technical data is distinct from screenshot content and recognition results, and is subject to Google's policies.

See ML Kit Terms & Privacy, ML Kit Android data disclosure and Google Privacy Policy. The absence of a developer analytics service is not a promise that SDKs or independently operated platform services never process technical diagnostics.

Android, Google Play, your device manufacturer, your image provider and receiving apps operate under their own policies. Opening an external help or policy page uses your browser or another app; that provider and the website host may handle connection information. This policy describes Veypix's app workflow rather than every independently operated service you use.

11. If you contact us and your privacy choices

If you email IVKApps, we receive the address you use, your message and any attachments you choose to send. This is separate from the app's local image processing. We use correspondence to respond, provide requested support, investigate issues and meet applicable obligations. Email or support providers may process that correspondence under their own policies, including outside your country.

We retain support information for as long as reasonably necessary for those purposes and applicable obligations, then delete or anonymise it where appropriate. Please do not send sensitive screenshots or information about other people unless necessary. We do not need access to your private image library to provide ordinary support.

You control which images to import, which detections and edits to use, and whether to save or share an output. Depending on your location and applicable law, you may have rights to request access, correction, deletion or a copy of personal information we hold, object to or restrict certain processing, withdraw consent where processing relies on consent, or complain to a relevant supervisory authority. Contact support@ivkapps.com to make a request.

We cannot remotely view or delete editing data held only on your device or copies held by another app. There is no Veypix account or server-side image history to delete. For local data, use the app's controls and Android app settings. For another provider's data, use that provider's controls or contact it directly.

12. Children and information about other people

Veypix does not ask users to create accounts or provide their age, date of birth, school or family details. Images you import can nevertheless contain information about children or other people. Use care when editing and sharing those images, and obtain any permissions required for your use.

If you believe a child has sent personal information to IVKApps through support correspondence, contact us so we can review the request and take appropriate action. These statements do not mean that an unreviewed screenshot is safe for a child to share.

13. Changes and contact

We may update this policy when the app or our data-handling practices change. We will revise the date at the top and provide additional notice or obtain consent where required by applicable law. New functionality is not automatically covered by a promise about a different version's data handling.

For privacy questions or requests, contact:
IVKApps - Veypix
support@ivkapps.com