Piuda Cookie Policy

Last Updated: September 29, 2026 · Effective Date: September 29, 2026 · Version: v1.3.0

⚠️ Important Notice

Piuda (the “Service”) is not officially offered in the United States, EU member states, EEA member states, the United Kingdom, or any other country or region that Passion Factory Corporation (the “Company”) expressly designates as an unsupported region. Accordingly, this Cookie Policy is not intended to represent that the Service satisfies all requirements of laws applicable in those excluded regions, including the GDPR, UK GDPR, ePrivacy Directive, and CCPA/CPRA. For more information about excluded regions, please see Sections 4 and 25C of the Piuda Terms of Service and the Piuda Privacy Policy.

This Cookie Policy (the “Policy”) explains the types of cookies and similar technologies used in Piuda, their purposes, retention periods, and how users can manage them.

This Policy supplements the Piuda Privacy Policy and has been prepared in accordance with applicable laws, including Korea’s Act on Promotion of Information and Communications Network Utilization and Information Protection, etc., the Personal Information Protection Act (PIPA), and Japan’s Act on the Protection of Personal Information (APPI).

Any term used but not defined in this Policy has the meaning given in the Piuda Terms of Service or the Piuda Privacy Policy.

1. Company Information

2. Key Information

This summary is provided for convenience. The detailed rights and obligations are set out in the sections below.

3. What Are Cookies and Similar Technologies?

3.1 Definition

A cookie is a small text file stored on a user’s device (such as a computer, tablet, or smartphone) when the user visits a website or uses an application.

3.2 Technologies Covered by This Policy

This Policy also covers similar technologies used by Piuda.

3.3 Classification by Duration

3.4 Classification by Setting Party

4. Why the Company Uses Cookies and Similar Technologies

4.1 Essential Cookies — Authentication and Session Management

These cookies are required to support login and session continuity and may be set without separate optional consent.

4.2 Essential Cookies — Infrastructure Security

Cloudflare infrastructure cookies are used for bot management and DDoS protection and support the stable operation of the Service.

4.3 Essential Cookies — Language Preferences

These cookies remember a user’s language preference.

4.4 Cookies the Company Does Not Use

The Company does not use cookies for the following purposes.

4.5 PostHog Behavioral Analytics and Cookies

The Company uses PostHog to analyze usage patterns. Behavioral events are collected through the client-side posthog-js SDK, while LLM usage is aggregated server-side through posthog-node. In the Company’s current configuration, the PostHog client SDK uses localStorage persistence rather than analytics cookies. Only after consent does it store analytics identifiers such as distinct_id and send them with behavioral events to PostHog Cloud in the United States. Before consent, the opt-out persistence configuration prevents analytics identifiers from being stored.

4.6 Advertising Conversion-Tracking Cookies (Google Ads)

The Company uses Google Ads conversion tracking (gtag.js) to measure advertising performance. When a user arrives through an advertisement and views a landing page, submits an early-access form, or downloads the desktop app, standard gtag may set first-party advertising/conversion-linking cookies to connect an ad click with a resulting conversion.

The Company does not currently use these advertising cookies for personalized advertising, retargeting, or individual advertising profiling. The Company also does not use Meta Pixel, LinkedIn Insight Tag, or similar advertising pixels.

4.7 Newsletter Email Open and Click Tracking

The Company does not place newsletter open-tracking pixels/beacons or newsletter click-tracking redirects on the Piuda website, web application, or desktop app. These technologies are used only in newsletter emails sent to users who have given all required newsletter-related optional consents, for the purpose of measuring delivery performance and managing newsletter content and recipient lists. They are email-based tracking technologies distinct from ordinary website/app cookies and from the social-media or web advertising pixels described in Section 4.4.

The Company has not configured this newsletter tracking feature to set an additional cookie itself. As a precaution, the Company is still verifying whether Amazon SES, another external provider, or the runtime environment may issue a separate Set-Cookie header in connection with tracking requests or redirect responses. Accordingly, this Policy does not state that no cookie can ever be set in connection with those responses. If a separate cookie is confirmed in production, the Company will add its name, purpose, setting party, essential/non-essential status, expiration period, and management method to Section 5 and the Appendix.

4.7.1 How to Stop or Limit Tracking

Newsletter email open and click tracking is managed separately from ordinary website cookie settings.

Stopping newsletter emails or withdrawing consent to collection and use of personal information for marketing purposes does not affect use of the Piuda Service.

4.7.2 Notes on Measurement Accuracy

• Some mail apps and email security systems may fetch images before the user actually opens the email, so an open record may not correspond to an actual user open.
• Enterprise email systems or security services may automatically inspect or pre-fetch links, which can be recorded as clicks even when the user did not click them. The Company takes these technical limitations into account when interpreting newsletter performance metrics.
• For more information about the personal information processed, see Sections 3, 5, 10, 12, and 13 of the Piuda Privacy Policy.

5. Cookies Used by the Company

This section describes the website and web-application cookies currently confirmed by the Company. Newsletter email open and click tracking is described separately in Section 4.7. The Company has not configured newsletter tracking to set an additional cookie itself, but is conservatively verifying whether an external provider or runtime environment may set a separate cookie in connection with tracking requests or redirects. If a separate cookie is confirmed, it will be added to this section and the Appendix.

5.1 Cookies in Use

5.2 Cookies Not Used

5.3 Authentication Data Processing (Reference)

Authentication-related data associated with cookies is handled as follows.

6. Managing Cookies and Similar Technologies

6.1 Browser Controls

Users can manage acceptance, blocking, deletion, and notifications for cookies through browser settings.

Blocking all cookies may limit normal use of the Service, particularly login functionality.

6.2 Mobile Devices

6.3 Desktop App

Session information in the Electron-based desktop app is stored in the OS Keychain using Electron safeStorage. To end a session, use the logout function in the app. Some web content or external pages may use browser technologies, so the exact storage behavior may vary depending on the runtime environment.

6.4 Consent Banner Operation

The web cookies used by the Company consist of authentication, security, and language-preference cookies needed to operate the Service, plus non-essential Google Ads conversion-measurement cookies. The Company does not operate a separate consent banner for Google Ads conversion-measurement cookies and manages them through notice in this Policy + user opt-out (see Section 4.6). Users can block or delete cookies through browser settings or change Google ad personalization settings to limit use of those cookies.

PostHog behavioral analytics uses client-side localStorage rather than cookies. For personal information transferred outside Korea, the Company follows the consent process described in Section 13.4 of the Piuda Privacy Policy. When the Company operates an opt-in banner for identified behavioral analytics and anonymous-to-sign-up conversion measurement, an analytics identifier such as distinct_id is stored in localStorage and persistent behavioral tracking is enabled only after the visitor gives explicit consent. Before consent or after refusal, that identified path is not activated. The user’s consent choice itself may be stored on the device, together with the applicable policy version and timestamp, to avoid repeatedly displaying the banner and to honor the user’s choice.

Separately, the Company may operate anonymous usage statistics that do not store values on the device and do not create personal profiles. These statistics may cover visits, referrers, download-button clicks, sign-up/login starts, pricing-page views, and other key interactions. A temporary identifier used to connect page transitions within a single visit exists only in browser or app memory and is deleted when the window is closed or the app restarts, so it cannot link a returning user to a prior visit or session. IP addresses are not sent, no personal profile is created in the analytics tool, and collected fields are limited to predefined event-specific lists. The detailed scope and handling are described in Section 13.4 of the Piuda Privacy Policy.

If the Company later introduces additional non-essential cookies or tracking technologies on the website or app, such as personalized-advertising/retargeting cookies or marketing pixels, it will update this Policy and apply the notice or consent process required by the nature of the technology and applicable law.

Newsletter email open and click tracking (Section 4.7) is an email-based tracking technology separate from ordinary browser cookies set when a user visits the website. It is operated based on the consent to collection and use of personal information for marketing purposes and the consent to receive newsletter (marketing) emails under the Piuda Privacy Policy. The Company has not configured this feature to set an additional cookie itself. As a precaution, it is still verifying whether an external provider or runtime environment may set a separate cookie in connection with the tracking response. If a cookie is confirmed, the Company will update the cookie list and management instructions in this Policy.

6.5 Global Privacy Control (GPC)

If a user’s browser sends a GPC signal, the Company will make reasonable efforts to take that signal into account for non-essential identifiable data collection. The Company’s non-essential web cookies are Google Ads conversion-measurement cookies, which users can limit through the opt-out methods described in Section 4.6. Anonymous usage statistics that do not store values on the device and do not identify individuals may operate through a separate technical path.

6.6 Do Not Track (DNT)

The Company does not currently respond consistently to DNT signals. The Company’s non-essential web cookies are Google Ads conversion-measurement cookies, and the Company does not build behavioral advertising profiles. Users can limit advertising cookies using the opt-out methods described in Section 4.6.

6.7 Managing Email Tracking Technology

Newsletter email open and click tracking is managed separately from ordinary browser cookie settings. The Company has not configured the feature to set an additional cookie itself, but is conservatively verifying whether an external provider or runtime environment may set a separate cookie in connection with tracking responses. See Section 4.7.1 for ways to stop or limit tracking. If a separate cookie is confirmed, the Company will also add browser-management instructions for that cookie to this Policy.

7. Local Storage (Reference)

In addition to cookies, Piuda uses the following forms of local storage. Storage location and server transmission differ by item.

7.1 Local SQLite in the Desktop App (Free Plan Research Data)

Free plan research data, including paper metadata, analysis results, and notes, is generally stored in a local SQLite database on the user’s device.

7.2 localStorage

Piuda may use localStorage to store UI state and, with consent, to support PostHog behavioral analytics.

7.3 OS Keychain (Electron safeStorage)

Desktop app session information is stored securely in the operating system’s credential store, such as macOS Keychain, Windows Credential Manager, or Linux Secret Service, rather than in a cookie.

8. Effects of Disabling Cookies or Stopping Tracking

9. Cross-Border Transfers Related to Cookies

9.1 Overview

Among the web cookies used by the Company, Better Auth session cookies are processed in the GCP Seoul Region and therefore do not constitute a cross-border transfer. Information related to Cloudflare infrastructure cookies and Google Ads advertising cookies is transferred to the United States and therefore constitutes a cross-border transfer.

Newsletter email open and click tracking is described separately from web cookies in Section 4.7. The Company’s Amazon SES resources and email event stores are configured only in the Seoul Region. However, during final delivery, information necessary to deliver an email may be sent to a recipient’s mail service outside Korea depending on where that mail service operates. See Section 13.1 of the Piuda Privacy Policy for details.

9.2 Cross-Border Transfer of Cloudflare Infrastructure Cookie Information

9.3 Cross-Border Transfer of Google Ads Cookie Information

9.4 Essential Cookie Notice

Cloudflare infrastructure cookies are used to the extent necessary for service access and security. Restricting these technologies may limit access to the Service or certain security functions.

For additional information about cross-border transfers of personal information, see Section 13 of the Piuda Privacy Policy.

10. Additional Regional Information

10.1 Users in the Republic of Korea (PIPA / Information and Communications Network Act)

The Company is a Korean corporation and seeks to comply with applicable privacy and information-communications laws.

10.1.1 Consent and Management Rules for Cookies and Email Tracking

10.1.2 Cross-Border Transfer of Cookie-Related Information

HTTP metadata such as IP addresses and User-Agent information associated with Cloudflare infrastructure cookies is transmitted to Cloudflare’s global Edge network in the United States.

Conversion-event metadata, IP addresses, User-Agent information, and related Google Ads cookie information are transmitted to Google LLC in the United States (see Section 9.3). Users can limit this processing through the opt-out methods in Section 4.6 without affecting their ability to use Piuda.

Cross-border transfers associated with PostHog behavioral analytics use a client SDK and localStorage rather than cookies and are handled through the Article 28-8 PIPA consent process described in Section 13.4 of the Piuda Privacy Policy.

Newsletter open and click tracking is governed by Section 4.7. The Company-configured SES resources and email event stores are located only in the Seoul Region, while final email delivery may involve a mail service outside Korea depending on where the recipient’s provider operates (see Section 13.1 of the Piuda Privacy Policy).

10.1.3 Changing Cookie Settings and Effects of Blocking

See Sections 6 and 8 for cookie-management methods and the effects of restricting cookies.

10.1.4 Remedies and Complaint Channels

For privacy complaints related to cookies or similar technologies, users may contact the remedies and complaint bodies listed in Section 14.6 of the Piuda Privacy Policy.

10.2 Users in Japan (APPI)

10.2.1 Cookies and Personally Related Information

A cookie does not automatically constitute personal information under Japan’s APPI. However, the APPI may apply when cookie information can identify an individual when combined with other information or when it is handled as “personally related information” (個人関連情報).

10.2.2 Company Practices for Cookies and Email Tracking

10.2.3 Japanese-Language Version

If a separate Japanese version of the Cookie Policy is provided, it may take precedence for users residing in Japan.

10.3 Other Supported Regions

10.3.1

This Policy also applies to users in supported regions other than the United States, EU/EEA, United Kingdom, and any region the Company expressly designates as unsupported.

10.3.2

The Company applies any notice or consent process required by mandatory law in the applicable region. The web cookies used by the Company consist of essential cookies for authentication, security, and language preferences, together with non-essential Google Ads conversion-measurement cookies. The Company does not use analytics cookies or personalized advertising/retargeting cookies. Newsletter open and click tracking is described separately in Section 4.7.

10.3.3

If mandatory law in the applicable region gives users rights that are more protective than this Policy, that mandatory law prevails.

10.4 Excluded Regions, Including the United States, EU/EEA, and United Kingdom

The United States, EU member states, EEA member states, the United Kingdom, and any other country or region expressly designated by the Company as unsupported are not currently official Piuda service regions. This Policy should not be interpreted as a representation or guarantee that the Company already satisfies all requirements of laws in those excluded regions, including the GDPR, UK GDPR, ePrivacy Directive, and CCPA/CPRA (see Sections 4 and 25C of the Piuda Terms of Service).

11. Changes to This Policy

11.1

The Company may update this Policy in response to changes in the cookies or similar technologies it uses, including the introduction of non-essential cookies or tracking technologies, as well as changes in law or operating practices.

11.2

The Company will provide notice of changes as follows.

11.3

If the Company later introduces a new non-essential cookie or tracking technology on the website or app, it will update this Policy before introduction and provide the notice, consent, and opt-out mechanisms required by the nature of the technology and applicable law.

12. Contact Information

For questions about cookies or similar technologies, please contact us using the information below.

For general questions about personal information processing, see Section 22 of the Piuda Privacy Policy or contact the Company’s privacy officer.

Appendix: Cookies and Similar Technologies in Use

This Appendix summarizes the cookie list in Section 5.1 and the email-tracking technologies in Section 4.7. Actual cookie names, retention periods, and technical configurations may vary with the production environment. Material changes will be handled under the change process described in this Policy.

Cookies Currently in Use (3 Essential Cookie Categories + 1 Advertising/Conversion-Linking Cookie Category)

Cookie Categories Not Used

Non-Cookie Tracking Technologies (Newsletter Email Only)

The technologies below are email-tracking technologies separate from website/app cookies. The Company has not configured them to set an additional cookie itself. As a precaution, the Company is still verifying whether an external provider or runtime environment may set a separate cookie in connection with tracking requests or redirects. If a separate cookie is confirmed, it will also be added to the cookie list above.

Non-Cookie Local Storage (Reference)

End of Policy

This Policy was originally written in Korean. If an English or other translated version is provided, the Korean version prevails for users in the Republic of Korea. If a Japanese version is provided, it may take precedence for users residing in Japan. In other supported regions, the English version or another version separately designated by the Company may apply.

This Piuda Cookie Policy supplements the Piuda Privacy Policy and should be read together with the Piuda Terms of Service and Piuda Privacy Policy.