# Review workplace and event photos before posting

> Check faces, badges, screens and documents in a team or conference photo before sharing a public copy.


A photo for a team update or conference post can contain more than the people posing for it. A screen in the background, a visitor badge or papers on a table may reveal details you did not intend to publish. A face review and a background review belong in the same workflow.

Start with your organisation's sharing process and the preferences of the people shown. A picture being taken at work does not tell you that everyone is comfortable appearing on a public account.

## Agree on the purpose and audience

Is this an internal update, a personal post or an official publication? Confirm the intended destination before editing. For clients, visitors or colleagues who prefer not to appear, consider whether a face cover addresses their preference or whether another image is more appropriate.

BlurFaces cannot determine permissions or assess whether a document is confidential. Make those decisions using the information and process available to you.

## Inspect screens and readable details

Look for employee names, badge numbers, client references, visitor lists, whiteboards, calendars and open chat windows. Read the background at a useful zoom level. A small detail on a phone can be easy to overlook when the main subject looks fine.

A manual box can cover a rectangular area such as a badge or part of a screen. If there are many details to remove, a simpler source image may be easier to review reliably. BlurFaces is not an automatic document-redaction system.

## Cover faces and details deliberately

Open [the local photo editor](https://blurfaces.app/private-image-editor). Review detected faces and add missing regions manually. Automatic boxes below 100 source pixels in either dimension are skipped. Move or resize the active areas before choosing an effect.

Block gives opaque rectangular coverage inside the selected region. Blur and pixelation retain transformed detail, so do not assume that lightly softened text is unreadable. Check the rendered pixels for each covered area, including any details outside the box.

## Keep the workflow suited to the organisation

Local photo processing means the image is not uploaded to BlurFaces for editing. The site still loads assets and has optional usage analytics; review [the privacy policy](https://blurfaces.app/privacy) when evaluating the workflow. Local processing does not replace your organisation's requirements for devices, storage or publication.

Download the copy, reopen it and check it before posting. Source metadata is not copied, while original dimensions are retained. Review the filename and caption, and make sure the uploaded attachment is the edited export.

Use the [before-posting checklist](https://blurfaces.app/guides/photo-privacy-checklist) as a final sweep. The goal is an intentional public copy, with the organisation and the people involved deciding what belongs in it.

[Open the photo editor](https://blurfaces.app/private-image-editor)

## Keep reading

- [A photo privacy checklist before you post](https://blurfaces.app/guides/photo-privacy-checklist.md)
- [Sharing street and travel photos with fewer visible bystanders](https://blurfaces.app/guides/street-photography-bystanders.md)
- [Check marketplace listing photos for personal details](https://blurfaces.app/guides/marketplace-listing-photos.md)

[BlurFaces app](https://blurfaces.app/) · [Privacy policy](https://blurfaces.app/privacy)