Back

Privacy Policy

Last updated: 3 November 2026

Platform-API registration: Our app URL is https://www.heysocialfish.com and this Privacy Policy is accessible at https://www.heysocialfish.com/legal/privacy as required for TikTok, Google/YouTube, LinkedIn, X, and Meta (Facebook/Instagram) API registrations.

1. Who We Are

HeySocialFish Ltd ("we", "us", "our") is the data controller for personal data collected through the HeySocialFish platform. We are registered in England and Wales.

Website & App: https://heysocialfish.com

Contact: support@heysocialfish.com

We're a small, independent team. This policy is written to be understood, not to bury the important bits in legalese. If anything is unclear, just ask us directly.

2. What Data We Collect

Account data: Name, email address, password (hashed), subscription tier, billing information (processed via payment gateway — we do not store card details).

Content data: Content you create, upload, or generate using the platform, including posts, video analysis results, strategy plans, and campaign data.

Platform connection data: OAuth access + refresh tokens for connected social platforms (YouTube/Google, TikTok, LinkedIn, X, Instagram, Facebook) and for social sign-in providers (Google, Microsoft, LinkedIn). These are stored in encrypted secret storage. See Section 3 for a per-platform breakdown of scopes, purpose, and revocation.

Performance data: Available post identifiers, titles or captions, publication dates, account identifiers and performance counters requested from connected platforms, as described below. Some measurements need additional permissions and may not be available.

Usage data: AI credit usage, feature usage, log data, session information, and error reports.

Voice and likeness data (optional, not yet switched on): only if you choose the optional voice features described in Section 7b: a recording of you reading a consent statement, a short sample of your voice, the synthetic voice made from them, and the parts of your own videos you ask us to re-voice or lip-match.

Technical data: IP address, browser type, device identifiers, and cookies (see Cookie Policy).

3. Connected Platforms — What We Access and Why

When you connect a third-party platform via the Connect page, or sign in with a social provider, we access data from that provider through their OAuth 2.0 API. The permissions below support the connected features. Connecting a publishing account can also enable the background performance checks described here; publishing still requires your approval. Social sign-in uses the separate grants in Section 3.2. The permissions a provider actually grants determine what data is available.

3.1 Connected platforms: publishing and performance

YouTube (Google): Scopes youtube.readonly, youtube.upload and yt-analytics.readonly. We read your connected channel's identity and recent video metadata. When you open Results, we request your channel and video statistics and YouTube Analytics reports, including views, watch time and subscribers gained or lost by day, to show how your content performed. The current live reporting integration does not save these reports as performance snapshots. We upload videos you review and approve with Private visibility; you can change their visibility in YouTube Studio. Disconnect on /connect; see Section 3.3 for credential cleanup. You can separately revoke the provider grant at myaccount.google.com/permissions.

TikTok: Scopes user.info.basic, video.list, video.upload and video.publish. We read your connected handle and recent video identifiers, descriptions and view, like, comment and share counts. Background performance checks run about every four hours and store available counters with your workspace. We upload or publish videos you review and approve through the Content Posting API. TikTok data is processed in accordance with TikTok's Privacy Policy. Disconnect on /connect; you can separately revoke the provider grant in TikTok's app settings.

LinkedIn (publishing): Scopes openid, profile, email and w_member_social. We read your LinkedIn identity for display and publish posts you review and approve to the connected member account. LinkedIn analytics is not currently collected. Disconnect on /connect; you can separately revoke access through LinkedIn's data-sharing preferences.

X (Twitter): Scopes tweet.read, tweet.write, users.read and offline.access. We read your connected identity for display and publish posts you review and approve. X analytics collection is disabled: we do not collect new X analytics data. Previously stored results may remain in workspace history. The offline.access scope permits a refresh token for the connected publishing account. Disconnect on /connect; you can separately revoke the provider grant in X's Connected Apps settings.

Facebook (Meta): Scopes public_profile, pages_show_list, pages_read_engagement and pages_manage_posts. We list Pages you manage so you can choose one and publish posts you review and approve to that Page. About every four hours we request recent post identifiers, text and available reactions, comments and shares to show how the Page's posts performed. We also attempt Page insights, such as reach and impressions, where granted permissions allow them. An optional consent request for read_insights is offered for additional insights; requesting it does not mean provider approval has been granted. Disconnect on /connect; you can separately revoke the provider grant in Facebook's Business Integrations settings.

Instagram (Meta): Scopes instagram_business_basic and instagram_business_content_publish. We read the connected professional account's identity and publish media you review and approve to that account. About every four hours we request recent media identifiers, captions, dates and like and comment counts. The integration also attempts media insights, such as impressions, reach, saves and shares, where available under the granted permissions. If you request additional insights, we ask for instagram_business_manage_insights; requesting it does not mean provider approval has been granted. Disconnect on /connect; you can separately revoke the provider grant in Instagram's Apps and Websites settings.

3.2 Sign-in providers (used to log in to HeySocialFish itself)

These OAuth grants are entirely separate from the publishing OAuths above. Different apps registered with each provider, different scopes, different purpose — just identifying you to create or log you into your HeySocialFish account.

Sign in with Google: Scopes openid + email + profile. We read your Google display name and email address to create or link your HeySocialFish account. We do not access YouTube, Drive, Gmail, or any other Google service via this scope. Revoke at myaccount.google.com/permissions.

Sign in with Microsoft: Scopes openid + email + profile + User.Read. We read your Microsoft display name and email for account creation/linking. We do not access Outlook, OneDrive, Teams, or any other Microsoft service via this scope. Revoke at account.live.com/consent/Manage or, for work/school accounts, via your Entra tenant admin.

Sign in with LinkedIn: Scopes openid + email + profile. We read your LinkedIn display name and email for account creation/linking. This is a distinct LinkedIn OAuth app from our publishing integration above — no content-write scope. Revoke via LinkedIn's data-sharing preferences.

3.3 OAuth token storage and deletion

Connected publishing-platform access and refresh tokens are held in encrypted secret storage and are not returned through the application interface. Disconnect stops newly started application use of that connection. We request deletion of its stored credential and confirm completion before clearing our cleanup reference. If deletion fails or a shared reference needs review, cleanup remains pending and is retried; it is not guaranteed to finish within the disconnect request. The secret store may retain recoverable, soft-deleted copies for its retention period, so this is not an immediate permanent purge. Disconnect does not automatically revoke the provider grant: use the provider's account settings if you also want to revoke that grant. Requests already in progress may complete. Account deletion is a separate request; see Section 9.

Saved work and performance history: We keep saved posts, uploaded or generated media, plans and stored performance snapshots as workspace data. A disconnect does not delete this workspace history or remove content already published on a provider. Background Facebook, Instagram and TikTok checks store recent post metadata and available counters; the live YouTube reporting integration currently displays its reports without saving them as performance snapshots. Deleting workspace data is separate from disconnecting an account. We do not read private messages or use OAuth credentials to train AI models.

3.4 Google API Services User Data Policy compliance

HeySocialFish's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we use YouTube API data only to power the features described in Section 3.1 (identify your connected channel, upload approved videos, and display channel and video statistics and YouTube Analytics reports). We do not use it for advertising. We do not sell it. We do not use it to train generalised AI models. We allow humans to read it only where required for security, to comply with law, or with your explicit permission.

3.5 Disclosure: who we share Google user data with

To be explicit about disclosure of data received from Google APIs (including YouTube Data API v3 and Google Sign-In):

  • We do not sell Google user data. We do not sell any user data, ever, to anyone.
  • We do not share Google user data with advertisers, ad networks, data brokers, or analytics providers. HeySocialFish contains no third-party advertising trackers.
  • We do not transfer Google user data to any third party outside the list below. Every named processor is engaged strictly to deliver HeySocialFish's stated features; each operates under a Data Processing Agreement and is bound by their own privacy policy.

Categories of processor that may handle Google user data:

  • Our cloud infrastructure provider (UK data residency) — hosts our application, encrypted database, and secure token storage. Google OAuth tokens are held in encrypted secret storage; profile fields (email, display name, picture URL) and YouTube channel metadata (channel id/title, saved video identifiers and metadata for publishing) are held in our encrypted database. No cross-border transfer of Google user data outside the UK/EEA.
  • OpenAI — receives only content you deliberately submit to an AI feature (e.g. a caption you asked Copilot to help write, a transcript for the Video Splitter). We do not send raw Google user profile data or YouTube listing data to OpenAI. OpenAI processes prompts under its enterprise privacy commitments and does not use API content to train shared models.
  • Stripe and GoCardless — payment processors. They receive billing details (name, email, address, card/DD data submitted on their hosted forms). They never receive Google user data or YouTube data.
  • Brevo — transactional email provider. Receives only recipient email address + the transactional message body (verification, password reset, receipts). Never receives Google user data or YouTube data.
  • Google (YouTube Data API v3, Google Identity) — the originating platform. We call Google's own APIs to read the channel state and publish videos you have composed in HeySocialFish. This is not a "transfer to a third party" — it is fulfilling the purpose Google authorised the token for.
  • Operational tooling (error monitoring, uptime checks) — receives only sanitised technical metadata (route, status code, timing). Personal identifiers, OAuth tokens, and API content are stripped before submission. Never receives Google user data or YouTube data content.

A complete, current list of sub-processors is maintained internally and available to users on request at support@heysocialfish.com.

Legal disclosure only: Google user data may be disclosed to law-enforcement or regulators where legally required (e.g. a valid UK court order or a lawful information notice from the ICO). We will notify affected users unless legally prohibited from doing so.

Merger, acquisition, or change of control: If HeySocialFish Ltd is acquired or merged, we will notify users in advance via email and give at least 30 days to export or delete data. The acquirer must honour these terms or offer a comparable protection level; a link to the successor privacy policy will be published here.

Any change to who we share Google user data with will be reflected in this section and communicated by email to active users at least 14 days before it takes effect.

4. How We Use Your Data

  • To provide, maintain, and improve the Service
  • To personalise AI Copilot guidance and content suggestions
  • To process subscription payments and manage your account
  • To send service-critical notifications (account, billing, security alerts)
  • To send product updates and hints (you can opt out any time)
  • To investigate abuse, fraud, or policy violations
  • To comply with legal obligations

We do not sell your data to third parties. We do not use your content to train AI models shared with other customers.

5. Legal Basis (UK GDPR)

  • Contract: Processing necessary to provide the Service under our Terms of Service
  • Legitimate interest: Security monitoring, fraud prevention, service improvement
  • Consent: Marketing communications (opt-in)
  • Explicit consent: The optional voice features in Section 7b. Checking that a consent recording and a voice sample come from the same person is biometric processing, so we rely on your explicit consent (UK GDPR Article 9(2)(a)), which you can withdraw at any time by deleting your voice.
  • Legal obligation: Compliance with applicable law

6. Data Storage, Security & Workspace Protection

Our core application data is stored on cloud infrastructure in the UK. Third-party processors may process data in other regions, as described below, including the planned optional voice features in Section 7b. We apply encryption at rest and in transit, role-based access controls, and regular security reviews.

Workspace isolation: Each user account operates within a private, isolated workspace. Your workspace data — plans, content, analytics, AI interactions — is stored separately and is not accessible to any other user of the platform. No cross-user data queries are possible through normal or API-level use of the Service.

Connected platform credentials: OAuth tokens for connected social platforms (TikTok, LinkedIn, Instagram, X, YouTube, Facebook) are stored in encrypted secret storage. They are never exposed in plaintext, cannot be retrieved via the application interface, and are not shared with any third party beyond the intended platform integration.

Staff access: HeySocialFish staff do not access workspace content in the normal course of operations. Access may occur only where strictly necessary for technical support you have requested, or to comply with a legal obligation — and only with appropriate authorisation and logging.

Your responsibility: While we protect your data on our end, you are responsible for the security of the devices and credentials used to access your account. If you choose to share your login with others, you accept responsibility for their actions within your workspace. We cannot protect your account from risks you introduce yourself.

7. Third-Party Processors

We use the following third-party processors under Data Processing Agreements. Each is engaged for a narrow, defined purpose and is bound by their own privacy policy and (where applicable) UK GDPR standard contractual clauses:

  • Cloud infrastructure provider — hosts our application, encrypted database, object storage, and secret storage. UK data residency. Named on request.
  • OpenAI — our AI provider for language and transcription. Powers the Copilot, Content Plan Generator, Post Composer, Video Splitter moment selection + captions, and Text Repurposer via GPT language models, plus Video Analysis + Video Splitter transcription via Whisper. Content sent to OpenAI is not used to train their models (per their enterprise privacy commitments). We name every AI provider on this page and in the AI Disclaimer before we start sending your content to it (see Section 7b for optional voice features that are not yet switched on).
  • Stripe — card payment processing. Card details are entered on Stripe's hosted form; we never see or store card numbers. Stripe operates under their own privacy policy and is authorised by the FCA under FRN 900461.
  • GoCardless — Direct Debit payment processing for UK subscribers who prefer bank-debit. Bank details are not stored by us; GoCardless operates under their own privacy notice and is authorised by the FCA under the Payment Services Regulations 2017 (FRN 597190).
  • Brevo (formerly Sendinblue) — transactional email delivery (verification, password reset, team invitations, beta welcome, billing confirmations). Brevo processes email delivery under their own privacy policy.
  • Connected platform providers — TikTok, Google/YouTube, LinkedIn, X, Meta (Facebook/Instagram). We interact with these via their public OAuth 2.0 APIs when you have explicitly connected them (see Section 3). We are not a "processor" for these providers — each is the controller of its own data on its own platform.

7b. Optional Voice Features (not yet switched on)

We are preparing an optional feature that lets you change the words in one of your own videos and have them spoken in your own voice. It is not switched on yet, and none of your data is sent to the providers below until it is and you choose to use it. When it is available:

  • Only your own voice, only with your explicit consent. You record yourself reading a consent statement and a short voice sample in the app. We never make a voice from someone else's recording or from videos you upload, and your voice is only used for your own workspace.
  • Microsoft (Azure AI Speech, Personal Voice) would receive your consent recording and voice sample to create your synthetic voice, check that both come from the same speaker, and speak the lines you edit. We plan to use Azure's Sweden Central region; Personal Voice is not currently available in the UK. Microsoft adds an inaudible watermark to synthetic speech.
  • Sync Labs (sync.so) would receive only the short part of your video around a line you edited, with its new audio, if you choose to match your lip movements for that line. This processing takes place in the United States, under UK GDPR safeguards for international transfers.
  • You approve every edit. Each changed line shows its cost and how its picture will be handled (matched lips, an extra shot over it, or the picture as filmed) before anything is made. Nothing is chosen for you, and a re-voiced video is never posted without your approval.
  • Clearly labelled. Videos with a synthetic voice or matched lips are marked as AI-altered when we post them, using each platform's own label where it offers one.
  • Delete it any time. You can delete your voice in the app. We then delete your consent recording, voice sample and synthetic voice, and request deletion at the provider. We keep a minimal record of your consent and withdrawal. Microsoft may separately retain a copy of a personal voice model to protect its service's security and integrity; see Microsoft's voice data policy.

Before switching this on we will update this section with any changes and tell you in the app.

8. Data Retention

We retain your data for as long as your account is active. On account closure, we delete personal data within 90 days, except where we are required to retain it for legal or financial compliance purposes (typically 7 years for financial records under UK law).

8b. Your Contacts' Data — CRM Features

HeySocialFish Membership includes CRM-style contact management features (the "Contacts" section of the Sales Hub). These features allow you to store names, email addresses, and engagement notes about your own contacts — people you are communicating with in your business.

You are the data controller for your contacts' data. HeySocialFish acts only as a data processor on your behalf for this data. Your contacts have rights under UK GDPR that you are responsible for honouring:

  • Right to be forgotten: If one of your contacts requests erasure of their data, you must delete them from the Contacts section. Use the Delete action on their record, or export and purge their data.
  • Unsubscribe requests: If a contact no longer wishes to receive email from you, you must respect that. Use the Unsubscribed tag on their contact record and do not include them in future mail sends. HeySocialFish does not add automated unsubscribe footers to mail sent from the Sales Hub — this is your responsibility.
  • Consent: You should only store contacts for whom you have a legitimate reason to hold data (e.g. they are a business contact, a customer, or have opted in to hear from you). Do not use the Contacts feature to store data obtained without a lawful basis.
  • Data portability: Use the Export CSV button to provide a contact with a copy of their data if requested.

HeySocialFish stores your contact data on the same secure cloud infrastructure as your other workspace data. Contact data is workspace-isolated and never shared with other users. We do not use your contacts' data for any purpose beyond providing the CRM feature to you.

If a contact of yours contacts us directly requesting erasure or unsubscription, we will forward that request to you as the controller. We cannot act on it without your instruction unless legally required to do so.

9. Your Rights (UK GDPR)

You have the following rights regarding the personal data we hold about you as a HeySocialFish user:

  • Access — request a copy of the data we hold about you
  • Rectification — correct inaccurate data
  • Erasure ("right to be forgotten") — request deletion of your account and all associated personal data
  • Restriction — limit how we use your data
  • Portability — receive your data in a machine-readable format (JSON/CSV)
  • Object — object to processing based on legitimate interest
  • Withdraw consent — at any time, for processing based on consent
  • Unsubscribe from marketing — use the unsubscribe link in any marketing email, or use the button below
Exercise your rights

To request erasure, a data export, or unsubscription — email us with your registered email address and the action requested. We will respond within 30 days.

✉ Submit a GDPR request
Or write to: HeySocialFish Ltd — support@heysocialfish.com — subject line: GDPR Request

You may also lodge a complaint with the ICO (Information Commissioner's Office) at ico.org.uk.

10. Cookies

We use cookies and similar tracking technologies. See our Cookie Policy for full details.

11. Changes to This Policy

Material changes will be notified via email or in-app notification. The latest version is always available at: https://www.heysocialfish.com/legal/privacy.

11b. Your Responsibilities as a User

When you use the Sales Hub CRM and mail features, you take on responsibilities as a data controller for your contacts' personal data. These include:

  • Ensuring you have a lawful basis for holding and contacting each person in your CRM
  • Honouring unsubscribe and erasure requests promptly
  • Not using the platform to send unsolicited bulk email (spam)
  • Keeping contact data accurate and up to date

HeySocialFish provides the tooling; the legal responsibility for how you use it rests with you. Our Terms of Service reflect this responsibility.

12. A Note to Early Adopters

If you're one of our early users — thank you. Your data protection matters to us, and so does your trust. We will never do anything unexpected with your data, and we welcome questions or concerns at support@heysocialfish.com. Early adopters have a direct line to the team and a real say in how the platform develops. Use it.

Terms of Service →Cookie Policy →AI Disclaimer →Data Deletion →