Your location should help wildlife—not expose you or it.

What the pilot stores

• Wildlife reports: species, time, behaviour, group details, optional notes and the location supplied by fresh phone GPS or original photo metadata.
• Evidence: photos or audio you deliberately attach. Original media can contain precise location and capture-time metadata.
• Arrival updates: whether an animal is still visible, visibility, side of road, estimated habitat distance and the confirming phone location.
• Installation identifier: a random identifier used to return your own pilot records and prevent duplicate submissions. It is not your phone number or advertising ID.
• Consent receipts: the optional purposes you choose, policy version and time of the choice.
• Beta-trial and official-waiting-list details: your name, surname, email address and phone number, together with the consent version and time of your request. The lists are stored separately. Joining one does not enrol you in the other, create an account, or subscribe you to community membership or general news.
• Administrator activity: approved staff identity, role changes and security-relevant Control Centre actions.

Two separate signup choices

The beta-trial list is used to contact people who volunteer to help test Wild This Way. The official waiting list is for official-release notification only, after both milestones are verified: the app has been running for at least three months and at least 90% of testing is complete. There is no fixed notification date, and the email-notification service is not yet connected. Existing beta-interest records remain in the beta list and are not copied to the official list.

Either list can be joined independently, including both by submitting both forms. To request a copy, correction, withdrawal or deletion of a list registration, email info@wildthisway.com and tell us which list you mean. We will verify your identity before releasing personal data. These contact records are not part of device-only sighting exports.

Why it is used

Essential processing supports the live map, truthful sighting records, safe roadside routing, quality checks, duplicate control, wildlife protection and the private journal. Optional route research, audience research, recommendations and marketing remain separate choices. The pilot does not currently activate optional research or marketing from a single toggle: a second confirmation service must be connected first.

Sharing and sale

The pilot does not sell personal data and has no commercial data-sharing feed. Approved employees may access only what their role permits. Future conservation sharing must be deliberately approved by the owner, limited to a named purpose and recipient, and redacted or aggregated unless exact access is genuinely necessary and separately controlled. Hosting, identity and storage providers process information only to operate the service.

Your choices and rights

The app works without optional research, recommendations or marketing consent. In My Wild → Consent Centre you can change or withdraw those choices, download the records tied to this installation, or delete its sightings, confirmations, evidence and consent receipts. Browser storage must remain intact for the pilot to recognise the same installation. Authentication-provider records and necessary security logs are handled separately.

Location and safety

GPS is requested only for map, reporting or active navigation functions. A trip trail is kept on the device to support a return route and is not uploaded as continuous tracking in this pilot. Do not report while driving unless you are a passenger; wildlife moves, maps can be incomplete, and a blue route is not a guarantee that an animal remains at a location.

Children

The pilot does not create child accounts, child movement histories or child-targeted advertising profiles. An adult may later add family details for park administration only through a separately designed, minimised and protected workflow. Those identity-document features are not active in this pilot.

Retention and safeguards

Pilot records persist in the shared database so that testing does not reset; users can delete installation-owned records through the app. Beta-trial and official-waiting-list contact details are retained for their separate purposes while each programme is active or until you ask us to remove them. Before public launch, the operator must approve and automate a purpose-specific retention schedule. Current safeguards include private media storage, role-checked Control Centre APIs, same-origin mutation checks, rate limits, audit records and redaction of protected public locations. No internet service can promise absolute security.