นโยบายความเป็นส่วนตัว Partigo / Privacy Policy

PARTIGO PRIVACY POLICY Effective Date: 13 August 2026 This Privacy Policy explains how Partigo collects, uses, stores, shares, retains, and protects personal data in connection with the Partigo app, booking features, influencer tools, invitations, payment flow, keep-card functions, customer support, and related operational systems. We wrote this policy to describe how the service works in practice. Some venue-side processes are controlled by participating venues, so their own policies may also apply when they receive or use information for on-site operations. 1. WHO IS RESPONSIBLE FOR DATA HANDLING For data processed inside the Partigo platform, Partigo acts as the service operator responsible for deciding why and how account, booking, support, and internal operational data are processed. When venue staff receive guest names, attendance details, invitation status, bottle records, or other information needed to serve a booking or a keep card, that venue may separately control how it uses those records within its own lawful operations. 2. CATEGORIES OF PERSONAL DATA WE COLLECT We may collect and generate the following categories of personal data: - Account and profile information such as name, nickname, phone number, email address, gender information, nationality, language preference, social handle, year of birth or date of birth, profile image, and preferred venues. - Booking information such as selected venue, event date, table or slot type, arrival deadline, booking status, invitation status, late-booking status, payment timer, cooldown rule, cancellation reason, expiry status, and no-show indicator. - Influencer information such as grade, follower range, preferred clubs, pool registration dates, guest count, application history, invitation response history, attendance quality, support history, and uploaded supporting materials. - Payment and transaction information such as payment channel, processor reference, amount, currency, capture status, refund review notes, dispute flags, anti-fraud indicators, and transaction timestamps. We do not intentionally store full raw card numbers or card security codes in our own application database. - Keep-card information such as item label, proof image, stored balance, transfer record, redemption record, recipient record, expiry, and venue verification notes. - Device, technical, and usage information such as device type, operating system, app version, IP address, session timestamps, push token, crash logs, error logs, and activity events generated while using the service. - Communication and support information such as chat logs, customer-service submissions, screenshots, issue reports, appeal content, and outcome notes. 3. HOW WE RECEIVE PERSONAL DATA We receive data directly from you when you register, edit your profile, complete a booking, submit guest details, upload proof, message support, or use keep-card features. We also receive data automatically from your device and app usage, from payment service providers, from venues involved in bookings or check-ins, and from authorized internal review by staff who manage risk, support, or venue operations. If you provide information about friends, guests, or recipients, you are responsible for having an appropriate basis to provide that information and for ensuring that it is reasonably accurate. 4. WHY WE USE PERSONAL DATA We use personal data to operate the service, perform bookings, manage invitations, deliver keep-card records, process payments, provide customer support, review disputes, improve reliability, reduce abuse, and comply with legal obligations. In particular, we may use data to: - create and manage user accounts; - determine eligibility for bookings, invitations, influencer opportunities, and support programs; - enforce reservation locks, timer windows, expiry rules, and anti-abuse cooldowns; - verify attendance, arrival timing, and no-show outcomes; - maintain transaction records, handle refund reviews, and respond to chargeback or fraud claims; - communicate service notices, alerts, invitation updates, and support replies; - analyze service quality, diagnose errors, and improve features; - meet legal, tax, accounting, safety, and recordkeeping obligations. 5. LEGAL BASES FOR PROCESSING Depending on the situation and the law that applies, we may process personal data because it is necessary to perform a contract with you, because we have a legitimate interest in operating and protecting the service, because we must comply with a legal obligation, or because you have given consent. Examples include contractual necessity for booking management, legitimate interests for risk review and service reliability, legal obligation for tax and accounting records, and consent for certain optional communications where required by law. 6. BOOKING, VENUE, AND ATTENDANCE OPERATIONS To make reservations work in practice, we may share relevant user and booking data with the venue or venue staff responsible for guest list management, table handling, identity checks, arrival validation, invitation handling, no-show review, or keep-card verification. This may include guest names, phone number, profile status, booking status, arrival deadline, table details, invitation status, and records needed to determine whether a booking was used, expired, or violated venue conditions. 7. INFLUENCER DATA AND MEDIA MATERIALS If you use influencer features, we may process information about your profile quality, grade, follower range, preferred clubs, uploaded screenshots, invitation responses, group composition, and attendance history to operate the pool and invitation system. Where a venue reviews influencer applications, Partigo may present only the information reasonably needed for that review, such as nickname, profile photo, follower range, grade, support history, no-show history, preferred clubs, and relevant notes. 8. PAYMENTS, FINANCIAL DATA, AND FRAUD PREVENTION Payments are processed through external channels or providers. Partigo normally receives confirmation, status, and reference information rather than storing full raw payment credentials. We may use transaction data, device signals, session data, timing patterns, reversal history, and account behavior to detect duplicate payments, suspicious activity, abusive refund patterns, or attempts to manipulate limited inventory. 9. CUSTOMER SERVICE, APPEALS, AND COMMUNICATION RECORDS When you contact support or file an appeal, we may keep the details of your report, screenshots, attachments, follow-up discussion, internal review notes, and the final resolution for service quality, compliance, and recordkeeping purposes. We may send transactional messages, support updates, invitation notices, booking reminders, risk notices, and policy notices that are necessary for the service. Optional marketing communications will be handled in accordance with applicable consent rules. 10. SHARING AND DISCLOSURE We may disclose relevant information to: - venues and venue staff that need the information to provide the requested reservation, entry flow, invitation handling, or keep-card service; - payment processors, banking channels, cloud providers, notification services, storage services, analytics providers, fraud-prevention vendors, and support tools acting on our instructions; - professional advisers, auditors, insurers, regulators, courts, or authorities where necessary to protect legal rights or comply with legal duties. We do not sell personal data in the ordinary sense of selling customer lists as a retail data product. 11. INTERNATIONAL OR CROSS-BORDER PROCESSING Some service providers that help us operate the app may process data outside Thailand. Where cross-border processing occurs, we take reasonable steps to require appropriate safeguards, vendor review, access controls, and contractual protections. 12. DATA RETENTION We collect and keep personal data only for operating, securing, supporting, and legally administering the service for the purposes described in this policy. We do not keep it indefinitely merely because it may be useful. Retention may continue only where it remains necessary for those purposes, for the establishment, exercise, or defense of legal claims, or to comply with law. Typical examples include: - account and profile data while the account is open. When account closure is confirmed, access is disabled and the profile is removed from ordinary service use and discovery. To preserve evidence of the account and its activity in case of a later complaint, chargeback, fraud investigation, or legal dispute, a closure-time snapshot of the account, profile, consent, booking, support, security, and audit context may be moved to a restricted archive and normally kept for 5 years after closure. It is not used for advertising, recommendations, or ordinary service operation; - booking, receipt, payment-reference, refund, and transaction records normally for 5 years from the relevant tax filing, report, receipt, or transaction record, and up to 7 years where the Thai Revenue Department or another applicable rule requires or orders a longer period; - support, appeal, fraud, security, chargeback, and dispute records while the matter is open and afterward only for the period reasonably needed to document the outcome or establish, exercise, or defend legal claims. If a complaint, investigation, audit, or dispute is pending when a normal retention period expires, the relevant archive is placed on a documented legal hold and retained only until that matter and the applicable claim period are resolved; - booking chat messages and related chat metadata for at least one year (365 days) from the latest relevant record creation, chat activity, booked visit, booking completion or cancellation, refund, or benefit-restoration or forfeiture date. This is our ordinary service evidence-retention period, not a claim that the law requires one year for every chat. Deletion is deferred while a related cancellation, refund, or benefit-restoration process remains unresolved, relevant dates require verification, or an evidence-preservation, security, accounting, legal, or active-dispute hold applies. Reaching the minimum period does not cause immediate automatic deletion; records become eligible for retention review and controlled cleanup only after the applicable periods and holds have ended; - technical logs only for the limited period needed to diagnose incidents, enforce security, and maintain reliability, after which they are deleted or de-identified unless subject to a documented legal or security hold. Account closure therefore does not mean that every record is erased immediately. It means that ordinary account access and use stop and a closure-time evidence snapshot may remain in a restricted archive for the periods above. Archived data is limited to dispute, security, fraud-prevention, accounting, tax, audit, and legal-compliance purposes; it is access-restricted and may not be restored for ordinary product use or marketing. It is deleted or irreversibly de-identified when the applicable retention purpose and period end, unless a documented legal hold still applies. We maintain a review process for records that reach the end of their retention period. 13. SECURITY MEASURES We use administrative, technical, and organizational measures designed to reduce unauthorized access, misuse, alteration, loss, or disclosure. These may include role-based access, internal permissions, vendor review, secured environments, authentication barriers, activity logging, and operational review. No app or internet-connected system is completely free from risk. If we identify a material security incident, we will respond in line with applicable law and our internal response process. 14. YOUR RIGHTS AND CHOICES Depending on applicable law and subject to legal limitations, you may have the right to request access to your personal data, request correction, request deletion, object to some processing, request restriction, withdraw consent where consent is the basis, or request a copy of certain data. We may need to verify your identity before fulfilling a request. Some requests may be denied or limited where the law permits, where another person's rights are affected, or where we must retain the information for legal or operational reasons. 15. CHILDREN AND AGE-RESTRICTED SERVICES Partigo is not intended for children and is not designed for users who are below the legal age for the nightlife or alcohol-related use case involved. If we reasonably believe an account belongs to an underage user, we may restrict or remove the account and related data where appropriate. 16. POLICY CHANGES We may update this Privacy Policy to reflect legal developments, service changes, venue-integration changes, product updates, or security improvements. The most recent version will be posted in the service together with the revised effective date. 17. CONTACT, REQUESTS, AND COMPLAINTS If you have privacy questions, want to exercise a right, or wish to make a complaint about data handling, please contact: Partigo Privacy Contact Primary in-app channel: Customer Center > 1:1 Inquiry Privacy email: lavie@rizzent.com Service reference name: Partigo Operating reference location: Bangkok, Thailand If you are making a privacy request, please tell us which right you want to exercise, such as access, correction, deletion, consent withdrawal, objection, complaint, or marketing opt-out. To protect account security, we may request enough information to confirm that the request is being made by the account holder or a properly authorized person. When writing to us, it is helpful to include the email address used for the account, the phone number or nickname associated with the account, the country where you are using the service, and the specific booking, support ticket, or transaction involved if your request relates to a particular event. This helps us locate the correct records and answer more accurately. If you remain dissatisfied after contacting us, you may also raise the matter with the relevant regulator or authority that has jurisdiction over your complaint.