Your social accounts and your data.

Who operates the service

Rollset LLC, an Arizona limited liability company, operates Rollset CRM. Copperline CRM is the product's former name. Native social management is part of the CRM at rollset.app. This notice applies when you use an available native social connection. See current availability and our general Privacy Policy for account information, security and privacy rights.

Our principal and mailing address is 4539 N 22nd St, Ste N, Phoenix, AZ 85016, United States. Privacy questions and requests can be sent to nick@rollset.app.

Information used by a connection

• Connected identity: provider account, channel, Page or business-location identifiers; names, usernames and profile images where supplied; and the authorization information needed to associate the grant with its destinations.
• Authorization: permissions, encrypted access and refresh tokens, expiration and connection status.
• Your content: captions, original media, titles, covers, selected destinations, schedules, drafts, publishing choices and processing results.
• Provider records: identifiers and links for published posts, processing results and failures, available performance counts, and follower or subscriber measurements where supplied.
• Comments and replies: comment or reply identifiers, author names, usernames or actor identifiers, text and timestamps returned by the provider. These post discussions are requested when available for a published post.
• Facebook and Instagram messages, where enabled: message text and IDs; sender, recipient, Page or Instagram account identifiers; conversation identifiers, short message previews and inbox state such as assignment or unread status; timestamps and delivery/read status where supplied; and inbound attachment type and provider URL references. Rollset stores the references, not downloaded bytes for inbound attachments. Replies and internal notes written in Rollset are also stored. If a workspace member attaches a library file to a CRM conversation, Rollset stores its file name, type, size and storage reference. A matching or newly created CRM contact may hold provider identifiers associated with that conversation. To prevent duplicate webhook processing, Rollset also keeps pseudonymous replay-prevention records made from hashed event values; scheduled cleanup removes these records after 90 days.
• Billing and requests: applicable checkout references, entitlement status, support requests and limited records needed to track deletion. Payment-card details are handled by the payment provider.

The exact information depends on the platform, account type and permissions you grant. Rollset does not ask you to send us your social-account password. Authorization happens with the provider.

What each platform shares with Rollset

Facebook and Instagram

Facebook supplies managed Page identifiers, names and Page credentials for the Pages you authorize. Instagram uses a linked professional account's identifier, username, profile image and parent Page association. A private association with the authorizing Meta user supports connection and deletion handling. Rollset sends selected captions, media and publishing choices, and retrieves available post results, insights and supported comments. When the separate messaging feature is enabled and the required permissions are granted, new Page or eligible Instagram professional account messages, message text, identifiers, attachment references and delivery/read updates are mirrored into the CRM inbox. Authorized workspace members can reply or add internal notes. This connection manages Pages and eligible professional Instagram accounts; it does not publish to a personal Facebook profile.

Threads

Threads supplies your profile identifier, username and profile image. Rollset sends the text or media you choose, reads supported post insights and replies, and sends replies you write. Available insights can include views, likes, replies, reposts and quotes. The native integration does not provide a follower history or a full moderation inbox.

LinkedIn

Rollset receives your member identifier, name and profile image through authorized sign-in. Organization identifiers are available only with the applicable approved organization access. Rollset sends selected posts and supported comments or replies, and reads the post response and available likes/comment counts. Company management, discussion reads and analytics depend on LinkedIn's access approval; member sign-in alone does not enable them all.

TikTok

Rollset receives a creator identifier, display name, avatar and available follower count. Before posting a video it checks the creator's permitted visibility, duration and interaction settings. Your original video, caption, cover-frame choice, privacy choices, interactions and selected commercial-content or AI labels are sent to TikTok. Rollset can retrieve the published video's available views, likes, comments and shares as counts. The native preview does not read or reply to TikTok comment text.

X

X is not available for new account connections, publishing or analytics in the current release. If a workspace has records from earlier setup or testing, Rollset handles them only as needed for security, account cleanup, support or applicable billing obligations; see the deletion instructions.

Google Business Profile and YouTube are described below. For every platform, access is limited by the permissions granted, the account's eligibility and the features enabled in the workspace.

How we use and share it

We use connected data to show the accounts you authorized, publish the content you choose at your requested time, maintain connections where refresh is supported, show available performance and let authorized workspace users read or respond to supported post discussions and, when enabled, Facebook or Instagram messages. We use connection and processing status to explain failures and support recovery. We do not sell connected social data or use it for advertising.

Your content, selected settings and media are sent to the destinations you choose. Connected information is available to authorized members of the relevant Rollset workspace and to service providers as necessary to host, secure and operate Rollset, as explained in our general Privacy Policy. We do not make one customer's private connection available to another customer.

Infrastructure used for native social includes Vercel for the web application and Convex for backend processing, database records, media storage and scheduled work. Stripe processes payment information for paid services when applicable. X billing is not offered in the current release. Other CRM features can involve additional providers described in the general Privacy Policy.

A workspace administrator may also connect an external AI agent to Rollset through the authenticated MCP or REST interface. Examples of agent clients include ChatGPT, Codex, Claude, Hermes and Grok; these are third-party products and are not operated by Rollset. Before granting social access, the administrator identifies the agent and the AI service provider, chooses the social permissions, and expressly authorizes the requested data sharing. When that agent calls a tool, the response may contain only the data allowed by its grants—for example, connected account labels, authored posts, available metrics, supported comments or Facebook/Instagram messages. The customer-selected agent provider may process or retain those responses under its own terms and privacy practices; its identity and processing locations depend on the provider the customer chooses. Rollset does not receive that provider's account credentials. Connecting a social account alone does not send its data to an AI provider.

The hosted MCP endpoint runs through Vercel, which processes requests and tool responses when that endpoint is used. A direct REST connection or an MCP client that connects directly to the API can avoid that hosted MCP relay. Revoke an agent's access by deactivating its API key in Rollset. Data already returned to an external agent is outside Rollset's control and must be managed under that provider's terms and deletion controls.

Best-time suggestions on supported platforms use measured engagement from your historical posts. They do not track individual followers' activity or report when every follower is online. YouTube data is excluded from these derived recommendations and combined platform totals.

Media hosting, cookies and third-party content

Original media and covers uploaded to the social composer are stored through Rollset's file storage. Publishing may send file bytes or a retrievable media URL to a selected network; Instagram and Threads can fetch the selected media from such a URL. These URLs are not authenticated file-sharing links. Someone who obtains a URL may be able to fetch the file while it remains stored, including before the scheduled post is published.

Disconnecting a social account or deleting its imported provider data does not itself delete the original upload or invalidate every media URL. Uploaded files can be used by multiple posts or destinations. Manage those files separately in Rollset, or include them in a broader deletion request.

Rollset uses session cookies for sign-in and browser storage for workspace, navigation and interface preferences. Where configured, PostHog uses cookies and local storage for dashboard usage analytics, and Sentry processes technical diagnostics and masked error-session replay. These services can receive account or workspace identifiers and technical information. See the general Privacy Policy for details and browser-storage choices.

Your browser may load profile images, previews or embedded content from third-party servers. Those requests disclose network and request information to that party, and content you open on the social network follows its own privacy and cookie practices.

Google Business Profile and YouTube

Business Profile access lets Rollset identify accounts and locations you manage and create or check updates, offers and events you request. Rollset stores the location and post identifiers, selected content and publishing results needed for that workflow. YouTube features use YouTube API Services to identify your channel, upload your videos and supported thumbnails, set the audience and visibility you choose, retrieve available channel/video statistics, and handle supported comments or replies. These connections do not themselves grant access to your Gmail, Calendar or Drive.

A Google account identifier associates the authorization with its connected destinations and supports shared-grant revocation. For YouTube, Rollset also records the local user, time and policy version associated with the connection's consent. Native YouTube uploads use original media supplied by the customer, not downloaded copies of YouTube videos.

Rollset's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. The Google Privacy Policy explains Google's practices. YouTube features are subject to the YouTube Terms of Service.

The YouTube account control Revoke access and delete data stops local access and starts removal of stored YouTube provider data. Where Rollset can verify the Google grant, it also requests revocation from Google. A pending result means the Google request needs another attempt; it does not mean Google has confirmed revocation. You can also revoke authorization through Google's third-party permissions settings. Revoking a Google grant may affect other Rollset connections that use the same Google application. The YouTube control removes imported data for YouTube channels linked to that Google grant, including those connected in other Rollset workspaces. It does not itself delete stored Business Profile data. Follow the controls and request-status guidance in our deletion help.

YouTube statistics are displayed as individual channel and video counts with their measurement time. They are not used for Rollset engagement scores, best-time recommendations or combined platform totals. Stored YouTube provider data is refreshed or removed when it can no longer be verified. Original content you supplied to Rollset is distinct from information retrieved from YouTube.

If a stored channel identity becomes stale and cannot be refreshed, Rollset stops publishing and asks you to reconnect. An encrypted credential may remain for explicit reconnection or revocation; it is not used to resume publishing automatically.

How long connection data stays

We keep active connection details and publishing records needed to provide the selected service. For platforms other than YouTube, disconnecting does not start a fixed automatic expiry period for all profile, history or measurement data. Use the separate data-deletion control or contact us to request removal. Original CRM content, uploads, billing records and limited security or request records have a separate purpose and removal process.

The YouTube preview has periodic authorization checks and a 28-day freshness limit for cached YouTube API data. Data is refreshed or scheduled for removal when it can no longer be verified. A confirmed invalid authorization starts provider-data cleanup. If a channel identity cannot be verified within that limit, its cached identity and measurements are removed, publishing stops and reconnection is required. An encrypted credential may remain solely to support explicit revocation or reconnection.

Deletion is processed in batches. A limited receipt can retain request identifiers, hashed authorization/request references, timestamps and status to track the request and prevent an old provider request from being applied to a new connection. Receipt completion describes the scoped cleanup in Rollset's active database; it does not certify removal from every backup or from the social network.

Disconnecting and deleting data

Disconnecting a native social account removes its stored publishing credential and stops future work through that connection. Provider authorization can also be removed in the provider's own settings. Disconnecting and deleting stored data are distinct actions; ordinary disconnect retains profile information, history, measurements and the private authorization association. A request already sent to a provider may have taken effect before disconnection. YouTube uses the combined revocation and data-deletion control described above instead of a local-only disconnect.

A request to delete a connection's stored provider data removes its connected profile, credentials, authorization association and associated provider-derived publishing records, existing mirrored discussions and measurements. It stops affected queued publishing. Content you wrote or uploaded in Rollset can be shared across destinations and is retained separately. Removing a post and removing its original uploaded files are separate operations; include both in a broader request where needed.

Meta and Threads can send signed deauthorization or deletion requests. These can cover destinations authorized by the same provider user and app across multiple Rollset workspaces. An ordinary in-app data-deletion request for another platform does not automatically revoke the provider's authorization. Use the provider's own settings as well. YouTube has the combined control and shared-grant behavior described above.

Neither action deletes posts that already exist on a social network. Those posts remain under the network's policies and your controls there. Account and billing records may also be retained as described in our general Privacy Policy. If a workspace has legacy X billing records, deleting social data does not itself cancel a related subscription; ask Rollset support to check its status. Follow the disconnect and deletion instructions or contact us for help with a specific request.

Contact and privacy requests

Email nick@rollset.app to ask about access, correction, export or deletion of your information. Include the workspace name and connected platform, but never passwords, OAuth tokens or client secrets. We may verify your identity and authority to act for the workspace. See the general Privacy Policy for your privacy rights.

You can also write to Rollset LLC, 4539 N 22nd St, Ste N, Phoenix, AZ 85016, United States. If a business or agency manages the workspace, tell us which organization is involved so the request can be directed appropriately. The available rights and any required response period depend on the law that applies to your request.