WORKLAZY TOOLS
Privacy Policy
Read how local file processing, Google and Naver Analytics, advertising and cookies are handled by Worklazy Tools.
1. Information processed in your browser
Files selected for available document, PDF, audio and image tools are read and processed in your browser. Text, payroll, employment dates and passwords are calculated in the current page and browser memory. Video Studio is currently unavailable.
- Input files and passwords are used only during the task
- Results are offered through temporary browser download URLs
- Text, payroll and password inputs are not sent to a server or permanently stored
- Ordinary task state disappears on reload or tab close; the official rhwp editor may keep a local recovery draft in IndexedDB
- When handing files to Office editing, document redaction, document-to-PDF conversion or XLS preservation screens, files may be kept temporarily in IndexedDB on this device. They are deleted from storage as soon as the receiving screen retrieves them. Files that could not be opened are deleted on the next visit after 15 minutes and may remain after the tab closes until then. Files are not sent to a server.
- The browser office editor may cache about 250 MB of shared application assets plus about 2 MB of editor-only Korean font data; the XLS preservation screen caches only the shared assets. Site-data settings can remove them, and opened documents or XLS files are not placed in that cache
2. Local workers and memory transfer
EXIF removal, QR image scanning, table conversion and other heavy operations run in task-specific browser workers that are stopped after completion. Audio PCM, editing history and the page clipboard remain in the current tab.
When an MP3 or AAC result is continued in Audio Studio, its Blob is transferred once in memory to a same-origin tab, the communication channel is closed, and the output is not placed in persistent browser storage.
3. Ordinary network information
Loading this static site and the analytics or advertising services below can expose ordinary request information such as IP address, browser type and request time to GitHub Pages and those providers. This is separate from work-file contents.
4. Self-hosted editing and processing components
Official rhwp JavaScript, WebAssembly, UI and fonts are bundled as pinned static assets. HWP files move to the same-site editor iframe through an in-browser MessageChannel, not an upload request.
Word comparison, PDF OCR, FFmpeg and LibreOffice-based editor files are served from this GitHub Pages deployment. Office editor files are a pinned snapshot whose size and SHA-256 are verified at build time. A first offline visit cannot start features whose required files are not yet cached.
Choosing a Google font in the image editor may send a font request and ordinary connection information to Google Fonts. Images and entered text are not sent. Default and system fonts do not require external requests.
Background removal shows the size of missing model and runtime files before you choose Download from this site (about 41 MB for portraits or 127 MB for objects and products). Verified assets may be kept in Cache Storage (worklazy-models-v1). Use Delete saved models in the editor or clear browser site data to remove them. If storage is unavailable, processing still uses the downloaded files and they must be downloaded again next time. Your images and results are never stored in this cache.
5. Google and Naver Analytics; Google AdSense and Coupang Partners
Google Analytics 4 and Naver Analytics can process page paths, referrals, visit and click times, and browser or device categories. Tool-menu events contain only the tool identifier and menu location.
File names, contents and sizes, entered text, payroll and passwords, QR results, generated output and detailed errors are not included in analytics events. Google Signals and ad personalization are disabled in Google Analytics.
Google AdSense and advertising partners may use cookies, web beacons, IP addresses and identifiers for ad delivery, measurement and abuse prevention. Available pages are not excluded by tool type; ad and analytics requests may start once a normal screen is ready. Ads are not requested on redirect, preparation or empty error screens.
Coupang Partners banners appear above the footer on tool pages, including the expanded HWP editing view without overlapping the work area. They are not shown while a tool is loading or has failed. Banner code runs in an iframe separate from the work area; selected files and tool inputs are not passed to it. Coupang may receive ordinary connection data and use identifiers for ad delivery and measurement. The operator may earn a commission from purchases through the banner.
6. Third-party services and your choices
This site does not show its own advertising or analytics consent dialog. Once a normal screen is ready, Google Analytics, Naver Analytics, Google AdSense and Coupang Partners on tool pages may load automatically. Where separate consent is required, deployment-level consent management and each provider's policies additionally apply.
Browser settings and content blockers can limit analytics or advertising without disabling local file processing. Worklazy Tools does not sell selected files or passwords or provide them to analytics or advertising companies. Third-party processing of ordinary connection data follows their policies.
7. Children, updates and contact
The service targets general work users and does not offer accounts or forms intended to collect information from children under 14. This policy and its effective date may be updated when features, providers or applicable law change. Never attach real work documents or passwords to a privacy inquiry.
8. Recent tools and favorites stored in your browser
This browser stores up to six recent tool IDs in worklazy:recent-tools and favorite tool IDs in worklazy:favorite-tools using localStorage. These lists do not store file names, search queries, file contents or generated results. Lists are not sent to a server, advertising or analytics services.
Lists remain until cleared using the home or policy buttons below, or browser site-data settings. Corrupt values are ignored and left untouched. A blocked store or failed write disables only the affected saved list. Corrupt values can be removed in browser site-data settings.
Excel cleaning rules stored in your browser
Selecting Save these rules stores the recipe name, save time and cleaning rules in this browser. User files and processing results are not stored, but rules may contain find-and-replace text, column names or other text you enter. Saved rules are not sent to a server and remain until you delete them individually or clear them below.