How OjasPilot connects to business services
OjasPilot uses the supported authorization flow offered by a connected service. You choose to connect an eligible account and grant the permissions needed for the features you want to use.
OjasPilot does not ask you to type your Facebook or Instagram password into OjasPilot. Authentication and permission approval occur through the connected platform's supported authorization process.
Current Meta and Instagram integration
OjasPilot's current social workflow is designed for eligible Instagram Professional accounts and related Meta business assets. The exact accounts, metadata and publishing capabilities available to OjasPilot depend on the permissions you grant, account eligibility and the platform APIs available at the time.
Connecting an account does not mean OjasPilot can perform every possible action on that platform. OjasPilot can only use the capabilities made available through the authorized integration and enabled inside your workspace.
What connected data OjasPilot may receive
Depending on the connected service and granted permissions, OjasPilot may receive account identifiers, profile or business metadata, authorization status, permission state, media or publishing information, and other data needed to operate the selected workflow.
OjasPilot uses connected-account information to support the workspace that authorized the connection. For more information about broader data handling, see the Privacy Policy.
Account sync is separate from AI generation
Connecting or synchronizing an account does not by itself create a new AI-generated post. OjasPilot is designed so that AI generation is tied to an explicit Generate or Regenerate action rather than routine page loads, approvals, scheduling or account sync.
When generation is requested, OjasPilot can use relevant business context and supported connected-account context to prepare the requested work.
Review, approval and publishing
OjasPilot supports review and approval before publishing. Manual approval can be used so prepared content waits for a business decision. Where auto-approval is enabled, it applies to explicitly generated work and does not create new content on its own.
The publishing scheduler is intended to publish work that has already been generated, approved and scheduled. It does not generate new posts simply because a publishing time arrives.
Disconnecting an integration
Disconnecting a supported integration prevents OjasPilot from using that connection for future actions. Connection credentials and secrets are handled separately from normal business content and are removed or revoked according to the disconnect flow and the connected platform's capabilities.
If the external platform also provides its own app-permission controls, you can use those controls to revoke access from that platform as well.
Data deletion and retention
Workspace owners can request full workspace deletion through OjasPilot Settings using the product's verified deletion-request flow. This helps prevent accidental deletion of a complete business workspace.
For privacy, deletion or connected-account data questions, contact hello@ojasyukti.tech. See the Privacy Policy retention and deletion section for additional context.
Workspace isolation
OjasPilot is designed as a multi-tenant product. Business context, connected-account data and workflow activity belong to the workspace that owns them and are not intended to be shared with another customer workspace.
Future integrations
OjasPilot is designed to support additional business workflows over time. New integrations should follow the same principles: explicit authorization, limited permissions, visible workflow state, reviewable actions and clear disconnect controls.
Questions about an integration? Visit Contact Us or email hello@ojasyukti.tech.