Data connected to AI assistants (Claude, ChatGPT)
Privacy Policy version 1.14 · effective 2026-11-18
Kết nối trợ lý AI (Claude, ChatGPT) — English translation of section 18
The MocaOne app on Claude and ChatGPT is provided and operated by Công ty Cổ phần Mocato Việt Nam (MOCATO VIETNAM JOINT STOCK COMPANY), which is responsible for it. You may connect your MocaOne account to an AI assistant you choose, currently Claude (Anthropic) or ChatGPT (OpenAI), so that the assistant can view figures, write posts and send them for approval on your behalf. Connecting is optional, done by you, and you can disconnect at any time. If you do not connect, MocaOne sends no data to these assistant providers. Step by step: mocaone.com/tro-giup/ket-noi-ai/.
Data the assistant can read through MocaOne, only in the business you choose when you allow it and within your role: the names and status of publishing channels, titles, short excerpts, post status and publishing schedule, and search performance (SEO) figures. Data the assistant can write through MocaOne, if you grant permission: posts being written (new or edited), requests for approval, publishing or scheduled publishing (only when the Owner has turned it on), and cancelling a schedule. MocaOne never returns passwords, access tokens, API keys or other businesses' data. MocaOne does not receive the content of your conversation with the assistant, only the commands the assistant sends to MocaOne.
Data exchanged when you connect (OAuth). When you connect in Claude or ChatGPT, you sign in to MocaOne and choose the business and permission level on MocaOne's consent screen. MocaOne records: your MocaOne account (user ID, email), your business and role in it, the assistant app name, the permissions you allow, the host that receives the authorization code, and the time. The assistant receives access and refresh tokens (not your password) and the list of permissions; it does not receive your email, password or API keys. An access token is valid for 1 hour, a refresh token for 30 days, and the code exchanged after consent for 60 seconds; MocaOne keeps only one-way hashes of these tokens. The connection expires on its own after 180 days.
The table below lists every tool MocaOne exposes to the assistant: the data the assistant sends in, the data MocaOne returns, the purpose, the recipient and how long it is kept. A tool is available only when the connection's permission level allows it (see the three permission levels below); staff accounts only see posts they wrote. Every input is limited in length and format; text written by users or third parties (titles, descriptions) is returned marked as data, not as instructions.
| Tool | Assistant sends in | MocaOne returns to the assistant | Purpose | Recipient | Kept by MocaOne |
|---|---|---|---|---|---|
| get_overview | Nothing | Your role, whether the business allows AI to publish, the business name; the number of channels needing attention; up to 5 posts awaiting approval (post ID, revision, title); failed posts in the last 7 days; suggested next steps | Summary of what needs attention | The assistant provider you chose | Read command, not logged |
| list_channels | Nothing | ID, type, name and site address of each publishing channel (WordPress, Haravan, Sapo, etc.), status, content rules (length, allowed blocks) | Write posts that fit each channel | The assistant provider you chose | Not logged |
| list_recent_posts, get_post_status | Status filter, count, post ID | Post ID, status, revision, title, update time; for each post: the state of each channel (queued, scheduled, published, failed) and the public link once published | Track posts | The assistant provider you chose | Not logged |
| preview_post | Post ID, up to 3 channel IDs | Title, a plain-text excerpt of the post as rendered for each channel, warnings against channel rules, a preview token | Preview before sending for approval | The assistant provider you chose | The preview token is valid for 30 minutes and tied to that exact revision and channels; preview content is not stored |
| get_seo_performance | Time range (7, 28 or 90 days), optional post ID, count | For published posts: clicks, impressions, click-through rate, average position, trend, indexing status; with a post ID, also that post's top search queries | SEO reporting | The assistant provider you chose. The source is Google Search Console that you connected (section 19); this command only reads data already synced and sends nothing to Google | Not logged; the source data is kept as described in section 19 |
| get_search_topics (when the topic-planning feature is enabled for the business) | Time range (28 or 90 days) | Up to 50 search queries of the whole website: impressions, clicks, click-through rate, position, the page that ranks, previous-period impressions, suggestion groups (no article yet, near page one, few clicks, rising) | Propose a topic plan | The assistant provider you chose. MocaOne reads the data from Google Search Console (section 19) | A compact result is cached for at most 24 hours, then deleted (section 19) |
| list_recent_videos, get_video_status | Count, state, video ID | Platform (YouTube or TikTok), state, revision, title, description, tags, YouTube privacy level, whether a TikTok privacy level has been chosen, suggested publishing time, a fixed error code; never the video file | Track videos | The assistant provider you chose | Not logged |
| create_draft, update_draft | Title, content (text blocks), SEO description, tags, a public https cover image URL, channel IDs for rule checks; when editing, also post ID and revision | Post ID, revision, status, warnings against channel rules, a link to open the post in MocaOne | Write and edit posts being drafted; nothing is sent to any channel | MocaOne stores the draft for your business | Drafts are kept and deleted like posts created in the app; command log 180 days; cover images as described below |
| update_video_draft | Video ID, revision, title, description, tags | State, revision | Edit a video draft; does not change the video file or its privacy level | MocaOne stores the draft for your business | As above |
| submit_for_approval, submit_video_for_approval | Post or video ID, revision, a note of up to 300 characters, suggested publishing time, up to 3 channel IDs (posts) | ID, revision, status, the suggested time awaiting approval | Ask an Owner or Manager to approve; nothing is published | Owners and Managers of your business, inside MocaOne | The note and suggested time are kept with the approval request; command log 180 days |
| publish_post (Full operation level only) | Post ID, revision, channel IDs, preview token, optional time, confirmation | Request status and the link to MocaOne's confirmation page | Request publishing or scheduling; a real person presses Publish on MocaOne, or the post is scheduled at least 15 minutes ahead and the Owner can cancel it | MocaOne; once approved, the post goes to the platform you chose (WordPress, Haravan, Sapo, etc.) | The publish request (post ID, revision, content hash, channels, status) is kept 90 days after it finishes; command log 180 days; approvals log 2 years |
| cancel_scheduled_post (Full operation level only) | Post ID, optional channel IDs, confirmation | The channels whose schedule was cancelled | Cancel a schedule that has not run yet | MocaOne | Command log 180 days; approvals log 2 years |
Recipient. Data returned to the assistant is sent to the assistant provider you chose (Anthropic for Claude, OpenAI for ChatGPT) and processed by them under the terms between you and them. Cloudflare, Inc. is the processor that runs the MocaOne application. Google is only the source of search figures when you connect Search Console (section 19) and receives no data from the tools above. MocaOne does not pass this data to anyone else. Video files, passwords, platform access tokens, API keys and other businesses' data are never returned to the assistant.
Starter prompts. Claude may show a few MocaOne starter prompts (write a post for the channels, schedule this week's posts, what needs handling today, check SEO of published posts, topic plan from SEO). Each is one fixed Vietnamese sentence with only a topic (up to 200 characters) or numbers of posts and weeks that you type yourself; it contains none of your data and no hidden instruction. MocaOne stores nothing when you choose a starter prompt.
The three permission levels, which you choose on the consent screen when connecting:
- View only: the assistant only reads the data above and changes nothing.
- Draft & schedule: includes View only, plus writing and editing posts being drafted and sending posts for approval. By default the assistant only drafts and never publishes on its own.
- Full operation: includes Draft & schedule, plus publishing, scheduling and cancelling a schedule. This level works only when the Owner has turned on "Let AI publish" for the business (off by default), with re-authentication, and the permission expires after 30 days. A post published by the assistant goes live only after at least 15 minutes; MocaOne notifies the Owner and Managers with a cancel button during the wait. If the assistant app can open MocaOne's confirmation page, a real person presses Publish there.
Whatever level you choose, these five things always need the business Owner's approval on MocaOne and the assistant cannot do them on its own: (1) deleting data or deleting the business; (2) inviting or removing staff, changing roles or changing the Owner; (3) payments and plan changes; (4) disconnecting a channel; (5) raising the assistant's permissions.
Data MocaOne additionally stores for this: the grant record (who connected, which business, which assistant, permission level, time), access tokens as one-way hashes, and the approvals log: every time a person approves or declines something the assistant proposed, it records who, what, when, through which assistant and the result; the log contains no post content. Purpose: to let you review and to serve as evidence in a dispute. The AI approvals log is kept 2 years and then deleted. This differs from the sign-in and authentication log of the account, which is kept 180 days.
Logs and retention for this feature:
- Command log: only write commands (create, edit, send for approval, publish, cancel) and refused commands: time, connection ID, user ID, assistant app name, tool name, post ID, result or error code. No post content or arguments. Read commands are not logged. Kept 180 days.
- Rate-limit counters (commands per connection per hour, per business per day): only numbers, deleted after 3 days.
- Approvals log: as above, kept 2 years. Each row may include a one-way hash of the approver's IP address (the IP address itself is not stored) and a browser class. Once a day a marker (business ID, sequence number, hash of the last row) is written to a separate store outside the database to detect edited or deleted log rows; the marker contains no content or personal information.
- Cover images: when the assistant sends a cover image link, MocaOne downloads the image (public https addresses only, up to 5 MB, JPEG, PNG, WebP or GIF) and keeps a private copy in MocaOne's own storage. The copy becomes public only after the post is approved; a copy not approved within 7 days is deleted; the copy of an approved post is kept and deleted with the post. Each business has a storage quota for images.
- Drafts, posts written by the assistant and requests for approval: your business's data, kept and deleted like posts created in the app (sections 7 and 9). A finished publish request is kept 90 days as shown in the table.
- System errors: only the tool name and error type are written to the technical log (up to 90 days, section 7), never content.
When you use it, the data the assistant reads from MocaOne is sent to the assistant provider you chose and processed by them under the terms between you and them; see the policy of Anthropic or OpenAI. MocaOne does not control that. These two providers may process data outside Vietnam.
When you disconnect in the app (or the Owner disconnects a staff member's connection): the connection's access tokens are deleted immediately, pending publish requests are cancelled, and the grant record is deleted within 30 days. The approvals log is the exception and is still kept the full 2 years as stated above, as evidence. Drafts and posts created through the assistant are your business's data, kept and deleted like posts created in the app.
Your controls: (1) Choose whether to connect, and choose the lowest permission level that is enough when you connect. (2) See the connections that exist (who connected, which assistant, permission level, last use) in the AI assistants section of MocaOne; the Owner sees the connections of the whole business, other members see their own. (3) Disconnect at any time in MocaOne: access tokens are deleted immediately and the assistant can no longer read or write. You can also remove the MocaOne app in Claude or ChatGPT; to be sure it stops immediately, also disconnect in MocaOne, because an access token stays valid for up to 1 hour and a refresh token for up to 30 days if the assistant does not tell MocaOne it was removed. (4) The Owner can turn off "Let AI publish" at any time so that every publishing permission of assistants lapses. (5) The Owner can view the approvals history of the actions assistants proposed in MocaOne. (6) To ask to view, correct, export or delete data, including your command log, email [email protected] under section 9; you delete drafts and posts yourself in the app. The approvals log is an exception because it must be kept the full 2 years as evidence. (7) To delete or restrict data already held by Anthropic or OpenAI, ask them, under their terms and tools.
MocaOne does not use your data to train AI models, whether MocaOne's own or anyone else's, and does not sell or transfer this data to third parties, other than the assistant you choose receiving data itself when you use it as described above. MocaOne also does not use this data for advertising, to build profiles of individuals or for credit scoring. Data processed by the assistant is governed by the terms and privacy policy between you and OpenAI or Anthropic.
You protect your own MocaOne account and your Claude or ChatGPT account: keep sign-in details secret, connect only on trusted devices, and disconnect when you no longer use it or suspect a leak. If you find a security vulnerability, see mocaone.com/bao-mat/bao-loi/.