How AryaPDF handles your files

PDF processing

This source build has no server-side PDF processing service. The supported tool workflows read selected files in the browser and construct outputs there. AryaPDF does not intentionally send the selected PDF contents to an AryaPDF processing API.

That does not mean that all network activity is disabled. The static site host serves the application and may keep ordinary request logs under its own policy. Markdown conversion can request image URLs contained in the input. OCR uses Tesseract.js defaults that can fetch worker/core and language data from jsDelivr. Those are resource requests; the OCR workflow does not submit the PDF to an OCR API. Avoid remote references when your workflow must make no external requests.

Contact submissions

When the Contact endpoint is configured, submitting the form sends your name, email address, contact number, optional category and comments to the server for delivery to the site operator's configured mailbox. The API does not accept files and the source implementation does not persist a submission database. The SMTP provider and mailbox may process or retain the email under their own policies; the production provider and operator are not yet configured in this source build.

The endpoint keeps a temporary, in-memory salted hash of the email address for a short repeat-submission limit. It is discarded on expiry or server restart. Do not include passwords, PDF content or sensitive personal data.

Storage and preferences

The application does not intentionally store selected PDF contents in localStorage or IndexedDB. The site and workspace save only the light/dark theme preference in localStorage under the key aryapdf-site-theme. The service worker caches same-origin application pages and build assets for app-shell use; it does not cache user-selected document contents.

Generated files are offered as browser downloads. Your browser and operating system control where downloaded files are kept.

Analytics and requests

The source pages do not include an analytics or advertising script. A production host, CDN, reverse proxy, or operator-added integration may collect request metadata under its own terms. Review those policies for the deployed website.

Security and limitations

Browser-side processing reduces the need to upload a document to a processing service, but it is not a guarantee that every workflow is offline, error-free, or suitable for every sensitive document. Keep a safe copy of important originals and verify the output before relying on it.

Operator and contact details

This source distribution does not identify a production operator, support address, hosting provider, jurisdiction, or privacy contact. The site operator must supply applicable details and review this notice for the actual deployment before publishing.