Skip to main content

DotSuite · DotShare

DotShare Privacy Policy

Last updated: November 13, 2026 (DotShare 3.8.1, dotshare-cli 3.2.1)

DotShare is an open-source developer tool from DotSuite. It turns your commits, release notes and code into posts and publishes them to the social accounts you connect. This policy covers the DotShare VS Code extension, the dotshare-cli package (its CLI and local MCP server for AI agents), DotShare sign-in on dotsuite.dev, and DotSuite cloud scheduling when you use it with DotShare.

DotShare is local-first. Your credentials, drafts and history stay on your device, and posts go from your device straight to each platform, unless you choose to schedule them in DotSuite's cloud. Your DotSuite account, billing and the dotsuite.dev website itself are covered by the general DotSuite privacy policy.

At a glance

DataWhere it is keptWho receives it
Platform credentials (tokens, app passwords, bot tokens, webhooks, API keys)On your device: VS Code SecretStorage (extension) or your OS keyring (CLI)Only the platform it belongs to, when you publish or check it. DotSuite gets a copy only if you schedule in the cloud and agree first.
AI provider API keysVS Code SecretStorage on your deviceOnly the AI provider you choose
Drafts, post history and receiptsOn your device. CLI and MCP records are encrypted (AES-256-GCM).No one, until you publish
Repository context for AI draftsNot stored by DotShareThe AI provider you choose, with your own key, when you ask for a draft
Sign-in tokens from LinkedIn and XPassed to your editor or CLI. dotsuite.dev keeps them only when you connect an account for cloud scheduling.Your editor or CLI, and DotSuite for cloud scheduling
X posts through DotShare's X appDotSuite: the X token (encrypted) and a record of each post's cost, without the post textX, published by DotSuite and charged to your plan's X budget
Scheduled posts and their imagesDotSuite servers (only if you schedule in the cloud)DotSuite's scheduler, which publishes them to the platforms you chose

What we never do

  • Sell, rent or share your data for advertising. DotShare shows no ads and contains no ad trackers.
  • Collect telemetry or analytics from the extension, the CLI or the MCP server. DotShare's own code sends none.
  • Send anything from your repository anywhere, except what you choose to include in an AI draft (to your AI provider) or a Gist (to GitHub).
  • Post on its own. Every post goes out because you, or an AI agent following your instructions, asked DotShare to publish or schedule it. The skill and tool guidance that ships with DotShare tell agents to show you a preview and wait for your approval.
  • Use content or data from LinkedIn, X or any other platform to profile you, or for any purpose other than publishing your posts and showing their results.
  • Train AI models on your content. When you use an AI provider, its own terms decide what happens to what you send.

1. What stays on your device

VS Code extension. Credentials are kept in VS Code SecretStorage, which uses your operating system's credential store. That covers LinkedIn and X tokens (including the X refresh token and expiry), the Telegram bot token and chat ID, the Discord webhook URL, the Bluesky handle and app password, the Mastodon instance and access token, the Dev.to API key, your AI provider API keys and your DotSuite key. VS Code's extension storage on your device holds your settings and history: recent posts, the last post, drafts for GitHub Gists, your chosen AI model and language, your call-to-action links, and your consent choices.

CLI and MCP server (dotshare-cli). Everything lives in ~/.dotshare, or the folder set in DOTSHARE_HOME, with private file permissions. accounts.json lists only each account's ID, name and platform. Credentials are kept in your OS keyring. Drafts, custom templates and the publishing journal are encrypted with AES-256-GCM, using a master key kept in your OS keyring. The journal stores request fingerprints, status and receipts (post IDs and links), not credentials or full post text. The MCP server reads images only from the folders you allow during setup (DOTSHARE_MEDIA_ROOTS).

Neither the extension nor the CLI keeps a plaintext copy of your credentials. Error messages are scrubbed of known secrets before they are shown or logged.

2. Publishing to social platforms

When you publish, preview or check an account, DotShare sends the post text, images or videos, and the matching credential directly from your device to that platform's API. DotSuite servers are not in that path. Each platform's own privacy policy then applies to what you post.

PlatformSent from your device to
LinkedInapi.linkedin.com (posts, media uploads, first comments, your basic profile to post as you)
Xapi.x.com (posts, media uploads, your username for account checks)
Blueskybsky.social (sign-in with your app password, posts, images, handle lookups for @mentions)
MastodonYour own instance (posts, media, the instance's character and media limits)
Telegramapi.telegram.org with your bot token
DiscordYour webhook URL on discord.com
Dev.todev.to with your API key

Post statistics. If you, or an agent you use, ask for a post's statistics, DotShare reads public engagement counts (likes, reposts, replies, quotes, impressions or views) for posts it published, from the same platforms. For Bluesky it uses Bluesky's public API without signing in. Nothing is stored except what is shown to you.

3. AI drafting (optional)

When you ask DotShare to write a draft, it sends a prompt directly from your device to the AI provider you selected (Google Gemini, OpenAI, Anthropic Claude, DeepSeek or xAI Grok), using your own API key. Depending on what you choose, the prompt can include commit messages, changelog and README excerpts, project metadata, parts of code changes from the repository you picked, and your own instructions. It does not pass through DotSuite. That provider's terms decide how your prompt is processed and retained, so leave out anything you don't want shared with it.

AI agents connected to the MCP server (such as Codex, Claude Code or Cursor) are separate products. What you tell them, and what they read through DotShare's tools, is governed by their providers' policies. DotShare never gives an agent your credentials. Agents work with account IDs and names instead.

4. GitHub Gists and CodeSnap

Creating a Gist uses your GitHub sign-in in VS Code (the gist permission) and sends the selected code to GitHub as a public or secret gist, as you choose. A secret gist is still viewable by anyone who has its link. CodeSnap screenshots are drawn inside VS Code and saved on your device. They leave it only if you attach one to a post. If you embed a live CodeSnap image of a gist (a dotsuite.dev/api/codesnap/gist/… link), dotsuite.dev reads that gist from GitHub's public API whenever the image is requested, at most once every 10 minutes, and draws it. Nothing is stored except the cached image.

5. Signing in to LinkedIn and X through dotsuite.dev

LinkedIn and X sign-in needs a server that holds DotShare's app credentials. DotShare uses dotsuite.dev/api/connect for this. DotShare 3.6 and earlier use dotshare-auth-server.vercel.app, which also passes tokens straight to your editor without storing them. During a sign-in on dotsuite.dev:

  • Your browser stores a signed, HttpOnly cookie for up to 10 minutes. It holds the sign-in's random security values (state and PKCE verifier), the platform, which editor or CLI to return to and, for dashboard sign-ins, your DotSuite user ID. It is deleted when the sign-in finishes, whether or not it succeeds.
  • LinkedIn or X sends a one-time code back to dotsuite.dev, and the server exchanges it for tokens. DotShare's app secret never reaches your browser.
  • Editor sign-in: the tokens are put in the result page, which opens your editor (vscode://, cursor:// and other known editors only), and the extension stores them in SecretStorage. The server doesn't keep them.
  • CLI sign-in (dotshare-agent accounts connect): the tokens are encrypted to a one-time key that exists only in the waiting CLI process and are sent to it on 127.0.0.1. They never appear readable in a URL, and the server doesn't keep them.
  • Dashboard sign-in (Connect in your DotSuite dashboard): the tokens are stored for cloud scheduling as described in section 6, but only if the same signed-in DotSuite user started and finished the sign-in.
  • X token refresh: X access tokens last about two hours. To renew one, the extension or CLI sends its refresh token to dotsuite.dev/api/connect/refresh/x and receives a new pair. Neither is stored.
  • X from DotShare 3.8: X tokens are saved to your DotSuite account as described in section 7 and never sent to your device, however you sign in.
  • Your IP address is used to rate-limit sign-in and refresh attempts. Errors are logged without tokens.
  • Sign-in pages load no analytics or third-party scripts.
Permission requestedWhy
LinkedIn openid, profileIdentify your member ID so posts are published as you
LinkedIn w_member_socialCreate posts, upload media and add the first comment you write
X tweet.read, users.readRead your username for account checks, and your own posts' metrics when you ask
X tweet.write, media.writePublish posts and threads, and upload images and videos
X offline.accessGet a refresh token, so you don't need to sign in again every two hours

The extension also asks dotsuite.dev which sign-ins are currently available, so it can disable unavailable buttons. That request contains no personal data.

6. DotSuite cloud scheduling (optional)

Cloud scheduling publishes posts at a set time, even while your computer is off. It needs a DotSuite account, and it's the only part of DotShare that stores your content and credentials on DotSuite servers. If you never schedule in the cloud or connect accounts in the dashboard, none of this applies to you.

  • Credentials. You add them in one of two ways. Connect LinkedIn or X in the dashboard (section 5). Or, from the extension, agree to the consent prompt shown before your first cloud schedule; Mastodon asks separately. The extension then sends the stored credentials of the platforms you schedule to (Telegram, LinkedIn, X, Bluesky, Mastodon or Dev.to). The server encrypts them with AES-256-GCM before storing them and uses them only to publish the posts you schedule.
  • Scheduled posts. The post text, chosen platforms, image URLs, time and status, plus retry count and the last error if publishing fails. Posts stay in your history after they publish.
  • Images. Images you schedule are uploaded to DotSuite storage on Cloudflare R2, recorded with your account, and served from a public, unguessable URL so the platforms can fetch them. Anyone with that URL can view the image. An image you upload but don't attach to a scheduled post is deleted after 24 hours. An image attached to a scheduled post is kept until the post is published, fails or is cancelled, then deleted 7 days later. You can only schedule your own uploads.
  • Device identifier. Requests from the extension and CLI include a one-way SHA-256 hash of a device identifier (VS Code's machine ID, or your computer's hostname and OS username for the CLI). It's used for device limits and abuse prevention and can't be reversed into the original value.
  • Activity records. Posting activity is used for rate limits and abuse prevention and deleted after 7 days. Security audit logs are deleted after 90 days.
  • Infrastructure. The DotSuite API runs at core.dotsuite.dev on Railway with a PostgreSQL database. Images are stored on Cloudflare R2. Payments for paid plans are handled by Lemon Squeezy, and DotSuite never receives your card details.

7. X posts and your X budget

X charges DotSuite for every post made through DotShare's X app: at X's current prices, $0.015 per post and $0.20 for a post with a link. To keep that fair and predictable, X posts made through DotShare's app are published by DotSuite and counted against a monthly X budget included in your plan. Scheduled X posts already work this way, and from DotShare 3.8 so do X posts you publish right away.

  • Your X connection. Once X posting goes through DotSuite, signing in to X saves the connection to your DotSuite account. The X tokens are encrypted on DotSuite's servers and never sent to your device; your editor and the CLI only learn that X is connected.
  • What is recorded for each X post: when it was posted, whether it counted as a post with a link, how many images it had, the price-table estimate, the amount X actually deducted when that could be measured, what you were charged, its status and its X post ID. These records contain no post text. Your recent charges and remaining budget are shown in the DotSuite dashboard.
  • How each charge is calculated. Before a post is sent, DotSuite holds the most X could charge for it from your monthly X budget, using X's published prices; anything that might be a link is held at the link price. DotSuite publishes X posts one at a time and reads its own X credit balance before and after each post. The post stays pending until X's deduction shows up. You're then charged exactly what X deducted, and the rest of the hold returns to your budget, like a card payment. If X's deduction can't be confirmed, the held amount is charged. Nothing is added after a post has settled. That balance belongs to DotSuite's X account and contains no information about you.
  • Limits. Each plan has a monthly X budget that resets on the 1st (UTC) and a daily limit on X posts per user, and DotSuite applies an overall daily limit to protect the service. A post that would go over a limit is refused before anything is sent.
  • If something goes wrong. A post X rejects isn't charged, apart from images X had already accepted. If X doesn't answer, the post is charged and never resent automatically, because X may have published it.
  • Retention. X budget records are kept while your DotSuite account exists and are deleted with it.
  • Your own X app instead. You can use an access token from your own X developer app with the DotShare CLI (dotshare-agent accounts add). Posts then go from your device to X, X bills your own developer account, and DotSuite isn't involved.

8. Your choices, and how to delete your data

  • Remove credentials from the extension. Use Clear all credentials at the bottom of DotShare's Settings, or run DotShare: Clear All Credentials from the Command Palette (DotShare 3.7.0 and later). Either way, you confirm first. It deletes every platform token and key, your AI provider keys, the GitHub token, your DotSuite key and your cloud-sync consent from this device. You can also disconnect LinkedIn, X or GitHub one at a time in Settings, or sign out of DotSuite with DotShare: Logout / Clear Token.
  • Remove CLI accounts: dotshare-agent accounts remove <id> deletes the account and its keyring entry. Your local library stays in ~/.dotshare until you delete that folder.
  • Revoke access at the platform. Removing a credential locally doesn't revoke it. Revoke it where it was issued: LinkedIn (Settings → Data privacy → Permitted services), X (Settings → Security and account access → Apps and sessions), Mastodon (Preferences → Account → Authorized apps), Bluesky (Settings → App passwords), Telegram (@BotFather → revoke token), Discord (delete the webhook) and Dev.to (Settings → Extensions → API keys).
  • Cancel scheduled posts from the extension, or with cancel_scheduled_post / dotshare-agent cloud cancel.
  • Disconnect a platform from DotSuite. In your DotSuite dashboard, under DotShare → Connected Accounts, select Disconnect on any connected platform. Its stored credential is deleted immediately.
  • Delete everything. Deleting your DotSuite account (Dashboard → Settings → Delete account) first deletes all your connected platform credentials, scheduled posts and their images, API keys and licence data, then the account itself. If any of that fails, the account is kept so you can try again. Billing, refund and security-audit records are kept for their legal and security retention periods. Every image you uploaded is deleted with it, attached or not.
  • Access or correction. Ask at the same address what DotSuite stores about your DotShare use, or ask us to correct it.

9. Security

  • Every connection to platforms, AI providers and DotSuite uses HTTPS. Credential requests are refused if TLS verification has been disabled.
  • Credentials are encrypted at rest: by your OS on your device, and with AES-256-GCM on DotSuite servers.
  • Sign-in only returns tokens to known editor schemes or to the encrypted CLI hand-off, and every sign-in is protected by a one-time state value and PKCE (X).
  • The CLI's encrypted library refuses to open with a missing or wrong key, so a copied folder alone doesn't expose your drafts.
  • DotShare is open source. You can review exactly what it sends at github.com/kareem2099/DotShare. Report security issues as described in its SECURITY.md.

10. Changes and contact

When DotShare's data handling changes, we update this page and the date at the top, and note the change in DotShare's CHANGELOG. For questions, requests or concerns, email support@dotsuite.dev.