1. Information we process and why
| Context | Items | Purpose and legal basis | Retention |
|---|---|---|---|
| Email sign-up and sign-in | Email, one-way hash of the password, display name, email verification status | Account creation, authentication and management; performance of contract | Until deletion upon account deletion |
| Google and Kakao sign-in | Account identifier for each provider, email, display name, profile image URL, link history | Providing the chosen sign-in method and linking accounts; performance of contract | Until deletion upon unlinking or account deletion |
| Account settings | Profile image you upload yourself, language and time zone settings | Displaying your profile and personalized display; performance of contract | Until changed or deleted, or until account deletion |
| Terms acceptance | Version of the terms accepted and policies acknowledged, time of acceptance, your self-declaration that you are 18 or older | Confirming sign-up conditions and managing the application of the terms | Until deletion upon account deletion |
| Workspace | Name, member identifiers and roles, invitation emails, channel access permissions and activity history | Collaboration and permission management; performance of contract | According to workspace use and deletion and the account deletion procedure |
| Content creation and scheduling | Body text, images and videos, per-channel settings, scheduled time and time zone, publishing results | Saving, previewing, scheduled publishing and progress notifications; performance of contract | Until you delete it or the workspace is deleted. When a channel is disconnected, that channel's schedules and publishing results (platform post identifiers and links) are deleted while body text, photos and videos remain. Photo and video originals follow the retention periods in Section 2 |
| Social channel connection | Channel identifier, name, handle, bio and profile image, granted permissions, access and refresh tokens | Verifying the selected channel and maintaining authentication | Until the channel is disconnected or a related deletion request is processed |
| Viewing comments, mentions and performance | Post/video identifier, description and preview, comment and mention text, author display information and attachments, reply and handling status, views, reactions, followers, and age range, gender and region aggregates provided by the platform, and YouTube aggregates by device, playback location, traffic source and search term and audience retention curves | Handling comments and mentions on connected channels and displaying performance | For the period needed while the connection is maintained (the last 30 days for YouTube performance). Cleaned up upon disconnection or deletion request. Platform-specific storage limits apply |
| Comment auto-reply settings | Auto-reply name, keywords, reply and Send DM text, selected post scope, times turned on and off and the member who did so | Running the auto-replies you turn on; performance of contract | Until deleted, or until the channel is disconnected or the workspace is deleted |
| Comment auto-reply history | Identifiers of comments and mentions containing keywords, identifiers of sent replies and DMs, handling results and reasons for skipping | Displaying execution results and preventing duplicate sending | Follows the comment history period. Mention records are kept for 30 days or less |
| DM auto-reply settings | Auto-reply name, keywords, reply text, times turned on and off and the member who did so | Running the DM auto-replies you turn on; performance of contract | Until deleted, or until the channel is disconnected or the workspace is deleted |
| DM auto-reply history | Message identifier, sender, text and sent time of received DMs (kept encrypted only until processed, deleted within 24 hours at the latest), matched keyword, non-reversible digests of the sender and message, handling results and reasons for skipping | Checking keywords, displaying execution results and preventing duplicate sending | DM text and sender identifier are deleted immediately after checking (within 24 hours at the latest); records are kept for 30 days |
| AI usage records | Requesting member and workspace, channels used, task type, model used, result and failure reason, usage (token counts) and processing time. Request text and AI suggestions are not included | Applying AI usage limits, preventing abuse and identifying causes of incidents | Deleted 90 days after creation |
| Paid subscription and payment | Plan and number of channels used, billing period, amount and currency, invoices and payment status, last four digits of the card, payment method identifier issued by the payment processor (billing key) | Performance of the paid subscription contract, payment and refund processing, retention of transaction records | After the subscription ends, according to the statutory retention periods below. The billing key is destroyed when the payment method is removed |
| Notifications | Identifier of the user receiving the notification, notification type and target post or workspace, read time, notification settings | Informing you of the results of tasks you requested; performance of contract | In-app notifications are deleted automatically when the history period expires. Notification email sending records are deleted 30 days after sending |
| Notification email sending | Recipient email address and body (stored encrypted), template type and language, sending status and error code, unsubscribe, bounce and spam complaint results | Delivering notification emails, identifying causes of failure and preventing resending | Deleted 30 days after sending |
| Browser push notification subscription | Push subscription information issued by the browser (endpoint and encryption keys, stored encrypted), service domain of the subscription endpoint, browser and operating system type, registration time and last delivery time | Delivering notifications to devices you have turned on yourself | Deleted immediately when you turn it off on the device or delete your account. Subscriptions expired or revoked by the browser are discarded as soon as a delivery failure is confirmed, and the record of that fact is deleted after 30 days |
| Authentication, security and incident response | Access time, request path and IP, browser and operating system information, session and device identifiers, security digests of partial IP/user agent, security activity records | Keeping you signed in, device management, new-device sign-in notices, blocking misuse and incident response | During account deletion, authentication information and device display information are removed. Security activity records are managed with information that directly links users, sessions and access environments reduced, and records of event type, time, handling result and pseudonymous identifiers may remain. Server access and error logs are deleted after 30 days. |
| Service usage analytics (optional) | Browser analytics identifier, categorized page type, sign-up button location, allowed referral campaign, browser and device category. When you are signed in, a pseudonymous analytics ID that cannot be traced back to your account ID, your current plan and display language. Results confirmed by the server: payment completed (plan, billing cycle, amount), channel connected (platform, whether it is the first connection) and post published (platform, post format, whether it is the first post) | Improving visits, referrals and feature use; enabled by default; collection can be limited through browser controls or Google’s opt-out tool. If you limit analytics in your browser, the server also stops sending results | You can limit collection through browser controls or Google’s opt-out tool, and analytics cookies can be deleted in your browser. The measurement link the server uses to send results is deleted if it is not updated for 13 months, or when you sign out, limit analytics or delete your account. Records already sent to Google Analytics follow its retention setting (14 months), and you can request their deletion via the support email. |
| Public page visit counting | Date of visit, public page type, display language, referral source, country reported by Cloudflare and device type. A one-time value made from the IP address and browser information to count each visitor once per day. IP addresses and cookies are not stored | Counting visits to Moyeo's public site and improving the service; counted on the server without cookies | Daily totals are deleted after 730 days, and the one-time value after the following day |
| Service usage day records | User identifier and the dates you used the service while signed in | Measuring daily, weekly and monthly active users and improving the service | Deleted after 400 days, and on account deletion |
| Sign-up origin | The kind of path where sign-up started (bio page or campaign link), the referral information of an external campaign link if you came from one (utm_source, utm_medium, utm_campaign, utm_term, utm_content, up to 100 characters each), where you tapped (Moyeo badge, share window or handle claim window) and the address of the bio page you were viewing if you came from a bio page, and the time saved. If you signed up from the bio page handle claim window, the bio page handle you wanted | Confirming sign-up routes and improving the service, and letting you create your first bio page with the handle you wanted. Saved once at sign-up regardless of whether visit analytics is collected | Referral information is kept until account deletion. The wanted handle is deleted when you create your first bio page or close the prompt. The same values in pending email sign-ups and social sign-in attempts that were not completed are deleted when those records expire |
| Technical errors and operational alerts | Error classification, code location and release version, internal user and workspace identifiers, the path of the screen where the error occurred (without query strings), and browser and operating system information; account identifier, masked email, name and browser and operating system category of the signed-up account; paying workspace, invoice identifier, plan and amount; aggregate numbers for first channel connections, first published posts and the daily summary. Emails notifying the operator of inquiries and plan requests contain the sender's email address and display name as-is so the operator can reply. Incident alert emails contain no personal information | Identifying causes of incidents and confirming sign-up, payment, activation and inquiry operations. Where configured, Sentry, an access-restricted Discord channel, and the operator mailbox (Google Workspace) are used | Encrypted bodies for Discord delivery are deleted when delivery ends, and undelivered bodies are kept for up to 24 hours. The ledger row recording delivery is kept for 30 days thereafter and then deleted. Errors and alerts delivered to external services and the operator mailbox are managed separately according to each service's retention and deletion settings. |
| Inquiries | Identifier and workspace of the user making the inquiry, inquiry type (account, payment, plan, channel connection, publishing, scheduling, error report, feature suggestion, other), inquiry text (at least 10 and up to 2000 characters), the screen from which the inquiry was sent, browser information, service release version and request identifier, time received | Reviewing and answering inquiries; performance of contract or action upon request | Deleted 3 years after the date received. Records of consumer complaints and disputes follow the statutory period below |
| Account deletion and cancellation survey (optional) | The reasons you select and follow-up answers (the service you are moving to, features you needed, difficulties you had), whether you would use Moyeo again, free-text comments (stored encrypted), and your plan and billing cycle at the time of cancellation | Understanding why users delete their accounts or cancel subscriptions in order to improve the service. Submitting the survey is voluntary and optional | 3 years after submission, free-text comments and the link to the respondent are deleted to anonymize the response, and only anonymous reason statistics are kept. On account deletion, the link to the respondent is removed immediately |
| Plan requests | Identifiers of the requesting workspace and requester, requested plan and billing cycle, number of channels to be used, accompanying note (up to 500 characters), request status and processing time | Receiving and processing usage requests before payment is enabled; performance of contract | While the workspace is maintained after the request is processed. Where it constitutes a transaction record, the statutory period below applies |
| Business profile and bio pages | Industry, team size, goals, address, phone number and weekly hours you enter, page profile, blocks, design, custom logo and public handle, measurement IDs of connected visit analytics tools (GA4, Meta Pixel, Naver Analytics) | Saving settings and publishing the information you choose; performance of contract | Address, phone and hours are removed when changed, cleared or the workspace is terminated. Pages are removed when deleted or the workspace is terminated. The public handle of a deleted page is held for 30 days so no one else can use it, then released |
| Bio page analytics | Visit date and hour, pages, blocks and links visited, traffic source (including share link code), country and Korean province reported by Cloudflare, device category, return-visit flag determined and sent by the browser, link clicks, visitor actions and time on page. Stored only as daily and hourly aggregate counts; no visitor identifier or IP is stored | Providing visit and activity statistics to the member who created the bio page (entrusted processing under 3-2) | Daily aggregates are deleted after 730 days and hourly aggregates after 90 days. Deleted immediately when the bio page is deleted. Items kept in the browser follow Section 9 |
| Bio page inquiry and reservation submissions | Name, email, phone number and submission content entered by visitors (stored encrypted), reservation date and quantity, traffic source, times received, read, replied and closed and processing status, version of the privacy notice agreed to and time of consent | Enabling the member who created the bio page to review and process submissions (entrusted processing under 3-2) | Deleted at the earlier of 180 days after closure or 365 days after receipt. Deleted immediately when the member deletes the submission or the bio page is deleted. Consent records (without contact details) are deleted after 1,095 days |
| Bio page newsletters | Name (optional) and email entered by visitors (stored encrypted), a non-reversible digest that prevents duplicate sign-ups with the same email, time of consent and notice version agreed to, time the confirmation email was sent and time it was confirmed, time of unsubscribing, bounce and spam complaint results, subject and body of newsletters sent and per-recipient sending results | Confirming with a confirmation email that the email signed up belongs to the visitor, sending newsletters and the biennial notice of consent to consenting visitors, and proving consent (entrusted processing under 3-2) | If the sign-up is not confirmed within 7 days, the sign-up including the email and name is deleted. When a visitor unsubscribes, the email and name are deleted immediately and the remaining record is deleted after 30 days. Contacts stopped because of bounces or spam complaints are kept until the member deletes them or the bio page is deleted so they are not sent to again. Newsletters sent and sending results are deleted after 365 days. Deleted immediately when the member deletes the recipient or the bio page is deleted. Consent records (without contact details) are deleted after 1,095 days |
| Bio page submission reply emails | Email of the visitor receiving the reply and the reply text (stored encrypted), name of the sending bio page, time of reply and the member who replied, sending status and error code | Delivering replies written by the member who created the bio page to visitors (entrusted processing under 3-2) | The reply text is not kept in the submission record. Email sending records and encrypted bodies are deleted 30 days after sending, the same as notification email sending records |
| Bio page guestbook | Display name chosen by the visitor (up to 20 characters) and message (up to 300 characters), time left, approval or hidden status and time of decision | Enabling the member who created the bio page to review entries and show approved entries on the public page (entrusted processing under 3-2). Approved entries can be viewed by anyone | Entries awaiting approval are deleted after 30 days, and hidden entries 7 days after being hidden. Approved entries are kept until the member deletes them or deletes the bio page |
| Bio page reports | Report reason, number of reports with the same reason and first and last report times, handling result and the operator who handled it. Information about the reporter is not stored | Confirming and acting on policy violations, and responding to disputes | Handled reports are deleted 1 year after handling. Open reports are kept until handled |
| Bio page public form protection | Request counts and time windows for submissions, guestbook entries, reports and unsubscribe requests. Bot check values and IP needed for the bot check (Cloudflare Turnstile) | Preventing automated submissions and flooding, and protecting the service | IP is not stored. Count records are deleted when the time window ends. Turnstile check values follow Cloudflare's processing terms |
| Receiving promotional emails (optional) | Email address registered to the account | Sending promotional emails such as introductions to Moyeo's features and services and events and promotions; separate optional consent (Article 15(1)(i) of the Personal Information Protection Act) | From the time of consent until consent is withdrawn or the account is deleted |
| Email subscription settings and change history | User identifier, whether email is allowed or refused, notice version, time and channel of change | Managing subscription settings you request, confirming choice history and applying opt-outs | Kept while the account is maintained and deleted in the deletion procedure upon account deletion. Change history after withdrawal is not used for sending advertisements |
For information visitors leave through the reservation, inquiry, newsletter sign-up and guestbook forms of a bio page, the member who created that bio page is the personal information controller and Redband processes it as entrusted (3-2). Reservation and inquiry forms show the name of the business receiving the information, the items collected and the purpose of use, the retention period, the entrusted processor (Moyeo) and a link to this policy, and ask for required consent to the collection and use of personal information; without that consent a visitor cannot submit. Newsletter sign-up shows the same notice and asks separately for consent to receive advertising information; without that consent a visitor cannot sign up for the newsletter, which does not affect reservation or inquiry submissions. When a visitor signs up for the newsletter, we send a confirmation email to that address and send newsletters only after the visitor confirms by clicking the link in the email. The version of the notice the visitor agreed to and the time of consent are kept as a consent record.
Social channel information is received within the scope you allowed on the official authorization screen. If photos or posts contain other people's personal information, please make sure you have the right to post or share it. Moyeo does not receive your Instagram, Threads or YouTube account passwords. You can use features that do not depend on them without adding a profile photo or connecting a social channel.
When sending an inquiry, you do not re-enter your email address. The email address and display name used for replies are not stored in the inquiry record; they are read from your signed-in account information and included only in the notification email sent to the operator. The screen and browser information sent with the inquiry text are used to re-check the same issue and are deleted 3 years after the inquiry is received.
The reason survey shown when you delete your account or cancel a subscription is optional and is used to improve the service; you can delete your account or cancel without submitting it. Free-text comments are stored encrypted, and 3 years after submission we delete the free-text comments and the link to the respondent, keeping only anonymous reason statistics. When you delete your account, we immediately remove the link between your responses and your account.
Moyeo does not collect personal information of children under 14. At sign-up we receive your self-declaration that you are 18 or older, and if we learn that a child under 14 has signed up, we delete the account and information after verification.
Use of personal information for marketing purposes and receipt of promotional emails are optional, and you can use the service without consenting. You can withdraw at any time in account settings, or without logging in through the unsubscribe link at the bottom of a promotional email or your mail app's unsubscribe button. We do not send promotional emails yet, but you can already choose whether to receive them and change that choice. For details, see the Marketing and Promotional Email Notice.
2. Retention period and destruction
Personal information is destroyed without delay once the purpose of processing has been fulfilled. Deleting an account deletes the linked posts, media, comments, statistics, AI suggestions and authentication data, and disconnecting a channel deletes that channel's scheduling and publishing records, comments, statistics, AI suggestions and authentication data, in sequence, so the time of receipt and completion may differ. Posts written in Moyeo remain after a channel is disconnected, and their photos and videos remain in the library and follow the file retention rules below. However, to enforce the plan's channel limit, the record showing which channels a workspace first connected (workspace identifier, provider and channel identifier, time of first connection) remains even after the channel is disconnected, for as long as the workspace is maintained.
When a bio page is deleted, its submissions, guestbook entries, newsletters and sending results, reports, pinned reviews and visit aggregates are deleted immediately, and emails not yet sent are not sent. When a workspace is deleted, the bio pages in it are deleted in batches in the same way. Consent records (without contact details) remain for 1,095 days, bio page change records for 2 years (operator take-down and restore records for 3 years), and sending records of emails already sent until 30 days after sending, and are then deleted. Change records do not contain submission content or visitor contact details.
Photos and videos you upload are kept while they are attached to a post or used by a schedule, workspace or profile. Files not used anywhere are deleted after 7 days, and files that failed inspection are deleted after 1 day. After publishing ends, the original of a file is kept for the retention period of the workspace's plan (30 days on the Free plan, 90 days on Pro and 180 days on Team) from the day its last publishing ended, and then deleted. After the original is deleted, the preview is kept for as long as the publishing record remains. When a channel is disconnected, we release the usage marks from that channel's schedules and publishing, and these rules apply from then on. Deleting an original does not delete posts already published to Instagram, Threads or YouTube.
Records retained under law
When electronic commerce records arise, we keep them for the following periods, separately from information used for general service purposes (Article 6 of the Enforcement Decree of the Act on the Consumer Protection in Electronic Commerce).
- Records of labeling and advertising: 6 months
- Records of contracts or withdrawal of subscription: 5 years
- Records of payment and supply of goods, etc.: 5 years
- Records of consumer complaints or dispute resolution: 3 years
Retention is limited to the records needed to verify the relevant transaction or dispute. Not every activity record of every member is kept for the same period.
Destruction procedure and method
- Time of destruction: Information is destroyed when the retention period ends or the purpose of processing has been achieved, or when you request deletion and verification is complete.
- Destruction procedure: We identify the information to be destroyed, destroy it after the Chief Privacy Officer confirms, and record the result.
- Electronic files: Deleted from databases and storage, or identifying information is removed, so that it cannot be recovered or reproduced. Items stored encrypted are deleted together with their ciphertext.
- Printed materials: If paper documents or similar are produced, they are shredded or incinerated.
- Backups: Information remaining in disaster recovery backups disappears as the backups rotate once the retention period below has passed.
Database backups for disaster recovery are kept for 7 days and then deleted automatically, and are never used for any purpose other than recovery.
3. Provision to third parties
Redband does not provide personal information to third parties without your consent or a legal basis. When you request tasks such as posting, replying or deleting, or turn on auto-reply, we provide content and identifiers to the relevant platform as described below to carry out that request. This is provision to a third party at your request, and since all recipients below are overseas businesses, their country, retention period and how to refuse are also disclosed in the cross-border provision table in §5. Processing and deletion after provision are governed by each platform's policies.
| Recipient | Purpose of provision | Items provided | Retention and use period |
|---|---|---|---|
| Meta Platforms, Inc. (Instagram, Threads) | Publishing posts you request, writing and deleting replies, comment, mention and DM auto-replies, viewing performance | Post text and media, target account and post identifiers, reply text, DM text sent by comment auto-replies, reply text of DM auto-replies and the recipient identifier, reply text to mentions, settings values needed for the request | According to the platform's policies |
| Google LLC (YouTube) | Shorts uploads you request, viewing and replying to comments, viewing performance | Video file and upload settings such as title, description and visibility, target channel and video identifiers, reply text | According to the platform's policies |
If you do not want this provision, you can choose not to request the task or disconnect the channel. Once disconnected, you can no longer post to that channel or handle its comments. Redband does not sell user data and does not provide data from connected channels for third-party ad targeting.
3-2. Information processed on your behalf
For comments, replies and mentions on channels you have connected and their authors' display names and account identifiers, replies and DMs sent by comment auto-reply and their results, and received DMs checked and replies sent by DM auto-reply (hereinafter "commenter information"), you are the personal information controller and Redband processes it as entrusted by you. This relationship follows Article 5-4 of the Terms of Service.
The information processed on your behalf and its purposes and retention are as follows.
- Comment and reply text on connected channels and the author's display name and account identifier: used for viewing comments, replying, comment auto-replies and displaying performance. Follows the comment history period and is deleted when the channel is disconnected.
- DM text, sender identifier and sent time of DMs received on channels with DM auto-reply turned on: used only for DM auto-reply, which sends the reply you saved once to a DM containing a keyword. Kept encrypted only until processed and deleted immediately after processing, upon disconnection, permission revocation, workspace deletion or a Meta data deletion request, and within 24 hours at the latest; records are kept for 30 days without the text.
- Identifier, text, author display name and handle of posts in which others mentioned the channel: used only while mention auto-reply is on, to collect and show mentions and post replies. Mention records are kept for no more than 30 days.
- Reply text of DM auto-replies and the recipient identifier, and reply text to mentions: provided to Meta to send the auto-replies you turned on (§3 Provision to Third Parties).
- Comments you pin as bio page reviews on the Comments screen: Only comments you choose are made public on the bio page. The public page shows the comment text, a platform mark, the date of the comment and the author name masked except for its first one or two characters, and does not show the author's profile image or account identifier. We do not keep a separate copy of the comment text, and it is removed from the public page if you unpin it, if the original is hidden or deleted, or if you disconnect the channel.
For information left by bio page visitors (reservation and inquiry submissions, newsletter sign-ups and newsletter sending results, submission reply emails, guestbook entries) and bio page visit statistics (hereinafter "visitor information"), the member who created that bio page is likewise the personal information controller, and Redband processes it as entrusted by the member. The items and retention periods of visitor information follow Section 1. Redband uses visitor information only for that member to review and reply to submissions, send newsletters, publish guestbook entries and view visit statistics, and does not mix it with other members' bio pages or use it for Redband's advertising. The member must have a legal basis for processing visitor information and give visitors the required notices, and this relationship follows Article 5-5 of the Terms of Service.
Redband uses commenter information and visitor information only for features you request, such as viewing comments, replying, auto-replies, displaying performance and running bio pages, and does not use it for other purposes or provide it to third parties. We do not further entrust processing to anyone other than the processors disclosed in this policy, and the security measures in this policy apply equally to commenter information and visitor information. When you disconnect a channel or delete a workspace, it is deleted according to the retention criteria in this policy.
4. Processing entrustment
The companies to which Moyeo entrusts the processing of personal information to provide the service are as follows. Through entrustment contracts, Redband sets the purpose and scope of processing, restrictions on re-entrustment, security measures and destruction obligations, and supervises compliance.
| Processor | Entrusted work | Information processed | Retention and use period |
|---|---|---|---|
| Amazon Web Services, Inc. | Operating servers and databases in the Seoul region, sending authentication, invitation and notification emails, sending inquiry, request and incident alert emails to the operator, sending newsletter confirmation emails, newsletters, consent notices and submission reply emails to visitors on behalf of members who created bio pages | Personal information stored in the service, emails and messages needed for sending (including visitors' emails and the bodies of newsletters and reply emails) | Until the entrustment contract ends |
| Cloudflare, Inc. | Running, delivering and protecting access to the website, storing and delivering images and videos, bot checks (Turnstile) and rate limiting for bio page public forms | Access requests and IP, data needed to process requests, uploaded media and public images, bot check values | Until the entrustment contract ends |
| Toss Payments Co., Ltd. | Payment authentication, approval and cancellation, and billing key management | Payment method identification information, transaction information | Until the entrustment contract ends |
| Google LLC — Google Workspace (Gmail) | Receiving and storing customer inquiry emails, receiving and storing operational alert emails (inquiries, plan requests, incidents) | Inquirer's email and display name, inquiry text and attachments, plan request details, incident alert body | Until the entrustment contract ends |
| Google LLC — Google Analytics | Service usage analytics for Moyeo's website and app | Analytics identifier, page type, sign-up button clicks, allowed referral information and device category; when signed in, a pseudonymous analytics ID, plan and display language; server-confirmed results for completed payments, channel connections and published posts. Email, names, internal account IDs, post content and arbitrary URL queries are not sent | According to Google Analytics retention settings (14 months) and deletion requests |
| Google LLC — Gemini API | Generating AI drafts, edited post text, post topics and reply suggestions you request | Request and body text, target comment, original post, channel information and language, time zone, scheduled time, and other items listed in the AI writing and reply suggestions notice below | Limited abuse monitoring period (according to Google's paid service terms) |
| Functional Software, Inc. (Sentry) | Identifying technical errors in the browser, web server, API and job processing | Allowed error classification, code location and release version, internal user and workspace identifiers, screen path (without query strings), and browser and operating system information. Email, names, request and response bodies, cookies, authentication information and screen recordings are not sent | Until the entrustment contract ends |
| Discord Inc. | Checking sign-ups, payments, activation (first channel connected, first post published) and a daily summary in an access-restricted operational channel | Sign-up and payment alerts contain the account identifier, masked email and name, device category, workspace and invoice identifiers, plan and amount. Activation alerts and the daily summary contain aggregate numbers only. Passwords, sessions, card numbers and raw IP are not sent | Until the entrustment contract ends |
When we add or change a processor, we revise this policy and publish it before the effective date, and make the changes viewable in the revision history. If you do not agree to the change, you can delete your account or stop using the relevant feature.
Google and Kakao are authentication providers that provide the information needed for the sign-in you choose, and Meta and Google/YouTube are external platforms that perform the functions of connected channels.
AI writing and reply suggestions
Before you use AI for the first time, we show a data processing notice and keep the notice version you acknowledged and the time as an acknowledgment record separate from acceptance of the sign-up terms. Acknowledging the notice does not cause posts to be created or published automatically, and you can use the service without using AI features.
When you request an AI draft, post text editing or a post topic recommendation, or press the reply suggestion button to generate a new suggestion, the Moyeo server sends the information needed for generation to Google's Gemini API. Depending on the task, this may include the request and body text you entered, the target comment, the original post, recent messages in the same conversation, recent text written on that channel, the post's engagement metrics, and channel information and language, time zone and scheduled time.
Context sent to AI is limited to what is needed from channels you can access in the current workspace, and writing history from other workspaces is not mixed in. Merely viewing a page or reusing a saved suggestion does not send a new generation request. Generated text is an editable suggestion and is not sent to social channels until you publish it or send it as a reply.
The commenter's display name is not sent as a separate item, and the sign-in account, workspace, generation job, comment identifiers and internal lookup values are not included in generation requests. However, personal information you enter or that is contained in reference text is not automatically removed, so please do not enter sensitive personal information or secrets.
Moyeo uses the Gemini API under paid terms with a linked billing account. Under paid terms, Google does not use the inputs Moyeo sends or the outputs it returns to improve its products or train models, and retains them for a limited period only to prevent abuse. Google's data processing is governed by the Gemini API Terms of Service, and Moyeo's internal retention period for generated results differs from Google's processing and retention terms.
Moyeo stores AI-generated suggestions encrypted and deletes AI drafts, edited post text and reply suggestions 24 hours after creation, and post topic recommendations after 7 days. Each suggestion is recorded together with the channels used to create it, and when a channel is disconnected, only AI suggestions created using that channel's data are deleted. Suggestions that used only other channels in the same workspace and suggestions created without channel data remain until the retention period above. When a workspace is deleted, all AI suggestions stored in that workspace are deleted.
Moyeo does not use AI to automatically make decisions that have legal effects or similarly significant effects on you. AI only creates suggestions that you review, edit and use.
5. Cross-border transfer
Servers and databases are operated in the Amazon Web Services Seoul region and are therefore not transferred overseas. Toss Payments and Kakao are domestic businesses, so they do not constitute cross-border transfer. Processing that goes overseas is disclosed in the two categories below according to its nature.
Processing entrustment and storage for performance of contract
In accordance with Article 28-8(1)(iii) of the Personal Information Protection Act, we disclose the following regarding processing entrustment and storage necessary for concluding and performing contracts.
| Recipient and contact | Destination country | Basis | Time and method of transfer | Items transferred | Purpose of transfer | Retention and use period | How to refuse and effect |
|---|---|---|---|---|---|---|---|
| Cloudflare, Inc. / dpo@cloudflare.com | Countries where Cloudflare's global edge is located, including the United States | Article 28-8(1)(iii) | Transmitted over encrypted communication when you access the service, use features, upload files or submit bio page forms | IP and request information needed to process web requests, uploaded images and videos and public images, bot check values | Providing the website, storing and delivering media, access protection and bot checks | For the period needed to provide the service and as processed upon Moyeo's deletion request | You can refuse via support@moyeo.io. If you refuse, we cannot provide the web service and media features |
| Google LLC (Google Workspace, Google Analytics) / 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | Countries where Google's data centers are located, including the United States | Article 28-8(1)(iii) | Transmitted over encrypted communication when inquiry, plan request and incident alert emails are received, and when events are sent from browsers with analytics enabled, and when the server confirms a completed payment, channel connection or published post | Email and display name of inquirers and requesters, inquiry text and attachments, plan request details, analytics events and device category; when signed in, a pseudonymous analytics ID, plan and display language; server-confirmed results (plan, billing cycle and amount; platform, post format and whether it is the first connection or post) | Processing inquiries and plan requests, usage analytics in browsers with analytics enabled | According to each service's retention settings and Moyeo's deletion requests | Analytics can be limited through browser controls or Google’s opt-out tool (which also stops server sending), and for inquiries you can use another channel. Refusing does not restrict your use of the service |
| Functional Software, Inc. (Sentry) / compliance@sentry.io | United States | Article 28-8(1)(iii) | Transmitted over encrypted communication when an error occurs while the service is running | Error classification, code location, release version, internal user and workspace identifiers, screen path (without query strings), and browser and operating system information | Identifying causes of incidents and maintaining service stability | According to the Sentry project's retention settings | You can request refusal via support@moyeo.io. Refusing does not restrict your use of the service |
| Discord Inc. / privacy@discord.com | United States | Article 28-8(1)(iii) | Transmitted to an access-restricted operational channel when a sign-up, payment or activation (first channel connected, first post published) event occurs and when the daily summary is sent | Account identifier, masked email and name, device category, workspace and invoice identifiers, plan and amount. Activation alerts and the daily summary contain aggregate numbers only | Internal alerts for the operator to check sign-ups, payments and activation | According to the operational channel's retention settings | You can request refusal via support@moyeo.io. Refusing does not restrict your use of the service |
Overseas processing when you request AI features
| Recipient and contact | Destination country | Basis | Time and method of transfer | Items transferred | Purpose of transfer | Retention and use criteria | How to refuse and effect |
|---|---|---|---|---|---|---|---|
| Google LLC (Gemini API) / 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | Countries where Google or its processing agents operate facilities | Article 28-8(1)(iii) | Transmitted over encrypted communication when you request AI generation | Request and body text you entered, post and comment context needed for generation, channel information, language, time zone and other items in the AI notice above | Generating writing and reply suggestions you request | Paid service terms apply, so data is not used for product improvement and is only retained on a limited basis for abuse detection | You can choose not to request AI generation. Other features can be used without using AI |
Moyeo calls the Gemini API from a project with a linked billing account, so the data processing terms for paid services apply. Under these terms, Google does not use inputs and outputs for product improvement and retains them only for a limited period for purposes such as abuse detection. For details, see the Gemini API Terms of Service and the Google Data Processing Addendum.
Cross-border provision at your request
The transfers below are cross-border provision made to carry out your request when you choose a sign-in method, connect a channel and request posting, replies or performance viewing, or turn on auto-reply. They are of the same nature as the provision to third parties in §3 above, and the recipient, country, items and purpose are explained on the sign-in screen and channel connection screen; they take place only within the scope you consented to on each platform's official consent screen.
| Recipient and contact | Destination country | Basis | Time and method of provision | Items provided | Purpose of provision | Retention and use period | How to refuse and effect |
|---|---|---|---|---|---|---|---|
| Meta Platforms, Inc. / 1 Meta Way, Menlo Park, CA 94025, USA | Countries where Meta's data centers are located, including the United States | Article 28-8(1)(i) | Transmitted over encrypted communication when you connect a channel and request posting, replies, auto-replies or performance viewing | Channel identifier and granted permissions, post content and media, reply text, DM text sent by comment auto-replies, reply text of DM auto-replies and the recipient identifier, reply text to mentions | Providing Instagram and Threads channel integration features (posting, replies, comment, mention and DM auto-replies, performance viewing) | According to the platform's policies and your deletion requests | You can choose not to connect a channel or disconnect it. If you refuse, you cannot use the posting and comment features for that channel |
| Google LLC (YouTube, Google Sign-In) / 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | Countries where Google's data centers are located, including the United States | Article 28-8(1)(i) | Transmitted over encrypted communication when you request sign-in, channel connection, uploads, replies or performance viewing | Sign-in account identifier and email, channel and video identifiers and granted permissions, uploaded videos and settings, reply text | Providing Google Sign-In and YouTube channel integration features | According to the platform's policies and your deletion requests | You can use another sign-in method or disconnect the channel. If you refuse, you cannot use that sign-in or the YouTube features |
The scope of Cloudflare's processing can be found in the South Korea Privacy Addendum and the Customer Data Processing Addendum, and the scope of Google Workspace's processing in the Data Processing Amendment and the Subprocessors and processing locations notice. The list of processing locations in each notice does not indicate the actual country where a specific file is stored.
6. Use of external platform data
What Moyeo receives from the external platforms you connect, with which permissions, for what purpose, and when it is deleted can be found for each platform in the Platform Data Use Notice.
- Instagram · Threads: Permissions requested and data received, handling of Meta's app deauthorization and data deletion request callbacks
- YouTube: Moyeo uses YouTube API Services. Data by permission, refresh method by data type, and deletion timing
- Google Sign-In · Limited Use disclosure: Sign-in information transferred to Google LLC in the United States and compliance with the Google API Services User Data Policy
- Kakao Login: Consent items and unlinking
- Data deletion by platform: How to disconnect and revoke permissions
7. Google and YouTube data
Moyeo uses YouTube API Services. We view and store the profile, video information, comments and performance data of connected channels within the scope of granted permissions, and use them for Shorts uploads you specify and for viewing comments and performance on connected channels. YouTube integration features are subject to the YouTube Terms of Service, and Google's processing of personal information is also subject to the Google Privacy Policy (https://policies.google.com/privacy).
Moyeo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. This information is processed to provide and improve user-facing features, and is not used for sale, ad targeting or credit assessment. Only the necessary personnel access it, and only in permitted cases such as supporting a user's specific request, security investigations or legal requirements. We do not combine data received from YouTube with personal information from other sources without your separate request or consent.
Data received through the YouTube API is refreshed differently by type. Performance metrics are refreshed once a day for each connected channel, and comments are refreshed by re-fetching recent activity about every 3 hours and re-fetching the entire history period once a day. For workspaces not used for more than 14 days, recent comment activity is re-fetched at intervals of up to 12 hours. When the entire history period is re-fetched, videos whose comment count has not changed may be skipped for up to 7 days. Channel information such as channel name, handle, profile image and description is received and stored when you connect or re-authorize the channel, and refreshed by re-fetching about every 3 days. When a comment deleted on YouTube is confirmed as deleted during a run that re-fetches the entire history period, its text is deleted immediately and its record within one day. Comments that have not been re-fetched for 30 days are deleted. Video information is re-fetched starting 27 days after it was last checked, and deleted videos or videos that could not be checked for 30 days are deleted together with related performance data. Performance metrics and viewer aggregates received from YouTube Analytics are kept only for the last 30 days regardless of your plan, and performance metrics older than 30 days are deleted even while the channel stays connected. When you disconnect a channel, delete a workspace or delete your account, we delete the related data and authentication tokens stored by Moyeo and request revocation of the authentication tokens through Google's revocation endpoint.
If you disconnect a channel, delete your account, or request deletion in the Moyeo app, we delete the YouTube data stored by Moyeo within 7 days; if you revoke Moyeo's access in your Google Account security settings, we delete it within 30 days. The same deadlines apply to data of channels that can no longer be fetched because token refresh failed.
You can revoke Moyeo's access in Manage third-party apps with account access in your Google Account. Unlinking Google sign-in in Moyeo deletes the link record kept by Moyeo, but you must revoke the app permission remaining in your Google Account yourself on the screen above. You can request deletion of information stored by Moyeo by disconnecting the channel or via support@moyeo.io. Deleting information stored by Moyeo does not delete videos posted on YouTube.
8. Kakao login data
When you use Kakao Login, we receive only the items you allowed on Kakao's consent screen. Kakao's consent item names and the items Moyeo stores are as follows.
| Kakao consent item | Item stored by Moyeo | Purpose of use |
|---|---|---|
| Kakao Account (Email) | Email address | Account identification and sign-in, sending service notices |
| Nickname | Display name | Initial value of the name shown on screen |
| Profile Image | Profile image URL | Initial value of the profile image shown on screen |
You can unlink Kakao Login in account settings, and when you delete your account, Redband requests unlinking from Kakao to disconnect it from Moyeo. For detailed procedures, see the Data Deletion Instructions.
10. Notifications
Service notification emails that inform you of the status of tasks you requested, such as publishing results, are notices for performance of contract and are separate from consent to receive advertising information. You can adjust how you receive each type in notification settings, and notifications essential to using the service, such as payment, security and account status, cannot be turned off in the app.
When you sign in on a device we have not seen before, we send a new-device sign-in notice to your account email to protect your account. The notice states only the sign-in time and the browser and operating system names, and does not include your IP address or the raw device information sent by your browser. We use the authentication and security information in Section 1 to tell devices apart and collect no additional information for this notice.
Sending records and encrypted bodies of notification emails are deleted 30 days after sending, so that we can check them when you ask about an email you received. In-app notifications disappear automatically when the history period expires, and the history period may vary by plan.
Browser push notifications are used only when you turn them on yourself for each device. When turned on, we receive the subscription information issued by the browser (delivery endpoint and encryption keys) and store it encrypted with a versioned key; we do not store the full delivery endpoint, keeping only the domain that shows which service it is sent to. Push bodies contain only the notification's title and summary and information on the screen to navigate to, and do not contain account identifying information or link URLs. Push notifications are delivered in encrypted form through the push services run by browser vendors (such as Google, Apple and Mozilla), which cannot read their content.
You can turn off push notifications under "푸시 알림" (Push notifications) in Settings > Notifications. Turn off the switch for the device you are using, or press "해제" (Remove) next to any other device; either way, we delete that device's subscription information right away. If you revoke notification permission in the browser, the subscription is discarded as soon as it is confirmed invalid on the next delivery attempt. When you delete your account, subscriptions for all registered devices are deleted.
11. Rights of data subjects and how to exercise them
You can manage display information and linked accounts and delete your account in account settings. Please send requests for access, correction, deletion or suspension of processing of personal information, and withdrawal of consent, to matthew@moyeo.io or support@moyeo.io. If you are signed in, you can also send the same request through the inquiry window opened by "모여에 문의하기" (Contact Moyeo) in the account menu at the bottom of the workspace sidebar or the floating question mark button on the screen. These requests are received by customer support (support@moyeo.io), and the Chief Privacy Officer confirms the result. We aim to respond within 2 business days. An agent can also make requests on your behalf, and we verify your identity or the agent's authority to the extent necessary. Requests are processed without delay, and for requests restricted by law, we explain the reason.
Bio page visitors can exercise their rights as follows.
- Newsletters: Confirming through the unsubscribe link at the bottom of a newsletter, or using your mail app's unsubscribe button, stops newsletters from that bio page and immediately deletes the email and name.
- Access, correction and deletion of submissions and guestbook entries: Visitors can ask the member who created that bio page. The member can immediately delete received submissions and newsletter recipients one at a time and guestbook entries one by one; the name, contact details and content of a deleted submission are erased so they cannot be restored, and only the consent record without contact details remains for the period in section 1. If the member cannot be reached or asking directly is difficult, send the bio page address, the date the information was left and the contact details to support@moyeo.io. Redband passes the request on to that member and, after verifying identity to the extent necessary, informs the visitor of the result within 10 days.
- Reporting a bio page: Use "Report" in the share window of the public page, or let us know at support@moyeo.io.
We do not accept sign-ups from anyone under 18 and do not collect personal information of children under 14. If we learn of such a sign-up, we verify it and delete the information.
For consultation on privacy infringement, you can contact the Personal Information Infringement Report Center at 118 (privacy.kisa.or.kr); for dispute mediation, the Personal Information Dispute Mediation Committee at 1833-6972 (kopico.go.kr); and to report crimes related to personal information, the Korean National Police Agency Cyber Investigation Bureau at 182.
Automated decisions
Comment auto-reply is a feature that executes the keyword and text rules you set exactly as they are, and Redband does not use it to make decisions in a fully automated manner that significantly affect the rights or obligations of you or commenters. Likewise, AI suggestions leave Moyeo only after a person reviews them and chooses to publish or send them.
12. Security measures
In accordance with Article 29 of the Personal Information Protection Act and related notices, Redband takes the following measures.
- Internal management plan: We establish and implement an internal management plan for the safe processing of personal information and review it regularly.
- Access rights management: We limit personnel who can access personal information to the minimum number needed for their work, and keep records of granting, changing and revoking permissions.
- Access log management: We keep access logs of personal information processing systems, retain them for at least the period prescribed by law, and review them regularly.
- Encryption: Passwords are stored as non-reversible one-way hashes, and sensitive values such as channel access tokens, payment method identifiers, notification bodies, push subscription information and bio page visitors' names, contact details and submission content are stored with AES-GCM encryption using versioned keys. IP and browser information in security records are kept as digests instead of the originals.
- Protection in transit: All communication between your browser and the server, and between the server and external services, is encrypted with TLS.
- Access control: We apply workspace- and channel-level permission checks, session and device management, blocking of abnormal access and request rate limiting.
- Physical measures: Servers and storage are operated in Amazon Web Services and Cloudflare data centers, and physical safeguards such as entry control are carried out by those businesses under the entrustment contracts.
- Responsibility and breach notification: Final responsibility for personal information protection lies with the representative. If we become aware that personal information has been or may have been lost, stolen or leaked (hereinafter a "breach"), we notify data subjects within 72 hours from that time and report to the authorities prescribed by law.
13. Chief privacy officer
We have designated a Chief Privacy Officer as follows to oversee personal information processing and handle users' inquiries and complaints.
| Item | Details |
|---|---|
| Name | 김용민 |
| Title | CEO |
| matthew@moyeo.io | |
| Phone | 010-5877-8951 |
For general customer support, please contact support@moyeo.io.
14. Changes to this policy
When we change this policy, we publish the effective date and the changes 30 days before the effective date for changes that are unfavorable to users or material, or 7 days before for other changes, and also notify you by account email. Previous versions are available in the revision history. Changes that require separate consent under applicable law are applied after obtaining your consent.
15. Business information
| Item | Details |
|---|---|
| Business name | 레드밴드 |
| Representative | 김용민 |
| Business registration number | 309-08-95749 |
| Mail-order business registration number | 2026-서울강동-0281 |
| Address | 서울특별시 강동구 상암로 11, 113동 2002호 (암사동, 선사현대아파트), 05240 |
| Phone | 010-5877-8951 |
| Customer support email | support@moyeo.io |
| Representative email | matthew@moyeo.io |
| Hosting provider | Amazon Web Services, Inc., Cloudflare, Inc. |
Revision history
| Effective date | Changes |
|---|---|
| 2026-10-31 (current version) | Added aggregates by device, playback location, traffic source and search term and audience retention curves received as YouTube performance to the processed items, and corrected YouTube performance metrics and viewer aggregates to be kept only for the last 30 days regardless of plan |
| 2026-10-27 | Added to the sign-up origin where you tapped on a bio page (Moyeo badge, share window or handle claim window) and the address of the bio page you were viewing, and clarified that referral information (UTM) is saved only for external campaign links |
| 2026-10-19 | Added pseudonymous analytics IDs for signed-in users and analytics sending of server-confirmed results (payments, channel connections, published posts), public page visit counting, service usage day records and AI usage records, corrected what is sent to Sentry and Discord, server log retention (30 days), cookie and browser storage items and retention and the push notification delivery path to match actual behavior, aligned the wording of notice periods for policy changes with the Terms of Service, and added the newsletter confirmation step to this translation |
| 2026-10-15 | Aligned AI feature names (text polishing is now post text editing), plan names in sentences, the contact menu name and how to turn off push notifications with the app, corrected the inquiry retention period to start from receipt as in the table, and simplified awkward wording |
| 2026-10-13 | Added the items and retention periods of bio page visitor information (submissions, reply emails, newsletters, guestbook, reports, visit statistics), consent to collection and use on public forms, the entrustment relationship for visitor information, bio page cookies and analytics tools connected by members (with the visitor's choice to refuse), how visitors exercise their rights and storage of sign-up origin, and explained login-free unsubscribing from promotional emails |
| 2026-10-07 | Added processing and retention details for bio page business information, visits, submissions and newsletter subscriptions |
| 2026-09-29 | Clarified how posts, photos, videos and publishing records are handled when a channel is disconnected, and aligned terms with the app (posts, publishing, history period, Send DM) |
| 2026-09-28 | Added per-plan retention of photo and video originals and new-device sign-in notices, and changed the retention of notification email sending records to 30 days |
| 2026-09-26 | Clarified default analytics, collection controls and transmitted information |
| 2026-09-23 | Initial version |