Questions on Data Handling and Credential Management in Adobe Extract API

Question

Hi Adobe Team,We are currently using the Adobe PDF Extract APIs to process PDF documents that are highly confidential. To align with our data security policies, we plan to use external storage, as we do not want customer data to persist on Adobe Cloud storage.I have a couple of questions regarding this:Transient Storage: Even when using external storage, does Adobe internally use any transient or temporary storage during the document processing phase? If yes, how is that data handled or purged to ensure data privacy?Credential Management: Is there a secure way to access the API via SDKs without hardcoding sensitive credentials like client_id and client_secret in the source code? For example, can we leverage environment variables, secure token exchanges, or any recommended practices from Adobe?Looking forward to your guidance on these aspects. Thanks in advance! Regards,Shivang

wilda_1157 · Answer

Hello!Regarding highly confidential PDF processing with Adobe PDF Extract APIs: yes, transient storage is used during processing, but documents are purged once extraction is complete and results are delivered, with detailed policies in your DPA. For credential management, avoid hardcoding client_id and client_secret by using environment variables or, ideally for production, secret management services (like AWS Secrets Manager or Azure Key Vault) that allow secure runtime retrieval via IAM roles/service accounts, aligning with industry best practices for data privacy.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded