scan2pdf Privacy Policy

Policy version: v2.6.157.5
Last updated: October 19, 2026
Effective date: October 19, 2026

1. Summary

Category	Main information
Our own services	Our internally developed service components manage scanning, image editing, the local document library, OCR workflows, PDF creation and tools, preferences, and advertising integration. The App has no registration, account binding, membership, payment, or cloud-sync service.
Information processed	Selected images and PDFs; camera frames; edited pages, OCR text and document metadata; PDF settings and passwords; local preferences and privacy choices; information you choose to send as feedback; Google advertising and SDK technical data.
Permissions	Camera access on request; Internet and network state; SDK-added advertising identifiers and Android advertising services permissions; library permissions for background task support and protected internal broadcasts. No broad gallery or storage permission is requested.
Third-party components	Google Mobile Ads (AdMob), Google User Messaging Platform (UMP), Google ML Kit Text Recognition, PDFBox Android, OpenCV, AndroidX (including CameraX and Room), Material Components, and Guava. Section 4 distinguishes network services from local libraries.
Your choices	Select individual files through Android; manage camera and advertising controls; delete local documents; decide whether to copy or send content to another app. Settings links to this policy and, when required by Google UMP, Advertising privacy choices.

2. Information We Process and Why

2.1 Scanning and document functions

Our internally developed service components process the following information when you use the corresponding functions. Local processing does not send document content to our servers or to advertising services. A cloud-based file provider or a receiving app you select may transfer content under its own policy.

Data type	Information processed	When it is used	Purpose	Processing and retention
Camera capture	Live camera frames, captured page images, image dimensions, and detected page corners.	You open the scanner and, if permission has not already been granted, read the purpose notice and choose Continue.	Preview, photograph paper documents, and locate page edges.	CameraX and local image processing access the active camera while the scanner is in use. Preview frames are processed in memory; captures and edits may remain in private cache as an active scan session. Saved pages are copied into private document storage. No camera images are sent to Google advertising. See Section 5 for deletion.
Selected files and edits	Images or PDFs you select, their file names and access URIs, copied page images, crop corners, rotations, enhancements, page order, and markup.	You choose Import images, open a PDF tool, or edit a page.	Create, edit, and organize your selected documents.	Android grants access to selected items; the App does not scan your entire photo library or file system. It may retain a read grant for an active scan session or make a private working copy. Files remain in private storage/cache until the applicable document or session is deleted or cleared. Original selected files are not deleted by deleting an App copy.
Document library and OCR	Document name and ID, page order/count, timestamps, thumbnails, file paths, PDF size, recognized text, and an imported-PDF fingerprint for reuse.	You save or view a document, extract text, or search recognized text.	List and find documents, restore edits, avoid duplicate imports, and show OCR results.	Images and text recognition are processed locally. Library metadata and OCR results are stored in the private Room database, with pages and PDFs in private files. Saved items remain until deletion, clearing App storage, or uninstall. Temporary OCR imports follow Section 5. ML Kit technical metrics are separately explained in Section 4.3.
PDF creation and protection	Selected page content, output name, page size, orientation, quality, page ranges, compression level, and an opening password you enter.	You generate, merge, split, compress, or protect a PDF.	Create the PDF operation you requested.	Processing occurs locally. Tool passwords are held for the operation and are not saved as a preference or database field, sent to us, or supplied to advertising. The protected output retains the encryption needed to open it. Intermediate tool files use private cache. Generated library PDFs stay with the document; a Save to device operation writes to your chosen Android destination.
Copy, share, and translation	The PDF or recognized text you choose.	You confirm Copy, Share, or Translate, or choose to open a PDF in another app.	Move selected content to your chosen recipient or clipboard.	Copy writes selected text to the system clipboard; the App does not read clipboard history. Other apps with clipboard access may read the copied text. Sharing uses Android; PDFs receive a temporary read grant and text is included in the outgoing intent. Translate sends text to a compatible app you choose, which may upload it. Recipient and clipboard retention is outside the App; no separate sharing history is kept.
Preferences and permission records	Language, layout, enhancement, page-size/quality choices, recent tool, onboarding status, active-session references, camera request count and denial time.	You change settings, use a tool, resume a scan, or respond to a camera request.	Remember choices, restore work, and manage permission prompts.	Stored locally in private preferences until changed, cleared, or uninstalled. Camera denial time is removed after permission is granted. These records are not sent to our servers or passed to advertising as document data.
Feedback and support	The App name/version and Android version included by the feedback action; the message, sender details, and any attachments you voluntarily add.	In Settings, you choose feedback and confirm opening another app, or contact us directly.	Let you report an issue and let us respond.	The App opens Android’s share chooser with version information; it does not automatically attach documents, OCR text, or logs, submit a report, or keep a feedback database. Sending occurs in your chosen app. If you send a message to us, it is held in our support correspondence and the communication provider’s systems for handling the request and any necessary follow-up; see Section 5.

2.2 Advertising, consent, and technical data

AdMob is the App’s only advertising SDK. We use Google UMP to refresh applicable privacy choices before allowing Google advertising requests. An introductory agreement and Google’s permission to request ads are both checked. Startup ads, native ads in Documents, and interstitials associated with PDF preview may be shown. If no ad is available, the document workflow continues.

The introductory decision and disclosure version are stored locally. UMP exchanges information with Google to obtain and apply the relevant privacy message and stores the resulting consent state. The precise network processing by AdMob, UMP, and ML Kit is described separately in Section 4; none receives document content from our advertising integration.

2.3 Access the App does not request

The App does not request microphone, precise or coarse location, contacts, phone-state, phone-number, SMS, call-log, Bluetooth, notification, all-packages, overlay, or broad photo/storage permissions. Our document features do not read IMEI, IMSI, ICCID, MEID, hardware serial numbers, MAC addresses, SSID/BSSID, Wi-Fi scan lists, a general installed-app list, or motion-sensor records. Advertising identifiers and IP-derived general location are different and are disclosed in Section 4.1. Limited SDK package-visibility declarations allow compatible browser or action handlers to be found; they do not authorize reading messages, contacts, calendar contents, or all installed apps.

3. Permissions and System Access

Camera is the only dangerous runtime permission requested by the App. Other declarations below are normal, system-managed, or signature permissions; they do not produce a camera-style permission dialog. A declaration does not mean that every supported SDK feature is used.

Permission	Permission code	When it is used	Purpose, scope and choices
Camera	android.permission.CAMERA	Open scanner → purpose notice → Continue, when access is not already granted.	Preview and capture pages, with local edge detection. No background recording or advertising camera access. Denial leaves image import and other non-camera functions available. You may revoke access in Android app settings.
Internet	android.permission.INTERNET	Google ad/consent requests and ML Kit SDK network activity.	Transfers the service data in Section 4, not the local document library. Granted by Android without a runtime prompt. Without network access, ads/online consent refresh can fail; local document processing remains available after introductory setup.
Network state	android.permission.ACCESS_NETWORK_STATE	SDKs check connectivity for their network work.	Checks connection availability/type; it is not access to the contents of your files, Wi-Fi passwords, or messages. No runtime prompt. Network restrictions may delay SDK work.
Advertising ID	com.google.android.gms.permission.AD_ID	Google advertising, subject to privacy choices and system settings.	Allows the SDK to access the resettable advertising identifier when available. It does not grant access to phone numbers or SIM identifiers. Android’s advertising controls can reset/delete or restrict the ID, depending on the device.
Advertising services ID	android.permission.ACCESS_ADSERVICES_AD_ID	Declared by the Google advertising dependency for supported Android advertising APIs.	Allows supported ad-ID access where available and permitted. No separate runtime prompt. System advertising controls and SDK configuration govern use; it does not provide document access.
Ad attribution	android.permission.ACCESS_ADSERVICES_ATTRIBUTION	Declared by the Google advertising dependency for supported attribution features.	Permits supported ad measurement APIs when available and enabled. It is not a location or storage permission. The App does not implement its own attribution reporting service; system advertising controls may restrict SDK use.
Ad topics	android.permission.ACCESS_ADSERVICES_TOPICS	Declared by the Google advertising dependency for supported topics features.	Permits supported interest-topic APIs when available and enabled. It does not permit reading your OCR text or scans. System advertising privacy controls govern availability; the App does not calculate topics from documents.
Wake lock	android.permission.WAKE_LOCK	Included through library background-task support.	Allows scheduled work to keep the CPU awake temporarily. It grants no access to personal files or sensors. No runtime prompt; Android battery restrictions can defer background work.
Foreground service	android.permission.FOREGROUND_SERVICE	Included through AndroidX WorkManager.	Permits foreground-task support; this App does not use a foreground service for background camera capture or document uploads. No runtime prompt for this declaration. System restrictions govern service execution.
Protected internal receiver	com.camscanner.pdfscannerapp.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION	Used by AndroidX for protected internal broadcasts.	A signature-level permission that restricts receiver access. It does not grant access to personal content and has no user permission dialog.

File selection and saving: Android’s system file picker and Save As interface grant access to the particular items or output location you choose. The App may persist a selected read grant while a scan session needs it. It does not request READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, or MANAGE_EXTERNAL_STORAGE. If you select a cloud document provider, that provider may download or upload the selected file.

Sharing and components: The App’s FileProvider is not exported. It grants temporary access to a specific file for your share/open action. The launcher activity is exported so Android can open the App; library initialization providers are not exported. System-facing library jobs and diagnostics receivers are protected by Android permissions. These components do not provide unrestricted access to the document library.

4. Third-Party SDKs and Libraries

The following components are included in the App. Our own document and integration code is not a separate third-party service. Libraries that process files locally do not receive an independent upload of those files.

4.1 Google advertising

4.2 Advertising privacy choices

4.3 On-device text recognition

4.4 Local document and image libraries

4.5 Android application libraries

5. Storage, Retention, and Security

5.1 Storage locations

The document library, page images, OCR results, and generated library PDFs are stored in Android’s private App files and database. Preferences are stored in private SharedPreferences; working copies use private cache. We do not maintain a cloud copy of your library. The App disables Android backup and excludes its data from the configured cloud-backup and device-transfer rules.

Exported files remain with the storage provider you select. Google services, communication providers, and recipients you choose may process information on servers outside your country. Their policies describe storage locations, transfer safeguards, and retention. This policy does not promise that all SDK data is stored in any single country.

5.2 Retention and deletion

• Saved documents: Kept until you delete the document from Documents, clear App storage, or uninstall. Deleting a document removes its database records and private document folder, including saved pages, text, and generated PDFs. Separate active-session copies or external exports may remain as explained below.
• Active scans and editing copies: Session references and working copies may survive navigation or a restart so you can resume editing. Starting a new scan/session or replacing the editing session clears the previous tracked session and releases its retained file grants. Untracked or interrupted cache files can remain until cache cleanup, clearing App storage, or uninstall; we do not promise immediate removal of every temporary file.
• Temporary OCR imports: Unless you choose Save to Documents, the App attempts to remove these imports when you leave the extraction view. If interrupted, temporary entries older than 24 hours are eligible for removal when the cleanup routine next runs; this is not a guaranteed 24-hour deletion deadline.
• PDF-tool working files: Normally deleted when processing completes or fails. Files left by an interruption may remain in private cache until cleanup. Passwords are not deliberately persisted as standalone App records.
• Exports, recipients, and clipboard: Copies saved outside private App storage, received by other apps, or placed on the clipboard follow your device/provider controls. Deleting the source in scan2pdf does not delete these copies. Remove exports with the relevant file provider and manage shared or copied content through the receiving app or Android.
• Preferences and privacy state: Retained until replaced, cleared, or uninstalled. Clearing App storage also deletes the private library; export anything you wish to keep first. Local deletion does not automatically erase records already held by Google or a recipient.
• Google service data: Google determines retention according to the service, purpose, security needs, and applicable obligations. See Google’s retention policy. We cannot set a single deletion period for Google’s server records.
• Support correspondence: If you contact us, we retain the message and necessary contact details while handling your issue and for necessary follow-up, dispute handling, or legal obligations. We do not apply an automatic App-based deletion timer to external correspondence. You may request deletion through Section 10; our communication provider may retain its own records under its policy.

5.3 Security

We use Android’s application sandbox, private storage, and scoped file grants to restrict access. Cleartext network traffic is disabled in the App configuration. Google documents encrypted transport for its advertising and ML Kit data. PDF password protection is available when you choose the Protect PDF tool; ordinary library files are not separately password-encrypted by default.

No storage or transmission method is completely secure. Protect access to your device and choose recipients carefully. If a security incident affects information under our control, we will take appropriate remedial steps and provide notices where required.

6. Sharing, Transfers, and Disclosure

6.1 Sharing

• Google processes advertising, privacy-choice, and SDK technical data as described in Section 4. Our advertising integration does not provide your document content to Google.
• Your chosen storage, sharing, translation, feedback, or browser app receives information needed for the action you confirm. Opening this policy in a browser contacts the policy website and exposes ordinary connection information, such as IP address and browser request information, to the website and its hosting provider; it does not upload your document library.
• We may provide information we hold when legally required, or when necessary to address fraud, security threats, or protect legal rights, subject to applicable law.

We do not sell your scans, PDFs, recognized text, or passwords. Advertising data flows may be treated as sharing or targeted advertising under some laws; available choices depend on your region and are presented through Google’s privacy messages and device controls.

6.2 Business transfers

If a merger, acquisition, or asset transfer affects personal information we hold, we will provide legally required notice and require appropriate protection by the recipient. A business transfer does not itself upload the private document library on your device.

6.3 Public disclosure

We do not publish your private document library. We disclose personal information publicly only with your authorization or where legally required.

7. Your Information and Choices

7.1 Access, correction, and deletion

Use Documents to view, rename, edit, export, and delete saved documents. Delete a document to remove its associated saved OCR results. Clear private App data through Android’s app storage settings, or uninstall, to remove the App’s local records; this also removes your private library. We cannot remotely retrieve or restore documents that exist only on your device.

For information we hold in correspondence, contact us to request access, correction, deletion, or other rights available under your local law, including restriction, objection, or portability where applicable. We may need proportionate information to verify your request. You may also complain to the relevant data-protection authority. Requests concerning data controlled by Google or another provider can be made through that provider’s privacy controls.

7.2 Permissions and advertising choices

You can revoke Camera permission in Android settings and continue using image import. Android’s advertising and advertising-privacy settings manage supported identifier and advertising-service controls; labels vary by device. When available, open Settings → Advertising privacy choices to revisit the Google form. Changing a choice affects subsequent processing and does not automatically delete past records.

The App’s introductory advertising agreement is separate from Google’s form. Declining that agreement closes the App; reopening lets you choose again. The App does not provide a universal in-app switch to revoke an already accepted introductory agreement. Clearing App storage resets local setup and privacy choices but also deletes local documents. Ad personalization choices do not necessarily eliminate all advertising or service data processing.

7.3 Accounts

scan2pdf has no user account, membership, or payment system. There is no account-deletion page. Use the local deletion controls above and contact us about information you have sent directly.

7.4 Responding to requests

We aim to reply to privacy requests within 15 business days and will comply with any applicable legal deadline. If more information or time is needed, we will explain why.

8. Children and Young Users

If you believe a child has provided personal information to us without appropriate authorization, contact us. We will investigate and take appropriate steps for information under our control. A parent or guardian can remove local documents using the controls in Section 7 and manage device permissions.

9. Changes to This Policy

We may update this policy as App features, permissions, services, or legal requirements change. The version and dates above identify the current text. For material changes, we will provide appropriate notice and obtain any further consent required by applicable law. The policy is accessible from the App’s welcome/privacy prompts and Settings.

10. Contact Us

For questions, complaints, or requests about this policy, contact the developer:

Developer: tasy
App: scan2pdf
Android package: com.camscanner.pdfscannerapp
Email: gz3create@163.com
WeChat: god_center

Please describe your request and include only the information needed to address it. Avoid sending document contents or passwords unless you decide they are necessary for your support request.

---

Thank you for trusting and using scan2pdf!
We are committed to protecting your privacy.

Developer: tasy