Delete your Pulse data

1. Delete one monitored post

1. Sign in to Pulse.
2. Open the monitored post.
3. Choose the option to stop monitoring or delete the post and confirm.

This deletes the post metadata stored in Pulse, its comments and replies, sentiment and spam results, reconciliation state and related alert records. It does not delete the original post or comments from Facebook or Instagram.

2. Disconnect inside Pulse

1. Sign in to Pulse and open the platform connection.
2. Choose Disconnect and confirm.

Pulse tries to unsubscribe from comment webhooks and revoke the granted permissions, removes the stored access token and active connection record, and stops collecting new data.

Disconnecting does not delete existing monitoring history. Posts, comments, sentiment results and alerts remain available so the operator can review or delete them later. To erase them, delete each monitored post, remove Pulse through Meta as described below, or send a verified deletion request.

3. Remove Pulse through Meta

1. Open the relevant Facebook or Instagram settings for apps, websites or business integrations.
2. Find Pulse and choose Remove or revoke its access.

When Meta sends Pulse a valid signed deauthorization request, Pulse automatically deletes the matching access token, connection, monitored posts, comments, derived sentiment data, alerts and stored webhook content.

If Meta instead sends its signed User Data Deletion Request, Pulse performs the same deletion and returns a confirmation code and status URL to Meta. A retry of the same signed request returns the original result and cannot delete data collected after a later reconnection.

4. Request deletion by email

Email dpo@massimilianopetrucci.it with the subject “Pulse data deletion request”.

Include only enough information to find the data:

• Connected-account operator: the email used to sign in to Pulse and the Facebook Page or Instagram username concerned.
• Comment author: your Facebook or Instagram username, the post permalink if available, and the approximate comment date or text. Do not include information that is not needed.
• Parent or guardian: identify the relevant comment and explain the relationship needed to handle the request.

Additional information may be requested when reasonably necessary to verify identity and avoid deleting another person’s data. Pulse will respond without undue delay and normally within one month. If the lawful response period must be extended because of complexity or request volume, notice and reasons will be provided within the first month.

5. Choose the scope of an email request

• Specific comment or post: delete only the identified content and Pulse’s derived results.
• All Meta-derived account history: delete connected-account details, monitored posts, comments, sentiment results, alerts and stored webhook content associated with the verified account.
• Full Pulse login account: also delete the Google identity link, email, TOTP factor, passkeys, recovery codes and active sessions. Security-event records are removed or minimized unless temporary retention is necessary for a legal or security reason.

6. What may remain temporarily

After content deletion, Pulse may retain only limited records needed to prove completion and prevent destructive callback replay:

• a deletion-request record containing platform, subject identifier, status and timestamps for up to 90 days;
• content-free cryptographic webhook tombstones for up to 90 days; and
• a content-free hash receipt for a signed Meta callback for up to 180 days.

These records are not used for monitoring, analytics or advertising. They are removed after the stated security periods unless a longer period is required by law or for a legal claim.

7. Questions or complaints

You may also complain to the Italian Data Protection Authority or another competent supervisory authority. See the Privacy Policy for the complete description of processing and rights.