Elegant Paper collects nothing. Your documents are processed on your computer and never leave it. The only network connection that exists is the licence and 15-day trial check against the Microsoft Store — and it is fail-open.
Elegant Paper collects nothing. Your documents are processed on your computer and never leave it.
Merge, split, rotate, extract pages, recognize text (OCR), compress and protect PDFs — all locally, using your machine's CPU and Windows' own services (Windows.Data.Pdf to render pages, Windows.Media.Ocr for text recognition).
There is no upload. There is no server of ours. There is no user account. You can turn off the internet and the app keeps working entirely — that is the simplest way to verify this policy.
No analytics, no trackers, no third-party SDK sending data.
The license and 15-day trial check against the Microsoft Store, made by Windows' own API (Windows.Services.Store). It only reports whether this app is licensed to this Store account. It transmits neither content nor metadata of your files.
If the Store is unavailable, the app keeps the access already granted (fail-open): a network failure never locks your work.
The app contains no other network client — no HTTP, no self-updater. Updates are delivered by the Microsoft Store.
The illustrated manual is displayed inside the app by a Windows component, Microsoft Edge WebView2. The manual's content is a resource embedded in the app itself and served from memory: that component never navigates to the internet, loads no remote pages, shows no ads and keeps no third-party cookies. Any navigation away from the manual is blocked by the app itself. The WebView2 engine is part of Windows and is installed and updated by Microsoft — Elegant Paper neither downloads nor installs it. If it is not present on the system, the app simply reports that it could not open the manual reader; nothing is downloaded.
In %AppData%\ElegantPaper (inside the package container when installed from the Store):
Two working folders may also hold copies of your images:
Elegantimports — when you put a photo on the desk in a format PDF can't embed (HEIC, TIFF, BMP, WEBP), the app writes a JPG version of it here so it can build the page. That is a copy of your image.scans — the pages that came from your scanner, written before they become a PDF (the PDF is only created when you say so).Both are cleaned automatically: files older than 7 days are deleted on the next start. None of it is sent anywhere, and you can erase everything at any time by uninstalling the app or deleting that folder.
There is a third working folder, and it is the most sensitive of the three — which is why it is spelled out in full:
montagem ("assembly"), in %LocalAppData%\ElegantPaper (not %AppData%) — when you click Save with finishes marked (searchable text, watermark, stamp, page numbering, password, "lighter", "no metadata"), the app builds the file here, step by step. Those steps are complete PDFs of yours, not fragments.Three things about it: it lives for seconds (each step deletes the previous one as soon as it closes, so at most two copies exist at a time); it disappears when the Save ends, whether it succeeded, failed, or you cancelled halfway; and if the app dies mid-Save (power cut, crash), whatever is left is deleted on the next start — not in seven days. The sweep only deletes what it can lock, so it never destroys the assembly of a second window that is saving at the same time.
It lives in %LocalAppData% rather than %AppData% for exactly this reason: %AppData% is the folder corporate networks sync to a server, and the assembly of your documents has no business leaving your machine.
If another Elegant suite app is installed, a small "presence" file (name, version and supported verbs) may be written to %LOCALAPPDATA%\Publishers\<publisher>\ElegantSuite\ — a folder readable only by apps from the same publisher. It holds integration metadata, never your document content, and is rebuildable cache.
Elegant Paper never modifies or overwrites the source file: every operation produces a new file. Your files are never permanently erased: deletions happen only by your explicit action (undoing a generation) and go to the Windows Recycle Bin.
There is a single permanent deletion in the app, and it never reaches a file of yours: when you cancel an operation in progress, whatever that operation had just produced is discarded for good — half-finished work doesn't linger, and it doesn't clog your Recycle Bin. The originals stay untouched.
The app is not directed at children and collects no data from anyone, minors included.
Since we do not collect, store or process any personal data of yours, there is nothing to request, correct, export or delete from us. Purchase and installation data stay with Microsoft, under the Microsoft Privacy Statement.
If this policy changes, the date at the top is updated and the new version is published on the product page and shipped with the app. A change that started collecting any data would be announced prominently — but the product's commitment is to collect nothing.