DMCA & Technical Policy

1. Intended Purpose: Personal Data Access & Portability

MegaHelper was developed exclusively as a lightweight, independent personal utility to assist individuals in downloading, streaming, and retrieving their own legitimate personal backup files, archives, and cloud data stored on MEGA.

Many users maintain extensive personal backups on cloud storage but face hardware or bandwidth constraints when accessing them through heavy proprietary client software. MegaHelper provides an accessible, standards-compliant bridge allowing individuals to access their own cloud data via universal web streaming and direct browser download protocols.

2. Absolute Zero-Logging & Non-Retention Policy

MegaHelper enforces an uncompromising zero-logging architecture designed to protect user privacy and confidentiality:

• No IP Logging: The server does not log, record, or track client IP addresses, browser fingerprints, or geographic locations.
• No Link Storage: Submitted MEGA URLs, folder hashes, file paths, and resource links are never saved, indexed, or stored in any database or disk log.
• No Searchable Catalog: MegaHelper does not maintain a public directory, search engine, file repository, or history of processed links.
• No User Identifiers: There are no user accounts, tracking cookies, advertising beacons, or third-party telemetry scripts.

Once a streaming connection ends or a browser tab is closed, all session-related memory is immediately discarded.

3. Zero File Storage & Stateless Operation

MegaHelper does not host, store, cache, or duplicate any files, media, or copyrighted assets on its servers or storage drives. The application operates in complete zero-disk mode: at no point is any file byte written to server storage media.

The platform acts strictly as an ephemeral conduit / cryptographic transport mediator. Data is processed on-the-fly entirely within transient volatile memory (RAM) buffer pools solely to stream the specific byte range requested by the user's browser, and is piped directly to the user socket.

4. Client-Side Decryption & User Key Ownership

In accordance with MEGA's end-to-end zero-knowledge architecture, files are encrypted at rest. The cryptographic keys required to decrypt files reside exclusively within the URL fragment (e.g. #key) provided directly by the user.

MegaHelper neither generates nor catalogs encryption keys. The server possesses no independent means to decrypt or inspect content without the user's explicit link parameter.

5. DMCA Takedown Protocol & Copyright Inquiries

Because MegaHelper does not host, store, catalog, or control underlying user files, and retains no record of submitted links or user identities, MegaHelper has no technical capability to delete or disable files hosted on third-party cloud infrastructure.

Copyright owners and legal representatives seeking the removal of specific infringing content must submit their DMCA takedown requests directly to the cloud storage provider that actually hosts the content:

Once a file or link is removed or invalidated by MEGA on their storage infrastructure, MegaHelper is automatically, permanently, and immediately incapable of resolving or streaming that file.

6. Contact & Inquiries

For inquiries, open-source documentation, or technical questions regarding the operation of this software, you can connect via our community channels:

@liquidxprojects on Telegram or iamLiquidX on GitHub.