What Copper collects

• Contact details you submit, such as name, email, company, and project notes.
• Design artifacts you choose to send for review, including board files, BOMs, schematics, PDFs, and related context.
• Operational metadata needed to run the service, such as timestamps, request logs, and review status.

How Copper uses it

• To perform board reviews and produce evidence-backed PDF reports.
• To contact you about review status, questions, payment, sample approvals, or support.
• To improve review quality using aggregate process lessons, not customer source files.

Ephemeral processing

• Uploaded zip files are mounted read-only in a throwaway review environment using sandboxed infrastructure and temporary filesystems.
• Copper processes the files, generates the review, then destroys the review environment.
• A human reviews the final report before delivery to keep findings accurate and useful; this sign-off is quality control, not reuse of your source data.

Source file deletion

• Uploaded source files and generated review reports can be deleted upon request at any point.

No training use

Copper does not use uploaded design files, excerpts, or review context to train models.

Exposure controls

• Copper avoids logging full file contents or sensitive excerpts.
• Temporary storage uses encryption in transit and at rest.
• Agents and tools run with least-privilege access to only the files needed for the review.

Confidentiality

Copper treats design files as confidential review material. Public testimonials, sample reports, or excerpts are used only with explicit permission. NDAs can be signed on request before sending files.

Contact

Questions or deletion requests can go to milind@trycopper.app.