Why this exists

Looting and illicit trafficking destroy context (the thing that makes evidence meaningful) and can endanger communities and sites. Our policies are designed to reduce that risk while keeping research and debate alive.

Site protection icon

Protect sites from harm

We limit sensitive location disclosures because publicizing exact site locations can lead to harm, theft, or destruction. Many heritage frameworks explicitly allow withholding location data when harm could result.

Citations icon

Protect evidence integrity

Archaeological ethics emphasize stewardship and accountability: the record is irreplaceable, and research should support long-term protection. Provenance isn’t bureaucracy — it’s the chain-of-custody of truth.

Privacy icon

Protect people

We don’t host doxxing, harassment, or calls to action that target individuals. Field content that encourages trespass or dangerous access is restricted. Truth-seeking does not require reckless endangerment.

Heritage protection rules

This is the “anti-looting layer”: rules for what you can publish, how locations are handled, and what gets removed.

Policy: Stewardship-first. Reduce harm risk. Preserve in situ whenever possible. Applies to: posts, images, coordinates, access routes, collections, and external links. Enforcement: labels → redaction → removal → account action.
No actionable looting enablement

Don’t publish “how-to” content for accessing restricted areas, bypassing gates, night routes, hidden entrances, or any operational detail that materially increases the chance of theft or vandalism.

Sensitive location handling

We may reduce location precision or withhold coordinates when disclosure could lead to harm, theft, or destruction. This is a standard heritage-protection practice.

No collecting / no disturbance

Don’t encourage removing artifacts, digging, scraping, or “just taking a sample.” If you found something, document it responsibly and report via proper channels.

Provenance required for evidence status

Uploads presented as primary evidence must include provenance metadata (who/when/where/how obtained) and citations where applicable. Otherwise, it stays labeled as unverified.

Ethics backbone

Our stance is aligned with widely used archaeological ethics frameworks emphasizing stewardship, accountability, and preservation of the record. We also treat illicit trafficking as a serious harm to cultural heritage.

Location confidentiality (plain language)

If a post contains details that could enable theft or destruction, we reduce precision or remove the operational detail. In some jurisdictions, agencies explicitly limit archaeological site location disclosure unless it won’t cause harm.

We’re not trying to “hide history.” We’re trying to keep it from being sold on a black market with its context destroyed.

Field safety

Curiosity is great. Gravity is undefeated. Use this as a baseline for safer research behavior when traveling, hiking, or documenting ruins.

Map icon

Permission & legality

Don’t trespass. Respect closures, permits, and local laws. “But it’s on the internet” isn’t permission. If a site is restricted, document from legal vantage points or use published sources.

Evidence icon

Don’t enter unstable structures

Avoid tunnels, caves, shafts, collapsed rooms, and cliff-edge platforms unless you are trained and authorized. Structural failure + poor exits is a classic “headline-shaped” combination.

Site protection icon

Do no harm

No climbing fragile masonry, no scraping surfaces, no “chalk marking,” no moving stones, no removing anything. Leave no trace, and treat conservation as part of research.

Minimal safety checklist

  • Go with a buddy (or leave a clear itinerary with someone who can escalate if you don’t return).
  • Bring water, headlamp, power bank, weather layer, basic first aid.
  • Check local conditions (heat, storms, flash floods, wildfire smoke).
  • Don’t enter confined spaces without training + proper gear.
  • Keep a respectful distance from edges, cliffs, and unstable stone piles.
This isn’t exhaustive. It’s the “don’t become a case study” version.

Respect communities

  • Some sites have sacred/indigenous protocols. Follow them.
  • Don’t publish people’s faces or private property details without consent.
  • When in doubt: ask local authorities or stewards — or don’t publish.
A platform about the past should not trample the present.

Safe sharing toolkit

Use this to think like a steward: if someone malicious read your post, could they use it to do harm? If yes, reduce precision, remove operational details, or keep it private.

Location Redaction Preview

Public map pins should be coarse by default; sensitive sites may be region-only.
Region-only (safest)
Approx (public pin)
Trusted (private)
Mode: Region-level. Enter latitude + longitude to preview redaction.
Best for sensitive or restricted sites: share the nearest city/region, not coordinates.
Example payload (UI can store both public + private versions when appropriate): { "location": { "mode": "region", "note": "Enter coordinates to compute redacted output." } }

Safe-sharing checklist

  • Remove hidden entrances, bypass methods, gate weaknesses, and off-hours suggestions.
  • Remove exact coordinates for sensitive, unprotected, or remote sites.
  • Don’t post “find spots” for artifacts, bones, or fragile features.
  • Prefer published sources: papers, museum catalogs, official site pages, reports.
Rule of thumb: if a looter could use it as a shopping list, it belongs in private stewardship channels (or nowhere).

How Evidence Atlas handles locations

  • Public: region-level or coarse pins for general discovery.
  • Sensitive: reduced precision + delayed reveals + curator gating.
  • Restricted: no public coordinates; citations only; “research summary” allowed.
This mirrors common disclosure practices where site locations are withheld if harm could result.
Location Handling: disclose only when it won’t cause harm, theft, or destruction. Tools: redaction, precision reduction, access-route removal, gating. Receipts: actions get logged in moderation/corrections when applicable.

Many heritage systems treat location information as sensitive and allow withholding it unless disclosure will not lead to harm, theft, or destruction. We apply a similar safety logic: public discovery does not require precise coordinates for vulnerable sites.

Report a heritage or safety risk

If you see looting enablement, sensitive-location leaks, threats, or dangerous “field instructions,” report it. Faster reports = less harm.

Risk Report

Seeded demo form — wire a backend endpoint when ready.
Read Moderation
Emergency note: this isn’t an emergency service. If immediate danger exists, contact local emergency services first.

Founding Access

Help us tune the safety stack: redaction defaults, disclosure gating, reporting flows, and public receipts. Founding Access ships in waves.

No spam. No selling your data. See Privacy.
Saved Done.