Log inGet Started

Privacy Policy

Last updated: November 5, 2026

SelfScale is a product of SelfScale Inc ("we," "our," or "us"), a Delaware corporation. This policy explains what we collect when you use SelfScale, how we use it and how to have it deleted. By using SelfScale you agree to it.

1. Information We Collect

1a. Information you provide

Your email address, name and profile picture from the sign-in you use (Google or LinkedIn); the voice profile data, writing samples, drafts, posts and media you create or upload in SelfScale; and anything you send to support.

1b. Information from connected social media accounts

If you connect a third-party account on the Integrations page, we collect the following information from it. Every connection is optional and yours to remove.

  • LinkedIn: Name, email address, profile photo, access token and the posts published through SelfScale with their engagement data.
  • YouTube (Google): Channel name and ID, your videos and their analytics, comments on your own videos (the comment text, when it was posted, its like and reply counts, and the commenter's public name, username, profile picture, channel link and channel ID), access token and videos uploaded through SelfScale.
  • Skool: Your communities and their post categories, posts published through SelfScale and the Skool email and password you type in, because Skool has no sign-in API. Your password and the session Skool issues are held encrypted in Google Cloud Secret Manager and never shown back to you. At sign-in your email and password pass through Scrapfly, a cloud browser service, to reach Skool; later checks and automatic re-sign-ins run through Browserless.
  • X (Twitter): Username, display name, profile photo, access token and posts published through SelfScale.
  • Instagram and Facebook (Meta): Instagram username, name, profile picture, follower and media counts, the Facebook Pages you manage, access token and media published through SelfScale. You can also connect a Creator or Business Instagram account directly through Instagram sign-in; for that connection we store the account ID, username and account type, an encrypted access token, your own posts (links, captions, thumbnails and like and comment counts), a daily follower count and the identifiers of posts published through SelfScale. Post insights are read live and are not stored. Disconnecting deletes this data, except the captions your voice profile learned from, which stay with your voice profile until you delete them or ask us to delete your data. If the same workspace also has Instagram connected through Facebook, the daily follower counts are kept.
  • TikTok: Display name, avatar, account identifier, access token and videos published through SelfScale. If you grant TikTok's two optional permissions (your account statistics and the list of your own videos), we read your follower, following, likes and video counts once a day and store the follower count as a daily history. We also store your own public videos (links, captions, cover images, publish dates and view, like, comment and share counts). Disconnecting deletes them.
  • Threads (Meta): Username, profile, access token and posts published through SelfScale.
  • GitHub: Public profile (login, name, avatar) and access token. If you also connect a personal access token, we store it encrypted and use it only on our server to read your profile and follower count, list your own repositories (names, descriptions, stars, forks) and read the README of each repository you choose to import. We record your follower count over time; imported README text and derived knowledge are stored as Sources until you remove them. The token can read only what you grant it on GitHub. Disconnecting deletes the token and the recorded follower counts.
  • Notion: The pages and databases you grant, access token, workspace name and ID and a record of items sent. Pages you import are stored, with derived knowledge, as Sources until you remove them there; disconnecting Notion does not remove them. Import suggestions and the daily import are described below.
  • Fireflies: Your Fireflies API key, stored encrypted (AES-256-GCM) with the Fireflies account name and email it belongs to. We use it only on our server, with your own key, to list your meetings (titles, dates, durations, participants) and to read the transcripts of the meetings you import or that a routine uses. By default we keep only your own lines; other speakers are dropped unless you switch an import to reference mode, which keeps every speaker's lines with their names, as reference only. Imported lines are stored as Sources, with derived knowledge, until you remove them. If you ask us to scan the past year, we keep that list (titles, dates, durations and Fireflies' own summary) with the meetings you tick. The Fireflies to Posts routine reads up to five meetings you organized per run, keeps only your own lines, removes other people's names, emails, phone numbers, money amounts, figures and percentages and drops lines that sound confidential, and sends what is left to our model providers to write one draft for you to approve. The assistant tool that lists your meetings returns titles and dates only, never transcript text. Disconnecting deletes the key and your import settings; imported meetings stay in Sources unless you tick the box to remove them when you disconnect.
  • Canva: Your designs, so you can attach one to a post, plus access token and display name.

We publish to a platform only when you press publish or set a schedule, and never post, like, follow, message or change settings on your behalf otherwise. If you delete or edit a post on X, SelfScale does not yet receive that change automatically; the data we stored for it is removed when you disconnect X or ask us. Fathom, Wispr Flow, Substack, Google Calendar, Slack, Telegram, Kit, Ghost, Readwise appear on the Integrations page as coming soon. None is generally available yet, and apart from the early-access integrations below, SelfScale collects nothing from any of them today.

Some integrations are turned on for a small number of accounts before general release. If one is on for your account and you connect it, we collect:

  • Kit: Your Kit API key, stored encrypted (AES-256-GCM). We use it only on our server to read your account name, subscriber count and recent newsletter stats, and the text of the newsletters you import as your own writing. Disconnecting deletes the key.
  • Ghost: Your Ghost site URL and read-only Content API key, stored encrypted (AES-256-GCM), and the author name you say is you. We use the key only on our server to list your published posts (titles, dates, authors) and import the ones you choose. Disconnecting deletes the key.
  • Readwise: Your Readwise access token, stored encrypted (AES-256-GCM). We use it only on our server to list the books and articles in your library (titles, authors, highlight counts) and import the highlights and notes of the ones you choose, as reference unless you mark them as your own words. Disconnecting deletes the token.
  • Substack: The public web address of your own Substack publication (its RSS feed). There is no key or login: we read only that public feed, on our server, to turn your new posts into social drafts you approve. Posts for paid subscribers appear in the feed as previews, so only the preview text is read. Disconnecting deletes the stored address.
  • Wispr Flow: When you connect Wispr Flow, you sign in on Wispr Flow's own page and approve read-only access. Wispr Flow gives us access and refresh tokens, which we store encrypted and use only on our server, to list your Wispr Flow Notetaker meetings (title, date and a short summary) so you can choose which to import, and to read the transcripts of the meetings you choose. Wispr Flow does not share your dictation history with connected apps, and we do not ask for it. A meeting transcript can include other people's words, so imported meetings are kept as reference material: they inform your topics but are not used to train your voice profile. Imported meetings are stored as Sources, with derived knowledge, until you remove them; to build that knowledge their text is processed by our model providers, as described in sections 2 and 3. Disconnecting deletes the tokens; imported meetings stay in Sources until you remove them.
  • Google Calendar: The secret iCal address of the one calendar you choose (you copy it from Google Calendar settings), stored encrypted (AES-256-GCM), and that calendar's name. We use it only on our server, when you open your Calendar, to read the next two weeks of events and show their titles, places and times to you; we do not read event descriptions, do not store your events, and never change your calendar. An event's title is sent to our AI providers only when you choose that event to make a post. Disconnecting deletes the address; you can also cut access at any time by resetting the secret address in Google Calendar.
  • Slack: The Slack bot token Slack gives us when you connect, stored encrypted (AES-256-GCM), your Slack workspace name and identifier, and the one channel you pick. We use the token only on our server to list your channels so you can pick one, and to post the private notifications you turned on (drafts ready to approve, a routine finished) to that channel. We never read your Slack messages. Disconnecting deletes the token.
  • Telegram: When you connect Telegram alerts, we store the numeric ID of your private chat with the SelfScale bot, your Telegram username if you have one, and when you connected. We use them only to send you SelfScale alerts in that chat, such as a routine finishing or drafts waiting for your approval. An alert names the routine, says how many drafts are waiting and links back to SelfScale; Telegram delivers and keeps those messages under its own privacy policy. We do not read your other Telegram chats or contacts, and we do not post anywhere on Telegram. If you block the bot we stop sending; disconnecting on the Integrations page deletes the stored chat ID and username.

Import suggestions and daily import. When you connect Fireflies, Kit, Ghost, Notion or Readwise, we suggest your items from the last 30 days (for Fireflies, meetings you organized), with every item pre-checked. Only the items you leave checked are imported. The same screen offers a daily import of new items, switched on by default where it is available; you can turn it off before importing, or turn it off at any time later. Imported text and derived knowledge are stored as Sources until you remove them.

1c. Google Account Data

When you connect your Google account we request:

  • YouTube: read access to your channel data and analytics, and the ability to upload videos on your behalf

SelfScale uses YouTube API Services. By connecting your YouTube account you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is governed by the Google Privacy Policy. SelfScale’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. To revoke SelfScale’s access, go to the Google security settings page.

Public YouTube information. When you search a topic or add a channel as inspiration, SelfScale uses YouTube API Services to read public information about YouTube channels and videos, whether or not you have connected a YouTube account: channel names, IDs, pictures and subscriber counts, and video titles, descriptions, thumbnails, publish dates and view, like and comment counts.

1d. Information collected automatically

Browser type, pages and features used, access times and error logs. We use essential cookies for sign-in and sessions, and four services that collect information on your device so the product keeps working: Vercel Analytics and Vercel Speed Insights (traffic and performance), PostHog (product usage events) and Sentry (error reporting). With your permission, given in our cookie banner, we also use analytics and advertising cookies: Google Analytics through Google Tag Manager to measure visits, Meta and TikTok pixels to measure and improve our ads on those platforms and Rewardful to credit referral partners. They stay off until you accept, and you can change your choice at any time in Cookie Settings. No third party serves advertising in the product.

2. How We Use Your Information

To run SelfScale, generate content in your voice, publish to your connected accounts when you ask, show you how published content performed, process payments, send service updates, answer support requests and improve the product. Content generation is performed by model providers such as Anthropic and OpenAI under their own privacy policies; they do not retain your data for training. We do not use data obtained from any connected platform to develop, improve or train generalised AI or machine-learning models.

3. How We Share Your Information

We do not sell your personal information. We share it with the platforms you connect, limited to the content you ask us to publish and the requests needed to read back its performance; with the service providers that host, store, process payments or generate content for us (Vercel, Supabase, Stripe, Anthropic, OpenAI) and services that help us read publicly available social media data; when required by law or to protect our rights; in a merger, acquisition or sale of assets; and otherwise only with your consent. The full list of companies that receive member data, what each receives and where, is on our Subprocessors and Third-Party Services page.

4. Security

Data is encrypted in transit and at rest. Supabase provides database and authentication and Vercel provides hosting; both are SOC 2 compliant. Access tokens for connected accounts are encrypted at rest and used only for actions you request.

5. Your Rights and Data Deletion

You can access, correct, export or delete your data at any time by emailing support@selfscale.app. Disconnecting a platform from its card on the Integrations page deletes the data we stored from that platform immediately. Step-by-step instructions for every platform are on our Data Deletion Instructions page. You can also withdraw SelfScale’s permission on the platform's side, in its connected-apps or security settings.

6. Data Retention

We keep your data while your account is active and delete your personal data within 30 days of account deletion, except where law requires us to keep it. When you disconnect Skool, your Skool password and session are deleted immediately. Posts you created in SelfScale stay until you delete them or your account. Deleting what SelfScale stored does not affect anything on the platform itself.

YouTube: if you disconnect YouTube or ask us to delete it, we delete that data within 7 calendar days at the latest, and in practice immediately. We keep YouTube data no longer than 30 days without refreshing it from YouTube. Both follow the YouTube API Services Developer Policies. Deleting the YouTube data SelfScale has stored does not, in any way, affect data stored by YouTube; videos you published remain on your YouTube channel.

7. Children, Transfers and Changes

SelfScale is not for anyone under 18, and we delete any such data we discover. Your data may be processed in countries other than your own, with appropriate safeguards. We will post any material change to this policy here and update the date above.

8. Contact Us

SelfScale Inc · support@selfscale.app · https://selfscale.app