Reporting a Scribd document that exposes personal information

01

Locate the exposure precisely

Save the document URL, uploader name, title, date observed, and page numbers. Explain the type of information involved without unnecessarily repeating complete identifiers in an ordinary email. For example, an unredacted customer list requires identifying the affected pages and your relationship to the records, not reposting the list publicly to demonstrate the problem.

02

Choose the appropriate support route

Use the support contact linked from Scribd's Community Guidelines and describe the privacy concern; do not select a copyright form unless your claim concerns copyright. If you uploaded the file yourself, also review the controls for that upload. A privacy-rights request concerning information Scribd holds about you is related but distinct from reporting a third party's document. The help center provides a privacy form and directs unlisted requests to support; eligibility and scope can depend on location and circumstances.

• Provide the direct document link and relevant page references.
• State whether you are the affected person or an authorized representative.
• Share only the verification material required through the official process.

03

Follow the actual result

Keep the request reference and check whether the document was removed, redacted, or left available. If it changes, inspect the original URL and relevant search display separately. A search update does not delete a live document, and a platform removal does not retrieve files already downloaded. If the exposure involves organizational records, involve the responsible privacy or security team to address the source of the leak.

Continue with your next step

Related guides on this topic