Privacy Policy
Current service status. All of the tool's features are free, and no ads are shown now. From 30 November 2026, Adsterra's banner ads will be shown on the tool, guide, FAQ and about pages (if you accept cookies; visitors who decline see A-ADS's ads, which use no cookies). While you're signed in to an account that bought Remove Ads, no ads are shown. This is how the service operates now, whatever the effective dates of the document changes below.
Changes to this privacy policy
This privacy policy takes effect on 2026-10-30, the day it was published. Until the day before, the previous privacy policy (effective 2026-10-06) applies. The change announced on 2026-10-25 (to take effect on 2026-11-24) does not take effect: this change replaces it.
- Why: the Site shows Adsterra's banner ads, and A-ADS's ads, which use no cookies, to users who decline cookies.
- What changes: the parts of the previous policy about ads now describe Adsterra: the advertising purpose (Section 1), the advertising information and its retention (Sections 2 and 3), the transfers abroad for advertising (Section 6), and the advertising cookies, behavioral information, the ad cookie notice and consent, and how to refuse (Section 9). Section 9 also adds a note on the Google cookies that security checks may use and on how to block or delete cookies, and Sections 2 and 6 now say more precisely when security check information is collected. Amended again the same day: A-ADS (Sections 1, 2, 3 and 6), Adsterra's script domain bauval.org and its partner BPGame (Section 6), and the notice's Accept and Decline, Cookie settings, the stored answer and Global Privacy Control (Section 9), and no ad loads anywhere until you answer.
This is an English translation of the Korean privacy policy (개인정보처리방침). If the two versions differ, the Korean version prevails.
Your MIDI files and chord progressions are processed on your device and never uploaded. An account is created when you sign in; payment records exist only if you buy Remove Ads.
Culture & Tech (the "Operator") establishes and publishes this privacy policy under Article 30 of the Personal Information Protection Act ("PIPA") to protect the personal information of data subjects and to handle related complaints promptly and smoothly. It applies to Chord to MIDI (https://chord-to-midi.app, the "Service"), provided by the Operator.
1. Purposes of processing
The Operator processes personal information for the purposes below. It isn't used for any other purpose, and if a purpose changes, the Operator will take the steps required by Article 18 of PIPA, such as obtaining separate consent.
- Member management: identifying members who sign in with a Google, Kakao or Naver account or an email link, linking several ways to sign in to one account, recovering an account with its confirmed email, linking a Remove Ads purchase to the account and restoring it, moving Remove Ads to another account after checking the proof of a member who lost both their sign-in and their mailbox, and handling withdrawal (account deletion).
- Selling and providing Remove Ads: confirming the email that receives receipts, creating orders, approving, cancelling and refunding payments, providing receipts, applying Remove Ads, and notifying buyers of important matters about it, such as the end of the Service.
- Legal obligations and customer support: keeping transaction records under the Act on the Consumer Protection in Electronic Commerce, handling inquiries and complaints, and responding to disputes.
- Security: preventing misuse such as automated requests and payment fraud, and keeping the Service running reliably.
- Advertising: showing Adsterra banner ads (or A-ADS's ads to visitors who decline cookies) to keep the Service free. The information used for the ads is collected directly by Adsterra and its partner, or by A-ADS, not by the Operator, as Section 9 explains.
2. Personal information processed
What we don't collect
We don't collect the MIDI files you open, the progressions you type, the MIDI you generate, the audio you play or your tool settings (octave, unit, velocity, tempo and so on). All of it is processed only inside your browser, and the Operator neither sends it to its servers nor gives it to third parties. Your settings and the progression you're working on are stored only in your browser (localStorage), so you can pick up where you left off. Favorites you save (a progression and its tempo) are also stored only in your browser (localStorage), and never on the Operator's servers, even when you're signed in. They don't appear in other browsers or on other devices, and clearing this site's data in your browser deletes them. A progression in a share link sits after the # in the address, which browsers don't send to servers. If you use the DAW drag extension, the clips the tool makes also go to its companion app on your computer, and they don't leave your computer either (see 3 below).
If you use the tool without signing in, the Operator doesn't collect your personal information. However, the information in 2 below may be generated and collected automatically while you use the Service.
1. When you sign in or buy Remove Ads
Signing in is needed only to buy Remove Ads or to restore a purchase. Your first sign-in creates an account, and the account information below and that of the sign-in method you chose are kept until you withdraw, whether or not you buy.
| Category | Items | When collected | Legal basis |
|---|---|---|---|
| Account information | Account identifier (Firebase UID), display name, account creation time, last sign-in time | At your first sign-in (the sign-in time at every sign-in) | Concluding and performing a contract (PIPA Article 15(1)4) |
| Google sign-in information | Google account ID, email address, name, profile photo URL | When you sign in with or link a Google account | Concluding and performing a contract (item 4) |
| Kakao sign-in information | Kakao member number, nickname (if you agree to share it), email address and whether Kakao says it is valid and verified (if you agree to share it) | When you sign in with or link a Kakao account, provided by Kakao with your consent | Concluding and performing a contract (item 4) |
| Naver sign-in information | Naver member identifier (a value used for this service only), nickname or name, email address | When you sign in with or link a Naver account, provided by Naver with your consent | Concluding and performing a contract (item 4) |
| Email sign-in information | Email address | When you ask for an email sign-in link (also if you never buy) | Concluding and performing a contract (item 4) |
| Receipt and recovery email | The confirmed email address and when it was confirmed | When you confirm an email before your first purchase, or change it | Concluding and performing a contract (item 4) |
| Buyer information | Payment customer key (a randomly generated value), whether Remove Ads applies and since when, record creation time and last use time | When you start buying Remove Ads | Concluding and performing a contract (item 4) |
| Order and payment records | Order number, product name, amount and currency, order and payment status, payment request and approval times, payment key, payment method, part of the card payment details (card company code, card type, installment months, approval number) or the name of the easy-pay service, receipt URL, cancellation details (amount, reason, time), error code and message if a payment fails, the receipt email address when the order was made, and a pseudonymous identifier of the account that made it | When you pay | Concluding and performing a contract (item 4); complying with legal obligations (item 2) |
| Temporary records | Email confirmation and change requests (account identifier, email address, kind of request and the page to return to), and payment details kept while you sign in (account identifier, order number, payment key, amount) | When you ask to confirm or change an email, and when you finish a payment in a browser where you aren't signed in | Concluding and performing a contract (item 4) |
| Administration records | Records of Remove Ads moves and refunds (pseudonymous identifiers of the accounts involved and of the administrator, order number, a hash of the request, the outcome and time, the length of the reason) | When the Operator moves Remove Ads or refunds a payment | Complying with legal obligations (item 2); the Operator's legitimate interest (item 6) |
| Inquiry records | Your email address, name, message, order number and anything else you send, including proof of payment and the Account ID of a new account when you ask to move Remove Ads | When you email us or request a refund or a move | Performing a contract (item 4); complying with legal obligations (item 2) |
Email addresses provided by Kakao and Naver are used only for display and to suggest the address to confirm, never to find or merge accounts. The receipt and recovery email is used only once you have opened the link sent to it. The emails with sign-in, confirmation and change links are sent by Firebase Authentication (Google). The Operator uses Kakao's and Naver's access tokens once, to receive your member information, and doesn't store them.
Card numbers, expiry dates, passwords and other payment details are entered in Toss Payments' payment window and processed by Toss Payments. Of the information Toss Payments reports about a payment, the Operator doesn't store the card number, the buyer's name, contact details or similar data.
2. Information generated and collected automatically
| Category | Items | Collected by, and how |
|---|---|---|
| Advertising information | IP address and the location estimated from it (country, region), browser and device information (user agent, operating system, browser language and so on), the address of the page showing the ad, cookies and other identifiers, ad impression and click records | Collected directly by Adsterra and its partner on the tool, guide, FAQ and about pages (only after you accept; see Section 9). If you decline cookies, A-ADS collects only the IP address, browser information and page address, without cookies |
| Security check information | Browser and device information, information about the environment you use, verification tokens | Collected by Google reCAPTCHA Enterprise (Firebase App Check) to prevent misuse when you open the sign-in, account or purchase pages, and in a browser signed in to an account with Remove Ads |
| Access logs | IP address, browser information (user agent), requested address, access time, error records | Recorded automatically by the Google servers that deliver the site and run its server functions (Firebase Hosting, Cloud Functions) |
Security check information and access logs are processed for the Operator's legitimate interest in running the Service securely and reliably (PIPA Article 15(1)6). The account and payment pages and the legal notices, such as the terms and this privacy policy, carry no ads. If you're signed in, your sign-in state and whether Remove Ads applies are also kept in your browser so they take effect immediately on your next visit.
3. When you use the DAW drag extension
The Chrome extension Chord to MIDI DAW Bridge and its companion app, Chord to MIDI Bridge, let you drag a clip from the tool straight into a music application such as Cubase. Both run only on your computer, and nothing they handle reaches the Operator or any third party.
| Item | Details |
|---|---|
| What they handle | The MIDI data and file name of each clip the tool makes while the extension is on, so that it's ready to drag |
| How | The tool page passes the clip to the extension, which passes it to the companion app on the same computer. The companion saves it as a .mid file that the music application can import. On macOS it attaches that file to your drag. On Windows the extension puts the file into the tool page with Chrome's debugging interface, and the page drags it; this happens only on the chord-to-midi.app tool page, and Chrome shows its debugging bar meanwhile. |
| Where it's kept | In the companion's folder, which only your user account can open: ~/Library/Caches/tech.cultureand.chordtomidi.bridge on macOS, %LOCALAPPDATA%\Chord to MIDI Bridge\Cache on Windows |
| How long | On macOS, a clip handed to a drag is deleted 24 hours later, and one you didn't drag 5 minutes after it was last used. On Windows, every clip is handed to the page as soon as it's made, so each is kept 24 hours whether or not you drag it. A file a music application is still reading can stay until it's released. The companion checks when it starts and every minute while it runs, so a file left from an earlier session is deleted the next time it starts. |
| Sent to | No one. Neither the extension nor the companion connects to the internet, and they don't read other websites, your browsing history or your other files. The extension stores nothing in your browser. |
To stop, turn off or remove the extension in Chrome and uninstall the companion app. Deleting the folder above deletes the saved clips at once.
The extension's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. The extension receives no personal information from Google; the only user data it handles is the clips above, used only for dragging them into a music application, never transferred to anyone, never read by a person, and never used for ads, sold or used for any other purpose.
3. Processing and retention periods
(1) The Operator processes and keeps personal information only within the retention period required by law or set when it was collected.
(2) The retention periods by item are:
- Account information, sign-in information, the receipt and recovery email, and buyer information: until you withdraw (delete your account). When you remove a sign-in method on the account page, its information is deleted without delay; when you disconnect the service at Naver, only a note that it was disconnected is kept. Remove Ads stops applying earlier if the payment is refunded (cancelled).
- Temporary records: email confirmation and change requests lapse after 30 minutes, and payment details kept while you sign in after 10 minutes; they are then deleted automatically (usually within a day), and immediately when you withdraw.
- Order and payment records, and administration records: until the end of the legal retention period in (3) (5 years).
- Inquiry records: 3 years from the day the inquiry is resolved.
- Advertising information: kept for the periods set by Adsterra and its partner, or by A-ADS, then deleted (see the advertising entries in Section 6).
- Security check information and access logs: kept for the period set by Google and then deleted. The Operator uses server records only to investigate errors in the Service.
(3) Information kept under law:
| Information kept | Legal basis | Period |
|---|---|---|
| Records of contracts or withdrawals of purchases | Act on the Consumer Protection in Electronic Commerce | 5 years |
| Records of payments and supply of goods or services | Same Act | 5 years |
| Records of consumer complaints or dispute handling | Same Act | 3 years |
(4) When you withdraw (delete your account), your account information, sign-in information, receipt and recovery email, buyer information and temporary records are destroyed without delay. Because the records in (3) must be kept for the legal period, they are kept separately from other personal information, with your account identifier and the receipt email address of your orders replaced by values from which the originals can't be recovered (hashes; pseudonymization), and are destroyed when the period ends. These values are not anonymous data; they are used only to match a refund or move request to its order. The receipt email address of your orders is replaced this way also when an order's Remove Ads was moved to another account.
4. Provision to third parties
The Operator processes personal information only within the purposes in Section 1 and provides it to third parties only in the cases allowed by Articles 17 and 18 of PIPA, such as with the data subject's consent or under a specific provision of law. The Operator currently provides no personal information to third parties.
5. Outsourcing of processing
(1) To provide the Service smoothly, the Operator outsources processing as follows.
| Processor | Work outsourced |
|---|---|
| Google LLC | Firebase Authentication (accounts of every sign-in method; sending sign-in, confirmation and change emails), Cloud Firestore (storing account and buyer information, sign-in method links, and order and payment records), Cloud Functions (processing sign-ins, orders, payments and account deletion), Firebase Hosting (delivering the site), Firebase App Check (preventing misuse) |
| Toss Payments Co., Ltd. (토스페이먼츠 주식회사) | Payment processing (approval, cancellation and refunds for cards and easy-pay services), issuing receipts |
(2) When concluding outsourcing contracts, the Operator sets out in writing, under Article 26 of PIPA, that personal information may not be processed beyond the outsourced work, the technical and managerial safeguards, restrictions on re-outsourcing, management and supervision of the processor, and liability for damages, and it supervises whether the processors handle personal information safely.
(3) If the outsourced work or the processors change, the Operator will publish the change in this privacy policy without delay.
6. Transfers abroad
(1) To conclude and perform contracts with data subjects, the Operator has personal information processed and stored abroad, and discloses the following under Article 28-8(1)3 of PIPA.
(2) Cloud Firestore and Cloud Functions are in Google's Seoul region (asia-northeast3), so the buyer information, Kakao and Naver member identifiers and profile information, and order and payment records stored there are processed in Korea. Firebase Authentication, however, handles every member's account whatever the sign-in method, and is transferred abroad as follows.
(3) Except for the advertising entries below, the recipient is Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA). Privacy questions can be sent to Google as described in Google's privacy policy.
Sign-in (Firebase Authentication)
- Countries: the United States and other countries where Google operates data centers
- When and how: when you sign in (and at each later sign-in), and when you ask for an email link or confirm or change an email, sent over the network
- Items: account identifier (Firebase UID), account creation and sign-in times, display name (your name with Google; your nickname with Kakao or Naver), for Google sign-in your Google account ID, email address and profile photo URL, and for email sign-in and the receipt and recovery email that email address
- Purpose: signing you in, managing your account and sending sign-in, confirmation and change emails
- Retention: until you withdraw (delete your account)
- How to refuse, and the effect: if you don't sign in, nothing is transferred. Without signing in you can still use every feature of the tool, including typing progressions, playback, and MIDI download and import, but you can't buy or restore Remove Ads. If you've already signed in, you can delete your account on the account page to have this information deleted.
Site delivery and security (Firebase Hosting, Firebase App Check)
- Countries: the United States and other countries where Google operates servers
- When and how: when you open the site (access logs), and when you open the sign-in, account or purchase pages or use a browser signed in to an account with Remove Ads (security check information), sent over the network
- Items: access logs (IP address, browser information, requested address, access time) and security check information (browser and device information, information about the environment you use, verification tokens)
- Purpose: delivering the site, preventing misuse and keeping it secure
- Retention: for the period set by Google
- How to refuse, and the effect: this information is needed to deliver and protect the site, so the only way to avoid the transfer is not to use the site. Security check information isn't transferred unless you open the sign-in, account or purchase pages, or use a browser signed in to an account with Remove Ads.
Advertising (Adsterra)
- Recipients: Adsterra, operated jointly by AD MARKET LIMITED (Christaki Kranou 49, Germasogeia, 4041 Limassol, Cyprus) and ADMEDIA LLC FZ (The Meydan Hotel, Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, UAE), contact support@adsterra.com, whose domain bauval.org serves the ad scripts; and BPGame, which Adsterra names as its partner (shown on bauval.org as Game Plan Zero Limited, United Kingdom; contact privacy@bpgame.org)
- Countries: Cyprus, the United Arab Emirates, the United Kingdom and other countries where they operate servers
- When and how: when you open a page that shows ads (the tool, guide, FAQ and about pages), your browser sends it over the network as it loads the ad script and the ads (only after you accept)
- Items: the advertising information in Section 2, part 2 (IP address and the location estimated from it, browser and device information, the address of the page showing the ad, cookies and other identifiers, ad impression and click records)
- Purpose: showing ads, limiting how often the same ad is shown, measuring ads and preventing invalid traffic
- Retention: under each company's policy (Adsterra says it deletes information tied to cookies when they expire, normally within a year, and may keep de-identified information without limit; Adsterra's partner BPGame says on bauval.org that it keeps some cookies for up to 5 years)
- How to refuse, and the effect: you can refuse as described in Section 9, and every feature of the tool still works. When you're signed in to an account with Remove Ads, the ad code isn't loaded at all.
Advertising (A-ADS, if you decline cookies)
- Recipient: A-ADS (AADS.com; a company headquartered in Hong Kong that doesn't publish its legal name; contact https://aads.com/contact_us/)
- Countries: Hong Kong and other countries where A-ADS operates servers. A-ADS's ad frame loads fonts from Google, so Google LLC (United States) receives the IP address too.
- When and how: when a browser that declined the ad cookie notice opens a page that shows ads, sent over the network as the browser loads A-ADS's ad frame
- Items: IP address, browser information (user agent), the address of the page showing the ad. A-ADS's ad frame sets no cookies and runs no scripts (checked 2026-10-29).
- Purpose: showing ads, counting ad impressions and clicks
- Retention: under A-ADS's policy (it states no period)
- How to refuse, and the effect: choosing Accept in the ad cookie notice or in Cookie settings shows Adsterra's ads instead of A-ADS's. When you're signed in to an account with Remove Ads, no ad is loaded at all.
7. Destruction procedure and method
(1) When personal information is no longer needed, for example because its retention period has ended or its purpose has been achieved, the Operator destroys it without delay.
(2) Where a law requires information to be kept, it is stored separately from other personal information (Section 3(4)) and destroyed when the retention period ends.
(3) Electronic files are deleted so that they can't be recovered. When a member withdraws, their Firebase Authentication account, their buyer information and sign-in method links in Cloud Firestore, and their temporary records are deleted; copies left in Google's backups are deleted after a period under Google's policies. Personal information on paper is shredded or incinerated.
8. Your rights and how to exercise them
(1) You can ask the Operator at any time to let you access, correct or delete your personal information, or to suspend its processing.
(2) On the account page you can check your Remove Ads status and purchases, change your receipt and recovery email, link and remove sign-in methods, and delete your account yourself. Other requests can be emailed to the privacy officer in Section 12, and the Operator will act without delay (within 10 days) and tell you the result.
(3) You can also exercise these rights through a representative, such as a legal guardian or someone you have authorized. In that case, a power of attorney must be submitted.
(4) Requests for access and for suspension of processing may be limited under Article 35(4) and Article 37(2) of PIPA.
(5) Personal information that another law specifically requires to be collected can't be deleted on request, and the transaction records in Section 3(3) are not deleted during their retention period.
(6) The Operator checks that the person making a request is you or your rightful representative.
9. Cookies and other automatic collection, and behavioral information
Cookies and browser storage
- The tool's settings, the progression you're working on, your favorites and your language choice are kept in your browser's local storage (localStorage), not in cookies, and are never sent to a server. If you're signed in, your sign-in state and whether Remove Ads applies are kept in browser storage too.
- When you open the sign-in, account or purchase pages, and on any page in a browser signed in to an account with Remove Ads, Google reCAPTCHA Enterprise (Firebase App Check) may use Google's cookies to prevent misuse (the security check information in Section 2, part 2).
- On the pages that show ads, Adsterra and its partner may use cookies and other identifiers for the ads. The Operator keeps only your answer to the ad cookie notice (accept or decline), its time and the notice's version in this browser's local storage.
- You can block or delete cookies and site data in your browser settings. Clearing this site's data deletes the tool settings, the progression you're working on and the favorites kept in your browser, and signs you out.
Advertising and behavioral information
To keep the Service free, Adsterra's banner ads are shown on the tool, guide, FAQ and about pages. Adsterra's script loads the ads inside this site's pages, and Adsterra uses cookies and other identifiers to show the ads, limit how often the same ad is shown and measure them. Adsterra may choose ads based on your visits to this site and other websites. Visitors who decline cookies see A-ADS's ads instead; A-ADS's ad frame sets no cookies and collects no behavioral information (see "Advertising (A-ADS)" in Section 6).
| Item | Details |
|---|---|
| Who collects and processes behavioral information | Adsterra and its partner (see "Advertising (Adsterra)" in Section 6) |
| Behavioral information collected | Website visit records, ad impression and click records, and the like |
| How it is collected | Automatically, through the ad scripts and cookies, when you visit a page that shows ads |
| Purpose | Showing ads, limiting how often an ad is shown, measuring ads, preventing invalid traffic |
| Retention | Under each company's policy (see Section 3) |
The Operator doesn't receive or store the information Adsterra collects, and doesn't pass your MIDI files or progressions to the ad companies: they are processed only on your device, as Section 2 explains.
The ad cookie notice and how to refuse
- When you open a page that shows ads, a notice about ad cookies appears at the bottom of the screen, with Accept and Decline buttons of the same kind for everyone. "Details" shows who collects, the purposes, how long, and how to change your mind later.
- Wherever you are, no ad loads until you answer, and ads load only after you accept.
- If you decline, Adsterra's ad code isn't loaded, and an ad from A-ADS, which uses no cookies, is shown in the same place.
- Your answer (accept or decline), its time and the version of the notice are kept only in this browser's local storage and are never sent to the Operator's servers. You're asked again after 6 months, or when the notice changes (a different ad company or new purposes).
- You can change your answer at any time: Cookie settings at the bottom of every page (the button below opens it too) shows your current answer and lets you change it. If you withdraw consent, Adsterra's ad code stops loading from then on, but cookies Adsterra already set must be deleted in your browser.
- If your browser sends the Global Privacy Control (GPC) signal, we treat it as Decline until you answer in this browser.
- You can block or delete cookies in your browser settings, and every feature of the tool still works. Adsterra offers no separate opt-out page for visitors.
- When you're signed in to an account with Remove Ads, the ad code isn't loaded at all.
10. Children under 14
The Operator doesn't accept sign-ups (sign-ins) or Remove Ads purchases from children under 14, and checks at purchase that the buyer is 14 or older. If the Operator learns that it has collected personal information of a child under 14, it destroys that information without delay. Anyone can use the tool without signing in.
11. Measures to keep personal information secure
Under Article 29 of PIPA, the Operator takes the following measures.
- Data minimization: the Service is designed so that MIDI files and progressions are never sent to a server, and card numbers and other payment details are not stored.
- Encryption in transit: all communication between the site and the servers is encrypted with HTTPS.
- Access control: database security rules let members read only their own records, and only server functions can write records. Administrative functions can be used only by accounts with administrator rights.
- Secrets management: payment secret keys, Kakao's and Naver's client secrets and other credentials are kept in Google Cloud Secret Manager and never in source code or logs. Kakao's and Naver's access tokens are not stored.
- Account protection: email confirmation and change links apply only to the account that asked for them and lapse after a while; linking or removing a sign-in method and changing the email need a recent sign-in. Accounts are never merged because their email addresses are the same.
- Misuse prevention: Firebase App Check blocks requests that don't come from the genuine app.
- Minimal access: the number of people who handle personal information is kept to a minimum, and the records of administrative actions keep pseudonymous identifiers only.
- Physical security: personal information is stored in Google's data centers under Google's physical security controls.
12. Privacy officer
(1) The Operator has designated the following privacy officer, who is responsible for all personal information processing and for handling data subjects' complaints and remedies related to it.
- Name: Chan Baek
- Email: contact@cultureand.tech
- Phone: +82-10-2265-8170
(2) You can bring any privacy question, complaint, request for remedy or request for access arising from your use of the Service to the privacy officer, and the Operator will answer and act without delay.
13. Remedies for infringement
To seek remedies for an infringement of your personal information, you can apply for dispute resolution or counseling to the Personal Information Dispute Mediation Committee, the Personal Information Infringement Report Center of the Korea Internet & Security Agency (KISA), and similar bodies. For other reports and counseling about infringements, you can contact the agencies below.
- Personal Information Dispute Mediation Committee: 1833-6972 (no area code) (www.kopico.go.kr)
- Personal Information Infringement Report Center: 118 (no area code) (privacy.kisa.or.kr)
- Supreme Prosecutors' Office: 1301 (no area code) (www.spo.go.kr)
- Korean National Police Agency: 182 (no area code) (ecrm.police.go.kr)
14. Changes to this privacy policy
(1) This privacy policy takes effect on 2026-10-30.
(2) If anything is added, removed or changed, the Operator will announce it on the site from 7 days before the change takes effect. Important changes to your rights, such as changes to the items collected or the purposes of use, will be announced from 30 days before they take effect.
(3) The previous privacy policy (effective 2026-10-06) remains available.