Files you select for local processing
When you select a ZIP, your browser makes that file available to the page. The application reads its directory, validates paths and sizes, and extracts selected entries locally. Filenames, directory names, compressed data, and extracted bytes are handled in the active browser environment. The tool does not provide an archive-upload endpoint or send this content to an external extraction API.
The original ZIP remains on your device. The app may create temporary object URLs to hand extracted data to the browser’s download system. These are local browser references, not publicly shared links to a hosted file. Temporary URLs are released after use, while the downloaded files remain in the destination managed by your browser or operating system.
Temporary state and passwords
The active archive, current folder, selected paths, and entered ZIP password are held in temporary application memory. They are not saved to localStorage, an account profile, or a database. Removing the archive, choosing another ZIP, or refreshing the page clears that active workflow. Closing the page ends the application session, subject to the browser’s ordinary memory management.
A ZIP password is used to decrypt and verify supported encrypted entries locally. It is not sent to the website server, logged by the application, or deliberately persisted. The tool cannot retrieve a password after the session is cleared. Browser extensions, password managers, and operating-system facilities have independent behavior outside the application’s control.
Downloads and destination-folder permissions
For an individual file, the browser receives extracted data and a suggested original filename. Your browser’s settings determine whether to prompt for a location or use a default destination. Files already downloaded are not deleted when you reset the extractor. Manage those copies using your device’s normal storage controls.
Where supported, direct extraction asks you to choose a folder and grant filesystem access. The tool creates a new extraction directory under that destination and writes the selected relative paths inside it. This permission does not create a remote copy. However, a destination synchronized by your own cloud provider may later be uploaded by that provider’s software. Choose storage appropriate to your needs.
Website delivery and hosting information
The site must serve pages, styles, fonts, and JavaScript to your browser. Those requests reveal ordinary connection information to the hosting infrastructure, potentially including an IP address, requested URL, browser user agent, timestamps, and response details. The hosting provider may use operational logs for service delivery, diagnostics, abuse prevention, and security.
This policy does not claim that visiting the site creates no records anywhere. Hosting logs are distinct from the locally processed ZIP contents. Their retention and handling depend on the deployed hosting configuration and provider. The app does not append archive filenames or passwords to page URLs, analytics events, or server-side extraction requests.
Accounts, databases, analytics, and cookies
The extractor does not require an account and has no application database for archive storage. There is no account dashboard, server-side archive history, or stored selection history. If you close or refresh the page, you must select the ZIP again to continue working with it. The lack of persistence is intentional and should be considered before interrupting a long extraction.
The application does not include analytics, advertising trackers, or application cookies. Fonts and interface assets are served with the site rather than fetched from a third-party font service during your visit. Hosting infrastructure, your browser, or a deployment access layer may have separate technical behavior. Any future analytics or tracking integration should be reflected in an updated policy before it is enabled.
Information you send by email
The contact address is contact@ilovezip.online. If you send an email, the message necessarily includes information such as your address, message body, subject, and any attachments you choose to provide. Email providers process that correspondence according to their own services and policies. The website does not provide a pretend contact form or claim to send messages without a configured service.
Please avoid sending ZIP passwords, private archives, personal documents, or confidential filenames. A description of the error, browser version, operating system, archive size, and whether encryption is involved is usually a better starting point. If you need to demonstrate a bug, create a small non-sensitive sample containing invented data.
Security boundaries and your device
Archive validation includes path checks and resource limits, but it is not a malware scan and cannot guarantee the safety of extracted content. Encryption protects the archive layer, not necessarily the files after extraction. Store sensitive output in an appropriate destination and apply your normal security checks before opening unfamiliar files.
Local processing does not protect against a compromised device, malicious extension, someone with access to your screen, or files synchronized by your own storage software. No application can promise perfect security or immediate physical erasure of memory. Use a trusted, updated browser and device for confidential work, and follow any organizational requirements that apply to your material.
Your choices and requests
You can choose not to select an archive, cancel a processing operation, or remove the active archive. These actions stop the corresponding application workflow, but they do not recall completed downloads or remove files already written. Browser controls and operating-system tools are needed to manage those persistent copies.
If you contact us about information in correspondence you previously sent, identify the relevant message without including unnecessary sensitive data. Applicable rights and obligations may depend on your location and circumstances. The service does not offer access to a cloud archive record because it does not maintain such a record.
Changes and contact
This policy should change when the implemented data handling changes. The effective date indicates the current published version. Review it again if new features, integrations, or hosting arrangements are introduced. A general privacy statement should not be assumed to cover a later service with materially different behavior.
For questions about this policy, write to contact@ilovezip.online. For practical instructions, consult the ZIP guides or return to the local extraction tool.