Privacy Policy
MAXScanner provides PDF, image, media, calculator, account and developer/API features. This policy explains the product-wide privacy model. The processing note on an individual tool is the more specific disclosure for that workflow.
Browser-local when supported
Many PDF and image tasks run on-device. A tool may make a stronger local-processing claim only when that specific workflow actually stays in the browser.
Private server-backed jobs
Some conversions and account/API workflows use server processing. Their source and result objects are private and must not expose storage keys in public URLs.
Privacy-safe measurement
Product measurement is designed around low-cardinality events and must not send document contents, filenames, calculator values or search text as analytics payloads.
Processing transparency
Browser-local tools keep selected files on your device. Server-backed tools identify when a file must be sent for processing.
Last updated: October 2026
1. Introduction
MAXScanner provides PDF, image, media, calculator, account and developer/API features. This policy explains the product-wide privacy model. The processing note on an individual tool is the more specific disclosure for that workflow.
2. How file processing works
MAXScanner uses more than one processing mode. We do not make a blanket claim that every file operation stays on your device.
Browser-local tools: the selected file is processed on your device by browser code and is not sent to a MAXScanner processing server for that operation.
Server-backed tools: the file required for the requested operation is transmitted to MAXScanner processing infrastructure for capabilities that cannot reliably run only in the browser.
Account and library features: files or metadata you explicitly choose to save can be stored so the signed-in feature can work.
Developer/API workflows: authenticated jobs can use private source and result objects and short-lived signed result URLs.
Check the processing details shown on the tool before using a sensitive document. If a workflow does not clearly state a processing model, do not assume it is browser-local.
3. Information we process
Browser-local tools do not need to upload the selected file for their operation. Server-backed tools process the file and job metadata needed to complete the request. Account/library features can keep items you choose to save. Private source or result storage keys are not intended to appear in public URLs.
If you use sign-in, saved documents, API access or similar account features, we process the identifiers, settings, job metadata and service records needed to provide and secure those features.
We may measure product usage and technical reliability so we can improve MAXScanner. Product analytics are designed to use low-cardinality events and must not include document contents, filenames, calculator values or free-form search text as analytics payloads.
4. Browser storage and saved state
MAXScanner can use browser storage such as localStorage or IndexedDB for local preferences and workflow features. Examples include language/theme preferences, recent or saved tools, saved calculation state and short-lived browser-local handoff artifacts between compatible tools.
Clearing site data in your browser can remove browser-local state. This is different from data you explicitly save to an authenticated account or library.
5. Cookies, analytics and advertising
MAXScanner uses three kinds of cookies and similar browser storage. The Cookie Policy lists them and lets you change your analytics choice.
Essential: sign-in sessions, security and preferences such as language and theme. The site needs these to work.
Analytics: MAXScanner uses Google Analytics 4 with Google Consent Mode. In the EEA, the UK and Switzerland, analytics cookies are used only after you allow analytics. Everywhere else they are on by default, and you can turn them off at any time with Cookie settings in the site footer or on the Cookie Policy page. While analytics is not allowed, the Google tag sets no analytics cookies and sends only cookieless pings, which Google uses for aggregate measurement. Analytics receives page paths and coarse usage events, never file names, file contents, typed values or search text.
Advertising: MAXScanner uses Google AdSense. Google and its partners use cookies or similar identifiers to serve ads, limit how often you see the same ad, measure ad performance and prevent fraud. With personalised ads, they also use your visits to this and other websites to choose which ads to show.
Your ad choices: you can turn off personalised ads in Google Ads Settings (https://adssettings.google.com), or opt out of personalised advertising by participating vendors at https://www.aboutads.info/choices or https://www.youronlinechoices.eu. Non-personalised ads still use cookies for frequency capping, aggregated reporting and fraud prevention.
EEA, UK and Switzerland: personalised ads require your consent, collected through a Google-certified consent message. Without consent, Google may serve only non-personalised or limited ads.
How Google uses data: Google explains how it uses information from sites that use its services at https://policies.google.com/technologies/partner-sites.
6. Service providers
Server-backed features can rely on infrastructure and processing providers needed to run the requested service. Those workflows should receive only the data required for the operation or account feature. MAXScanner does not present server-backed processing as browser-local processing.
Google: Google provides analytics (on by default outside the EEA, the UK and Switzerland, and only with your consent inside them) and advertising through Google AdSense, under Google's own privacy policy at https://policies.google.com/privacy.
7. Retention and deletion
Retention depends on the feature. Browser-local temporary state is controlled by the browser and the workflow. Server-backed jobs and signed-in library/account features can have different operational retention needs. We do not state one universal deletion window here when the active implementation does not have one universal lifecycle. Where a feature persists user files, its UI or product documentation should describe that behavior.
8. Security
Browser-local processing reduces network exposure for workflows that support it. Server-backed source and result objects are designed to remain private, with authenticated access or short-lived signed URLs where applicable. No online service can promise zero risk, so use the processing disclosure for the specific tool when deciding whether to handle sensitive material.
9. Your choices and rights
You can choose browser-local tools when available, clear browser-local site data, and avoid saving files to account features. Depending on where you live, privacy law may also give you rights relating to personal data we hold. Contact us through the contact page for a request or question about an account or stored data.
10. Children's privacy
MAXScanner is not directed at children under 13. We do not knowingly design account or processing features to collect personal information from children in violation of applicable law.
11. Changes to this policy
We may update this policy as MAXScanner changes. Material changes should be reflected on this page with an updated date.
12. Contact us
If you have a privacy question or a data request, email [email protected] or use the MAXScanner contact page.
Know where your files go
Many MAXScanner tools process files locally in your browser. Some conversions, account features and API workflows use server-side processing when the tool says so.