Aerialist2 — Privacy Policy

What this applies to

This policy covers both the web app at cyberhirsch.github.io/aerialist2 and the "Aerialist2 — PDF Editor" Chrome extension, which is the same application packaged a second way.

No data collection

• No PDF content, filenames, or metadata are ever uploaded to a server — there is no backend at all.
• No analytics, telemetry, tracking pixels, or crash reporting of any kind.
• No accounts, no sign-in, no cookies used for identification.
• No data is sold or shared with any third party, because none is collected in the first place.

What stays on your device

Signatures you draw or type, and your workspace layout, are saved using your browser's local storage (localStorage) so they're there the next time you open the app. This data never leaves your device and is not accessible to us or anyone else. Clearing your browser's site data for Aerialist2 removes it completely.

Chrome extension permissions

The extension requests the minimum permissions needed to replace Chrome's built-in PDF viewer:

• declarativeNetRequest — redirects .pdf page loads to the extension's own viewer instead of Chrome's built-in one.
• webRequest — read-only, used to detect PDFs served without a .pdf file extension (via the response's Content-Type header) so those redirect too.
• webNavigation — remembers which URL a tab was about to load, so the viewer knows which PDF to fetch after the redirect.
• tabs — updates a tab's URL to the viewer page, and opens a fresh tab from the toolbar icon.
• host_permissions (all sites, plus file://) — needed to fetch the PDF bytes from wherever it's hosted, and to read local files. Nothing is ever sent onward — the bytes are only read into the page to render and edit them.

Changes

If this policy ever changes, the "last updated" date above will change with it. Given the app has no server and no accounts, we don't expect much to change here.

Contact

Questions about this policy or the extension: open an issue on GitHub.