Privacy Policy (English translation, with EU/EEA and Switzerland Supplement)
About this translation. This is an English translation of the Suodata Inc. Privacy Policy, provided for your convenience together with the EU/EEA and Switzerland Supplement that follows it. The Traditional Chinese version of the Privacy Policy (/privacy) and of the Terms of Service (/terms) is the sole authoritative version. Where this translation and the Traditional Chinese version differ, the Traditional Chinese version prevails; this does not displace mandatory provisions of the law of the place where you are located, to the extent that law applies. Chapter numbers in this translation correspond to the chapter numbers of the Traditional Chinese version. The "Additional disclosures" section after Chapter 16 and the Supplement are not translations: they give additional, more specific information and apply together with Chapters 1 to 16.
If you are in the European Economic Area or Switzerland, please read the "EU/EEA and Switzerland Supplement" at the end of this page. It is based on the Country and Region Privacy Supplements (Appendix 1) of the Traditional Chinese version, gives you the information required by Articles 13 and 14 of the EU General Data Protection Regulation (GDPR), and prevails over the main text for you where the two differ.
Suodata Inc. (the "Company", "we", "us" or "our") takes your privacy seriously. This Privacy Policy explains how the Company collects, processes, uses and protects the personal data that you provide, or that is generated, when you use the Company's services.
This Privacy Policy is made under the Personal Data Protection Act of the Republic of China (Taiwan) (the "PDPA") and related regulations, and constitutes the notice given by the Company under Articles 8 and 9 of the PDPA. In this Policy the Company has expressly informed you of the matters listed in Article 8(1) of the PDPA; where, having been so informed, you do not object and you provide your personal data, you are presumed under Article 7(3) of the PDPA to have consented to the Company collecting, processing and using your personal data within the specific purposes listed in this Policy. Data generated automatically by your use of the Services is processed on the basis of Article 19(1)(ii) of the PDPA (a contractual or quasi-contractual relationship) and of that consent. You may refuse marketing at any time under Chapter 5 and exercise your rights under Article 3 of the PDPA as provided in Chapter 14.
1. Scope and Definitions
1. Author of this Policy and collecting entity:
- Company name: Suodata Inc. (指數資訊股份有限公司)
- Official LINE account (customer service channel): https://line.me/R/ti/p/@746cckjp (LINE ID @746cckjp)
2. Scope of "the Services": In this Policy, "the Services" means all services listed in Appendix 1 of the Company's Terms of Service, including but not limited to:
| Service | Description |
|---|---|
| lawplayer.com website | Search for legislation, court judgments, administrative interpretations, Judicial Yuan interpretations (J.Y. Interpretations and Constitutional Court judgments), company registration records, judge and prosecutor pages and past examination papers (including the corresponding data of foreign jurisdictions and of mainland China, Hong Kong and Macau, to the extent actually included, subject to the chapter of the Terms of Service titled "General Disclaimer for Foreign-Jurisdiction Data"), together with AI-assisted features, the community board, name-based judgment search (KYC) and similar features |
| LawPlayer Academy | The Company's own online course and digital content service (including the Company's own checkout), including but not limited to course videos, files, templates and access-code products; other product types are as actually listed |
| LawPlayer lite iOS App | The mobile application published on the Apple App Store (com.lawslog.campus.lite) |
| LawPlayer App | The Company's new mobile application (version 1 collects no personal data; see Chapter 8, Section 4) |
| 罰單申訴.com | A separate-domain product of the Company |
| Cloud notes, documents and knowledge management platform (including the notes marketplace) | Cloud notes, documents and knowledge management features (including but not limited to editing, storing, sharing, importing and exporting multiple document types, and AI-assisted features), and marketplace transactions in digital content products such as notes and teaching materials (including products produced by the Company and, in future, products licensed by content providers); features are made available progressively as announced and are brought within this Policy under item 4 when launched (per-service disclosure in Chapter 8, Section 7) |
| Future services | Other services that the Company launches in future and announces as being subject to this Policy (brought within this Policy on launch by announcement under Chapter 15) |
3. Relationship between the general rules and the per-service disclosures: Chapters 1 to 7 and Chapters 9 to 16 of this Policy are the general rules and apply to all of the Services. Chapter 8 contains the per-service disclosures, describing the additional data collected by, and the third-party SDKs used in, each service. Where a per-service disclosure is inconsistent with the general rules, the per-service disclosure prevails for that service.
4. Future services: When the Company launches a new service, it will update the per-service disclosures in Chapter 8 before or at launch. Where this involves a material change to the purposes of collection, the categories of data or the recipients, the Company will give prominent notice under Chapter 15. The same applies to the timing and scope of data collection for individual features of services already listed in the table in item 2 whose features are made available progressively as announced; until a feature is launched, the Company collects your data only within the scope of the general rules.
2. Notice of Collection of Personal Data
Under Article 8(1) of the PDPA, the Company informs you of the following:
1. Name of the collecting entity: Suodata Inc.
2. Purposes of collection (by the specific-purpose codes used under the PDPA):
- 040 Marketing (including marketing by email, SMS, app push notification, social media and messaging app messages, and the building and use of advertising audience lists and the attribution and measurement of advertising performance)
- 052 Internal management of registers of shareholders, members, staff or other members of a legal person or organisation
- 054 Legal services
- 063 Collection, processing and use of personal data by a non-government agency in performance of a statutory obligation
- 069 Contractual, quasi-contractual or other legal relationship matters
- 090 Consumer and customer management and service
- 091 Consumer protection
- 109 Education or training administration (LawPlayer Academy course services)
- 129 Accounting and related services (issuing invoices, bookkeeping)
- 135 Information (communication) services
- 136 Information (communication) and database management
- 137 Information and communication security and management
- 148 Online shopping and other e-commerce services
- 152 Advertising or commercial conduct management
- 157 Surveys, statistics and research analysis
- 181 Other business conducted in accordance with the business registration items or articles of incorporation
3. Categories of personal data collected:
- C001 Data identifying an individual: name, nickname, email address, mobile phone number, address (only where the payment method you choose requires it, such as buy-now-pay-later), account name, password (stored as a hash), social sign-in identifiers (Google / Facebook / LINE / Apple), device identifiers, push notification tokens, and API access tokens (if you create them in the relevant feature)
- C002 Data identifying financial details: credit card or financial account information (handled by third-party payment service providers; the Company does not directly store full card numbers; for recurring charges, the Company keeps the payment tokens issued by the payment service provider and the card information it returns)
- C011 Personal description: age, gender, date of birth, country
- C021 Family circumstances: marital status (only if you choose to provide it)
- C035 Leisure activities and interests: interest tags you select at registration or in your member settings
- C038 Occupation: the identity group you select (such as lawyer, judge or prosecutor, law student, in-house counsel)
- C051 School records: education information and exam-preparation status that you choose to provide
- C093 Financial transactions: subscription records, course purchase records, payment records, invoice information and refund records
- C132 Unclassified data: service usage records, browsing behaviour, search keywords, reading duration, checkout events, IP address, device information, pseudonymous identifiers that the Company generates for you and records mapping them to browsers, sessions and devices, advertising click identifiers and source parameters (such as gclid, fbclid, ttclid and utm parameters), A/B test assignment records, app crash and performance diagnostic records, content you post on the community board (including photos you choose to upload), and notes and document content you create, files and assets you upload and data you import from external services on the cloud notes, documents and knowledge management platform (applicable from the time that platform is brought within this Policy under Chapter 1, item 4)
The Company does not ask you to provide the special categories of personal data defined in Article 6 of the PDPA (medical records, medical treatment, genetic information, sex life, health examinations and criminal records). Please avoid entering such data in community posts, customer service conversations or search boxes. The processing of public government data of any country included in the Services (including but not limited to legislation, court judgments, administrative interpretations, Judicial Yuan interpretations, company registration records and judicial personnel information) is governed by the chapter of the Terms of Service titled "Statement on the Use of Public Data"; data of foreign jurisdictions and of mainland China, Hong Kong and Macau is also governed by the chapter titled "General Disclaimer for Foreign-Jurisdiction Data".
4. Period of use: The period of the Company's operation, and the period for which each of the purposes listed in this Policy continues to exist. Termination of your account, unsubscribing or the end of a service does not of itself extinguish those purposes. Where the law prescribes a retention period, the data is kept at least until that period ends (the purpose-persistence framework and its exceptions are set out in Chapter 10).
5. Territory of use: The Republic of China (Taiwan) and the places outside Taiwan listed in Chapter 12.
6. Recipients:
- The Company, its affiliates, and each of the services the Company operates now or in future (including those listed in Appendix 1 of the Terms of Service and those added later)
- The service partners listed in Chapter 6, item 1 (payment, invoicing, SMS, push notification, cloud infrastructure, content delivery, video streaming, email delivery, customer service messaging, data warehousing, analytics tools and others)
- Advertising and marketing partners: advertising platforms, advertising networks, advertising measurement services and providers of marketing channels; the current list is set out in Chapter 6, item 1-1, and the Company may add partners of the same category and for the same use, announcing them under Chapter 15, item 4
- A successor to the Company in a merger, acquisition, demerger or business transfer (Chapter 6, item 4)
- Content providers (collectively, partner instructors and third-party suppliers of content such as notes, courses and teaching materials; that is, the partner instructors referred to in the "LawPlayer Academy" chapter of the Terms of Service and the content providers referred to in the "Notes Marketplace and Third-Party Content Products" chapter; this Policy uses the collective term without changing the definitions in those chapters), affiliate marketing partners and joint marketing partners (only within the scope, and to the extent necessary, set out in Chapters 5 and 6)
- Authorities with a legal power of investigation
7. Manner of use: By electronic means, in writing, by telephone, SMS, the internet, app push notifications, messaging app messages and any other lawful means, including processing and analysis by automated means.
8. Your rights: Under Article 3 of the PDPA you may exercise the following rights (see Chapter 14 for how):
- To enquire about or request to review your personal data
- To request a copy
- To request supplementation or correction
- To request that collection, processing or use stop
- To request deletion
9. Consequences of not providing data: If you decline to provide some personal data, you may be unable to complete registration or payment or to use some features of the Services. You are, however, free to decide whether to provide data used for marketing (such as interest tags); not providing it does not affect your use of the basic Services.
10. Visitors and users who are not signed in: The notice in this Chapter and the whole of this Policy apply equally to data generated when visitors and users who are not signed in use the Services.
3. How We Collect Data
The Company collects your personal data in the following ways:
1. Data you provide directly:
- The mobile number, email address, name or nickname, password, date of birth, gender, country, identity group and interest tags that you enter when registering an account (whether each field is required or optional is as marked on each registration page; for fields provided for personalisation and marketing purposes, not providing them does not affect registration or use of the basic Services)
- Payment and invoice information when you subscribe to a paid service or buy a course (including your address, where the payment method you choose requires it)
- Information you provide when contacting customer service or completing forms or questionnaires
- Articles, comments and photos you choose to upload on the community board
- Notes and document content you create, files and assets you upload, and data you import from external services on the cloud notes, documents and knowledge management platform (applicable from the time that platform is brought within this Policy under Chapter 1, item 4; per-service disclosure in Chapter 8, Section 7)
- Case-related data you provide when submitting an appeal case on 罰單申訴.com (see Chapter 8, Section 5)
- Your image, voice and statements when you take part in live course sessions, online events or voice or video customer service (if a session is recorded, the Company will tell you before it starts)
- Feedback and interaction records you provide when taking part in user research (interviews, questionnaires, usability tests)
- The content of messages you exchange with the Company through the official LINE account or other customer service channels
2. Data collected automatically:
- IP address, browser type, operating system, device model and device identifiers
- Approximate geographic location inferred from your IP address (country or city level); the Company does not collect your precise location through GPS or device location functions
- Pages viewed, click records, search keywords, time on page, reading duration and checkout events
- When you arrive at the Services through an advertisement or referral link, the advertising click identifiers and source parameters attached to the URL (such as gclid, fbclid, ttclid and utm parameters); these are linked to your order when you complete a payment (see Chapter 4, item 12)
- Pseudonymous identifiers that the Company generates for you (see Chapter 7, item 3) and A/B test assignment records
- In-app event records, crash and performance diagnostic records, and push notification tokens
- Information collected by cookies and similar tracking technologies (see Chapter 7)
- Time of access and referring page
2-1. Search records:
Keywords you enter in the search box of the Services are recorded automatically for service improvement, autocomplete, analysis of popular searches and security detection. Collection works as follows:
- Visitors who are not signed in: identified by a randomly generated session identifier; where that identifier is not available, a one-way hash of the IP address and browser information is used instead. The Company does not attempt to identify any specific individual from these records. The retention, access restriction, deletion and de-identification of raw records are governed by Chapter 10, item 4; de-identified aggregate statistics (containing only the popularity of legislation, articles and interpretations, with queries containing personal data such as personal names, company names and business registration numbers filtered out) are kept permanently as the basis for features that do not require sign-in, such as autocomplete.
- Signed-in members: identified by your member ID and used for personalised ranking, push notifications and search history recall (see purpose 7 in Chapter 4 and Chapter 14). Raw records are handled in accordance with Chapter 10, item 4; aggregate statistics are kept permanently. You can enquire about, request a copy of or delete your personal search history through your member settings (if that feature is provided) or by contacting customer service through the official LINE account; a deletion request also covers the part of the restricted raw records that can be linked to your member identifier (Chapter 10, item 4).
Other people's data in search strings: The search strings you enter may contain other people's names, company names or other data (for example, when you use the name-based judgment search). Those strings are kept under restriction as provided in Chapter 10, item 4; the Company does not use them to identify, compile files on or contact the persons searched for, and does not use them for marketing or for building advertising audiences.
3. Data from third-party sources:
- When you sign in with a Google, Facebook, LINE or Apple account, the basic data provided by that service under its privacy policy and within the scope of your authorisation (such as name, email address and social identifier)
- Transaction result notifications from third-party payment services
- Advertising performance statistics returned by advertising platforms (in aggregate form that does not directly identify you), and the click identifiers that advertising platforms attach to links when you click an advertisement
- Course purchase records and contact data transferred to the Company on migration from a third-party course platform previously engaged by the Company (used for account consolidation, attaching purchased course entitlements to your account, and marketing as provided in this Policy)
4. Purposes of Use
The Company uses your personal data for the following purposes:
- Providing and improving the Services: account management, provision of features, personalised experience and service quality improvement; including sharing your account, purchase and usage records among the services listed in Appendix 1 of the Terms of Service (the website, mobile apps, LawPlayer Academy, the cloud notes platform and services added in future), so as to provide a single account, cross-service entitlements and a consistent personalised experience
- Subscription and transaction processing: payment processing, invoicing, refunds, subscription management, and management of course purchases and learning records
- Customer service: responding to your enquiries, handling complaints and troubleshooting
- Security and compliance: account verification (including OTP text messages), fraud prevention, detection of abnormal activity and automated extraction, and compliance with legal obligations
- Analysis and research: service usage statistics, user behaviour analysis, feature optimisation, and app stability and performance improvement; and, using de-identified or aggregated data and, to the extent permitted by law, identifiable data (excluding the other people's data in search strings referred to in Chapter 3, item 2-1), improving the Company's search, recommendation and AI-assisted features (including training, evaluating and improving models) and developing new products. The full text of private notes and documents you store is not used for model training unless you separately give express consent (Terms of Service, chapter "Licence and Responsibility for User Content", sections 3.6 and 3.7)
- Marketing and promotion: in the forms listed in Chapter 5 (you may unsubscribe at any time under Chapter 5)
- Personalised ranking and push notifications (signed-in members only): adjusting the ranking of search results based on your search and browsing history and, when the relevant feature is launched, notifying you of changes to legislation you follow. You can turn off or delete your history through your member settings (if that feature is provided) or by contacting customer service through the official LINE account.
- Course and learning services (LawPlayer Academy): activating courses, recording learning progress, and providing courses and after-course services together with partner instructors
- Accounting and tax: issuing and keeping transaction vouchers and invoices under the Business Entity Accounting Act and tax laws
- Personalisation and profiling: the Company uses your behavioural records, member data and transaction records to infer content, features and plans that may interest you (profiling), for ranking and recommending search results and content, audience segmentation and selecting marketing messages. The Company does not make solely automated decisions that produce legal effects concerning you or similarly significantly affect you; where automated processing is involved in account restrictions, refusal of a transaction or abuse determinations, you may request human review through the official LINE account. You may opt out of personalised marketing under Chapter 5, item 5, and request that profiling stop under Chapter 14
- User research: inviting you to take part in interviews, questionnaires, usability tests or previews of new features; participation is voluntary and does not affect your entitlements; the feedback and records collected are used only for product improvement, and separate consent is obtained before any of it that identifies you is used for marketing
- Advertising attribution and measurement: recording the advertising click identifiers and source parameters you carry when entering the Services and, when you complete a payment, linking them to that order and to your pseudonymous identifier, in order to calculate advertising performance, reconcile accounts and optimise ad delivery (under Article 19(1)(ii) of the PDPA and specific purposes 040, 152 and 157); for users connecting from the consent regions (the European Economic Area, the United Kingdom and Switzerland, Chapter 7, item 6), this linking is not carried out until their consent to marketing has been obtained. After you opt out of personalised advertising (Chapter 5, item 5), the Company no longer uses this data to serve advertising to you, but attribution records for orders already placed are kept with the transaction records (Chapter 10, item 3)
- Developing and launching new services: using your data (including de-identified data and, to the extent permitted by law, identifiable data) to research, design, test and launch new features and services; new services are brought within this Policy on launch under Chapter 1, item 4
- Corporate changes and affiliates: transfer to a successor in a merger, acquisition, demerger or business transfer under Chapter 6, item 4, and joint use with affiliates within the purposes of this Policy
- Cross-border transfer: transfer to processors and platforms outside Taiwan for processing under Chapter 12
5. Special Provisions on Marketing Use
1. Legal basis: The Company collects your data for specific purposes "040 Marketing" and "152 Advertising or commercial conduct management" under Article 19(1)(ii) (a contractual or quasi-contractual relationship) and Article 19(1)(v) (consent of the data subject) of the PDPA, and uses it for marketing within the scope necessary for the specific purposes of collection, as provided in Article 20(1).
2. Forms of marketing use: The Company's marketing use includes all or some of the following:
- (1) Email marketing (EDM): marketing email sequences about offers, new feature announcements, and course and event information. Every marketing email contains an unsubscribe link, and after unsubscribing you are placed on a permanent unsubscribe list.
- (2) Marketing text messages: the Company currently sends only account verification (OTP) text messages and does not yet send marketing text messages. Before the Company begins sending marketing text messages, it will give prominent notice under Chapter 15 and will send them only from the effective date stated in that notice; the text-message opt-out channels described in this section and in the opt-out table in item 5 take effect at the same time.
- (3) App push notifications: the Company may in future send marketing messages through app push notifications. Marketing push notifications and service notifications (such as notices of changes to legislation) are managed separately, and you can turn each off individually in the app settings or your device's system settings.
- (4) LINE official account messages: the Company may in future send marketing messages through its LINE official account to users who have added it as a friend.
- (5) Building and uploading advertising audience lists: the Company uploads your email address, mobile phone number or mobile advertising identifier (if collected), after SHA-256 hashing or other irreversible processing specified by each platform, to advertising platforms in order to build custom audiences (to show advertising to you or to exclude you from advertising) and lookalike audiences (to find potential users with characteristics similar to existing users). Platform list: in use: Meta (Custom Audiences / Lookalike Audiences) and Google (Customer Match); may be used: TikTok (Audience; the Company already uses the TikTok pixel and server-side event reporting, see item (7) and Chapter 7, but audience lists will not be uploaded until that feature is formally enabled). In addition to hashed email addresses and mobile phone numbers, the matching keys may include a hash of the pseudonymous identifier the Company generates for you (Chapter 7, item 3). Before adding any other platform, the Company will first announce that platform in the list in Chapter 6, item 1-1, and will not upload to it before that announcement. Data collected from the Company's iOS app is not included in the audience building and uploading described in this item unless the user of that app has allowed tracking under Chapter 9. Hashed data is used by each platform only to match it against that platform's existing users, and under each platform's data use policy unmatched hashes may not be used for any other purpose after matching is complete.
- (6) Remarketing: the Company may build audience groups based on your browsing behaviour (such as viewing particular pages, or entering checkout without completing payment) and serve personalised advertising to those audience groups through advertising platforms.
- (7) Server-side event reporting: in addition to browser-side tracking technologies (Chapter 7), the Company's servers report conversion events (such as sign-up, sign-in, add to cart, begin checkout, purchase, and subscription start, renewal charge, failed charge, pause, cancellation, refund and access-code activation) directly to Google Analytics 4 (Measurement Protocol), Meta (Conversions API) and TikTok (Events API), for advertising attribution, performance measurement and delivery optimisation. The data reported includes: the event name and time, order number, plan, amount and currency, an event identifier used for de-duplication (the order number, or a one-way hash of the access code; the original access code is not sent out), your pseudonymous identifier (as the GA4 user_id) or its SHA-256 hash (as the external_id for Meta and TikTok), and, for reports to Meta and TikTok, possibly your SHA-256-hashed email address or mobile phone number, your IP address, browser information, and the browser or click identifiers set by each platform (such as Meta's fbp / fbc and TikTok's ttclid). The Company's server-side events do not contain your name, email address or telephone number in plain text; the browser side and the server side use the same event identifier for the same event to avoid double counting; for users connecting from the consent regions (the European Economic Area, the United Kingdom and Switzerland, Chapter 7, item 6), no report is made until consent has been obtained.
- (8) Joint marketing: when the Company runs courses, talks, events or offers together with partner instructors, affiliate marketing partners or other joint marketing partners, it may, to the extent necessary for that joint marketing purpose, provide your name or nickname, contact details (email address, mobile phone number) and registration and purchase records to the partner for that event, so that the Company or the partner can send you marketing messages related to that event. The name of the partner for each joint marketing activity will be shown on the event page, registration form or message. Partners are bound by contract with the Company to use your data only for the purpose of that event and may not use it for other purposes or provide it to any other third party. You may refuse joint marketing through any of the channels listed in item 5.
- (9) Advertising attribution: under Chapter 4, item 12, when you complete a payment the Company links the advertising click identifiers and source parameters you carried when entering the Services to that order and to your pseudonymous identifier; this record is used to calculate advertising performance and reconcile accounts, and may be used as the basis for the exclusion audiences in item (5) and the event reporting in item (7).
3. Free means of refusal at first marketing contact: Under Article 20(3) of the PDPA, on its first marketing contact with you the Company will provide you with a means of refusing marketing, at the Company's expense (such as an unsubscribe link or a free reply mechanism). The audience matching, remarketing and event reporting in item 2(5), (6) and (7) are not carried out by sending messages; the Company provides a marketing contact switch in member settings (account centre) as the means of refusing those forms of marketing.
4. Marketing stops on refusal: Under Article 20(2) of the PDPA, once you refuse marketing, the Company will immediately stop using your personal data for marketing. An email unsubscribe takes effect immediately when you click the unsubscribe link; for other channels, messages already scheduled and in transit stop completely no later than 7 working days after your refusal.
5. Opt-out table:
| Marketing channel | How to opt out | Notes |
|---|---|---|
| Email (EDM) | The "Unsubscribe" link at the bottom of each email (including one-click unsubscribe in the email header) / member settings (account centre) / contact customer service through the official LINE account | After unsubscribing you are placed on the permanent unsubscribe list |
| Marketing text messages | Reply as stated in the message (for example, reply STOP) / contact customer service through the official LINE account | Takes effect when the Company begins sending marketing text messages |
| App push notifications | Turn off marketing push notifications in the app settings / device system notification settings / contact customer service through the official LINE account | Turning off marketing push notifications does not affect the service notifications you have chosen |
| LINE official account | Block or delete the official account as a friend / follow the instructions in the message / tell the official account's customer service that you wish to unsubscribe | Takes effect when the Company begins LINE marketing |
| Advertising audience lists and remarketing | The marketing contact switch in member settings (account centre) / contact customer service through the official LINE account and ask to be excluded from audience lists; you can also manage or opt out of personalised advertising in the ad preference settings of each platform, such as Meta, Google and TikTok | Under its operating procedures, the Company removes you from the audiences it has built in a subsequent list synchronisation; platform-side ad settings are provided by each platform |
| Opt out of all channels at once | Turn off all marketing contact in member settings (account centre) / contact customer service through the official LINE account and say "refuse all marketing" | The Company will stop all of the marketing uses listed above |
6. Protection of minors: The Company does not include users known to be under 18 in advertising audience lists and does not serve them personalised advertising.
7. Effect of opting out: Opting out stops only messages of a "marketing" nature. Transaction notices (payment confirmation, invoice issuance, refund progress), account security notices (OTP, unusual sign-in) and notices required by law or about material changes to the Services are necessary to perform the contract and legal obligations and do not stop when you opt out.
6. Sharing and Disclosure of Data
The Company does not sell your personal data to third parties. It shares or discloses your data only in the following cases:
1. Service partners processing data on the Company's behalf:
- Third-party payment services: TapPay (喬睿科技股份有限公司), NewebPay (藍新科技股份有限公司), AFTEE buy-now-pay-later (恩沛科技股份有限公司), LINE Pay (LawPlayer Academy checkout), Apple (in-app purchase): processing payment transactions
- Electronic invoicing service: ezPay cloud invoicing: issuing and delivering electronic invoices (name, email address, business registration number, carrier information)
- Text message services: every8d, Twilio: sending account verification (OTP) text messages (mobile phone number)
- Push notification services: Apple APNs, Google FCM: delivering app push notifications (push notification tokens)
- Content delivery network and security protection: Cloudflare, Inc.: all connections to the Services are routed through its network, which processes IP addresses, request headers and browser information for caching and acceleration, blocking malicious traffic and automated extraction, bot detection, and applying the regional rules set out in this Policy according to the country from which you connect
- Video streaming service: Bunny.net: delivering LawPlayer Academy course videos, processing the IP address and browser information of the playing device
- Read-aloud (text-to-speech) services: OpenAI, ElevenLabs, Google (Cloud Text-to-Speech), MiniMax, Microsoft (Azure): when you use the read-aloud feature, the text you choose to have read aloud (such as legislation text) is sent to these services to generate speech; your account data is not sent
- Email delivery service: Resend: delivering transactional and marketing emails (recipient address, nickname, email content) and reporting delivery, bounce and spam complaint status (on receiving a complaint, the Company unsubscribes you at the same time); open and click statistics for marketing emails, if enabled, are used only to measure marketing performance
- Customer service messaging platform: LY Corporation (LINE official account): when you contact the Company through the official LINE account, message content is transmitted and stored on the LINE platform and handled under its privacy policy
- Data warehousing: Google Cloud (BigQuery) and cloud object storage engaged by the Company: storing, under Chapter 10, item 4, de-identified event data (BigQuery data is located in Taiwan) and access-restricted raw search records
- Cloud infrastructure and cloud storage providers: data hosting, and storage and backup of user content and files; if the Company changes or adds a main cloud storage provider so that the transfer locations listed in Chapter 12 change, it will give notice under Chapter 15
- Analytics tools: Google Analytics 4 (including the server-side Measurement Protocol, using your pseudonymous identifier as the user_id to combine usage records across devices), Mixpanel (product usage analytics identified by member identifier), Firebase Analytics and Firebase Crashlytics: usage behaviour analysis and app stability diagnostics (see Chapters 7 and 8)
- Third-party AI platforms (link-out type: Perplexity AI, OpenAI, Anthropic, Google, xAI): the "AI reads the judgment for you" and "AI looks at the company for you" features are triggered by the user, and send public legal information (such as a judgment summary or company name) as a prompt to the third-party AI platform the user chooses for analysis. The Company only provides the prompt template and link and does not automatically send users' personal data. After the user clicks, that information is handled under the privacy policy of the AI platform concerned, which the Company cannot control
- AI model providers (processor type): if the Company provides features in which its systems send your content to an AI model provider for processing (including but not limited to the AI-assisted features and web research feature described in Chapter 8, Section 7, brought within this Policy on launch under Chapter 1, item 4), when you use those features the instructions you enter and the content processed by the feature are sent to AI model providers engaged by the Company, in categories including but not limited to Anthropic, OpenAI and service providers compatible with their APIs (the providers actually used are listed in Chapter 8, Section 7 and Chapter 12). An engaged AI model provider may process your data only to the extent necessary to provide the feature and is bound by its contract with the Company or its published terms of service; to process your content, the Company engages only providers that commit not to use content received through their API to train models; this does not apply where you bring your own API key or specify your own endpoint. Where you connect an AI service with your own API key or your own endpoint, the recipient is the provider you specify, its processing is governed by your arrangement with that provider, and it is not processing on the Company's behalf. The Company does not send your stored private content to AI model providers unless you trigger the relevant feature or your settings provide for it.
- External search service providers (web research feature): if the Company provides a web research feature (brought within this Policy on launch under Chapter 1, item 4), the query strings you enter are sent to an external search service engaged or set up by the Company; where an overseas provider is used, its name and location will be added to this list and to Chapter 12 under Chapter 15 when the feature is launched
The processors listed above process your data only to the extent necessary to provide their services and are bound by contract and by law.
1-1. Advertising platforms (joint or independent collectors):
- In use: Meta (Meta Pixel, Conversions API, Custom / Lookalike Audiences), Google (Google Ads remarketing and conversion tracking, Customer Match, remarketing lists exported from GA4 audiences, and the display of advertising through AdSense and Google's advertising network), TikTok (TikTok Pixel, Events API)
- Embedded content: some pages of the Services embed YouTube videos; when they load, Google may set cookies and collect browsing information under its policies
- May be used: TikTok audience list upload (Audience; nothing is uploaded until formally enabled, and this list will be updated under Chapter 15 before enabling)
- For data these platforms collect themselves, or link to their user profiles after matching, they are independent collectors or entities that use the data jointly with the Company, and the data is handled under each platform's privacy policy. The data use terms the Company has agreed with each platform restrict the platform to processing data uploaded by the Company only for audience matching and the advertising delivery commissioned by the Company. You can manage or opt out of personalised advertising in each platform's ad preference settings (Chapter 5, item 5).
2. Content providers and joint marketing partners (recipients):
- Content providers (collectively, partner instructors and third-party suppliers of content such as notes, courses and teaching materials; that is, the partner instructors referred to in the "LawPlayer Academy" chapter of the Terms of Service and the content providers referred to in the "Notes Marketplace and Third-Party Content Products" chapter; this Policy uses the collective term without changing the definitions in those chapters):
- Partner instructors: when you buy a partner instructor's course on LawPlayer Academy, the Company may provide your nickname, email address, course purchase record and learning progress to that instructor for course delivery, marking assignments, after-course service and joint marketing under Chapter 5, item 2(8).
- Other content providers: when you buy notes, teaching materials or other products licensed by a third-party content provider and sold by the Company, the Company in principle provides that provider only with sales statistics and revenue-share reconciliation information that does not directly identify you; where the nature of the product requires the provider to deliver after-sale service, marking or other individual interaction, the Company provides only your nickname and the information necessary to deliver that service, and states this on the product page.
- The Company does not provide your payment data (credit card or financial account information) to any content provider.
- Affiliate marketing partners: for orders placed through an affiliate partner's referral link, the Company provides the partner only with order statistics and revenue-share reconciliation information that does not directly identify you, and does not provide your name, contact details or other personal data.
- Joint marketing partners: handled under Chapter 5, item 2(8); the partner for each event is named on the event page.
- Counterparties in the infringement notice procedure: if you submit a notice or counter-notice under the chapter of the Terms of Service titled "Notice, Takedown and Restoration for Rights Infringement", the Company may forward the content of the notice or counter-notice (including your name and contact details) to the person who provided the content or to the original notifier so that they can respond to the dispute and exercise their legal rights; that use is limited to handling the dispute.
3. Legal obligations:
- Where required by law, court order or a lawful request of a government authority
- To protect the rights, property or safety of the Company, users or the public (including investigating conduct that infringes the Company's rights and gathering evidence for litigation, see Chapter 10, item 7)
4. Corporate changes:
- If the Company undergoes a merger, acquisition, demerger or asset transfer, your personal data may be transferred to the successor. The Company will notify you before the transfer; the successor will continue to use the data already collected within the purposes and scope disclosed in this Policy, and any change of purpose or manner of use will be handled under Chapter 15.
- The Company's affiliates may jointly use your data, within the scope of the recipients listed in Chapter 2, item 6, only to provide the Services, for internal management and for the marketing purposes set out in this Policy, and are bound by the same obligations as the Company.
7. Cookies and Tracking Technologies
1. Cookies and tracking technologies used by the Services:
| Type | Purpose | Duration |
|---|---|---|
| Necessary cookies | Keeping you signed in, security verification, sign-in status hint (lp_auth_hint), traffic classification marker (lp_sc, used only for measurement segmentation) | Session up to 90 days |
| Consent-region flag (lp_geo_eea, necessary) | Indicates that you are connecting from a consent region (the European Economic Area, the United Kingdom or Switzerland, item 6), so that the Services keep analytics and marketing technologies switched off until consent is obtained; the value is a fixed flag only and contains no country or other personal data | 12 hours |
| Consent record (lp_consent, necessary) | Records the choice you make in the consent banner or "Cookie settings" (version, whether analytics and marketing are each accepted, time of the choice) so that the Services operate according to your choice; written only by your browser, and the value contains no personal data | 12 months |
| Consent receipt ID (lp_consent_rcpt, necessary) | A random consent ID generated each time you make or change a choice, allowing you to look up the record of that choice and allowing the Company to prove your choice (item 7); written only by your browser | 12 months |
| Functional cookies | Remembering your preferences | Up to 1 year |
| Analytics cookies | Understanding how the Services are used (Google Analytics 4); in the consent regions, set only after you consent to analytics | Up to 2 years |
| Advertising cookies (in use) | Advertising performance tracking and remarketing (Meta Pixel, Google Ads, TikTok Pixel); in the consent regions, set only after you consent to marketing | Up to 1 year |
| Attribution cookies and local storage | Recording the advertising or referral channel through which you entered the Services (lp_attr: utm parameters, advertising click identifiers and the Company's first-party click code; lp_ref: short-link code; lp_coupon: coupon code), for order attribution, affiliate revenue-share reconciliation and marketing performance statistics; in the consent regions, lp_attr is set only after you consent to marketing | lp_attr up to 90 days; lp_ref and lp_coupon up to 30 days |
| First-party visitor identifier (lp_vid) | A randomly generated value that recognises repeat visits from the same browser, used to record the time of first visit, for usage analysis across visits, and to map to your pseudonymous identifier after you sign in (item 3); in the consent regions, not set until you consent to analytics | Up to 400 days (extended on each visit) |
| Session identifier (lp_sid) | Recognises the consecutive actions of a single visit, used for search records, usage analysis and security detection; in the consent regions, not set until you consent to analytics | 30 minutes of inactivity |
| First-touch and click records (__lp_first_touch, __lp_click) | Record the source through which you first entered the Services and advertising click identifiers, for order attribution and marketing performance statistics; in the consent regions, written only after you consent to marketing | __lp_first_touch up to 7 days; __lp_click up to 90 days |
| On-site placement click record (lp_pid; local storage lp_pidn) | Records the on-site promotional placement you most recently clicked (placement code, position and time; lp_pidn also stores the name of the promoted item), used to attribute a subsequent order to that placement; written when you click an on-site promotional placement | lp_pid 30 days |
| Internal test marker (lp_it) | Written only when a page is opened with the Company's internal testing parameter, used to exclude test traffic from statistical reports; ordinary visitors do not receive it | 180 days |
| Service entry and test-group markers (lp_app_entry, lp_live_shell) | Mark the entry point through which you opened the Services from the app, and the A/B test group assignment on live-session pages | lp_app_entry 1 day; lp_live_shell 30 days |
| Advertising display (AdSense / Google's advertising network) | Displaying advertising on some pages to users who have not paid, with measurement and personalisation by Google under its policies | As set by Google |
| Local temporary storage | Temporary storage of checkout data (sessionStorage, cleared when the browser is closed) | Session |
2. Management of tracking code: The tracking code on the Services is loaded and managed directly by the Company's own code, and the items loaded are limited to those listed in this Chapter and in Chapter 5; the Company has stopped using Google Tag Manager.
3. Server-side tracking and pseudonymous identifiers: In addition to the browser-side technologies in the table above, the Company's servers report events directly to the GA4 Measurement Protocol, the Meta Conversions API and the TikTok Events API under Chapter 5, item 2(7). These reports do not depend on browser cookies, so they cannot be stopped simply by clearing cookies; if you wish to refuse them, please use the opt-out table in Chapter 5, item 5. In the consent regions, these reports require your consent (items 6 and 7). For each member, the Company generates a pseudonymous identifier from the member ID using a keyed one-way hash (HMAC), which serves as the GA4 user_id and as the matching key for server-side events and audience lists, and whose SHA-256 hash serves as the external_id for Meta and TikTok; third parties cannot derive your member ID, email address or telephone number from this identifier. When you sign in, the Company creates an identity mapping record linking that pseudonymous identifier to your browser identifiers at that time (the first-party visitor identifier and the GA4 client id), your session identifier, a hash of your app device credential, and the advertising click identifiers carried by orders you have paid for, in order to combine the usage records of the same member across devices, build and exclude audience lists, and attribute advertising performance. Where the same browser maps to more than one member, the Company does not on that basis merge different members into one person. The retention and revocation of this record are governed by Chapter 10, item 4-2.
4. Enabling advertising tracking platforms: The Company uses the TikTok Pixel and the TikTok Events API (listed in the table in item 1 and in Chapter 5). The Company may in future use tracking technologies of other platforms of the same kind; until formally enabled, those platforms' tracking code will not run on the Services, and when they are formally enabled the Company will update the tracking technology table in this Chapter.
5. Managing cookies: You can refuse or delete cookies through your browser settings. Turning off cookies may, however, cause some features not to work properly. Users in the consent regions can also manage cookies through "Cookie settings" in the footer under item 7.
6. Users in the European Economic Area, the United Kingdom and Switzerland (consent regions): The Company's systems determine the country from which you connect, and this item applies to users connecting from the European Economic Area, the United Kingdom or Switzerland (the "consent regions"). In the consent regions, until your consent is obtained, the Company does not set Google Analytics, Google Ads, Meta or TikTok cookies, does not load the Meta or TikTok pixels, does not set persistent cookies used to identify visitors, does not report events to analytics or advertising platforms (including the server-side reports in item 3), does not create identity mapping records, and does not include you in any audience list. Before consent, Google's tags operate in the "denied" state under Google Consent Mode: they do not read or write cookies, advertising click identifiers are redacted, and only cookieless connection signals are sent (such as the page URL, the time and the information a browser ordinarily sends when connecting), for Google's aggregate statistics and modelling, and not to serve advertising to you individually. Only after you consent does the Company load or set the relevant technologies, according to the categories you have accepted (analytics, marketing); after you withdraw consent, the related cookies on the Services' domain expire, the pixels stop operating, and event reporting stops according to your choice.
7. Managing and withdrawing consent:
- Three options presented equally: when users in the consent regions first visit, the Services ask for their choice in a banner, presenting "Accept all", "Necessary only" and "Settings" with equal size and weight, so that refusing is as easy as accepting; in "Settings", you can choose separately for analytics (Google Analytics 4) and marketing (Google Ads, Meta, TikTok). Closing the banner (for example by pressing Esc) counts as choosing "Necessary only"; continuing to browse or scrolling the page is not treated as consent.
- Global Privacy Control (GPC): if your browser sends a Global Privacy Control signal and you have not yet made a choice, the Services treat you as refusing analytics and marketing; you can still make a different choice in "Cookie settings".
- Withdrawal at any time: you can change or withdraw your consent at any time through "Cookie settings" in the footer, and withdrawing is as easy as giving consent; after withdrawal, the related processing stops under item 6. Withdrawal does not affect the lawfulness of processing based on consent before its withdrawal.
- Consent ID and look-up: each time you make or change a choice, the Services generate a random consent ID, stored in your browser (lp_consent_rcpt) and shown in the "Cookie settings" panel. The Company's servers keep a record of that choice consisting of the consent ID, time, version, the choice for each category, interface language, country of connection, device type (desktop, mobile or other) and a digest of the explanatory text you were shown, without your IP address or full browser information, and keep it as proof of consent for 24 months; where a dispute or legal proceedings are involved, retention is extended under Chapter 10, item 7. You can provide your consent ID through the channels in Chapter 14 to look up the record of that choice.
- Asking again after updates: when the banner's explanations, categories or listed third parties change materially, your earlier choice lapses and the Services will ask again; the same applies when your choice record reaches 12 months.
8. Per-Service Disclosures
This Chapter describes the data collected and the third-party SDKs used by each service in addition to the general rules. The general rules (Chapters 1 to 7 and Chapters 9 to 16) apply to every service.
1. lawplayer.com website
- Tracking technologies: GA4, Meta Pixel, TikTok Pixel, Google Ads remarketing and AdSense advertising display, as set out in the table in Chapter 7, and the server-side event reporting listed in Chapter 5; the Meta Pixel and the TikTok Pixel are loaded only on pages of the Traditional Chinese interface.
- Search records: handled under Chapter 3, item 2-1.
- Community board: articles and comments you publish are public content that anyone (including search engines) may view, store or reproduce; please do not disclose your own or anyone else's personal data in posts.
- Name-based judgment search (KYC) and company search: the Company records search activity (query string, time, IP) for security detection and abuse prevention; when you search for information about others (including the corresponding data of foreign jurisdictions and of mainland China, Hong Kong and Macau included in the Services), you must yourself comply with the Personal Data Protection Act and the personal data protection laws of the jurisdiction to which the data relates (see the chapters of the Terms of Service titled "Disclaimer for Company Registry Search", "Disclaimer for Name-Based Judgment Search (KYC)" and "General Disclaimer for Foreign-Jurisdiction Data").
- Data subjects in public government data: individuals who are not users of the Services (such as parties named in court judgments, company registration records and other public government data of any country) who seek redaction or correction of, or object to, data included in the Services may use the procedures in the chapter of the Terms of Service titled "Redaction of Personal Data in Judgments and Complaints", item 5 of the chapter titled "Judge and Prosecutor Pages" and item 5 of the chapter titled "Algorithmically Derived Data", or contact the Company by the means listed in Chapter 14 of this Policy; for data of foreign jurisdictions and of mainland China, Hong Kong and Macau, the verification period may be reasonably extended (see the chapter of the Terms of Service titled "General Disclaimer for Foreign-Jurisdiction Data"). However, where a data subject exercises the right under the Personal Data Protection Act to enquire, correct, supplement, stop collection, processing or use, or delete, the time limit for handling remains that set by Article 13 of that Act, and the extension does not apply.
2. LawPlayer Academy
- Checkout data: payments are processed through TapPay, NewebPay, AFTEE or Apple in-app purchase (Chapter 6, item 1); invoices are issued by ezPay cloud invoicing.
- Record of consent to the digital content exception to the right of rescission: if you tick the box at checkout agreeing to the immediate supply of digital content, the Company records the time of consent, your member identity and the version of the terms text you agreed to (textVersion) as proof of consent under the Consumer Protection Act and the Regulations Governing Reasonable Exceptions to the Application of the Right of Rescission in Distance Sales, and keeps it for the same period as the transaction records (Chapter 10).
- Refund handling: applications and handling records for the 7-day refund window (account, order, reason for refund) are kept with the transaction records.
- Anti-piracy and traceability information: the Company may embed information identifying the purchaser (such as the account identifier) in course videos or other digital content to prevent unauthorised recording and distribution and to trace the source of infringement in individual cases; this information is not used for any other purpose.
- Affiliate revenue share: when a sale is made through a referral link, the system records attribution information (referral code, time of sale); information provided to affiliate partners is handled under Chapter 6, item 2 (it does not include your personal data).
- Partner instructor courses: the scope of data instructors receive is governed by Chapter 6, item 2.
3. LawPlayer lite iOS App (com.lawslog.campus.lite)
In addition to what is described in the general rules, this App uses the following SDKs and collects the following data:
- Firebase Analytics (Google): linked to your member ID, collecting your in-app usage behaviour such as search keywords, reading duration, checkout events and screen views, for service improvement, personalised experience and the Company's own statistical analysis. Unless you have allowed tracking through the ATT authorisation prompt under Chapter 9, data collected from this App is not used for the advertising audience building and uploading, remarketing or identifier-bearing server-side reporting described in Chapter 5, item 2(5), (6) and (7).
- Firebase Crashlytics (Google): collecting crash and performance diagnostic data (device model, operating system version, program stack trace at the time of the crash) to improve stability.
- Push notifications (APNs / FCM): if you allow push notifications, the Company collects and stores your push notification token to deliver service notifications; marketing push notifications are handled under Chapter 5.
- Camera and photo library permissions: accessed only when you publish a post on the community board and choose to attach a photo, after authorisation through the iOS system permission; this App does not read your camera or photos in the background. You can withdraw the permission at any time in iOS Settings.
- In-app purchase: the lifetime plan is processed through Apple in-app purchase (IAP), and payment data is handled by Apple under its policies; if you separately subscribe to a monthly or annual plan on the Company's website, the disclosures in Sections 1 and 2 of this Chapter and in Chapter 6 apply to that website transaction; when this App opens a page of the Company's website, it does so in the device's system browser or the browsing view provided by the system.
- Account deletion: this App has a built-in account deletion feature (in the App settings), and you can request deletion of your account in the App at any time; data after deletion is handled under Chapter 10.
- App Tracking Transparency (ATT): see Chapter 9.
- The disclosures in this Section are consistent with this App's privacy disclosure (App Privacy) on the App Store; if there is any discrepancy, the Company will correct the disclosure or this Section once it becomes aware of it.
4. LawPlayer App (new mobile application)
- The current version of this App (v1) does not offer account registration, has no third-party analytics or advertising SDK installed, and does not actively collect your identity data. However, when this App connects to the Company's servers to obtain data, the servers automatically record connection logs such as IP address and request time (handled under Chapter 3, item 2 and Chapter 10, item 4).
- If a future version adds account, analytics or other data collection features, the Company will update this Section before that version is released and give notice under Chapter 15.
5. 罰單申訴.com
- This website is a separate-domain product of Suodata Inc. and is subject to the whole of this Policy.
- Tracking technologies: this website has its own separate Meta Pixel installed for advertising performance tracking and remarketing (Chapters 5 and 7); its audience lists are managed separately from those of lawplayer.com.
- Data you actively provide when completing forms or submitting cases on this website (such as contact details, and ticket and case information) is used only to provide that service, for customer service and for statutory retention, and is not used for marketing, advertising audience building or remarketing; the Meta Pixel on this website is not installed on the appeal form or case-related pages.
6. Future services
- When future services of the Company are launched, a corresponding Section will be added to this Chapter describing the additional data and SDKs they involve.
- Until the corresponding Section is added, those services collect, process and use your personal data only within the scope of the general rules.
7. Cloud notes, documents and knowledge management platform (including the notes marketplace)
Under the mechanism in Appendix 1 of the Terms of Service and Chapter 1, item 4 of this Policy, the services and features described in this Section are brought within the scope of this Section as each feature is launched; until the corresponding feature is launched, the Company collects, processes and uses your personal data only within the scope of the general rules. The actual availability and scope of each feature are as stated in platform announcements and on the relevant pages.
- Storage and processing of document content and uploaded assets: notes and document content you create, files and assets you upload and data you import on this platform are stored in the Company's databases and storage systems and processed only to provide, maintain and back up the service and to process them as you instruct, including but not limited to creating search index copies, generating previews and thumbnails, format conversion and disaster recovery backups; the scope of licence is governed by the chapter of the Terms of Service titled "Licence and Responsibility for User Content", and they are not used for marketing. Retention and deletion are governed by Chapter 10 (including item 4-1).
- Visibility in collaborative workspaces: if you take part in a multi-user workspace, members of that workspace can view and search content in the workspace within their permissions; the editor attribution contained in document version history is visible to other members of that workspace.
- Local browser storage: to support autosave and offline editing, some editing content is temporarily stored in your device browser's local storage (such as IndexedDB and localStorage); this data is stored on your device, not on the Company's systems, and is deleted when you clear your browser data.
- Public nature of share links: if you create a share link for a document, anyone who obtains the link can access the document content (including card content displayed with whiteboard documents) without signing in, and may view, store or reproduce it; please do not disclose your own or anyone else's personal data in shared documents. If you provide content containing personal data to a third party through a share link, that is your own act of providing data externally.
- Data flow of AI-assisted features: when you use AI-assisted features, the instructions you enter and the document content processed by the feature are sent for processing to processor-type AI model providers as defined in Chapter 6, item 1, and this may involve the cross-border transfers listed in Chapter 12; the Company does not send your stored private content to AI model providers unless you trigger the relevant feature or your settings provide for it.
- Web research feature: when you use the web research feature, the query strings you enter are sent to an external search service provider (Chapter 6, item 1), and the content of relevant web pages is retrieved and sent to an AI model provider to generate an answer. Please do not enter the special categories of personal data defined in Article 6 of the Personal Data Protection Act (medical records, medical treatment, genetic information, sex life, health examinations and criminal records) or other sensitive information in queries.
- AI usage records: the Company records the use of AI features (feature, usage such as number of tokens, time) for billing, quota management and abuse prevention.
- API access tokens: if you create API access tokens, the Company records the creation, use and revocation of tokens (including access time and IP address) for security detection and abuse prevention; when you authorise external programs or tools to access your content with a token, the data provided through that access is provided by you to the third party yourself; those external programs or tools are not provided by the Company, and the Company cannot control their data processing.
- Deletion mechanism: when you delete documents, files or other content, the system uses soft deletion and deferred purging, rather than immediately and physically deleting them from all systems; until purging is complete, the content may still be temporarily held in the systems or in backups, and the retention and deletion periods are governed by Chapter 10.
- Notes marketplace transactions: when you buy products in the notes marketplace, the disclosures in Section 2 of this Chapter apply, with the necessary modifications, to checkout payments, invoices, records of consent to the digital content exception to the right of rescission, refund records and anti-piracy and traceability information; the scope of data content providers receive is governed by Chapter 6, item 2, and does not include your payment data.
9. iOS App Tracking Transparency (ATT)
- Under Apple's App Tracking Transparency (ATT) framework, "tracking" means linking user or device data collected from an app with data collected from other companies' apps or websites for targeted advertising or advertising measurement, or sharing such data with data brokers.
- The Firebase Analytics currently used in the Company's iOS app is first-party analytics for the Company's own services; the Company has excluded data collected from the iOS app from its advertising audience building and identifier-bearing server-side reporting pipelines (see Chapters 5 and 8), and does not link data collected in the app with data from other companies' apps or websites for cross-app tracking.
- If the Company's apps in future enable features involving cross-app tracking (such as third-party advertising attribution SDKs), the Company will, in accordance with Apple's rules, separately ask for your permission through the system ATT authorisation prompt before tracking; without your permission, the Company will not carry out cross-app tracking.
- Refusing ATT authorisation does not affect your use of any service feature of the App.
- You can change your authorisation at any time in iOS "Settings > Privacy & Security > Tracking".
10. Retention and Deletion of Data
- Purpose-persistence principle: The Company continues to keep, process and use your personal data for as long as each of the purposes listed in this Policy continues to exist. Those purposes include: performance and evidencing of the contract, transactions and accounting, dispute handling and proof, audit, fraud prevention and information security, provision and improvement of the Services, product analysis and new service development, statistical research, legal compliance, and marketing (until you refuse marketing). Termination of your account, unsubscribing or the ending of all or part of the Services does not of itself extinguish those purposes. When a purpose ceases to exist or the period expires, the Company deletes the data or stops processing or using it under Article 11(3) of the PDPA, unless it is necessary for the performance of the Company's business or you have consented in writing. Where the law prescribes a retention period, the Company keeps the data at least until that period ends. Where you exercise your rights under Chapter 14, that Chapter applies.
- Account data: kept while your account exists and, after closure, for as long as the purposes persist, to handle post-closure transaction disputes, refunds, fraud prevention and verification of complaints about account takeover, audit and legal compliance; not used for marketing after closure.
- Transaction records and proof of consent (including invoice information, records of consent to the digital content exception to the right of rescission, and records of the version, time, source and scope of your agreement to the Terms of Service and this Policy): kept at least for the statutory period under the Business Entity Accounting Act and tax laws, and for as long as the purposes of the contractual relationship, dispute handling and proof persist.
- Service usage records:
- Raw records in operational systems (including search strings, session identifiers or member identifiers, and the IP addresses and browser information contained in access records for judgment pages, judge pages and similar pages): kept in the Company's online operational systems for the cycle set by its operating procedures and then deleted from those systems (exceptions under item 7).
- Restricted raw search records: the Company also keeps the raw search records in full in an access-restricted storage area (Google BigQuery and the Company's own storage equipment), for purposes limited to: (1) audit and checking the integrity of service records; (2) reconciliation of accounts, performance and attribution; (3) handling and verifying requests made under Chapter 14 by you or by other data subjects to enquire, obtain a copy, correct, stop use or delete; (4) detecting and investigating automated extraction, abuse, fraud and information security incidents; (5) dispute handling, preservation of evidence and proof; and (6) producing de-identified data from those records for the uses set out in the next point. That storage area may be accessed only by authorised personnel in the course of their duties; it is not used for marketing or for building advertising audiences, nor to identify, compile files on or contact the persons searched for. Those records are kept for as long as each of those purposes continues to exist, and the Company reviews at least once a year whether each purpose still exists; where a purpose has ceased, the records are deleted or de-identified under Article 11(3) of the PDPA. Where you request deletion under Chapter 14, the Company deletes or de-identifies the records that can be linked to your member identifier, except in the circumstances described in item 7.
- De-identified event data: de-identified event data produced from the records above (removing fields that directly identify an individual; one-way hashing session identifiers with a key that changes daily; pseudonymising visitor and device identifiers) is moved to the Company's data warehouse (the Taiwan region of Google BigQuery, cloud object storage engaged by the Company and the Company's own storage equipment) and kept and used permanently for statistical analysis, service improvement, performance measurement, model improvement and new product development, and not to identify specific individuals. Event data already uploaded or reported to third-party analytics and advertising platforms is retained on those platforms under each platform's policy (Chapter 7); the validity period of audiences the Company sets on a platform is set according to that platform's specifications and the Company's operating procedures.
- De-identified aggregate statistics (containing only the popularity and trends of legislation, articles and interpretations, with personal data such as personal names, company names and business registration numbers filtered out): kept permanently as the basis for improving services such as autocomplete
- Personal search history (signed-in members only): kept while your membership exists; you can enquire about, request a copy of or delete it under Chapter 14
4-1. User content (cloud notes, documents and knowledge management platform; applicable from the time that platform is brought within this Policy under Chapter 1, item 4):
- Notes and document content you create, files and assets you upload and data you import are kept while your account exists, so that you can use the Services.
- When you delete particular content, the system uses soft deletion and deferred purging and completes purging under the Company's operating procedures; until purging is complete, the content may be temporarily held in the systems or in backups, and backups and logs are handled under item 8. The Company's system backups exist for overall disaster recovery and are not provided for restoring your individual content; please export your own backups of important content under the chapter of the Terms of Service titled "Cloud Notes, Documents and Knowledge Management Features".
- After your account is closed, except where the law requires retention, a purpose listed in item 1 persists or a circumstance in item 7 applies, the Company handles your user content under item 2 and then deletes or de-identifies it.
4-2. Transaction and conversion event records and identity mapping records:
- Transaction and conversion events recorded by the Company's servers (including order number, plan, amount, pseudonymous identifier, event identifier and the results of reports to each platform) are kept for as long as the purposes of reconciliation, dispute handling, performance measurement, audit and legal compliance listed in item 1 persist.
- The identity mapping records in Chapter 7, item 3 are kept while your account exists and thereafter for as long as the purposes persist; when you close your account, withdraw consent or request deletion, the Company marks them as revoked and stops using them for marketing, and their subsequent deletion or de-identification follows applicable law and the Company's operating procedures.
- Records of your consent to or opt-out from marketing (including the item, time, source and the provision relied on) are kept as proof of consent under item 3.
- Marketing suppression list: to ensure that you no longer receive marketing messages after unsubscribing, your unsubscribe record (including your email address or mobile phone number, or a hash of it) is kept permanently on the marketing refusal list; this is necessary to perform the obligation to stop marketing under Article 20(2) of the PDPA.
- After your account is closed, the Company keeps necessary data as pseudonymised matching values (such as a hashed email address) to prevent duplicate registration, maintain the security of the Services and for the purposes listed in item 1, until those purposes end. When you delete your personal search history yourself, the Company completes deletion under its operating procedures; backups and logs are handled under item 8.
- Exception (extended retention for investigations, disputes and legal proceedings): records relating to investigations of violations (including but not limited to automated extraction or crawling in breach of the Terms of Service, infringement of the Company's intellectual property or database rights, account takeover and fraud), dispute handling or administrative, judicial or other legal proceedings (including server log files, IP addresses, access records, and related account and transaction data) may be kept by the Company, notwithstanding the preceding items, until the investigation, dispute handling or legal proceedings end, for investigation, preservation of evidence and proof. This is a case of "necessity for the performance of duties or business" under the proviso to Article 11(3) of the PDPA. After the relevant proceedings end, the Company handles those records under the other items of this Chapter.
- Backups and logs: system backups, server log files and audit trails are kept according to the Company's technical cycles and information security needs, and are not immediately removed from backups when individual data is deleted; backups are used only for disaster recovery and security investigations and are overwritten or destroyed under operating procedures when they expire.
- Corporate changes: where a successor takes over the Services through a merger, acquisition, demerger or business transfer of the Company, the successor takes over the retention and use of the data described above within the purposes and scope set out in this Policy; any change of purpose by the successor is handled under Chapter 15.
11. Data Security
- The Company takes reasonable technical and organisational measures to protect your personal data, including but not limited to:
- Encryption of data in transit (HTTPS/TLS)
- Hashed storage of passwords
- SHA-256 hashing of matching data before upload to advertising platforms (Chapter 5)
- No plaintext name, email address or telephone number in server-side events or de-identified event data; restricted raw search records are additionally protected by access controls and by limiting access to a minimum of authorised personnel (Chapters 5 and 10)
- Access control
- Periodic security testing
- Credit card data is handled by third-party payment providers that meet the PCI-DSS security standard; the Company does not store full card numbers.
- Although the Company does its best to protect your data, no method of internet transmission is absolutely secure. The Company cannot guarantee the absolute security of data transmission.
- Notification of personal data incidents: if personal data is stolen, leaked, altered or otherwise compromised, the Company will, after becoming aware of the incident, notify you within the statutory time limit by email, text message, in-service notice or other appropriate means under Article 12 of the Personal Data Protection Act and related laws and regulations, including the facts of the incident and the measures the Company has taken in response; where the law requires a report to the competent authority, the Company will also report as required.
12. Cross-Border Transfers of Data
- The Company's servers and main data storage facilities are located in data centres of international cloud service providers selected by the Company; some data is also stored within the Republic of China (Taiwan) (including the Taiwan region of the Company's data warehouse, Google BigQuery).
- Because the Company uses third-party services, some of your data may be transferred outside Taiwan, to destinations including but not limited to:
- United States: Google LLC (Google Analytics 4, Firebase Analytics, Crashlytics, FCM, Google Ads, Customer Match), Meta Platforms, Inc. (Meta Pixel, Conversions API, Custom / Lookalike Audiences), Apple Inc. (APNs, in-app purchase), Twilio Inc. (OTP text messages), Cloudflare, Inc. (content delivery network and security protection), Mixpanel, Inc. (product usage analytics), Resend, Inc. (email delivery), Anthropic PBC and OpenAI, L.L.C. (processor-type AI model services under Chapter 6, item 1, applicable from the time the relevant features are brought within this Policy under Chapter 1, item 4)
- Singapore and the United States: TikTok Pte. Ltd. / ByteDance (TikTok Pixel, Events API; audience list upload when formally enabled)
- Location of external search service providers: if the web research feature is launched and an overseas provider is used, its name and location will be added to this list under Chapter 15 when the feature is launched; no transfer takes place before it is enabled
- Japan: LY Corporation (LINE official account customer service messages); cloud infrastructure and object storage of Akamai Technologies, Inc. (Linode) (the data centre where the Company's servers are located, and storage of de-identified event data)
- Other places where the Company's cloud infrastructure providers operate
- The Company will ensure that data recipients provide a level of protection comparable to the Personal Data Protection Act of the Republic of China, and binds their processing by service contracts and data processing agreements.
- Under Article 21 of the Personal Data Protection Act, if the central competent authority restricts international transfers to particular countries or regions, the Company will comply.
- Users outside Taiwan: the Company is a legal person of the Republic of China, and your personal data is collected, processed and used under the Personal Data Protection Act of the Republic of China. If you use the Services from outside Taiwan (including but not limited to Singapore, Japan and the European Union), you understand that your data will be transferred to Taiwan and to the places listed in this Chapter for processing; if the personal data protection law of your jurisdiction (such as Singapore's PDPA or the EU GDPR) gives you additional rights, you may contact the Company under Chapter 14, and the Company will handle your request to the extent that law actually applies to the Company.
13. Protection of Minors
- The Services are aimed mainly at adults. Under the Civil Code, minors under 18 should use the Services only with the consent of their legal representative.
- The Company does not accept registration by anyone under 7. If a minor aged 7 or over provides personal data without the consent of their legal representative, the Company will delete that data once it discovers this or is notified by the legal representative.
- If a legal representative finds that their minor child is using the Services without consent, please contact the Company immediately.
14. How to Exercise Your Rights
- Enquiry, review and copies: you can sign in to your account to view your personal data, or apply through the official LINE account to review it or obtain a copy. The Company will decide whether to grant the request within 15 days of receiving it; where necessary, this may be extended by 15 days, and you will be notified in writing of the reason for the extension.
- Supplementation or correction: you can correct your data yourself in your account settings, or apply for correction through the official LINE account. The Company will handle the request within 30 days of receiving it; where necessary, this may be extended by 30 days, and you will be notified in writing of the reason for the extension.
- Deletion and stopping collection, processing or use: you can apply to delete your account or to stop processing your personal data through your member settings, the in-app account deletion feature (lite iOS App) or the official LINE account; the time limit is the same as in the preceding item. However, data the Company is required by law to keep, and data necessary for the investigations, disputes or legal proceedings described in Chapter 10, item 7, are excluded.
- Marketing opt-out: handled under the opt-out table in Chapter 5, item 5.
- Fees: under Article 14 of the Personal Data Protection Act, the Company may charge the necessary costs for enquiries, requests to review personal data or requests for copies.
- Identity verification: to protect the security of your data, the Company may ask you to provide information sufficient to confirm your identity before handling the requests above; where your identity cannot be confirmed, the Company may refuse the request.
- Contact: please contact the Company through its official LINE account or the customer service channels of the Services.
- Handling principles: the Company handles your requests according to the conditions, exceptions and time limits set by applicable law (the time limits in items 1 to 3 of this Chapter are those set by Article 13 of the Personal Data Protection Act); for rights not conferred, or time limits not set, by law, the Company may handle requests at its discretion under its operating procedures and makes no additional commitment through this Policy.
15. Changes to this Privacy Policy
- The Company may revise this Privacy Policy at any time, and the revised version will be published on the Services' website and in each app.
- For material changes (such as changes to the purposes of collection, categories of data, recipients or manner of use), the Company will notify you before they take effect, by email, in-service notice or other prominent means.
- If, after being informed, you continue to use the Services and provide personal data, you are presumed under Article 7(3) of the PDPA to consent to the revised Privacy Policy; if you do not agree, please stop using the Services, and you may exercise your rights under Chapter 14. Where a revision involves use outside the specific purposes within the meaning of Article 20(1) of the PDPA, the Company obtains your consent as that Article requires.
- Where the Company adds or replaces a processor or an advertising and marketing partner of the same category and for the same use as those already disclosed in Chapter 6, this is not a material change under item 2; the Company updates and announces the lists in Chapters 6 and 12, and the change applies from the time of the announcement.
16. Contact
If you have any questions or suggestions about this Privacy Policy, or wish to exercise your rights relating to personal data, please contact us by the following means:
- Company name: Suodata Inc. (指數資訊股份有限公司)
- Official LINE: https://line.me/R/ti/p/@746cckjp (LINE ID @746cckjp)
- Official website: https://lawplayer.com
Additional disclosures
This section is not part of the translation. It gives additional and more specific information about the service providers, cookies and data practices of the Services, and applies together with Chapters 1 to 16.
1. Service providers: locations and Google advertising
Locations. In addition to the places listed in Chapter 12, item 2: Bunny.net (video streaming, Chapter 6, item 1) is operated by BunnyWay d.o.o. in Slovenia (European Union) and delivers video through its global network; the read-aloud providers in Chapter 6, item 1 are based in the United States (OpenAI, ElevenLabs, Google, Microsoft) and in mainland China (MiniMax), and receive only the text to be read aloud.
Google advertising. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to the Services and to other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to the Services and other sites on the internet. You can opt out of personalised advertising in Google Ads Settings and, for other participating vendors, at www.aboutads.info/choices. Google explains how it uses information from sites that use its services at policies.google.com/technologies/partner-sites.
2. Additional cookies and similar technologies
In addition to the table in Chapter 7, item 1, the Services use the following browser storage:
| Name | Purpose | Duration |
|---|---|---|
| lp_pidn (local storage; see Chapter 7, item 1) | Name of the on-site promotion you last clicked | Kept on your device until replaced or cleared |
| Session storage (first-party measurement) | A random identifier for the current browser session, used for first-party usage statistics when no lp_sid cookie is available | Browser session |
| Local storage (reading position) | Remembers where you stopped reading a document so that you can resume | Kept on your device; treated as expired after 90 days |
lp_pid, lp_pidn, lp_it, lp_app_entry, lp_live_shell, the reading position and the session-storage identifier hold a placement code, a flag, a test-group value, a reading position or a session value rather than the visitor identifier (lp_vid). They are used in all regions, including the consent regions, and do not depend on the choice described in Chapter 7, item 7; the same applies to lp_ref and lp_coupon (Chapter 7, item 1), which are written when you arrive through one of the Company's short links or coupon links. You can block or delete them in your browser settings.
First-party measurement. The Services send page and event measurements (such as the type of page, events and loading performance) to the Company's own servers, where they are recorded in server logs and handled under Chapter 10, item 4. In the consent regions, until you consent to analytics, these measurements are sent without the visitor identifier (lp_vid) and without Google identifiers.
Outside the consent regions. The consent banner, "Cookie settings" and the Global Privacy Control handling described in Chapter 7, items 6 and 7 apply to visitors connecting from the consent regions (the European Economic Area, the United Kingdom and Switzerland). Elsewhere, analytics and advertising technologies operate on a notice and opt-out basis: in addition to your browser settings (Chapter 7, item 5) and the channels in Chapter 5, items 3 and 5, you can use Google Ads Settings for personalised ads and the Google Analytics opt-out browser add-on.
EU/EEA and Switzerland Supplement
This Supplement applies to you if you are in the European Economic Area (the 27 EU Member States, Iceland, Liechtenstein and Norway; the "EEA"); item 15 applies if you are in Switzerland. We are established in Taiwan and have no establishment in the EEA; this Supplement applies to the extent that the GDPR (Regulation (EU) 2016/679) applies to our processing of your personal data under Article 3(2) GDPR. It forms part of the Privacy Policy, and where it differs from the main text above, this Supplement prevails for you. Nothing in this Privacy Policy displaces the mandatory provisions of the GDPR, of the ePrivacy Directive (Directive 2002/58/EC) or of the national laws implementing them that apply to you.
1. How the main text applies to you
- Legal bases, not presumed consent. The main text states that, once you have been informed and you provide your personal data (opening paragraphs) or continue to use the Services after a revision (Chapter 15, item 3), you are presumed to have consented under Article 7(3) of Taiwan's Personal Data Protection Act. That presumption operates under Taiwanese law. It is not our legal basis for you and is not relied on as consent under the GDPR. For you, each processing activity relies on the legal basis stated in the table in item 4 of this Supplement, and where that basis is consent, we ask for it separately and specifically.
- Purposes. The Taiwanese purpose codes in Chapter 2 describe our processing under Taiwanese law. For you, the purposes and legal bases are those in item 4.
- Retention. Chapter 10 applies to you subject to item 10 of this Supplement. The purpose-persistence rule in Chapter 10, item 1, including its exceptions for what is necessary for our business or covered by written consent, does not apply to you to the extent it conflicts with the storage limitation principle (Article 5(1)(e) GDPR) or your right to erasure (Article 17 GDPR).
- Your rights. Chapter 14 applies to you subject to item 11: the rights listed there are yours under the GDPR, we reply within the time limits in item 11, and fees are limited to those allowed by Article 12(5) and Article 15(3) GDPR. Chapter 14, item 8 does not limit those rights.
- International transfers. Chapter 12, item 3 is supplemented by item 9 of this Supplement.
- Children. Chapter 13 applies together with item 13.
2. Who is responsible for your data (controller)
The controller is Suodata Inc. (指數資訊股份有限公司), a company incorporated in Taiwan (Republic of China); its representative (代表人) is 莊東碩. Our registered address and company registration number are published in the company registry of Taiwan's Ministry of Economic Affairs under the name 指數資訊股份有限公司.
You can contact us about anything in this Privacy Policy, including requests to exercise your rights, through our official LINE account @746cckjp or the customer service channels of the Services (main text, Chapter 16). You may write to us in English.
Data protection officer. Our core activities do not consist of processing operations that require a data protection officer under Article 37 GDPR, and we have not designated one. Data protection enquiries are handled through the contact channels above.
3. Representative in the Union (Article 27 GDPR)
We are not established in the Union. Where Article 27 GDPR requires us to designate a representative in the Union, the representative's name and contact details will be published in this item once designated. No representative is listed at present; please contact us directly through the channels in item 2.
4. Purposes and legal bases
| What we do (main text reference) | Main data involved | Legal basis under Article 6(1) GDPR |
|---|---|---|
| Creating and running your account, providing the features you ask for, one account across our services, service and transactional messages, personal search history (Chapter 4, items 1 and 7; Chapter 5, item 7) | Identifiers, profile data you provide, usage data | (b) performance of a contract |
| Subscriptions, payments, refunds, course delivery and learning records, including giving partner instructors what they need to deliver a course you bought (Chapter 4, items 2 and 8; Chapter 6, item 2) | Identifiers, transaction data, learning progress | (b) performance of a contract |
| Customer service and complaints (Chapter 4, item 3) | Identifiers, messages | (b) performance of a contract; (f) legitimate interests where you are not a customer |
| Invoices, accounting and tax records required by the laws of Taiwan (Chapter 4, item 9) | Transaction data | (f) legitimate interests (complying with the statutory obligations to which we are subject in Taiwan); (b) performance of a contract |
| Security, fraud prevention, account protection, detecting and blocking automated extraction and other abuse, server logs, and routing connections through our content delivery and security provider (Chapter 4, item 4; Chapter 6, item 1) | IP address, device and browser data, logs, account data | (f) legitimate interests (network and information security and fraud prevention, Recitals 47 and 49 GDPR; protecting the Services and our database against unauthorised extraction) |
| Investigations, disputes, audits and legal proceedings (Chapter 10, item 7) | Logs, account and transaction data | (f) legitimate interests (establishing, exercising or defending legal claims) |
| Cookies and local storage that are strictly necessary for the Services you ask for, for security and for recording your consent choice: sign-in, security, the consent-region flag, your consent record and receipt, checkout storage (Chapter 7, item 1) | Cookie values | Exempt from consent under Article 5(3) of the ePrivacy Directive; (b) performance of a contract and (f) legitimate interests under the GDPR |
| Records proving your consent choices, objections and opt-outs (Chapter 7, item 7; Chapter 10, items 3, 4-2 and 5) | Consent ID, time, version, choices, country, device type; the contact detail on the marketing suppression list or its hash | (c) legal obligation (Articles 7(1) and 21(3) GDPR); (f) legitimate interests (being able to demonstrate your choice and to establish or defend legal claims) |
| First-party service statistics, page-layout tests and attribution of on-site promotions, recorded on our own servers (Chapter 4, item 5; Chapter 7, item 1; "Additional disclosures", item 2) | Pages viewed, events, session values, placement codes | (f) legitimate interests (understanding how the Services are used, keeping them working and improving them) |
| Product analytics about how signed-in members use features, sent from our servers to our processor Mixpanel (Chapter 4, item 5; Chapter 6, item 1) | Member identifier, usage events | (f) legitimate interests (understanding how members use the Services and improving them); you may object at any time |
| Personalised ranking and recommendations, and information and offers about our own services shown inside the Services (Chapter 4, items 7 and 10) | Member identifier, usage data, purchase history | (b) performance of a contract where it is a feature you ask for; otherwise (f) legitimate interests (personalising and promoting our own Services to our users); you may object at any time |
| Improving search, recommendation and AI-assisted features and developing new products and services, using de-identified, pseudonymised or aggregated data and, where the law permits, identifiable data, excluding other people's data in search strings (Chapter 3, item 2-1; Chapter 4, items 5 and 13) | Usage data, search records | (f) legitimate interests (improving the Services and developing new ones); your private notes and documents are not used for model training unless you separately give express consent |
| Long-term statistical and research use of pseudonymised event data and of aggregated statistics (Chapter 10, item 4) | Pseudonymised events, aggregates | (f) legitimate interests, with the safeguards of Article 89(1) GDPR; further processing for statistical purposes under Article 5(1)(b) GDPR |
| Restricted raw search records (Chapter 10, item 4; item 10 of this Supplement) | Search strings, which may include other people's names, and the session or member identifiers recorded with them | (f) legitimate interests, limited to the purposes listed in Chapter 10, item 4 (audit and integrity of service records; reconciliation of accounts, performance and attribution; detecting and investigating automated extraction, abuse, fraud and security incidents; disputes and evidence; producing de-identified data); (c) legal obligation where they are used to handle and verify requests under Articles 15 to 22 GDPR. They are not used for marketing or advertising audiences, nor to identify, compile files on or contact the persons searched for |
| Cookieless signals sent by Google's tags before you make a choice, in the Consent Mode "denied" state (Chapter 7, item 6) | Page address, time and the information a browser ordinarily sends when connecting, including the IP address | (f) legitimate interests (aggregate measurement without cookies or device identifiers) |
| Analytics cookies and similar technologies (Google Analytics 4), the first-party visitor identifier lp_vid and the session identifier lp_sid (Chapter 7) | Cookie identifiers, usage data | (a) consent, under Article 5(3) of the ePrivacy Directive and Article 6(1)(a) GDPR |
| Advertising cookies and pixels (Google Ads, Meta, TikTok), remarketing, attribution cookies (lp_attr, __lp_click, __lp_first_touch), identity mapping records, server-side event reporting to GA4, Meta and TikTok, and linking ad clicks to orders (Chapter 4, item 12; Chapter 5, item 2(6), (7) and (9); Chapter 7, items 3 and 6) | Cookie and click identifiers, pseudonymous identifiers, hashed contact data, order data | (a) consent |
| Google AdSense advertising, where ad requests are enabled for the EEA (Chapter 6, item 1-1; Chapter 7, item 1; item 5 of this Supplement) | IP address, browser information, page address, Google cookies | (a) consent; Google is an independent controller |
| Uploading hashed email addresses or phone numbers to advertising platforms for custom and lookalike audiences (Chapter 5, item 2(5)) | Hashed email, hashed phone, hashed pseudonymous identifier | (a) consent |
| Marketing emails about our own similar products and services to existing customers, that is, people whose email address we obtained in the context of the sale of a product or service (Chapter 5, item 2(1)) | Email address, purchase history | (f) legitimate interests (direct marketing, Recital 47 GDPR), under the existing-customer rule of Article 13(2) of the ePrivacy Directive as implemented in your country; you can object when we collect your address and in every message |
| All other marketing by email, text message, push notification or LINE, and sharing your contact details with joint marketing partners (Chapter 5, item 2(1) to (4) and (8)) | Contact details, preferences | (a) consent |
| User research (Chapter 4, item 11) | Feedback, recordings | (a) consent |
| Publishing your community posts (Chapter 8, item 1) | Post content, nickname | (b) performance of a contract |
| Embedded video players for the videos you open: Bunny.net, and YouTube on some pages (Chapter 6, items 1 and 1-1; item 5 of this Supplement) | IP address, browser information | (b) performance of a contract or (f) legitimate interests (delivering the video you choose to watch); YouTube (Google) is an independent controller for the data it collects |
| Including public government data in the Services (legislation, court decisions, administrative interpretations, company registry records and judicial personnel information), which may contain personal data of people who are not users (Chapter 2, item 3; Chapter 8, item 1) | Names and other details as published by the official source | To the extent the GDPR applies to this processing: (f) legitimate interests (making public legal and registry information accessible and searchable; freedom of expression and information, Articles 85 and 86 GDPR); requests for redaction, correction or objection are handled under Chapter 8, item 1 and item 11 |
| Anti-piracy identifiers embedded in purchased content (Chapter 8, item 2) | Account identifier | (f) legitimate interests (protecting our content against unauthorised copying) |
| Handling your data protection requests and verifying your identity; notifying you and authorities of personal data breaches (Chapter 11, item 4; Chapter 14) | Contact details, request and incident data | (c) legal obligation (Articles 12 to 22, 33 and 34 GDPR) |
| Mergers, acquisitions, demergers and business transfers, and joint use with our affiliates within the purposes of this Policy (Chapter 6, item 4) | Data held for the Services | (f) legitimate interests (carrying out the transaction, continuing the Services and group administration) |
Our legitimate interests. Where we rely on legitimate interests, the interests are: keeping the Services, our network and our users secure; preventing fraud, account takeover, abuse and unauthorised automated extraction of our content and database; compiling service statistics and understanding how the Services are used; improving the Services and developing new products and services; personalising the Services and showing our users information about our own services inside the Services; marketing our own similar products and services to existing customers by email; keeping records of consent, objections and transactions and carrying out internal audit and reconciliation; protecting our intellectual property; establishing, exercising or defending legal claims; complying with the laws of Taiwan that apply to us; making public legal and registry information accessible and searchable; and carrying out corporate transactions and group administration. We have weighed these interests against your interests, rights and freedoms, taking into account what you can reasonably expect, the use of pseudonymisation and aggregation, access restrictions and your right to object. You can ask us for more information about this balancing through the contact channels in item 2.
Right to object. You can object at any time, on grounds relating to your particular situation, to processing based on legitimate interests (Article 21(1) GDPR). You can object at any time and without giving reasons to the use of your data for direct marketing, including profiling related to it (Article 21(2) and (3) GDPR); we will then stop.
5. Consent in the EEA
- Google Analytics and advertising technologies only after you consent. Until you consent, we do not set Google Analytics, Google Ads, Meta or TikTok cookies, do not load the Meta or TikTok pixels, do not set the first-party visitor identifier lp_vid, the session identifier lp_sid or the attribution cookies lp_attr, __lp_click and __lp_first_touch, do not report events to Google Analytics 4, Meta or TikTok (including the server-side reports described in Chapter 7, item 3), do not link ad clicks to your orders and do not include you in any advertising audience (main text, Chapter 7, item 6). Product analytics for signed-in members and our own first-party statistics rest on the legal bases in item 4.
- A clear choice. The banner offers "Accept all", "Necessary only" and "Settings" with equal size and weight. In "Settings" you choose analytics and marketing separately. Closing the banner counts as "Necessary only"; scrolling or continuing to browse is never consent; a Global Privacy Control signal counts as refusal until you choose otherwise (main text, Chapter 7, item 7).
- Change your mind at any time. Use "Cookie settings" in the footer. Withdrawing is as easy as consenting, and does not affect the lawfulness of processing before withdrawal (Article 7(3) GDPR).
- Marketing consent is separate. For you, creating an account or accepting the Terms of Service is not relied on as consent to marketing messages or to audience matching. Where we ask for that consent, you can refuse it and still use the Services.
- Google tags before consent. Before consent, Google's tags run in the Consent Mode "denied" state described in the main text, Chapter 7, item 6: they do not read or write cookies and send only cookieless connection signals.
- First-party items that do not depend on your choice. The following first-party items are used whatever you choose: lp_pid (30 days; records the on-site promotion you last clicked, so that a resulting order can be attributed to that placement; written when you click an on-site promotion); lp_app_entry (1 day; written only when you arrive through an app entry link); lp_live_shell (30 days; keeps you in the same page-layout test group on live-session pages); lp_it (180 days; written only on devices opened with our internal testing parameter); lp_ref and lp_coupon (up to 30 days; written when you arrive through one of our short links or coupon links, so that the coupon can be applied and the order attributed); the reading position kept in your browser's local storage; and a random identifier kept in session storage for the current browser session, with which our own servers count page views and events without the visitor identifier lp_vid and without Google identifiers. These items hold a placement, link or coupon code, a flag, a test-group value, a reading position or a session value, not the visitor identifier (main text, Chapter 7, item 1; "Additional disclosures", item 2). You can refuse them by blocking or deleting cookies and site data for the Services in your browser settings.
- Embedded videos. Some pages embed videos delivered by Bunny.net or by YouTube (Google) (main text, Chapter 6, items 1 and 1-1). When a YouTube player loads, Google receives your IP address and browser information and may set its own cookies; you can prevent those cookies by blocking third-party cookies in your browser settings.
- Google AdSense. Google AdSense advertising is shown on some pages of the Services (main text, Chapter 6, item 1-1 and Chapter 7, item 1; Google's advertising disclosures and opt-out links are in "Additional disclosures", item 1). By default, the Services do not send ad requests to Google AdSense for visitors connecting from the EEA, the United Kingdom or Switzerland.
- Proof. Each choice receives a consent ID, and we keep a record of your choice without your IP address (main text, Chapter 7, item 7), so that both you and we can show what you chose.
6. Recipients
We share personal data with the following recipients or categories of recipients, to the extent described in Chapter 6 of the main text (their locations are given in Chapter 12 and in "Additional disclosures", item 1):
| Category | Role | Examples |
|---|---|---|
| Hosting, cloud infrastructure, cloud storage, data warehousing | Processor | Akamai Technologies (Linode), Google Cloud (BigQuery) |
| Content delivery and security | Processor | Cloudflare |
| Payment, invoicing | Processor or independent controller under their own legal duties | TapPay, NewebPay, AFTEE, LINE Pay, Apple, ezPay |
| Email, text message and push delivery | Processor | Resend, every8d, Twilio, Apple APNs, Google FCM |
| Customer service messaging | Independent controller for its own platform | LY Corporation (LINE) |
| Analytics and product analytics providers | Processor | Google Analytics 4 (only after your consent), Firebase, Mixpanel |
| Video hosting and streaming (course videos) | Processor; YouTube as independent controller | Bunny.net (EU), YouTube |
| Speech synthesis (read-aloud) and AI model providers | Processor | OpenAI, ElevenLabs, Google, MiniMax, Microsoft, Anthropic; these receive the text or content to be processed |
| Advertising and marketing partners (advertising technologies only after your consent) | Joint or independent controller | Google (Google Ads, Customer Match, remarketing lists exported from GA4 audiences, AdSense), Meta, TikTok; the current list is in Chapter 6, item 1-1 |
| Partner instructors, content providers, joint marketing partners | Independent controller within the limits in Chapter 6, item 2 | Named on the relevant course, product or event page |
| Successors in a corporate transaction, and our affiliates | Controller | Chapter 6, item 4 |
| Courts, authorities and parties to legal proceedings where legally required or necessary for legal claims | Independent controller | Chapter 6, item 3 |
Advertising and marketing partners. This category is defined in Chapter 2, item 6 of the main text, and the current list is in Chapter 6, item 1-1. We may add partners of the same category and for the same use and announce them under Chapter 15, item 4. For you, where a new partner would receive your data on the basis of your consent, your earlier choice lapses and we ask you again before that partner receives it (main text, Chapter 7, item 7).
Advertising platforms as controllers. When their cookies or pixels run on the Services after your consent, Meta, Google and TikTok may collect data directly from your browser. For that collection and its transmission to them, we and the platform may be joint controllers (Court of Justice of the EU, Case C-40/17, Fashion ID): we are responsible for giving you this information and for asking for your consent on the Services, and you may exercise your rights against the platform or against us. Each platform is solely responsible for what it does with the data afterwards, under its own privacy policy: Meta, Google, TikTok.
7. Where your data comes from
Most data comes from you or from your device. We also receive data from: the sign-in provider you choose (Google, Facebook, LINE, Apple: name, email address, social identifier); payment providers (transaction results); advertising platforms (aggregated performance statistics and the click identifiers they attach to links); for learners who bought courses on a third-party course platform we used before, the purchase records and contact details transferred to us when we migrated (Chapter 3, item 3); and, for the public government data included in the Services, the official publications of the authorities concerned (publicly accessible sources).
8. Is providing data required?
The sign-in and contact details marked as required on the registration page (such as your mobile number) are needed to create an account, and payment and invoice data are needed to buy a paid product (invoice details are also required by the tax laws of Taiwan); without them we cannot enter into or perform that contract. Fields marked optional, interest tags and all consent-based data are voluntary, and not providing them has no consequence other than less personalisation.
9. International transfers
- Taiwan. We are based in Taiwan, and the European Commission has not adopted an adequacy decision for Taiwan. When you give data to us directly, for example by using the Services, the GDPR applies to our processing directly (Article 3(2) GDPR, where applicable); the European Data Protection Board considers that data disclosed directly by a data subject to a controller outside the EEA is not a "transfer" within Chapter V GDPR (EDPB Guidelines 05/2021, version 2.0). Your data is processed in Taiwan and in the places listed in Chapter 12 under Taiwan's Personal Data Protection Act and this Policy.
- Onward disclosures to our service providers and partners outside the EEA rely on an adequacy decision (Article 45 GDPR) or on appropriate safeguards (Article 46 GDPR):
- United States: for recipients certified under the EU-U.S. Data Privacy Framework, the Commission's adequacy decision (Implementing Decision (EU) 2023/1795); otherwise the Commission's standard contractual clauses (Implementing Decision (EU) 2021/914), Module 2 (controller to processor) for processors and Module 1 (controller to controller) for independent controllers.
- Japan: the Commission's adequacy decision for Japan (Implementing Decision (EU) 2019/419) for recipients covered by it; otherwise the standard contractual clauses.
- Singapore and other countries without an adequacy decision: the standard contractual clauses.
- Mainland China: one speech synthesis provider (MiniMax) receives only the text to be read aloud, such as legislation text, and no account data.
- Recipients located in the EEA (for example, our course video streaming provider Bunny.net) do not require a transfer mechanism.
- Copies. You can obtain a copy of the relevant safeguards (commercial terms may be redacted) by contacting us under item 2.
- Derogations. In individual cases we rely on Article 49(1)(b) GDPR (a transfer necessary to perform a contract with you or to take steps you ask for, for example a payment or invoice you ask us to process through our payment and invoicing providers in Taiwan, or a verification code you ask us to send), on Article 49(1)(a) GDPR (your explicit consent) or on Article 49(1)(e) GDPR (legal claims).
10. How long we keep your data
We keep personal data in a form that identifies you only for as long as necessary for the purposes for which it is processed (Article 5(1)(e) GDPR). The criteria are:
| Data | How long |
|---|---|
| Account data | While your account exists; after closure, for as long as necessary for the purposes that then remain (refunds, disputes, fraud and account-takeover complaints, audit and legal claims; as a rule, the limitation periods that apply to such claims), together with the pseudonymised matching values described in Chapter 10, item 6 (preventing duplicate registration and abuse) |
| Transaction records and invoices | For the periods required by Taiwan's Business Entity Accounting Act and tax laws, and for as long as needed for audit, a dispute or a legal claim |
| Consent records | For as long as we need to be able to demonstrate your choice (Article 7(1) GDPR) and to defend related claims: 24 months for the record of each cookie choice, extended where a dispute or legal proceedings are involved (Chapter 7, item 7; Chapter 10, item 7); for records of marketing consent and opt-out, while the consent is relied on and for the limitation period thereafter (Chapter 10, items 3 and 4-2) |
| Cookies and browser storage | As stated in the table in Chapter 7, item 1 and in "Additional disclosures", item 2 |
| Raw records in our operational systems: search strings with session or member identifiers, and access records (Chapter 10, item 4) | Currently 90 days, after which they are deleted from those systems |
| Restricted raw search records (Chapter 10, item 4) | For as long as each of the purposes listed in Chapter 10, item 4 continues to exist; we review at least once a year whether each purpose still exists, and delete or de-identify the records once it has ceased. On your request we delete or de-identify the records that can be linked to your member identifier, subject to Chapter 10, item 7. Access is restricted, and your rights to object and to erasure (item 11) apply |
| De-identified (pseudonymised) event data in our data warehouse (Chapter 10, item 4) | Kept long term for statistical and research purposes with the safeguards of Article 89(1) GDPR (pseudonymisation, no direct identifiers, access control), for as long as it remains useful for those purposes (Article 5(1)(e) GDPR) |
| Aggregated or anonymised statistics | Without time limit (no longer personal data) |
| Marketing suppression list | For as long as needed to make sure we do not market to you again after you object or unsubscribe |
| Identity mapping records | Until you withdraw your consent, object or close your account; they are then marked as revoked and no longer used for marketing, and are deleted or de-identified under Chapter 10, item 4-2. Attribution records of completed orders are kept with the transaction records (Chapter 4, item 12) |
| Data on advertising platforms | Under each platform's own retention rules; audiences we set up expire according to the platform's settings |
| Data needed for an investigation, dispute or legal proceeding | Until it ends (Chapter 10, item 7) |
| Backups and logs | Overwritten on our technical backup cycle (Chapter 10, item 8) |
11. Your rights
You have the right to: access your personal data and receive a copy (Article 15 GDPR); have it rectified (Article 16); have it erased (Article 17); restrict its processing (Article 18); receive the data you gave us in a portable format and have it transmitted to another controller where processing is based on consent or contract and carried out by automated means (Article 20); object to processing based on legitimate interests and, at any time, to direct marketing (Article 21; see item 4); and withdraw any consent at any time, without affecting the lawfulness of earlier processing (Article 7(3)). Cookie consent can be withdrawn through "Cookie settings" in the footer; marketing can be stopped through the channels in Chapter 5, item 5.
We respond without undue delay and within one month of receiving your request. We may extend this by two further months where necessary, taking into account the complexity and number of requests, and we will tell you why within the first month (Article 12(3) GDPR). Requests are free of charge; where a request is manifestly unfounded or excessive, in particular because it is repetitive, we may charge a reasonable fee or refuse to act on it (Article 12(5) GDPR), and we may charge a reasonable fee for further copies (Article 15(3) GDPR). We may ask for information to confirm your identity where we have reasonable doubts (Article 12(6) GDPR). These rights apply under the conditions and with the exceptions set by the GDPR, for example where we need the data to establish, exercise or defend legal claims (Articles 17(3)(e), 18(2) and 21(1) GDPR) or where an access request would adversely affect the rights and freedoms of others (Article 15(4) GDPR).
12. Complaints
You have the right to lodge a complaint with a supervisory authority, in particular in the EEA Member State of your habitual residence, place of work or place of the alleged infringement (Article 77 GDPR), and to seek a judicial remedy (Articles 78 and 79 GDPR). A list of EEA supervisory authorities is published by the European Data Protection Board. In Germany, the competent authority is generally the data protection authority of your federal state (Land); in France, it is the CNIL. We would appreciate the chance to deal with your concern first (item 2).
13. Children
Where we rely on consent for information society services offered directly to a child, the child must be at least 16, or the lower age set by the law of their Member State (not below 13), for example 15 in France; below that age, consent must be given or authorised by the holder of parental responsibility (Article 8 GDPR). We do not include users known to be under 18 in advertising audiences and do not show them personalised advertising (main text, Chapter 5, item 6).
14. Automated decisions, breaches and changes
- Automated decisions. We do not make decisions based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you (Article 22 GDPR). Where automated processing contributes to account restrictions, refusals of transactions or abuse decisions, you can ask for human review (main text, Chapter 4, item 10). Profiling for personalised advertising takes place only with your consent.
- Personal data breaches. We notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to your rights and freedoms (Article 33 GDPR), and we inform you without undue delay where the breach is likely to result in a high risk (Article 34 GDPR).
- Changes. We will tell you about material changes before they take effect (main text, Chapter 15). Where a change requires your consent, we will ask for it; for you, we do not treat continued use as consent and do not rely on the presumption in Chapter 15, item 3.
15. Switzerland
Switzerland is not part of the EEA. If you are in Switzerland, this item applies, and items 1 to 14 apply by analogy to anything this item does not address, with the corresponding provisions of Swiss law in place of the GDPR.
- Law and authority. The Federal Act on Data Protection (FADP, in force since 1 September 2023) and its Data Protection Ordinance, Article 45c of the Telecommunications Act (information on, and the right to refuse, the storage of or access to data on your device) and Article 3(1)(o) of the Unfair Competition Act (mass electronic advertising). The supervisory authority is the Federal Data Protection and Information Commissioner (FDPIC).
- Basis for processing. The FADP does not require a legal basis for every processing activity; we nevertheless follow the table in item 4, and where we ask for consent it is specific, informed and can be withdrawn.
- Cookies and pixels. We apply the same consent mechanism to Switzerland as to the EEA: no analytics or marketing cookies, no advertising pixels and no server-side marketing events before you consent (main text, Chapter 7, items 6 and 7; item 5 of this Supplement).
- Marketing. Marketing emails require your prior consent, except to existing customers for our own similar products or services; every message identifies us and contains a free opt-out.
- Your rights. Access (Article 25 FADP; normally answered free of charge within 30 days), delivery or transfer of data (Article 28), rectification, erasure, restriction and objection (Article 32), withdrawal of consent, and information about and the right to state your view on automated individual decisions (Article 21; we do not make such decisions). Use the contact channels in item 2.
- Transfers. Taiwan is not on the Federal Council's list of countries with adequate protection. Onward disclosures rely on standard contractual clauses recognised by the FDPIC (including the EU standard contractual clauses as adapted for Switzerland) under Article 16(2) FADP, and, for certified US recipients, on the Swiss-U.S. Data Privacy Framework.
- Representative. Where Article 14 FADP requires us to designate a representative in Switzerland, the details will be published here once designated; no representative is listed at present.
- Breaches. We report data security breaches likely to result in a high risk to your personality or fundamental rights to the FDPIC as soon as possible, and inform you where necessary for your protection or where the FDPIC requires it (Article 24 FADP).
- Retention. We destroy or anonymise personal data once it is no longer needed for the purposes of processing (Article 6(4) FADP), applying the criteria in item 10.
- Complaints. You may contact the FDPIC.