Data Processing Information for "Scan & Store"

This page provides supplementary technical data-processing information for Scan & Store in connection with the Scan & Store mobile application and its included extensions. It complements, but does not replace, the full Privacy Policy published at /en/privacy-policy.

This page is limited to technical data-flow context that helps explain how the public V1 handles local processing, imports, cloud connections, backups, and related third-party involvement.

The currently shipped public V1 stores archive documents in a standard local archive within the app's private storage area on your device and does not operate a general server-side document storage backend for user documents.

Core scanning, local storage, OCR, archive organization, editing layers, and many viewer functions are designed to work primarily on-device.

Certain imports may temporarily pass through a shared local staging zone used by extensions and handoff flows before being copied into the archive or cleaned up. The public V1 does not expose or require a separate Vault feature.

If you connect Google Drive, Dropbox, or pCloud, readable PDF files, filenames, folder structure, and restore or sync metadata may be transferred directly between your device and the selected provider rather than through a general Scan & Store document backend.

For Google Drive, the current shipped connection flow requests the full Google Drive scope https://www.googleapis.com/auth/drive as currently implemented in the app, which may permit broader Drive access than a single app-specific folder.

Apple handles App Store distribution, in-app purchase billing, subscription management, and restore-related platform functions. RevenueCat is used for product loading, entitlement resolution, subscription state, and purchase restoration support.

Supabase is used only for limited authentication and connection functions in connection with the pCloud flow and is not used as a general document-storage backend or document-file proxy.

The Share Extension can copy files and images into a shared local import zone used by the app as a temporary staging area and subject to app cleanup.

When you import content from an http or https link via the Share Extension, the extension may contact the third-party server hosting that resource directly in order to retrieve the file.

The Document Picker Extension and File Provider Extension operate with the same shared import and app-group-based local zone. The current V1 File Provider is import-oriented and is not described as a general browser for the private archive stored inside the app.

Locally stored archive content remains in the app's private storage area on your device until you delete the relevant document, reset the app, or otherwise remove local data. Trash content remains until you clear it, the app cleans it up according to lifecycle logic, or local reset/removal occurs.

Cloud copies and related restore or sync metadata at Google Drive, Dropbox, or pCloud remain subject to deletion actions you trigger and the provider’s own systems and retention logic.

Depending on your device settings and Apple backup behavior, local app data may also be included in device backups, including iCloud backups, unless excluded from backup. Deleting content in the app does not automatically delete copies that may already exist in device backups or with third-party cloud providers.

International transfers may arise through the third-party provider you connect, Apple service infrastructure, RevenueCat service infrastructure, Supabase service infrastructure, or website and hosting infrastructure where applicable.

For authoritative information about legal bases, rights, retention logic, recipients, and current processing details, refer to the full Privacy Policy at /en/privacy-policy.