Cookie Policy

This Cookie Policy explains how STORYBOARD Co., Ltd. (Head Office) (“STORYBOARD”, “we”, “us” or “our”) uses cookies and similar technologies on the public website at storyboard.co.th (the “Site”). It should be read with our Privacy Policy.

This Policy describes the current Site only. It does not state that technologies planned for a future newsletter, analytics service, content system, workshop checkout, authentication system or advertising campaign are already in use.

2.1 Cookies

A cookie is a small text record that a website or service may ask a browser to store and return with later requests to a matching domain. Cookies may be temporary session cookies or may remain until a stated expiry date or deletion.

2.2 Similar technologies

Similar technologies can include local storage, session storage, software development kits, pixels, device identifiers, cached data and other browser or device mechanisms. A server or CDN log is not itself a browser cookie, although it may contain technical request information associated with delivery of a page or media file.

Meta Pixel advertising and conversion tracking operates only after acceptance. The Site stores your consent preference locally so it can respect that choice. Apart from these technologies, the Site does not intentionally:

• set application cookies unrelated to consent-based Meta measurement;
• use a separate general-purpose analytics or personalization service;
• use session replay;
• store visitor preferences in browser storage beyond the advertising-consent choice; or
• operate a cookie-based login, checkout, newsletter or contact form.

The hero sound preference is held only in temporary page memory and is not persisted after a reload. The portfolio playback logic uses browser APIs to determine visibility but does not write a visitor identifier or preference to browser storage.

“None” and “not implemented” describe the current application source. Production infrastructure can add necessary delivery or security behavior, so the deployed site must be audited before this table is treated as final.

The Site loads video through a third-party media-streaming and content-delivery provider. The browser requests video playlists and segments directly from the provider’s infrastructure. The provider may create technical delivery, performance and security logs containing information such as request time, requested URL, IP address or anonymized IP information, user agent, referrer, request identifier, country and serving edge location.

Those server or CDN records are not the same thing as storing a cookie in the visitor’s browser. A current playlist response inspected during development did not return a Set-Cookie header. That observation does not guarantee every provider response, account configuration or future provider behavior and must be checked again in production.

Some workflow pages may contain embedded Instagram content. When such a page is opened, the Instagram script and iframe content load automatically and cause the visitor’s browser to make requests to the third-party provider. The provider may receive technical request information and may set or read cookies or similar technologies under its own policies. STORYBOARD does not control the provider’s independent cookies, duration or subsequent data practices.

A cookie is stored on a device and may be returned with later requests. A server log is created on infrastructure when a request is received. A website can therefore generate ordinary request logs even if it sets no cookies. Once the production host is selected, it may process IP addresses, timestamps, URLs, browser headers, response status and security events for delivery, reliability and security.

The current application does not use those logs to create marketing profiles, but the exact host, log fields, access permissions and retention period have not yet been configured.

7.1 Strictly necessary technologies

Necessary technologies support functions requested by a visitor or reasonably required to deliver, secure and maintain a website. The current Site may rely on ordinary network, caching and security mechanisms operated by the future hosting provider and media-delivery provider even where those mechanisms do not set a browser cookie.

7.2 Optional technologies

Optional technologies may include analytics, personalization, advertising, retargeting, conversion measurement or other non-essential tracking. Meta Pixel is optional and is loaded only after acceptance. It sends PageView events and Contact events for workshop LINE button clicks. It may transmit technical information including page URLs, referrer, IP address, browser information and cookie identifiers to Meta, which processes data under its own policies. A Contact event does not confirm a conversation or booking.

A compact banner offers acceptance or rejection of advertising tracking. Before acceptance, the Site does not load the Meta Pixel script, tracking image or send Pixel events. Rejection leaves these disabled. Accepting starts measurement from that point; earlier activity is not replayed. Your versioned choice is stored in localStorage for six months. A new choice is requested after expiry or if you clear site storage.

Use the control below to change your choice at any time. Selecting Reject withdraws permission for future Pixel events and requests consent revocation if Meta’s script is already loaded. It does not undo prior transmissions or remove third-party cookies outside our control. LINE links work regardless of your choice. Automatically loaded Instagram embeds are separate and are not disabled by this advertising preference; their practices are described in Section 5. STORYBOARD does not control Meta’s independent data practices.

Cookie preferences

See Meta’s Privacy Policy and Meta’s Cookies Policy for provider information.

Most browsers allow users to inspect, block or delete cookies and clear site data. Browser settings may also restrict third-party cookies, tracking or autoplay. The location and effect of these controls depend on the browser and device. Blocking a technology that is necessary for media delivery or security may affect playback or site availability.

You can also use Cookie preferences in Section 8 to change the Site’s advertising-tracking choice. Browser controls can remove existing cookies and stored preferences independently.

The “นักเรียนเดิม” link opens members.storyboard.co.th, a technically and functionally separate member site. That site may use authentication, cookies, storage or other technologies that are not part of this main-site repository. Visitors should consult the notices presented on the member site. This Cookie Policy does not describe or authorize its separate technologies.

Analytics, newsletter capture, content-management integration, workshop registration, payments, authentication and additional advertising features require separate review. Before introducing technology associated with any such feature, STORYBOARD should inventory the data and provider, classify the technology, define its purpose and duration, establish a lawful basis, configure consent where required and publish an updated notice.

A future technology must not be treated as covered merely because this Policy contains general definitions of cookies or similar technologies.

We may update this Policy when the Site, providers, production configuration or applicable law changes. The updated document will show a revised “Last updated” date. If an update introduces optional technology requiring consent or another choice, the appropriate control should be provided before or when that technology becomes active.

Tax ID: 0105559096309

Email: info@storyboard.co.th
LINE: @storyboard.co.th

Before public launch, STORYBOARD must confirm:

1. the production host and all response headers, cookies and storage behavior it introduces;
2. hosting security and request-log categories, settings and retention;
3. media-streaming and content-delivery provider cookie, logging, anonymization, region, retention, DPA and subprocessor settings;
4. the deployed Site’s behavior across representative pages, videos, browsers and regions;
5. that the main Site and member site remain correctly distinguished; and
6. whether any consent banner or preference mechanism is legally required in production.