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 data-flow context that helps explain how the public V1 handles local processing, imports, cloud connections, optional AI assistance, Split Bill participant links, 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 hosted 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.

Optional AI assistance for naming or metadata suggestions is not part of normal local OCR. It is used only after an active user request and the required consent, and may transmit document context required for the specific request to an AI provider named in the app.

Split Bill is a limited sharing feature and a documented exception to the general local archive model. The public Split Bill page processes structured receipt item and selection data, but it does not upload or display the original receipt image or PDF there.

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 for limited provider connection functions, structured Split Bill session, item, participant selection, and link data, and coordinated forwarding of optional AI requests to the named AI provider. Supabase is not a general document-storage backend or document-file proxy for archive documents.

Anthropic or another AI provider named in the app may process document context if you actively use an external AI function and have consented. AI results remain suggestions and are not automatically adopted as final document data.

Vercel hosts and routes the website, legal pages, support pages, and public Split Bill participant page, and may process technically necessary access, security, and routing data for that purpose.

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.

When a Split Bill link is created or opened, private link identifier, receipt title, merchant name, currency, total amount, recognized item names, amounts, quantities, participant names, browser-local participant identifier, selection status, timestamps, and an optional PayPal.me link may be processed.

Anyone who has the active Split Bill link may be able to open the public participant page. PayPal.me is opened externally only; Scan & Store does not process payments or hold funds through Split Bill.

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.

Active Split Bill sessions, item data, participant names, participant selections, optional PayPal.me link references, and link status remain until the creator closes or deletes the Split Bill, until the configured expiry or deactivation takes effect, or as long as needed for security, abuse prevention, legal compliance, dispute handling, and operational integrity.

AI consent and audit metadata may be retained for evidence, withdrawal handling, security, abuse prevention, premium access validation, or legal compliance. Complete AI request texts, transmitted document contents, PDFs, OCR text, or complete AI provider responses are not stored as diagnostics or product analytics logs.

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, the AI provider used after active request and consent, 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.