Privacy

This website

• No cookies, no analytics, no trackers. The site is static files: HTML, CSS, one small script for copy buttons, fonts, and images. The page runs no analytics or advertising requests.
• No third-party requests. Fonts and images are served from this site itself; there is no CDN, tag manager, or embedded widget.
• Hosting logs. The site is served by a hosting provider, and like any web host it may keep technical request logs (IP address, user agent) under its own retention policies to operate the service. This site adds nothing on top of that.
• Email. If you write to tailorcorp@icloud.com, the message goes to a human and is used only to reply and, if you asked for early access, to tell you when a build exists. No mailing list, no resale, and you can ask for your messages to be deleted at any time.

The application

Pure Vault is a local desktop program. Its privacy posture is architectural, not a policy promise layered on top:

• Nothing is uploaded. There is no account, telemetry, crash reporting, update ping, or network API. The typography is bundled; no font or asset is fetched at runtime.
• Sources stay read-only. Files and folders you select are opened read-only, and ZIPs are read in place without extraction. The app has no source-destructive actions.
• Selection is the only grant. Native pickers are the only way the interface can authorize a path, and selecting one file does not authorize its siblings.
• Workspaces are memory-only. Imported content, source paths, and search queries live in process memory. Clearing a workspace or quitting releases them. What persists is your display preferences and, only after you turn the feature on, a capped list of up to twelve previously opened backups. That list holds pointers and detection metadata: the path, source name, format, item count, size, and when you last opened it. It never records content from inside a backup, filenames from within it, or search text, and you can turn it off or clear it. This is a process-level promise, not cryptographic memory erasure: an operating system can retain bytes in swap or crash artifacts.
• Imported content cannot phone anywhere. HTML and Markdown from a backup are rendered inert, remote media URLs are never loaded, and bookmark addresses are copy-only text the app never opens.
• Exports are explicit. A normalized JSON or CSV copy is written only after you choose a destination in a native save dialog, always to a new file.

Reporting a problem

If you believe you found a privacy or security problem, do not include real backup data in your report. Build a minimal fictional reproduction and email tailorcorp@icloud.com. Machine-readable contact details are published in security.txt.

Changes

If this page materially changes, the effective date above changes with it.