← PandaiTech Social

Privacy Policy

Last updated: 29 September 2026

What PandaiTech Social 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 PandaiTech Social 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, PandaiTech Social may also retrieve published posts and provider-reported engagement metrics so Workers can learn from your own content performance. Facebook, Threads and Instagram publishing is optional and requested separately. If you enable it, PandaiTech Social records the granted permissions and sends the approved content to the account and time you select. Supported formats include Facebook posts and Reels, Threads posts and replies, and Instagram images, carousels and Reels. 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 PandaiTech Social 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. PandaiTech Social uses that token only to retrieve the selected account's profile. After the token expires, PandaiTech Social 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 Telegram, PandaiTech Social stores an encrypted bot token, the bot identifier and username, and the channel identifier, title and public username. It checks the bot's administrator and posting permissions without sending a message. Disconnecting erases the stored bot token while retaining the channel identity. This connection does not retrieve channel history or enable automatic publication.

When you connect YouTube, PandaiTech Social stores an encrypted Google OAuth credential, your channel identifier and name, and a copy of your channel's upload metadata. 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. The youtube.readonly scope identifies your channel and reads its uploads; yt-analytics.readonly reads channel performance by date, including views, likes, comments and shares. Optional youtube.upload access lets PandaiTech Social upload a video version you approve to the selected channel. We store the video, metadata, approval, schedule and returned upload status needed to carry out and verify that request.

A TikTok connection stores your account identity, public video metadata and reported engagement. Optional Direct Post access uses video.publish to send an approved video with the visibility, interaction settings and commercial or AI disclosures you select. We record your upload consent and TikTok's processing result. Public posting remains unavailable until TikTok approves Direct Post. A separate, optional TikTok Business analytics connection requests user.info.basic and user.insights for daily performance, subject to provider approval and your consent.

How the data is used

PandaiTech Social 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. Scheduling a Kit newsletter additionally requires approval of the saved content, selected audience and future send time. Drafting alone does not authorize sending.

Media publishing may use short-lived, signed links bound to one workspace, asset and job so the selected provider can retrieve the approved media, or an authenticated upload to that provider. PandaiTech Social records the resulting identifier, status, permalink when available and publication time. Cancelling before execution stops the queued job; an in-flight provider result is held for reconciliation if its outcome is unclear.

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, display daily channel analytics, upload explicitly approved videos, and let your Workers analyze selected evidence for you. PandaiTech Social 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 PandaiTech Social, 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 PandaiTech Social'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. PandaiTech Social 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.

PandaiTech Social'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 PandaiTech Social 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, PandaiTech Social deletes the connection and asks the member to consent again before collecting the profile again. PandaiTech Social does not call LinkedIn again after disconnection. Members can also remove PandaiTech Social 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. PandaiTech Social 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 PandaiTech Social timeline. While connected, PandaiTech Social rechecks authorization and refreshes or deletes stored YouTube data within 30 days. If Google reports that access was revoked, PandaiTech Social deletes the stored YouTube data. You can also revoke PandaiTech Social 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 PandaiTech Social 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.