Privacy Policy

1. Legal Compliance

The Platform adheres to Taiwan's Personal Data Protection Act and follows GDPR standards for cross-border users.

2. Categories and Purposes of Information Collection

When registering or using Patisco, we may collect:

· Identity and contact data: name, title, company, email, phone, address · Transaction and document data: product specifications, quotations, purchase orders, proforma invoices, change records · Technical data: IP address, browser type, device info, cookies, system logs

Purposes: to provide trade collaboration services, identity verification, transaction recordkeeping, customer support, system optimization, and necessary business notifications.

3. Data Use Principles: Trust Network and Audit Trail

· Internal use: all data is limited to purposes necessary for delivering platform services · Non-repudiation records: to maintain trust in B2B trade, the system automatically records each document's submission time, operator, and modification history. These audit trails are preserved as evidence for the duration of the transaction relationship and any legally required retention period, and cannot be deleted at the unilateral request of either party · Anonymized analytics: the Company may use aggregated platform data (e.g. transaction hotspots, currency distribution) for analytics and service improvement, excluding any specific company name or individual identifier

4. Data Sharing and Third-Party Services

The Company does not sell or rent user data. Sharing occurs only in the following cases:

· Trading counterparties: when a user sends an invitation or submits a trade document, the invited party may access the relevant business information shared · API integrations / third-party services: when users enable third-party services (e.g. payment gateways, ERP/CRM integrations), the Company transmits necessary data to that provider based on user authorization · Legal requirements: when required by judicial proceedings, investigations, or regulatory authorities

5. Information Security Measures

· Encryption: the Platform enforces SSL site-wide to prevent data interception or tampering in transit · Access control: the system provides multi-tier role-based access control (RBAC); users should configure internal account permissions on a least-privilege basis · User self-protection: users must protect their account credentials and not share them with third parties; privacy breaches resulting from improper account management are the user's responsibility

6. Use of Cookies

The Platform uses cookies to record your login status and operational preferences. Users may disable cookies via browser settings, though some features (such as auto-login and collaboration tools) may not function properly as a result.

7. Data Subject Rights and Corrections

Users may access, review, obtain copies of, or correct personal data by logging into the Platform. Account deletion (subscription termination) will be handled per the subscription agreement and applicable law. Transaction audit trails already generated are not subject to deletion under this provision.

8. Connecting a Personal Mailbox (Google / Microsoft)

Patisco offers a "My mailbox" feature: users may choose to connect their personal work mailbox to Patisco through the official authorization (OAuth) of Google (Gmail / Google Workspace) or Microsoft (Outlook / Microsoft 365). This feature is entirely opt-in; users who do not connect a mailbox are not affected by this section. This section explains how the Company accesses, uses, stores, shares and deletes your mailbox data once connected.

(1) Data and permissions we obtain · Account identity (Google: openid, email; Microsoft: openid, email, User.Read): the email address you authorize with, used to show which mailbox is connected and to recognize which messages were sent by you. · Read mail (Google: gmail.readonly; Microsoft: Mail.Read): we read the headers (From, To, Cc, Subject, Date, Message-ID, etc.), body and attachments of messages in your Inbox and Sent folders. We never mark messages as read, move, delete or otherwise modify any message in your mailbox, and we do not access your contacts, calendar or mailbox settings. · Send mail (Google: gmail.send; Microsoft: Mail.Send): we send, from your own mailbox, the messages you compose in Patisco and click [Send] on. · Long-lived authorization credential (refresh token): lets the system keep synchronizing new messages while you are not logged in.

(2) Purposes · Sole purpose: to place the emails exchanged between you and your trading counterparties (buyers, suppliers and their contacts) into the discussion thread bound to the corresponding document (quotation, purchase order, proforma invoice, etc.), so that in-app collaboration and email correspondence for the same transaction live in one place. · Which emails come in: every few minutes the system compares the sender or recipients in the message headers with the buyer and supplier contacts your company has created in Patisco (or addresses you have mapped). Only matched messages have their full content and attachments retrieved; they first go to "To place", where you decide which thread they belong to, and later messages in the same conversation are placed automatically. Replies you send directly from Gmail / Outlook to a matched contact are synchronized into the same thread. Promotional, newsletter and automated bulk mail is not collected. · Mail from unknown senders: for messages that match no contact, we keep only the headers (sender, subject, date). The body and attachments are not downloaded, and only you can see these entries. When you click [View content], the system fetches the message from Google / Microsoft once for display and does not store it. Entries not handled within 14 days are deleted automatically. · Sending: an email is sent from your mailbox only when you personally click [Send] in Patisco, and it also appears in your mailbox's Sent folder. The Company never sends on another person's behalf and never sends automatically. · AI assistance (only when you click): if your company has configured its own AI assistant key, you may click [AI draft reply] to have the AI draft a reply from that discussion thread and its document, filled into the editor; the draft is sent only after you review it and click [Send]. You may also click [Ask AI to read attachments] on an email waiting to be placed, so that the AI reads that email's attachments and suggests the matching document or helps transcribe it into one; the result takes effect only after you confirm it. The AI cannot send email and never reads your mail automatically in the background. · Fetching older mail: by default only messages received after connecting are synchronized; you may opt to fetch correspondence with matched contacts from the last 30 days.

(3) Storage and protection · Authorization credentials are encrypted with AES-256-GCM before being stored in the Company's database; the encryption key exists only on the backend server and cannot be read by other systems or personnel. Short-lived access tokens are held in memory only. · Original message files (.eml) and attachments of placed emails are stored in the Company's object storage on Amazon Web Services (US East region), segregated by company and mailbox; access requires an authorization check and is served through time-limited links. · All transfers use TLS encryption; system logs never record credentials or message bodies. · Who can see what: emails waiting to be placed or claimed are visible only to the mailbox owner, not even to your company's administrators. Once placed in a thread, visibility equals that thread's participants (colleagues you chose to add). Company personnel do not read your email content unless you explicitly ask for help, it is necessary to investigate a security incident, or the law requires it.

(4) Who we share data with · Thread participants: once placed in a discussion thread, an email is visible only to the colleagues you added to that thread. Email threads are never copied to other companies using Patisco. · AI model providers: only when you click one of the AI features above, the content needed for that request (the thread's messages, the related document, or the selected attachments) is sent, using your company's own API key, to the AI model provider your company chose (Anthropic or OpenAI), solely to generate the result returned to you. Under these providers' API terms, data sent through their APIs is not used to train their models by default; the Company never transfers Google user data to any service that would use it to train AI/ML models. · Infrastructure provider: Amazon Web Services hosts our servers and storage and processes data only on the Company's instructions. · Legal requirements: when disclosure is required by judicial proceedings or competent authorities. We do not share your email data in any other case.

(5) What we do not do · We do not sell, rent or provide your email data to third parties, including advertising platforms and data brokers. · We do not use it for advertising, retargeting or building advertising profiles. · We do not use it, whether raw, aggregated, anonymized or derived, to develop, train or improve any machine-learning or artificial-intelligence model. · We do not include Google user data, whether raw, aggregated, anonymized or derived, in the anonymized analytics described in Section 3. · We do not use it for creditworthiness assessment or any purpose unrelated to the Patisco trade collaboration service. · We do not modify or delete messages in your mailbox in any way.

(6) Retention and deletion · Unlinking: you may click [Unlink] in [Profile settings › My mailbox] at any time. The system immediately revokes the authorization with Google / Microsoft, deletes the stored credential and stops synchronizing; you may also choose to delete emails that have not yet been placed. · Emails already placed in a discussion thread are transaction records and live as long as that thread, handled under Sections 3 and 7 of this Policy. · Unclaimed emails are deleted automatically after 14 days; when an account is deleted, its mailbox connections and unplaced emails are deleted with it. · You may also revoke Patisco's access from your Google Account's "Third-party apps & services" page or your Microsoft account's "Apps and services" page. · To request deletion of specific email data, contact service@patisco.com.

(7) Google API Services User Data Policy Patisco's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements, and such data is never used to develop, improve or train generalized AI/ML models.

(8) Microsoft Mail data obtained through the Microsoft identity platform (Microsoft Entra ID and personal Microsoft accounts) is handled in the same manner as described in this section.

9. Connecting a LINE Official Account

Your company's administrator may connect your company's own LINE Official Account to Patisco. This feature is enabled by your company; companies that do not connect one are not affected by this Section.

(1) Data we obtain - After the official account joins a group: that group's messages, photos, videos and files, and the LINE display name and profile image of each speaker. - When a message is edited, both the earlier and the edited versions are kept. - Messages sent before the official account joined cannot be obtained. One-to-one chats on employees' personal LINE accounts are not obtained either.

(2) Purpose - Sole purpose: to keep your company's LINE exchanges with buyers and suppliers in the matching discussion thread, as your company's business records. - When the official account joins a group, it posts a notice stating that the conversation will be kept by your company in Patisco. - Until an employee binds the group to a discussion thread, message content is not stored; only the group ID, name and message count are recorded. If a group is not bound within 7 days of joining, the official account leaves it automatically. - When a message is unsent, its content and files are also deleted from Patisco, and only an "unsent" marker remains. - Messages are sent to a group in the official account's name only when an employee presses send in Patisco. AI does not send messages.

(3) Storage and visibility - The channel secret and access token are stored encrypted with AES-256-GCM. Files are kept in the same object storage as described in Section 8. - Once a group is bound, its messages are visible to the participants of that discussion thread.

(4) Retention and deletion - Bound messages are your company's transaction records and last as long as the discussion thread. - After disconnecting, no new messages are received and existing records are kept. To request deletion, contact service@patisco.com.

(5) What we do not do We do not sell this data or provide it to third parties, use it for advertising, or use it to train any AI model.

10. Connecting a WhatsApp Business Number

Your company may connect its WhatsApp Business App number to Patisco through Meta's official signup flow. This feature is enabled by your company; companies that do not connect one are not affected by this Section. Personal WhatsApp accounts cannot be connected. Do not connect an employee's private number, because all one-to-one conversations on a connected number are synchronized.

(1) Data we obtain - One-to-one messages on the connected number, including messages sent from the WhatsApp Business App, along with the other party's phone number or WhatsApp identifier, display name, and any attached photos and files. - Earlier messages: only if your company agrees at the time of connection, one-to-one messages from up to 180 days before connection are synchronized. - Group chats are not synchronized.

(2) Purpose - Sole purpose: to keep your company's WhatsApp exchanges with buyers and suppliers in the matching discussion thread, as your company's business records. - Conversations that do not match a buyer or supplier contact do not enter a discussion thread and are visible only to the employee your company designates as the user of that number; they are deleted automatically if not handled within 14 days. If your company changes the user of the number, these unhandled conversations are deleted. - Messages are sent from Patisco only when an employee presses send in Patisco. AI does not send messages.

(3) Storage and visibility - Authorization credentials are stored encrypted with AES-256-GCM. Files are kept in the same object storage as described in Section 8. - Messages placed in a discussion thread are visible to the participants of that thread.

(4) Who the data is shared with Messages are transmitted through Meta and are subject to the terms and privacy policies of Meta and WhatsApp. Patisco processes this data only on your company's instructions.

(5) Retention and deletion - After disconnecting, no new messages are received. Messages already in a discussion thread are your company's transaction records and last as long as the thread. Conversations not yet placed in a thread are deleted. - To request deletion, contact service@patisco.com.

(6) What we do not do We do not sell this data or provide it to third parties, use it for advertising, or use it to train any AI model.

11. Amendments to This Policy

The Company reserves the right to amend this Policy at any time. Material changes will be announced on the official website or notified by email. Continued use of the service after changes take effect constitutes acceptance of the updated policy.

Contact: service@patisco.com　+886 2 2396-9522 Address: 11F, No. 34, Section 2, Jen-Ai Road, Taipei City, Taiwan 10026