BirdWatch integration privacy

Updated 8 September 2026. This page supplements the BirdWatch Privacy Policy for our catalogue connection to AI assistants.

What the connection receives

Your AI provider sends the arguments needed for the tool you use, such as destination, bird IDs, travel dates, budget or a tour ID. BirdWatch processes those arguments to return public catalogue information. The connection does not require your full conversation, email address or BirdWatch account. Avoid entering sensitive information into search fields.

What is returned

Only published tour information, public organizer or guide details, target species, and BirdWatch page and image links are available. The tools do not expose private inquiries, customer records, account passwords, internal notes or unpublished listings.

Operational information

The integration records aggregate daily request counts, HTTP status groups and total processing time for up to seven days. Abuse-prevention counters use a daily changing keyed hash of the server-observed network address and are reset by the next request in a new minute. They do not store the raw address or tool arguments. Hosting infrastructure may separately process IP addresses and technical logs as explained in the main Privacy Policy.

The public catalogue connection does not create browser cookies or retain conversation sessions. Existing private OAuth pilot connections additionally use consent cookies and hashed, expiring authorization tokens. Those connections can be revoked.

Your AI provider

ChatGPT or Claude receives the tool results and handles your conversations according to its own policies and your account settings. BirdWatch does not control that processing.

Questions and requests

BirdWatch is operated by Webtribe, Belgrade, Serbia, as identified in the main Privacy Policy. Contact privacy@birdwatch.info or support@birdwatch.info for privacy questions, corrections or requests.