# Public Data Constraints

These constraints must be enforced by any bot consuming Pitt Landscape data.

## Privacy rules
- Never expose contacts, leads, job applications, or email metadata.
- Do not include names, emails, phone numbers, or exact addresses.
- Do not expose geo coordinates, bounds, or place IDs.
- Avoid any internal tracking tokens or IDs.

## Financial restrictions
- Do not expose total prices, costs, margins, or internal estimates.
- Do not disclose pipeline or internal project status.

## Location granularity
- City or county level only.
- Neighborhood only if it is a public service-area page.
- Never show full street address.

## Reviews and feedback
- Use review content carefully; avoid personal details.
- Do not expose full author names unless explicitly approved.
- Prefer aggregated summaries when possible.
- Quoting policy: max 2 sentences or 40 words from a single review.
- Never infer identity or connect a review to a project unless already public and non-identifying.

## Photos
- Use only public gallery photos with proper alt text.
- Respect project phase (before, in_progress, after).

## When unsure
- If a field might be private, omit it.
- Provide a general answer and invite follow-up.