Privacy policy

Applies to version: 0.1.24
Last updated: October 8, 2026
Effective: October 8, 2026
Developer: Panda Pillow Apps
Contact: heesu.jung.developer@gmail.com

1. Scope and purpose

This extension organizes BIFF bookings by screening date, restores viewing preferences and position in the same tab, and improves the layout of booking details, cancellation details, and the booking page. At your request, it saves a personal ticket-list HTML file or combines previously downloaded lists. It is an independent tool, not affiliated with or endorsed by BIFF or its ticketing provider.

2. Information processed

The extension uses these fields from the ticketing service’s list API:
• Film titles, screening dates and times, venues and auditoriums.
• Booking identifiers, booking times, ticket quantities, and booked, cancelled, or awaiting-payment status.
• Mobile-ticket links and issuance quantities, cancellation quantities, and delivery methods needed to decide whether to show those links.
• Selected month, booked/cancelled view, date filter, title search text, venue, sort order, and original-view setting.
• The booking identifier used to anchor your position, displayed identifier order, scroll position, and the item’s position on screen.

The original API response may contain additional fields. It is read in browser memory; the list model retains fields needed for its features. The extension does not require your real name, email address, phone number, or payment-card details, or call separate APIs to retrieve them. This does not guarantee that the original API never returns such fields. On detail pages, it adjusts the layout and styling of the information already displayed by the original site, including booking-holder, seat, and payment details; it does not add those details to the downloaded list or send them to a developer server.

When downloading a list, you enter an account label of 1–80 characters. It is a display name to help you recognize which account to use when opening tickets. You do not need to enter an actual login ID, email address, phone number, or password. The extension does not automatically detect, authenticate, or switch accounts.

“Merge ticket lists” reads the content and names of HTML files you explicitly select in your browser. File names are displayed in the selection list. Screening information, booking identifiers, booking times, quantities, mobile-ticket links, and saved account labels are read from the files and combined. You manually assign labels to older files without them. Account information is not inferred from file names.

3. Purposes of use

Information is used to display tickets by date, search titles, filter venues, sort results, query booking status from the official service, link to official details and tickets, restore list state and position in the same tab, and create or merge personal HTML lists. Account labels distinguish accounts in saved lists and are preserved when merging again.

Saved or merged lists are snapshots and do not automatically refresh current booking or cancellation status. Merging does not transfer tickets or account access. Information is not used to collect browsing history on other sites, target advertising, or profile users. The extension contains no usage analytics, error-log collection, or advertising SDKs.

4. Storage and retention

Retrieved ticket lists and mobile-ticket links are processed in page memory, not stored on a developer-operated server or database. The browser’s back-forward cache may temporarily retain page memory.

Viewing preferences, anchor booking identifiers, and identifier order are stored in sessionStorage under the ticketing site’s origin. This is tab-scoped storage shared with the website, not a private extension vault. It is generally cleared when the tab session ends, but reopening a closed tab or restoring a session may restore it. The extension does not use Chrome Sync, chrome.storage.sync, or localStorage for persistent synchronization.

When you download a list, an HTML file is saved to your device containing film titles, screening dates and times, venues, booking identifiers, booking times, quantities, confirmed status, mobile-ticket links, and account labels. It also contains the save time and selected month or date range. Downloads include all confirmed bookings for the selected month regardless of current search or filters. Files remain until you delete them; uninstalling the extension or clearing site data does not remove them.

Selected file content and labels are processed in browser memory on the merge page. Original files are not executed or overwritten; the required information is read to generate a new HTML file. The merged file retains account labels and ticket links. The merge page does not persist its work state for restoration after it is closed or refreshed.

No additional application-level encryption or password lock is applied to sessionStorage or downloaded HTML files. Anyone who can open a file can read its contents. If you save files to a cloud-synced folder or transfer them through another app, that service’s retention and synchronization policies also apply.

5. Network requests and disclosure

The extension sends the selected month, query criterion, history type, pagination range, and language to the ticket-list API at filmapi.maketicket.co.kr over HTTPS. Requests use credentials: include, allowing the browser to send the existing ticketing-service session to that server. The extension does not directly read passwords or cookie values and send them to the developer.

Opening details navigates to an original biff.maketicket.co.kr URL containing the booking identifier. Opening a mobile ticket opens its tket.me URL in a new tab. Official tickets require internet access and may require signing in to the corresponding account. Downloaded lists do not save QR codes or offline admission tickets.

File generation and merging happen in your browser; file contents, file names, and account labels are not uploaded to a server for these operations. The developer operates no collection server and does not transmit or sell ticket data, viewing preferences, position information, or account labels to the developer or advertising or analytics providers. If you share a file with someone, its booking information and ticket links are shared too.

The original site and ticket service may process IP addresses, request information, and login sessions under their own policies during direct communication. The extension does not block or manage analytics or cookies independently operated by the original site.

6. Your controls and deletion

Disable or uninstall the extension and refresh open ticket pages to stop its additional behavior. “Show original view” switches the display; it does not delete stored data or stop every request. “Reset filters” resets viewing filters, not all stored information.

To remove saved viewing state, disable the extension and clear the ticketing site’s stored data in browser settings. Clearing site data may affect your sign-in on the original site. Uninstalling the extension alone does not guarantee immediate deletion of the website’s sessionStorage.

Cancelling the account-label prompt stops the download without generating a file. Delete downloaded original and merged HTML files, and copies on your phone or cloud storage, from each location yourself. The extension cannot remotely delete copies already shared with others. To update booking information or account labels, download a fresh list with the correct information and delete older files you no longer need.

Booking cancellations, refunds, and requests to access or delete information held by the ticketing service are handled by that service. The extension does not automatically cancel tickets or delete the original service’s account data.

7. Limited Use

In accordance with the Chrome Web Store User Data Policy’s Limited Use requirements, use of information and its transfer to the original service are limited to the user-facing features described above. Information is not used for advertising, data sales, creditworthiness assessments, or lending decisions. The extension provides no feature for the developer to remotely view your ticket data or local files.

8. Contact and changes

For feature or privacy questions, contact heesu.jung.developer@gmail.com.
Do not send actual booking identifiers, mobile-ticket URLs, passwords, payment information, or personal ticket-list files. This policy describes data processing by extension features. Information you separately send through support channels is also subject to those channels’ operation and privacy information.
If data processing changes, this document will be updated and any necessary notice provided.