Which browser technologies PDFNexa uses—and which it does not.
This policy describes cookies and similar browser storage as PDFNexa operates today. We do not list analytics, advertising, consent, or PDF-processing cookies simply because those categories are common on other websites. A cookie belongs in this policy when a real PDFNexa feature actually uses it.
A cookie is only one kind of browser storage.
Cookies are small pieces of data a website or related service can ask a browser to store and send back later. They are commonly used for sign-in, preferences, security, consent choices, analytics, or advertising.
Similar technologies can include local storage, session storage, pixels, or identifiers held in the browser. This policy uses “cookies” as a convenient label when the same privacy question applies, but we distinguish technologies when the difference matters.
Used when a requested feature, security control, administrative session, or preference cannot work properly without the browser remembering something.
Used to remember a non-essential choice such as interface settings or optional service preferences.
Used to measure visits, interactions, performance, or usage patterns. PDFNexa does not describe this category as active until an analytics service is deliberately configured.
Used by advertising systems for functions such as delivery, frequency control, measurement, personalization, or fraud prevention. This category is not currently presented as active on PDFNexa.
We prefer an honest status table to a guessed cookie list.
Cookie names can vary by WordPress configuration, user state, security layer, provider, and future feature changes. The table below therefore describes the technologies PDFNexa intentionally relies on today and separates them from categories that have not been activated.
Supports sign-in, authenticated administration, and WordPress interface preferences for authorized site administrators.
Authorized administrators rather than ordinary readers.
May use short-lived browser or server-side mechanisms when needed to protect forms, validate requests, manage sessions, or prevent abuse.
Only when the relevant feature requires it.
No analytics cookie category is described as active until a specific measurement service is configured and disclosed.
Not currently activated as an optional category.
Advertising cookies or similar identifiers will be documented only if advertising technology that uses them is enabled.
Not currently activated as an optional category.
Current PDF tools process selected documents locally in the browser. Any temporary browser memory or storage used by the tool remains part of that local processing workflow rather than a PDFNexa server upload.
Visitors using the current PDF tools.
Necessary does not mean invisible or unlimited.
A technology is treated as necessary when the requested feature or security control cannot reasonably work without it. That can include WordPress authentication for administrators, short-lived request validation, security measures, or a future cookie that remembers a visitor’s consent choice.
Calling a cookie “necessary” does not make every use automatically justified. Its purpose should still be narrow, and it should not quietly become an analytics or advertising identifier.
Most visitors do not need a PDFNexa login.
Public guides, tool explanations, legal pages, accessibility information, and the contact page can be viewed without creating a PDFNexa account. WordPress authentication cookies are therefore primarily an administrative function, not a condition for reading ordinary public content.
Blocking necessary browser storage in your browser may affect a feature that genuinely relies on it, while rejecting an optional category should not be used as a reason to block access to ordinary editorial pages.
Inactive means inactive—not “probably coming soon.”
PDFNexa does not treat analytics or advertising cookies as active simply because the site may use those services later. When an optional provider is added, this page should identify the category and purpose instead of relying on generic wording.
Optional services need their own disclosure and, where required, consent.
If PDFNexa later enables analytics, advertising, personalization, or another optional browser technology, the relevant provider, purpose, cookie or storage category, and available choices will be added to this policy. Where applicable law requires prior consent, the optional technology should not be activated before the visitor has made that choice.
Browser controls and site controls solve different problems.
A site preference panel can control optional services configured by PDFNexa. Your browser can also block or remove cookies more broadly. Neither approach changes cookies that belong to a completely different website.
Site preference controls
If optional categories that require consent are introduced, PDFNexa will provide a way to make and revisit those choices. The control should be reachable without hunting through a long legal page.
Browser controls
Modern browsers allow you to view, delete, restrict, or block cookies. Blocking all cookies can also break features that rely on necessary storage, including authenticated administrative functions.
Rejecting optional categories
Rejecting an optional analytics or advertising category should not prevent access to ordinary public guides and policy pages.
Not every third-party request is a PDFNexa cookie.
A browser may connect directly to an external provider to load a resource. That request can transmit ordinary connection information even if no PDFNexa cookie is created. Cookie disclosures and third-party connection disclosures are related, but they are not identical.
Cookie lifetime depends on the purpose.
Some browser data exists only for a session. Other necessary settings may last longer. WordPress authentication and administrator preference lifetimes are governed by the relevant WordPress behavior and sign-in choices. Optional provider cookies, if introduced, may have their own durations.
We do not publish a made-up universal duration. When an optional service is activated, its actual cookie or storage duration should be documented with the service rather than guessed in advance.
The inventory changes when the site changes.
PDFNexa may update this policy when WordPress behavior, security mechanisms, consent controls, PDF tools, analytics, advertising, or other providers change. The date at the top identifies the current version.
If a material optional category is introduced, the policy and any applicable consent interface should be updated together so visitors are not asked to make a choice without knowing what that choice controls.
Ask about a real browser behavior, not a generic policy label.
If you believe PDFNexa is setting or using a cookie or similar technology that is not described accurately here, send the page URL, browser, and what you observed. Choose “Privacy request” on the contact page. Do not send private documents or passwords.