Effective 26 September 2026
Cookies and local storage
Most cookie pages are written to make a long list seem unavoidable. This one is short because the list is short: public tools need no cookies. Your consent choice is a local preference; first-party measurement keeps no persistent visitor identity. Administrator authentication and optional provider cookies are separate and listed below.
- Required for tools
- None
- Analytics cookies before consent
- None
- Admin session only
- 8 hours
Strictly necessary
The tools need no cookies whatsoever.
A conventional file-processing site needs a session cookie, because it must remember which uploaded file on its server belongs to which visitor. Nothing here is uploaded, so there is no public file-processing session to identify. The separate admin cookie authenticates operators, not visitors using PDF tools.
You can therefore block cookies entirely, browse in a private window, or clear site data between every visit, and every tool will behave identically. The only consequence is that the consent banner will ask again, because the record of your previous answer was what you cleared.
- Authentication cookies
- None for public tools. Only administrators who sign in receive a necessary session cookie.
- Upload session cookies
- None. No file is ever uploaded to be tracked.
Complete inventory
Everything that can be stored
Browser preferences and tool state are separate from optional measurement and advertising. The admin cookie is only for signed-in operators. First-party aggregate data is held on the server, not in your browser; its retention is described in the privacy policy.
mypdfiles.consent.v1
Necessary for preferences
Remembers whether you accepted or declined analytics and advertising, so the banner asks once rather than on every visit.
- Kind
- localStorage
- Duration
- Until you clear site data
- Gate
- Set only once you answer the banner
Tool session state
Necessary
Your files, page order, previews and results while a tool is open. Held in the tab’s memory, never written to storage or to a server.
- Kind
- Tab memory
- Duration
- Discarded on reload or close
- Gate
- No consent needed — never leaves the tab
First-party measurement queue
Analytics
A bounded temporary queue of anonymous tool events and random delivery IDs, not a visitor profile. No document content, filenames, options or arbitrary errors.
- Kind
- Tab memory; no cookie
- Duration
- Short retries; discarded on revocation, reload or close
- Gate
- Analytics consent and server-confirmed eligibility
mypdfiles_admin_v2
Necessary for administrators
Authenticates the private admin workspace. Root scope also lets the server suppress authenticated administrator activity on public tools. Not a public visitor identifier.
- Kind
- First-party HttpOnly cookie
- Duration
- 8 hours; removed on sign-out
- Gate
- Successful administrator sign-in only
Optional Google Analytics cookies
Analytics
Separate optional measurement; never the source of the first-party admin dashboard. Provider cookie details depend on its configuration. Enhanced Measurement must be disabled in the GA property before use.
- Kind
- Provider-managed cookies
- Duration
- Set by the provider and its configuration
- Gate
- GA configured, analytics consent and non-admin eligibility
Advertising cookies
Advertising
Frequency capping and ad measurement by the ad network, under its own policy. Not set by us and not readable by us.
- Kind
- Third-party cookies
- Duration
- Set by the ad network
- Gate
- Ads configured and enabled, advertising consent and non-admin eligibility
The one key we set
mypdfiles.consent.v1
This is a localStorage entry, not an HTTP cookie. The practical difference is that it is never attached to a network request: it sits in your browser and is read by the page’s own code to decide whether to show the banner. It is not an identifier, contains nothing about you, and is not sent to us.
The v1 suffix is deliberate. If the categories we ask about ever change materially, the key version changes with them, which means an old answer cannot be silently carried forward to cover something you never agreed to — you will be asked again.
It is written only at the moment you answer the banner. Visit the site and process a hundred files without touching the banner, and no consent preference or analytics history is written to browser storage. If storage is unavailable, your choice can apply for the current page without being remembered for a later visit.
- Mechanism
- localStorage
- Sent to server
- Never
- Expires
- On clearing data
Withdrawing consent
Three ways to change your answer
Withdrawal stops future reporting without affecting the tools. It does not undo prior anonymous aggregates or automatically erase provider cookies; browser storage controls can remove those.
- 01
Use the cookie settings link
Reopen settings in the public site footer and change your answer. Future analytics delivery stops and queued events are discarded. Reload after withdrawing to clear already-loaded third-party scripts, and use browser controls to remove their stored data.
- 02
Clear site data for this domain
In your browser’s site settings, clear cookies and storage for this site. That removes the stored consent record along with anything a third party had set, and the banner will ask again on your next visit.
- 03
Block it at the browser level
Browser storage and content-blocking controls do not affect local PDF processing. Blocking third-party cookies alone is not withdrawal of consent for cookieless first-party measurement: also decline analytics in cookie settings. A private window has a separate consent choice.
Questions about storage
Effective 26 September 2026
Can I use the tools with cookies entirely blocked?
Yes, and nothing will be missing. No cookie is required for any tool on this site to function, because the tools run in your browser rather than in a session on our server. Blocking cookies costs you nothing here except that the consent banner may reappear, since the record of your choice is itself something that has to be stored.
Is the consent key a cookie?
Not technically. mypdfiles.consent.v1 is a localStorage entry rather than an HTTP cookie, which means it is never attached to a network request — it stays in your browser and is read by the page itself. We describe it here anyway, because the distinction matters far less to you than knowing what is stored.
How do I withdraw consent after accepting?
Open cookie settings in the site footer and change your choice. Future analytics delivery stops and queued events are discarded; previously aggregated counts cannot be associated with you and undone. Advertising is not loaded without consent. A script that already executed cannot be unexecuted: reload after withdrawing and use browser controls to remove provider cookies or storage. Clearing this site’s data also removes your consent preference.
Are any cookies set before I answer the banner?
No analytics or advertising cookies are set before consent. First-party measurement uses no analytics cookies even after consent. The separate administrator sign-in sets a necessary authentication cookie only after a successful login; ordinary PDF tools do not need it. Your browser may also cache the site’s assets.
What does an ad network store if I accept advertising?
Cookies and identifiers of its own, under its own policy rather than ours, typically to limit how often you see the same ad and to measure whether ads were seen. We do not control that set and would be misleading you if we enumerated it as though we did — which is precisely why its script is loaded only after you have agreed to it.
Do you track me across other websites?
Our first-party measurement has no cross-site identifier, fingerprint or persistent visitor ID. Optional GA and advertising are separate services governed by their providers’ policies and require configuration, consent and non-admin eligibility. If either is enabled, do not interpret this site as entirely first-party or cookieless.
If something on this page turns out to be inaccurate, that is a bug and we want to know — write to hello@mypdfiles.com.