AIBO is a supervised customer messaging and CRM workspace. It helps a business's authorized staff receive, review, organize, and reply to customer messages from connected business communication channels, including Facebook Messenger, Instagram, TikTok, WhatsApp, and Telegram.
This policy applies to AIBO pages, review workspaces, webhook receivers, and connected channel integrations operated by AIBO.
Information We Process
For AIBO app account holders, we process the username, display name, verified email address, password hash, two-step authentication settings, session and security records, team role, project memberships and actions taken in the business workspace. The Android app may register an optional device push token so AIBO can send generic update alerts; alerts do not contain customer message text. When enabled, Google Firebase Cloud Messaging receives the device push token to deliver those alerts. We use these records to sign users in, enforce project access, deliver invitations and account notices, and maintain an audit trail.
When you message a business account connected to AIBO, AIBO may process information provided by the communication channel and by your conversation, including:
- channel identifiers, such as Facebook Page-scoped IDs, Instagram-scoped IDs, TikTok conversation and account IDs, Telegram chat IDs, WhatsApp chat IDs, and related page or account IDs;
- public or channel-provided profile details, such as display name, username or handle, profile picture when available, and the channel used. AIBO keeps its own copy of the profile picture, because the platform's picture links expire, and deletes it with the rest of your data;
- message content, media attachments, captions, delivery status, timestamps, and conversation history;
- CRM information created by authorized staff, such as lead status, category, tags, follow-up notes, customer preferences, and scheduled actions;
- operator replies, AI-assisted draft content, review actions, audit records, and technical logs needed to secure and operate the service.
How We Use Information
We use this information only to provide and improve customer communication and CRM operations, including to:
- receive, route, and display customer conversations to authorized staff;
- send human-reviewed replies and attachments through the channel where the conversation occurred;
- manage leads, follow-ups, pipeline status, and customer support history;
- generate supervised AI draft replies for staff review before sending;
- protect the service, verify webhooks, prevent misuse, troubleshoot delivery, and maintain audit records;
- comply with applicable law, platform policies, and valid deletion or security requests.
Safety reports
When you report AI content, AIBO receives only the AI text you select and your optional note, with basic project, platform, reason and review metadata. No conversation history is automatically attached. Remove private details and secrets before submitting; common email addresses and telephone numbers are masked. Reports are encrypted, available only to authorized AIBO safety staff, retained for up to 28 days, and removed earlier with the associated source or reporter deletion where applicable. They are used to investigate unsafe output and record mitigation, not to train general-purpose AI models. Reports about customer content are handled separately by your business moderators.
Meta Platform Data
For Facebook Messenger and Instagram, AIBO processes Meta-provided user data only for the connected business messaging experience described above. We do not sell Meta user data, use it for unrelated advertising, or transfer it except to service providers that help operate AIBO under confidentiality and security obligations. When a business connects its Instagram professional account, AIBO also reads that account's public details (its username, name, profile picture, follower count and number of posts) to show the business's staff which account is connected. When a business allows comments and insights, AIBO also reads the comments and mentions on that business's Facebook Page and Instagram posts (the commenter's name or username, the comment and any photo in it), and the posts' own numbers (views, reach, likes, comments, shares and saves). AIBO uses them only to show them to the business's staff, suggest replies for staff to review, send the replies, private messages or hides that staff choose, and report how the business's posts perform. A commenter's comments are deleted with the rest of their data.
TikTok Data
For TikTok, AIBO connects only TikTok Business Accounts whose owners authorize it on TikTok's consent page, through TikTok's Business Messaging API. AIBO receives the direct messages customers send to that business account and the replies the business sends, including photos, videos, stickers, and shared posts, plus the ad or link a customer came from when TikTok provides it. AIBO replies only after the customer has written first and within TikTok's messaging limits; it never starts conversations or sends unsolicited messages. TikTok data is used only to provide the connected business's customer conversations and CRM records. It is visible only to that business's authorized staff, is never sold, shared with other businesses, or used for advertising, and access tokens and app secrets are encrypted at rest. TikTok Business Messaging is not used for accounts or customers in the European Economic Area, Switzerland, or the United Kingdom.
Sharing
We share information only as needed to operate the service: with the messaging platforms used to receive and send messages, with hosting/security/service providers that operate AIBO on our behalf, with the connected business's authorized staff, or when required by law or platform policy. We do not sell personal information.
Requests From Public Authorities
AIBO requires a review of the legality of any request from a government or other public authority before disclosing personal information processed through AIBO. We verify that the request has a valid legal basis, comes from an authorized authority, and identifies the information sought. Requests that cannot be validated are not fulfilled unless disclosure is otherwise required by applicable law.
Retention
The mobile app accesses a photo, video, document or client-data file only when you choose it with the system picker. Microphone access is optional and requested only when you tap Record voice note; recording stops when you stop it, leave the app or reach the displayed limit. A recording is sent to AIBO only when you submit the reply. Selected uploads, voice notes and business data follow the same project access and retention controls as the dashboard. Private downloaded previews and exports use temporary app storage, cleared when you switch projects or sign out; copies you explicitly open or save in another app are controlled by that app.
Conversation and CRM records are retained while needed for customer support, lead management, service quality, security, audit, dispute resolution, and legal or platform compliance. When data is no longer needed, or when a valid deletion request is approved, records are deleted or anonymized unless retention is required for legal, security, fraud prevention, dispute, or compliance reasons.
Security
AIBO uses administrative, technical, and access controls appropriate for a customer messaging system. Provider credentials and tokens are encrypted server-side, webhook signatures are verified where supported, reviewer access is restricted, and operational access is limited to authorized personnel.
Your Choices And Deletion Path
AIBO account holders can request account deletion in Settings > Account or in the Android app's Settings. The request immediately revokes sessions. We then verify transfer or erasure of any business projects and shared customer records, remove associated personal account data and confirm completion. The account deletion instructions also provide a web route for people who cannot sign in.
You may request access, correction, or deletion of personal data processed by AIBO. Email admin@aibo.world (admin [at] aibo [dot] world) or message the same Facebook Page, Instagram professional account, or TikTok business account where the conversation happened with the phrase: "Please delete my AIBO conversation data." Include the channel used and approximate conversation date so we can locate the correct record.
For detailed deletion instructions, visit /data-deletion.
Contact
For privacy, security, or data deletion requests, contact admin@aibo.world (admin [at] aibo [dot] world).
Google and YouTube Data
AIBO uses YouTube API Services. When you choose to connect a channel, Google asks for permission to let AIBO read that channel's information. AIBO receives authorization tokens, not your Google password. Read Google's Privacy Policy.
Information and permissions
For a channel you authorize, AIBO accesses its channel ID and name, upload playlist, video IDs, titles, descriptions, thumbnails, publication dates, visibility, duration and available format/broadcast information; public comments, replies and their author channel identifiers and names; and official video counts. Optional read-only YouTube Analytics access provides views, watch time, engagement and subscriber statistics. Authorization tokens are encrypted on AIBO's server and bound to your project and connected channel.
Read access powers your project's content library and synchronization. Optional management access enables team-reviewed public comment replies, moderation, and uploading or scheduling Videos and Shorts. AIBO only takes those write actions when authorized staff request them. Uploads use the title, audience, visibility and notification choices selected in Planner. AIBO does not provide YouTube direct messages or Community Post publishing.
Use, sharing and AI assistance
We use Google and YouTube data only to provide these features for the authorizing business and the teammates it permits to access its project. We do not sell this data, share it with unrelated businesses, or use it for advertising, data brokerage, credit decisions or training general-purpose AI models. AIBO's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
AI-assisted comment replies use the comment text, relevant thread/post context and your project's business knowledge. That limited context is processed by the AI service providers used to operate AIBO, solely to produce the requested feature. YouTube replies remain suggestions for your authorized team to review and send. They are not sent automatically. Hosting, storage, security and AI service providers may process data on our behalf for these disclosed purposes under access and security controls. Google credentials are never included in AI prompts. Staff access is limited to your authorized project team and operational access needed for support you authorize, security, or legal obligations.
With whom we share, transfer or disclose Google user data
AIBO shares Google and YouTube user data only with the following recipients, to provide the features you authorize, protect the service, or comply with law:
- Your business and its authorized team members: the connected channel's details, saved uploads, comments, replies and Analytics reports are visible within your project according to the access you grant. They are not made available to other businesses using AIBO.
- Google and YouTube: AIBO sends authorization tokens and the channel, video or comment identifiers needed to make API requests. When your authorized team requests a reply, moderation action or upload, Google and YouTube receive that action and its content, including selected video files and thumbnails. Published replies and uploads are visible on YouTube according to the action and visibility you choose.
- DigitalOcean, our application hosting and storage provider: processes the saved Google and YouTube records, encrypted authorization tokens and temporary upload files needed to host AIBO, maintain its database and backups, and complete your requested uploads.
- Cloudflare, our application traffic delivery and security provider: processes HTTPS traffic between your device and AIBO, including Google and YouTube data contained in the pages, API responses or uploads you use. Private API responses and private media are excluded from shared edge caching.
- OpenAI, our AI processing provider: receives relevant YouTube comment text, thread/post context and your project's business knowledge to generate and check AI-assisted reply suggestions. Google authorization tokens and client secrets are never included in these AI requests. This processing supports AIBO's disclosed features; Google and YouTube data is not used to train general-purpose AI models.
- Authorized AIBO support and safety staff: may access specific data with your affirmative permission for support, or where necessary to investigate security, abuse or a legal obligation. If you submit an AI safety report, the selected AI text and optional note are handled as described under Safety reports above.
- Public authorities or other legally required recipients: receive only information required by a valid legal request or applicable law, after review as described under Requests From Public Authorities above.
Our infrastructure and AI providers process data on AIBO's behalf for the purposes above, under applicable service agreements and access controls. We do not otherwise share, transfer or disclose Google user data to third parties. We do not sell it or provide it to advertisers, data brokers or information resellers. Any additional recipient or new purpose that requires your consent will be disclosed before that processing begins.
Retention, disconnecting and deletion
AIBO refreshes or removes saved YouTube API content, comments and reports within 29 days. Disconnecting under Platforms > YouTube stops synchronization, removes AIBO's stored channel authorization, and schedules deletion of the active saved YouTube data within five minutes. Disconnecting AIBO does not delete videos or comments on YouTube itself. You can also revoke AIBO's access in your Google Account permissions. When AIBO detects revoked authorization, it stops access and schedules the same removal. User-requested deletion of YouTube API data is completed as soon as possible and within seven calendar days after verification of the request.
To request deletion or ask about these practices, email admin@aibo.world with the connected channel URL or ID and your project/account email. Never send a Google password or access token. For an individual commenter's data, include the comment or video link. See Data deletion instructions.
Browser storage and third-party content
AIBO uses session cookies and browser storage for sign-in, project selection and interface preferences. Google and YouTube operate their own sign-in pages and may use their own cookies under Google's policies. AIBO displays official YouTube thumbnails through its authenticated service and links to YouTube for playback; it does not download YouTube video files or insert advertisements into YouTube content.