Know the data boundaries.

Three clear boundaries

Data on the mobile device

• The selected server address and scoped API token are stored locally; credentials and account-specific saved searches use device secure storage.
• Camera captures, shared items, and files or photos explicitly selected by the user are copied into a protected, backup-excluded upload queue. Failed or unfiled items remain until uploaded or explicitly discarded.
• Each staged or downloaded file is limited to 64 MiB, and every mobile write must preserve 512 MiB of free space. The app requests no broad photo-library or storage permission.
• Optional offline document copies are protected, backup-excluded local files. More → Privacy & storage reports their usage and can remove copies for the current account or accounts no longer signed in.
• Opening or sharing a server document creates a protected temporary export. Failure, cancellation, sign-out, the next cold launch, or a 24-hour limit removes app-held exports. A file handed to another app or copied to the clipboard is then controlled by that destination.
• Device OCR can add recognized text, confidence, and language to an upload. Enabling “Server OCR only” before starting an upload omits that metadata.

Android excludes all Companion app data from backup and device transfer. On iPhone, queued and offline files are excluded from backup, but a Keychain credential may survive uninstall; sign out or revoke the token at the selected server before uninstalling when credential removal is required.

Suchi operates no advertising, remote crash-reporting, analytics, or document-relay service. On Android, Google Play services’ ML Kit document and QR scanners separately collect device and app information, identifiers, performance and configuration metrics, and feature event and error data for diagnostics and usage analytics. QR auto-zoom also collects a generated scanning-session ID, zoom changes, and predicted barcode bounding-box coordinates. Google says QR images are processed on-device and it does not store the image or result. See Google’s ML Kit Android data disclosure and code scanner guide.

Data on a self-hosted server

The selected server receives the API credential, uploaded document bytes, and any submitted device-OCR metadata. It can store originals, derived files, searchable text, metadata, thumbnails, account records, and operational logs. Its operator controls hosting, access, backups, retention, and optional processors or integrations. Those integrations may send data to providers chosen by the operator.

A document moved to Trash is normally recoverable for 30 days unless permanently deleted sooner. A purge removes document records and rendered files; unreferenced blob bytes remain until the operator runs offline garbage collection. Backups and exported copies follow the operator’s own retention policy. Ask the operator of your server about its actual configuration. The server privacy guide describes stock behavior.

Data on this public website

The website has no archive login or upload path. It sets no application cookie and includes no analytics, advertising beacon, or third-party active resource. The host receives ordinary HTTPS request information, including IP address, requested path, time, and browser headers, for delivery, security, and operational logs. Following an external link makes a request governed by that site’s policy.

Requesting Companion early access opens your email app; this website does not submit a form or store the address. Messages go directly to [email protected]. A supplied Google Play account email is used only to manage Android tester access and related early-access messages. You may ask for it to be deleted at any time.

Retention, deletion, and contact

• Sign out to remove the local API token, temporary exports, and the current account’s offline copies. Queued originals remain to prevent silent data loss; discard them explicitly in Scan → Uploads.
• Use More → Privacy & storage to inspect and remove current-account or orphaned offline copies, protected cleanup leftovers, and saved searches.
• Contact your server operator for account access, server-side deletion, logs, garbage collection, processors, or backup retention.
• For this website or the mobile companion, email [email protected]. Do not send passwords, API tokens, private server URLs, or document contents.