privacy-policy

song-po隱私權

SONG-PO非常重視用戶的隱私權,因此制訂了隱私權保護政策,請您詳閱以下內容。

 

若您未滿二十歲,應請您的家長(或監護人)協同閱讀、瞭解並同意本政策之所有內容,當您繼續使用本網站服務時,即推定您的家長(或監護人)已閱讀、瞭解並同意接受本政策之所有內容,並遵守全部適用的法律與規定。


一、隱私權內容

 

  • 隱私權保護政策內容包括本網站如何處理由用戶使用網站服務時所收集到的身份識別資料,也包括本網站如何處理在商業伙伴與本網站合作時分享的任何身份識別資料。
  • 隱私權保護政策並不適用於SONG-PO以外的公司、非SONG-PO所僱用或管理的人員。
  • 當您註冊帳號、使用本網站的產品或服務、瀏覽本網站網頁、參加活動或贈獎時,SONG-PO會收集您的個人識別資料,為保障您的隱私及安全,您的帳號資料會用密碼保護。
  • SONG-PO會自動接收並紀錄您瀏覽器上的伺服器數值(包括IP Address、第三方的廣告性Cookies中的資料及您要求取用的網頁紀錄)。
  • 您有隨時修改帳號資料的權力,其中包括接受SONG-PO通知您特別活動或新產品的決定權。

 

二、您的資料本網站將會作為以下用途使用:

  • 改善及提升SONG-PO產品及服務。
  • 改進為您提供的廣告及網頁內容。
  • 完成創建會員及提供會員相關服務。
  • 完成您對某項產品的要求及通知特別活動或新產品。
  • 個人化行銷,如透過第三方的廣告性Cookies,提供符合您個人偏好的行銷與廣告內容、根據您過往使用京盛宇產品及服務的模式來推薦適合您的服務內容。
  • 任何其他取得您同意的目的。

三、個人資料的蒐集、處理及利用方式
  • 當您造訪本網站或使用本網站所提提供之功能服務時,我們將是該服務功能性質,請您提供必要的個人資料,並在該特定目的範圍內處理及利用您的個人資料;非經您書面同意,本網站不會將個人資料用於其他用途
  • 本網站在您使用服務信箱、問卷調查等互動性功能時,會保留您提供的姓名、電子郵件地址、聯絡方式及使用時間等
  • 於一般瀏覽時,伺服器會自行記錄相關行徑,包括您使用連線設備的IP位址、使用時間、使用的柳覽器、瀏覽及點選資料紀錄等,做為我們增進網站服務的參考依據,此紀錄為內部應用,決不對外公怖
  • 為提供精確的服務,我們會將收集的問券調查內容進行統計與分析,分析結果之統計數據或說明文字呈現,除供內部研究外,我們會是需要公布統計數據及說明文字,但不涉及特定個人之資料

 

四、不會向任何人出售或出借您的個人識別資料,僅在以下的情況,SONG-PO會向政府機關、合作夥伴或公司提供您的個人識別資料:

 

  • 需要與合作夥伴或公司共用您的資料,才能夠提供您要求的產品或服務時(若未經事先通知,這些公司均無權使用本網站所提供的個人資料,作為提供產品或服務以外的其他用途)。
  • 依照法令規定或政府機關的正式函文要求。
  • 當您在網站上的行為已造成侵權或違反條款時,我方有權提供相關資料及證明文件給檢調單位以協助調查。
  • 為了保護使用者個人隱私,我們無法為您查詢其他使用者的帳號資料,若您有法律相關問題需查閱他人資料時,請務必向警政單位提出告訴,我們將全力配合相關單位調查並提供所需資料以協助調查。  

 

五、管理個人資料

  • 若您對於您所提供的個人資料有以下情況,您可以透過網站訊息功能或 Email 至 hello@fellowproducts.com.tw 與我們聯繫:
    • 無法自行更新但希望進行更新。
    • 拒絕我們使用您部份或全部的個人資料(例如:您認為我們可能不當地蒐集或使用您的個人資料)。
    • 限制我們使用您個人資料的用途(例如:不希望我們將您的個人資料作為分析使用)。
    • 若您一開始同意SONG-PO向您蒐集個人資料,但之後希望撤銷此同意,您亦可隨時與我們聯繫,或向我們提出撤銷同意的請求,我們將不會繼續蒐集您的個人資料,只會保留撤銷申請之前所蒐集的資訊。

 

  • 基於法律或保護之目的,一直以來SONG-PO皆致力於維持您個人資料的正確性,亦保護您的個人資料免於任何意外或惡意的破壞,然而當有以下任一情形發生時,我們將無法保證能滿足您提出的上述管理個人資料之需求:
    • 於法律允許範圍內可保留之情形。
    • 基於正當服務提供目的需保留。
    • 需要超過合理範圍內過多資源使用、技術支援付出,例如僅得以新系統之開發建置或改變現行服務提供模式始得完成的需求。
    • 有危害他人隱私權之風險。

 

六、資料之查閱予刪除 

  • 會員能隨時在網站的會員帳號查看授權的姓名與電郵資料,並且僅作為商店會員、訂單資料的內容。
  • 商店依照本人請求,使用者可透過商店右上角聯絡我們管道提出刪除、停止使用該個人資料的要求。
  • 相關需求可來信至:hello@fellowproducts.com.tw

本政策變更:SONG-PO有權並保留修訂本政策之權利,當我們在規定上作出大幅修改時,會在網站明顯之處張貼修訂條例與影響之告示。


LINE USER DATA POLICY


Those persons (“Developers”) using the LINE Software Development Kit and Application Programming Interface (“the Platform”) must comply with matters prescribed in this policy when they handle information relating to the users of LINE-affiliated services (“LINE Services”) provided by LINE Corporation (“the Company”).

 

 

1. LINE User Information

“LINE User Information” refers specifically to the following information related to users of LINE Services.

1.1 User-related information the Company, under users’ consent, provides to Developers (including but not limited to LINE profile name, icon image, Company internal identifiers for identifying users and status messages).

1.2 Information Developers directly receive from users from within LINE Services (including but not limited to messages from users sent to a Developer’s Official Account).

Any information Developers directly receive from users within their own services is not LINE User Information, even in instances where they have integrated a LINE Login feature to their service.

 

2. General Privacy Principles related to Services Using the Platform (“Relevant Services”)

2.1 Developers must abide by laws and regulations related to personal information and privacy.

2.2 Developers must create privacy policies for Relevant Services.

2.3 Developers must conduct development and operation of the Relevant Services with consideration for privacy and in accordance with the privacy principles below.

2.3.1 Developers must notify users of the personal information that will be collected, and seek users’ consent to collect, use, or disclose users’ personal information.

2.3.2 Developers must identify the purposes of use for collecting users’ personal information.

2.3.3 Developers must collect only information that is necessary to carry out the identified purposes of use.

2.3.4 Developers must use and disclose users’ personal information only for the purposes for which it is collected, except with users’ consent or as required or permitted by law. Developers must keep users’ information only as long as necessary to fulfill those purposes.

2.3.5 Developers must endeavor to make sure that users’ personal information is accurate, complete, and up-to-date.

2.3.6 Developers must protect users’ personal information by appropriate security safeguards.

2.3.7 Developers must make the policies and practices for the handling of users’ personal information as transparent as possible.

2.3.8 Developers must allow users to access their own personal information and correct their personal information as appropriate.

2.3.9 Developers will be accountable to users. Developers must always be receptive to hearing users’ opinions regarding Developers’ compliance with these principles, privacy policies, and applicable laws. Developers must always exert their best efforts to fulfill their accountability to users. Users will be able to express their opinions regarding the compliance with these principles and the privacy policies at any time.

2.4 Developers shall disclose and ensure that Relevant Service-related privacy policies are easily viewable to anyone at any time (including before and after a user starts to use the Relevant Service).

 

3. Protection of LINE User Information

3.1 Developers must properly protect LINE User Information against unauthorized access and use. Developers should enact the best possible measures for information protection, with potential measures including the implementation of security training, the signing of non-disclosure agreements between the employees and the company, the establishment of rules for the handling of confidential and personal information, the implementation of internal audits and third-party audits, the establishment of incident response procedures, the implementation of monitoring for unauthorized access, and physical access control.

3.2 Developers must collect, maintain and use LINE User Information in line with the following:

3.2.1 Developers shall only be able to collect, maintain and use LINE User Information necessary for providing Relevant Services.

3.2.2 Developers must obtain LINE User Information in a fair and legal manner.

3.2.3 When storing any LINE User Information other than Company internal user identifiers for more than 24 hours, Developers must notify users that LINE User Information will be stored by Relevant Services. However, regardless of whether or not users have been notified, Friend and Group information must not be stored for more than 24 hours.

3.2.4 LINE User Information collected for the provision of Relevant Services must not be used for any other purposes.

3.2.5 When using the Platform for various services, LINE User Information obtained from various services must not be linked together. However, this does not apply when approved by the Company.

3.2.6 LINE User Information must not be purchased or sold.

3.2.7 Developers must not obtain or request to provide users’ LINE account passwords.

3.2.8 Friend information and Group information can only been used while users are using the Relevant Services.

3.2.9  The audience of LINE User Information must be equivalent to that within the Company’s services (for example, a user’s Friend information/Group information may only be viewable to the user him/herself) or must be even more restricted.

3.2.10 When linking a Relevant Service account and a LINE account (“LINE Link”), Developers must provide a feature to unlink from LINE and a feature to withdraw from the Relevant Service.

3.2.11 When using contact information included in LINE User Information (phone number, email address, home address, etc.) to contact a user, Developers must first receive the approval of the individual. They must also comply with applicable laws and guidelines related to spamming.

3.3 When using proxy sending features (features for sending messages in place of a user using that user's account) and proxy posting features (features for posting to Timeline as a user using that user's account), Developers must not send/post anything against the volition of users. Specifically Developers must comply with the following:

3.3.1 Clearly indicate to the user the following every time before sending or posting by proxy.

3.3.1.1 The fact that the message will be sent or Timeline post will be made by proxy via the user's account

3.3.1.2 The content to be sent or posted by proxy

3.3.1.3 The recipient(s) of the message sent by proxy, or the reach of the post made by proxy

3.3.2 To not perform sending or posting by proxy unless users explicitly indicate their desire for the content indicated in 3.3.1 to be sent or posted by proxy.

3.3.3 To promptly perform the sending or posting by proxy when users explicitly indicate their wishes in accordance with 3.3.2.

3.4 LINE User Information must not be disclosed to third parties except in the following cases:

3.4.1 When required under laws and regulations.

3.4.2 When disclosing to contractors to the extent necessary for contracted work.

When disclosing to contractors, said contractors must also comply with obligations imposed on Developers by the Company. In instances where violations or other issues arise involving a contractor, the Developer shall bear responsibility.

3.5 Developers must delete LINE User Information in line with the following. Anonymized statistical data created based on LINE User Information shall not be subject to deletion.

3.5.1 When terminating Platform usage, Developers must immediately delete Company internal identifiers for identifying users and any other User Information excluding that which users have been informed will be stored for more than 24 hours. However, continued storing is possible in instances where an obligation for storing information has been provided by laws or regulations or a separate agreement with the Company.

3.5.2 After a Relevant Service is closed, or a user withdraws from the Relevant Service, all LINE User Information including Company internal identifiers for identifying users must be deleted, except:

3.5.2.1 When the deletion of such information causes violation of laws or ordinances; or

3.5.2.2 In limited instances when, in the presence of LINE user’s consent, storing temporarily after a Relevant Service is closed or a user withdraws from the Relevant Service for legitimate purposes such as handling inquiries.

3.5.3 Developers must comply when users make a request for disclosure, correction, deletion or the suspension of use of LINE User Information obtained by Developers. However, this shall not apply in instances when such compliance causes violation of laws or regulations.

3.5.4 Developers must comply when requested by the Company to submit a proof of disposal of LINE User Information.

 

4. Other Important Matters

4.1 Developers must keep security in mind when conducting system development and operation.

4.2 Developers must comply with industry standards and meet all METI System Management Standards or equivalent standards.

4.3 Developers must allow the Company to audit Relevant Services in order to confirm service safety and that there are no violations.

4.4 Developers must quickly respond when receiving requests from the Company for Relevant Service improvement. If a request cannot be accommodated, said reason must be reported.

4.5 In instances where a security incident related to LINE User Information, such as the leakage of personal information, arises, Developers must promptly notify the Company of the incident, implement necessary investigations, responses and prevention measures and report on the results.

4.6 The Company may on occasion change this policy. Developers must recognize that they will be deemed to have accepted the changes when they continue to use the Platform.

4.7 The Company may stop providing the Platform to Developers in the following cases:

4.7.1 when they have violated this policy

4.7.2 when they have not followed the Company's instruction for improvement

4.7.3 when they have performed any action that the Company otherwise deems inappropriate


Latest revision: November 1, 2017