AMMO Morning Report Reporting — privacy and data controls
AMMO Morning Report Reporting — privacy and data controls
This notice describes AMMO's Google reporting connection and the protected HQ reports it supports. It is separate from the AMMO storefront's shopping and checkout privacy notice.
Information accessed and its purpose
With an authorized owner's consent, we read Google Analytics property settings and aggregate sessions, engaged sessions, purchase counts and purchase revenue by date and default channel. We also use YouTube API Services to verify the authorized AMMO NYC channel and retrieve daily views and period totals. We use these reports for AMMO's internal performance review, source validation and historical comparisons.
The connection uses read-only reporting permissions. It does not collect Google passwords, private messages, individual viewer identities or Google Drive documents. OAuth credentials are stored separately from reports and are not included in the HQ data files.
Storage, access and processing
Aggregate reports and dated validation records are stored in restricted operational files and the protected AMMO HQ. Access is limited to the authorizing owner and AMMO-approved operators. Cloudflare provides HQ hosting. Approved operators may use Codex-assisted tools to process selected aggregates for AMMO reports and troubleshooting; credentials are excluded from those report exchanges.
The app uses Google data to provide these reporting features. It does not sell that data or send it to advertising platforms to target individuals. HQ uses its existing sign-in/session controls. The informational pages do not initiate an OAuth connection; consent occurs through Google's own authorization screen.
Retention and deletion
We retain dated aggregate reports and validation records while they are needed for the authorized reporting purpose and the owner's authorization remains valid. The present reporting adapters do not automatically expire historical files. Owners can request removal of their stored data using the support contact below.
For a verified YouTube-data deletion request, AMMO will remove the affected stored data as soon as possible and within seven calendar days. If authorization is revoked, affected YouTube API data will be removed within thirty calendar days. These requirements include copies retained for validation and recovery; stopping collection alone is not deletion. Deleting AMMO's stored reports does not delete data held by Google or YouTube.
Your controls and contact
You can revoke the connection in Google Account permissions. To request deletion or ask about the reporting app's data handling, contact larry@ammonyc.com. We may verify your authority over the affected source without asking for your password or token.
Google's services are covered by the Google Privacy Policy. This app uses YouTube API Services; see the YouTube Terms of Service.