Privacy Policy

1. Who we are and scope

This Privacy Policy explains how Neverland Technologies, LLC, a Delaware limited liability company doing business as "ZipRecover" ("Neverland Technologies", "we", "us", or "our"), handles information in connection with the ziprecover.online website and the browser-based ZIP password recovery tool made available through it (together, the "Service"). It reflects an architecture in which the core functionality, ZIP password recovery, runs locally on your device. This policy is a draft provided for transparency and is not legal advice. It should be reviewed and tailored by counsel before launch.

2. Your files are processed locally and are not collected by us

When you select a ZIP archive, it is read in your browser using the File API and processed on your device, by the page and by the Web Workers that test passwords. The archive is never transmitted to our servers or to any third party by the Service, and there is no upload step. As a result, we do not collect, receive, store, or have access to any of the following:

• The ZIP file itself or the contents of any file inside it;
• Filenames or folder names stored inside the archive;
• Candidate passwords you test;
• Any password that is recovered; or
• Hashes, fingerprints, or other derivatives of your archive.

Because this information never leaves your device through the Service, there is no copy of it for us to disclose, sell, lose, or be compelled to produce.

3. Information automatically processed by our hosting and CDN provider

The Service is delivered as static files through Cloudflare Workers, our hosting and content-delivery provider. As with essentially every website, when your browser requests pages, scripts, or the WebAssembly compatibility probe, Cloudflare automatically processes standard technical request data in order to deliver content, provide security, and produce aggregate, non-identifying traffic measurements. This data may include:

• Your IP address and general, approximate location derived from it;
• Your user-agent string, device and browser type, and language;
• The URL requested, referrer, timestamp, and response status; and
• Security signals used to detect and mitigate abuse, bots, and attacks.

This request data is processed by Cloudflare acting as our service provider, under Cloudflare's own terms and privacy commitments and our account configuration. We use it only for delivering, securing, and understanding aggregate use of the Service, and it does not contain any data from your archive. [Owner to confirm Cloudflare log retention, analytics configuration, and data-processing terms with counsel.]

4. Cookies, local storage, and analytics

The Service does not set advertising or cross-site tracking cookies and does not build a profile of you across other sites. Two features store data in your browser, on your device only, and never send it to us:

• Hand-off from the home page. If you drop or choose a ZIP on the home page, your browser keeps a copy of the file in its local IndexedDB storage (database toolsite_handoff) just long enough for the recovery page to open it, and the recovery page deletes that copy as soon as it reads it. If the recovery page does not open, the copy stays in your browser until the next time you open that page (it then reads and deletes the copy) or until you clear this site's data.
• Resume. While a mask or brute-force search runs, and while it is paused, the tool saves its progress about every 1.5 seconds under the local-storage key zr_resume_v1, so you can continue after a reload or after closing the tab. The record holds the archive's file name and size (to recognize the same file later), the search settings (character sets and lengths, or the mask you typed, which can include characters of your password), how far the search has run, and the time it was saved. It never contains the archive, its contents, the candidate passwords, or a recovered password. It is deleted when the search finishes, when you press Stop, or when you choose Start fresh, and you can remove it at any time through your browser's site-data controls. Dictionary searches are never saved.

The recovery tool includes a privacy-friendly analytics hook in its own code. It can record only a few non-identifying labels about a run: the encryption scheme, the archive's AES key size where it has one, the mode you chose, and whether the archive is supported. It can never receive archive contents, internal filenames, candidate passwords, recovered passwords, or archive hashes. No collector is attached today, so it sends these events nowhere. Separately, Cloudflare records standard request metadata for every page as described above. If aggregate, privacy-respecting analytics are enabled in the future to understand page traffic, they will stay within that same allowlist and will never receive your archive or its passwords.

Error reports

If the site's own code fails unexpectedly in your browser, a small report is sent to this site's own address (/api/error, same origin) so we can fix the breakage. It contains only the error type and message, the script stack trace, the address of the script that failed with its line and column, the page path (never the query string or fragment), the page language, your browser's user-agent string, a timestamp, the site's release version, and, for a failure inside the recovery tool, a one-word label for the part that failed. It never contains your archive, its contents or file names, any password the tool tried or recovered, or anything you typed. It is anonymous (no account, cookie, or identifier), always on, and capped at ten reports per page view. This site's server is set up to forward each report to our central error hub, which will store it in a Cloudflare D1 database tagged with the site it came from and delete it after 90 days. The hub is not running yet: until it is, and whenever it cannot be reached, a report goes only to this site's Cloudflare Worker log. Reports are kept for at most 90 days.

5. How we use information

We use the limited request data described in Section 3 and the error reports described in Section 4 only to operate, deliver, secure, maintain, and improve the Service, to detect and prevent abuse and technical problems, to understand aggregate usage, and to comply with legal obligations. We do not use this data to identify you individually where that can be avoided, and we do not use it for advertising.

6. No sale or sharing for advertising

We do not sell your personal information, and we do not share it for cross-context behavioral advertising, as those terms are used under applicable privacy laws. We do not trade in personal information.

7. Third parties and subprocessors

We keep third-party involvement to a minimum. Our primary subprocessor is Cloudflare (Cloudflare Workers), which provides hosting, content delivery, and security for the Service and processes the request data described in Section 3 on our behalf. Error reports (Section 4) are handled by this site's Cloudflare Worker; once our central error hub is running, the Worker will forward them to it, in a separate Cloudflare account that stores them in Cloudflare D1. Open-source libraries used by the recovery engine are bundled with the Service and served from our own origin rather than called at runtime to transmit your data. We do not share your information with advertisers or data brokers. [Owner to finalize the list of subprocessors and their data-processing agreements with counsel.]

8. Data security

The Service is served over HTTPS with a strict Content-Security-Policy and other hardening headers, and connections are limited to the site's own origin. Because your archive stays on your device, the most sensitive data never traverses the network and is not exposed to us or to third parties. No method of transmission or storage is completely secure, and you remain responsible for the security of your own device, browser, and backups.

9. Data retention

Because recovery is local, we hold very little data about you. We do not retain your archives, their contents, or any passwords, as we never receive them. Error reports (Section 4) are kept for up to 90 days and then deleted. The limited request data processed by Cloudflare is retained by Cloudflare according to its configuration and retention practices and is used only for the purposes described above. [Owner to confirm applicable retention periods with counsel.]

10. Children's privacy

The Service is intended for adults and is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided information in connection with the Service, contact us and we will take appropriate steps. [Owner to confirm the applicable age thresholds for its jurisdictions with counsel.]

11. International users and cross-border processing

The Service can be accessed globally and is operated from the United States. Because recovery is performed on your device, your files are not transferred across borders by the Service. The limited request data described in Section 3 and the error reports described in Section 4 may be processed by Cloudflare in the United States and in other regions where Cloudflare operates. By using the Service, you understand that request data may be processed in those locations. [Owner to confirm cross-border transfer mechanisms with counsel.]

12. GDPR and UK GDPR (individuals in the EEA and UK)

Where the EU General Data Protection Regulation or the UK GDPR applies, our legal bases for processing the limited request data described in Section 3 and the error reports described in Section 4 are our legitimate interests in operating, securing, and understanding aggregate use of the Service, and, where relevant, compliance with legal obligations. Because we hold very little personal data about you, requests to access, correct, delete, restrict, port, or object to processing will in most cases relate only to request data held by Cloudflare on our behalf or to the anonymous error reports described in Section 4, and we will act on valid requests as required by law. You may also have the right to lodge a complaint with a supervisory authority. [Owner to confirm whether the GDPR or UK GDPR applies, identify any controller or representative, and finalize legal bases with counsel.]

13. CCPA and CPRA (California residents)

Where the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies, California residents have rights to know about, access, and delete personal information, to correct inaccurate personal information, and to opt out of the sale or sharing of personal information and the use of sensitive personal information for certain purposes. As described above, we do not sell or share personal information, and we collect only limited request data through our hosting and CDN provider and the anonymous error reports described in Section 4. We will not discriminate against you for exercising your rights. To make a request, contact us using the details below. [Owner to confirm applicability of the CCPA and CPRA and finalize consumer-rights disclosures with counsel.]

14. Your choices and how to exercise your rights

You can limit local storage and cookies through your browser settings without affecting the core, local-only recovery function. Because we do not collect personal information about you through the recovery tool, there is generally no personal profile for us to access or delete. For any request data held by our hosting or CDN provider, or to ask a question or make a rights request under any applicable law, contact us at privacy@ziprecover.online. We may need to verify your request to the extent required by law. [Owner to map these rights to specific statutory obligations with counsel.]

15. Changes to this policy

We may update this Privacy Policy from time to time. Changes are effective when posted, and the "last updated" date above will change accordingly. Your continued use of the Service after changes take effect constitutes acceptance of the updated policy.

16. Contact

Privacy questions and requests can be sent to Neverland Technologies, LLC (d/b/a ZipRecover) at privacy@ziprecover.online. A physical mailing address for privacy notices is [physical mailing address to be added].