Disconnect an account. Choose what to delete.

Stop publishing through a connection

1. Sign into Rollset and select the client workspace where the account was connected.
2. Open Settings → Integrations → Social.
3. Find the account and choose Disconnect. For YouTube, use the combined revocation and deletion control described below.

Rollset removes the stored credential and stops future publishing through that connection. Review affected scheduled posts before reconnecting. If a request had already reached the platform when access was removed, check the platform for its result before creating another copy. For native Facebook or Instagram connections, disconnect also erases the mirrored message conversations, message copies, replies, notes and conversation attachment references for that connection. It removes provider identifiers imported from that connection where they have not since changed, while retaining the CRM contact and independent contact information. Ordinary disconnect retains other connected social profile, post history and measurements for reconnection. It does not delete planner drafts or reusable uploaded media files, and does not itself revoke the grant held by the provider. The inbox cleanup runs asynchronously in the active database; it does not delete messages from Meta or make a separate backup-erasure promise.

X connections are not available in the current release. If your workspace has a legacy X authorization or subscription record from earlier setup, contact Rollset support for help checking its status. Charges from a customer-owned X developer app are managed with X.

Revoke YouTube access and delete its data

In Settings → Integrations → Social, find the YouTube connection and choose Revoke access and delete data. Review the affected access and type REVOKE to confirm. Google may share the grant with other YouTube channels or Rollset Google Business Profile connections, so revoking it can also stop those connections. The related YouTube channels may be connected in other Rollset workspaces. Their imported data is removed as part of this request; stored Business Profile data is not deleted by this YouTube control.

Rollset blocks local access and starts deleting the related provider data. Where it has a usable credential and verified Google grant identity, it also asks Google to revoke access. For an older connection without those requirements, no server revocation is attempted; remove access yourself in Google's third-party permissions settings. Rollset does not report manual removal as confirmed automatically.

• Completed revocation: Google confirmed revocation. Local data cleanup may still be running; this result alone does not mean every local record has been removed.
• Pending revocation: Google has not yet confirmed the request. Rollset retries within a 24-hour retry window; a pending result is not a confirmation that provider access is revoked.
• Manual action required: use Google's permissions settings to remove access. This applies when the grant cannot be verified or automatic revocation cannot be confirmed. Local access remains stopped and local deletion can proceed independently.

Videos and comments already on YouTube remain there. Use YouTube's own controls to delete them. Drafts and original media you supplied to Rollset can remain for your other destinations. Removing access through Google's settings is also supported; Rollset checks authorization periodically and removes associated provider data when invalid authorization is detected.

Remove the provider's authorization

You can also remove Rollset from the connected-app or business-integration settings of the social provider. For Google Business Profile or YouTube, open Google's third-party permissions settings. A shared Google grant may support more than one Rollset connection, so check the access shown by Google before removing it.

For Facebook and Instagram, review Facebook's Apps and Websites or Business Integrations settings. Threads, LinkedIn and TikTok provide their own app-authorization controls. For LinkedIn, TikTok, legacy X and Google Business Profile, the ordinary Rollset disconnect/data-deletion action is local; remove the app's grant at the provider as well if you want that authorization revoked. Provider-side removal does not by itself confirm that stored Rollset records have been deleted.

Facebook, Instagram and Threads requests

When Meta or Threads sends a valid signed deauthorization request, Rollset stops the affected connections and removes their stored publishing credentials. A signed data-deletion request starts the scoped data cleanup described below. These requests can affect destinations authorized by the same provider user and app across multiple Rollset workspaces. They are not necessarily limited to the one Page or profile you most recently viewed in Rollset.

For a provider deletion request, keep the confirmation code and status link supplied through the provider's flow. If removing a provider app did not give you a deletion confirmation, use Rollset's available deletion control or contact us to confirm what data you want removed. Review affected schedules before making a fresh connection.

Delete stored social-provider data

In Settings → Integrations → Social, choose Delete account data when available and review its confirmation. This removes the connected profile, credentials, authorization association and related provider-derived jobs, publishing results, comments/replies and measurements. For native Facebook and Instagram connections it also erases mirrored message conversations, message bodies and IDs, operator replies and internal notes, attachment references, previews, conversation notifications and activities, and related imported provider identifiers. Message cleanup is processed in bounded asynchronous batches. The CRM contact itself, other independently maintained contact information, reusable file-library uploads, authored planner drafts and media remain. For YouTube, use Revoke access and delete data instead of this separate control.

Content you wrote or uploaded in Rollset is separate from data retrieved from a provider and may be used by other destinations. Planner drafts and original uploads remain separate from this connection cleanup. Removing a post does not necessarily remove its uploaded files. Existing media URLs may remain retrievable while those files are stored; manage the files separately or include them in a broader request. Already-published posts and comments remain on the social network; delete those using the network's controls.

Limited request records can remain to track deletion and prevent an old provider request from affecting a new connection. These include status, timestamps, confirmation references and hashed authorization/request references. Pseudonymous Meta webhook replay-prevention records contain hashed event values rather than message bodies or raw provider IDs and are removed by scheduled cleanup after 90 days. If legacy X billing references exist, they can remain as needed for billing, cancellation or legal records. Deletion does not cancel a subscription or close your whole Rollset workspace.

If a control is unavailable during rollout, you cannot sign in, or you need a broader request, email nick@rollset.app with the subject Delete my Rollset social data. Include your Rollset account email, workspace name, platform and whether you want to delete one connection's data or the wider workspace/account. Do not send passwords, tokens or app secrets. We may need to verify your identity and authority before processing the request.

You can also write to Rollset LLC, 4539 N 22nd St, Ste N, Phoenix, AZ 85016, United States. Tell us if your request includes original uploads, drafts, the entire workspace or your wider CRM account, rather than only data imported from one social provider.

Check a deletion request

Meta and Threads provider-deletion callbacks can return a Rollset confirmation code and status link. Open that link to check whether that request is in progress or complete. The receipt does not display the connected identity. An ordinary in-app or emailed request does not necessarily have this public receipt. For an emailed request or a problem with a receipt, contact nick@rollset.app with the request reference. Do not send the original signed provider request.

A completed receipt means the records covered by that request have been processed in Rollset's active database. It does not confirm that posts were removed from the social network, a legacy X subscription was canceled, your whole CRM account was erased, or every backup and third-party copy was deleted. Contact us if the request scope or status does not match what you intended.

This page gives instructions; it is not the provider's automated deletion callback. For details about data use, see Social privacy, the general Privacy Policy, the Google Privacy Policy and the YouTube Terms of Service where applicable.