HEY YO PIZZA為『田田永穗企業有限公司』所經營（以下稱「本公司」），本公司十分重視您的隱私權保護，將依個人資料保護法及本隱私權政策蒐集、處理及利用您的個人資料，並提供您對個人資料權利之行使與保護，在未經消費者同意下，我們絕不會將您的個人資料提供予任何與本公司服務無關之第三人。
 
1. 本隱私權政策適用之範圍
請您在於使用本網站服務前，確認您已審閱並同意本隱私權政策所列全部條款，若您不同意全部或部分者，則請勿使用本網站服務。
本隱私權政策僅適用於本網站對您個人資料所為蒐集、處理與利用，不及於其他非本公司所有或控制之其他公司或個人。您可能經由本網站連結至第三人所經營之網站，各該網站所為之個人資料蒐集係依其網站之隱私權政策規定處理，與本公司無涉。
2. 個人資料保護法應告知事項
(1)蒐集機關名稱：田田永穗企業有限公司。(2)蒐集目的：提供本公司相關服務、行銷、契約、類似契約或其他法律關係事務、消費者、客戶管理與服務、網路購物及其他電子商務服務、廣告和商業行為管理業務、其他經營合於營業登記項目或組織章程所定之業務。(3)個人資料類別：識別類（姓名、地址、聯絡電話、電子郵件信箱）、特徵類（年齡、性別、出生年月日等）、社會情況類（興趣、休閒、生活格調、消費模式等）、其他（往來電子郵件、網站留言、系統自動紀錄之軌跡資訊等）。(4)個人資料利用期間：本網站會員有效期間及終止後六個月；若非會員則於該蒐集個人資料之目的消失後六個月。(5)個人資料利用地區：本公司執行業務及伺服器主機所在地，目前主要為台灣地區。(6)個人資料利用對象：本公司及本公司委外之協力廠商（例如：提供物流、金流或活動贈品、展示品之廠商）；如為本公司與其他廠商共同蒐集者，將於該共同蒐集之活動中載明。(7)個人資料利用方式：依蒐集目的範圍及本隱私權政策進行利用。(8)行使個人資料權利方式：依個人資料保護法第3條規定，您就您的個人資料享有查詢或請求閱覽、請求製給複製本、請求補充或更正、請求停止蒐集、處理或利用、請求刪除之權利。您可以聯繫我們（為避免電子郵件系統漏信或其他原因無法收悉，以本公司回覆收悉為準），本公司將於收悉您的請求後，儘速處理。(9)個人資料選填說明：若本公司於蒐集個人資料時，相關網頁或文件載明為選填者，僅為提供您使用本網站更佳體驗，不影響您使用本網站之權益。
3. 個人資料蒐集、處理及利用說明
本公司可能透過 Facebook 或類似社群服務系統，於取得您的同意後，將部分本網站的資訊發布於您的社群活動資訊頁面，若您不同意該等訊息之發布，請您勿點選同意鍵，或於事後透過各該社群服務之會員機制移除該等資訊或拒絕本網站繼續發布相關訊息。若有任何問題，仍可與本公司聯絡，本公司將協助您確認、處理相關問題。 除依法應提供予司法、檢調機關、相關主管機關，或與本公司協力廠商為執行相關活動必要範圍之利用外，本公司將不會任意將您的個人資料提供予第三人。
當本公司或本網站全部或部分分割、獨立子公司經營、被其他第三者購併或收購資產，導致經營權轉換時，本公司會於事前將相關細節公告於本網站，且本公司或本網站所擁有之全部或部分使用者資訊亦可能在經營權轉換的狀況下移轉給第三人。惟限於與該經營權轉換服務相關之個人資料。若本公司或本網站部分營運移轉予第三人，您仍為本公司會員，若您不希望本公司後續利用您的個人資料，您可以依本隱私權政策向本公司行使權利。
4. Cookie 技術
為便於日後的辨識，當您使用本網站服務時，本公司可能會在您的電腦上設定與存取 Cookie。 您可以透過設定您的個人電腦或上網設備，決定是否允許 Cookie 技術的使用，若您關閉 Cookie 時，可能會造成您使用本網站服務時之不便利或部分功能限制。
5. 保密與安全性
我們會將有權存取您個人資料之員工限於我們合理相信是為了向您提供產品或服務或為了完成工作而需要取得這些資料的員工。為了保護您的帳戶及個人資料的安全，請您不要任意將個人帳號、密碼提供予第三人或允許第三人以您的個人資料申請帳號、密碼，否則，相關責任由您自行負擔。若您的帳號、密碼有外洩之虞，請您立即更改密碼，或通知本公司暫停該帳號（本公司可能會要求核對您的個人資料）。
網際網路並不是一個安全的資訊傳輸環境，請您在使用本網站時，避免將敏感的個人資料提供予他人或在網站上公開揭露。
6. 未成年人保護
本網站並非特別為未成年人/兒童設計，未成年人使用本網站時，若同意本網站蒐集、利用其個人資訊時，應在法定代理人或監護人之同意下為之。法定代理人或監護人得隨時請求本公司停止特定帳號及其相關之個人資料之蒐集、處理及利用行為。
7. 隱私權政策之修改
HEY YO PIZZA有權於任何時間修改或變更本隱私權政策之內容，且不進行個別通知，若您不同意該等變更或修改，請停止繼續使用本網站服務，並依本隱私權政策規定通知本公司停止蒐集、處理及利用您的個人資料。
您可隨時修改個人帳號資料，我們保有權利向您傳送HEY YO PIZZA服務相關的特定訊息 (如服務公告、管理訊息)，這些訊息被視為您帳號的一部分，您無法選擇退出接收。
8.「Facebook 登入」如何收集、運作、使用顧客資料。
本公司可能透過 Facebook 或類似社群服務系統，於取得您的同意後，將部分本網站的資訊發布於您的社群活動資訊頁面，若您不同意該等訊息之發布，請您勿點選同意鍵，或於事後透過各該社群服務之會員機制移除該等資訊或拒絕本網站繼續發布相關訊息。若有任何問題，仍可與本公司聯絡，本公司將協助您確認、處理相關問題。若您所填寫之送貨地址、聯絡人、聯絡方式等非您本人之個人資料，您同意已取得各該當事人之同意提供予本公司，並已代本公司就前開法定告知事項予以告知。除依法應提供予司法、檢調機關、相關主管機關，或與本公司協力廠商為執行相關活動必要範圍之利用外，本公司將不會任意將您的個人資料提供予第三人。
如果您有任何問題或建議，請與我們聯繫。

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 LY 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