Skip to main content
Dispatchr

Privacy Policy

How we collect, use, and protect your data.

About This Policy

Effective Date: October 6, 2026

This Privacy Policy explains how Dispatchr ("Dispatchr", "the Service", "we", "us"), a social media management platform operated by Corey Alan Consulting in the United States, collects, uses, stores, shares, and protects your information. Dispatchr is available at https://dispatchr.social.

Dispatchr lets you draft, schedule, publish, and measure social media content across connected accounts on YouTube, Facebook, Instagram, LinkedIn, and TikTok from a single workspace. Corey Alan Consulting is the data controller for the purposes of the GDPR, and is the developer and operator of Dispatchr.

If you connect a Google account or a YouTube channel to Dispatchr, please read the "Google User Data" section below. It describes in specific terms what Google user data Dispatchr accesses, how we use it, who we share it with, how we protect it, and how long we keep it.

Google User Data

Dispatchr uses Google APIs for two distinct features: optional Sign in with Google authentication, and the optional YouTube channel integration that publishes and measures videos on your behalf. Both are opt-in. If you never sign in with Google and never connect a YouTube channel, Dispatchr accesses no Google user data about you at all.

What Google user data Dispatchr accesses

We request only the OAuth scopes required by the features you choose to use. When you grant access, Dispatchr accesses the following Google user data:

Sign in with Google (scopes: openid, email, profile)

  • Your Google account identifier
  • Your email address and whether Google has verified it
  • Your name
  • Your Google profile picture

YouTube channel integration (scopes: https://www.googleapis.com/auth/youtube.readonly, https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/youtube.force-ssl)

  • Channel information — the channel ID and channel title of the YouTube channels you own, so you can choose which channel to publish to and see it labeled in the Service.
  • Video statistics — the public view, like, and comment counts for videos you published through Dispatchr, so we can show you performance analytics for your own content.
  • The content you submit for publishing — the video file, title, description, tags, category, and privacy status you enter in Dispatchr, which we transmit to YouTube on your behalf.
  • OAuth tokens — the access and refresh tokens Google issues so we can carry out the actions above at the time you scheduled them.

The youtube.force-ssl scope is used for exactly one purpose: posting the optional "first comment" you write in Dispatchr to your own video after it publishes. Dispatchr does not read, moderate, hide, or delete comments from your viewers, does not delete or alter your existing videos, and does not access videos or channels that you did not connect to the Service.

How Dispatchr uses Google user data

We use Google user data solely to provide and improve the user-facing features you asked for:

  • Your Google account identifier, email address, name, and profile picture are used to create and authenticate your Dispatchr account, to identify you inside your workspace, and to send you service-related email.
  • Channel information is used to let you select a destination channel and to display which channel a post belongs to.
  • The title, description, tags, category, privacy status, video file, and optional first comment you enter are used to publish that content to your channel at the time you scheduled.
  • Video statistics are used to display analytics for your own published content, and to power optional, user-initiated performance insights about your own posts.
  • OAuth tokens are used only to authenticate these API calls to Google on your behalf.

We do not use Google user data for advertising of any kind, for profiling, for credit or lending decisions, for surveillance or tracking, to build or enrich independent databases, or for any purpose unrelated to the features described above.

Who we share, transfer, or disclose Google user data to

We do not sell Google user data, and we do not transfer or disclose it to third parties for any purpose other than providing or improving the features described above. Google user data is disclosed only in these limited circumstances:

  • Back to Google/YouTube — we transmit the content you schedule to the YouTube Data API in order to publish it to your channel.
  • Google Cloud (our infrastructure provider) — Dispatchr's application, database, and media storage are hosted on Google Cloud in the United States, under contractual terms that limit Google Cloud's use of the data to providing hosting services to us.
  • Anthropic (our AI provider) — if, and only if, you invoke an optional AI insight feature on one of your own posts, the caption or description of that post and its numeric engagement metrics (including YouTube view, like, and comment counts) are sent to Anthropic's API to generate the analysis you requested, and the result is returned to you. See the "AI-Powered Features" section for the full limits that apply.
  • Legal requirements — we may disclose data where we are required to do so by law or in response to a valid request from a public authority.
  • With your consent — for any other purpose, only with your explicit consent.

Dispatchr does not transfer Google user data to data brokers, information resellers, advertising networks, or any party that would use it for targeted, personalized, retargeted, or interest-based advertising.

How we protect Google user data

Security procedures are in place to protect the confidentiality of your Google user data:

  • All Google OAuth access and refresh tokens are encrypted at rest in our database using envelope encryption with keys held in a managed key service, separate from the database itself.
  • All data in transit is protected with TLS/HTTPS, and the Service is served under HTTP Strict Transport Security with a strict Content Security Policy.
  • Access to Google user data inside the Service is scoped to your own account and workspace, and is protected by authentication, optional two-factor authentication, CSRF protection, and role-based authorization checks.
  • Administrative access to production systems is restricted to authorized personnel on a least-privilege basis and is audit-logged.
  • We do not allow humans to read your Google user data unless you have given us explicit permission (for example, when you ask our support team to investigate a problem with your account), it is necessary for security purposes such as investigating abuse or a suspected incident, it is required to comply with applicable law, or the data has been aggregated and de-identified so that it is no longer linked to any individual user.

No method of transmission over the Internet or electronic storage is completely secure, so we cannot guarantee absolute security, but we maintain the safeguards above and review them as the Service changes.

How long we keep Google user data, and how to delete it

  • Google OAuth tokens are retained only while your Google account or YouTube channel is connected. When you disconnect, we revoke the token with Google and delete it and the associated channel information from our systems.
  • Cached YouTube video statistics are refreshed or deleted within 30 days, in line with YouTube API data-retention requirements.
  • Account information obtained through Sign in with Google is retained until you delete your Dispatchr account, after which it is deleted.
  • Content you created in Dispatchr is retained until you delete it or delete your account. When a retention period expires, the data is deleted.

You can delete your Google user data at any time, in any of these ways: disconnect the account in Dispatchr under Settings > Accounts; permanently delete your whole Dispatchr account under Settings > Your Data > Delete Account; revoke Dispatchr's access directly at Google Account Permissions; or email us at privacy@dispatchr.social and we will process the request. See also our Data Deletion Instructions.

Limited Use affirmation

Dispatchr'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. Specifically, Dispatchr affirms that:

  • We limit our use of Google user data to providing or improving the user-facing features of Dispatchr that are prominent in the Service's user interface.
  • We do not transfer Google user data to third parties except as necessary to provide or improve those user-facing features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after obtaining your explicit consent.
  • We do not use or transfer Google user data for serving advertisements.
  • We do not allow humans to read Google user data except in the narrow cases described under "How we protect Google user data" above.
  • Dispatchr does not use Google user data — including data obtained from Google Workspace APIs or the YouTube Data API — to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models. Dispatchr does not call Google Workspace APIs. Google user data is never used as AI or ML training data, by us or by our AI provider; it is only ever processed to return a result to you, for your own content, at your own request.

Our use of YouTube API Services is additionally governed by the YouTube Terms of Service, and Google's own handling of your data is described in the Google Privacy Policy.

Information We Collect

Account information

To create and operate your account, we collect your email address, your first and last name, your password in hashed form (if you register with a password), your organization or workspace name, and your timezone. If you register using Sign in with Google, we receive your name, email address, Google account identifier, and profile picture from Google instead of a password.

Connected social media account data

When you connect a third-party social media account (Facebook, Instagram, LinkedIn, TikTok, or YouTube), we collect and store:

  • Your account, channel, or page identifiers and display names
  • The OAuth access and refresh tokens needed to act on your behalf
  • The scopes you granted
  • Engagement metrics for content you published through Dispatchr (such as views, likes, comments, shares, and impressions)

All access and refresh tokens are encrypted at rest. We only access the permissions you explicitly grant during the OAuth authorization flow, and only for the accounts you choose to connect.

Content you create

We store the posts, captions, titles, descriptions, hashtags, comments, templates, campaigns, schedules, and media files you create or upload in Dispatchr, so that we can publish them at the time you choose and so you can revisit them later.

Billing information

Paid subscriptions are processed by Stripe. We receive and store a customer identifier, subscription status, and plan details. We never receive or store your full payment card number.

Usage and diagnostic data

We automatically collect limited technical data when you use the Service, including your IP address, browser type and version, the pages you visit, the time and date of your visit, device identifiers, and error diagnostics. We also retain security records such as login attempts and an audit trail of significant account actions.

How We Use Your Information

We use the information we collect for the following purposes:

  • To provide and maintain the Service — creating and scheduling posts, publishing them to your connected accounts, and showing you analytics for your own content.
  • To manage your account — authenticating you, managing your workspace and team members, and connecting or disconnecting your social accounts.
  • To perform our contract with you — administering subscriptions, billing, and plan entitlements.
  • To communicate with you — sending transactional and service email such as publishing failures, invitations, security alerts, and account notices.
  • To support you — responding to your requests and troubleshooting problems you report.
  • To keep the Service secure and reliable — detecting and preventing abuse, diagnosing errors, and maintaining an audit trail.
  • To improve the Service — understanding aggregate usage so we can fix and refine user-facing features.

We do not use your data, or data from your connected accounts, for advertising, profiling, resale, credit or lending decisions, or to train generalized AI or machine learning models.

How We Share Your Information

We share your information only in the following situations:

  • With service providers (subprocessors): We share data with providers who process it on our behalf under contractual terms that restrict their use of it to providing services to us:
    • Google Cloud — application hosting, database, and media storage
    • Anthropic — AI content generation and analysis (see below)
    • Mailgun — transactional and notification email
    • Stripe — subscription billing and payments
    • Sentry — error monitoring and diagnostics
    • Chatwoot — in-app support chat, if you choose to use it
    • Rybbit Analytics — privacy-focused, cookieless usage analytics
  • With social media platforms: When you schedule or publish content, we transmit that content to the platform you selected (Facebook, Instagram, LinkedIn, TikTok, or YouTube) using the access you granted.
  • With members of your workspace: Content and analytics inside a workspace are visible to the other members you have invited to it, according to their role.
  • For legal reasons: We may disclose information where required by law or in response to a valid request by a public authority.
  • With your consent: For any other purpose, only with your consent.

We do not sell your personal data, and we do not transfer or disclose it to third parties for purposes other than those described in this policy.

Platform-Specific Data Practices

We access and use data from each connected platform as follows:

YouTube (Google)

When you connect a YouTube channel, we access your channel ID and title, upload the videos and metadata you submit, optionally post the first comment you wrote to your own video, and read public view, like, and comment counts for videos you published through Dispatchr. This data is used solely to publish your content and display your own analytics. Full details, including scope-by-scope disclosure and our Limited Use affirmation, are in the "Google User Data" section above.

TikTok

Scopes requested: user.info.basic, video.publish, video.list.

  • What we access: your basic TikTok profile (open ID, display name, avatar) so you can identify the connected account; the ability to post the video and caption you submit directly to your profile; and the view, like, comment, and share counts for videos you published through Dispatchr.
  • How we use it: solely to publish the content you scheduled and to display your own performance analytics. Before publishing we show you a preview and the privacy, comment, duet, and stitch settings you have chosen, and we flag AI-assisted content to TikTok when you mark it as such.
  • Deletion: when you disconnect, we call TikTok's token revocation endpoint and delete the account record and all TikTok data derived from it. We also honor TikTok's authorization.removed webhook, which triggers the same purge if you remove Dispatchr from within TikTok.

LinkedIn

Scopes requested for a personal profile: openid, profile, email, w_member_social. If you connect a company page, we additionally request w_organization_social, r_organization_social, and rw_organization_admin.

  • What we access: your name, email address, and LinkedIn member identifier; the company pages you administer (name and identifier); the ability to publish posts as you or as a page you administer; and aggregate engagement counts on content you published through Dispatchr.
  • How we use it: solely to publish the content you scheduled and to display your own engagement analytics.
  • What we never do: we do not export or transfer LinkedIn member data to you, to your customers, or to any third party; we do not use it to enrich a CRM or any other record; we do not build or display a social feed of other members' activity; and we do not retain other members' profile data. Analytics derived from LinkedIn data are shown only to members of your own workspace who are associated with the connected account.
  • Deletion: LinkedIn publishes no programmatic token-revocation endpoint, so on disconnect we immediately delete the stored access and refresh tokens together with the account record and all LinkedIn data derived from it.

Facebook & Instagram (Meta)

Scopes requested for Facebook: pages_show_list, pages_manage_posts, pages_read_engagement. For Instagram: instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, pages_show_list, pages_read_engagement.

  • What we access: the list of Facebook Pages and connected Instagram professional accounts you manage (name and identifier); the ability to publish the posts, images, videos, and carousels you submit; the ability to add the first comment you wrote to your own post; and insights and engagement metrics (likes, comments, shares, views, impressions, reach) for content you published through Dispatchr.
  • How we use it: solely to publish the content you scheduled and to display your own analytics.
  • Deletion: when you disconnect, we call Meta's permission-revocation endpoint and delete the account record along with all Platform Data derived from it, including the platform post identifiers and cached metrics — not just the account link. We also implement Meta's data deletion callback (which returns a tracking URL and confirmation code) and a separate deauthorization callback, so removing Dispatchr from within Facebook or Instagram triggers the same purge. See our Data Deletion Instructions for step-by-step instructions.

Comments on your content

Some of the permissions above allow creating comments. Dispatchr uses them for one purpose only: posting the optional "first comment" that you wrote in Dispatchr to your own post or video. Dispatchr does not read, store, analyze, moderate, hide, or delete comments written by your viewers on any platform. The only comment-related data we retain is the aggregate comment count shown in your analytics, and the text of the first comment you authored yourself.

AI-Powered Features

Dispatchr offers optional AI-assisted features such as caption and hashtag generation, content suggestions, quality scoring, and performance analysis of your own posts. To provide a feature you invoke, we send the relevant content and the numeric engagement metrics for your own posts to our AI provider, Anthropic, for processing, and return the result to you. The following limits always apply:

  • AI processing happens only when you invoke an AI feature. It is never applied in the background to your connected account data.
  • AI features operate only on your own content and your own account's metrics — never on another user's content. Other platform members' content is never used as input to generate anything, and comments written by your viewers are never sent to our AI provider.
  • We do not use your content, your account data, or any data obtained from connected platforms — including Google and YouTube user data — to develop, improve, or train generalized, non-personalized AI or machine learning models.
  • Our AI provider does not train its models on data submitted through its API, and processes the data only to return the requested result to us.
  • We do not send your OAuth tokens, passwords, payment details, or other credentials to our AI provider.
  • AI-assisted features are clearly identified as AI in the interface, and their output is presented to you as an editable suggestion. You review and can edit every suggestion before anything is published. Dispatchr never auto-publishes AI-generated content that you have not reviewed, and where a platform requires it we flag AI-assisted content to that platform.

Data Retention and Deletion

We retain personal data only for as long as necessary to provide the Service and to fulfill the purposes described in this policy, unless a longer retention period is required or permitted by law. When the retention period for a given type of data expires, we delete it. Specifically:

  • Account data is retained until you delete your account.
  • Social media access and refresh tokens, including Google and YouTube tokens, are deleted from our systems when you disconnect an account or delete your Dispatchr account. Where the platform provides a revocation endpoint (Google, Meta, and TikTok) we also revoke the token upstream so the grant disappears from your connected-apps list. LinkedIn publishes no such endpoint, so for LinkedIn the mechanism is immediate local deletion.
  • Data derived from a connected account — the account record, the platform post identifiers, and the cached engagement metrics — is deleted when you disconnect that account, not merely unlinked.
  • Posts, content, templates, and media you create are retained until you delete them or delete your account.
  • Engagement metrics retrieved from connected platforms (such as views, likes, comments, and shares) are cached to power your analytics and are refreshed or deleted within 30 days, in line with platform data-retention requirements.
  • Audit logs are retained for up to 12 months for security purposes.
  • Login attempt records are retained for 30 days.
  • Billing records are retained for as long as required by tax and accounting law.

Deleting your data

You may delete your data at any time. You can permanently delete your account and all associated data from Settings > Your Data > Delete Account. This is irreversible and removes your personal data, posts, content, templates, connected account records, and activity history. You can also email privacy@dispatchr.social to request deletion, and we will process the request promptly. If you connected via Facebook or Instagram, you can also initiate deletion through Facebook under Settings & Privacy > Settings > Apps and Websites; we issue a confirmation code so you can track the status of such a request.

Revoking platform access

You can disconnect any connected account at any time under Settings > Accounts. You can also revoke access directly from each platform:

  • Google / YouTube: Visit Google Account Permissions
  • Facebook / Instagram: Settings & Privacy > Settings > Apps and Websites
  • LinkedIn: Settings > Data Privacy > Third-party connections
  • TikTok: Settings and Privacy > Security and Permissions > Manage App Permissions

When you disconnect or revoke access, we delete the stored tokens, the account record, and the data derived from that account (platform post identifiers and cached metrics) from our systems, and — where the platform provides a revocation endpoint — revoke the token upstream. For full details, see our Data Deletion Instructions.

Security of Your Data

Security procedures are in place to protect the confidentiality of your data. We encrypt OAuth tokens and other sensitive fields at rest using envelope encryption with keys held in a managed key service; we protect all data in transit with TLS/HTTPS under HTTP Strict Transport Security; we enforce a strict Content Security Policy, CSRF protection, and secure session cookies; we offer two-factor authentication and passkeys; we scope every request to your own account and workspace with role-based authorization; and we restrict and audit-log administrative access to production systems on a least-privilege basis.

No method of transmission over the Internet or method of electronic storage is 100% secure, so while we use commercially acceptable means to protect your personal data we cannot guarantee its absolute security. If we become aware of a breach affecting your personal data, we will notify you and the relevant authorities as required by applicable law.

Cookies and Tracking

We use cookies and similar technologies. Strictly necessary cookies power authentication, session management, and security (including CSRF protection) and are always active. Beyond those, we use a small number of non-essential technologies only with your consent:

  • Analytics — Rybbit Analytics, a privacy-focused, cookieless analytics service, to understand aggregate usage. Loaded only after you grant the "analytics" category.
  • Functional — the Chatwoot chat widget, which sets a conversation cookie so we can support you. Loaded only after you grant the "functional" category.

On your first visit we present a consent banner where you can accept or decline each non-essential category; visitors in the EU/UK are asked to opt in, and you can change your choices at any time. You can also instruct your browser to refuse cookies. We do not use advertising or cross-site tracking cookies.

Your Privacy Rights

Depending on where you live, you may have some or all of the following rights over your personal data. Residents of the European Economic Area and the United Kingdom have these rights under the GDPR and UK GDPR:

  • Right of access: You can download a complete copy of your personal data at any time from Settings > Your Data > Export.
  • Right to rectification: You can update your personal information through your account settings.
  • Right to erasure: You can permanently delete your account and all associated data from Settings > Your Data > Delete Account.
  • Right to data portability: Your data export is provided in machine-readable JSON format.
  • Right to object or restrict: You may contact us to object to or request restriction of processing of your personal data.
  • Right to withdraw consent: Where we rely on consent, you can withdraw it at any time, including by changing your cookie choices or disconnecting a social account.
  • Right to complain: You may lodge a complaint with your local data protection authority.

If you are a California resident, the CCPA/CPRA grants you the right to know what personal information is collected, to request its deletion, to request correction, and to opt out of the sale or sharing of personal information. We do not sell or share personal information, so there is nothing to opt out of, and we will not discriminate against you for exercising your rights.

You can exercise your access and deletion rights directly in your account settings, or by contacting us at privacy@dispatchr.social. We respond to verified requests within the timeframes required by applicable law.

Legal Bases for Processing (EEA/UK)

Where the GDPR applies, we rely on the following legal bases: performance of a contract (to provide the Service you signed up for, including publishing your content and billing you); consent (for non-essential cookies, optional integrations such as connecting a Google or YouTube account, and optional AI features); legitimate interests (to keep the Service secure, prevent abuse, and diagnose errors); and compliance with legal obligations (such as tax and accounting record-keeping).

International Data Transfers

Dispatchr is operated from the United States, and your information is processed and stored on servers located in the United States. Our subprocessors may also process data in the United States or other countries.

If you access the Service from the European Economic Area, the United Kingdom, or other regions with laws governing data transfers, your personal data may be transferred to and processed in a country whose data-protection laws differ from those of your jurisdiction. Where required, we rely on appropriate safeguards for such transfers, including the European Commission's Standard Contractual Clauses. By using the Service, you acknowledge this transfer, storage, and processing.

Children's Privacy

The Service is not directed to anyone under the age of 13, and we do not knowingly collect personal data from anyone under 13. If you are a parent or guardian and believe your child has provided us with personal data, please contact us and we will delete it.

Third-Party Links

The Service may contain links to third-party websites and social media platforms that we do not operate. We have no control over, and assume no responsibility for, the content, privacy policies, or practices of any third-party site or service. We encourage you to review the privacy policy of every site you visit.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will post the updated policy on this page and revise the "Effective Date" above. If we change how Dispatchr uses Google user data, or make any other material change to how we handle your data, we will notify you — for example by email or by an in-product notice — before or when the change takes effect.

We encourage you to review this policy periodically. Changes are effective when posted on this page.

Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, contact us:

Dispatchr is operated by Corey Alan Consulting, United States, which is the data controller for the personal data described in this policy.