Privacy Policy

What Pandaigent stores

When you sign in with Google, we store your Google account identifier, email address, name and profile image so one account can own one Pandaigent company.

When you connect an email sender such as Kit, we store encrypted OAuth credentials, account details, sent broadcast content, campaign performance and subscriber engagement. Subscriber email addresses and names are encrypted. A keyed, non-reversible email fingerprint is used to recognise the same customer across connected providers.

When you connect a social account, we store its encrypted OAuth credential and account name. For Threads, Instagram and Facebook, Pandaigent may also retrieve published posts and provider-reported engagement metrics so Workers can learn from your own content performance. A basic LinkedIn connection requests only the openid andprofile scopes and stores the LinkedIn member identifier, name and encrypted access token. LinkedIn may also return a profile image with the basic profile, but Pandaigent does not store that optional field or request the member's email address. An X connection stores the X account identifier, @handle, and an encrypted short-lived access token. Pandaigent uses that token only to retrieve the selected account's profile. After the token expires, Pandaigent erases it during the next connection-state check while retaining the profile identity you selected. It does not retrieve or store X posts, or post, like, follow or send messages on X through this connection.

When you connect YouTube, Pandaigent stores an encrypted Google OAuth credential, your channel identifier and name, and a read-only copy of your channel's uploads. That copy can include video identifiers, titles, descriptions, publish dates, thumbnail URLs and the public view, like and comment counts returned by the YouTube Data API. Pandaigent requests only the youtube.readonly scope and cannot use it to publish, edit or delete YouTube videos.

How the data is used

Pandaigent uses connected email history to show analytics, identify patterns, calculate customer-level engagement and help its Workers learn from writing that performed well. Workers may create unscheduled email drafts in a connected provider. Pandaigent does not provide a tool that sends or schedules those emails without the owner acting separately.

Google and YouTube data is used only to provide the user-facing features you request: sign in, identify the connected channel, show its uploads and provider-reported counts in your private workspace, and let your Workers analyze that evidence for you. Pandaigent does not use Google user data for advertising, credit decisions, sale to data brokers, or training a general-purpose or shared AI model.

Sharing and security

We do not sell personal information. Data is shared only with infrastructure and AI service providers needed to operate Pandaigent, subject to their service terms. OAuth tokens and personal email fields are encrypted at rest, and each company's records are separated by its owner account.

The minimum relevant Google user data may be processed by Pandaigent's infrastructure or configured AI service provider only when needed to deliver a feature you request. It is not transferred to advertising platforms or data brokers. Pandaigent personnel do not read Google user data unless you ask for support and give permission, access is necessary for security or legal compliance, or the data has been aggregated and anonymised for internal operations.

Pandaigent's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Retention and disconnection

Disconnecting a provider erases its active OAuth token and stops future access. Unless a provider's rules or your deletion request require removal, previously imported history can remain in Pandaigent so past reports do not disappear.

Disconnecting LinkedIn deletes the LinkedIn connection record, including the member identifier, account name and encrypted OAuth credential, together with any LinkedIn data stored for that workspace. LinkedIn access tokens last about 60 days and this connection has no refresh token; when the token expires, Pandaigent deletes the connection and asks the member to consent again before collecting the profile again. Pandaigent does not call LinkedIn again after disconnection. Members can also remove Pandaigent from LinkedIn's Permitted services settings.

Disconnecting X revokes any remaining OAuth credential and deletes the X connection record, including the account identifier, @handle and encrypted access token. Pandaigent does not retain X post history because this connection does not retrieve it.

YouTube is handled more strictly. Disconnecting YouTube revokes its OAuth credential and deletes the imported YouTube channel and video data from your Pandaigent timeline. While connected, Pandaigent rechecks authorization and refreshes or deletes stored YouTube data within 30 days. If Google reports that access was revoked, Pandaigent deletes the stored YouTube data. You can also revoke Pandaigent directly from your Google account's third-party access settings.

Google sign-in and other connected-app access can also be revoked from the respective Google, LinkedIn, X, Meta, Threads or email-provider account settings. To request deletion of the Pandaigent account and its stored data, use the data deletion instructions.

Contact

For privacy questions or a request concerning your account data, email faiqradzali@gmail.com.