Privacy Policy

Information the application accesses

Social AutoPilot accesses information only after you sign in and explicitly connect a supported platform account. Access is limited to the permissions you grant during OAuth authorization. The application does not access your connected accounts without an active authorization you initiated.

Instagram account and profile information

When you connect an Instagram account, Social AutoPilot may receive profile and account identifiers authorized by you, such as your Instagram user ID, username, and display name. This information is used to identify the connected account inside Social AutoPilot and to operate connector features you enable.

Instagram owned media information

With your authorization, Social AutoPilot may read metadata about media you own on Instagram, such as media identifiers, media type, timestamps, permalinks, and comment counts. This supports account verification, sync operations, and coach features tied to your content.

Instagram comments

If you grant comment-related permissions and enable comment access, Social AutoPilot may read top-level comments on your owned media, including comment identifiers, comment text, commenter identifiers, and timestamps. Ingested comments may be stored to power inbox, coaching, and relationship features inside the application.

Comment read access depends on the permissions you approve and the features enabled in your deployment. If comment access is not authorized or not enabled, Social AutoPilot does not ingest comments from Instagram.

OAuth credentials and tokens

Platform OAuth tokens and refresh credentials are stored server-side in encrypted form. Tokens are used only to perform authorized connector operations on your behalf. Social AutoPilot does not display access tokens or refresh tokens in the user interface.

How information is used

Social AutoPilot uses authorized platform information to:

• maintain connected account status and capabilities;
• ingest supported activity you authorize (such as comments on owned media);
• power inbox, coaching, relationship memory, and audit features within the application;
• generate recommendations and drafts in Coach Mode under your supervision.

V1 defaults to Coach Mode. Autonomous outbound posting, liking, reposting, and similar actions are not enabled unless explicitly configured in a later milestone.

Semantic AI classification (when explicitly enabled)

When live semantic AI is explicitly enabled in a deployment, Social AutoPilot may send bounded social comment and post context text to an AI service provider (such as OpenAI) solely to classify comment intent for attention assistance. The provider acts as a third-party service/subprocessor for that classification step.

• Only bounded comment text and minimal aggregate context are sent. Identifiers, handles, OAuth tokens, credentials, and internal database IDs are not intentionally included in classifier inputs.
• Derived classifications, confidence scores, and related audit metadata may be stored inside Social AutoPilot to support scoring and coaching features.
• Personal information is not sold. Provider handling of submitted data is subject to the applicable provider terms and policies for the configuration your deployment operator uses.

Live semantic AI is off by default. Normal operation uses a deterministic mock classifier unless all required enablement settings are configured by the deployment operator.

Supervised Instagram comment replies (when explicitly enabled)

When supervised live reply is explicitly enabled by the deployment operator, Social AutoPilot may send an Instagram comment reply only after you review and approve the exact reply text inside the application. Approved reply text is retained as an immutable snapshot until send completes or the approval expires.

• Confirmed sent replies are stored as outbound conversation records (comment reply events) separate from inbound comments.
• Send attempts store sanitized operational metadata only — not OAuth tokens, raw Meta responses, or credentials.
• On explicit send, Meta receives the approved reply text under the permissions you granted. This is not autonomous outbound activity; each send requires separate human approval and an explicit send action.

Supervised live reply is off by default. V1 Coach Mode does not enable autonomous posting, liking, or reposting.

Data retention

Social AutoPilot retains information needed to operate connected-account features, including encrypted OAuth credentials while an account remains connected, ingested platform events (such as comments), relationship records derived from ingested activity, audit logs, and application configuration data.

Retention continues until you disconnect a connected account, request deletion, or the deployment operator removes stored data according to deployment policy.

User-requested deletion

You may disconnect connected accounts at any time from the Accounts page while signed in. Disconnecting removes stored OAuth tokens for that connection in Social AutoPilot.

To request deletion of other Social AutoPilot-stored data associated with your connected accounts, follow the instructions on the Data Deletion page.

Third-party and platform data

Information from Instagram and other connected platforms is provided by those platforms under the permissions you grant. Social AutoPilot processes that information to deliver its features. Platform providers maintain their own terms and privacy policies governing data on their services.

You may also revoke Social AutoPilot's access through your Instagram or Meta account settings.

Sharing and sale of personal information

Social AutoPilot does not sell personal information. Social AutoPilot is not designed to share your personal information with third parties for their independent marketing purposes.

Authorized platform APIs and infrastructure providers (such as hosting or database services used by your deployment) may process data solely as needed to operate the application you use.

Security

Social AutoPilot stores platform tokens using server-side encryption, restricts connector credentials to server-side use, and requires authentication to access the command center. No security measure is perfect; the deployment operator is responsible for securing the environment where Social AutoPilot runs.

Changes to this policy

This policy may be updated as Social AutoPilot features evolve. The "Last updated" date at the top of this page will change when revisions are published.

Contact

For privacy questions or data requests related to Social AutoPilot, contact the administrator of the Social AutoPilot deployment you authorized. If you operate your own instance, you are that administrator.

For deletion requests, see Data Deletion.