FDAM Article đź’«

Why franchisor headquarters need integrated delivery‑app sales view

This outlines why franchisor headquarters should view Baemin, Coupang Eats, Yogiyo, etc., not by platform but aggregated by franchise location, period, and platform, and how to leverage FDAM.

FRANCHISE INSIGHT · DELIVERY SALES DASHBOARD

Franchisor headquarters,
Why integrated delivery‑app sales view is essential

Moving beyond separate views of Baemin, Coupang Eats, and Yogiyo, headquarters must manage delivery sales flow by franchise location.

Franchisor staff reviewing scattered delivery‑app sales data across multiple admin screens

Franchisor staff reviewing scattered delivery‑app sales data across multiple admin screens

CORE SUMMARY

Delivery sales are now a core metric that franchisor headquarters must control. As the share of delivery‑app revenue in store sales grows, headquarters need to monitor Baemin, Coupang Eats, Yogiyo and other platforms together. As of March 2025, about 27.01 million Korean smartphone users were using delivery apps, and reports in March 2026 indicated that the combined payment volume of the four major platforms exceeded ₩3 trillion. The delivery channel is no longer a store‑level concern—it drives brand‑wide operations and must be tracked at the headquarters level.

Data sources: WiseApp·Retail March 2025 delivery‑app trends, March 2026 delivery‑app payment report, Fair Trade Commission announcement on delivery‑app terms, Google AI Search Optimization Guide

In a nutshell

Franchise headquarters must go beyond checking delivery‑app sales by platform and consolidate data by franchise location, period, and platform into a headquarters‑level view.

POINT 01

Platform‑by‑platform checks have limits.

Looking at Baemin, Coupang Eats, and Yogiyo separately makes it hard to grasp the brand’s overall trend quickly.

POINT 02

Headquarters need to see the full picture.

You need to view each franchise location’s ranking, period‑over‑period changes, and platform share together to make operational decisions.

POINT 03

Move beyond manual Excel aggregation.

Staff should spend time analyzing data, not gathering it.

Why has integrated delivery‑app sales reporting become a headquarters priority?

f4ff8a9c150df.png

Delivery sales are no longer a side channel for restaurant franchises. Cafés, chicken, pizza, snack, burger, Korean, salad, and dessert brands all reach customers via delivery apps. Some locations generate more revenue from delivery than dine‑in, and in new markets the app listing often serves as the first customer touchpoint.

The problem is that as delivery sales grow, headquarters management becomes more complex. Checking each platform’s admin page separately, consolidating franchise location sales in Excel, and then reformatting the data for headquarters reports consumes more time than expected. When you have 10 stores, manual work is manageable, but at 50 or 100 locations the situation changes dramatically.

In practice, these questions come up often: “Which store saw the biggest delivery‑sales increase this month?” “How have platform shares shifted?” “Which stores saw delivery sales drop compared to last month?” “Can we see the overall delivery‑sales trend at a glance from the headquarters perspective?” If you can’t answer quickly, it’s time to stop viewing delivery sales by platform.

AEO ANSWER BLOCK

Reasons franchise headquarters need integrated delivery‑app sales reportingWhen data is scattered across Baemin, Coupang Eats, Yogiyo, etc., it’s hard to quickly assess franchise‑location sales trends, period changes, platform dependence, and promotion impact. Headquarters must consolidate delivery sales by franchise location to see the brand’s overall flow.

1. Delivery sales have risen, but headquarters management has become more complex

Delivery apps are a critical revenue channel for the restaurant industry. Customers search for stores, compare menus, order, pay, and review—all within the app. For headquarters, the app is not just an order channel but also a brand‑exposure, promotion, and new‑customer acquisition channel.

However, from the franchisor headquarters' management perspective, the story changes. Managing delivery sales for 10 franchise locations versus 100 franchise locations is entirely different. As the number of locations grows, you must monitor platform‑by‑platform revenue, revenue per franchise location, period‑over‑period changes, regional differences, pre‑ and post‑promotion shifts, and platform dependence.

For example, if a brand operates 80 franchise locations and each uses three delivery apps, the franchisor headquarters must track up to 240 delivery‑revenue streams. Adding daily, weekly, and monthly comparisons, month‑over‑month changes, location rankings, and regional variations quickly exceeds what can be handled with Excel aggregation alone.

Management overviewIndividual platform verificationHeadquarters unified view
Revenue reviewPlatform‑specific admin accessConsolidated view by franchise location
Period comparisonManual processing after file downloadTrack daily, weekly, and monthly trends
Location comparisonStandardize by location name and periodView rankings and growth rates per location
Headquarters decisionPost‑aggregation decisionRapid response via dashboard

2. The franchisor headquarters must focus on the overall trend rather than individual revenues.

HEADQUARTERS DASHBOARD

Total delivery revenue

1.28 billion

vs. last month

+8.4%

Growing stores

42 locations

Declining stores

11 locations

Store

Delivery sales

Change rate

Key platforms

Gangnam location

48.2 million

+14%

Baemin

Songdo location

31.4 million

-7%

Coupang Eats

The headquarters dashboard provides a single view of total brand delivery sales, store rankings, and trend data by period.

Franchisees look at their own store’s delivery sales. However, the franchisor headquarters must view the brand’s overall performance. Beyond noting that a particular store’s delivery sales have risen, you need to determine why, whether the insight applies to other locations, if it’s driven by a specific platform, or by regional demand shifts.

The questions the headquarters must answer differ from those of individual franchisees: Which locations have seen a sharp drop in delivery sales? Where are delivery sales increasing? Which stores rely heavily on a particular platform? Are there stores where delivery sales grew but total sales fell? And is the post‑promotion delivery sales lift sustainable?

Answering these questions requires the headquarters to aggregate delivery‑app data in a decision‑ready format. It’s not enough to look at raw platform numbers; the data must be organized so that the operations team, supervisors, marketing, and executives can all review the same metrics and keep store‑management strategies aligned.

Key delivery‑sales questions for the headquarters

· Which locations experienced a steep decline in delivery sales compared to the previous month?

· Which locations have an excessive concentration of sales on a single platform?

· Are there stores where delivery sales rose but overall sales fell?

· Is the sales increase after a promotion being maintained?

Three scenarios when integrated delivery‑sales reporting is essential

606f01117f396.png

Infographic cards showing the three situations that require integrated delivery‑sales reporting

First, when comparing delivery sales across franchise locations

Don’t rely solely on a simple ranking of high‑ versus low‑performing stores. You must also consider market area, store size, operating hours, delivery‑app usage, advertising spend, and review‑management quality. Still, the starting point is consolidated sales data. The headquarters needs a uniform basis to compare all locations and decide which stores require support.

Second, when tracking sales trends over time

Check whether delivery sales have dropped month‑over‑month, whether sales after a specific event remain stable, and whether weekend‑weekday differences are significant. This data is essential for evaluating marketing effectiveness. A sales spike during an event doesn’t automatically mean success; you must verify post‑event retention and whether new customers are re‑ordering.

Third, when assessing platform dependency

If a store’s delivery sales are overly concentrated on one app, it becomes more vulnerable to exposure policies, fee changes, or rising ad costs. The headquarters should monitor each location’s platform mix to manage risk. Even with identical total delivery sales, a store with 80% Baemin versus one split 50% Coupang Eats, 30% Yogiyo, 20% Baemin faces a very different risk profile.

Purpose of the queryData to be reviewedHow the headquarters can use it
Franchise location comparisonDelivery sales, rankings, and growth rates by franchise locationIdentify underperforming versus growing franchise locations
Period AnalysisDaily, weekly, and monthly sales trendsAssess seasonal performance and campaign impact
Platform ShareDelivery sales share of Baemin, Coupang Eats, and YogiyoEvaluate platform dependence and advertising strategy
Promotion AnalysisPre‑ and post‑event sales, retention, and franchise location responseDetermine the effectiveness of marketing spend

4. Delivery sales are an operational metric, not just revenue

Delivery sales are not just raw revenue data. They reflect store operational health, marketing effectiveness, platform reliance, and regional demand. If a franchise location’s delivery sales drop suddenly, it may not be merely fewer orders—it could be lower review scores, reduced delivery windows, paused advertising, or new competitors entering the market.

Conversely, a sudden surge in delivery sales isn’t always positive. It might result from aggressive discount coupons that boost volume but lower average order value, hurting profitability. Therefore, the integrated delivery sales view should serve as a diagnostic starting point, not just a display of numbers.

Headquarters should evaluate delivery sales alongside dine‑in sales, total sales, cost of goods, promotional spend, royalties, receivables, and supervisor visit logs. If delivery sales rise while total sales stagnate, dine‑in customers may be shifting to delivery. If delivery sales increase and receivables grow, the settlement structure and franchisee profitability need review.

Delivery sales risks that headquarters often overlook

• Delivery sales increase while dine‑in sales decline, causing overall sales to plateau

• Heavy reliance on a single platform makes the franchise vulnerable to fee or exposure policy changes

• Sales spike during promotions but fail to sustain after the event ends

· Even when delivery sales rise, settlement amounts, royalty collections, and franchisee profitability may not improve

5. FDAM enables the franchisor headquarters to view delivery sales in a unified dashboard


e6341766ada10.png

Dashboard on FDAM that consolidates sales by delivery app and by franchise location

FDAM is an ERP solution that lets franchisor headquarters manage all franchise location operations data in one place. By using FDAM’s unified delivery sales view, headquarters can move beyond checking each delivery app separately and monitor sales flow from a central perspective.

Seeing each franchise location’s delivery sales, trends over time, and platform share together lets you assess store performance faster. For example, if a specific store’s delivery sales drop compared to the prior month, headquarters can investigate the cause rather than just noting a decline—determining whether the drop is limited to a single platform, affects overall delivery sales, or differs from offline sales.

Marketing teams can verify whether delivery‑app promotions actually moved the needle, and supervisors can identify counseling points based on each store’s delivery sales trends. In short, the unified delivery sales view is not merely a reporting tool—it becomes an operational benchmark that supports store management and marketing decisions at headquarters.

Headquarters challengesFDAM’s management approach
Checking each delivery‑app admin page separatelyConsolidating Baemin, Coupang Eats, and Yogiyo sales at the headquarters level
Difficult to rank franchise locations by delivery salesView sales, growth rate, and platform share for each store on a single screen
Hard to assess promotion effectiveness accuratelyCompare delivery sales changes before and after events over time
Challenging to identify dependence on specific platformsCompare platform sales share by franchise location to spot risk
Excel aggregation takes too longReduce repetitive aggregation and focus on analysis and response

6. Moving away from Excel aggregation speeds up headquarters operations

6adf9094ec7b5.png

Side‑by‑side view of a cluttered Excel aggregation screen versus a streamlined integrated dashboard

Managing delivery sales solely in Excel overloads staff. Downloading files from each platform, matching store names, standardizing periods, and rebuilding reports creates error risk. At franchisor headquarters, a single staff member often oversees many locations. When data consolidation takes too long, critical analysis and response are delayed.

The headquarters should focus on interpreting data, not gathering it. Quickly identify which stores need support, which platform’s sales share has shifted, and where delivery demand is rising. Spending a day on Excel consolidation pushes analysis and action to the back burner.

FDAM organizes delivery sales data from an operations perspective, letting staff shift focus from repetitive aggregation to store management and decision‑making. The speed of headquarters operations ultimately depends on how fast the data is compiled.

Common issues in Excel aggregation

· Store names differ by platform, making it hard to match the same location

· Varying reporting periods cause inconsistent month‑over‑month change calculations

· Each time a reporting file is created, formula errors or omissions can occur

· When staff change, aggregation methods and judgment criteria also change

7. Supervisors and the marketing team must view the same data

Integrated delivery sales view isn’t just for the operations team. When supervisors, marketing, and executives see the same data, decision‑making at headquarters becomes faster and more accurate. Supervisors can track a store’s delivery sales trend to pinpoint coaching points, marketing can compare promotion performance across stores, and executives can assess overall brand delivery channel growth and risks.

For example, suppose the marketing team runs a discount promotion on a specific platform. Reporting only that total sales rose during the promotion isn’t enough. You need to know which stores responded most, which regions saw the biggest impact, whether sales held after the promotion ended, and whether sales on other platforms declined.

Supervisors also rely on integrated data. When a franchisee says, “Delivery volume has dropped lately,” you must determine whether it’s a perception or an actual decline. If the drop is isolated to one platform, investigate exposure, reviews, advertising, or operating hours. If overall delivery sales are down, examine market demand and competitor activity.

UserUse cases for integrated delivery sales view
Operations teamMonitor brand‑wide delivery sales trends and spot underperforming stores
SupervisorDiagnose delivery sales drops for each store and determine coaching points
Marketing TeamAnalysis of sales changes and store-level responses before and after delivery app promotions
Executive TeamAssess delivery channel growth, platform risks, and brand operating direction

8. Delivery App Sales Consolidated Review Checklist

This checklist serves as a benchmark for franchisor headquarters to evaluate how systematically delivery sales are being managed. It’s not just about accessing the delivery app admin page; the key is whether the headquarters can compare data by franchise location, period, and platform.

CategoryChecklist QuestionData to Verify
01Can sales from Baemin, Coupang Eats, and Yogiyo be compared on a single screen?Sales by platform
02Can you view delivery sales rankings and growth rates by franchise location?Store sales compared to the previous month
03Can delivery sales trends be viewed by day, week, and month?Trend charts by period
04Can platform dependency be assessed for each franchise location?Revenue share by delivery app
05Can we compare delivery revenue changes before and after promotions?Revenue before and after the event
06Can we quickly identify franchise locations with declining delivery revenue?Decline rate and list of outlier locations
07Are operations, supervisors, and marketing teams viewing the same data?Franchisor headquarters shared dashboard

9. 30‑day action plan to launch integrated delivery revenue management

Integrated delivery revenue management doesn’t require perfect metrics from the start. The key is to start with the core questions the franchisor headquarters must review repeatedly. Begin by aggregating platform revenue at the franchise location level, standardizing time‑period comparisons, and then looking at each location’s ranking and change rate.

1

Week 1: Identify data sources for each platform

Document where to access Baemin, Coupang Eats, and Yogiyo revenue data and in what format to download it.

2

Week 2: Standardize by franchise location

Unify store names, store codes, regions, and assigned supervisor identifiers that vary across platforms.

3

Week 3: Define key metrics

We focus on total delivery sales, month‑over‑month change rate, platform share, underperforming stores, and pre‑/post‑promotion sales as key metrics.

4

Week 4: Apply dashboard‑based operations meetings.

The operations team, supervisors, and marketing team review the same dashboard to spot underperforming stores, growth stores, and platform risks.

Delivery sales management is no longer just a single franchise location’s responsibility.

Delivery sales are rising, but if headquarters still rely on checking each platform separately and aggregating data in Excel, operational speed will inevitably lag. While HQ verifies app sales, the market moves faster—platform policies change, demand shifts, and new competitors appear.

Headquarters must move beyond separate app checks and consolidate delivery sales across the entire franchise network. You need a single view of each franchise location’s sales flow, period‑over‑period changes, and platform mix so operations, supervisors, and marketing can act in sync.

Delivery sales management is a core KPI for the franchisor headquarters, not just an individual store task. Beyond identifying top‑performing locations, HQ must explain why they succeed, where declines occur, and what platform risks exist.

Frequently Asked Questions

Q. Why do we need integrated delivery sales visibility?

A. Looking at each delivery app in isolation makes it hard to see the brand’s overall trend. Headquarters must view sales by franchise location, period, and platform together for accurate management. As the number of franchise locations grows, relying on platform admin pages and Excel aggregation slows operations.

Q. Why is comparing delivery sales by franchise location important?

A. Store‑level delivery sales differences reveal market dynamics, operating hours, promotion impact, and platform dependence. This data supports supervisor consultations and marketing strategy development. It’s essential to look at month‑over‑month change rates and platform shares, not just raw sales rankings.

Q. Why track platform dependence?

A. When sales are overly concentrated on a single delivery app, the store becomes vulnerable to changes in exposure policies, fee structures, or ad costs. Headquarters should monitor each store’s platform mix to spread risk and adjust platform‑specific marketing tactics.

Q. How should we evaluate delivery app promotion effectiveness?

A. Don’t rely solely on sales during the promotion period. Assess pre‑ and post‑promotion sales shifts, post‑promotion retention, store‑level response differences, and any drop in sales on other platforms. Integrated delivery sales visibility lets headquarters analyze promotion impact faster.

Q. How does FDAM help with delivery sales management?

A. FDAM lets headquarters view delivery sales data in one place, track each franchise location’s sales flow and period changes, and reduce reliance on Excel aggregation. It enables store management from the headquarters perspective, and ensures operations, supervisors, and marketing all make decisions from the same data.

Q. Isn’t Excel sufficient for management?

A. It works at first, but as the number of franchise locations and delivery apps grows, Excel aggregation quickly hits its limits. Aligning store names and time frames per platform, calculating growth rates, and generating reports become time‑consuming and error‑prone. Headquarters should focus on analysis rather than data collection.

Q. Is looking at delivery sales alone enough?

A. Delivery sales are a valuable starting point, but they’re limited when viewed in isolation. Headquarters must evaluate delivery sales alongside total sales, dine‑in sales, cost of goods, promotional spend, royalties, receivables, and settlement data, because higher delivery revenue doesn’t always translate into better profitability.

DELIVERY SALES MANAGEMENT · FDAM

Your current delivery‑app revenue,
are you tracking it separately by platform?

Delivery revenue may be rising, but if headquarters still relies on platform‑by‑platform checks and Excel aggregation, operational speed will inevitably lag.

With FDAM’s unified delivery‑sales view, see each franchise location’s revenue trends, period‑over‑period changes, and platform share at a glance.

Request a deployment consultation

※ This content provides general information from the perspective of franchisor headquarters operations. Delivery‑app fees, settlement methods, and platform policies can vary by timing and contract terms, so you should verify each platform’s policy alongside your internal headquarters guidelines during actual operations.

Terms of Use

Article 1 Purpose

These Terms of Use govern the conditions and operational rules for using the services of "Site Name" (hereinafter referred to as "the Site").

Article 2 Definitions

Key terms used in these terms are defined as follows.

1. Member: An individual who agrees to these terms, provides personal information to register as a member, enters into a usage agreement with the Site, and uses the Site.
2. Usage Agreement: The contract concluded between the Site and a member regarding Site usage.
3. Member ID ("ID"): A unique combination of letters and numbers assigned to each member for identification and service access.
4. Password: The combination of letters and numbers selected by the member to verify identity and protect the member’s rights.
5. Operator: The entity that creates and manages the website offering the service.
6. Termination: The act of a member canceling the usage agreement.

Article 3 Supplemental Rules

The Operator may issue separate operational policies as needed; if these policies overlap with these terms, the operational policies will take precedence.

Article 4 Formation of the Usage Agreement

1. The usage agreement is formed when a person registers as a member, agrees to these terms, and the Operator accepts the registration request.
2. Anyone registering as a member indicates agreement to these terms by reading them during the Site registration process and selecting the "I Agree" option.

Article 5 Service Use Application

1. Individuals registering as members must provide all required information requested by the Site (such as user ID, password, nickname, etc.).
2. Members who use another person’s information, submit false data, or otherwise fail to provide authentic personal information have no rights to use the Site and may be subject to penalties under applicable law.

Section 6: Privacy Policy

The operator does not retain members' passwords provided at sign‑up, and related matters are governed by the site’s privacy policy.
The operator strives to protect members’ personal information, including registration data, in accordance with applicable laws.

Member privacy is handled according to the privacy policy set by applicable law and the site.

However, the operator assumes no responsibility for information exposed due to the member’s own fault.
If a member posts or distributes illegal content—such as material that violates public morals or national security—the operator may, upon request from relevant authorities, review the member’s data and submit it to those authorities.

Section 7: Operator Obligations

(1) When a member’s opinion or complaint is deemed legitimate, the operator must address it as promptly as possible. If personal circumstances prevent immediate action, the operator will make a best effort to follow up with a notice, message, or email after the fact.
(2) To ensure continuous and stable site operation, the operator may require the site to repair or restore equipment without delay when failures or losses occur. In cases of force majeure or unavoidable circumstances affecting the site or operator, site operation may be temporarily suspended.

Section 8: Member Obligations

(1) Members must comply with the terms of this agreement, all site policies, notices, operational guidelines, and applicable laws, and must not engage in actions that interfere with site operations or damage the site’s reputation.
(2) Unless expressly authorized by the site, members may not transfer, gift, or use their service rights or contractual status as collateral to any third party.
(3) Users must exercise great care in managing their ID and password and may not allow third parties to use their ID without the operator’s or site’s consent.
(4) Members must not infringe the intellectual property rights of the operator, the site, or any third party.

Section 9: Service Availability

(1) Service is generally available 24 hours a day, 365 days a year, unless technical or operational constraints arise. The site may temporarily suspend service for scheduled maintenance, upgrades, or replacements on dates and times announced by the site. Planned interruptions will be posted on the site’s homepage, so please check regularly.
(2) The site may also suspend service temporarily or permanently without prior notice in the following situations:
- Urgent system inspections, upgrades, replacements, or malfunctions
- Force‑majeure events such as national emergencies, power outages, or natural disasters
- When a telecommunications provider ceases service as stipulated by the Telecommunications Business Act
- If excessive traffic or other issues disrupt normal service use, the service may be unavailable.
③ When service interruptions occur as described in the preceding clause, the site will notify members in advance via announcements or similar notices. If the interruption is caused by circumstances beyond the site’s control and advance notice is impossible, the site will provide notice after the fact.

Article 10 – Termination of Service Use

â‘  A member who wishes to terminate the usage agreement with the site must submit a cancellation request online personally. Separately, termination of the site usage agreement itself must be handled independently of the site access termination.
② Upon submission of the cancellation request, any site‑related programs provided by the site are automatically removed from the member‑management interface, and the operator can no longer view the applicant’s information.

Article 11 – Restriction of Service Use

Members may not engage in any of the following actions. If a member does, the site may restrict the member’s service access, take appropriate legal measures, terminate the usage agreement, or suspend service for a specified period.
① Registering false information during sign‑up or when updating member details.
② Interfering with another person’s use of the site or misappropriating their information.
③ Impersonating site administrators, staff, or affiliates.
④ Infringing on the personal rights or intellectual property of the site or any third party, or disrupting business operations.
⑤ Illegitimately using another member’s ID.
⑥ Collecting, storing, or disclosing another member’s personal data without their consent.
⑦ Engaging in conduct that can be objectively judged as criminal.
â‘§ Any other actions that violate applicable laws and regulations.

Article 12 – Management of Posted Content

â‘  The operator is responsible for managing and operating all posts and materials on the site. The operator must continuously monitor for inappropriate content, and upon discovering or receiving a report of such content, must delete it and issue a warning to the member who posted it.
Members are responsible for the content they post; therefore, members must not publish material that violates these terms of use.
② If a public authority such as the Information and Communication Ethics Committee issues a corrective request, the operator may delete or relocate posts without the member’s prior consent.
③ The criteria for determining inappropriate content are as follows.
- When the content severely insults or defames another member or a third party.
- When distributing or linking to content that violates public order or good morals.
- When the content encourages illegal copying or hacking.
- When it is advertising intended for profit.
- When the content is objectively recognized as being linked to criminal activity.
- When it infringes copyright or other rights of other users or third parties.
- When it is deemed to violate other applicable laws.
- If the site or its operator receives a request from a third party to halt a post because of alleged defamation, intellectual‑property infringement, or similar rights violations, the post may be temporarily taken down (transmission stopped). The site will follow any lawsuit, settlement, or other decision by the relevant authority that is submitted concerning the requester and the poster.

Article 13 Retention of Posts

If the site operator must discontinue the site due to unavoidable circumstances, they will give members prior notice and make reasonable efforts to facilitate the transfer of posts.

Article 14 Copyright in Posts

① The copyright of a post submitted by a member on the site belongs to that member. The site may not commercially use the post without the poster’s consent, except for non‑profit purposes, and the site retains the right to display the content within the service.
② Members may not commercially use materials posted on the service, such as by arbitrarily processing or selling information obtained through the service.
③ The operator may delete, relocate, or reject registration of any content posted or uploaded by a member that is judged to fall under any of the items listed in Article 12, without prior notice.

Article 15 Liability for Damages

â‘  All civil and criminal liability arising from the site is primarily the responsibility of the member.
② The site will not compensate for damages that result from force majeure events such as natural disasters, or from the member’s intentional or negligent actions.

Article 16 Disclaimer

â‘  The operator is exempt from liability for any loss of expected benefit, or for damages arising from the selection or use of service materials provided by the site.
② The operator is exempt from liability for interruptions caused by the site’s service infrastructure or by telecommunications services provided by other carriers, and any damages related to the site’s service infrastructure are governed by the site’s terms of use.
The operator assumes no responsibility for any material that members store, post, or transmit.
If service disruptions occur due to a member’s fault, the operator is not liable.
The operator is not responsible for any activities—such as data transmission or other community interactions—between members or between members and third parties, whether inside or outside the service.
The operator does not guarantee the authenticity, reliability, or accuracy of material posted or transmitted by members, nor any content that members can obtain from this site.
If members trade goods or conduct other transactions through the service, the operator is not liable for any resulting damages.
The operator bears no responsibility for any disputes that arise between members or between members and third parties, unless the operator is at fault.
The operator is not liable for member losses caused by system failures during equipment maintenance, inspections, repairs, or replacements, or software operation, unless caused by intentional wrongdoing or gross negligence; nor for failures due to third‑party attacks, undiscovered viruses, or other force‑majeure events beyond the operator’s control.

Supplementary Provisions

These terms <Effective from the site launch date>.

Privacy Policy

MS Venter (hereinafter referred to as “the Company”) establishes and publishes these privacy processing guidelines to protect data subjects’ personal information under Article 30 of the Personal Information Protection Act and to address related concerns promptly and smoothly.

Article 1 (Purpose of Personal Information Processing)
The Company processes personal information for the purposes listed below. Collected data will not be used for any other purpose, and if the purpose changes, the Company will obtain separate consent in accordance with Article 18 of the Personal Information Protection Act and take any other required actions.

1. Website membership registration and management
Personal information is processed to confirm membership intent, verify identity for member‑only services, maintain and manage membership status, conduct limited identity verification, prevent fraudulent use, verify parental consent for children under 14, provide notices, handle inquiries, and address complaints.

2. Provision of goods or services
Personal information is processed for product delivery, service provision, sending contracts and invoices, delivering content, offering personalized services, identity and age verification, payment processing and settlement, and debt collection.

3. Complaint handling
Personal information is processed to verify the complainant’s identity, confirm the nature of the complaint, contact for fact‑finding, and notify the outcome of the handling process.

Article 2 (Processing and Retention Period of Personal Data)
The Company processes and retains personal data only for the period required by law or the period consented to by the data subject at the time of collection.
The specific processing and retention periods are as follows:

1. Website membership registration and management: until the member withdraws from the website.
However, if any of the following circumstances apply, data will be retained until the circumstance ends:
1) Ongoing investigations or inquiries related to violations of applicable laws: until the investigation or inquiry concludes.
2) Outstanding creditor‑debtor relationships arising from website use: until those relationships are fully settled.

Article 5 (Rights of Users and Their Legal Representatives and How to Exercise Them)

Data subjects may exercise any of the following privacy rights with the Company at any time.
1. Request to access personal data
2. Request correction of errors or inaccuracies
3. Request deletion
4. Request suspension of processing
These rights can be exercised by submitting a written request, calling, emailing, or faxing the Company, and the Company will act without undue delay.
If a data subject requests correction or deletion of personal data, the Company will refrain from using or disclosing that data until the correction or deletion is completed.
The rights in paragraph 1 may also be exercised through a legal representative or an authorized agent, provided a power of attorney in the format specified in Appendix 11 of the Enforcement Rules of the Personal Data Protection Act is submitted.
Data subjects must not violate applicable laws, including the Personal Data Protection Act, by infringing on the personal data or privacy of themselves or others that the Company processes.

Article 6 (Categories of Personal Data Processed)
The Company processes the following categories of personal data:

1. Website membership registration and management
Required items: company name, full name, title, phone number, email
Optional items: referral source, awareness channel

2. Provision of goods or services
Required items: company name, full name, title, phone number, email
Optional items: referral source, awareness channel

3. During the use of internet services, the following personal data items may be automatically generated and collected.
IP address, cookies, MAC address, service usage records, visit logs, error usage records, etc.

Article 7 (Destruction of Personal Data)
â‘  The company shall promptly destroy personal data that is no longer needed due to the expiration of the retention period or achievement of the processing purpose.
② If, after the consented retention period has expired or the processing purpose has been achieved, the personal data must be retained under other laws, the company shall preserve it by transferring it to a separate database or storing it in a different location.
③ The procedures and methods for destroying personal data are as follows.
1. Destruction Procedure
The company selects the personal data subject to destruction and, with approval from the company’s personal data protection officer, destroys the data.
2. Destruction Methods
The company destroys electronically stored personal data using methods such as low‑level formatting to make records unrecoverable, and destroys paper records by shredding or incineration.

Article 8 (Measures to Ensure the Security of Personal Data)
The company implements the following measures to ensure the security of personal data.
1. Administrative measures: establishment and implementation of internal management plans, regular employee training, etc.
2. Technical measures: management of access rights to personal data processing systems, installation of access control systems, encryption of unique identifiers, etc., and installation of security programs.
and other encryption, security program installations.
3. Physical measures: access control for computer rooms, data storage rooms, etc.

Article 9 (Installation, operation, and refusal of automatic personal data collection devices)
(1) The company uses cookies to store user information and retrieve it as needed in order to provide personalized services.
(2) A cookie is a small piece of data sent by the server (http) that runs the website to the user's browser, and it may also be stored on the user's hard drive.
a. Purpose of using cookies: to analyze each service and website visited by the user, usage patterns, popular search terms, secure connection status, etc., and to deliver optimized information to the user.
b. Installing, operating, and refusing cookies: Tools menu at the top of the web browser>Internet Options>You can refuse cookie storage by adjusting the options in the privacy menu.
c. Refusing cookie storage may make it difficult to use personalized services.

Article 10 (Personal Data Protection Officer)
(1) The company designates a Personal Data Protection Officer who oversees all personal data processing activities and handles data subject complaints and remediation as follows.

â–¶ Personal Data Protection Officer
Name: O Manseok
Title: Representative
Contact: 1544-7120
※ This connects to the personal data protection department.

â–¶ Personal Data Protection Department
Department: Development Team
Contact Person: Lee Seongjae
Contact: adffewr@benter.co.kr

Data subjects may direct any privacy‑related inquiries, complaints, or requests for redress arising from use of the company’s services to the privacy officer or the responsible department. The company will respond and address such inquiries without delay.

Article 11 (Request for Access to Personal Data)
Data subjects may submit a request to access their personal data under Article 35 of the Personal Information Protection Act to the department below. The company will strive to process access requests promptly.

â–¶ Department for Receiving and Processing Access Requests
Department: Operations Team
Contact: O Chae‑hyun
Email: boram03@benter.co.kr

Article 12 (Remedies for Rights Violations)
Data subjects may contact the following agencies for redress or counseling regarding personal data breaches.

â–¶ Personal Data Breach Reporting Center (operated by Korea Internet & Security Agency)
- Scope: Reporting personal data breach incidents, requesting counseling
- Website: privacy.kisa.or.kr
- Phone: 118 (no area code needed)
- Address: 3rd Floor, Personal Data Breach Reporting Center, 9 Jinheung‑gil, Naju‑si, Jeollanam‑do 58324 (Bitgaram‑dong 301‑2)

â–¶ Personal Data Dispute Mediation Committee
- Scope: Filing personal data dispute mediation requests, collective dispute mediation (civil resolution)
- Website: www.kopico.go.kr
- Phone: 1833‑6972 (no area code needed)
- Address: 4th Floor, Government Complex Seoul, 209 Sejong‑daero, Jongno‑gu, Seoul 03171

▶ Supreme Prosecutors' Office Cyber Crime Investigation Unit: 02‑3480‑3573 (www.spo.go.kr)
â–¶ Cyber Safety Division, National Police Agency: 182 (http://cyberbureau.police.go.kr)

Article 13 (Implementation and Amendment of the Privacy Policy)
This privacy policy takes effect on January 31, 2024.