Brainy SocialBY IS&S

Privacy Policy

Last updated: November 20, 2026

This policy explains what personal data Brainy Social collects, including from the social accounts you connect, how we use it, who receives it, how long we keep it and what rights you have.

Brainy Social is operated by Integration for Services and Solutions (IS&S), Arabic legal name انتيجريشن فور سيرفيسس اند سوليوشن, First Northern Touristic Area, Plot 2, 6th of October, Giza, Egypt ("IS&S", "we"). It applies to our website, app and public pages.

1.Who is responsible for your data

IS&S decides how and why data is used for your Brainy Social account, billing, security and product operation.

For content a business handles through its workspace, such as its Brand Brain, customer comments and messages, link-in-bio leads and client reports, that business or agency decides why the data is used and we process it on its behalf. If you are one of its customers, please contact that business first. We will help it respond, and you can also write to us.

2.Data we collect directly

  • Account data: name, email address, phone number, company or brand name, country, account type (personal or agency), password (handled by our authentication provider in hashed form), profile picture and language, plus when you accepted our terms and how you heard about us. If you continue with Google, we receive your name, email address and profile picture from Google, and ask you for the rest. Your phone number is only visible to you and our team, not to your workspace colleagues.
  • Workspace data: workspace names, members and roles, profile and cover photos of brands and agencies, publishing settings, time zone and notification preferences. A brand's photos are public while it has a published link-in-bio page, and appear on reports you share.
  • Content you provide: Brand Brain entries, websites you ask us to read, uploaded files, images and videos (including files you add from a link, which we download from that address), briefs, drafts, schedules, replies, notes and answers to the onboarding assistant.
  • API and MCP activity: for access tokens that can publish, a record of what each token did (for example creating, scheduling or cancelling a post, or importing media), with the time and the person who created the token, shown to the workspace's owners and admins.
  • Connected apps: when you connect an AI app (such as Claude or ChatGPT) with one click, the app's name and the address it returns to, the workspace and access you chose, when it was last used, and its access and refresh tokens, stored only as one-way hashes. Access tokens expire after an hour and refresh tokens after 30 days; expired ones are deleted within a day, and you can disconnect an app at any time in AI & MCP settings.
  • Help and sales requests: messages to the in-app assistant and details you send in a quote request or by email.
  • Technical data: IP address, used briefly to limit abuse, plus request and error logs. See Cookies for what we store in your browser.
  • How you found us: the campaign tags (UTM parameters) and ad click IDs (such as gclid, fbclid or ttclid) in the link you first opened, the site that sent you there (its address without the query), the first page you opened and when. We keep this from your first visit and attach it to your account when you sign up, to learn which channels bring customers. Only you and our team can see it.

3.Data from connected social accounts

We access a social account only after someone with authority over it approves the connection on the platform's own consent screen, and only through official APIs. We do not scrape these platforms. What we can read depends on the permissions granted.

  • Meta (Facebook and Instagram): your app-scoped Meta user ID; names, handles, pictures and follower counts of the Pages and Instagram business accounts you manage; posts, media, captions and insights; comments, mentions and direct messages for the inbox, including the names and IDs of the people who wrote them. If you connect ads: ad accounts, campaigns, ad sets, ads, budgets, spend and performance. We also read public data such as hashtags and public business profiles for listening and competitor features, using your connected account.
  • X: your profile, posts, public metrics and mentions and, only if your X app has the permission, direct messages. X accounts use your workspace's own X developer app. Its Client Secret is stored encrypted, and X bills you directly.
  • TikTok: basic profile and statistics, your video list and video metrics, and upload and publishing access. Public trend data may come from TikTok's Research API.
  • LinkedIn: the organization pages you administer, their posts, comments and statistics, and permission to publish to them.
  • Threads (Meta): your Threads profile (ID, username, name, picture, follower count), your posts and their insights (views, likes, replies, reposts, quotes), the replies to your posts with the usernames of the people who wrote them, and permission to publish, to answer replies and to hide them.
  • Google Business Profile: the business locations you manage (name, address area, Maps link), their updates (posts), the reviews customers left with the reviewer's public name and picture and their star rating, your replies, and daily performance numbers (searches, map views, calls, website clicks, direction requests, messages, bookings). Permission to publish updates and to reply to reviews.
  • YouTube (Google): channel details, videos, statistics, analytics and comments, and permission to upload and to answer or moderate comments.
  • Auto-replies (Facebook, Instagram and WhatsApp chats): only if an owner or admin turns them on. Brainy then reads new comments and direct messages as described above and, following your rules, sends public replies, direct-message replies and one private message per comment through Meta's official APIs, within Meta's time limits. If a rule lets AI write the reply, the conversation and your Brand Brain go to the AI provider of your workspace's own key, as for reply suggestions. We keep a log of what was sent, skipped or handed to a person.
  • Google Analytics 4 and Search Console: read-only access, only if an owner or admin connects them. We read the list of properties the Google account can see, then for the property and site you choose: aggregated website numbers (sessions, users, page views, engagement, top pages, traffic channels) and Google Search numbers (clicks, impressions, click-through rate, position, top search queries and pages). These are totals, not data about individual visitors. We keep the latest numbers per period and remove them when you disconnect.
  • Pinterest: your business account's profile (ID, username, name, picture, follower count), your boards, your pins and their numbers (impressions, saves, reactions, comments), daily account analytics (impressions, engagements, saves, pin and outbound clicks), and permission to create pins and boards.
  • Telegram: your bot's token, which you create with @BotFather and paste into Brainy (stored encrypted), and the channel you connect (ID, title, username, subscriber count). Through your bot we post to the channel, and we read the messages people send to the bot and the comments in the channel's discussion group, with the senders' Telegram names, usernames and IDs, for the inbox.
  • WhatsApp Business (Meta): the WhatsApp Business Account and phone numbers you share during Meta's signup (number, verified business name, quality rating), your message templates, and the chats customers start with you: their WhatsApp number, profile name and messages, delivered to us by Meta for the inbox. We send your replies, approved templates and auto-replies through Meta's Cloud API. Meta charges your WhatsApp Business Account for conversations.
  • Canva: only if you connect your own Canva account (each person connects their own). We read your Canva user ID, display name and the list of your designs, and export only the designs you choose to import into a post. Tokens are stored encrypted and nobody else in the workspace can use them.
  • Ad accounts on Google Ads, TikTok and LinkedIn: only if an owner or admin connects them, through each network's official API (Google Ads API, TikTok API for Business, LinkedIn Marketing API). We read the ad accounts you can access (name, currency, time zone, status), their campaigns, ad groups and ads with status and budgets, and daily performance (spend, impressions, clicks, conversions and, where reported, reach and conversion value). We change something only when you ask: pausing, turning on after you confirm, editing a budget after you confirm, or creating a new campaign, which is always created paused. Tokens are stored encrypted.
  • Online stores (Salla, Zid, Shopify): only if an owner or admin connects a store. Read-only access to the store's name, address and currency and to its product catalogue (titles, descriptions, prices, photos, links, stock status and SKUs) so you can turn products into posts. We do not read orders or customer data. On Shopify, if you send a blog article from Brainy, we also list your blogs and create that article. If you install the app from Shopify before choosing a workspace, we keep the store's access token encrypted for up to 7 days until you sign in and pick one, then delete it. When a Shopify store uninstalls the app, or Shopify asks us to erase a shop, we delete its connection, any waiting install and imported products.
  • WordPress: only if an owner or admin connects a site. We store the site address, the WordPress username and an Application Password you create in WordPress (encrypted). We use them to check the account can publish and to create the posts, tags and cover images you send from Brainy. You can revoke the Application Password in WordPress at any time.
  • Snapchat: only if an owner or admin connects a Snapchat Public Profile through Snap's official Public Profile API. We read the profile (ID, display name, username, logo, subscriber count), your recent Stories and Spotlight posts and their numbers (views, unique viewers, shares, replies, favourites), and we upload the photos and videos you schedule, encrypted as Snap requires, to post them as Stories, Spotlight or Saved Stories. Tokens are stored encrypted. You can remove Brainy from your Snapchat account's connected apps at any time.
  • Snapchat Ads: only if an owner or admin connects them through the Snapchat Marketing API. We read your organizations and ad accounts (name, currency, time zone, status), their campaigns, ad squads and ads with status and budgets, and daily performance (spend, impressions, swipes, unique reach, purchases and their value). We change something only when you ask, with the same confirmations as other ad networks; new campaigns are always created paused.
  • Bluesky: only if an owner or admin connects an account with a Bluesky app password. We use the password once to sign in and do not store it; we keep the encrypted session tokens. We read your public profile (DID, handle, display name, avatar, follower count) and your recent posts with their likes, reposts, quotes and replies from Bluesky's public API, and we create the posts (text, images, video) you publish from Brainy. Bluesky posts are public. You can revoke the app password in Bluesky's settings at any time.

Access tokens and platform secrets are encrypted at rest (AES-256-GCM), are never shown in the browser and are used only to perform the actions you ask for.

YouTube and Google: Brainy Social uses YouTube API Services, so using those features also means agreeing to the YouTube Terms of Service. The Google Privacy Policy applies to Google's handling of your data, and you can revoke our access in your Google security settings. Our use of data received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

4.How we use data

  • To provide the service: create, adapt, schedule and publish content; show your inbox, analytics, trends, listening, competitor and ads views; and send notifications.
  • To perform actions you request on a platform, such as publishing, replying, hiding a comment, or changing an ad budget after you confirm it.
  • To personalize results for your workspace, for example best posting times worked out from your own account's performance.
  • To produce anonymized network benchmarks: weekly totals per platform and segment, stored only when enough workspaces contribute, and containing no account IDs, names or post text.
  • To secure the service, prevent abuse, enforce plan limits, provide support, keep records and meet legal obligations.

We do not sell personal data, and we do not use platform data to advertise to you. Depending on where you are, our legal bases include performing our contract with you, your consent (which you can withdraw), our legitimate interests in running a secure service, and legal obligations.

5.AI processing

Brainy Social uses AI to read your sources into the Brand Brain, write and adapt content, curate trends, suggest inbox replies, assess sentiment, suggest ad audiences and answer help questions. To do that, the relevant text is sent to an AI provider, which may include Brand Brain content, briefs, post captions, comments and messages. Attachments are sent only for the features that need them.

  • AI runs only on the API key a workspace connects for OpenAI, Anthropic or Google Gemini: the relevant text goes to that provider under the workspace's own agreement with them. We do not send your workspace's content to an AI provider under our own account, with one exception: while a new workspace without its own key is being set up, the onboarding assistant and the Brand Brain import (your answers, and the website pages or files you choose to import) may run on our own Anthropic account, for a limited number of requests. That help ends when onboarding is complete.
  • Without a key, AI features use offline templates and nothing is sent to an AI provider.
  • For each workspace we record how many tokens its keys used per month, provider and model, as the provider reported them, to show on the AI settings page. We do not keep the prompts or answers for that.
  • AI assistants you connect through our MCP server or API (such as Claude Desktop or ChatGPT) receive what they ask for under your own account with their provider.
  • We do not use your content or platform data to train AI models, and we do not authorize our AI providers to do so.
  • AI suggestions can be wrong. Inbox replies are never sent automatically: a person must review and send them.

6.Agencies and their clients

An agency can manage several brands in Brainy Social. Its team can access a brand's data according to the roles the agency assigns, and changes to that access are recorded in an audit log.

If a client is invited to a portal, they can see that brand's scheduled posts, connected account names, the agency's branding, reports shared with them and post reviews. They do not see the brand's internal data.

The agency is responsible for having its client's authorization to connect accounts and process their data, for its contract with the client, and for answering its client's requests. Reports are saved snapshots, so they may still contain figures after an account is disconnected, until the report is deleted.

7.Link-in-bio pages and shared reports

Link-in-bio pages are public, as are reports opened through a share link. Visits and clicks are counted as statistics. We do not store visitors' IP addresses or browser user agents for this: unique visitors are estimated with a hash that changes daily.

If you submit a contact form on a business's page, your details go to that business, which is responsible for how it uses them.

8.Payments

Payments are handled by a third-party payment provider, such as Stripe or Paymob. We do not receive or store your full card number. We keep your plan, billing period, currency, invoices, payment status and the provider's reference numbers. The provider handles your payment details under its own privacy policy.

Egypt pricing. To check who qualifies for prices in Egyptian pounds, we use: the country of your connection, and whether it looks like a VPN or proxy, when you pay and once a day when you use the app; an Egyptian mobile number you verify by SMS, through an SMS provider; the issuing country of your card, from the payment provider; and, for agency plans, a commercial register or tax card number or copy, which our staff review. We don't keep your IP address for this: we store the country and a keyed hash of the address. This only decides which price applies.

9.Who receives data

We share data only as needed to run the service, under contracts or platform terms that limit its use:

  • Infrastructure: Supabase (database, authentication and file storage) and our hosting and queue providers.
  • AI providers: as described in AI processing.
  • Email: Resend, for notifications and reports.
  • Social and ad platforms: the content and instructions you send to them.
  • Your automation tools: if an owner or admin adds a webhook, we send the events they choose (published posts, new inbox messages and comments with the sender's name and text, link-in-bio leads with the contact details given) to the URL they enter, such as a Zapier, Make or n8n address. That service then handles the data under its own terms; we keep the events for 30 days for retries and the API.
  • Payment providers: as described in Payments.
  • Your organization: workspace members, your agency and invited clients, according to their roles.
  • Our staff: a small number of IS&S staff can see account, plan and usage details, and can view an account read-only to help with a support, billing or safety issue. That view lasts up to 30 minutes, can't change anything, and is recorded with the staff member's name, the reason and the time. They never see your connected accounts' tokens or your AI keys.
  • Authorities and advisers: where the law requires it, or to protect rights and safety. If our business is transferred, data may transfer with it under this policy's protections.

Some of these providers process data outside Egypt and outside your country. Where the law requires it, we rely on appropriate safeguards for those transfers.

10.Cookies and browser storage

We use only cookies that the service needs or that remember your choices. We do not use advertising or third-party analytics cookies.

  • Session (`sb-…`): keeps you signed in.
  • Language (`NEXT_LOCALE`) and theme (`bs_theme`): remember your preferences.
  • Last workspace (`bs_last_ws`) and agency (`bs_agency`): reopen where you left off.
  • First visit (`bs_acq`): remembers how you first reached our site (see “How you found us” above) for 90 days, so we can attach it to your account if you sign up. It is our own cookie, is never shared with advertisers and is not overwritten by later visits.
  • Connection security (`bs_social_oauth`, `bs_ads_oauth`, `bs_web_oauth`, `bs_canva_oauth`, `bs_store_oauth`): protect the connection flow for about 10 minutes.
  • Shopify install (`bs_shopify_install`): after you install the app from Shopify, lets only your browser attach the store to a workspace, for up to 7 days.

Your browser may also store your theme choice and the current help chat, which stays on your device for that browser session. Blocking necessary cookies prevents sign-in.

11.How long we keep data

  • Account and workspace data: while the account or workspace exists, then deleted following a deletion request.
  • Connected accounts, tokens and their posts, inbox threads and ad data: until the account is disconnected or a deletion request is processed.
  • Hourly post metric history: up to 180 days.
  • Daily ad insights: about 100 days.
  • Listening mentions: up to 90 days.
  • Webhook events and delivery records: 30 days.
  • Abuse-prevention records using IP addresses: usually no more than 24 hours.
  • Login country and hashed address, for Egypt pricing: 90 days.
  • Verified mobile number and business documents, for Egypt pricing: while the account exists, or until replaced.
  • Billing and tax records: for as long as the law requires.
  • Ad-change audit logs: while the workspace exists. They may keep an ad account's name.
  • Deletion request records: the confirmation code, status, counts and dates, as proof the request was carried out, without your Meta user ID once completed.
  • Backups: removed in the normal backup cycle.

12.Your rights

Depending on the law that applies to you, including Egypt's Personal Data Protection Law No. 151 of 2020 and, where applicable, the EU and UK GDPR, you may have the right to:

  • know what data we hold about you, access it and receive a copy;
  • correct inaccurate data;
  • have your data deleted or its processing restricted;
  • object to certain processing;
  • withdraw consent at any time, for example by disconnecting a social account; and
  • complain to your data protection authority.

To use these rights, email info@integration-ss.com from your account's address. We may need to verify your identity, and we aim to answer within 30 days. See Data deletion for deletion steps.

13.Security

We use encryption in transit, encrypted storage of platform tokens and API keys, tenant isolation at database level, role-based access, rate limits and security reviews. No system is perfectly secure. If a breach affects your data, we will notify you and the authorities as the law requires.

14.Children

Brainy Social is a business tool for people aged 18 or over. It is not directed at children, and we do not knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.

15.Changes to this policy

We will post changes on this page and update the date at the top. For significant changes, we will also notify you by email or in the app before they take effect.

Contact us

Integration for Services and Solutions (IS&S)

First Northern Touristic Area, Plot 2, 6th of October, Giza, Egypt

Email: info@integration-ss.com

Phone: +20 100 370 3755