Last updated: September 4, 2026
This page explains how to request deletion of data associated with Jeffrey Stop website services, the Jeffrey Stop Facebook automation app, and the Jeffrey Stop LinkedIn automation app.
Facebook App Data
The Jeffrey Stop Facebook automation app is used to publish JeffreyStop.com news links to the Jeffrey Stop Facebook Page. The automation posts site-owned news content. It does not provide Facebook Login for public users, and it is not designed to collect or store Facebook app-user profile data.
Operational records may include non-personal Page automation information, such as public Page post IDs, article links, workflow status, and redacted token validation status. Credential secrets are stored only in private local or GitHub secret stores and are not published.
LinkedIn App Data
The Jeffrey Stop LinkedIn automation app is used to publish JeffreyStop.com news links to the Jeffrey Stop LinkedIn Page through the LinkedIn Community Management API. The automation posts site-owned news content. It does not provide LinkedIn sign-in for public users, and it is not designed to collect or store LinkedIn member profile data.
The app authenticates only as the Jeffrey Stop Page administrator. LinkedIn API responses are processed in memory while the publishing workflow runs and are not cached, committed to our repository, or retained in published site data.
Operational records may include non-personal Page automation information, such as public LinkedIn post IDs, article links, workflow status, and redacted token validation status. Credential secrets, including OAuth access and refresh tokens, are stored only in private local or GitHub secret stores and are not published.
Request Deletion
To request deletion, contact us through the contact page or email support@jeffreystop.com with:
- Your name and contact email.
- A short description of the data you want deleted.
- Any relevant Facebook user ID, app-scoped user ID, LinkedIn member or organization URN, Facebook or LinkedIn Page post URL, or request reference, if you have one.
Do not send access tokens, passwords, or other secret values.
What Happens Next
We will review the request, search the documented local and operational storage locations for matching retained records, and delete or redact matching records where it is safe to do so. Credential secrets are not edited automatically through the deletion process; if a request indicates a credential exposure issue, those credentials are rotated or removed through the relevant secret-management system.
If no matching retained Facebook or LinkedIn app-user data exists, we will respond with a confirmation that no matching retained data was found.
Confirmation
Deletion request reviews produce a confirmation code and status report for tracking. The confirmation code is not a password and should not be treated as a secret.