DispatchSocial publishing & comment automation

Privacy Policy

Effective 12 November 2026

Dispatch is a social-media publishing and comment-automation tool operated by Dheeraj Properties, a sole proprietorship of Dheeraj Raikwar in Jabalpur, Madhya Pradesh, India ("we", "us"). It lets businesses schedule content to connected accounts, including Facebook Pages, Instagram professional accounts, Threads and, when enabled, X accounts and YouTube channels. Comment and message automation is available for supported Facebook and Instagram accounts. This policy explains what data Dispatch handles and why.

Data we collect

  • Account data. Your name, email address and a salted hash of your password (we never store the password itself), plus workspace and team-membership records. Google sign-in also supplies your Google account identifier and, when available, your profile photo URL.
  • Content you create. Posts, captions, media files and automation rules you set up in your workspace.
  • Data from Meta Platforms (Platform Data). When you connect a Facebook Page or Instagram professional account, we receive and store: the Page and Instagram account IDs and names, access tokens, the posts Dispatch publishes for you, and — for accounts with automation enabled — comment and message events on your connected accounts, including the commenter's ID, name and comment text as delivered by Meta's webhooks.
  • Data from Threads (Platform Data). With your permission, we verify and store your Threads account ID and username, encrypted access token, granted permissions, token expiry and data-access expiry when returned. We also store identifiers, processing and publishing results, and available links for posts you publish through Dispatch.
  • Messages and files sent to your WhatsApp number. When you connect a WhatsApp Business number, the messages people send to it are stored for your team inbox. A photo, video, voice note, document or sticker they send is fetched from Meta when it arrives and a copy is kept in our storage so your team can open it; a shared location or contact card is kept as text.
  • Interaction data. When someone replies to an automated message or taps a WhatsApp link Dispatch sent on your behalf, we record that event so your workspace can measure its own campaigns.
  • Data from X. When you authorize X, we store your account ID, name, username, encrypted access and refresh tokens, expiry and granted permissions. We send the posts and media you select to X and store publishing identifiers and results. We do not use this connection for automated replies or reading your inbox.
  • Data from YouTube. Connecting YouTube is separate from signing in with Google. With your permission, we receive your channel ID, name and handle, access and refresh tokens, and identifiers and processing results for videos you upload through Dispatch. We store the title, description, visibility, audience and altered-content choices you supply for each upload.

How we use it

  • To publish the content you schedule, at the time you schedule it.
  • To send the automated comment replies and direct messages that your workspace has explicitly configured.
  • To show your workspace its own engagement statistics.
  • When you request a poster, to generate its artwork, caption and hashtags from your selected photos, project information and brief. Results are saved as drafts for review.

We do not sell personal data, use it for advertising, build profiles for any purpose beyond the features above, or share it with third parties except the service providers listed below.

Where it lives

  • Application hosting: Fly.io (Singapore region).
  • Database: Supabase (AWS ap-southeast-1, Singapore). Access tokens are stored encrypted (AES-256-GCM envelope encryption); row-level security isolates each workspace's data.
  • Media and encrypted nightly database backups: Cloudflare R2 (Asia-Pacific). The backup process prunes dated recovery copies older than 30 days after a successful backup; failures can delay that rotation. New database backups exclude stored YouTube provider data. Older recovery copies may still contain that data and are included in the YouTube deletion requirements below.

These hosting providers are bound by their own data-processing terms.

When you request AI poster generation, we send the selected campus photos, the project's logo if available, public project or selected listing details, your brief and chosen language to OpenAI. Owner-contact fields and internal property notes are excluded from these requests. Do not place private information in photo labels or the generation brief. Generation history and uploaded reference photos remain with your workspace; reference photos are separate from published-post media retention.

Platform Data from Meta

Dispatch uses Meta's Graph API under Meta's Platform Terms and Developer Policies. Platform Data is used only to provide the features described above to the workspace that owns the connected account, is never sold or transferred to data brokers, and is deleted as described on our Data Deletion page when you ask us to or when Meta requires it. Disconnecting Threads removes its stored credentials; account identity and publishing history remain subject to the retention and deletion rules below.

X account access

We use your X authorization to identify your account, upload selected media and publish posts at your direction. You can disconnect X in Channels to remove stored credentials and stop future Dispatch posts. You can also revoke Dispatch in X settings under connected apps. Disconnecting does not delete published posts on X. Account identity and publishing history follow the retention and deletion rules in this policy.

YouTube API Services

Dispatch uses YouTube API Services to identify the channel you authorize, upload your selected videos, and check their upload and processing results. The video and metadata you approve are sent to Google/YouTube when you publish or schedule an upload. Your authorized workspace team can access this information in Dispatch. YouTube data is not sent to our AI poster service or used to train AI models. Google handles information under its Privacy Policy.

In Channels, choose Disconnect and revoke Google access to stop new uploads and request removal of Dispatch's Google authorization. Google may also remove other Dispatch permissions granted by that Google account, including Google sign-in consent. If an upload is already active, cleanup waits for its worker to finish. If Google does not confirm revocation, we keep encrypted credentials only to retry that request and erase the saved provider data within six days of your request, once any active worker has finished. You can also remove Dispatch directly through Google's security settings; do this if Dispatch reports that Google revocation could not be confirmed. Your original uploaded files, authored drafts and local publishing history remain until you delete them or the applicable retention period ends. Disconnecting Dispatch does not delete videos on YouTube; manage those in YouTube Studio.

We periodically check YouTube authorization and refresh channel details. Stored YouTube upload identifiers and session records are removed within 30 days; historical Dispatch publishing records may therefore no longer include a YouTube link. If you request deletion of YouTube data by emailing dheeraj.raikwar224@gmail.com, we remove it as soon as possible and within seven calendar days. That deadline also applies to a request to delete your entire workspace and to copies of YouTube provider data in older backups; ordinary backup rotation does not extend it.

Dispatch's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use this information to provide the Google sign-in and YouTube features described here, not to target advertisements or train generalized AI models.

Browser storage

Dispatch uses session cookies to keep you signed in, short-lived cookies to protect account connection flows, and browser storage for interface preferences. We do not embed the YouTube player or serve third-party advertisements in the YouTube connection and publishing screens.

Retention

We keep data while your workspace is active. Free and trial workspaces retain saved media until the user removes it, within the shared 1 GB storage allowance. New uploads are blocked when that allowance is full. Other workspaces retain media according to their configured policy: media attached to a post is deleted from our storage 7 days after the post is published (some workspaces are configured with a longer window, shown on their Published page). After a downgrade, media published under the paid plan is deleted 30 days later. The post's text and history remain. A file a customer sends to a connected WhatsApp number is deleted from our storage 180 days after it arrives, and is deleted when the workspace deletes that conversation or contact; the text of the message remains with the conversation. Disconnecting a channel stops new Dispatch activity for it and removes stored credentials; YouTube revocation and any active uploads follow the process described above. Deleting your workspace, or asking us to, removes stored YouTube provider data as soon as possible and within seven calendar days, including when you request deletion of your entire workspace. Other workspace data is removed from the live database within 30 days; recovery copies follow the backup rules described above.

Your rights

You can ask us to access, correct, export or delete personal data we hold about you by writing to dheeraj.raikwar224@gmail.com. If you interacted with a business that uses Dispatch and want your data removed, the Data Deletion page explains how.

Changes

If this policy changes materially we will update this page and its effective date.

Privacy Policy · Data Deletion · Terms of Service
Questions: dheeraj.raikwar224@gmail.com