Privacy Policy

Effective Date: May 17, 2026

Developer / Contact Email: rrenaturibin@gmail.com

This Privacy Policy describes the data processing practices, privacy safeguards, and client-side compliance protocols of the application Renaturibin Chat Lock (hereinafter referred to as the "Application").

1. Serverless Architecture and Privacy-by-Design

The Application operates on a strict serverless, privacy-by-design framework. The Application does not own, manage, or communicate with any proprietary remote servers or central databases ("No Server"). Your raw text messages, generated cryptographic keys, processed frequency configurations, and audio elements are compiled exclusively on the fly inside your local device environment. No data is ever transmitted, uploaded, or exposed to the developer or any external entity.

2. Local Storage Sandbox and Data Control

To maintain interface continuity, track metrics, and manage user preferences, the Application uses client-side sandboxed storage mechanics (localStorage and sessionStorage) directly within your device. The data retained locally includes:

• Application History Logs: Localized records of encrypted text blocks and generated outputs to enable structural reload states inside the interface.

• Performance Statistics: Local count parameters tracking total encrypted/decrypted entries and accumulated character counts.

• Aesthetics and Localization: Custom user choices regarding active theme modes (Light/Dark toggle) and interface language selections.

• Ad and VIP Lifecycle Status: Operational metrics used by the Omega Ad Manager v5 system, including daily rewarded video watch milestones (managed through a 10-video looping array), the strict countdown expiration timestamp (_omg_..._exp) for ad-free premium access, and warning confirmation logs.

Data Destruction: You maintain full ownership and access controls over this data. You can permanently and irreversibly purge all locally saved information at any moment by using the internal "Clear" or "Reset" functions, or by clearing your browser önbellek/app site data. The developer has zero technical capabilities to remotely audit or recall your local activity.

3. Cryptographic and Frequency Processing Parameters

The platform implements technical local procedures to transform text variables into secure frequency outputs:

• Unicode and Frequency Synthesis: Individual text parameters are systematically mapped to their corresponding Unicode numeric codepoint values and synthesized locally into corresponding acoustic frequencies and steps.

• Password Layer Protection (Optional): When an explicit passcode is supplied by the user, data security is enhanced via a robust local cryptographic structure. The platform derives security keys using the PBKDF2 standard with 100,000 iterations, combined with a 16-byte random salt and a 12-byte Initialization Vector (IV) to block unauthorized local access. Client-side decryption is entirely restricted unless the matching passcode is entered.

4. Device Permissions and Native API Utilization

To run smoothly offline without executing hidden background scripts or embedding heavy tracking software, the Application targets native web components:

• Web Audio API: Synthesizes sound waves (sine, square, sawtooth, or triangle variations) to audibly play back encrypted frequency data via your device hardware. The Application never requests microphone access, performs zero environmental recording, and lacks voice-logging behaviors.

• Clipboard API: Facilitates secure, user-initiated duplication of ciphertexts, cryptographic keys, and system reports to the device clipboard registry.

• Canvas API: Dynamically renders visual audio waveforms and real-time frequency spectrum graphs (vizCanvas) directly on the UI canvas layout, without generating persistent video files or screenshot caches.

5. Third-Party Networks and Advertising Entegration

To sustain free deployment, the Application leverages the Omega Ad Manager v5 framework to communicate securely with the Google AdMob advertising infrastructure. The data streams interacting with these systems include:

• Google AdMob Ad Unit Identifiers:

  • Rewarded Video Ad ID: ca-app-pub-1708403343487585/2005037766 (Utilized to dynamically award temporary ad-free VIP privileges upon successful video ad completion).

  • Interstitial Ad ID: ca-app-pub-1708403343487585/8438199733 (Served during layout tab switches and key task execution transitions).

• IP Geolocation Infrastructure (ipapi.co): Upon software launch, a secure network query is sent to https://ipapi.co/json/ to verify the user's connecting country code. This verification is done exclusively to adjust local AdMob parameter boundaries and conditionally present regional regulatory disclosure panels. Full IP strings are never retained on developer infrastructure.

• Network Time Verification (worldtimeapi.org / timeapi.io): To prevent local device clock modification from subverting the rewarded VIP ad-free duration limits, the Application fetches verified, objective UTC timestamps from public API time networks.

• Google Fonts CDN (fonts.googleapis.com): Remotely loads interface typography sheets—specifically Inter, JetBrains Mono, Cinzel, and Rajdhani—to render structural layouts correctly.

6. Regional Compliance and GDPR Rights

The Application features an integrated GDPR Compliance Module (gdpr-consent-dlg). If the geographic geolocation via ipapi.co indicates that the device connection originates within the European Economic Area (EEA) or the United Kingdom (UK), users are provided with a dedicated consent panel. This panel allows them to explicitly allow or deny personalized ad targeting schemas. Users hold the absolute right to reset their consent configuration or pull tracking privileges back at any time via the internal privacy options.

7. Children's Privacy (COPPA Compliance)

Because the platform maintains an absolute zero-collection policy regarding user assets and executes all cryptographic transformations strictly on the client side, it complies fully with the Children’s Online Privacy Protection Act (COPPA) and international child privacy criteria. It presents no data harvesting vulnerabilities and is entirely safe for users under the age of 13.

8. Updates to this Document

The developer reserves the right to amend this text to mirror revisions in technology infrastructure or international compliance mandates. Any structural modifications will be declared directly within the Application UI alongside a revised "Effective Date" at the top of the statement.

9. Contact Information

For formal validation requests or structural privacy inquiries, you can establish direct contact with the developer via email at: 

rrenaturibin@gmail.com