Your files and inputs stay in the browser.

Files and entered data

The tools read selected PDFs, images, CSV/XLSX files and Markdown, or process pasted JSON, text, URLs, QR payloads and calculator inputs. Files and values are held in page memory and passed to local parsers or renderers. They are not uploaded to Two Trees and are not written tolocalStorage or sessionStorage.

Generated documents, images, ZIP archives and text files are created on your device. When you choose a download, your browser saves the file wherever your download settings direct it. Two Trees does not receive a copy. Copy controls write the selected output to your clipboard only after you press them.

The tools do not set cookies. Closing or reloading the tab clears the values you entered unless your browser restores form state on its own.

Appearance preference

If you choose light or dark appearance, this site stores only that choice under twotrees.appearance in local browser storage. Your selected files and tool contents are never stored with it. You can clear the preference through your browser site-data settings.

Product analytics

This build ships with product analytics disabled. If a collector and an explicit consent choice are configured later, the UI is limited to a small allowlist of aggregate events: tool opened, started, completed, failed, file downloaded, and output copied. Those events may include a tool identifier and a coarse format or error category such aspng or validation.

Analytics never receive your payload, URL, Wi-Fi name or password, business name, generated image, form contents, or file. The tool UI does not send arbitrary page beacons or copy query parameters into an event.

Hosting and third parties

The apps are static sites. Like any website, the hosting provider may keep standard request logs such as IP address, user agent, and requested path. Those logs are controlled by the hosting provider rather than by the tools. This build does not add advertising pixels or third-party tracking scripts.

Scanning a generated code can open the destination you entered. That destination has its own privacy practices. A Wi-Fi code can instead prompt your phone to join the encoded network.

Wi-Fi credentials and sensitive data

A Wi-Fi QR code encodes the network name and password. Anyone who can scan or photograph the code can read those credentials and may be able to join the network. Use a guest network where possible, rotate the password when a code is no longer under your control, and do not post photos of a private network’s code publicly.

The same applies to any sensitive text or private URL you choose to encode. A static QR code is not encrypted.

Your choices

• Do not enter credentials you are not prepared to encode.
• Test a code before printing, then store or dispose of it carefully.
• Clear the tab if you are using a shared or public computer.
• Avoid putting personal data, customer data, or confidential URLs into a public issue.

Changes and contact

This policy describes the current build and may change as the project develops. Material changes should be reflected here before a public launch. Questions and corrections can go through thecontact page; there is no email address published yet.