Privacy Policy

Agentic Force LLC, based in Ulaanbaatar, Mongolia ("we", "us"), operates agenticforce.tech and the Agentic Force AI agent services. This policy covers accounts, connected business tools and the optional AgenticForce Page Automation feature.

Available tools depend on your account and authorized workspace. Creating an account does not automatically grant access to a workspace or its connected services. Questions and data requests can be sent to aimongoliatushig@gmail.com.

Google sign-in uses your basic Google profile and email address to identify your account. Connecting Google Workspace is a separate authorization and requires your explicit consent.

Depending on the tools you authorize, Workspace access can include:

• Gmail: reading, sending and modifying messages.
• Google Calendar: working with calendars and events.
• Google Drive, Docs and Sheets: accessing and working with files, documents and spreadsheets.
• Google Contacts: reading basic contact information.

We use this access only to carry out the specific actions you ask your agent to perform, such as summarizing unread emails, scheduling a meeting or creating a document. We do not sell Google user data or use it for advertising. Where your request needs an AI response, only the data needed for that request is included.

Google Limited Use disclosure: Agentic Force'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.

Disconnect the Google connector in your workspace to remove its saved live credential. You can also revoke the authorization in your Google Account permissions. Disconnection does not automatically erase previously processed content, history or backup copies. Use our data deletion instructions to request their removal.

• Account and workspace information needed to identify you and control access.
• Conversation history and files you provide so an agent can carry out your request and maintain context.
• Data from business tools you choose to connect, such as Notion, Linear, Airtable or Odoo, and messaging services such as Telegram.
• Brand information, content drafts, uploaded or generated media, schedules, approval records and operational records needed to run your selected workflows.

The specific data depends on the connected service and the actions you authorize. A connection to one service does not grant access to all of your other accounts.

Facebook Page Automation is an optional feature being prepared for Meta App Review. When a connection is enabled and you authorize it, the Page publishing workflow lets you select a Page you manage and prepare photos or Reels for publication after human approval.

Permissions and their purpose

• pages_show_list: find the Pages you manage so you can choose the Page to connect.
• pages_read_engagement: access Page information needed for the Page publishing permission and workflow. This feature does not collect follower profiles or audience lists.
• pages_manage_posts: publish approved content on your selected Page. Although Meta's permission also permits editing or deleting posts, those operations are not currently offered by this publishing workflow.

Meta may also include public_profile in login authorization. The app configuration currently includes business_management and pages_manage_metadata; the Page publishing workflow does not currently use them for general business-asset administration or Page webhook processing. A permission appearing in Meta's configuration does not mean that every user has granted it or that every permitted data type is collected.

Data used when a Page is connected

• Page ID, Page name and the Page management tasks available to the person connecting it.
• A Page access token that allows the service to act within the permissions you grant.
• Content you supply or approve, media, publication schedules and approval history.
• Meta post or video IDs, publishing status, timestamps and operational error or audit records.

The current Page Automation workflow does not read Messenger conversations, Page comments, follower lists or advertising accounts. Page insights collection is not currently implemented. Other messaging integrations, if separately connected, are distinct from this feature.

We use Page data to identify the selected Page, check publishing access, publish the approved content and report the outcome. AI can prepare drafts from information you supply; a human must approve the final content package before this workflow publishes it. Stored Facebook access tokens are not included in AI prompts.

We use information to provide your requested services, maintain access controls, process approved actions, troubleshoot failures and respond to support or deletion requests. We do not sell or rent your data.

Information is shared with service providers where needed to deliver the function you request: hosting and account services, AI providers such as OpenAI when AI generation is enabled, and the connected services you authorize. Only the information needed for the request is sent to the relevant provider. Approved Page posts and media are sent to Meta for publication under the Page's Facebook settings.

Authorized administrators may access information to operate and support the service. Providers process information under their own applicable terms and privacy policies. Provider infrastructure may be outside Mongolia.

We use infrastructure we operate and configured service providers. Access to protected workspaces requires an authorized account. Access controls limit service and administrative access; public website connections and Meta API calls use HTTPS.

In Marketing OS Page Automation, saved Page tokens are encrypted server-side and excluded from normal application responses. Workspace access is checked before operations, and OAuth connections use expiring authorization state.

Google Workspace credentials are stored server-side with restricted file permissions. Authorized service processes and administrators may access credentials to provide or support a connection. These controls are not a claim that all stored data, every backup or every internal connection is encrypted. No security measure eliminates every risk.

We retain operational information to provide the service and maintain its records. There is no single automatic deletion period covering all data types. Disconnection stops use of a connection and removes or clears its live credentials; it is different from deleting information already stored.

For Page Automation, disconnecting a Page clears its saved access token. Page identifiers, drafts, media, publication and approval records, and audit records may remain. Request deletion through our public data deletion instructions.

Deletion requests are handled by an operator after verifying the requester's authority. The request must also address relevant backup copies and restricted records; we do not promise immediate erasure from every backup. If a record must be retained for an applicable legal obligation or a specific security need, we will explain what remains and why. Ask us to confirm the completed scope and any remaining records.

Deleting our stored copies does not itself delete posts already published on Facebook or information held independently by Google, Meta or another connected provider. You can manage those records directly with that provider.

You can decline a connection, revoke provider access, ask about the information we hold, request a correction or request deletion. Contact aimongoliatushig@gmail.com. Please identify your account, workspace or Page and describe your request. Do not send passwords, access tokens, API keys or unnecessary identity documents.

For steps, what to include and how to distinguish revocation from deletion, see Data deletion instructions.

We update this policy when our services or data practices change and show the revision date above. A new connection or new purpose requiring authorization must be explained before that authorization is requested.