Legal
Privacy Policy
Last updated 11 November 2026
Who we are
Panda AI (“Panda”, “we”, “us”) is the social media suite from Panda AI Labs Limited at trypandai.com. This policy explains what we collect when you use the site, the app, and our API, and how we use it.
Questions: [email protected]. Related documents: Terms of Use and Terms & Conditions.
What we collect
Account. Email address, password (stored hashed), Google sign-in identifiers if you use Google, and whether your email is verified.
Workspace. Brand/project profiles, posts you draft or schedule, media you upload or generate, channel destinations, and connection status for X, LinkedIn, Discord, Slack, Facebook, Instagram, Bluesky, TikTok, YouTube, and WhatsApp.
Connected networks. OAuth tokens and basic profile details those networks return (for example display name, username, workspace or server id, and the channel you pick). Tokens are stored encrypted and used only to publish on your behalf or to list destinations you choose. For Bluesky, you provide a handle and an app password. Panda exchanges that for a session and does not store the app password.
Billing. Plan, trial dates, usage meters (AI credits and published posts), and Stripe customer/subscription identifiers. Card details are handled by Stripe, not stored on our servers.
Mail. Product and billing messages. New accounts also receive marketing and product emails until you turn them off in Settings or use the unsubscribe link in a message.
Contact. If you use the contact form, we receive your name, email address, and message, and we send that message to [email protected]. A problem report stores your email, the page you name, and the description.
Technical. Logs needed to run the service (time, path, status, request id). Error and warning lines are kept for seven days so we can fix faults. A session cookie and browser storage keep you signed in and remember your active brand. The installable app (PWA) stores a small amount of data on your device.
Product analytics. PostHog receives usage events such as pages viewed, actions in the product, and error reports. After you sign in we also send your account id and email so those events can be tied to the account. PostHog is hosted in the United States. We do not use this for third-party advertising.
How we use it
We use this information to:
- Create and secure your account
- Draft, schedule, and publish posts to networks you connect
- Show your WhatsApp inbox, send the replies and templates you ask for, and keep the opt-in and opt-out record for that number
- Run Studio, captions, and other AI features you ask for
- Meter plans, trials, and billing
- Send transactional mail, and marketing mail until you turn it off
- Measure how the product is used and fix failures
- Prevent abuse and improve the product
We do not sell your personal information. We do not use your connected social accounts to post except when you schedule or publish through Panda.
AI processing
If you use drafting, Studio, or similar features, the text and brand context you provide may be sent to our AI provider (currently OpenAI) to generate output. Do not put secrets, private customer data, or anything you cannot share with that provider into prompts. You are responsible for reviewing AI output before it is published.
WhatsApp message content stays in the inbox. It is not sent to the AI provider, to connected AI tools, or to any other AI feature. This version of Panda sends no automated WhatsApp reply.
Who we share with
We share data with processors only as needed to run Panda, including:
- Stripe, for payments and invoices
- OpenAI, for AI drafts you request
- Google, if you sign in with Google or connect YouTube
- X, LinkedIn, Discord, Slack, Facebook, Instagram, Bluesky, TikTok, and YouTube, to connect and publish
- Meta, for the WhatsApp Business Platform, when you connect a number and when a message is sent or received on it
- PostHog, for product analytics
- Email delivery (SMTP) for verification, billing, marketing, and contact-form messages
- Hosting, storage, and queue infrastructure that run the product
Those parties process data under their own terms. Publishing to a network means that network’s rules and privacy policy also apply to the post.
YouTube
If you connect a YouTube channel, Panda uses YouTube API Services to upload a video you choose, set its title, description, tags, category, privacy, publish time, made-for-kids choice, and thumbnail, and to read that channel’s name. After a video is published through Panda, we read its views, likes, and comments so you can see how it did.
We store the channel id, channel name, the upload tokens Google returns, and those view, like, and comment counts. Tokens are encrypted. We use them only to publish and to read stats for videos you sent through Panda. We do not sell this data, and we do not use it for advertising.
YouTube’s own rules also apply. Google’s privacy policy is at http://www.google.com/policies/privacy.
You can disconnect YouTube in Settings. That stops new uploads. You can also revoke Panda’s access from your Google Account at Google security settings. Deleting your Panda account from Settings deletes the stored channel record, tokens, and the stats we saved. The video stays on YouTube until you delete it there.
If you connect a WhatsApp Business number, you are the business those people are talking to. Panda is a Tech Provider. We process the WhatsApp data below so you can read the inbox, reply, manage templates, and send a broadcast you approve. We do not own your WhatsApp Business Account, and we do not sell this data.
You are responsible for the notice you give those people and for the legal basis that applies to them. Meta’s WhatsApp Business Messaging Policy and WhatsApp Business Terms also apply to the messages.
The number. We store the WhatsApp Business Account id, the phone-number id, the display number, the verified business name, the connection status, the quality and messaging-limit values Meta sends, and the billing currency of that account. The access token and the two-step registration PIN are encrypted. They are not shown in the product and they are not written into logs. If the number already has two-step verification, the owner types that PIN. Replacing a stored PIN is limited to the owner, and the audit row does not contain the PIN.
Messages. We store the message body, the type (text, image, audio, video, document, sticker, or a type we do not support yet), the direction, the time, the delivery status, and any failure reason Meta returns. Image, audio, video, document, and sticker files are not downloaded in this version. Those rows keep a placeholder instead of the file. A status receipt from Meta can include whether Meta marked the message billable, the pricing model, the pricing type, and the category. That receipt has no money amount. A broadcast cost in Panda is an estimate from Meta’s published rate card in the account’s billing currency.
People. For each person on that number we store the phone number when Meta or your import includes it, the business-scoped user id Meta assigns for your business, the parent business-scoped id when Meta sends it, the username, and the profile name. The business-scoped id is a country code, a period, and an id. It is not the phone number. We store the parent id and we do not send messages to it. We also store the country we learned from the phone number, from Meta’s webhook, or from the two letters at the start of the business-scoped id, and which of those sources we used. A missing phone number is allowed. Meta omits the phone number in some cases, including when the person uses a username and this number has not exchanged messages with that phone in the last 30 days.
Consent. We store whether the person is opted in, opted out, or has no consent on record, together with the source, the time, and any evidence you save. A business-initiated WhatsApp message needs opt-in under Meta’s policy. A chat the person starts is not marketing opt-in. The default opt-out words are STOP, PARAR, ARRÊT, and توقف. The default words that opt back in are START and UNSTOP, and they apply only to someone who had already opted out. A project can replace either list. An opt-out, including one you record outside WhatsApp, stops further sends to that person until a new consent record exists.
The suppression hash. An opt-out is also stored as an HMAC-SHA256 hash of a salt that belongs to the project and a normalized form of the phone number, the business-scoped user id, or the username. The hash is still personal data. It survives deletion of the contact, so a later import of the same person is still treated as opted out. The hash is removed when the project is deleted. A contact export includes a count of these hashes. It does not include the hashes themselves.
Marketing blocks. If Meta returns error 131049, we store a temporary block on further marketing to that person. For a United States number, or for a contact with no phone whose stored country is the United States, the reason is a US number and the block is 30 days unless the operator sets a different number of days. For anyone else the reason is Meta’s per-user marketing limit and the block is 1 day unless the operator sets a different number of days. Utility and service messages are unchanged. Meta does not deliver marketing templates to United States numbers. That skip is separate from this timed block.
How long we keep it. While the inbox is connected, message bodies follow the project’s WhatsApp retention setting. The default is 30 days. A setting of 0 keeps the messages. Contacts stay while the inbox is connected. If you disconnect and choose not to retain, messages, conversations, and contacts are deleted then. If you disconnect and choose to retain, they stay until the purge date, and are deleted when that date has passed. The suppression hashes stay until the project is deleted. A contact export is encrypted and deleted after 7 days. Deleting the project removes the contacts, including the phone number, the business-scoped id, the parent id, and the username, and it removes the hashes.
Logs of a send or a received message do not include the phone number, the business-scoped id, the parent id, the username, the message body, the token, or the PIN.
Cookies, local data, and the site notice
A notice at the bottom of the site asks you to accept this Privacy Policy and the Terms, or to decline. Accepting stores that you agree. Declining closes the notice. Either choice is saved in this browser so the notice does not appear again. You can still read this policy and the Terms from the footer.
We store the following on your device:
- A sign-in cookie and local storage for your session and active brand. These are required to run the product after you sign in.
- A preference cookie that remembers whether the sidebar is open.
- PostHog storage (a cookie and local storage) that identifies the browser for product analytics. This is set when you load the site, whether you accept or decline the notice.
- The notice choice itself, stored locally as accepted or declined.
We do not run third-party advertising cookies.
Retention and deletion
We keep account, post, media, and billing records while your account is open and as required for tax, dispute, and security purposes. You can disconnect a social network at any time in Settings. WhatsApp retention is described above. You can turn off marketing mail in Settings or via the unsubscribe link.
Signed-in users can delete the account and its data from Settings. That removes the profile, brands, posts, uploaded media, and connected social logins, and stops billing. Invoices already issued may remain with the payment processor. If you cannot sign in, email [email protected]. We may keep a limited record for security or legal reasons.
Your rights
Depending on where you live, you may have rights to access, correct, export, or delete personal data, or to object to certain processing. Email us to exercise those rights. You can also lodge a complaint with your local data protection authority.
Security and transfers
We encrypt social tokens at rest and use HTTPS in production. No method of transmission is perfectly secure. Infrastructure may be located in more than one country. By using Panda you understand your data may be processed outside your home country with appropriate safeguards for the service.
Children
Panda is not directed at children under 18. We do not knowingly collect personal information from them.
Changes
We may update this policy. The date at the top will change. Continued use after an update means you accept the revised policy.