Receive identity documents through websites and email
Define why a copy is needed before asking customers to upload one. Identify the legal basis, necessary fields, access permissions and deletion schedule. Explain these points to the person. A document-redaction tool can support data minimisation, but it does not establish a legal basis or make a workflow compliant by itself.
Control the intake channel and storage
Use authenticated upload links, encrypted transport and restricted staff access. Keep documents out of public folders and routine support-ticket attachments. Track copies in email, CRM systems, exports and backups. Decide what must be retained and how removal is verified. A shared mailbox should not become a permanent identity-document archive.
Give the sender a clear checklist
Specify which fields must remain visible, which can be masked, accepted file formats and maximum size. Let the sender review a redacted copy before transmission. For large volumes, use a documented review process and account quotas. Keep exceptions and retention decisions separate from recognition results; a risk score is not an identity-verification decision.
How Sandocs processes your document
Web sends images over HTTPS for processing in memory. Accounts and quota records are stored separately from document contents. Desktop processes images locally and contacts the server for sign-in and quotas. Cloud AI sends images to the selected provider only when enabled. Check the provider’s retention settings before using cloud analysis.