A screenshot or sample page can expose names, addresses, account numbers, or medical details. You can usually explain a scanning problem with your device, app version, lighting, and the steps that cause it instead.
Step by step
- Recreate the problem with a test page.Use a blank page or a made-up document when you can. Write down exactly what you did, what you expected, and what happened.
- Note your device details.Include device model, operating-system version, Paperlane version, camera mode, and whether the issue occurs offline.
- Send as few attachments as possible.Send logs or screenshots only when support asks for them. Crop or redact sample content, and don’t assume a black box drawn over text removes it from the file.
- Check who you’re sending to.Confirm the support address and delete drafts or downloaded samples after the case is resolved.
Check before you send
A good support report lets someone recreate the problem without having your private document. If they really need a real page, first ask how it will be stored and who can see it.
- You recreated the problem with a test page.
- Device and app versions are included.
- Attachments show as little as possible.
- You checked the support address.
Paperlane support shouldn’t need your full private documents to look into an ordinary camera, OCR, or app screen problem. Send only what shows the problem.
How to get useful support without sharing the document
Support usually needs the steps that cause the problem and your device details, not your full passport, contract, or medical record. Start with a blank page or made-up sample that causes the same problem.
Include device model, operating-system version, app version, camera mode, whether you were online, and what you expected versus what happened. Support can then look into the problem without seeing what’s in your documents.
How to decide
Don’t send a screenshot that shows names, account numbers, or a readable page. A black rectangle drawn on top can leave the text underneath readable, so delete the content or use a real redaction tool instead.
Send only what shows the problem, check the support address, and delete drafts or downloaded samples once the case is closed. If support needs a real document, ask how it will be stored first.
Example
Imagine a support request includes a screenshot with a client name and account number even though the bug is a camera outline that flickers on a blank page.
Recreate the problem on a blank page, give your device and app details, and send only what shows the problem. Support needs to know how to make the bug happen, not to see your documents.
Questions people ask
Should I email the original scan? +
No, not by default. Describe the issue and use a made-up or redacted sample unless support clearly explains why they need the original.
Is drawing a black rectangle enough to redact? +
Not always. Use a real redaction tool or delete the content. A shape drawn on top can leave the text underneath readable.
Should I email the original scan to support? +
Not by default. Use a made-up or properly redacted sample unless support explains why they need the original and who will be able to see it.
After you scan, check where copies ended up: the app you shared to, previews, backups and temporary exports. Delete any you didn’t mean to keep.