Choose one feature.

Before offering a reporter a demonstration, choose one feature and identify the permissions it requests in the current product. For example, a fictional calendar tool might ask a user to authorize access to a calendar before it can display availability. Use the actual feature and permissions in your own product.

Explain the request in plain language.

Write two or three sentences that identify what the feature requests, why that access is needed and when the user is asked to grant it. Distinguish what the permission technically allows from the narrower actions the product actually takes. Do not imply the product can access less than the permission permits.

Verify the details.

Ask the product and security or privacy team to check the wording against the current version, the authorization screen and the relevant product documentation. Explain any differences between platforms, plans or configurations. Do not promise that data is never stored, shared or retained unless the claim has been verified for the feature.

Show what a user can control.

Where applicable, explain what happens if someone declines or revokes access and where they can make that choice. Verify the steps before sharing them, including any limitations that remain after access is revoked. Use a demonstration account and avoid exposing real customer information.

Include the context with the demo.

In your note to a reporter, briefly describe the feature and offer the permission explanation alongside a demonstration. Provide current documentation or an appropriate technical contact for follow-up. Clear context helps the reporter evaluate the product; the publication decides what to cover.