Privacy Policy
Last updated:
1. About this policy and who is responsible
This policy describes how PrivaPress (“the service”), image and video tools that run in your web browser, handles information.
The party responsible for the service (“the operator”) is:
- Operator: PrivaPress (pixnelo.com)
- Contact email: si2666760@gmail.com
2. Your images
The images you choose are processed in your browser, on your device. The service is built so that image data is not uploaded: the pages restrict the browser’s network connections to the site’s own address (a Content Security Policy with connect-src ‘self’), so the page’s scripts cannot send your images to another server.
Some things are outside the service’s control, for example browser extensions, the security of your device, and what you do with the files after you download them.
3. What the service stores on your device
The service stores up to two small items in your browser’s local storage (localStorage). They stay on your device and are not sent to the operator:
- privapress.market-limits.v1 — the marketplace limit settings you enter, kept on this device only.
- privapress.lang.v1 — remembers only that you chose a language or dismissed the language suggestion. It never contains image data.
Video tools process selected videos locally and write temporary MP4 and ZIP files to this browser’s private file storage. Videos are never uploaded. After downloading, use “Delete results & temporary files” to remove the copies. Cancelling or replacing a video deletes that job’s files. Unused files older than 24 hours are removed when you next open the tool; files held by an open tab are retained. Clearing this site’s browser data also removes them.
The service itself does not set cookies. You can delete these items at any time by clearing the site’s data in your browser.
4. Information processed by the hosting provider
The service is hosted on Cloudflare. Like any web hosting, Cloudflare processes technical request information when your browser loads a page. This can include:
- your IP address
- the page address (path) you requested
- your browser’s user agent and request headers
- security signals and timestamps used for abuse protection
Cloudflare uses this information to deliver the site and to protect it against abuse. How long Cloudflare keeps it is determined by Cloudflare’s own terms and settings.
The operator does not set up or keep its own access logs. The operator can see only the aggregate statistics that Cloudflare shows in its dashboard (for example visits by country and by page). Cloudflare may process requests on servers in several countries, including outside Korea and outside your own country.
The service uses Cloudflare Web Analytics to count page visits and measure how fast pages load. Cloudflare adds a small script to the pages (loaded from static.cloudflareinsights.com) that reports to this site’s own address (/cdn-cgi/rum). According to Cloudflare, it collects page-load timing metrics, does not use cookies or localStorage, does not fingerprint individuals, and does not track individual visitors across its customers’ sites. When we inspected a live report, it also contained the page address, the browser name and version and memory figures of the page, and no file data. The service does not pass your image, PDF or video files, their file names or your settings to it; those stay in your browser as described in section 2. Visitors in the European Union are excluded: Cloudflare does not add the script to their pages, so no measurements are collected from them, and every feature of the service works the same for them.
5. What the service does not have
The service does not provide or use any of the following:
- user accounts or sign-in
- payments
- comments
- contact forms
- advertising or cross-site tracking scripts (the only analytics is Cloudflare Web Analytics, described in section 4)
6. Advertising and analytics in the future
The service currently shows no advertising and sets no cookies. Its only analytics is Cloudflare Web Analytics, described in section 4. If the operator later adds advertising (for example Google AdSense) or other analytics, this policy will be updated before it starts.
Advertising partners such as Google may use cookies or similar technologies to serve and measure ads and, depending on your settings, to personalise them. For visitors in the European Economic Area, the United Kingdom and Switzerland, and wherever else the law requires it, the service will ask for your consent before such cookies are used, and you will be able to change your choice later. You can manage Google ad personalisation in your Google account’s ad settings.
7. Children
The service is not directed at children, has no accounts, and does not knowingly collect personal data from children.
8. Your rights and contact
Depending on where you live, you may have rights over personal data that is processed about you (for example under Korea’s Personal Information Protection Act or the EU GDPR), such as access, correction, deletion and objection, and the right to complain to your local data protection authority. The service holds no accounts, so what the operator can look up or delete is limited to emails you send. If you email the operator, your address and message are used only to reply and are deleted without undue delay once your request is handled, unless the law requires them to be kept.
To ask a privacy question or make a request, contact the operator, who is responsible for privacy matters:
- Contact email: si2666760@gmail.com
9. Applicable law and legal review
The service is operated from South Korea and Korean law applies to this policy. Mandatory privacy rules that apply to you where you live, for example in the EU, the UK, Japan or China, are not excluded. This policy has not been reviewed by a lawyer.
10. Changes and effective date
Effective date: 2026-10-30
Version history: 2026-11-02, corrected this version history and the dates (no change to how information is handled). 2026-10-30, described Cloudflare Web Analytics, which visitors it excludes and what a live report contains. 2026-10-28, first version. Changes will be posted on this page together with a new effective date.