SocialClaw legal

Privacy Policy

SocialClaw is a social media scheduling and publishing service. Customers use SocialClaw to sign in, connect social accounts, upload media, schedule content, and publish to supported platforms. This policy explains what data SocialClaw accesses, how that data is used, how it is protected, and how users can request deletion.

When SocialClaw accesses sign-in and connected account data

SocialClaw accesses account data when a user signs in, connects a supported social account, uploads content, or asks SocialClaw to publish or reconcile content on their behalf. Supported providers may include Google / YouTube, Facebook, Instagram, TikTok, LinkedIn, X, Pinterest, Reddit, WordPress, Telegram, Discord, and other providers offered in the product.

Data from sign-in and connected social accounts

• Sign-in data: account identifiers, verified email address where provided, display name, and profile image used to create and authenticate a SocialClaw user and workspace membership.
• Connected account data: provider account identifiers, usernames, page or channel identifiers, granted permissions or scopes, access tokens, refresh tokens, token expiry data, and account metadata required to keep a connection active and perform requested publishing actions.
• User-submitted publishing data: media files, titles, captions, descriptions, links, scheduling data, and other content metadata a customer asks SocialClaw to upload, schedule, or publish.

Google and YouTube specific disclosures

• Google Sign-In data: verified email address, Google account subject identifier, display name, and profile image used to create and authenticate a SocialClaw dashboard user.
• YouTube account data: YouTube channel identifier, channel title, channel custom URL if available, granted OAuth scopes, access token, refresh token, and token expiry information required to keep the connected channel active.
• User-submitted YouTube publishing data: video files, titles, descriptions, and other publishing metadata a customer asks SocialClaw to upload or publish to YouTube.

Other data SocialClaw stores

• workspace metadata and API keys used to identify and secure a customer workspace
• connected account records for supported providers, including provider account identifiers and credentials required for publishing
• scheduled posts, campaign definitions, publish attempts, provider post identifiers, and analytics snapshots where available
• uploaded media metadata and, when configured, the media objects stored in private object storage
• operational logs related to job execution, token refresh attempts, connection health, abuse prevention, and customer support
• website and product usage analytics, including pageview and interaction data collected through analytics tools such as Google Analytics

How SocialClaw uses sign-in and connected account data

• to authenticate a user into the SocialClaw dashboard and associate that user with a workspace
• to connect a customer’s selected social accounts to SocialClaw at the customer’s direction
• to upload, schedule, publish, and reconcile content the customer explicitly asks SocialClaw to send to connected platforms
• to refresh tokens, maintain connections, and show publishing or delivery status inside the product
• to secure the service, investigate failures or abuse, and respond to customer support requests

How SocialClaw uses other data

• to authenticate workspace requests and enforce billing, security, and usage limits
• to complete provider OAuth flows and maintain connected accounts
• to publish posts, reconcile publish status, and surface analytics
• to host user-uploaded media and render the dashboard, API, and CLI experiences

Sharing of connected account data and other personal data

SocialClaw sends data to the social platforms a customer explicitly connects in order to authenticate, publish content, refresh tokens, or retrieve publish status. SocialClaw also uses infrastructure providers for hosting, database, backups, object storage, and analytics in order to operate the service. SocialClaw does not sell connected account data, Google user data, or other personal data to advertisers, data brokers, or information resellers, and does not use Google user data for advertising.

Connected account data, including Google and YouTube data, is only shared when necessary to provide the user-facing service the customer requested, to protect the security of the service, or when required by law.

Data storage and protection

SocialClaw stores data on backend systems and cloud infrastructure used to operate the service. Data is transmitted over HTTPS. Access to production systems and stored data is restricted to authorized personnel and service processes that need it to operate, secure, or support SocialClaw. Workspace API keys are encrypted at rest. Connected account credentials, including OAuth tokens, refresh tokens, and other connection metadata for supported providers, are stored on backend systems with access controls so SocialClaw can maintain authorized connections and publish content on the customer’s behalf.

Data retention and deletion

Sign-in profile data is retained while the associated SocialClaw user account and workspace remain active. Connected account data, including tokens and account metadata for supported providers, is retained until the user disconnects the account, revokes access, requests deletion, or the workspace is removed, subject to legal retention obligations. Scheduled posts, publish attempts, and operational records may be retained for security, fraud prevention, accounting, dispute resolution, and service integrity.

Users can request deletion or disconnect connected data by using the SocialClaw dashboard where available, visiting https://getsocialclaw.com/legal/data-deletion, or contacting hello@getsocialclaw.com. If a user cannot access the dashboard, they can email a deletion request with enough information to identify the workspace or connected account.

SocialClaw aims to respond to verified deletion requests without undue delay and normally within one month of receiving the request or completing identity verification where needed. If a request is unusually complex or subject to legal retention obligations, SocialClaw may require additional time and will communicate that to the requester.

Your controls

• disconnect connected accounts from the SocialClaw dashboard or API
• revoke and replace workspace API keys in the dashboard
• request provider-connected data deletion through the data deletion page or through supported provider deauthorization callbacks
• contact hello@getsocialclaw.com for manual privacy or deletion requests

Questions

For privacy questions or requests, contact hello@getsocialclaw.com.