> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/manage-private-feed-access/protect-listener-data-and-private-urls.md).

# Protect listener data and private URLs

Handle private-feed identities, credentials, URLs, and support diagnostics with minimum exposure.

Listener email addresses, usernames, private feed URLs, passwords, and access tokens require careful handling.

## Minimum access

* Grant listener scopes only to clients that need private-feed administration.
* Filter listener lists by podcast.
* Revoke unused agent connections and personal access tokens.
* Prefer deactivation to deletion when temporary access removal is enough.

## Secret handling

* Treat a complete private feed URL like a password.
* Do not paste it into chat, logs, tickets, screenshots, or documentation.
* Do not ask an agent to repeat or transform an access token.
* Use invitations and password resets instead of sharing credentials manually.
* Never include passwords in a preview, audit note, or support message.

## Support-safe diagnostics

Share the podcast ID, listener ID, status, expiry, operation ID, and non-secret error code. Mask personal data that Support does not need. Do not share the private URL or token.

## Revocation

Deactivate the listener to stop access reversibly. Revoke the connected agent grant when the client itself should no longer manage listener data.

## Related tasks

* [Review and revoke connected clients](/documentation/start-here/ai-agents/connect-and-authorize/review-and-revoke-connected-clients.md)
* [Activate, deactivate, or delete a listener](/documentation/start-here/ai-agents/manage-private-feed-access/activate-deactivate-or-delete-a-listener.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/manage-private-feed-access/protect-listener-data-and-private-urls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.