RajSecure Shield Privacy Policy

1. Overview & Purpose

RajSecure Shield ("the App", "we", "us", or "our") is developed by Raj Kumar / RajSecure. The application is designed to help users identify and reduce digital exposure, safeguard against digital coercion, extortion, and non-consensual media sharing, and manage secure evidence preservation.

This Privacy Policy explains with technical transparency what data the App accesses, how it is processed, where it is stored, under what conditions data is transmitted, and your complete rights to access, export, and delete your data.

2. Data Classification & Processing Flows

To ensure complete transparency required by Google Play Data Safety standards, the following table details every data category accessed or handled by RajSecure Shield:

3. Detailed Subsystem Privacy Analysis

3.1. Notification Threat Shield

When you explicitly enable the Android Notification Listener Service for RajSecure Shield, the App inspects incoming notifications in real time to detect threat patterns, coercive extortion language, and blackmail keywords.

• 100% On-Device Processing: Threat parsing and severity classification run strictly inside local device memory.
• Zero Remote Uploads: Raw notification bodies, message transcripts, sender contact names, and phone numbers are never transmitted to our servers, Supabase, or any third party.
• Zero Plaintext Logging: Notification text is not written to persistent unencrypted system log files.

3.2. Camera2 & Microphone Active Capture Defense

When a recipient views a sensitive image shared via Protected Share, the App activates an on-device heuristic defense mechanism to guard against unauthorized physical camera recording:

• Front Camera Heuristic: The camera sensor analyzes frame luminosity and optical reflections to detect secondary recording lenses. Frames are processed in volatile memory buffers (`ImageReader`) and immediately recycled. No photos or video files are ever saved, stored on disk, or uploaded to any server.
• Microphone Heuristic: The microphone analyzes ambient audio signals for anomalous acoustic spikes. Audio is never recorded, never stored, and never streamed over the network.
• Honest Technical Boundary: Optical camera detection is a best-effort heuristic shield. While highly effective, it cannot guarantee detection of every possible external recording device. The App does not perform facial recognition or identity profiling.

3.3. Evidence Vault & Cryptographic Architecture

The RajSecure Evidence Vault enables users to preserve sensitive forensic evidence (screenshots, threat messages, and provenance metadata) securely on their device:

• Encryption at Rest: All files stored in the Vault are encrypted using AES-256-GCM with hardware-backed encryption keys created and stored in the Android Keystore.
• Zero Cloud Media Upload: Vaulted media files never leave your device. Only if you enable cloud synchronization, non-sensitive case identifiers and cryptographic SHA-256 hashes are synchronized to allow multi-device revocation tracking. Raw media is never uploaded.
• Emergency Freeze & Wipe: Users can instantly lock or cryptographically sanitize the local vault using the in-app Emergency Wipe function.

3.4. Protected Share Flow & Zero-Knowledge Relay

Protected Share allows users to share a single photo with a trusted contact under controlled viewing parameters:

• Client-Side Encryption: Media is encrypted on the sender's phone before transmission using AES-256-GCM with a unique Content Encryption Key (CEK).
• Zero-Knowledge Relay: The relay server (Supabase) stores only the encrypted ciphertext, wrapped key blocks, and expiration metadata. The server never possesses the decryption key or plaintext media.
• Cryptographic Revocation: When the sender revokes a share or when the timer expires (15 minutes to 7 days), the encrypted ciphertext and key blocks are permanently deleted from the relay server, rendering the content unrecoverable.

4. Third-Party Services & Network Transmissions

RajSecure Shield minimizes third-party dependencies. We do not integrate advertising SDKs, third-party analytics trackers, behavioral profiling engines, or external crash telemetry brokers.

• Supabase (Backend Infrastructure): Used solely for secure user authentication (email/password) and zero-knowledge encrypted share relay hosting. All transmissions occur over TLS 1.3 encrypted HTTPS. Data is protected by PostgreSQL Row-Level Security (RLS) policies.
• No Analytics SDKs: We do not use Google Firebase Analytics, Meta Pixel, Mixpanel, AppsFlyer, or similar tracking tools.
• No Advertising: The application contains zero advertisements and zero ad-network SDKs.

5. Account Creation & Data Deletion Rights

RajSecure Shield supports both Anonymous Local-First Mode and optional Authenticated Cloud Sync Mode:

• Anonymous Mode: You can use all core protection features (Vault, Threat Detection, Leverage Firewall, Takedown Generator) without creating an account or providing an email address.
• In-App Account Deletion: If you created an account, you can permanently delete your account and all associated cloud data directly inside the App by navigating to Settings → Account & Identity → Delete Account.
• Web-Based Account Deletion: You can also request complete account and data deletion at any time via our public web portal at https://www.rajsecure.site/rajsecure-shield/delete-account.
• Deletion Processing: When an account deletion is executed, authentication records, cloud sync entries, and active share tokens are immediately purged from our servers. Local vault files can be wiped at any time directly on your device.

6. Android Permissions & Prominent Disclosures

The App requests only standard Android runtime permissions strictly necessary for its security functions:

• Notification Access (`BIND_NOTIFICATION_LISTENER_SERVICE`): Required to scan notifications for threat patterns. Processed 100% locally on-device.
• Camera (`android.permission.CAMERA`): Required for Protected Viewer optical reflection heuristics. Ephemeral local processing only; no recording.
• Microphone (`android.permission.RECORD_AUDIO`): Required for Protected Viewer acoustic spike heuristics. Ephemeral local processing only; no recording.
• Biometric (`android.permission.USE_BIOMETRIC`): Required to authenticate vault unlock actions. Handled exclusively by the Android OS Keystore.
• Internet (`android.permission.INTERNET`): Required for Protected Share relay, Cloud Sync (if signed in), and takedown verification.
• Query All Packages (`android.permission.QUERY_ALL_PACKAGES`): Used locally to scan installed apps for the Digital Access Map risk assessment. Never uploaded.

7. Security Safeguards

RajSecure Shield incorporates defense-in-depth security measures:

• Hardware-Backed Keystore: Master cryptographic keys are generated within the Android Keystore (StrongBox / TEE where available).
• Window Protection: Sensitive screens enforce `FLAG_SECURE` to block unauthorized screenshots and screen recording by other apps.
• Code Hardening: Production builds are obfuscated and minified using R8 / ProGuard rules to prevent reverse engineering and tampering.
• Encrypted Transport: All network communications use TLS 1.3 with strict certificate validation.

8. Children's Privacy

RajSecure Shield is not directed to children under the age of 13 (or under 16 in certain jurisdictions). We do not knowingly collect personal data from children. If you become aware that a child has provided us with personal information, please contact us at security@rajsecure.site for immediate deletion.

9. Legal Boundaries & Non-Affiliation Disclaimer

RajSecure Shield is an independent cybersecurity application developed by Raj Kumar / RajSecure.

• The App is not affiliated with, endorsed by, or representing any government agency, police department, law enforcement authority, or CERT-In.
• The App assists users with personal digital safety analysis and documentation, but does not constitute formal legal counsel or automatic law enforcement dispatch.
• Security features provide advanced heuristic risk mitigation and do not guarantee complete prevention of all digital threats.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect enhancements in our security practices or regulatory requirements. Any updates will be posted on this page with a revised effective date.

11. Contact Information

If you have questions, feedback, or privacy-related requests regarding RajSecure Shield or this Privacy Policy, please contact: