Local PDF Studio

Privacy Policy

Effective date: 19 April 2026  ·  Last updated: 2 September 2026

Local PDF Studio (“the Extension”) is a client-side PDF manipulation tool that runs entirely inside your browser. This policy explains what data the Extension handles, where it is stored, and the only external service it contacts.

Summary

  • The Extension does not collect, transmit, sell, or share any personal information or document content.
  • Every PDF you open and every annotation you draw is processed locally on your device.
  • The developer operates no servers, no analytics, no telemetry, and no advertising.
  • By default the Extension makes no outbound network requests. Its Content Security Policy restricts connections to the Extension itself.
  • If you turn on the optional “Use Studio for all PDFs” setting, the Extension downloads the PDF you navigated to (and only that PDF) on your own device, using your own browser session. That file is never sent anywhere else.

1. Data We Collect

None. The developer of Local PDF Studio does not collect, receive, or have access to any user data of any kind. There is no account system, no login, no usage tracking, and no error reporting service.

2. Data Stored on Your Device

The Extension stores the following data locally in your browser’s IndexedDB, on your own device only. It is never transmitted off the device.

Data Purpose Location
PDF files you open or import To allow you to view and edit them and to auto-save your session Browser IndexedDB
Annotations, drawings, highlights, text, signatures, form entries To persist your edits across sessions Browser IndexedDB
Session / undo history To support undo, redo, and crash recovery Browser IndexedDB
User preferences (tool settings, theme, etc.) To remember your UI choices Browser localStorage / IndexedDB

You can delete this data at any time by removing the Extension, clearing its site data from chrome://extensions, or clearing your browser’s storage.

3. Outbound Network Connections

By default the Extension makes no outbound network connections. Its Content Security Policy (declared in its manifest) limits connect-src to 'self', and it requests no host permissions at install time, so the browser blocks any connection to an external server.

3.1 Optional: “Use Studio for all PDFs”

Settings → Browser contains an opt-in toggle that makes the Extension open web links ending in .pdf instead of Chrome’s built-in PDF viewer. When you turn it on:

You can turn the toggle off at any time; the permission can also be revoked from chrome://extensions, which disables the feature automatically.

3.2 Right-click menu

The Extension adds three entries to the right-click menu on web pages. They run only when you click them:

The result is stored in the Extension’s IndexedDB “inbox” on your device until the app consumes it (unconsumed items are discarded after 24 hours). Nothing is sent anywhere.

4. Data Sharing

The developer does not share user data with any third party, because the developer does not collect any user data.

No third party is involved in the operation of the Extension.

5. Limited Use

The Extension’s use of any data it handles is limited to providing and improving its single, user-facing purpose: local, client-side PDF viewing and editing. Specifically:

6. Chrome Permissions

None of the Extension’s permissions is used to collect or transmit user data.

7. Children’s Privacy

The Extension is not directed at children under 13 and does not knowingly collect information from anyone.

8. Security

9. Changes to This Policy

This policy is published at https://nikola-radovic.github.io/local-pdf-studio/. If it changes in any material way, the updated version will be published at that same URL, with a new “Last updated” date. Continued use of the Extension after an update constitutes acceptance of the revised policy.

10. Contact

Questions about this policy can be sent to:

Nikola Radović

localpdfstudio@gmail.com