Skip to content
FanCue
FeaturesHow it worksSafetyFAQRequest access

Privacy policy · Effective July 2, 2026

Clear about the data behind the conversation.

FanCue processes creator-workspace and connected-account information to prioritize comments, prepare human-approved replies, coordinate teams, and operate the service.

AdvertisingNo third-party ad tracking
Data saleFanCue does not sell personal data
Public repliesHuman approval is required
On this pageOverviewData we processConnected accountsAI featuresHow data is usedSharingRetention & deletionSecurityContact

01 · Overview

What this policy covers

This policy describes information processed by FanCue, a product operated by Omnia Data Analytics LLC. FanCue is currently in development and early evaluation, with an iPhone and iPad app, a browser experience, and backend services that support creator-engagement workflows.

FanCue uses connected-account data to provide the workspace’s requested functionality. It does not track people across unrelated apps or websites for advertising.

02 · Information

Data we process

Contact information

Email addresses and information you provide for account operation, support, product inquiries, privacy requests, or App Review.

User and workspace content

Connected social comments, post context, reply drafts, approved replies, campaigns, brand-voice examples, knowledge-base entries, workspace offerings, assignments, and internal notes.

Identifiers and connection data

User and workspace IDs, connected social-account IDs, provider post and comment IDs, device push tokens, OAuth state, and the encrypted provider credentials needed to maintain an authorized connection.

Usage, audit, and diagnostics

Feature events, workflow status, approval and moderation records, audit logs, account health, provider sync state, job results, API errors, performance data, and operational diagnostics used to run, secure, and support FanCue.

Information FanCue does not request for its current product

  • Precise location, contacts, browsing history, or financial information
  • Health or medical records
  • Social-network passwords
  • Advertising identifiers for cross-app tracking

03 · Connections

Connected social accounts

FanCue uses official provider authorization flows. The current connected-account implementation includes YouTube read-only comment and recent-upload sync. Instagram and Facebook authorization and connector work may be limited by configuration, provider approval, and platform capabilities.

Provider tokens are treated as credentials. The current backend encrypts stored access and refresh token values using authenticated encryption and records only a token fingerprint for comparison. Tokens are used to sync authorized data and perform a workspace-approved provider action only when that action is implemented, enabled, and allowed.

Disconnecting an account marks the connection as disconnected and begins the applicable cached-data cleanup workflow. The product also tracks reconnect needs without asking for the provider password.

04 · AI

AI-assisted features

FanCue can classify comment intent, summarize the comment and original-post context, prepare reply suggestions, and rewrite a draft for a selected tone. Relevant comment, post, brand-voice, knowledge-base, and workspace-offering context may be processed to produce these results.

AI results are suggestions and can be inaccurate. The current product requires human approval for public reply drafts. Live public posting is disabled by default, and the workspace remains responsible for reviewing accuracy, tone, and appropriateness.

05 · Purpose

How information is used

  • Provide the inbox, priority classification, comment context, reply, campaign, insights, team, and notification features
  • Connect and maintain authorized social accounts
  • Enforce roles, workspace boundaries, provider capabilities, approval requirements, and automation safeguards
  • Prepare support, audit, compliance-export, deletion-report, reconnect, and operational-readiness workflows
  • Secure, debug, monitor, and improve FanCue
  • Respond to product, support, legal, and privacy requests

FanCue does not sell personal data and does not use workspace content for third-party advertising tracking.

06 · Service providers

When information is shared

Information may be processed by service providers that help operate FanCue, such as cloud infrastructure, databases, AI services, diagnostics, and notification delivery. Connected social platforms receive only the requests required for the authorization, sync, moderation, or reply action the workspace initiates and the platform permits.

Information may also be disclosed when required by law, to protect the security and integrity of FanCue or its users, or as part of a business transaction subject to appropriate safeguards.

07 · Notifications

Notification preferences

Push notifications are optional. Workspaces can configure categories such as questions, purchase intent, brand risk, assignments, and reconnect alerts, along with quiet hours. The product is designed to exclude full comment text from push payloads unless a workspace opts in.

08 · Control

Retention, export, disconnect, and deletion

FanCue retains information for as long as needed to provide the workspace, maintain security and audit evidence, satisfy legal obligations, and resolve disputes. Retention can vary by record type and workspace policy.

The current backend includes workspace-scoped compliance export and non-destructive deletion-report workflows, disconnected-account cleanup fields, AI metadata retention fields, and retention-event records. A deletion report previews scope and exceptions before destructive work is performed.

You can request access, export, correction, disconnect, or deletion assistance by emailing info@omniadataanalytics.com. Include the workspace or account email connected to the request so it can be verified and routed safely.

09 · Safeguards

Security and workspace boundaries

Current safeguards include encrypted provider-token fields, OAuth state expiry and replay protection, workspace-scoped records, role and permission checks, audit logs, provider-capability checks, automation dry runs, human-approval fields, and idempotency controls intended to prevent duplicate reply dispatch.

No service can guarantee absolute security. Please do not email passwords, provider access tokens, authorization codes, recovery codes, or other secrets to FanCue support.

10 · Updates & contact

Questions or requests

This policy may be updated as FanCue, provider APIs, and legal requirements evolve. Material changes will be reflected by updating the effective date or providing another appropriate notice.

FanCue is operated by Omnia Data Analytics LLC in Phoenix, Arizona. Email info@omniadataanalytics.com for privacy questions or requests.

FanCue

Creator engagement, cued up.

ProductFeaturesPreviewFAQ
CompanyAboutNewsContact
CareSupportPrivacyTerms
© 2026 Omnia Data Analytics LLCinfo@omniadataanalytics.com