Skip to main content

​
Article 1(Purpose and Definitions)

These Terms govern the use of the A.drop service provided by Open Rhapsody Co., Ltd. ① These Terms are intended to define the rights, obligations, responsibilities, terms of use, and procedures between Open Rhapsody Co., Ltd. (hereinafter referred to as the “Company”) and Publishers regarding the use of the A.drop service (hereinafter referred to as the “Service”) provided by the Company. ② The terms used in these Terms are defined as follows. ③ Terms not defined in these Terms follow the meanings established by relevant laws and the Company’s individual policies. Otherwise, general trade practices apply.

​
Article 2(Service Composition and Ad Types)

① The Service consists of Ad.Control (the core service) and supplementary services that Publishers may choose as needed. ② The content of each service is as follows.
  1. Ad.Control: An ad server solution primarily for reserved ads. Publishers can create/manage ad spaces and view reserved ad delivery status and revenue performance through this service.
  2. Ad.Note: A supplementary service that promotes Publisher ad products to Advertisers and brokers transactions. On the Ad.Note advertising platform (adnote.adrop.io), Publisher ad products are listed and Advertisers can directly reserve/purchase them. On the Ad.Note community, product brochures and advertising benefits registered by Publishers in the console are displayed. Details are per Article 8.
  3. Bidding Backfill Ads: A supplementary service that fills empty ad spaces without reserved ads to earn additional revenue. Details are per Article 9.
③ Supplementary services are provided only to Publishers who apply for them. Ad.Note requires a listing application for ad products per Article 8(3), and Backfill Ads requires an application at the Ad Unit level per Article 9(1). Failure to apply for supplementary services does not restrict Ad.Control’s reserved ad delivery. ④ The Company provides the following ad types.
  1. Banner Ads
    • Standard ads displayed in designated ad spaces within an app or website.
  2. Interstitial Ads
    • Full-screen ads that cover the entire app screen, typically displayed at screen transitions.
  3. Rewarded Ads
    • Full-screen ads similar to interstitial ads that grant rewards (e.g., game items, points) to End-Users who watch the ad to completion.
    • Only video creatives are used, but Ad.Control fees exceptionally apply at the same rate as image/text creatives. Details are per Article 5(3).
  4. Native Ads
    • Ads that blend naturally into the surrounding content of an app or website.
  5. Popup Ads
    • Ads that appear as separate windows over the app screen. Display position and size follow ad space and creative settings.
    • Supports a carousel (slide) feature for browsing multiple campaigns; in this case, each campaign’s creative is counted as an individual impression (see Article 4(2)).
  6. Splash Ads
    • Full-screen ads displayed first when an app launches.
    • Because splash ads have short display windows at app launch, they pre-download the next ad image and temporarily store it on the End-User’s device (retained for up to 7 days).
    • Display timing is controlled by the Company’s server. If loading takes longer than a set time (approximately 1 second), the ad is automatically skipped and not counted as an impression.
⑤ Supported environments by ad type are as follows. ⑥ Regarding the supported environments in the preceding paragraph, the following apply.
  1. Splash ads are shown at the moment an app first launches, so they are supported only in apps, not on websites.
  2. The table in paragraph 5 is based on the effective date of these Terms. The Company may add or adjust supported environments. Changes that discontinue currently used features will be notified in advance per Article 15.

​
Article 3(Ad Products, Pricing Models, and Targeting)

① Publishers compose ad products by bundling their Ad Units and directly set pricing model, unit price, targeting conditions, sales period, etc. However, selling ad products on the Ad.Note advertising platform requires a separate listing application and review. Setting a product as public alone does not automatically list it on Ad.Note. Even after listing is complete, only products set as public are displayed on Ad.Note. Details are per Article 8. ② Publishers may choose one of the following pricing models for each ad product. The pricing models below are the calculation method for ad fees paid by Advertisers to Publishers and are separate from the Ad.Control fees (Article 5) paid by Publishers to the Company. ③ The selection of pricing models follows these rules.
  1. Certain pricing models may not be selectable due to the characteristics of the ad type. In such cases, only selectable models are displayed in the console.
  2. Splash ad products do not support clicks, so they cannot be sold as CPC. When splash ad products are included, CPC cannot be selected in the console.
  3. Splash ads pre-download images and display them at the next app launch (Article 2(4)(6)), so the Company’s server has limitations in real-time impression control. For CPM, there may be discrepancies between target and actual impressions. Splash ad products are therefore recommended to be sold as CPP (period-based fixed pricing).
④ In-house ads follow these rules.
  1. In-house ads are ads that Publishers register directly to promote their own services or content. In-house ads are a type of reserved ad and do not involve Advertiser payments or revenue settlement.
  2. In-house ads are delivered as a lower priority when ad spaces are empty due to no reserved ads (CPM/CPC/CPP) from Advertisers. When reserved ads exist, they take priority.
  3. In-house ads are delivered before bidding backfill ads.
  4. When impressions actually occur, in-house ads are subject to Ad.Control fees (Article 5).
⑤ The order of ad selection is as follows. If no ad exists in a given category, no ad is displayed in that ad space.
  1. Ads reserved by Advertisers (CPM/CPC/CPP)
  2. In-house ads (when no Advertiser-reserved ads exist)
  3. Bidding backfill ads (when no reserved or in-house ads exist, and only for Ad Units with Backfill enabled. See Article 9)
⑥ The Company provides the following targeting.
  1. Audience Targeting
    • Publishers define targeting attributes (e.g., age group, gender, interests, usage behavior) based on their own user information and link them to ad products.
    • Advertisers may select linked targeting attributes as ‘Include’ or ‘Exclude’ when reserving. Publishers may designate certain attributes as mandatory.
    • Ad products with targeting conditions may have premium pricing set by the Publisher.
    • User attribute information used for targeting is transmitted by Publishers via the SDK. Up to 256 attributes may be registered, with each value up to 256 characters.
  2. Contextual Targeting
    • A method that displays ads matching the content the End-User is currently viewing (e.g., a specific post or product page).
    • Publishers transmit contextual information about the current screen when requesting ads, and the Company selects and delivers matching ads.
⑦ Responsibility for obtaining End-User consent for information used in targeting is per Article 11(3). ⑧ In the Ad.Control Console under Settings > Payment Methods, Publishers register payment methods to offer to Advertisers. Only registered methods appear on the Advertiser’s campaign reservation screen, and Advertisers select from among them. The following paragraphs apply to campaigns directly reserved by Publishers from Advertisers. Payment methods and fees for campaigns reserved through Ad.Note follow Ad.Note’s policies and are not individually set by Publishers (see Article 8). ⑨ For bank transfer, the following apply.
  1. Ad fees are deposited directly by the Advertiser to the Publisher’s account and do not pass through the Company.
  2. Tax invoice issuance, deposit confirmation, and receivables management are handled directly by the Publisher.
  3. The Company does not charge payment gateway fees for such ad fees and is not the settlement/payment entity.
⑩ For card payment, the Company handles settlement per the following procedure.
  1. When the Advertiser pays by card, the Company receives the ad fees via payment gateway.
  2. The Company deducts the payment gateway fees per paragraph 11.
  3. The Company pays the remaining amount to the Publisher in cash. Settlement and payment follow Article 10.
⑪ The payment gateway fee rates commonly applied to card payments are as follows. ⑫ The fee rates in paragraph 11 also apply to campaigns reserved through Ad.Note that are paid by card (see Article 10(4)). ⑬ Campaigns directly reserved by Publishers are not subject to the Ad.Note commission (Article 8(7)). Payment gateway fees are deducted only for card payment. Ad.Control fees (Article 5) are incurred based on ad impressions regardless of reservation route or payment method.

​
Article 4(Reserved Ad Impression Standards)

Impressions used as the basis for Ad.Control fees and ad revenue settlement are counted per this Article. ① Impression counting standards by ad type are as follows.
  1. Image/text creatives are counted as impressions when the ad area is at least 50% visible on screen and remains so for at least 0.5 seconds.
  2. Video creatives are counted as impressions when the ad area is at least 50% visible and video playback begins. Completion status or completion rate does not affect impression counting.
  3. Rewarded ads use video creatives but are counted by the same standard as image/text. They are counted as impressions even if the End-User stops watching before receiving the reward.
② To prevent duplicate counting, the following apply.
  1. Creatives received in a single ad request are counted as impressions only once. Even if they leave the screen and return, they are not re-counted.
  2. When a new ad request receives a different creative, that creative is counted as a separate impression.
  3. In popup ad carousels, when the End-User navigates to a different campaign, each campaign’s displayed creative is counted as one impression.
③ The following impressions are not counted as Ad.Control impressions and are not subject to fees or revenue settlement.
  1. Impressions filled by bidding backfill ads (see Article 9(5))
  2. Cases that do not meet the impression counting standards in paragraph 1
④ Regarding reference values, the following apply.
  1. Fee billing and revenue settlement are based on values recorded on the Company’s ad server.
  2. Discrepancies may arise from the Publisher’s own tracking or third-party analytics tools due to differences in measurement methods.
  3. Publishers may raise objections within 30 days of receiving invoices or settlement statements. The Company will reply with the verification result within 15 days of receiving the objection. If errors are found, they will be reflected in the next billing/settlement.
⑤ The Company may change impression measurement methods for improved accuracy or industry standard changes. Changes affecting billing amounts will be notified by email 30 days in advance.

​
Article 5(Ad.Control Fees and Payment)

① The Free tier (Stream) follows these rules.
  1. Up to 10,000 reserved ad impressions per month may be used free of charge.
  2. The free limit is calculated by summing all ad types and creative types, including impressions from rewarded ads and in-house ads.
  3. The free limit is deducted in order of impression occurrence. Impressions beyond the limit are billed at the rates in paragraph 3.
  4. Impressions from bidding backfill ads are neither included in the free limit sum nor subject to paid billing.
  5. If no payment method (e.g., credit card) is registered, service usage is automatically suspended upon exceeding the 10,000 free impressions. During suspension, reserved ad delivery is stopped. Normal usage resumes upon payment method registration.
② The Paid tier (Wave) follows these rules.
  1. Billing begins from the moment the free limit (10,000 impressions/month) is exceeded.
  2. Fees are calculated based on the actually displayed creative, with rates per the price table in paragraph 3. The rate depends on which creative is displayed even in the same Ad Unit. When exceptions are defined in the price table (e.g., rewarded ads), those exceptions apply.
③ Fee rates by creative type are as follows. ④ Application of fees follows these rules.
  1. Rewarded ads use only video creatives, but are billed at KRW 280 per 1,000 impressions (same as image/text) instead of the video creative rate (KRW 560).
  2. The rates in paragraph 3 apply only to reserved ads. Bidding backfill ads are not subject to Ad.Control fees; backfill ads are settled by the commission method per Article 9.
  3. The application of fees/commissions by reservation route and ad type is as follows.
    • Reserved ads directly booked by Publishers: Ad.Control fees (paragraph 3) apply, and no sales commission applies. Payment gateway fees (Article 3(11)) are deducted only when Advertisers pay by card.
    • Campaigns reserved through Ad.Note: Ad.Control fees (paragraph 3) and 20% sales commission (Article 8(7)) apply. For card payments, payment gateway fees are additionally deducted.
    • In-house ads: Ad.Control fees (paragraph 3) apply.
    • Bidding backfill ads: Ad.Control fees do not apply; only the 20% operating commission (Article 9(5)) is deducted.
⑤ Payment procedure is as follows.
  1. Invoice: The Company sends an invoice listing the previous month’s usage and billing amount to the registered email. The invoice separately displays impressions and amounts by creative type.
  2. Automatic Payment (default): On the 5th of every month, fees for the previous month’s usage are automatically charged to the registered credit card.
  3. Tax Invoice Then Manual Payment (upon agreement): By separate agreement with the Publisher, payment may be changed to tax invoice issuance followed by payment. In this case, billing and payment deadlines follow the same standards as the settlement schedule in Article 10(5).
⑥ Handling of non-payment follows these rules.
  1. If fees are not normally paid on the payment date, the Company notifies the Publisher of the non-payment and payment request by email.
  2. The Company grants a grace period of at least 7 days after the notification. Service can be normally used during this period.
  3. If payment is not made after the grace period, service may be suspended or the agreement may be terminated.
⑦ Late fees accrue starting the day after the grace period in paragraph 6 ends. Late fees are not charged if payment is completed within the grace period. The late fee rate is 12% per annum, calculated daily for the delay period, and added to the next month’s invoice. ⑧ Billing entities by region are as follows.
  1. Users in the Republic of Korea: Open Rhapsody Co., Ltd.
  2. Users outside the Republic of Korea: Jumoney Inc., subsidiary of Open Rhapsody

​
Article 6(Term, Termination, and Refund)

① The Service is renewed monthly and automatically renews for the next month unless a separate termination request is made before the usage period ends. ② Termination methods are as follows.
  1. Publishers may request termination at any time by email (contact@adrop.io).
  2. Service may be used until the end of the month in which the termination request is received.
  3. Existing data may be retained by the Company for the period required by relevant laws even after termination.
③ Fee settlement and refund upon termination follow these rules.
  1. The Service is a usage-based post-paid model where the impressions actually occurring in a given month are billed the following month, not a prepaid period-based model. Since there is no prepaid fee, the concept of refund for the remaining period does not apply.
  2. Even upon termination, fees for impressions occurring until termination are normally billed under Article 5 and must be paid by the Publisher.
  3. In case of duplicate payment or overbilling, the Company will refund the difference or deduct it from the next invoice.

​
Article 7(Service Level Agreement, SLA)

① Guaranteed scope and measurement standards are as follows.
  1. Guaranteed Level: The Company guarantees a monthly uptime of 99.9% or higher for reserved ad delivery.
  2. Incident States
    • The Company’s ad server fails to respond to ad requests
    • The server responds with errors
    • Reserved ads are not delivered due to Company system issues despite having ads to deliver
  3. Incident Duration Calculation
    • Incident duration is calculated from the time the Publisher’s report is received to the time the Company notifies the Publisher of recovery completion.
    • If the Company detects the incident first via its own monitoring, calculation begins from the time of Company detection.
    • The recovery completion time is when the Company confirms normal ad delivery has resumed and notifies the Publisher.
    • Incident duration is measured in minutes, and the total incident duration for the month is used to calculate uptime.
    • Periods not reported and not detected by the Company are not included in incident duration. However, if the incident start time is subsequently confirmed by objective materials such as Company server logs and monitoring records, incident duration is calculated from that time.
  4. Cases Not Considered Incidents
    • Ads not displayed due to no reserved ads to deliver
    • Cases where backfill ads are not filled
    • Cases due to Publisher setting errors/app errors or End-User device/network environment
  5. Basis of Measurement
    • Start/end times of incidents are based on the Company’s report reception records, monitoring records, and recovery notification records.
    • Scheduled maintenance times previously notified are excluded from both total time and incident duration.
② Incident compensation standards are as follows.
  1. Base Amount for Credit Calculation
    • Credits are calculated based on the monthly average Ad.Control fees for the 3 months preceding the incident month (excluding VAT).
    • If the usage period is less than 3 months, the monthly average of the actual usage period is used. If there is no prior usage record, the Ad.Control fees of the incident month are used.
    • Ad.Note revenue, backfill revenue, and Advertiser ad fees are not subject to calculation.
    • Publishers using only the Free tier (Stream) with no fees incurred are not eligible for credits, as there are no fees to deduct.
  2. Compensation Amount
    • Compensation is provided as service fee credits (not cash) and is first deducted from Ad.Control fees incurred after approval.
    • Credits not fully deducted in one billing cycle do not expire and are carried over to subsequent invoices.
    • Availability drop is defined as 99.9% minus the actual uptime for the month (e.g., actual uptime 99.5% → drop 0.4%).
③ Compensation claim procedure and limits are as follows.
  1. Step 1 — Incident Report
    • Upon discovering issues such as ads not being delivered, Publishers must promptly report to the technical support email (tech-support@adrop.io), including the time of occurrence, symptoms, and affected Ad Units.
    • Incident duration is calculated from the report reception time, so delayed reports reduce the compensable duration. However, if the Company detected the incident first via monitoring, calculation begins from the Company’s detection time (see paragraph 1(3)).
    • Upon receiving reports, the Company responds per paragraph 4 and, if confirmed as an incident, notifies the Publisher of the fact and scope of impact.
  2. Step 2 — Compensation Claim
    • Uptime is confirmed monthly, so compensation claims can be made after the incident month ends.
    • Publishers must claim compensation by email (contact@adrop.io) by the end of the month following the incident month. Including the Step 1 report details (reception time or reply email) will expedite verification.
    • The Company will review report reception and recovery notification records within 15 days of the claim and notify the approval status and credit amount by email.
    • Approved credits are deducted in order from Ad.Control fee invoices issued after notification. Remaining amounts are carried over until fully deducted.
    • No credits are provided for claims not submitted within the deadline.
  3. Compensation Limits
    • Credits provided for incidents in one month do not exceed 30% of the base amount.
    • Credits are not refundable in cash and cannot be used for purposes other than fee deduction or transferred to third parties.
    • Upon contract termination, unremoved credits expire.
    • The Publisher’s remedy for the Company’s failure to comply with SLA is limited to credits under this Article. However, in case of willful misconduct or gross negligence by the Company, Article 17 applies.
④ Response and resolution times follow these rules.
  1. Reporting Channels
    • Incident reports are received 24 hours a day via the technical support email (tech-support@adrop.io).
    • In preparation for emergency situations where ad delivery is entirely stopped, the Company provides Publishers with emergency contact channels (contact persons or dedicated channels) at the time of contract.
    • When the Company detects an incident first via monitoring, it immediately notifies affected Publishers.
  2. Response and Resolution Times
    • The Company aims to resolve issues within 48 hours. However, resolution may take longer depending on the nature of the issue. In such cases, the Company will provide the reason for the delay and expected schedule, and share progress regularly.
    • The response and resolution times in this section are the Company’s target standards. When causes lie in external factors or reproduction is difficult, times may vary. The Publisher’s remedy for failure to comply is limited to credits under paragraph 2.
  3. Emergency Incident Recovery Procedure
    • Reception/Confirmation: Recognize the incident via report or monitoring and determine the scope of impact.
    • Temporary Measures: Roll back to the previous version, switch to a bypass route, or take other measures to prioritize resuming ad delivery.
    • Recovery: Eliminate the root cause and restore normal state.
    • Normal Confirmation: Verify that ad delivery and metrics have returned to normal, then notify the Publisher of recovery completion.
    • Post-Incident Report: Provide a report on the cause, actions taken, and preventive measures to the Publisher within 5 business days of recovery completion.
⑤ The following cases are excluded from incident duration counting and credit compensation.
  1. Suspensions due to previously notified scheduled maintenance and emergency security measures
  2. Force majeure such as earthquakes, typhoons, floods, wars, and epidemics
  3. Internet network failures by telecommunications carriers, or widespread outages by cloud providers
  4. Publisher’s incorrect settings or operational inexperience
  5. Publisher’s own app/website errors or Publisher server issues
  6. End-User’s device issues or network environment
  7. Policy changes or outages by external platforms such as Google and Apple
  8. External ad network (backfill) outages or ad shortages
  9. Cases where ads are not displayed due to no reserved ads to deliver (no-fill)
  10. Issues arising from continued use of SDK versions whose support has ended by the Company (see Article 13(4))
  11. Issues arising during the use of beta/pilot features (see Article 13(5))
  12. Periods when the Company suspended the Service due to the Publisher’s reasons such as non-payment or prohibited conduct (see Article 12(4) and Article 15(3))
  13. Suspensions due to work performed at the Publisher’s request

​
Article 8(Ad.Note Service)

① Ad.Note is a supplementary service of Ad.Control that promotes Publisher ad products to Advertisers and enables Advertisers to directly reserve and purchase them. It consists of the following two channels. ② Ad.Note usage follows these rules.
  1. Usage is chosen by the Publisher. Ad.Note is not automatically used; ad products are listed only when the Publisher applies for listing per paragraph 3. Failure to apply does not affect Ad.Control’s reserved ad delivery.
  2. Advertisers can browse ad products listed on the Ad.Note advertising platform and reserve/purchase campaigns per the pricing model and targeting conditions defined in Article 3.
  3. Ad.Note is available to Publishers using the Wave tier.
  4. Revenue generated through Ad.Note is subject to the sales commission in paragraph 7, and Ad.Control fees are separately incurred for ad impressions per paragraph 8. Settlement and payment of revenue follow Article 10.
③ Ad product listing procedure and display conditions are as follows.
  1. Listing is not automatic. Publishers must directly apply for listing in the Ad.Control Console.
  2. The Company reviews submitted ad products. Products that pass review begin display on the Ad.Note advertising platform (adnote.adrop.io).
  3. Even after listing is complete, only products set as public by the Publisher are displayed on the Ad.Note advertising platform. Changing a product to private stops its display on the platform.
  4. On the Ad.Note community, product brochures and advertising benefit information registered by Publishers in the console are displayed. Publishers must manage registered materials to ensure they are factually accurate. To modify or take down materials, Publishers change the registration content in the console.
  5. The Company may reject listings or halt display when ad products or registered materials do not comply with relevant laws, Company policies, or Advertiser protection standards, and will inform the Publisher of the reason.
④ Campaigns reserved through Ad.Note are distinguished in the Ad.Control Console as follows, allowing Publishers to verify Ad.Note reservations at any time.
  1. In the Reservation Management menu, a blue Ad.Note logo is displayed next to the campaign name.
  2. The contract manager of the campaign is displayed as ‘Ad.Note’.
⑤ Campaign approval authority rests with Publishers per these rules.
  1. Even when Advertisers request reservations through Ad.Note, campaigns are not immediately delivered. Publishers directly decide whether to approve campaigns.
  2. Publishers may review campaign details (Advertiser, period, placement, creatives, amount, etc.) in the Reservation Management menu of the Ad.Control Console and approve or reject them.
  3. Publishers may reject campaigns that do not match their service characteristics or ad policies, or that include inappropriate creatives. The Company does not intervene in Publisher approval decisions.
  4. Only approved campaigns are delivered. Unapproved campaigns are not delivered, and no sales commission or ad fee settlement occurs in such cases.
  5. For Advertiser protection, Publishers must decide on reservation approval before the campaign start date. Publishers bear responsibility for damages to Advertisers caused by unjustified delays in approval decisions.
⑥ Other campaign operation matters are as follows.
  1. Payment, cancellation, and penalty details for reserved ads are governed by the separate 「Ad.Note Campaign Reservation Terms」, which takes precedence.
  2. If Advertisers cancel or change campaigns, penalties defined in the relevant policy may be charged, potentially affecting Publisher revenue.
⑦ Sales commission follows these rules.
  1. The Company deducts 20% of total ad revenue generated through Ad.Note as sales commission.
  2. Scope of Application: Regardless of prior transaction history or direct sales relationships between the Publisher and Advertiser, a 20% sales commission applies to all campaigns reserved through the Ad.Note platform. All campaigns confirmed as Ad.Note reservations per paragraph 4 fall under this scope.
  3. Publishers cannot request exemption or reduction of sales commission on the grounds that the Advertiser was an existing customer.
  4. If a separate sales distribution agreement exists, the commission terms of that agreement take precedence.
⑧ Separate Ad.Control fees follow these rules.
  1. When campaigns reserved through Ad.Note are delivered, Ad.Control fees (Article 5) are incurred separately from the 20% sales commission for the campaign’s ad impressions.
  2. Accordingly, Publishers are subject to both of the following.
    • Receive settlement of revenue after deducting the 20% sales commission from ad revenue.
    • Separately bear Ad.Control fees for impressions generated by the campaign.
  3. Ad.Control fees are calculated by creative type rates per Article 5(3) and included in the monthly fee invoice.
  4. Since revenue settlement and fee billing follow different schedules, fees are not deducted in advance from settlement amounts.

​
Article 9(Bidding Backfill Ads)

① The overview and usage conditions of bidding backfill ads are as follows.
  1. Backfill ads are a supplementary service of Ad.Control that automatically fills the Publisher’s ad spaces with external ad network ads via real-time bidding when both reserved ads and in-house ads are unavailable.
  2. Backfill ads are not enabled by default. Publishers must apply for ‘Turn on Backfill Ads’ at the Ad Unit level in the Ad.Control Console to activate them. Units without application will not display ads when no ads are available.
  3. Even for activated units, backfill ads are delivered only after the Company connects external ad network placements to the unit.
  4. When using automatic refresh of banner ads (replacing with new ads at set intervals), if the backfill ad response does not arrive within a set time (approximately 3 seconds) at the refresh point, the refresh is skipped and the existing ad is retained.
② Backfill ads depend on formats provided by external ad networks. Not all ad types are supported in all environments. Supported ranges by environment and ad type are as follows. ③ Environment-specific notes are as follows.
  1. Web Environment
    • When native ad spaces on websites have no reserved ads, backfill ads are not displayed in native form (blending with content). They may be displayed as standard display ads in the Publisher’s designated area, or not displayed.
    • Web backfill ads can be selected to either automatically fit ad area size (responsive) or fit a Publisher-specified height (fixed).
  2. App Environment
    • Popup ads and splash ads do not support backfill in any environment. Without reserved ads, these ads are not displayed.
④ Characteristics of bidding ads follow these rules.
  1. Due to the real-time auction structure of bidding backfill ads, pre-reviewing ad content before display may be technically impossible.
  2. The Company provides filtering features to screen inappropriate ads but cannot guarantee complete blocking in all cases.
  3. Publishers who wish to block specific types of ads may use the blocking settings provided by the Company.
  4. Backfill ad fill rates, unit prices, and revenue levels vary depending on external ad network market conditions. The Company does not guarantee specific levels.
⑤ Backfill ad commission follows these rules.
  1. The Company deducts a 20% operating commission from backfill ad revenue and pays the remaining amount to the Publisher in cash (payment = backfill ad revenue × 80%).
  2. Revenue used as the settlement basis is the amount finalized and paid by the external ad network for that month’s backfill ad performance. If the external ad network deducts revenue due to invalid traffic, the reduced amount serves as the basis.
  3. Backfill ad impressions are not subject to Article 5 fees. Ad.Control fees are not charged; the only cost borne by the Publisher is the 20% operating commission in this paragraph.
  4. Revenue settlement, payment, and exchange rate application follow Article 10.

​
Article 10(Revenue Settlement and Payment)

This Article defines the settlement procedure for revenue paid by the Company to Publishers. The billing and payment of Ad.Control fees paid by Publishers to the Company follow Article 5. ① The scope of application of this Article is as follows. ② For campaigns directly booked by Publishers and paid by bank transfer, ad fees do not pass through the Company and are not subject to settlement under this Article. ③ The reference month (M) in the settlement schedule varies by settlement target as follows. Even if a campaign spans multiple months, settlement is processed at once based on the month the campaign ended. ④ Payment amount is calculated by deducting the following items from ad revenue.
  1. When campaigns reserved through Ad.Note are paid by card, both the 20% sales commission and payment gateway fees are deducted, and the remaining amount is paid to the Publisher.
  2. Taxes and Public Charges: If withholding tax or other public charges arise under the laws of the Republic of Korea or the Publisher’s country of residence, the Company deducts the statutory amount before payment. Publishers eligible for exemption/reduction must submit relevant supporting documents in advance.
  3. Uncollected Amounts: Amounts not actually collected by the Company due to payment cancellation, refund, or card approval reversal are excluded from settlement, or deducted from the next settlement if already paid.
⑤ Settlement and payment schedule is as follows.
  1. Example: For revenue from campaigns ending in March and backfill revenue occurring in March, settlement statements are sent by April 5. If the tax invoice is issued by April 10, payment is made within 30 days from that date.
  2. For backfill ads, if there are delays in receiving confirmed revenue from external ad networks or other reasons beyond the Company’s control, the Company will inform the Publisher of the reason and expected payment date, and pay without delay after confirmation.
⑥ Exchange rate application follows these rules.
  1. Overseas ad revenue is generated in USD and converted to KRW for payment.
  2. Exchange rates are based on the average KRW/USD standard exchange rate published by the Bank of Korea Economic Statistics System (ECOS) for the revenue generation month (M), with amounts under 1 KRW rounded up in KRW conversion.
⑦ Objections to figures and amounts in settlement statements follow Article 4(4). ⑧ The Company is not liable for payment delays or errors caused by external parties such as credit card companies and payment gateways (PG), and will cooperate sincerely in resolving issues.

​
Article 11(Data and Privacy Protection)

① Data ownership follows these rules.
  1. Data generated and managed through the Service (e.g., ad statistics, revenue information) belongs to the Publisher.
  2. The Company does not sell or share such data with third parties without the Publisher’s explicit consent. However, in case of court orders or legitimate legal requests, the Company may respond in accordance with relevant laws.
② Application of the privacy policy follows these rules.
  1. All matters concerning personal information processing (items collected, purposes, retention periods, destruction methods, international transfer, End-User rights, etc.) are defined in the Company’s 「Privacy Policy」, which takes precedence over these Terms.
  2. The Privacy Policy is always posted on the Company’s website. Changes are notified per the procedures defined in the policy.
③ Responsibility for obtaining End-User consent follows these rules.
  1. Publishers bear sole responsibility for obtaining lawful consent (personal information collection/use, advertising identifier collection, personalized ad receipt, third-party provision, etc.) from End-Users of their app/web under relevant laws (Personal Information Protection Act, GDPR, CCPA, etc.).
  2. If a dispute arises from End-Users or third parties due to the Publisher’s failure to fulfill the obligations in the preceding item, the Publisher must indemnify the Company at its own expense and responsibility and compensate all damages incurred by the Company.
④ The Company holds the status of Processor processing data under the Publisher’s delegation. The Publisher bears legal responsibility as the Controller determining the purpose and means of data collection and use. ⑤ Publishers must not transmit the following information to the Company via the SDK’s user identifier (setUid), user properties, or custom events.
  1. Sensitive information under Article 23 of the Personal Information Protection Act (information on health and medical treatment, sex life, thoughts/beliefs, political opinions, labor union/political party affiliation, genetic information, criminal records, etc.)
  2. Unique identification information under Article 24 of the Personal Information Protection Act (resident registration number, passport number, driver’s license number, foreign resident registration number)
  3. Personal information of children under 14 without legal guardian consent
⑥ If the Company confirms that such information has been transmitted, it may block reception of the data or delete it, and will notify the Publisher. Damages arising from the transmission of such information are the responsibility of the Publisher.

​
Article 12(Publisher Obligations)

① Publishers must properly integrate the Company-provided SDK into their app or website. Technical documentation and inquiry channels for integration are per Article 13(3). Responsibility for integration and console operation is as follows.
  1. Verification of Integration Results: After integrating the SDK, Publishers must directly verify that ads are properly displayed in the intended positions. Publishers bear responsibility for consequences of incorrect integration (ads not displayed or displayed in wrong placements).
  2. Console Operations: Settings and operations performed in the console under the Publisher’s account (ad product/price/targeting settings, campaign creation/modification/start/stop, creative approval, payment method registration, etc.) are deemed the Publisher’s intent.
  3. Verification Before Saving: Before saving settings or starting campaigns, Publishers must verify that the content matches their intent. Consequences attributable to misunderstanding the interface are the Publisher’s responsibility.
  4. Impressions from Incorrect Settings: Even when ads are delivered due to Publisher setting errors, actual impressions are billed per Article 5.
  5. Inquiries: If uncertain about console usage or setting results, Publishers may inquire with the Company before starting campaigns.
② Ad space settings follow these rules.
  1. Publishers must accurately use the unique Unit ID issued by the Company for each ad space.
  2. Publishers must not misappropriate others’ Unit IDs or use test Unit IDs in actual services.
  3. Responsibility for managing authentication information (account information, API keys, etc.) lies with the Publisher. If leakage is suspected, Publishers must immediately notify the Company.
③ Publishers must not engage in the following acts.
  1. Displaying ads on pages containing content that violates relevant laws or Advertiser policies (e.g., adult content, gambling, hate speech)
  2. Intentionally hiding or obscuring ads from End-Users
  3. Disassembling, decompiling, or modifying the SDK without the Company’s prior written consent
  4. Reselling the Service to third parties or lending Service usage rights without the Company’s prior written consent
  5. Clicking ads oneself or requesting/urging others to click (click fraud)
  6. Artificially generating impressions or clicks using automated programs or scripts
  7. Deceiving End-Users into clicking ads
Items 5 through 7 of this paragraph apply only to placements where campaigns reserved through Ad.Note are delivered and to Ad Units with backfill ads activated. Items 1 through 4 apply to all Ad Units. ④ If a Publisher engages in the prohibited acts in the preceding paragraph, the Company may suspend the Service or terminate the agreement without prior notice. If damages are incurred by the Company, the Publisher must compensate.

​
Article 13(Service Provision Method and Support Scope)

① The Service is a standard cloud service (SaaS) provided to all Publishers with the same features and manner. The Company provides the Service as-is (in the state it is currently provided) and does not provide feature development, interface modifications, dedicated server construction, or separate version distribution for individual Publishers. ② The scope of warranty is as follows.
  1. The Company guarantees the monthly uptime (SLA) for reserved ad delivery specified in Article 7 but does not guarantee the following.
    • That the Service meets a specific purpose or business plan of the Publisher
    • That the Service is free from errors or interruptions
    • Specific levels of ad revenue, ad prices, or fill rates
    • Consistent operation on specific devices, OS versions, or browsers used by the Publisher
  2. Ad revenue varies depending on ad market conditions, the Publisher’s user base and characteristics, ad placement, etc.
③ The scope of technical support is as follows.
  1. Technical Inquiries: Technical inquiries such as SDK integration and ad delivery errors are received at tech-support@adrop.io.
  2. Other Inquiries: Non-technical inquiries such as contracts, fees, settlement, and termination are received at contact@adrop.io.
  3. Technical documentation is available on the Company’s website (help.adrop.io).
  4. Support scope is limited to issues with the Company-provided SDK and console themselves. Publisher app/website development, debugging, server operation, and design work are not included in the support scope.
④ SDK version support policy follows these rules.
  1. Publishers must strive to keep the Company-provided SDK up to date.
  2. The Company may end support for specific SDK versions due to security, external platform policy changes, technical support termination, etc. In such cases, notice is provided by email 30 days in advance.
  3. The Company is not liable for errors, ad non-delivery, or revenue loss arising from continued use of unsupported versions. Such cases are excluded from SLA compensation.
⑤ Features labeled as ‘beta’, ‘pilot’, or ‘preview’ are not formal services and may be changed or discontinued without notice. SLA and compensation rules do not apply to beta features. ⑥ Third-party services follow these rules.
  1. Bidding backfill ads are provided through third-party ad networks.
  2. Advertiser payments are processed through payment gateways such as Toss Payments and Stripe.
  3. Publishers must also comply with the policies and terms of such third parties. The Company is not liable for account suspension, ad cessation, or revenue non-payment due to third-party policy violations.
⑦ The Company routinely validates Publisher ad requests for service stability and invalid traffic prevention, and may not deliver ads to requests that fail validation. This follows these rules.
  1. The rules and detailed standards used in validation (thresholds, criteria, request frequency limits, etc.) are not disclosed, as disclosure would enable circumvention of those standards.
  2. Requests not delivered are not counted as impressions, and no Ad.Control fees are incurred for them.
  3. Ad non-delivery due to measures under this paragraph is not considered an incident under Article 7. The Company is not liable for Publisher revenue reductions arising therefrom.

​
Article 14(Intellectual Property Rights)

① Company rights follow these rules.
  1. All intellectual property rights to all software, code, SDK, documents, designs, databases, and other assets related to the Service belong to the Company.
  2. Publisher use of the Service does not transfer ownership or intellectual property rights of the preceding assets to the Publisher. The Publisher only holds the usage rights defined in paragraph 4.
② Publisher content follows these rules.
  1. Rights and responsibility for content provided by Publishers through their app/website belong entirely to the Publisher.
  2. The Company does not use Publisher content for purposes other than ad delivery.
③ Data usage permission follows these rules.
  1. Publishers permit the Company to analyze and process service usage data for service provision, service improvement, statistics generation, and development of new services.
  2. Even in this case, the Company does not use personally identifiable information and processes only anonymized information or statistical form under the Personal Information Protection Act. When processing pseudonymized information, the Company complies with the procedures and safety measures defined in Articles 28-2 and 28-4 of the same Act.
④ SDK usage rights follow these rules.
  1. The Company grants Publishers the right to use the SDK only for the purpose of displaying ads on Publisher-operated apps/websites during the contract period.
  2. This right is non-exclusive and may not be transferred to third parties or sublicensed (resold, leased, etc.).
  3. This right merely enables SDK use and does not transfer ownership or intellectual property rights of the SDK.
  4. Publishers may not use the SDK in ways prohibited in Article 12(3) (disassembly, decompilation, modification, third-party resale, etc.).
  5. Upon contract termination, this right expires simultaneously. Publishers must immediately cease SDK use and remove the SDK from subsequently distributed app/website versions.

​
Article 15(Service Changes and Suspensions)

① Service content changes follow these rules.
  1. The Company may change all or part of the Service as needed for operations or technology.
  2. Important changes unfavorable to Publishers (e.g., fee increases, discontinuation of major features, changes to impression measurement methods) will be notified by email 30 days in advance, including content and effective date.
  3. Urgent changes (e.g., security vulnerability responses) may be made without prior notice, in which case ex-post notification is provided.
② The Company may temporarily suspend all or part of the Service in the following cases. Suspensions are notified by email in advance; if prior notification is impossible, ex-post notification is provided.
  1. Unavoidable cases such as scheduled system maintenance, equipment replacement, or malfunctions
  2. When key telecommunications carriers under the Telecommunications Business Act suspend telecommunications services
  3. Force majeure such as natural disasters
③ The Company may entirely suspend a Publisher’s ad delivery in the following cases. Revenue losses during this period are not subject to SLA compensation.
  1. Non-payment: Fees not paid after the grace period in Article 5(6) has passed
  2. Legal/Policy Violation: Content violating relevant laws or Advertiser policies on the Publisher’s app/website
  3. Security Incident: Publisher account or authentication information leaked, causing or potentially causing unauthorized delivery
  4. External Demand: Orders from relevant authorities or demands from external platforms such as Google/Apple
  5. Advertiser Protection: Serious harm to Advertisers has occurred or is clearly imminent
④ When suspending under the preceding paragraph, the Company notifies the reason and lifting conditions together. However, in cases requiring immediate action such as paragraphs 3(3), (4), and (5), the Company may suspend first and notify without delay. When the Publisher resolves the cause and notifies the Company, the Company will confirm and resume delivery without delay.

​
Article 16(Amendments to the Terms)

① The Company may amend these Terms. Upon amendment, the content and effective date are notified by email 30 days in advance. ② If Publishers disagree with the amended Terms, they may terminate the agreement before the effective date. ③ If no termination is expressed by the effective date, or if the Service is continuously used after the effective date, the amended Terms are deemed accepted.

​
Article 17(Limitation of Liability)

① The Company is liable for direct damages incurred by Publishers due to failure to comply with the specified service level (SLA) or technical defects. The Company’s liability shall not exceed the fees for the immediately preceding one month from the date of damage occurrence. ② The limitation of liability in paragraph 1 does not apply to damages caused by the Company’s willful misconduct or gross negligence. The Company bears liability under relevant laws in such cases. ③ The Company is not liable for damages caused by the following.
  1. Publisher negligence (SDK integration errors, SDK misuse, use of unsupported versions, console setting errors, etc.)
  2. Fault of third parties such as Advertisers, ad networks, payment gateways, and telecommunications carriers
  3. Force majeure such as earthquakes, typhoons, floods, wars, and epidemics
  4. Issues due to End-User device, network, or browser environments
  5. Indirect/consequential damages such as ad revenue reductions or unmet expected revenue
④ Disputes arising during campaign operation follow these rules.
  1. If disputes or damages arise between Publisher and Advertiser due to the Publisher’s incorrect SDK integration or console operation, the Publisher bears responsibility. The following cases apply.
    • Setting campaign period, budget, unit price, or targeting differently from intent
    • Accidentally starting or stopping campaigns, or registering/approving incorrect creatives
    • Incorrectly connecting Ad Units or removing them from placements, resulting in ads not being delivered per contract
    • Misunderstanding console screens or features
  2. The Company sincerely cooperates in cause identification and provision of delivery/performance data for such disputes but does not bear responsibility for compensation to Advertisers or re-delivery.
  3. The preceding items are distinguished from issues caused by technical defects in the Company’s system. If Company system defects are confirmed, Article 7 and paragraph 1 apply.

​
Article 18(Dispute Resolution)

① The interpretation and application of these Terms are governed by the laws of the Republic of Korea. ② In case of disputes, both parties will endeavor to resolve them amicably through sincere consultation for at least 30 days before litigation. ③ Litigation related to these Terms shall be under the exclusive jurisdiction of the Seoul Central District Court.

​
Article 19(Miscellaneous)

① These Terms constitute the entire agreement between the parties regarding the use of the Service and supersede all prior oral or written agreements. ② These Terms are written in Korean. In case of discrepancies in meaning between the Korean version and translations, the Korean version prevails. ③ Assignment of rights follows these rules.
  1. Publishers may not assign rights or obligations under this agreement to third parties without the Company’s prior written consent.
  2. The Company may notify Publishers and assign rights when rights are transferred due to merger, division, or business transfer.
④ Even if some provisions of these Terms are deemed invalid under relevant laws, the remaining provisions remain effective. Invalid provisions are replaced with valid content closest to their purpose. ⑤ Notification methods follow these rules.
  1. Company notifications are sent to the email address registered by the Publisher in the console. They are deemed delivered 3 business days after sending. However, if the Publisher actually receives them earlier, they are deemed delivered upon actual receipt.
  2. If the email address changes, Publishers must immediately update it in the console. Publishers bear any disadvantages arising from neglecting this.

​
Addendum

Article 1(Effective Date) These Terms take effect on October 1, 2026. Article 2(Related Documents) Documents applied together with these Terms are as follows.
  1. 「Privacy Policy」
  2. 「Ad.Note Campaign Reservation Terms」