Media Processing: SafeShare is engineered around a strict on-device processing boundary. Your photos, videos, and PDF documents are analyzed and redacted locally on your phone. SafeShare does not upload your media, recognized text, OCR results, watchlist terms, or saved projects to Prinix Labs servers or any cloud AI service.
Data Controller: Prinix Labs. Inquiries may be directed to contact@prinixlabs.com.
This Privacy Policy applies to the SafeShare mobile application and the public website at safeshare.prinixlabs.com, developed and published by Prinix Labs ("we", "us", or "our"). SafeShare is designed with privacy-by-design principles to process media on-device, minimize data exposure, and provide transparency regarding third-party software development kit (SDK) diagnostic telemetry.
1. Media and Information You Choose to Process
SafeShare opens photos, videos, and PDFs that you explicitly select from your device storage, gallery, or share into the application from other apps. It analyzes them directly on your device to help identify faces, human heads, confidential text, barcodes, and other sensitive details for redaction.
- Local Processing: Media decoding, facial detection, optical character recognition (OCR), temporal motion tracking, and redaction rendering run locally on your device hardware.
- App-Private Persistence: Projects, recognized values, mask definitions, watchlists, user preferences, thumbnails, and exported files may remain in app-private sandbox storage so you can review edits or resume projects.
- No Server Analysis: SafeShare does not upload your media, recognized text, masks, watchlists, or project state to our servers or any cloud service for analysis or inference.
2. SDK Diagnostics and Technical Telemetry
SafeShare uses Google ML Kit for on-device machine learning detection features (e.g. text and face detection APIs).
- Google ML Kit Disclosures: Google ML Kit may collect and send device information, per-install identifiers, diagnostic metrics, performance statistics, and feature-use events to Google over encrypted connections. This diagnostic telemetry is separate from your media and recognition results. Your photos, videos, and recognized text are not transmitted.
- For full details on Google's collection and handling of ML Kit diagnostics, review the official Google ML Kit Android Data Disclosure and the Google Privacy Policy.
- No Advertising or Analytics Trackers: SafeShare does not integrate third-party advertising networks, in-app ad tracking SDKs, or third-party behavioral analytics services.
3. Subscriptions and Billing Verification (Android)
If you choose to purchase or subscribe to SafeShare Pro on Android:
- Google Play In-App Billing: Payment processing and subscription management are handled entirely by Google Play. SafeShare never receives, processes, or stores your credit card, debit card, or payment credentials.
- Stateless Verification: SafeShare transmits the Google Play purchase token over an encrypted HTTPS connection to a stateless Prinix Labs verification endpoint hosted on Google Cloud Run. The verifier queries the Google Play Developer API strictly to validate the subscription status and entitlement expiry date. The application code does not store your purchase token in a permanent SafeShare user account or database. Standard operational cloud infrastructure access logs (such as request timestamps and IP addresses) may be temporarily retained by hosting providers for routing, reliability, and security diagnostics.
- Zero Media Linkage: The billing verification service does not receive your media, recognized OCR content, or personal files.
- Platform Availability: In-app subscription purchases are currently offered exclusively through Google Play on Android. An iOS subscription flow is not currently active and will be reviewed under separate disclosures prior to any iOS commercial availability.
4. Exports, Metadata Handling, Privacy Receipts, and Sharing Boundary
When you export protected media from SafeShare:
- Metadata Removal Setting: By default, SafeShare removes photo EXIF metadata (such as GPS coordinates, camera model, and timestamps) and requests removal of video container metadata during export; you can turn this setting off in export preferences. Inspect exported files before sharing if metadata is sensitive.
- Generated Filenames: Exports receive generated filenames rather than the original source filename. Generated filenames include the export date and time.
- Rendered Output Layers: Exports render your selected redactions directly into the output image, video frames, or rasterized PDF pages. Automated detection can miss sensitive details, and blur or pixelation may leave information recognizable; review every export before sharing and use an opaque covering where details must be completely concealed. Originals and copies shared elsewhere remain separate.
- Privacy Export Receipts: If you copy or share an export receipt, it can include the output filename, timestamp, custom profile name, output dimensions, mask/category counts and file hash. Check the receipt before sharing. Custom profile names can themselves contain identifying or descriptive information. Copies sent to another app or person are outside SafeShare's control.
- Recipient Control & Sharing: When you save an export to your device gallery or share it to another application (such as WhatsApp, Slack, Gmail, or cloud storage), that destination receives the file. The destination's storage, backup, and privacy policies apply. Email attachments you choose to send to support or third parties are processed by the applicable mailbox provider and recipients.
- Advisory Notice: Automated machine learning detection is an advisory aid and may not detect every private element due to variations in lighting, angle, occlusion, or resolution. Always visually inspect exported copies before transmitting them to third parties.
5. Operating System Backups and Sandbox Exclusions
To reduce unintended inclusion of local project data in cloud backups, controls are configured within the application:
- Android: SafeShare configures Android cloud-backup exclusions for app-private data (
android:allowBackup="false"and Android 12+ cloud backup exclusion rules). Device transfer and operating system backup behavior remain subject to platform behavior. - iOS Platform Note: Local document directories include non-backup file attributes; iOS backup behavior is not yet verified for release.
- Scope Limitation: These controls are configured for app-private sandbox data. Gallery/shared copies follow their destination's backup settings.
6. Data Retention, Storage, and In-App Cleanup
- App-Private Project Data: Projects, thumbnail artifacts, recognized coordinate cache, and temporary render files reside in app-private sandbox storage. SafeShare provides an in-app cleanup control in Settings that clears project history, associated app-private thumbnail/export artifacts on a best-effort basis, and selected temporary scanning files.
- Settings, Watchlists & Profiles: Custom watchlist terms, privacy profiles, and application preferences are stored locally in app-private storage and remain on device until separately cleared or until the application is uninstalled.
- Original Media & Gallery Exports: Original source media and media you choose to export to your device gallery or photo library remain in your device storage and are not deleted by in-app project cleanup controls. You manage or delete them through your device's photo gallery or file manager.
- Uninstalling the App: Removing or uninstalling SafeShare deletes the application's private sandbox storage, subject to operating system cleanup behavior.
- No Server Account Deletion Needed: Because Prinix Labs does not maintain user accounts, user profiles, or remote media repositories, there is no remote user account or server-side media database to delete.
7. Privacy Rights and Data Control
We respect your privacy and design our software to keep data under your direct supervision:
- On-Device Access & Management: Because your photos, videos, and PDFs remain on your device, you maintain direct custody over your files. You can edit, mask, export, or delete projects directly within the app.
- Scope of Deletion: The in-app cleanup feature is designed to clear local project histories and temporary scan artifacts. It does not delete copies previously exported to device storage, shared with third-party applications, or operational records held by Google Play.
- Do Not Sell or Share Personal Data: Prinix Labs does not sell, rent, or trade personal data or user media with third parties for cross-context behavioral advertising or monetary consideration.
- Email Support Correspondence: You may request deletion of correspondence from our active support mailboxes by contacting privacy@prinixlabs.com. We review requests and delete information when it is no longer needed, subject to applicable recordkeeping obligations. Email-provider backups may follow a separate retention lifecycle. (Note: Email removal does not affect Google Play purchase or transaction records, which are managed separately by Google under Google Play policies).
- Inquiries: If you have questions regarding your data privacy rights, you may contact our privacy team at privacy@prinixlabs.com.
8. Age Rating & Minor Users
SafeShare is intended for people aged 13 and older. It does not require a SafeShare account or upload selected media to our servers. Because automated detection features utilize Google ML Kit, Google ML Kit may collect the device, app, identifier, diagnostic, and usage information described in Section 2 when its features are used. SafeShare does not solicit or knowingly harvest personal profile information from children under the age of 13. If you believe a child under 13 has provided personal data, please contact our team at privacy@prinixlabs.com.
9. Website Hosting, Google Fonts, Technical Logs & Email Retention
When you visit the public website at safeshare.prinixlabs.com or contact us via email:
- Website Fonts: The website loads fonts from Google Fonts (
fonts.googleapis.comandfonts.gstatic.com). Your browser contacts Google to request the font stylesheet and files; these requests disclose connection and request information (such as your IP address and browser headers) to Google. Google's privacy policies apply. - Hosting Infrastructure & Logs: The website is hosted via global content delivery network (CDN) infrastructure (Vercel). The hosting provider automatically collects standard technical request logs (such as IP address, browser type, referring URL, and request timestamp) to serve pages, maintain network performance, and defend against denial-of-service (DDoS) attacks. These provider-managed operational edge logs are retained in accordance with the hosting provider's infrastructure operations and security policies. Prinix Labs does not export these operational records into a separate database or marketing system.
- No Tracking Cookies: The website does not use third-party advertising cookies, social media tracking pixels, or cross-site behavioral analytics scripts.
- Support & Direct Inquiries: If you contact us via email (privacy@prinixlabs.com, support@prinixlabs.com, or contact@prinixlabs.com), your email address, message content, and any diagnostic details you provide are used solely to answer your questions and provide technical assistance.
- Email Retention Criteria: Support and privacy email correspondence is retained only for as long as necessary to investigate and resolve your inquiry, troubleshoot reported technical issues, or satisfy applicable recordkeeping obligations. You may request deletion of correspondence from our active support mailboxes at any time by contacting privacy@prinixlabs.com. We review requests and delete information when it is no longer needed, subject to applicable recordkeeping obligations. Email-provider backups may follow a separate retention lifecycle.
10. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect modifications in our software architecture, platform capabilities, or legal requirements. Material changes will be published on this website with an updated effective date. We encourage you to review this page periodically.
11. Contact Information
If you have any questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact Prinix Labs:
- Developer: Prinix Labs
- Privacy Inquiries: privacy@prinixlabs.com
- Support & General: support@prinixlabs.com or contact@prinixlabs.com
- Website: safeshare.prinixlabs.com