Privacy
StackSignal · not affiliated with Substack, LinkedIn, Instagram, Facebook, X or YouTube · Last updated 17 November 2026
Who is responsible
A Roll Media (FZE), United Arab Emirates, is the controller of your personal data for StackSignal. Contact: support@stacksignal.app.
The short version
- We collect only what StackSignal needs to run your dashboard.
- AI help is your choice: nothing is sent to the AI service until you allow it, and you can switch it off any time in Settings under AI help. The detail is under Your writing style profile.
- Your private numbers are shown only to you. We never sell your data, show ads, build advertising profiles or use your data to train AI models.
- You can delete your account and all your data yourself, any time, in Settings → Account → Delete my account and data. See Data deletion.
What we collect
- Account: your email address, sign-in times, the days you open the app (just the dates, never what you looked at; it helps us see which members need a hand and improve the app), how long each section of the app is open on your screen (just the section name and a number of seconds per day, never what you typed, posted or looked at, and nothing from other sites; it helps us see which parts members use and who might like a hand), and, only if you opt in, your choice to receive our free newsletter. If you sign in with Google, Google tells us only your verified email address and an account ID that links your Google sign-in to your StackSignal account. We don't receive your name, photo, contacts or Gmail. If you first arrived from a tagged link (for example one ending ?ref=newsletter), we keep that tag with your account so we know which links work. We also keep whether you get the weekly Growth Brief and rival alerts, and which ones were sent. If you rate an AI answer (👍 / 👎), we keep the rating and the reason you picked, never your question or the answer. If you were given a personal invite or guest code, we keep that code with the email it was issued to (removed if you delete your account).
- Billing: your plan and its status. For website plans that is your Stripe customer and subscription status; card details go straight to Stripe and never touch our servers. For plans bought in the iPhone, iPad or Android app, Apple or Google handles payment and we receive only your subscription status, plan, renewal dates and an anonymous purchase ID, through our purchase-management provider RevenueCat. We never see your Apple Account, Google account or payment details.
- Handles you add: your Substack, LinkedIn, Instagram, Facebook, X and YouTube handles and up to 5, 15 or 40 competitor handles per platform, depending on your plan.
- Public data: public profile counts, posts, Notes and engagement for those handles. We fetch it from public pages, in part through a specialist public-data collection provider. For competitors this is public counts and public posts only. We keep a tracked account's data only while at least one member is tracking it: once no one tracks it we stop refreshing it and remove it in a regular clean-up. If you are tracked and want out sooner, see Data deletion.
- Stats you enter or upload: numbers you choose to add from your own stats (revenue, views, open rate, new subscribers, podcast plays) and any screenshot of your own stats page you attach, which is kept private to you.
- Accounts you connect (only if and when you choose to): if you connect an account through the platform's own sign-in screen, we receive a secure access token and read only the data you approved on that screen. See “Accounts you connect” below.
- Chrome connections: if you connect the StackSignal extension in Chrome, a one-way fingerprint of the connection key (never the key itself), a random number the browser made for itself (so connecting again from the same browser replaces the old connection), the name of the browser (such as “Chrome on Mac”), and when it was connected, last used and, if you ended it, revoked. While you connect, StackSignal also keeps a one-way fingerprint of a one-time connect code (never the code itself) and when it was made and used, so that the code can work only once. See “StackSignal for Chrome” below.
- Subscriber CSV (optional): if you upload your Substack subscriber export, your browser reads it on your device. Raw email addresses never reach us (this Snapshot upload only). We keep totals, monthly join counts, the display names of your top 30 most engaged readers and of up to 50 recent joiners, each with their paid status and activity stars (or a masked email like “q•••@gmail.com” when there's no name), and a fingerprint of each email scrambled with a key unique to your account so your next upload can count who left. We keep only your two latest uploads, and you can remove them any time in Settings. If you connect an AI assistant to your account, it can read only the totals from your latest upload (how many readers, how many paid, joins by month); it can never read names, masked emails or the scrambled fingerprints. You decide whether to upload; you're responsible for having your readers' data lawfully.
- Audience hub (optional): if you import a subscriber list into the Audience hub and tick the box to agree, we keep that list in your account: names, email addresses and activity (such as opens and paid status), plus the tags, stars, VIP marks and groups you add. It is private to you, used only to help you tag and group your own audience, and never sold or shared. You can delete all of it any time in Settings, and it is removed when you delete your account. You're responsible for having your readers' data lawfully.
- If you import or link your Substack subscriber list, we keep every column of it (such as names, emails, activity, location and plan) in your account only, never use it to email anyone or train AI, never keep card or bank details, and delete it whenever you ask.
- Goals and settings: your weekly goals and whether you hit them, your time zone and your display choices.
- Post ideas and drafts: the daily ideas on your Content tab, and any draft you open from one, with your edits and whether you marked it as posted. Kept until you delete the draft or your account.
- Scheduled posts (only if you use scheduling): the text and picture or video link you ask us to post, the time you picked, whether it went out, and the link to the live post. You can cancel a scheduled post any time before it goes.
- Security logs: the IP address and browser details of each sign-in session, for sign-in protection; short-lived counters for rate limiting (the counter for an IP address or email is deleted within 48 hours); and, only when automated-access monitoring is on, a record of each automated-access check (no page content). See “How long we keep it” and “Security” below.
- Page views: aggregate, cookieless page-view counts through Vercel Web Analytics. No advertising identifiers, no cross-site tracking and nothing that identifies you personally.
Your writing style profile (Alixc). AI help is your choice: nothing is sent to the AI service until you allow it, and you can switch it off any time in Settings under AI help. Alixc learns your writing style from your own public posts and from the edits you make to its drafts, and keeps a style profile so drafts sound like you. Only you can see it. When Alixc writes, that profile and a few of your recent posts go to the AI service, and about once a week some of your recent posts are read to refresh it. You can see it, reset it, clear your edits or switch AI help off any time in Settings. Your style is never learned from your messages, chats, other members or the people you track. Here is the detail.
- What it learns from: your own public posts and Notes on the accounts you connect (Substack, LinkedIn, X, Instagram, Facebook and YouTube: the last 90 days on Substack and 180 days on the others), and how you change Alixc's drafts before you post them. The first version of each draft Alixc writes is kept so it can be compared with what you posted. It also counts whether you kept, edited or turned away a draft (with the reason you pick from a fixed list, if you pick one) and any thumbs up or down you give. Posts that seem to name another person are left out of the weekly read.
- What is stored: in your account, a short style profile (counted habits such as length, openers, sign-offs, emoji, punctuation, humour, topics and phrases you come back to, and a few of your best posts as examples); the short phrases you often cut or add when you edit, and counts of drafts kept, edited and turned away; the first version of each draft; your thumbs; and anything you type into “Your voice” in Settings. Only you can see it. Our team does not read it, and it is not available to assistants you connect.
- What goes to the AI service: when Alixc writes a draft, a title or a reply with your style, the AI service receives this profile, a few of your own recent posts as examples, your weekly goal if you set one, and the idea or message it is writing about. About once a week it is also sent up to 24 of your own recent posts (each cut to 500 characters) to describe things counting cannot, such as how you open a story and how you land a point. What comes back is a short description of your style, which is stored in the profile. The same style summary, without your posts, is used when you press “Alixc, write this” on a welcome message. Nothing is used to train the AI.
- What is never used for it: your direct messages, chats and comments from other people, your readers, other StackSignal members' writing, the posts of the people you track, and your email address, password or private revenue. The “Draft a reply” features below send only what each one lists.
- How often it refreshes: it is rebuilt from your latest posts whenever a draft feature runs or you press “Update from my latest Notes”, your edits are counted the moment you mark a draft as posted, and the weekly read happens about once every seven days. The weekly read, and anything sent to the AI service, happen only while AI help is on.
- How long it is kept: the profile is replaced each time it is rebuilt, from the posts of the last 90 days (Substack) or 180 days (other platforms). Edit habits are counted from your last 120 days of edits. The first versions of drafts, your counts and your thumbs stay until you delete the draft or your account, or clear the first versions and edit habits with “Forget my edits”. Everything here is deleted when you delete your account.
- Your controls, in Settings: “What Alixc learned about your voice” shows what it has learned and lets you add your own Always and Never lines. “Update from my latest Notes” refreshes it. “Reset” clears your own changes and the stored profile and relearns it from your posts (your thumbs and drafts stay). “Forget my edits” deletes the edit habits and the saved first versions. Switching AI help off stops anything being sent to the AI service straight away; the saved profile stays in your account, out of reach of the AI, until you delete your account. If you want it deleted sooner without closing your account, email support@stacksignal.app and we will remove it. We use it only to word drafts for you, never to judge you or decide anything about your account.
Accounts you connect
Connecting Instagram or LinkedIn and scheduled posting are available on the StackSignal website only, not in the iPhone or Android apps. The Instagram and Facebook message and comment Inbox is on the website only too.
StackSignal may let you connect your own Instagram, LinkedIn or Stripe account (for YouTube numbers no connection is needed: we read your public channel from its handle) so your numbers update by themselves. This is always your choice, and you approve exactly what is shared on the platform's own screen before anything reaches us.
- Instagram (Business or Creator accounts): your username, account ID and account type; once a day, your follower count, how many accounts you follow and how many posts you have; and, for your latest 25 posts, the caption, post type, link, date and the number of likes and comments, so your dashboard updates by itself. These numbers join your own Instagram handle's history in your dashboard, beside the public numbers we already show you. If you use scheduling, also the ability to publish the posts you confirm. We do not read the text of comments, your contacts, your reach or audience information, or anything you didn't approve. Message and comment access is a separate, optional permission for the Inbox described below: StackSignal asks for it only when the Inbox is switched on for you, and only reads messages and comments while you use the Inbox.
- Facebook Page (only if you connect one): the name and ID of the one Page you choose on Facebook's own screen, and, if you use scheduling, the ability to publish the posts you confirm to that Page. The Page's access is stored in encrypted form. We do not read your personal Facebook profile, your friends or anything you didn't approve.
- Threads (only if you connect one): your Threads username and account ID, from Threads' own screen, so we know which account is connected; and the ability to publish the text posts you confirm to that account. The account's access is stored in encrypted form and renewed in the background. We do not read your followers, your replies, your messages or anything you didn't approve.
- LinkedIn: your name and LinkedIn member ID, from LinkedIn's own sign-in screen, so we know which account is connected; and, if you use scheduling, the ability to publish the posts you confirm. Once LinkedIn approves StackSignal for post analytics, also the impressions, reactions, comments and shares of your own posts and your follower figures, as LinkedIn provides them.
- YouTube (public channel data only): the channel handle you give us, then the public subscriber count, total views, video count and recent public videos (titles, thumbnails, views, likes and comments counts). We use Google's YouTube API Services for this and do not need you to sign in to YouTube for it, so we cannot see private analytics, revenue or anything unlisted. Use of YouTube data is also subject to the YouTube Terms of Service and the Google Privacy Policy.
- YouTube uploads (only if you choose “Connect YouTube”; not available to members yet): a separate step from “Continue with Google”, approved on Google's own screen. Google then lets StackSignal upload the videos you confirm to your channel (the YouTube upload permission) read your channel's name and whether it is verified (read-only YouTube access), and read your own channel's YouTube Analytics reports (read-only) so a video's stats window can show its views by day, watch time, likes, comments, subscribers gained, where viewers came from and its thumbnail click rate. For that click rate we ask YouTube to prepare its daily reach report for your channel. These numbers are fetched fresh each time you open the window and are not stored by StackSignal. We keep your channel ID and name, and Google's access for your account, stored in encrypted form. For each upload we keep its title, who can see it, the time it goes public and the video ID once it is up. Your video goes straight from your browser to Google: it never passes through or is stored on StackSignal's servers. A thumbnail you pick is passed to YouTube once and not kept. We never upload, change or delete anything you didn't confirm, and we don't read your comments' text or your revenue. You can disconnect at any time in StackSignal or in your Google Account (Security → Third-party apps with account access), and deleting your account removes all of it. Use of YouTube data is subject to the YouTube Terms of Service and the Google Privacy Policy; StackSignal's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
- Stripe (read-only): revenue totals and paid-subscription counts from the Stripe account that receives your Substack payments. We cannot move money, refund, or change anything in your Stripe account.
Posting for you (only if you choose to). If StackSignal offers scheduling and you connect LinkedIn or Instagram for it, you approve a separate permission to post on the platform's own screen. We then publish only the exact text (and picture or video link) you wrote, at the time you picked, and only after you confirm that post. Nothing is ever posted that you haven't confirmed, and AI never changes a post you wrote yourself. You can withdraw the permission at any time, in the same places as above. Connecting Instagram or LinkedIn and scheduled posting are available on the StackSignal website only, not in the iPhone or Android apps. The Instagram and Facebook message and comment Inbox is on the website only too.
Buffer (only if you choose to). If you already use Buffer, you can connect your Buffer account so StackSignal can send posts to the channels you have set up there. You approve this on Buffer's own screen. We store the access Buffer gives us in encrypted form, read the list of your Buffer channels and the status of the posts we sent, and pass Buffer only the exact text (and picture or video link) of a post you confirmed, plus the channel and time you chose. Buffer then handles that post under its own terms and privacy policy. We never post to Buffer without your confirmation, we don't read anything else in your Buffer account, and you can disconnect Buffer at any time in Settings. Buffer is available on the StackSignal website only, not in the iPhone or Android apps.
Message and comment inbox (Instagram and Facebook). StackSignal's Inbox lets you read and answer your Instagram and Facebook Page messages and comments in one place. It is rolling out to members once Meta approves the permissions it needs; until it is switched on for your account, StackSignal does not ask you for message or comment access. It is always your choice: you approve the extra message and comment permissions on Meta's own screen when you connect.
- What it shows: your own Instagram direct messages and the comments on your own Instagram posts, and your own Facebook Page's Messenger conversations and the comments on your Page's own posts. They are read from Meta with your own connected account's access when you open the Inbox, and shown only to you.
- What we store: the messages and comments themselves are not stored by StackSignal. Meta sends our server a notice each time a new message or comment arrives (Meta requires this): we keep only how many new items arrived and when, on your connection, so the Inbox can show a “new” count, never the words, the sender or any message ID. The profile picture of a person who messaged you is held in our server's memory for a few minutes and in your own browser, never in our database. For each reply or Page like you send we keep a short record with no words in it (Instagram or Facebook, a direct message, a comment or a like, when, and whether it went through), so we can apply your plan's daily reply limit, which is shared with Substack replies, and so nothing is ever sent twice. A picture or video you attach to a reply is kept in your own private storage so Meta can collect it, until you delete your account.
- Replies and likes happen only when you press the button: a reply goes only when you press Send, one reply per press, and a like as your Page only when you press Like. Direct-message replies go only into a conversation the other person started and only within Meta's 24-hour reply window (after that the Inbox says “Reply window closed” and nothing can be sent). Comment replies go only under comments on your own posts. StackSignal never starts a conversation, never replies by itself, and never sends bulk or promotional messages.
- “Draft a reply”: only if you tap it on one message or comment and you have agreed to AI help, the text of that one message or comment and the tone you chose are sent to our AI service to suggest a reply; so the reply is written as you, the AI is also told how you are named on your own accounts (your own name, handle and publication names, from your own StackSignal record). Never the sender's name, handle or picture, any ID or time, your other messages, or a voice note. The text and the suggested reply are not stored or logged, and are not used to train AI models. The suggestion is shown to you to edit; nothing is sent until you press Send.
- Message previews (only if switched on for your account): a separate, read-only Instagram preview keeps only the latest message of each conversation (kept and shown as a preview of up to 140 characters), who it is with and when it was sent, and deletes it 30 days after the message was sent. It is never sent to any AI service unless you tap “Draft a reply” on it, as above.
- Never used for advertising. Message and comment text is shown only to you and never used for advertising or profiling.
- Stopping it: disconnect in Settings, or remove StackSignal in Instagram's or Facebook's own settings. The stored access, the new-item counts and any message previews are deleted at once. Your reply records and attachments are deleted when you delete your account.
What we do with connected data: show it to you, and only you, in your dashboard and in the emails we send you. We don't sell it, share it with anyone else (apart from the AI service listed below, which only receives what each AI feature needs to write its answer, such as your daily tip or a chat message to Alixc), use it for advertising, use it to train AI or machine-learning models, or combine it with other people's data to identify anyone. Access tokens are stored encrypted and used only to fetch your data. You can disconnect at any time in Settings or in the platform's own settings (Instagram: Apps and websites; LinkedIn: Settings & Privacy → Data privacy → Permitted services; Stripe: your Dashboard's connected apps). Disconnecting stops all access straight away. We delete the stored access and the data we fetched through it within 30 days (for Instagram, LinkedIn and Buffer the access is deleted at once). The one exception is the Instagram numbers already added to your own handle's history: they are kept like the rest of that handle's public history (see “Public data” above) until you remove the handle or delete your account. Disconnecting removes the connection and cancels posts that were waiting; your post history stays in your account until you delete the account. If your plan ends and is not renewed, we disconnect any connected Instagram or LinkedIn account about three days later: the stored token is deleted and any post that was waiting is cancelled (your post history stays, as above).
Where a platform sets stricter limits on how long we may keep its data, we follow the stricter limit.
Instagram and Facebook permissions, one by one
When you connect Instagram or a Facebook Page, Meta's own screen shows the permissions StackSignal asks for. This is what each one is used for, how long we keep what it gives us, and how to delete it. We never use any of it for advertising, never sell it and never use it to train AI models.
instagram_business_basic(Instagram)- What we access: Your Instagram username, account ID and account type; your follower count, how many accounts you follow and how many posts you have; and, for your latest 25 posts, the caption, post type, link, date and like and comment counts. In the Inbox, the profile picture of a person who messaged you.
- Why: So your own Instagram numbers update by themselves in your dashboard, and so the Inbox can show who wrote to you.
- How long we keep it: Your account details while you stay connected. Your daily numbers join your own handle's history until you remove the handle or delete your account. A sender's profile picture is never stored: it is held in our server's memory for a few minutes and in your own browser.
- How to delete it: Disconnect Instagram in Settings (the stored access is deleted at once), remove StackSignal in Instagram's Settings → Apps and websites (Instagram tells us and we delete it automatically), or delete your account.
instagram_business_content_publish(Instagram)- What we access: The ability to publish to your Instagram account the posts you write and confirm.
- Why: So a post you scheduled goes out at the time you picked. Nothing is ever posted that you did not confirm.
- How long we keep it: For each post: its text, picture or video link, the time you picked, whether it went out and the link to the live post, until you delete it or your account.
- How to delete it: Disconnect Instagram in Settings (the stored access is deleted at once), remove StackSignal in Instagram's Settings → Apps and websites (Instagram tells us and we delete it automatically), or delete your account. Removing StackSignal in Instagram also deletes the posts you scheduled or published through StackSignal.
instagram_business_manage_messages(Instagram)- What we access: Your Instagram direct-message conversations, read from Instagram when you open the Inbox, and the ability to send one reply each time you press Send, only into a conversation the other person started and only within Meta's 24-hour reply window. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: So you can see and answer the people who message you, from one place.
- How long we keep it: Messages are shown to you and not stored. Instagram's notices of new messages leave only a count and a time on your connection. For each reply you send we keep a short record with no words in it (direct message or comment, when, and whether it went through) for your daily reply limit. A picture or video you attach to a reply is kept in your private storage until you delete your account. The separate read-only message preview, if switched on for you, keeps only the latest message of each conversation (up to 140 characters) and deletes it 30 days after it was sent.
- How to delete it: Disconnect Instagram in Settings (the stored access is deleted at once), remove StackSignal in Instagram's Settings → Apps and websites (Instagram tells us and we delete it automatically), or delete your account. Message previews and new-message counts go when you disconnect; reply records, attachments and everything else go when you delete your account.
instagram_business_manage_comments(Instagram)- What we access: The comments on your own Instagram posts, read when you open the Inbox, and the ability to post one public reply under a comment each time you press Send. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: So you can read and answer comments on your own posts.
- How long we keep it: Comments are shown to you and not stored. Only new-comment counts and a reply record with no words in it are kept, as above.
- How to delete it: Disconnect Instagram in Settings (the stored access is deleted at once), remove StackSignal in Instagram's Settings → Apps and websites (Instagram tells us and we delete it automatically), or delete your account.
pages_show_list(Facebook)- What we access: The list of Facebook Pages you manage, shown once so you can choose which one to connect.
- Why: So you connect the right Page.
- How long we keep it: Only the name and ID of the Page you choose. The list itself is held for at most 10 minutes, encrypted, in your own browser while you choose, and then discarded.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
pages_manage_posts(Facebook)- What we access: The ability to publish to your chosen Page the posts you write and confirm, and to remove a post StackSignal published when you ask it to.
- Why: So a post you scheduled goes out to your Page at the time you picked.
- How long we keep it: The same post record as for Instagram, until you delete it or your account. The Page's access is stored encrypted while you stay connected.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
pages_read_engagement(Facebook)- What we access: Your chosen Page's own details and its own recent posts with their basic engagement figures.
- Why: So StackSignal can confirm the Page you connected and list its posts, for example to show the comments under them in the Inbox.
- How long we keep it: Read when needed and not stored, apart from the Page's name and ID.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
pages_read_user_content(Facebook)- What we access: The comments people leave on your Page's own posts, with the name Facebook shows for each, read when you open the Inbox. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: So you can read comments on your Page's posts.
- How long we keep it: Shown to you and not stored. Only new-comment counts are kept on your connection.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
pages_manage_engagement(Facebook)- What we access: The ability to post one public reply as your Page under a comment on your Page's own post, each time you press Send. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: So you can answer comments on your Page.
- How long we keep it: A reply record with no words in it, for your daily reply limit, until you delete your account.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
pages_manage_metadata(Facebook)- What we access: Turning on Facebook's notices of new messages and comments for your chosen Page. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: Meta requires these notices for an inbox. We use them only to show how many new items are waiting.
- How long we keep it: Only how many new items arrived and when, on your connection. Never the words, the sender or any message ID.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account. The counts go when you disconnect.
pages_messaging(Facebook)- What we access: Your Page's Messenger conversations, read when you open the Inbox, and the ability to send one reply each time you press Send, only into a conversation the other person started and within Meta's 24-hour reply window. Part of the Instagram and Facebook Inbox, which is rolling out to members once Meta approves this permission; it is asked for only when the Inbox is switched on for you.
- Why: So you can answer people who message your Page.
- How long we keep it: Messages are shown to you and not stored. Only new-message counts and a reply record with no words in it are kept, as for Instagram. An attached picture or video is kept in your private storage until you delete your account.
- How to delete it: Disconnect Facebook in Settings (the stored access is deleted at once), remove StackSignal in Facebook's Settings → Apps and websites (or Business integrations), or delete your account.
Deleting through Meta: removing StackSignal in Instagram's settings, or asking Instagram to delete the data an app holds about you, sends StackSignal a signed request; we check it and delete your Instagram connection, its message previews and the Instagram posts you scheduled or published through StackSignal, and you get a reference you can check on our Data deletion page. For a Facebook Page, follow the Facebook Page steps on that page.
Threads permissions, one by one
When you connect Threads, Threads' own screen shows the permissions StackSignal asks for. This is what each one is used for, how long we keep what it gives us, and how to delete it. We never use any of it for advertising, never sell it and never use it to train AI models.
threads_basic(Threads)- What we access: Your Threads username and account ID.
- Why: So you can see which Threads account you connected. Every other Threads permission needs this one.
- How long we keep it: Your username, your account ID and an encrypted access key, while you stay connected. The key lasts 60 days at a time and StackSignal renews it for you in the background.
- How to delete it: Disconnect Threads in Settings (the stored access is deleted at once), remove StackSignal in your Threads settings (Threads tells us and we delete it automatically), or delete your account.
threads_content_publish(Threads)- What we access: The ability to publish to your Threads account the text posts you write and confirm.
- Why: So a post you scheduled goes out at the time you picked. Nothing is ever posted that you did not confirm.
- How long we keep it: For each post: its text, the time you picked, whether it went out and the link to the live post, until you delete it or your account.
- How to delete it: Disconnect Threads in Settings (the stored access is deleted at once), remove StackSignal in your Threads settings (Threads tells us and we delete it automatically), or delete your account. Removing StackSignal in Threads also deletes the posts you scheduled or published through StackSignal.
Deleting through Meta: removing StackSignal in your Threads settings, or asking Threads to delete the data an app holds about you, sends StackSignal a signed request; we check it and delete your Threads connection and the Threads posts you scheduled or published through StackSignal, and you get a reference you can check on our Data deletion page.
Instagram statistics permission
Where Instagram statistics are switched on for you, Instagram's own screen asks for one more permission. This is what it is used for. We never use it for advertising, never sell it and never use it to train AI models.
instagram_business_manage_insights(Instagram)- What we access: The totals for your own Instagram account over the last 7 and 28 days: accounts reached, views, accounts engaged, likes, comments, saves, shares, reposts, replies and profile link taps. No post text, no names and nothing about any other person. It is rolling out to members once Meta approves this permission, and is asked for only when Instagram statistics are switched on for you.
- Why: So the Statistics page can show how your own Instagram is doing, next to your other channels.
- How long we keep it: Nothing is stored. The totals are read from Instagram when you open the Statistics page, held in our server's memory for a few minutes, and shown to you.
- How to delete it: Disconnect Instagram in Settings (the stored access is deleted at once), remove StackSignal in Instagram's Settings → Apps and websites (Instagram tells us and we delete it automatically), or delete your account.
Assistants and automation apps you connect
On the Pro and Business plans you can connect an AI assistant (such as Claude or ChatGPT) or an automation app (Zapier or Make) to your StackSignal account. This is always your choice: you approve it on StackSignal's own Connect screen, or by making a Zapier & Make key in Settings.
- What the app can see: your own StackSignal numbers and posts, the same things your dashboard shows you. If you use the “New message or comment” automation, it also learns when someone sent you an Instagram message and their username (never the words of the message), and the comment counts on your own posts (never who commented or what they wrote).
- What the app can do: read only, unless you tick the separate box that lets it save drafts and ask to schedule a post. A post it asks for waits until you approve it in StackSignal.
- What we keep: a one-way fingerprint of the access we gave the app (never the access itself), the app's name and return address, and when it connected and was last used. Some apps (Claude and ChatGPT among them) introduce themselves with a public web address that describes the app. We read that public page to learn the app's name and return address. Nothing about you is sent when we do.
- After it leaves StackSignal: what the app does with what it reads is covered by that app's own privacy policy (Anthropic for Claude, OpenAI for ChatGPT, Zapier, Make).
- Stopping it: disconnect the app in Settings, or delete the key. Access stops at once. Moving to a plan without connections, or your plan ending, also ends it.
StackSignal for Chrome
StackSignal for Chrome is a free extension for the Chrome browser, from A Roll Media (FZE). It shows your StackSignal numbers and next move in Chrome's side panel, and can add the creator whose profile you are looking at to your list. It works only for StackSignal members, and only after you press Connect.
What it keeps on your device
- A connection key that tells StackSignal which member is asking, the last numbers it showed (so the panel opens at once and still works offline), a partly hidden version of your email address (for example j***@gmail.com) so you can see which account is connected, and a random number made when you install it.
- When you press Disconnect, or StackSignal tells the extension that a connection has ended, the key, the saved numbers and the partly hidden email are all removed from your device. Only the random number stays, so that connecting again replaces the old connection instead of adding another one.
- While you are connecting, a random secret that the extension makes when you press Connect. It is kept in the browser's memory only, never saved to disk. It is thrown away once the connection is made or when you press Disconnect, it stops working after ten minutes, and it is forgotten when you close Chrome.
- If you click the toolbar icon on a page, the extension notes which tab it was and, only if the page is a Substack, LinkedIn or Instagram profile, that profile's own address (for example https://name.substack.com/). Everything after it, such as tracking codes, a post or a sub-page, is cut off before anything is kept. This is kept in the browser's memory only, and is forgotten when you close Chrome or close the tab. After that click, Chrome lets the extension keep seeing that tab while you stay on the same website, so if you open another profile on the same website in that tab, the extension notes that one too without another click. When the tab moves to a different website, the note is dropped. The address of any page that is not such a profile is never kept.
What it sends to StackSignal
- Your connection key, with each request for your numbers.
- When you press Connect, the extension opens stacksignal.app in a new tab. The address carries the extension's own id, its random number, and a one-way fingerprint of the secret (never the secret itself). Once you are signed in and press “Connect Chrome” there, StackSignal's page is given a one-time connect code and passes only that code to the extension. The extension then sends the code and the secret to StackSignal and receives its connection key in return. The key is never shown to the web page. The code works once, for two minutes, and only for that browser.
- When you press “Add this creator”, only that profile's own address (for example https://name.substack.com/). Anything after it in your browser's address bar, such as tracking codes, a post or a sub-page, is removed first. The panel says so in one line above the button, and again on its first screen before you connect. StackSignal adds that creator to your list exactly as if you had added them on the website, so the same limits and the same handling of public data apply (see “Handles you add” and “Public data” above). Nothing else about the page is sent.
- Your browser's usual details, which we turn into a name such as “Chrome on Mac” so you can recognise the connection in Settings.
What it cannot do
- It does not watch your browsing. It has no permission to read your history or what is on any page, and it adds nothing to the pages you visit. The only exception is Substack, and only if you allow it: then it uses your own signed-in Substack for the features you switch on and press, described below. Chrome gives it the address of a page only after you click its toolbar icon on that page, and that carries on to other pages of the same website in that tab until you leave that website or close the tab. Those addresses stay in your browser: one leaves it only when you press “Add this creator”, and then it is only the cleaned address of that one profile.
- It ignores a connect code it did not ask for. Nothing connects unless you pressed Connect, in the panel or on stacksignal.app, in the last ten minutes.
- It never posts or replies anything you did not write or approve, never publishes a Substack post and never emails your subscribers (see the two parts below). It cannot change your plan, or see your card or sign-in details. Plans are bought on stacksignal.app, never in Chrome.
- It has no advertising, no tracking and no analytics.
Your control
- Press “Disconnect this browser” in the panel, or open Settings in StackSignal and end any browser in the Chrome card. An ended connection stops working at once, and the browser you disconnect also forgets the key, the saved numbers and the partly hidden email.
- Changing your sign-in email on stacksignal.app ends every connected browser at once, together with signing your other devices out, so a connection never outlives the sign-in it was made under. You can connect again in two taps.
- The Chrome card in StackSignal Settings lists every connected browser, with its name (such as “Chrome on Mac”) and when it was connected, so you can see each one and end it whenever you like.
- A connection key stops working 90 days after you last used it, and in any case after a year. Up to five browsers can be connected at once; connecting a sixth ends the one you used least recently.
Connecting in one press (StackSignal for Chrome 0.5.2 and later)
- Substack access is asked once, when you add the extension. From version 0.5.2, Chrome's own “Add extension” window asks you to allow StackSignal for Chrome on substack.com and your own *.substack.com address, so there is no second question later. Having that access does not start anything: nothing is read from Substack until you give your consent below.
- Your consent is given on the Connect screen. Above the Connect button on stacksignal.app there is one line: “One press connects subscribers, inbox, chats and auto-post.”, with links to this policy and our Terms. When you press Connect with that line in view, StackSignal records your consent for each of those features (your Substack stats, your subscriber list, reading your messages and comments, keeping the chats you tick, making drafts you ask for, and posting the Notes you approve at their time), with the time, the extension's id and version, and that it was given on the Connect screen. The extension then starts your first sync straight away, with no further Approve. Where no consent was recorded by that press (for example an older version of the extension), nothing is recorded and the extension asks you in its own panel instead.
- Chats you tick. Where Chats is switched on for your account, StackSignal for Chrome reads the Substack chats and direct messages you tick, from your own signed-in Substack, and StackSignal keeps a copy of their text (the words, times, the display names and pictures Substack shows, and reaction counts) so you can read them on your phone too. Only ticked chats are kept, for 90 days, and then they are deleted. No AI, assistant or connected app ever reads them, they are never part of anything public, and they are not in any export. Un-tick a chat, or press Erase in Chats, and its saved text is deleted at once; erasing your account deletes it all. StackSignal never sends a message from Chats. The list of your chats (names and pictures only, no message text) is kept so you can choose which to tick, and is deleted when you press “Erase all my saved chats”.
- What stays in your hands. Every reply still goes only when you press Send on that one message. Notes you have approved post at their time because posting publicly is part of what you agreed to on the Connect screen, and you can pause that at any time in the extension's panel or turn it off for good in Settings.
- Changing your mind. You can stop any one of these features at any time in the extension's panel (for example “Stop Substack sync”) or in StackSignal, or limit or remove the extension's Substack access in Chrome's own settings, or remove the extension. Stopping is recorded the same way, and nothing more is read.
Your Substack messages and comments (StackSignal for Chrome)
Once you have pressed Connect, StackSignal for Chrome can show your own Substack direct messages, the comments on your own posts and the replies to your own Notes, and send a reply you have written or approved.
- You allow it first. Nothing is read until you allow it: by pressing Connect, under the one line above the button, on stacksignal.app (version 0.5.2 and later), or by pressing “Allow reading my messages and comments” in StackSignal for Chrome. You can stop it there at any time, or by removing the extension's Substack access in Chrome.
- It reads only when you look. Messages and comments are read from your own signed-in browser when you open them or press Refresh. Nothing is read in the background. Group chats are left out, and nothing is marked as read on Substack.
- What it reads stays in your browser. Message and comment text, names and pictures are shown in the extension and in StackSignal's Inbox page in that same browser. They are not sent to or stored on StackSignal's servers.
- One exception, only when you ask. If you press “Draft with Alixc” (this needs AI help switched on), the text of that one message or comment is sent to StackSignal and our AI service to write a suggested reply; so the reply is written as you, the AI is also told how you are named on your own accounts (your own name, handle and publication names, from your own StackSignal record). For a comment on your own post or Note, so the reply can actually answer it, the AI is also given your post or Note (read from its public Substack page), the text of the comments above it in that thread (never their names), a count of your own posts and Notes from your StackSignal record, and your Alixc voice notes. It is used for that draft only and none of this text is stored or logged; StackSignal counts only that a draft was made (with the tone you chose) for your daily allowance. The sender's name, handle and picture are never sent.
- You press Send on every reply. StackSignal never sends a message or comment by itself, never starts a new conversation and never sends the same text to many people. Replies go only into conversations that already exist, under comments on your own posts, or under replies to your own Notes.
- What StackSignal keeps. When you allow it (and whether on the Connect screen or in the extension), and when you stop it, with the extension's version. For each reply you send, a small record with no words in it: the kind (message, comment reply or Note reply), a random reference number, which connected browser sent it, whether it was sent, and when. This is used for your daily limit and so a reply is never sent twice. It is deleted when you delete your account.
- Limited use. This information is used only to provide this feature to you. It is never sold, never used for advertising, never used to train AI models, and never shared except with the service providers that run StackSignal.
Substack Notes and drafts (StackSignal for Chrome)
- Posting a Note you approved. When you press Post on a Note you approved in StackSignal, StackSignal for Chrome posts it from your own signed-in Substack tab. StackSignal keeps the Note's words you approved, its time, whether it went out and Substack's number for it.
- Automatic posting at a time you choose (on after you press Connect, and you can pause it any time). Once you have pressed Connect, StackSignal for Chrome posts each Note you approved at its time, from your own browser while Chrome is open, connected to StackSignal and signed in to Substack. StackSignal keeps a record of when it was switched on or off. A Note that could not be posted within 2 hours of its time (for example because Chrome was closed) is skipped, never posted late, and StackSignal tells you. StackSignal never posts from its own servers.
- Send to Substack as a draft. If you press “Send to Substack as a draft”, the post you wrote in StackSignal goes from that page to StackSignal for Chrome in the same browser, which makes one private draft in your own publication. StackSignal keeps only a small record of that press and Substack's number for that draft (so pressing again opens the same draft), never its words. Publishing and emailing your subscribers stays your own click in Substack's editor.
- Keeping an article's draft in step with Substack (only after you press the button). If you press “Keep my drafts in step with Substack” in the Article editor, StackSignal for Chrome keeps ONE private draft of that article in your own publication, from your own signed-in tab, and updates it as you write. It only ever makes or updates a draft: it never publishes, schedules or emails anyone, and never sends a test email. StackSignal keeps Substack's number for that draft and a small record of the press. You can turn it off any time.
- Notes you scheduled on Substack (off unless it is switched on for your account). With your Substack sync consent, StackSignal for Chrome reads the list of Notes you scheduled on Substack itself, from your own signed-in browser, so they show on your StackSignal calendar. For each one StackSignal keeps only Substack's number for it, its scheduled time, its first 200 characters, who may reply and how many pictures it has (never the pictures). Nothing is changed, posted or cancelled on Substack, and a Note you delete or post there drops off your calendar at the next read.
- Pictures on a Note (being tested; not available to members yet). When you add pictures to a Note you approved, StackSignal for Chrome takes each picture from StackSignal and uploads it to your own Substack from your own signed-in browser, the way Substack's own composer does, only when that Note goes out. Pictures are never sent to any AI.
Your own Substack stats (StackSignal for Chrome, off unless it is switched on for your account)
- What it reads. Once a day, from your own signed-in Substack, the totals on your own publication's stats pages: how many subscribers you have in each country and US state (up to 100 places), your followers and views per day, where your traffic and new subscribers came from, new paid subscribers and paid subscriptions that ended, gift subscription totals, and for your newest 20 posts the email numbers split free and paid (sent, opened, open rate) with subscribes, free trials, upgrades, unsubscribes and restacks.
- Totals only. It never reads or keeps a reader's name, email or Substack id, and never your revenue. StackSignal keeps these totals in your account to show them to you, and deletes them when you delete your account.
The Chrome Web Store rules. What the extension handles is used only to provide the features described here. We do not sell it, use it for advertising, use it to judge creditworthiness or lending, or use it to train AI models. Our use of it follows the Chrome Web Store User Data Policy, including its Limited Use requirements.
Affiliate programme
StackSignal runs an affiliate programme on the website (see the Affiliate Terms). This is what it stores, and nothing more.
- If you open an affiliate's link (an address ending
?ref=and their code): a small first-party cookie,ss_aff, holds only that code and the day you first opened it, for 60 days. We add one to that affiliate's click count for the day. Clicks are a single number per affiliate per day: we don't store your IP address, a visitor ID or which pages you looked at. - If you then subscribe, we record that the affiliate referred you, your plan, whether you are signed up, on a trial, paying or cancelled, and the commission on each payment (worked out from the amount Stripe tells us was paid, refunded or disputed). The affiliate sees only your first name and last initial, your profile photo if you have one, your plan, that status and the date you joined. They never see your email, handles or stats.
- If you are an affiliate, we keep your link code, the version of the Affiliate Terms you accepted and when, your click counts, the people you referred (as above), your commissions and the payouts we send you, and the payout email or handle you give us for Wise or PayPal. We never ask for or store card data. To block self-referrals we compare, through Stripe, whether a referred payment used the same account, email or card as you; we keep only the result, never card details.
- Why we're allowed to. To run the programme you joined (contract), and to credit the right affiliate and stop abuse (our legitimate interests).
- How long. The cookie lasts 60 days. If you delete your account, your affiliate account is closed, your payout details are cleared and any unpaid commission is cancelled; commission and payout amounts are kept only as the financial records the law requires.
Automations you switch on
StackSignal can do some things for you in your name once you switch them on on the Automations page (see the Automations section of our Terms). These keep records of what they did, and only counts and numbers: never who commented or what they wrote.
Automatic replies. If you switch on Automatic replies, StackSignal replies to comments on your own posts for you, in your name. On Facebook it does this through the Facebook connection you already gave us, including while you are away. On Substack it does this from your own Chrome, with StackSignal for Chrome, inside your own signed-in Substack session, only while Chrome is open: comments under your own posts and replies directly under your own Notes. The words that go out are the replies you saved yourself. If a saved reply contains the {first_name} greeting, the commenter’s first name is read from the platform at that moment, put into the reply and not kept; on Substack that happens inside your own browser and the name never reaches StackSignal.
What we keep: the time you switched it on and the version of the wording in force, whether it is on or paused, when StackSignal for Chrome last checked in, the replies you saved (your own words), and for each comment we may answer, only its comment number, the number of the post or Note it sits under, a one-way fingerprint of the commenter that cannot be turned back into who they are, which of your saved replies fitted, which variation went out, a short status (waiting, replied, not sure, not sent, held for you) and the times. On Substack the words of a comment are read inside your own browser only to see which of your saved replies fits and are never sent to StackSignal. We never keep, show or store the name, handle, picture or words of anyone who comments, and we never send any of it to an AI. When you ask Alixc to suggest wording for a saved reply, only the kind of comment it is for and your own voice notes are used, never what any commenter wrote. The screen shows counts, such as “12 sent today”, not names. Pause all stops it at once; switching it off stops it too. Deleting your account deletes these records.
Auto-like. If you switch on Auto-like, StackSignal likes comments on your own posts for you, and on Substack also replies in those comment threads and replies under your own Notes. On Facebook it does this through the Facebook connection you already gave us, including while you are away. On Substack it does this from your own Chrome, with StackSignal for Chrome, inside your own signed-in Substack, only while Chrome is open, by making the same request Substack’s page makes when you press the heart. It only likes. It never replies, follows, messages or posts.
What we keep: the time you switched it on and the version of the wording in force, a switch that says on or off, the choice you make of who gets Substack likes (stored as private reference numbers of your own tags and people, never names), and for each comment we may like, only its comment number, the number of the post or Note it sits under, the name of your own publication (when it is a post), a short status (waiting, liked, not sure, not sent) and the times. We never keep, show or store the name, handle, picture or words of anyone who comments, and we never send any of it to an AI. StackSignal for Chrome reads new comments and replies on your own posts and Notes in your browser and tells StackSignal only numbers and true or false facts about them. To choose who gets a like, a commenter’s Substack number is checked once against your own Audience and then dropped. The screen shows counts, such as “12 liked today”, not names. Switching Auto-like off stops it at once. Deleting your account deletes these records.
Audience automations. If you switch on “Tag new subscribers”, “Mark most active people as VIPs” or the weekly “say hello” list, StackSignal adds and removes tags and VIP marks on the people in your own Audience for you. It works only inside StackSignal: it does not touch your email list or any other service, and it never contacts anyone.
What we keep: the time you switched each one on and the version of the wording in force, a switch that says on or off, the time it last looked, and for each tag or VIP mark it set, only that person’s private reference number in your Audience, the kind of mark, the month it was set for and the time the tag or mark was set. It uses information already in your Audience: the date a person joined, Substack’s activity rating, emails opened in the last 30 days and the last time they opened an email. None of this is sent to an AI, and your own tags and VIPs are never listed or changed by it.
New Substack subscriber to Kit. If you switch it on, StackSignal reads the email address and first name of each new Substack subscriber in your Audience and sends them to your own Kit account through your own Kit connection, to add them to the sequence and tags you chose. It keeps a record of each person it handled with only a masked address (such as ma***@gmail.com) and a one-way fingerprint, never the full address, and the assistant never sees any of it. The time you switched it on and the version of the wording in force are kept with your settings. It is used only for this automation.
Super fan to Kit and VIP to Kit. If you switch either on, StackSignal reads the email address and first name of the people you marked in your Audience and sends them to your own Kit account through your own Kit connection, to add them and give them the tags (and sequence) you chose. It keeps a record of each person it handled that holds only a masked address, a one-way fingerprint and a few fixed words, and a record of when each person first reached five stars if you chose Super fan. The addresses never go to an AI, are never shown to anyone else and are not kept beside those records. Switching it off stops it at once; deleting your account deletes the records.
What you press once to switch on
For the tools in the Tools and connections section of our Terms, pressing the button for a tool is your OK for it. Here is what each one reads or keeps. Nothing is sold, used for ads or shared with another member.
Outlier Engine. If you switch it on, StackSignal looks at the numbers of your own connected accounts to spot a post that takes off, and emails you about it (at most 3 a week). It keeps the time you switched it on and when it last ran. Nothing is posted for you.
Welcome messages. If you switch them on, StackSignal notes the new subscribers it sees on your Substack so it can send them the messages you wrote, and keeps a record of what was sent and when. The time you switched it on and the version of the wording in force are kept with your settings. It is used only for your own welcome messages.
Your Kit subscribers. If you approve it, StackSignal brings your Kit subscribers into your Audience hub to match them with your Substack readers. Only you can see them. StackSignal keeps a one-way fingerprint of each email address, never the address itself, and the assistant never sees any of it. You can delete them any time. They are never sold, never used for ads and never shared with another member.
beehiiv. If you connect it, StackSignal keeps your beehiiv key and reads your subscriber totals and how your emails perform, only to show them to you. The key is deleted when you disconnect.
Files you add to the Audience hub. A subscriber list or a LinkedIn or Instagram export you add is read on your own device and its people are stored securely for you only: names, emails or profile links, dates and the other columns in the file. StackSignal never emails them, and you can delete all of it any time in Settings.
Message people. StackSignal keeps your message, the people you chose (their Substack handle, name and picture, as already shown in your Audience) and what happened to each message (sent, not sure or skipped), so nobody gets the same message twice and you can follow its progress. It is only for you, is never sent to an AI, never put in Kit and never shared, and it is deleted with your account.
How we use it
Only to run StackSignal: sign you in, bill you, show your dashboard, send the emails you'd expect from the service (sign-in codes, receipts, a welcome series for new members, a weekly Growth Brief, occasional rival breakout alerts (at most 3 a week) and a milestone email when you pass a new milestone, at most one a day, each of which you can turn off in Settings or from the link in any of those emails) and keep the service secure. If you schedule a post and it can't be sent, we email you once about that post. We don't sell your data or use it for advertising. Your private stats and connected-account data are only ever shown to you. We don't use artificial intelligence to profile you or make decisions about you. The writing style profile described under “What we collect” is used only to word drafts for you.
Why we're allowed to
To provide the service you signed up for (contract); to keep it secure and working (our legitimate interests); and, for the optional free newsletter, your consent, which you can withdraw by unsubscribing. For connected accounts, your consent on the platform's approval screen, which you can withdraw by disconnecting.
Who processes it
These companies process data for us, only to provide their service to us and under their data-protection terms. We don't sell or rent your data to anyone.
- Vercel Inc. (hosting and servers, India and United States) · Supabase Inc. (database, India and United States) · Stripe (website payments) · Resend (sign-in and service email delivery, Japan and United States)
- Sentry (error and security monitoring): receives technical error reports and security alerts, with message, DM, chat and comment text, email addresses, request bodies, cookies and query strings removed before anything is sent
- Apple (App Store purchases) and Google (Google Play purchases), only if you use the apps
- RevenueCat (verifies app-store purchases and tells us whether your subscription is active)
- Kit (our mailing list for customer emails, such as the welcome series)
- Google (only if you choose “Continue with Google”, to confirm your email)
- A specialist public-data collection provider (fetching public LinkedIn and Instagram data)
- Google YouTube API Services (fetching public YouTube channel and video data, and, only if you connect YouTube, uploading the videos you confirm and reading your own channel's analytics for its stats window)
- An AI service (Anthropic PBC's Claude, United States, reached through Vercel's AI Gateway or directly), to put into plain words the short “Today's move” tip we write for you each day and, when you tap “Why did this pop?”, why one of your posts did well, and to answer questions you type into “Ask about my numbers” (we don't store your questions or the answers). It receives a short summary of your own numbers and the titles of your own posts and, for Ask, the public names and numbers of the people you track, the same ones you already see in your dashboard. It never receives anything about other StackSignal members, and it is not used to train AI models. Tips are kept for 60 days; “why it popped” notes until you delete your account.
- The same AI service, for “Suggested for you” on the Content tab: it words three post ideas a day from the facts we build (your own top posts' titles and numbers, your public profile bio, a few of your own opening lines when your writing style profile is on, and the public posts of people you track), writes a starting draft when you tap “Draft this” (using your writing style profile and a few of your own public posts as a guide to your tone: see “Your writing style profile” above), and rewrites your draft when you tap a quick-polish button (it receives the draft text you are editing). Nothing is posted anywhere for you. Ideas are kept for 8 days so reloading costs nothing; drafts you keep are stored until you delete them or your account. A tracked creator's name is never saved in a draft. You can rate any idea or draft, or report it as offensive, and a person reviews every report. With AI help off, ideas come from your numbers alone and drafts are fill-in templates.
- The same AI service, for chat with Alixc, our in-app Coach, if he is switched on for you: when you type a question to Alixc, that message, up to the last six messages of the chat and the name you asked him to call you go to the AI service to write one short reply. Alixc is not sent your numbers, posts or accounts, or anything about other members. We don't store or log your messages or his replies. It needs your agreement to AI help, so nothing is sent if you haven't agreed or you turn AI help off. His tour and starter buttons are answered by StackSignal itself and send nothing to the AI service. Alixc's panel also sends our server your device's hour of the day (0 to 23) so he can say good morning or good evening; it is used on the spot, is not stored or logged, and is never sent to the AI service.
- Our AI assistant (the same AI service), for your writing style (Alixc): when AI help is on and Alixc writes a draft, it receives your style profile, a few of your own recent posts and, if you set one, your weekly goal, and about once a week up to 24 of your own recent posts to update the profile. Nothing is sent if AI help is off. The full detail, including what is stored and how to clear it, is under “Your writing style profile” above.
- The same AI service, for “Draft a reply” in the Instagram and Facebook Inbox (only if it is switched on for you and you have agreed to AI help): when you tap it on one message or comment, it receives the text of that one message or comment and the tone you chose (warm, short or detailed), plus how you are named on your own accounts (your own name, handle and publication names, so the reply is written as you), and nothing else: not the sender's name, handle or picture, any ID or time, your other messages, a voice note or your numbers. It writes one suggested reply, which we show you and do not keep or log. Nothing is sent without your tap, and nothing is sent to anyone until you press Send.
- The same AI service, for “Draft with Alixc” on your Substack messages and comments in StackSignal for Chrome (only if it is switched on and you have AI help on): when you press it on one message or comment, it receives the text of that one message or comment and the tone you chose, plus how you are named on your own accounts (your own name, handle and publication names, so the reply is written as you). For a comment on your own post or Note it also receives that post or Note, the text of the comments above it in the thread, a count of your own posts and Notes, and your writing style (a short description of how you write, up to two of your own posts as examples and, if you wrote one, your own note on how you want to sound), so the reply can answer what was asked. It never receives the sender's name, handle or picture, or your other messages. It writes one suggested reply, which goes back to your browser and is not kept. Nothing is ever sent to Substack without your press on Send.
- The same AI service, for “Ask Alixc” in the Article editor, which is not available yet and sends nothing today. Once it is switched on: When you tap “Ask Alixc” in the Article editor, the text of that one article (its first 6,000 characters, never pictures), with its title and subtitle, is sent to the same AI service to write a few title and subtitle ideas. Nothing else is sent: not your readers, numbers, accounts or other drafts. It only happens when you tap, we don’t store or log the text or the ideas, nothing is used to train the AI, and nothing in your article changes until you press “Use”. It needs your agreement to AI help, so nothing is sent if you haven't agreed or you turn AI help off.
- Substack (your newsletter subscription, only if you choose to join it)
- Instagram (Meta) and LinkedIn (Microsoft), only for accounts you choose to connect
- Buffer, only if you choose to connect your Buffer account
We may also disclose data when the law requires it. See Requests from public authorities below.
Requests from public authorities
If a court, regulator, police force or other public authority asks A Roll Media (FZE) for your data, we:
- review every request to check it is lawful and properly made before we act on it;
- challenge any request we consider unlawful, too broad or lacking a proper legal basis;
- disclose only the minimum information necessary to answer a lawful request;
- keep a record of every request, how we responded and the legal reasoning behind our response;
- tell you about the request before we disclose anything, unless the law prohibits us from doing so.
Where it's stored
Our processors work in several countries, including India (our hosting and database, Mumbai), the United States, Japan (email delivery) and the European Union. Where data moves between countries, it's covered by the processor's standard data-protection terms.
How long we keep it
For as long as your account is open. The retention of your writing style profile, edit habits and the first versions of drafts is set out under “Your writing style profile” above. Sign-in codes expire after 10 minutes and sessions after 90 days of inactivity. Time-on-app totals are removed after 90 days. Rate-limit counters are deleted within 48 hours. The IP address and browser details of a sign-in session are deleted about a week after that session expires (sessions expire 90 days after you last used them). Automated-access monitoring records, when that monitoring is on, are deleted after 90 days. Instagram and Facebook messages and comments are not stored; Instagram message previews, if switched on for you, are deleted 30 days after the message was sent; the Inbox's new-item counts go when you disconnect. Handles stop refreshing automatically as soon as an account is closed or its plan ends. When you delete your account (yourself, in Settings, or by emailing us) we remove your email, handles, uploads, private stats, screenshots, goals, daily tips, “why it popped” notes, post ideas and drafts, your writing style profile and edit habits, your Audience hub list (people, tags, VIPs, groups and imports), scheduled posts, message-inbox previews, AI ratings, your Substack message, comment and draft send records and the switches you set for them in StackSignal for Chrome, weekly brief and rival alert history, the link tag that first brought you, connected-account tokens and data, sign-in history and time-on-app totals, your Inbox reply and like records and any picture or video you attached to a reply, and take you off our mailing list. Self-service deletion happens immediately; an emailed request is completed within 30 days. We keep only the billing records the law requires, with no link to your handles or stats. Chrome connection keys stop working 90 days after you last use them, and a year after they were made at the latest. The record of each connection (browser name and dates) stays until you delete your account. A one-time connect code is of no use after two minutes or after its first use; its fingerprint is tidied away the next time you connect once it is over an hour old, and in any case when you delete your account.
Security
Everything travels over HTTPS (with HSTS, so browsers always use it) and our pages send strict security headers. Data sits in access-controlled databases with row-level security; only StackSignal's own server can read or write member data, and our database provider encrypts it at rest. Access tokens for accounts you connect (Instagram, Facebook, LinkedIn, Buffer and others) are encrypted with AES-256 before they are stored. Sign-in codes are stored only as one-way hashes, work once, expire after 10 minutes and lock after a few wrong tries, and card details never touch our servers. Messages from Meta (data-deletion requests and new-message notices) are accepted only with a valid signature. Admin tools are open only to the owner's accounts, and rate limits protect sign-in and every sensitive action. If a breach ever affects your data we will tell you and the authorities as the law requires.
We also run error and breach monitoring: technical errors, and alerts for things such as repeated wrong sign-in codes, rate limits being hit, automated access and attempts to open admin tools, are reported to our monitoring service as counts and IDs only. Message, DM, chat and comment text, email addresses, request bodies, cookies and query strings are removed before anything is sent, and no screen recording is ever made.
To protect your data, StackSignal watches for automated access (bots, scrapers and AI agents driving a browser) and may pause it. Assistants you connect in Settings are not affected.
Your rights
Wherever you live, you can ask for a copy of your data, a correction, to object, or for deletion, at any time. If you are in the EEA, the UK, the UAE or a US state with a privacy law, these rights are set out in the law that applies to you and we honour them for everyone. We don't discriminate against you for using them. We reply within 30 days. You can complain to your local data-protection authority.
To withdraw a consent (for example to stop the newsletter), unsubscribe from the newsletter on Substack, or disconnect an account in Settings. Withdrawing doesn't affect anything done before. To delete your data, see Data deletion. If your public profile has been added to someone's competitor list and you want your handle's data removed from StackSignal, email support@stacksignal.app and we'll remove it and block it from being added again.
Children
StackSignal is for adults only (18+). We don't knowingly collect data from anyone under 18 and will delete it if we learn we have.
Changes
If we change this policy in a way that matters, we'll tell you by email before it takes effect, and we'll ask for your permission again if we ever want to use connected-account data for something new.
Contact
Privacy contact: support@stacksignal.app, or reply to any StackSignal email. Postal address: A Roll Media (FZE), Block B-B56-131, SRTIP, P.O. Box 66636, United Arab Emirates. More help: Support.