Your connected-account data.

Information used by Lion AI

• Google identity: a verified Google account identifier, email address and profile name, used for sign-in and workspace authorization.
• Workspace records: client name, timezone, membership, role and the account or property you select.
• Connection credentials: platform access tokens and, when issued, refresh tokens, used server-side for the account connection.
• Reports: advertising account and campaign identifiers, names, status, spending, impressions, clicks and available conversion metrics; aggregate Analytics traffic and key events; and Search Console query metrics.
• Lion Chat: your private conversation messages, saved tool evidence, explicit client memory and reviewed action proposals. Private transcripts belong to their login; client-shared memory is visible to authorized members of that workspace.
• Social Lion: the organization and explicitly selected social-channel identifiers, calendar post content, states, timestamps, platform settings, media-library references, proposed posts and execution receipts from your connected Social Lion organization.
• Operational records: report retrieval times, connection health, workspace activity and technical information needed to operate and protect the service.

The current reporting connector does not collect individual Meta lead-form submissions, customer contact lists or private messages.

Purpose and access

We use connected data to provide the reports and client services requested through Lion AI, operate account connections, diagnose measurement and delivery issues, and prepare reviewed recommendations. Access is limited by the user's workspace memberships and explicit SEM Lion administration.

Google sign-in requests identity information only. Platform connections request additional permissions separately. Google Ads requires its management-capable advertising permission even though the public connector currently performs reporting reads. Analytics and Search Console request reporting access. Meta requests ads_read; a provider token may retain permissions previously granted to the same Meta app. The reporting connector uses fixed reporting calls. Separately configured campaign management requires its own valid platform access and an exact human review before execution.

You choose the account or property after platform consent. A provider login or account list does not automatically connect every account you can access.

Social Lion connections and posting

Social Lion is SEM Lion’s operated Postiz instance at postiz.goask.online. A client separately authorizes its dedicated Social Lion organization and explicitly selects channels for Lion AI. The native OAuth grant permits organization-level management; Lion AI enforces selected-channel access and exact human review before saving a draft, scheduling or publishing. The global operator’s MCP connection and unrelated organizations are not inherited. We use the structured MCP tools that also power Social Lion’s agent; Lion Chat does not delegate arbitrary prompts to that autonomous agent.

Authorized workspace members can read the connected social data. Posting proposals and execution require a workspace owner or SEM Lion administrator. Approved posts and media references are sent through Social Lion to the selected social platform for the requested action. Selected social evidence can be included in your OpenAI chat context when needed to answer your question.

Disconnecting Social Lion stops Lion AI access but does not remove or cancel posts and schedules already stored in Social Lion. Revoke its app grant under Social Lion’s Approved Apps if you want to remove native authorization. Historical chat evidence remains subject to the chat deletion controls below.

Providers and optional AI reviews

Google and Meta process the authorization and API requests needed for their connected products. SEM Lion's hosting infrastructure stores and processes the portal's private application data.

Where SEM Lion enables an optional model-written review and an authorized agency user requests it, pseudonymous campaign metrics and diagnostic evidence are sent to OpenAI. That request excludes real client, campaign and account names and identifiers and does not include the user's full conversation. A page view or ordinary report read does not automatically generate a model request. Generated advice is a proposal for human review.

Lion Chat is separate from those optional review briefs. When you send a chat message, your message, relevant recent conversation text, permitted saved memories and the selected client’s tool evidence are processed by OpenAI to produce the answer. This context can contain the client/account/campaign names and identifiers needed for your question. Credentials and execution-approval tokens are excluded. A page view alone does not send a chat message. The server requests store: false for these API responses; this setting is not a promise that the provider has no operational retention. AssistantCloud and DeepSeek are not part of the current Lion Chat processing path.

We do not sell connected Google or Meta data, use it to target unrelated advertising, or use it to train a general-purpose AI model. Lion AI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Storage, retention and disconnection

Connection grants are encrypted in the private server credential vault. Credentials are not included in browser reports or public release files. Reports, access records and saved recommendations remain associated with their workspace for delivery of the service.

Chat messages, saved memory, titles and action proposals are encrypted in the private server database with a separate application key. The server decrypts authorized content when providing the service; this is not end-to-end encryption against the service operator. Private conversations are not automatically accessible through the agency manager’s business-data role.

Disconnecting a platform removes its active Lion AI connection and that workspace/platform's saved report snapshots and model briefs. It does not change platform campaigns or necessarily revoke the app's entire upstream authorization. You can also revoke access in your Google or Meta app settings.

Disconnection does not automatically remove historical chat messages or their saved evidence. You can delete your private conversation through Lion Chat. Memory is managed separately: personal memory is private to its login, while changes to client-shared memory require workspace-owner review. Use the deletion-request process for records and protected backup copies that require separate handling.

Identity, membership and activity records, and copies in protected backups, can remain after a platform disconnection. Contact us for a deletion request covering those records. Backup restoration requires separate reconciliation with disconnections and deletion requests; a recovery test does not restore a backup into the live service.

Requests and control

Use the data-deletion instructions to disconnect, revoke access or request deletion. Contact office@semlion.com for access, correction or other privacy requests. We may need to verify your identity and workspace authority. Never send us a password, access token or authentication code in a deletion request.