Legal

Privacy Policy

What we collect, why we collect it, who else processes it, how long we keep it, and what you can ask us to do with it.

Last updated: October 2026

1. Who We Are

  • Social Sphere CRM is a content planning, approval, publishing and social media collaboration platform for agencies, marketing teams and their clients. It is operated by Zero One Creation, which is the data controller for the personal data described in this policy.
  • This policy covers the Social Sphere CRM web application at socialspherecrm.com, the marketing website, and the Social Sphere CRM Android application (package com.socialspherecrm.app), which presents the same web application and is governed by this same policy.
  • For any privacy question, request or complaint, email contact@zeroonecreation.com.

2. Information We Collect

  • Account details: your name, email address and profile image. These come from Google if you sign in with Google, or from what you enter when you register with an email address.
  • Authentication data: if you register with an email and password, we store a cryptographic hash of that password, never the password itself. If you sign in with a one-time email code, we store only a hash of the code until it is used or expires. If you sign in with Google, we store the tokens Google issues, encrypted at rest.
  • Workspace data: workspace names and logos, client names and contact addresses you enter, member roles, invitations, ideas, scripts, blog posts, social posts, captions, schedules, tasks, comments, approval decisions, campaigns and notification preferences created by you or your team.
  • Media: images, video and other files you upload to a workspace media library or as a profile image, together with their filenames, sizes and types.
  • Connected platform data: when you connect a social or business account, the account identifiers, names, profile images, tokens and metrics described in section 6.
  • Comments and messages: if your workspace uses the engagement inbox, the public comments and WhatsApp messages described in section 7.
  • Public posts: if your workspace uses social listening, the public posts matching your search terms described in section 8.
  • Billing data: your subscription plan, its status and billing dates, and, if you add them, your legal business name, GSTIN and billing address. Card and payment credentials are collected and processed directly by Razorpay; we never receive or store your full card details.
  • Usage and log data: IP address, browser and device user-agent, and a record of significant actions taken in a workspace, kept in an audit log so workspace owners can review who did what.
  • Feedback and bug reports: what you write, the page you were on, any screenshots you attach and, only if you choose to include them, technical details such as browser, operating system, screen size, language, time zone and recent error messages.
  • Communications: messages you send through our contact form or to our support address, and our replies.

3. How We Use Your Information

  • To provide the service: authentication, workspaces, content planning, approvals, scheduling, media storage and notifications.
  • To publish content to the accounts you connect, at the times you schedule, and to show you the analytics, comments and mentions described in sections 6 to 8.
  • To send transactional email: address verification, one-time sign-in codes, password resets, workspace invitations, approval requests, reminders, digests, trial notices and billing notices. You control the optional notifications in notification preferences; verification, security and billing messages are necessary to operate the account and cannot be switched off.
  • To process subscription payments, manage renewals and issue invoices through Razorpay.
  • To keep the service secure and available: rate limiting, abuse and bot prevention, error monitoring, enforcing plan limits, and maintaining audit trails for workspace owners.
  • To improve the product using aggregated, de-identified usage patterns.
  • We do not use your content to train AI models, we do not sell your personal data, and we do not show advertising or share your data with advertising networks.
  • We do not use data received from any connected platform for advertising, profiling or any purpose other than providing the features you use in your workspace.

4. Legal Bases For Processing

  • Performance of a contract: providing the service you or your organization signed up for, including authentication, workspaces, publishing and billing.
  • Consent: connecting a social or business account, connecting Slack or WhatsApp, opting in to WhatsApp notifications, authorizing a third-party application to access your workspace, and optional notification emails. You can withdraw consent at any time by disconnecting, opting out, revoking the authorization, or changing your preferences.
  • Legitimate interests: securing the service, preventing abuse, maintaining audit logs for workspace owners, and improving the product using de-identified data.
  • Legal obligation: retaining financial and tax records.

5. Sharing & Service Providers

  • We do not sell your personal data, and we do not share it with advertisers or data brokers.
  • Workspace content is visible only to members of that workspace, scoped by their role, and to anyone you send a client review link (section 9).
  • Vercel: hosts and serves the application, records anonymous page-level usage through Vercel Analytics, and receives the hostname when you add a custom domain.
  • Cloudflare: content delivery and network protection; processes request metadata including IP addresses.
  • Neon: hosts the PostgreSQL database holding account and workspace data.
  • Cloudflare R2: stores the files you upload.
  • Razorpay: receives your name and email address, and your legal business name and GSTIN if you provide them, in order to take payment and issue invoices.
  • ZeptoMail (Zoho): delivers transactional email and receives the recipient address and content of every email we send.
  • Inngest: orchestrates scheduled publishing, analytics syncs, reminders and digests, and processes the identifiers, names and email addresses those jobs act on.
  • Sentry: error monitoring. Receives technical details of errors; it is configured not to collect personal data by default and does not record sessions.
  • Better Auth: security tooling for the sign-in system. Receives sign-in activity and browser signals, including user-agent, used to detect bots and abuse.
  • Sanity: stores our own marketing blog, and, if you connect it, receives the blog content you publish to your own Sanity project.
  • Convex: relays live teleprompter controls between your devices. It receives session identifiers, playback state and a device label, never your identity or script text.
  • Google and Twilio STUN servers: help two of your devices connect directly for the teleprompter. They see only your devices' network addresses.
  • Google: identity provider when you choose to sign in with Google.
  • Connected platforms (Meta, Threads, X, LinkedIn, YouTube, Pinterest, Bluesky, Google Business Profile, WhatsApp and Slack): receive the content and replies you choose to send and return the data described in sections 6 to 9.
  • These providers process data on our instructions under contract. We may also disclose data where required by law, or to establish, exercise or defend legal claims.

6. Connected Social & Business Accounts

  • Connecting an account is optional. The product is fully usable for planning, drafting and approvals without connecting anything. Connected accounts are used only to publish content you or your workspace created and scheduled, and to show analytics and comments for those accounts inside your workspace. Nothing is published without a deliberate action by a workspace member, either publishing directly or scheduling a post for a time they chose.
  • For each connected account we store its platform identifier, display name, username, profile image, follower count and the tokens needed to act on it, encrypted at rest. Account-level analytics are synced daily, starting with the previous 30 days, and post metrics are synced for posts published through Social Sphere CRM. We do not read private or direct messages on any social platform, and we do not read your personal feed.
  • Facebook and Instagram (Meta): we request pages_show_list, pages_read_engagement, pages_manage_posts, read_insights, instagram_basic, instagram_content_publish, instagram_manage_insights and business_management to list the Facebook Pages and Instagram professional accounts you manage, publish posts, photos, videos, Reels and Stories, and read Page and account insights. Where the engagement inbox is offered we also request pages_read_user_content, pages_manage_engagement, pages_manage_metadata and instagram_manage_comments to read, reply to and hide comments on your recent posts. Your use is subject to the Meta Platform Terms (developers.facebook.com/terms) and Meta Privacy Policy (facebook.com/privacy/policy).
  • Threads: we request threads_basic, threads_content_publish and threads_manage_insights to read your profile, publish text, image, video and carousel posts, and read account and post insights. Your use is subject to the Threads Terms of Use and Threads Supplemental Privacy Policy, published at help.instagram.com.
  • X: we request tweet.read, tweet.write, users.read, media.write and offline.access to read your profile and follower count, publish posts with images or video, and read public metrics for posts we published. Your use is subject to the X Terms of Service and Privacy Policy (x.com/tos, x.com/privacy), and our access is governed by the X Developer Agreement.
  • LinkedIn: we request openid, profile, r_organization_social, w_organization_social and rw_organization_admin to list the LinkedIn Pages you administer, publish posts with images or video to them, and read their share and follower statistics. LinkedIn is used only to connect Pages, not to sign in. Your use is subject to the LinkedIn User Agreement and Privacy Policy (linkedin.com/legal).
  • YouTube: we request openid, email, profile, youtube.upload, youtube.readonly and yt-analytics.readonly to read your channel, upload videos you schedule, and read channel and video analytics. Where the engagement inbox is offered we also request youtube.force-ssl to read and reply to comments on your channel. Social Sphere CRM uses YouTube API Services: by connecting YouTube you agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google's handling of your data is described in the Google Privacy Policy (https://policies.google.com/privacy).
  • Pinterest: we request user_accounts:read, boards:read, pins:read and pins:write to read your profile, follower count and boards, publish Pins to the board you choose, and read account and Pin analytics. Your use is subject to the Pinterest Terms of Service and Privacy Policy (policy.pinterest.com).
  • Bluesky: you connect with your handle and an app password you create in Bluesky, never your account password. We store the app password encrypted and use it to publish posts with images and links and to read profile and post counts. Your use is subject to the Bluesky Terms of Service and Privacy Policy (bsky.social/about/support).
  • Google Business Profile: we request openid, email, profile and business.manage to list your business accounts and locations (name, address, phone number, website and categories), publish and delete local posts you manage here, and read daily performance metrics such as searches, map views, website clicks, calls and direction requests. We store the Google account email used to connect. We do not read or reply to reviews. Your use is subject to the Google Terms of Service and Google Privacy Policy (https://policies.google.com/privacy).
  • Social Sphere CRM's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. (https://developers.google.com/terms/api-services-user-data-policy)

7. Engagement Inbox & WhatsApp

  • On plans that include it, the engagement inbox collects public comments left on your recent Facebook Page posts, Instagram posts and YouTube videos, by webhook from Meta and by regular polling. For each comment we store the commenter's platform identifier, name or username, YouTube profile image where provided, the comment text, a link to it and when it was made.
  • Workspace members can reply to comments and, on Facebook and Instagram, hide or unhide them. Replies are sent through the platform's own API and stored with the member who sent them. We never delete comments on any platform.
  • A workspace can connect its own WhatsApp Business number through Meta's WhatsApp Business Platform, using a phone number ID and access token it provides. We then receive messages customers send to that number: the sender's phone number and profile name, the text of text messages, and delivery statuses. Photos, files and other media are not downloaded. Members can reply within the 24-hour window WhatsApp allows. Your use is subject to the WhatsApp Business Terms of Service.

8. Social Listening

  • On plans that include it, a workspace can set up monitors that search for terms in public posts. Sources are public YouTube videos, public Bluesky posts, and, where enabled, recent public posts on X searched through the workspace's connected X account, and Instagram hashtags searched through the workspace's connected Instagram account.
  • For each matching post we store its text, link, publication time, language, public engagement counts, and the author's public name or handle. No author is stored for Instagram hashtag results. Listening never reads private content.
  • Mentions are deleted automatically 90 days after they were published, and immediately when their monitor is deleted.

9. Notifications, Integrations & Client Review Links

  • Slack: if you connect Slack we request chat:write, chat:write.public, channels:read and groups:read to list channels and post workspace notifications (a title, a short message, the workspace name and a link) to the channel you choose. We store your Slack team ID and name and an encrypted bot token.
  • Webhooks: you can send the same notifications to Microsoft Teams, Google Chat, Discord or any HTTPS endpoint you control. We store the URL and signing secret encrypted, and sign each delivery.
  • WhatsApp notifications: workspace members can choose to receive notifications on WhatsApp through the workspace's connected number. We store the phone number they enter and when they consented. Opting out stops messages immediately and keeps a record of the opt-out.
  • We keep a log of each notification delivery, including its text, link and recipient channel or phone number, so workspace admins can see what was sent.
  • Client review links: a workspace can share a private link that lets a client review posts and scripts without an account. Anyone with the link can see the workspace name and logo and the content shared for review; drafts are never shown. Reviewers enter a display name, which their browser remembers. Approvals and change requests are recorded with that name, IP address and user-agent. Links expire after 60 days and can be revoked at any time.
  • Invited clients who join a workspace see only what their client role allows.

10. Other Features

  • Blog publishing (Sanity): you can connect your own Sanity project with its project ID, dataset and an API token. We store the token and a webhook secret encrypted, send blog posts and their images to your project only when you choose to save or publish, and import posts from it only when you ask.
  • Teleprompter: you can display a script on a second device paired by QR code or connection code. Sessions expire after 12 hours, only hashes of the pairing tokens are stored, and session records are deleted within a day of the session ending.
  • Custom domains: if you add a custom domain, we send the domain name to Vercel to configure and verify it.
  • Content import: you can upload a CSV file to create draft posts. We do not import existing posts from your social accounts.

11. Third-Party Application Access

  • Social Sphere CRM can act as an authorization server, so that an external application (for example an AI assistant that supports the Model Context Protocol) can be granted access to your workspace on your behalf.
  • This happens only when you explicitly approve it on a consent screen that names the application and the permissions it is requesting. Access is limited to those permissions and to what your workspace role allows, every action it takes is recorded in the workspace audit log, and access tokens expire after one hour.
  • Data such an application reads is sent to whoever operates it, under their privacy policy rather than ours. Only grant access to applications you trust.
  • You can revoke an authorization at any time from your profile page. Revoking removes the application's consent and its refresh tokens, so it cannot obtain new access; an access token it already holds expires within one hour.

12. Data Retention & Deletion

  • We keep your data while your account is active. Workspace data, including synced analytics, inbox comments and messages, and the notification delivery log, is kept for as long as the workspace exists, including after an account is disconnected, so that its history remains available to the workspace.
  • You can permanently delete your account yourself at any time. See socialspherecrm.com/account-deletion for the exact steps and the full list of what is deleted and what is retained.
  • Deleting your account removes your profile, sign-in methods, sessions, third-party application authorizations, every platform login you linked and its tokens, your WhatsApp notification number, your feedback reports, pending invitations and email notifications addressed to you, your workspace memberships, and every workspace you are the billing owner of together with all of its content, connected accounts, analytics, inbox, listening monitors and integrations.
  • Content you created in a workspace owned by someone else stays in that workspace and is reassigned to its owner.
  • Files go with them: deleting a workspace or your account removes its uploaded files, your profile image and your feedback screenshots from storage in a background job, normally within minutes.
  • Unsubscribe choices are kept after deletion so that an address that opted out is never emailed again.
  • Invoices and payment records are retained for as long as tax and accounting law requires, currently seven years in India, with your profile unlinked from them.
  • Audit-log entries recording actions you took in someone else's workspace are retained for that workspace's owner, with your user account unlinked from them.
  • Encrypted database backups may still contain your data for up to 30 days after deletion, after which they expire.
  • Aggregated, de-identified statistics that cannot be traced back to you are retained indefinitely.

13. Disconnecting & Revoking Access

  • You can disconnect any connected account at any time from workspace settings. Publishing, syncing and inbox collection for it stop, and its name and identifier are kept, marked disconnected, for the workspace's history. Content already published to a platform remains there; remove it on the platform if you no longer want it public.
  • Disconnecting deletes the tokens stored for that account: Facebook Page and Instagram tokens, the Threads token, and the Bluesky app password. For Google Business Profile we also revoke the grant with Google. For X, LinkedIn, YouTube and Pinterest, and for your Facebook login itself, the token belongs to the login you linked to your profile; it stays stored, encrypted, until you delete your account, and you can end it immediately by revoking access on the platform using the links below.
  • Disconnecting Slack revokes our token with Slack. Disconnecting a webhook, WhatsApp or Sanity deletes the stored credentials.
  • You can also revoke our access directly on each platform: Google and YouTube at https://myaccount.google.com/permissions; Facebook and Instagram under Settings, Business Integrations on Facebook; Threads under Settings, Account, Website permissions; X at x.com/settings/connected_apps; LinkedIn at linkedin.com/mypreferences/d/permitted-services; Pinterest under Settings, Security and logins, Apps; Bluesky by deleting the app password under Settings, Privacy and security, App passwords; Slack from your Slack workspace's app management page.
  • If you remove Social Sphere CRM from your Facebook settings, Meta tells us and we delete the Page tokens and mark the affected accounts as needing reconnection. If you ask Meta to delete your data, we also delete your linked Facebook login and its tokens, and return a confirmation code to Meta. Workspace content and the metrics of posts already published are kept for the workspace.

14. Security

  • All traffic is served over HTTPS with strict transport security. Session cookies are signed, and are set HttpOnly and Secure so that page scripts cannot read them.
  • Passwords are stored only as hashes produced by a memory-hard key derivation function. One-time sign-in codes are stored hashed and expire after ten minutes.
  • Sign-in tokens, connected platform tokens, Bluesky app passwords, Slack, webhook and WhatsApp credentials, and Sanity tokens are encrypted at rest with AES-256-GCM or our authentication library's token encryption, and are decrypted only to make a request to that service.
  • Authentication endpoints and third-party application access are rate limited, which makes credential-guessing and email-flooding attacks impractical.
  • Data is encrypted at rest by our database and storage providers. Access to production systems is restricted to those who need it.
  • No system is perfectly secure. If a breach affects your personal data we will notify you, and the relevant authority, as required by applicable law.

15. International Transfers

  • We are based in India. Several of our service providers operate globally, so your data may be processed in countries other than your own, including the United States and countries in the European Union.
  • Where personal data is transferred out of the EEA or the UK, we rely on the European Commission's Standard Contractual Clauses or on an adequacy decision, as offered by the provider concerned.

16. Your Rights

  • Access and correct your account information at any time from your profile page.
  • Delete your account and its data yourself, from your profile page, without contacting us.
  • Request a copy of your workspace data by emailing contact@zeroonecreation.com.
  • Object to or restrict certain processing, and withdraw consent where processing is based on consent.
  • If someone else's workspace stored your public comment, message or post through the engagement inbox or listening, contact that workspace or us and we will help you exercise your rights.
  • Residents of India under the Digital Personal Data Protection Act, of the EU and UK under the GDPR, and of other regions have additional statutory rights, including the right to complain to a supervisory authority. We honor valid requests regardless of where you live.
  • We respond to privacy requests within 30 days.

17. Cookies & Local Storage

  • We use essential cookies to keep you signed in and to protect the service. These cannot be switched off without breaking sign-in.
  • We use your browser's local storage for interface preferences, such as your theme, the workspace you last had open, and the name you enter on a client review link.
  • The installed web app and the Android app cache application code and static branding assets on your device so they load quickly and can show an offline notice. Workspace content and API responses are not cached on the device.
  • We do not use advertising cookies or cross-site tracking cookies, and Vercel Analytics does not set cookies to track individuals.

18. Children

  • Social Sphere CRM is business software intended for use by adults. It is not directed at children, and we do not knowingly collect personal data from anyone under 18.
  • If you believe a minor has provided us personal data, contact us and we will delete it.

19. Changes & Contact

  • We may update this policy as the product evolves. Material changes are announced by email or an in-app notice before they take effect.
  • Email contact@zeroonecreation.com for any privacy inquiry, data request or complaint.
  • We aim to respond within 48 hours on business days, and within 30 days at the latest.

Questions about any of this?

Email contact@zeroonecreation.com and a person will reply.

Contact form