Features
Websites & publishingPortfolio engineMedia & deliveryConservation & fieldworkClient deliveryCoursesCommerce & operationsTeam & workflow
FoundationSolutionsPricing
DocumentationGuides
About
AboutCommitmentNewsroom
Sign In
ArtInStack

The creative operating system

Product

  • Features overview
  • Websites
  • Portfolio
  • Media
  • Conservation
  • Client delivery
  • Courses
  • Commerce
  • Team
  • Solutions

Resources

  • Guides
  • Documentation
  • Platform foundation
  • Pricing
  • Changelog
  • Roadmap

About

  • About
  • Commitment
  • Newsroom
  • Status
  • Talk to us

Customer login

© 2026 ArtInStack. All rights reserved.

Privacy policyTerms of service
All documentation

Conservation and Fieldwork

  • Conservation and fieldwork overview
  • Field surveys and deployments
  • Tag species and observations
  • Data Governance for conservation
  • Impact maps and location privacy for conservation
  • Public observations on photo detail pages
  • Evidence of Impact
  • Conservation Story
  • Fundraising campaigns for conservation
  • Impact Records
  • Events and volunteers for conservation
  • Export a Camtrap DP package
  • Prepare and publish to GBIF
Platform Migration
Documentation/Conservation and Fieldwork

Data Governance for conservation

Configure org-wide location privacy for field work: IUCN threat tiers, species overrides, and time-bound embargoes so Evidence, Impact Map, and GBIF or Camtrap packages follow one policy above Geo privacy.

Field programs need one privacy policy for maps, Evidence, and harvest packages, not three separate habits. Data Governance is that policy when your plan includes field surveys. Open it under Settings → Privacy & security → Data Governance. It stacks above your everyday Geo privacy defaults.

Studios without field surveys never see this panel. Geo privacy under Location Data remains the baseline for every organization.

For judgment background, read Publishing sensitive species. This page is the settings how-to.

Prerequisites

  • A plan that includes field surveys
  • Admin access to Settings
  • Optional: surveys with tagged observations and IUCN categories (from GBIF species suggest)

How the cascade works

Most specific rule wins:

  1. Manual rules and embargoes: survey or deployment Public after date; per-species overrides (force fuzz or withhold)
  2. Automatic threat tiers: when enabled, IUCN bands (for example CR/EN, VU) apply your configured fuzz radii or withhold
  3. Geo privacy baseline: Location Data fallback fuzz and portfolio Public map location (exact, redacted, or hidden)

Portfolio albums still set the baseline. Governance can still soften or hide pins for photos that carry conservation observations, even on an exact album, without changing albums that have no observations.

Open Data Governance

  1. Go to Settings → Privacy & security.
  2. Open Data Governance (only visible when field surveys are on your plan).
  3. Review the read-only line for your Geo privacy fallback fuzz radius. Change that baseline under Location Data if needed.
  4. Save with the normal Settings Save control.

Automatic threat-based obfuscation

Turn on automatic threat-based obfuscation when you want IUCN categories to enforce location policy without a per-photo checkbox.

Band (typical)What you configure
CR / EN (and similar)Fuzz radius (often kilometers) or withhold; optionally mask place names
VUSmaller fuzz or withhold
NT / custom bandOptional lighter fuzz

Apply to checkboxes choose which surfaces obey the tiers:

  • Public Impact Map
  • Evidence feeds
  • GBIF / Camtrap packages

With the toggle off, overrides and embargoes still apply. IUCN tiers do not run automatically.

Species overrides

Use the override table when a locally sensitive site is not well covered by global IUCN status (for example a common species at a sensitive rookery).

For each override: GBIF taxon key (and optional scientific name), action (fuzz or withhold), optional fuzz meters, optional mask of public place names.

Overrides beat automatic tiers for that taxon.

Time-bound embargoes

Set an organization default embargo for new surveys (none, 6 / 12 / 24 months, or custom days). New surveys can receive a Public after date from that default.

Until that date:

  • Items stay off the public Evidence feed
  • Related pins stay off public Impact Map when those photos are the pin source
  • Rows are omitted from GBIF Prepare and Camtrap partner packages

Edit the date on the survey (and optionally per deployment). When the date passes, gates lift automatically. You do not need a separate “make public” switch.

What each surface does

SurfaceBehavior
Impact MapAlbum public map location first; conservation observations can still fuzz, withhold, or omit
Evidence of ImpactPlace chips and station pins follow the cascade; shared stations use the station’s strictest rule
GBIF PrepareSame omit/fuzz rules; you still confirm fuzz vs withhold when sensitive detections require a choice
Camtrap exportPartner zip applies the same omit/fuzz/withhold rules as Prepare

Shared responsibility for location

Location privacy is a partnership between ArtInStack’s public surfaces and the files you upload and share.

ArtInStack protectsYou remain responsible for
Softening, hiding, or omitting places on Impact Map, Evidence, and related public page content according to your portfolio and Data Governance settingsChoosing what to upload (including whether camera GPS stays in the original file)
Applying the same omit / fuzz / withhold rules you confirm in GBIF Prepare and Camtrap partner packages for table coordinatesStripping or avoiding GPS in files before upload when a downloadable original must never carry exact location
Not linking private storage media as public image URLs in harvest packagesReviewing Prepare’s private-media advisory, and deciding whether image links belong in a given harvest
Keeping map and page controls separate from partner exportsTreating partner zips, IPT uploads, and public image downloads as channels you control

ArtInStack does not rewrite or strip GPS from the image files you store and publish. Soft pins on your site are not the same as cleaning GPS out of a downloadable JPEG. For maps and exports in practice, see Impact maps and location privacy and Prepare and publish to GBIF.

Steps

  1. Confirm field surveys are on your plan.
  2. Open Data Governance and note the Geo privacy baseline link.
  3. Decide whether automatic threat obfuscation should be on; set band actions and apply-to surfaces.
  4. Add species overrides for local exceptions.
  5. Choose an embargo default for new surveys; set Public after on active sensitive surveys if needed.
  6. Preview Evidence and Impact Map signed out; run Prepare once on a test survey if you publish to GBIF.
  7. For sacred or patrol-sensitive sites, confirm originals are GPS-clean before upload if downloads or partner handoff must never carry exact coordinates.

Verifying your setup

  • With automatic obfuscation on, elevated IUCN rows show approximate (or withheld) places on Evidence and soft pins on maps.
  • A species override forces fuzz/withhold even when IUCN is Least Concern.
  • Embargoed surveys disappear from public Evidence until the date passes.
  • Albums without conservation observations still follow ordinary Geo privacy only.
  • GBIF Prepare still asks you to choose fuzz or withhold when the checklist requires it.

Next in this flow

Impact maps and location privacy for conservation

Related documentation

  • Impact maps and location privacy for conservation
  • Evidence of Impact
  • Prepare and publish to GBIF
  • Export a Camtrap DP package
  • Portfolio geo visibility and impact maps
  • Privacy & security overview
  • Publishing sensitive species
  • Conservation and fieldwork overview