How to protect whiteboard photos — on device, in the cloud, and in transit.

## At capture time

Capture directly in BoardSnap rather than using the native Camera app and then importing. This keeps the raw image inside the app's sandboxed storage rather than your open camera roll, which may sync to iCloud, Google Photos, or be visible to any app with Photos access.

## On your device

• iPhone encryption: iPhones encrypt local storage automatically when a passcode is set. Ensure your device has Face ID/Touch ID and a passcode enabled.
• Strong passcode: Use a 6-digit or alphanumeric passcode. "1234" defeats encryption in practice.
• Photos app access control: Review which apps have Photos access in Settings > Privacy & Security > Photos. Limit access to apps that genuinely need it.

## In the cloud

• iCloud Photos: Images captured in the native camera roll are uploaded to iCloud by default. If the board contains sensitive content, either disable iCloud Photos or delete the image from your camera roll before it syncs.
• Shared Albums: Never add sensitive whiteboard photos to shared iCloud albums — everyone in the share has access.
• Google Photos backup: Same concern if you use Google Photos on your device.

## When sharing

Prefer text over images. BoardSnap's summary and action item output is text — copy it, control exactly what you send. The raw image is a single file that can be forwarded, downloaded, and shared without your knowledge.

For image sharing when necessary: use channels where access is controlled (restricted Slack channels, company-managed SharePoint, not personal email).

## Deleting after capture

Once BoardSnap has processed a board and you have the summary output, delete the raw photo from your camera roll if the board content was sensitive. Go to Photos > Recently Deleted and clear it there too — it stays for 30 days otherwise.