# ScubaRogue Data Source Policy

## Principle

ScubaRogue should use third-party sites as attributed reference sources, approved API/feed sources, or partner-submitted data. Do not copy or scrape protected content by default.

## Source Roles

| Source | Role | Use |
|---|---|---|
| PADI | Training-agency and dive-region reference | Destination guidance, shop locator links, certification context |
| SSI / divessi | Training-agency and dive-center ecosystem reference | Certification pathway and center/resort reference |
| Tripadvisor | Review signal | Use only through approved Content API/widgets/manual links and display rules |
| Local operators | Primary operational truth | Operator-submitted details, trip availability, gear hire, boat model, group sizes |
| ScubaRogue | Editorial intelligence | Difficulty, capability fit, trip design, gear checklist, cost envelope |

## Integration Ladder

| Stage | Description |
|---|---|
| Manual attributed source | Link to PADI/SSI/operator/Tripadvisor pages and summarize in ScubaRogue words |
| Operator-submitted profile | Operator provides approved details and commercial relationship status |
| Approved API/feed | Use formal API key, partner feed or widget under source terms |
| Automated sync | Pull current ratings, availability or data after permissions and display rules are approved |

## Do Not Do

| Avoid | Reason |
|---|---|
| Blind scraping | Legal, terms and reliability risk |
| Copying reviews or destination text | Copyright and trust risk |
| Claiming PADI/SSI approval | Must be backed by verifiable affiliation or source |
| Claiming preferred/partner status | Must be backed by relationship or agreement |

## V1 Position

R11/R12 should use curated source links, source labels and ScubaRogue editorial interpretation. Live feeds can be designed into the data model, but source access should be validated before implementation.