Privacy Policy
This is an English translation of the Korean Privacy Policy (개인정보처리방침). If the two differ, the Korean version prevails.
1990Company (the "Company") provides the K-OTP website (k-otp.dev), console (app.k-otp.dev), documentation (docs.k-otp.dev) and OTP API (api.k-otp.dev) (together, the "Service"). To protect the personal information of data subjects under the Personal Information Protection Act ("PIPA") and other applicable laws of Korea, and to handle related complaints promptly, the Company publishes this Privacy Policy.
Effective date: 2026-10-20
Kakao Login supplement (applies from 2026-10-06)
This supplement applies from 2026-10-06 to members who choose Kakao Login.
- Collection and items: after the member consents on Kakao's consent screen, the Company receives their email address and verification status, nickname, and app-specific member identifier from Kakao Corp. For the sign-in connection, it also stores the access and refresh tokens Kakao issues, their expiry times and the consented scopes. It does not request Kakao profile photos, phone numbers or friends lists.
- Purposes: identifying accounts for sign-up and sign-in, linking an existing account at the member's choice, managing connected accounts and preventing unauthorized sign-ins. A new account uses the nickname as its display name.
- Choice: Kakao Login is optional. Members can use the existing email sign-in without using Kakao Login or consenting to Kakao sharing their information.
- Retention and disconnection: Kakao member identifiers and authentication tokens are deleted when Kakao is disconnected or the K-OTP account is deleted. When the member disconnects on Kakao, the Company verifies the signed disconnection notification, removes that Kakao connection and deletes existing sign-in sessions. The K-OTP account, its email and display name, and organization information remain available through email or other sign-in methods. To delete K-OTP member information too, request account deletion in the console's account settings; the retention periods for member and payment records are in Section 3.
1. Purposes of processing
The Company processes personal information for the purposes below. It does not use it for any other purpose, and if a purpose changes, it takes the required steps, such as obtaining separate consent under Article 18 of PIPA.
- Membership: identifying and signing in members with sign-in links and codes sent by email, managing accounts, inviting organization members, preventing abuse, and sending service notices and notifications
- Providing the Service: issuing and managing apps and API keys, sending and verifying codes at Customers' requests, and providing delivery status and usage
- Payments and settlement: selling credits, granting, using and refunding credits, and keeping those records
- Promotions: granting signup bonus and referral program free credits, preventing duplicate or fraudulent claims, and sending expiry reminders
- Support: reviewing inquiries, investigating, and replying
- Security and reliability: limiting sign-in requests, responding to incidents, preventing security incidents, and meeting legal obligations
- Website and documentation improvement: analyzing usage statistics of the website (k-otp.dev) and the documentation (docs.k-otp.dev) for visitors who agree in the cookie notice
2. Personal information processed and how it is collected
The Company does not collect resident registration numbers or other unique identifiers, sensitive information, or passwords.
- Sign-up and sign-in (entered by the member in the console)
- Required: email address, name (set from the part of the email address before the @ when the account is created; the member can change it)
- Optional: profile image, passkeys (the public key created by the device and authenticator details; fingerprints, face data and other biometrics stay on the member's device and are never sent to the Company)
- Sign-in credentials: the token of the sign-in link and the 6-digit sign-in code sent by email. They are stored only as hashes and can be used once within 15 minutes. Code records are keyed by a hash of the email address instead of the address.
- Session data: session token, IP address, browser details (User-Agent), session creation and expiry time, last used organization
- Organizations and use of the Service (entered by members or created while using the Service)
- Organization name and URL (slug), organization logo (optional), members and their roles, email addresses of invited people (entered by the inviting member)
- App names, API key details (the key itself is not stored; only its hash and its first and last few characters for display), allowed origins and rate limit settings per key
- Notifications and notification preferences, language
- Credit payments (created during payment or received from the payment provider)
- Payment method details (such as card numbers) are entered by the member directly on the checkout page (for USD payments, the checkout page of Creem, the merchant of record); the Company never receives or stores them.
- Sent by the Company to the payment provider (including the merchant of record, Section 5) for USD payments: the paying member's email address, and organization, member and credit pack identifiers
- Stored by the Company for USD payments: the payment provider's order number and customer identifier, product, amount and currency, payment time, the paying member and organization, refunds (amount, reason, status and who handled it)
- Card details entered by the member in the payment window of a KRW card payment are collected directly by the payment agent that operates the window; the Company never receives or stores them.
- The buyer name and mobile phone number that Creb's payment window requires are entered by the member on the console's payment screen; the Company only passes them on to the payment agent to process the payment and does not store them (required; without them KRW card payment cannot be used).
- Sent by the Company to the payment agent for KRW payments: buyer name, mobile phone number, order number, product name, payment amount
- Stored by the Company for KRW payments: the order number and the payment agent's payment key and transaction number, product, amount and currency (supply value and VAT), payment time, the paying member and organization, refunds
- Credit ledger: records of credits granted, used, clawed back on refunds, and free credits granted and expired, per organization
- Free credits and the referral program (created while using the Service)
- Preventing duplicate or fraudulent signup bonuses: a hash (HMAC) of the normalized (e.g. lower-cased) email address, a hash (HMAC) of the sign-up request's IP address range (/24 for IPv4, /48 for IPv6), and the email domain. The email address and IP address themselves are not stored separately for this purpose.
- Referral program: each organization's referral code, accounts that signed up through a referral link and when the link was visited, a hash (HMAC) of the IP address range at sign-up, the referring and referred organizations, and decisions to grant, refuse or take back rewards. To detect self-referrals, the session IP address ranges of the two organizations' owners are compared; no IP address is stored beyond the result.
- Records of free credit expiry reminders (number of recipients)
- Support inquiries (provided by the person by email)
- Name, email address, the inquiry and anything sent with it
- Information generated or collected automatically
- IP address, access time, browser details, cookies (Section 11), request paths, response statuses, errors and other usage logs
- Sign-in rate limit records: counts per IP address and request path, and counts of sign-in emails and failed codes per hash of the email address
- Usage statistics of the website (k-otp.dev) and the documentation (docs.k-otp.dev) (only with consent in that site's cookie notice, Google Analytics): cookie identifiers, pages visited and events, referrers, browser, device and language details, and an approximate location estimated from the IP address
Personal information of Customers' end users (Customers being members who use the API) is described separately in Section 4.
3. Processing and retention periods
The Company processes and keeps personal information within the period set by law or consented to by the data subject, and destroys it without delay once that period ends or the purpose is fulfilled.
- Member information (Section 2, items 1 and 2): until the account is deleted
- Sign-in links and codes: 15 minutes after they are sent (they stop working once used)
- Sessions: at most 30 days. Sessions are deleted on sign-out, and the remaining session records are deleted with the account.
- Organization information: until the organization is deleted. App and API key records are not deleted but kept as revoked, so they still match the credit usage records; when a member deletes their account, the records are unlinked from that member.
- Payment and refund records and the credit ledger (Section 2, item 3): 5 years. When a member deletes their account, the records are unlinked from that member and kept for the period required by law. Records past their retention period are destroyed without delay.
- Signup bonus abuse-prevention hashes (Section 2, item 4): 2 years from the day the grant record is created. They are kept for that period even after the account is deleted, to prevent the same person from claiming twice, and then deleted.
- Referral program records (Section 2, item 4): the record of a sign-up through a referral link (including the IP address range hash) is kept until the account is deleted. Reward decisions are kept as records of free credits granted and taken back, and are unlinked from a member who deletes their account.
- Support inquiry records (Section 2, item 5): 3 years
- Sign-in rate limit records: deleted once the limit window (at most 24 hours) has passed
- Website and documentation usage statistics (Section 2, item 6, with consent): Google Analytics event- and user-level data are deleted after 2 months. Aggregated reports that identify no one may remain afterwards.
- Administrator access and activity records (administrator account, date and time, access information, the target viewed or processed and the action taken): 1 year. Records past that period are deleted without delay.
The following are kept for the periods required by law:
- Records of contracts and withdrawals of offers: 5 years (Act on the Consumer Protection in Electronic Commerce)
- Records of payments and supply of goods: 5 years (same Act)
- Records of consumer complaints and dispute resolution: 3 years (same Act)
- Service access records (logs, access location information): 3 months (Protection of Communications Secrets Act)
4. Personal information of Customers' end users
When a Customer asks the OTP API to send a code, the Company processes personal information of the users of the Customer's service ("end users") on the Customer's behalf. The Customer is the controller of this information; the Company is a processor and processes it only as needed to carry out the Customer's requests.
- Items: the end user's mobile phone number, the code, the message content, metadata the Customer puts in the request, and the IP address of the device that calls the API (used only for rate limiting)
- How it is processed
- Code issue records store only a hash (HMAC) of the phone number, never the number itself.
- Codes are stored only as hashes and are never returned by the API or shown in the console.
- The recipient and sender numbers and metadata of delivery records are stored encrypted, together with a hash and a partly masked value for lookups. About 24 hours after a delivery reaches a final status (delivered, failed, cancelled, unknown), the recipient and sender numbers, their hashes, encrypted and masked values, and metadata outside the allow list are deleted. Delivery status, times, delivery route and identifiers are kept for settlement and incident investigation.
- Rate limits are counted only on hashes (HMAC) of phone numbers and IP addresses; the originals are not stored.
- Phone numbers and message content are sent to the SMS and AlimTalk delivery provider (Section 6) for delivery.
- Retention: number data in delivery records is deleted as described in item 2. Code issue records (including the phone number hash) are kept for one year from issue for credit settlement and usage reporting, then destroyed. Credit amounts used remain separately in the credit ledger described in Section 3, item 2.
- End users should send requests to access, correct or delete their information to the Customer that runs the service. Requests sent to the Company are forwarded to the Customer, and the Company helps the Customer respond.
5. Provision to third parties
The Company provides personal information to third parties only in the cases set out in Articles 17 and 18 of PIPA, such as with the data subject's consent or where a law specifically requires it.
For USD payments, the merchant of record sells the credits to the member as a party in its own right: it processes the payment, issues receipts and invoices, handles taxes and makes refunds. From the effective date of this Policy, only when a member buying credits in USD has been informed of the items in item 1 and has given separate consent before going to the merchant of record's checkout page does the Company provide personal information to Creem, a third party abroad, under Articles 17(1)(1) and 28-8(1)(1) of PIPA. Item 2 describes information sent to Polar for orders paid or attempted through Polar before the switch to Creem, which the previous Privacy Policy described as entrustment; from the effective date of this Policy, nothing new is provided to Polar. The payment method and billing details the member enters on the merchant of record's checkout page are collected by the merchant of record directly under its own privacy notice.
- Armitage Labs OÜ (Creem)
- Recipient: Armitage Labs OÜ (trading as Creem, Estonia)
- Privacy contact: support@creem.io
- Recipient's purposes: concluding and performing the USD credit purchase (payment processing, issuing receipts and invoices, calculating, collecting and remitting taxes, refunds and chargebacks), fraud prevention and compliance with legal obligations
- Items provided: the paying member's email address, and organization, member and credit pack identifiers. Separately, the payment method and billing details (such as name and billing address) the member enters on Creem's checkout page are collected by Creem directly.
- Recipient's retention: under Creem's privacy notice, for as long as reasonably necessary for its purposes or as a legal obligation requires: contractual data for 3.5 years after the contract ends, accounting data for 7 years under the Estonian Accounting Act, and customer due diligence data for 5 years after the relationship ends (longer where the law requires).
- Countries: Estonia. Creem uses service providers inside and outside the European Union and the European Economic Area and states that it applies safeguards such as standard contractual clauses approved by the European Commission to those outside the EU/EEA (it does not name the countries).
- When and how: over the network when the member consents and goes to Creem's checkout page
- Refusing consent and its effect: the member may refuse to consent. Without consent, paid credits cannot be bought in USD; the rest of the Service is not affected.
- Polar Software Inc. (orders before the switch to Creem)
- Recipient: Polar Software Inc. (United States)
- Privacy contact: privacy@polar.sh
- Purposes of the recipient: processing payments and refunds of, and keeping records of, orders paid or attempted through Polar before the switch to Creem
- Items sent: the email address of the member who paid or attempted to pay, and organization, member and credit pack identifiers of those orders. The payment method and billing details the member entered on Polar's checkout page were collected by Polar directly.
- Recipient's retention: under Polar's privacy policy, for as long as needed to provide its services (or longer where the law requires)
- Countries: the United States and other countries where Polar stores information
- When and how: over the network when the member started a credit purchase through Polar, before the switch to Creem. Nothing new is provided to Polar.
- Questions and requests: questions about information already sent to Polar, and requests to delete it or suspend its processing, can be sent to support@k-otp.dev (Section 12); the Company reviews them and forwards them to Polar or takes other necessary steps.
6. Processors
The Company entrusts the following processing to provide the Service:
- Smileserv Inc. (IWINV): sending SMS and KakaoTalk AlimTalk messages at Customers' requests
- Cloudflare, Inc.: hosting and content delivery (CDN) of the website, console and API, serverless runtime (Workers), message queues and state storage for delivery processing (Queues, Durable Objects), storage of profile images, organization logos and database backup copies (R2), database connections (Hyperdrive), service logs
- Smileserv Inc. (IWINV): the server environment of the database that stores member, payment and delivery records, and of the backup copies kept on it (Republic of Korea)
- Creb Co., Ltd.: authorization and cancellation of KRW card payments and operation of the payment window. Items entrusted: buyer name, mobile phone number, order number, product name, payment amount. Retention: until the processing agreement ends, or for the period required by law (for example five years for records of payment and supply of goods under the Act on Consumer Protection in Electronic Commerce). Subcontracting: Creb may subcontract card authorization to a payment gateway (such as KSNET Inc. (KSPAY)).
- Google LLC: usage statistics of the website (k-otp.dev) and the documentation (docs.k-otp.dev) (Google Analytics), only for visitors who agree in that site's cookie notice
- Email delivery: sign-in emails, invitations, notifications and free credit expiry reminders are sent from a mail system the Company operates itself. If this is entrusted to an outside provider, this Policy will be amended and announced.
Creem, which processes USD payments, and Polar, the previous payment provider, receive personal information as third parties (merchants of record), not as processors, and are listed in Section 5. Creb, which processes KRW card payments, is a processor and is listed in this Section.
Under Article 26 of PIPA, the Company's processing agreements set out in writing that processors may not process information beyond the entrusted work, must take technical and managerial safeguards, may subcontract only with restrictions, are supervised by the Company, and are liable for damages, among other things; the Company supervises their processing. Any change to the entrusted work or the processors is published in this Privacy Policy without delay.
7. International transfers
The Company transfers personal information abroad as follows. The transfer to Cloudflare (item 1) is entrustment and storage to provide the Service (perform the contract) under Article 28-8(1)(3) of PIPA; the transfer to Creem (item 2) is the provision to a third party abroad, with the member's separate consent, described in Section 5; item 3 (Polar) is the pre-switch transfer described in Section 5, item 2. Item 4 (Google) is the processing entrusted in Section 6 (website usage statistics), transferred with your consent given in the website's cookie notice under Article 28-8(1)(1) of PIPA.
- Cloudflare, Inc.
- Contact: dpo@cloudflare.com
- Countries: the United States (headquarters) and Cloudflare's data centers worldwide. Profile images, organization logos and database backup copies are kept in storage set to the Asia-Pacific region.
- When and how: over the network whenever the Service is used; database backup copies once a day over a TLS-encrypted connection
- Items: the personal information in Section 2 that is carried in requests to the Service (email address, name, IP address, browser details, cookies, usage logs, profile images and organization logos, etc.), end users' phone numbers and message content entrusted by Customers (while a delivery is processed), and database backup copies for disaster recovery (all of the information in Sections 2 and 4 that is stored in the production database; end users' phone numbers are stored there only as hashes or encrypted values)
- Purpose: the work entrusted in Section 6 (hosting, content delivery, serverless runtime, message queues, file storage, service logs)
- Retention: the periods in Sections 3 and 4, or until the processing agreement ends; database backup copies for 30 days from the day they are made
- Armitage Labs OÜ (Creem): provision to a third party abroad under Section 5, item 1 (with the member's separate consent)
- Recipient: Armitage Labs OÜ (trading as Creem, Estonia)
- Privacy contact: support@creem.io
- Recipient's purposes: concluding and performing the USD credit purchase (payment processing, issuing receipts and invoices, calculating, collecting and remitting taxes, refunds and chargebacks), fraud prevention and compliance with legal obligations
- Items provided: the paying member's email address, and organization, member and credit pack identifiers. Separately, the payment method and billing details (such as name and billing address) the member enters on Creem's checkout page are collected by Creem directly.
- Recipient's retention: under Creem's privacy notice, for as long as reasonably necessary for its purposes or as a legal obligation requires: contractual data for 3.5 years after the contract ends, accounting data for 7 years under the Estonian Accounting Act, and customer due diligence data for 5 years after the relationship ends (longer where the law requires).
- Countries: Estonia. Creem uses service providers inside and outside the European Union and the European Economic Area and states that it applies safeguards such as standard contractual clauses approved by the European Commission to those outside the EU/EEA (it does not name the countries).
- When and how: over the network when the member consents and goes to Creem's checkout page
- Refusing consent and its effect: the member may refuse to consent. Without consent, paid credits cannot be bought in USD; the rest of the Service is not affected.
- Polar Software Inc.: Section 5, item 2 (orders before the switch to Creem)
- Recipient: Polar Software Inc. (United States)
- Privacy contact: privacy@polar.sh
- Purposes of the recipient: processing payments and refunds of, and keeping records of, orders paid or attempted through Polar before the switch to Creem
- Items sent: the email address of the member who paid or attempted to pay, and organization, member and credit pack identifiers of those orders. The payment method and billing details the member entered on Polar's checkout page were collected by Polar directly.
- Recipient's retention: under Polar's privacy policy, for as long as needed to provide its services (or longer where the law requires)
- Countries: the United States and other countries where Polar stores information
- When and how: over the network when the member started a credit purchase through Polar, before the switch to Creem. Nothing new is provided to Polar.
- Questions and requests: questions about information already sent to Polar, and requests to delete it or suspend its processing, can be sent to support@k-otp.dev (Section 12); the Company reviews them and forwards them to Polar or takes other necessary steps.
- Google LLC (Google Analytics): only when you agree in the cookie notice of the website or the documentation
- Contact: Google's privacy contact form
- Countries: the United States and other countries where Google processes data
- When and how: over the network whenever a visitor who agreed in the cookie notice uses that site (the website k-otp.dev or the documentation docs.k-otp.dev)
- Items: the website usage statistics in Section 2, item 6 (Google Analytics cookie identifiers, pages visited and events, referrers, browser, device and language details, and an approximate location). Your IP address reaches Google with each request, but Google Analytics does not store it and uses it only to estimate the approximate location.
- Purpose: the processing entrusted in Section 6 (website and documentation usage statistics)
- Retention: event- and user-level data are deleted after the retention period set in Google Analytics (2 months); aggregated reports that identify no one may remain
- How to refuse and what happens: if you decline in the cookie notice or do not answer it, Google Analytics is not loaded and nothing is transferred. Consent is asked separately on each site, and after agreeing you can withdraw at any time under "Cookie settings" at the bottom of that site. Declining or withdrawing does not affect your use of the Service.
To refuse the transfer to Cloudflare, delete your account; the whole Service runs on Cloudflare, so refusing it means the Service cannot be used. The transfer to Creem happens only with your consent; without it, paid credits cannot be bought in USD, but the rest of the Service is not affected. The transfer to Google happens only with your consent in the cookie notice of the website or the documentation; declining or withdrawing it does not affect the Service. Questions about refusing a transfer (including information already sent to Polar and requests to delete it or suspend its processing) can be sent to the contact in Section 12.
8. Destruction
- Procedure: personal information whose retention period has ended or whose purpose has been fulfilled is destroyed without delay. Information that must be kept under law is stored and managed separately from other personal information.
- Method: electronic information is destroyed so that it cannot be restored, such as by deleting it from the database; paper documents are shredded or incinerated.
- Backups: the production databases are backed up every day for disaster recovery. Only the latest 14 backup copies are kept on the database server in Korea, and copies in Cloudflare R2 (Section 7, item 1) are kept for 30 days from the day they are made and then deleted. Backups made manually just before a database structure change, to roll back a change that goes wrong, are kept on the database server in Korea for 30 days, but the latest three per database may be kept beyond 30 days. These are also deleted, oldest first, as newer pre-change backups are made, and are never kept for more than one year from the day they are made. Information destroyed in the database can remain in backup copies until they are deleted, but access to it is restricted and it is not used for any purpose other than disaster recovery, and if the databases are restored from a backup, information past its retention period is destroyed again without delay.
9. Rights of data subjects and legal representatives
- Data subjects may at any time ask the Company to access, correct, delete or stop processing their personal information, or withdraw consent.
- In the console: under General in the account settings (app.k-otp.dev/settings/general) you can change your name, email address, profile image and language, and delete your account. When you ask to delete your account, a confirmation link is emailed to you; the account is deleted when you open that link in the same browser within one hour. Organization details can be changed in the organization settings. An organization that has apps, a credit balance or payments cannot be deleted in the console; ask by email instead.
- Other requests can be made by email (support@k-otp.dev) or in writing, and the Company acts on them without delay (access requests within 10 days).
- Rights can also be exercised through a representative, such as a legal representative or a person authorized by the data subject, who must submit a power of attorney.
- Information that the law requires to be kept cannot be deleted on request, and access or suspension requests may be limited in the cases set by law, such as where they could infringe the rights of others.
- The Company verifies that the person making a request is the data subject or a legitimate representative.
10. Safeguards
The Company takes the following measures to keep personal information secure:
- Managerial: the people who can access personal information and their permissions are kept to a minimum, and database accounts are separated by purpose so that each account reaches only the data it needs. Access records of administrators who use the administration screens (administrator account, date and time, access information, the target viewed or processed and the action taken) are kept for 1 year and reviewed at least once a month.
- Technical
- No passwords are used. Sign-in links and codes are stored only as hashes, expire after 15 minutes and work once. Failed codes and sign-in email requests are limited per IP address and per email address.
- The administration screens can be used only by administrator accounts that have passed two-step authentication.
- API keys are stored only as hashes; the key itself is shown once when it is issued.
- Code issue records store end users' phone numbers and codes only as hashes; number data in delivery records is stored encrypted and deleted as described in Section 4.
- Email addresses and IP address ranges used to prevent abuse are stored only as hashes (HMAC).
- Traffic to the website, console and API is encrypted with TLS. The database has no port open to the internet and is reached only through an encrypted tunnel over TLS.
- Database backup copies are sent over TLS-encrypted connections and kept in dedicated storage with public access blocked, which only the backup accounts can reach.
- Payment method details are handled by the payment provider and never stored by the Company.
- Physical: physical access to servers and data centers is controlled by the processors in Section 6.
11. Cookies
The Company uses cookies to store information the Service needs. A cookie is a small text file a website stores in your browser. On the website (k-otp.dev) and the documentation (docs.k-otp.dev), analytics cookies (Google Analytics) are used only when you agree in that site's cookie notice; they are stored for that site only and are not sent to other subdomains. The console uses no analytics cookies, and no cookies are used for advertising anywhere.
- Website (k-otp.dev)
consent: your answer to the cookie notice (30 days)locale_banner_seen: whether you answered the language suggestion (1 year)_ga,_ga_<measurement ID>: Google Analytics visitor identification for usage statistics (up to 2 years), stored only when you agree in the cookie notice
- Documentation (docs.k-otp.dev)
consent: your answer to the cookie notice (30 days)_ga,_ga_<measurement ID>: Google Analytics visitor identification for usage statistics (up to 2 years), stored only when you agree in the cookie notice
- Console (app.k-otp.dev)
better-auth.session_token(with the__Secure-prefix over HTTPS): keeps you signed in (up to 30 days)better-auth-passkey: checks a passkey registration or sign-in in progress (only during that step)kotp_sign_in_request: tells whether the browser that opens a sign-in link is the one that asked for it (15 minutes)kotp_ref: the referral code and visit time from a referral link, to credit the referral at sign-up (30 days)NEXT_LOCALE: language of the console and its emails (1 year)locale_banner_seen: whether you answered the language suggestion (1 year)sidebar-collapsed: whether the sidebar is collapsed (1 year)- Your color theme (light or dark) is kept in browser storage (localStorage).
You can refuse or delete cookies in your browser settings. Without cookies, parts of the Service, such as signing in to the console, will not work. You can decline analytics cookies in the cookie notice and, after agreeing, withdraw under "Cookie settings" at the bottom of that site (the website or the documentation). Withdrawing stops Google Analytics, deletes its cookies (_ga, _ga_<measurement ID>) and shows the cookie notice again. Declining or withdrawing does not affect your use of the Service.
12. Privacy officer
The Company has designated the following privacy officer, who oversees personal information processing and handles complaints and remedies. Requests to access personal information are also received and handled at this contact.
- Name: Junglei Kim (김정래)
- Title: Personal Information Officer (개인정보처리담당자)
- Email: support@k-otp.dev
- Phone: +82-2-877-1990
Company: 1990Company, CEO Junglei Kim (김정래), business registration number 163-31-01584, 601, 7, Cheonjung 1-gil, Dongnam-gu, Cheonan-si, Chungcheongnam-do, South Korea (충청남도 천안시 동남구 천중1길 7, 601), phone +82-2-877-1990, email support@k-otp.dev
13. Remedies
Data subjects may apply for dispute resolution or counseling about infringements of their personal information to the following bodies:
- Personal Information Dispute Mediation Committee: 1833-6972 (in Korea), www.kopico.go.kr
- Personal Information Infringement Report Center (Korea Internet & Security Agency): 118 (in Korea), privacy.kisa.or.kr
- Supreme Prosecutors' Office: 1301 (in Korea), www.spo.go.kr
- Korean National Police Agency: 182 (in Korea), ecrm.police.go.kr
14. Changes
This Privacy Policy takes effect on 2026-10-20. Additions, deletions or changes are announced on the website at least 7 days before they take effect, and changes important to data subjects' rights, such as changes to the items collected or the purposes of use, at least 30 days before.
Change history
- Effective 2026-10-20: access and activity records of the Company's internal administration screens are now kept, and access control of administrator accounts was strengthened. The following changed. The amendment adds safeguards on the Company's side and changes nothing about the items collected from users, the purposes of use, processing entrustment, provision to third parties or international transfers (so it is not a change important to data subjects' rights), so it takes effect on the day it is published without the advance notice period of Section 14.
- Section 3: added item 8 (administrator access and activity records: administrator account, date and time, access information, the target viewed or processed and the action taken, kept 1 year).
- Section 10: added the keeping (1 year) and at-least-monthly review of administrator access records to item 1, and two-step authentication for the administration screens to item 2.
- Effective 2026-10-14: a KRW card payment option processed by Creb Co., Ltd. was added, and the following changed. The amendment applies only to those who pay by KRW card after it is published, does not affect existing processing, and discloses a processing entrustment, so it takes effect on the day it is published. The items the Company already collected and its purposes of use did not change, and Section 7 did not change because Creb and its subcontractor process in the Republic of Korea, so there is no international transfer.
- Section 2 item 3: added the items of KRW card payments. Card details entered in the payment window are collected directly by the payment agent and are not received or stored by the Company; the buyer name and mobile phone number that Creb's payment window requires are only passed on to the payment agent to process the payment and are not stored; and the KRW payment information the Company stores (order number, payment key and transaction number, product, amount, payment time, paying member and organization, refunds) is listed. The earlier items are now marked as those of USD payments.
- Section 6 (Processors): added Creb Co., Ltd. (authorization and cancellation of KRW card payments and operation of the payment window, entrusted items, retention) and that Creb may subcontract card authorization to a payment gateway (such as KSNET Inc. (KSPAY)), and added a sentence stating that Creb is listed in that Section as a processor.
- Effective 2026-10-13 (second amendment that day): consent-based usage statistics (Google Analytics) now also apply to the documentation (docs.k-otp.dev), so the documentation was added to Section 1 item 7, Section 2 item 6, Section 3 item 7, Section 6, Section 7 item 4 and Section 11, and Section 11 lists the documentation's cookies and per-site consent and withdrawal. Google Analytics on the documentation applies only to visitors who newly agree after this amendment is published, so it takes effect on the day it is published.
- Effective 2026-10-13: with the introduction of website usage statistics (Google Analytics) on k-otp.dev, the following changed.
- Timing: the new processing applies only to visitors who newly agree in the cookie notice after this amendment is published, and does not affect anyone who does not agree or any information already processed, so it takes effect on the day it is published. The personal information collected in the console and the API did not change.
- Section 1 (Purposes): item 7 (website improvement: usage statistics of visitors who agree) was added.
- Section 2, item 6: website usage statistics of visitors who agree were added.
- Section 6 (Processors): Google LLC (Google Analytics) was added.
- Section 3 (Retention): item 7 (website usage statistics, 2 months) was added.
- Section 7 (International transfers): the consent-based transfer to Google LLC (item 4), its legal basis and how to refuse it were added.
- Section 11 (Cookies): the statement that no cookies are used for analytics or advertising was replaced by the consent-based analytics cookie on the website, and the Google Analytics cookies and how to refuse or withdraw ("Cookie settings" at the bottom of the website) were added.
- Effective 2026-10-12: with the introduction of regular backups of the production databases, the following changed. Backup copies are sent to Cloudflare R2 only after this amendment is published, so it takes effect on the day it is published. The items the Company collects and the purposes of use did not change.
- Section 6 (Processors): storage of database backup copies was added to Cloudflare's R2 storage, and the backup environment to Smileserv (IWINV).
- Section 7 (International transfers): database backup copies were added to the items transferred to Cloudflare, with where they are stored (Asia-Pacific), how they are sent (once a day over an encrypted connection) and how long they are kept (30 days).
- Section 8 (Destruction): item 3 was added on how long backup copies are kept and when they are deleted, the exception for backups made just before a change and its one-year limit, and destroying information again after a restore.
- Section 10 (Safeguards): encrypted transfer of backup copies and restricted access to their storage were added.
- Effective 2026-10-07: because USD payments are now processed by Creem, the following changed. This amendment was first announced on 2026-10-06 to take effect on 2026-11-06 and announced again on 2026-10-07, aligned with the Terms of Service and the Refund Policy, to take effect on 2026-11-07; because there had been no actual USD purchases yet, it was brought into force on 2026-10-07. The changes are the same as first announced.
- Section 5 (Provision to third parties): added the provision, with the member's separate consent, of personal information to Armitage Labs OÜ (Creem) abroad (recipient, purposes, items, retention, countries, timing and method, contact, how to refuse consent and its effect). It previously read: "Personal information currently provided to third parties: None".
- Corrected classification: a merchant of record sells to the member as a party in its own right and processes personal information for its own purposes, so Polar Software Inc., previously listed as a processor in Section 6, is now correctly listed as a third-party recipient in Section 5, limited to information sent for orders paid or attempted through Polar before the switch to Creem. Nothing new is provided to Polar, and the way to ask about, or request deletion or suspension of, information already sent is stated. Section 6 previously read: "Polar Software Inc.: processing credit payments (including collecting payment method details) and refunds".
- Section 7 (International transfers): added the transfer to Creem (Estonia), stated that the transfer to Creem is provision to a third party abroad with the member's separate consent, and limited the transfer to Polar to purchases started before the switch to Creem. Previously the only payment-related transfer was to Polar, described as entrustment under Article 28-8(1)(3), and the way to refuse it was "do not buy credits (Polar)".
- Section 2(3): the checkout where payment method details are entered changed from "the payment provider's (Polar's)" to the checkout page of Creem, the merchant of record, for USD payments.
- The items the Company collects and the Company's purposes of processing did not change.
- Applies from 2026-10-06: the Kakao Login supplement for members who choose Kakao Login was added.
- Effective 2026-10-02: previous Privacy Policy.