How to Collect Customer Photos and Documents Privately

Private customer file collection should answer four questions: how the customer uploads, where the files appear, who may use them, and when they are removed. Evaluate those decisions separately. A private upload link, encryption, AI analysis, and retention are related features, but none substitutes for a clear explanation of the others.

Entagl's secure file uploads let the AI or team request supported customer files through a private upload page connected to a conversation. This guide explains the workflow and the questions a buyer should ask before adopting it.

Why use an upload page during a conversation?

Customers may need to send property photos, product pictures, a PDF, or another file to help the business understand a request. Attaching that file directly to a social message places a copy in that messaging service. A dedicated upload page offers a different collection path.

In Entagl, the customer opens the link in a browser and sends the supported files there. Accepted uploads appear in the relevant conversation with a Vault badge marking private uploads and are associated with the customer's media. The team can review them where the request happened.

This does not erase copies already shared elsewhere. If the customer previously attached the same photo to another app, deleting the Entagl copy does not remove the other copy.

What should the owner configure?

Before sending the first request, review the accepted file types, retention period, and whether AI analysis is allowed. The operator should understand each setting in ordinary language and know where to change it.

Entagl's secure-upload setup guide documents these controls. File storage and AI analysis have different limits: a file may be accepted for the team to inspect while being too large or otherwise unsuitable for automatic analysis. Ask the provider to demonstrate the file types and sizes your customers normally send.

Decision	Buyer question	Evidence to request
Collection	What does the customer open?	The actual upload page
Access	Who can use the link and view stored files?	Link rules and team permissions
AI processing	Can I disable analysis?	The setting and its effect
Retention	What happens at the deletion date?	Policy and the visible file state

Is a conversation-linked URL proof of identity?

No. A link may belong to one conversation without proving who is using it. Possession of a valid forwarded upload URL can allow someone else to submit files into that conversation. Keep the link private and explain this distinction accurately.

Ask what happens when the link expires or is revoked. Also ask whether revocation affects files already uploaded. In Entagl, revocation and file deletion are distinct operations; stopping future uploads does not itself remove existing stored files.

An honest explanation of link access is more useful than an undefined promise that an upload is “completely secure.” Review Entagl's data-protection information and the applicable privacy policy for the broader processing context.

Can the AI still help with privately uploaded files?

Entagl offers a setting controlling AI analysis of secure uploads. With analysis enabled and a supported file, the AI can use the uploaded information as part of the conversation. With it disabled, the team can still inspect the files in Entagl.

The important question is whether the setting matches the business's purpose. A private file does not mean that no service provider ever processes it. Encryption at rest and in transit should not be described as an end-to-end confidentiality guarantee when a service must process the content.

For regulated information, establish the applicable configuration and agreement before using the workflow. This article does not determine whether a particular business process satisfies a regulation.

How should you test retention and the team workflow?

Use demonstration files, not a real customer's sensitive information. Send the link from the inbox, upload a supported file, and confirm it appears in the expected conversation. Check its visibility on the customer record and test the analysis setting where appropriate.

Then inspect early deletion and link revocation as separate scenarios. Make sure the operator can explain the result. The conversation may retain an indication that files were received or deleted even after the file itself is unavailable. Backup handling belongs in the policy and agreement; do not infer it from a disappearing thumbnail.

Private uploads also connect to customer intake choices and the need for human control over AI work. The whole process should help the team make the next decision with the minimum information needed.

FAQ

Does the customer need an Entagl workspace account?

The customer uses the upload link in a browser. They do not need to sign in as a business user of the Entagl workspace.

Can I stop the AI from analyzing uploaded files?

Yes. Entagl's secure-upload settings include a control for AI analysis. The team can still access the supported uploaded files when that analysis is disabled.

Does revoking a link delete the files?

No. Link revocation stops the link's future use. Delete stored files through the relevant file action or retention process.

Is a private upload the same as a normal attachment?

No. Compare the collection path, access, storage, analysis, and retention behavior. A feature name alone does not establish that two attachment paths have identical controls.

Book a demo to follow a private upload from the customer page to the inbox and its retention controls.

Reviewed September 2026. Sources: Entagl secure-upload documentation and privacy information. Demonstration scenarios should use sample files.