Terms and Conditions
Scope
These Terms & Conditions cover Glamish and Glamish Partner. Customer provisions apply when booking, purchasing or using customer features. Partner provisions apply when managing a shop, its clients, staff or business records. Agreeing to these terms does not authorise unrelated marketing or constitute consent on another person's behalf.
Operator & Contact
Code on Petra Inc. in the Republic of Korea provides the Glamish platform. Code on Petra OPC in the Philippines provides local customer and partner support by receiving enquiries and complaints and forwarding them to Code on Petra Inc. for review and action. Participating shops are separate businesses that provide the services listed in the apps and independently use the customer information needed to deliver their services.
Service and privacy enquiries: info@codeonpetra.com
Website: https://www.codeonpetra.com
Include the relevant shop and transaction reference when reporting a problem. Do not send your password, verification code or full payment credentials.
Customer Terms — Accounts & Access
You can browse public shop information without signing in. Reservations, purchases and personal account features require sign-in. Mobile verification is required to claim vouchers. Google or Apple sign-in does not by itself verify your mobile number.
Keep your account information accurate and protect access to your device and sign-in credentials. Do not impersonate another person, make fraudulent bookings or misuse offers and payment features.
Reservations, Cancellation & Refunds
Review the selected shop, services, specialist or space, date, time and price before submitting. A request is not a confirmed reservation until the app shows the applicable confirmation and payment status. Changes proposed by a shop must be reviewed before you accept them.
The shop is responsible for the services it provides, its availability and the accuracy of its listing. Contact the shop about service requirements or a booking problem, and contact Glamish about an app or transaction-record problem.
Use the cancellation action available in the reservation details. A cancellation request is not automatically an approved cancellation or refund. The applicable booking conditions, transaction status and payment method determine the next steps. No fixed refund deadline or unconditional no-refund rule is imposed by this notice.
Nothing in these terms removes consumer remedies or responsibilities that applicable law places on a shop or the platform.
Payments, Glamish Points & Vouchers
Check the amount and payment method before paying. Keep the payment reference and use the recorded transaction status to check progress. A pending or failed payment is not proof of a successful purchase.
Point products and vouchers have their own eligible shops, value, service restrictions, validity and usage conditions. A balance at one shop is not automatically available at every other shop. Review the offer details before purchase, claim or redemption; ask for clarification if a condition is unclear.
Do not create duplicate accounts or submit false information to obtain repeat claims or other benefits. Deleting and recreating an account does not reset prior voucher claims or restore old balances and entitlements.
Reviews & Content
Reviews should describe your actual service experience. Review content may be visible to other users. Do not publish another person's contact details, sensitive information, unlawful content or material you do not have permission to share.
Partner Terms — Authority & Shop Information
Use Glamish Partner only for shops you are authorised to manage. Shop owners and managers are responsible for granting and reviewing access, protecting shared devices and removing access when an employee or manager no longer needs it.
Keep shop details, map pins, services, prices, hours, specialist availability and booking conditions accurate. Shop listings, thumbnails, shop images, galleries and other published content can be visible in the customer app. Obtain permission for content showing clients, employees or another rights holder's work.
Bookings, Payments & Business Records
Confirm and fulfil bookings responsibly and keep service status and payment records accurate. Do not mark a service as completed or a payment as received unless that reflects the actual transaction. Communicate changes, cancellation decisions and refund handling to the affected customer.
Use Glamish Points and vouchers only within their stated eligibility and redemption conditions. Do not promise redemption at an ineligible shop or create false point, voucher or payment transactions.
Commercial charges and settlement amounts are those disclosed in the relevant plan, invoice, statement or separately agreed terms. This page does not introduce a new subscription price, fee, commission or settlement deadline.
Client Information & Customer Care
A shop may receive a client's name, mobile number, User Number and related service and transaction information when handling that client's activity. Use it for the disclosed booking, service, payment, points and customer-care purposes, not unrelated profiling or unsolicited marketing.
The shop is responsible for its own collection and use of client information, including any required notice, lawful basis and permission. Access through Glamish Partner is not blanket consent to copy client lists, contact customers for promotions or share their information with another business.
Limit notes to information genuinely needed for the service. Do not enter unnecessary health, identity-document, financial or other sensitive information. Never record passwords, verification codes or full payment credentials in notes.
Attendance, Payroll & Incentives
Employee records can include identification, role, attendance times and live check-in or check-out photos, salary settings, incentive rules and payment history. Inform employees about the information collected, its purpose and who can access it before using these features.
Select the correct employee on a shared device. Attendance photos are evidence submitted for shop attendance records, not a guarantee of identity or a substitute for reviewing disputed attendance.
Automatic incentives depend on the configured rules and recorded service amounts. Multiple matching rules can contribute to the same incentive. Review rules and recorded payments before payroll settlement. A pending incentive or a manually marked payment is an operational record, not proof that a bank transfer occurred.
The employer remains responsible for employment arrangements, payroll accuracy, taxes, statutory benefits and applicable labour requirements. Glamish records do not replace those obligations.ext, images, and elements right on the page, streamlining your workflow and maintaining control over your content.
Privacy notice
Revision date: October 28, 2026
Code on Petra Inc. in the Republic of Korea operates Glamish and Glamish Partner. We process sign-in and profile details for your account and the bookings, payments, points and vouchers you request. The selected shop receives relevant contact and transaction information for your requested activity and client records. Partner features also process shop, employee, attendance, payroll and operational records. This document explains recipients, retention, international processing and your rights. It does not grant permission for unrelated promotional contact.
Operator & Contact
Glamish and Glamish Partner are provided by Code on Petra Inc., a company in the Republic of Korea. Participating shops are separate businesses that provide the services listed in the apps and independently handle the client information they use to provide those services.
Service and privacy enquiries: info@codeonpetra.com
Website: https://www.codeonpetra.com
Include the relevant shop and transaction reference when reporting a problem. Do not send your password, verification code or full payment credentials.
Privacy — Customer Information
Account data can include your User Number, sign-in identifier, name, verified mobile number and email or profile information supplied through a chosen sign-in provider. Booking and transaction data can include shop and service choices, dates, payment references, points, vouchers, reviews and notifications.
When you transact with a shop, its authorised accounts may access your name, mobile number, User Number and related booking, visit, payment, points and voucher records for service delivery and customer care. These records can form the shop's client history. Simply opening a public shop page is not consent to promotional contact.
When registering or when the current policy version needs acknowledgement, the apps show the Terms & Conditions and Data Privacy for you to review. Before submitting a reservation, payment or voucher use, the app explains the information shared with the selected shop. Acknowledgement is recorded against your sign-in account, policy version and server-recorded time. It is not blanket consent or permission for additional marketing.
Information Shared with the Selected Shop
When you submit a reservation, make a payment or use a voucher with this shop, Glamish provides its authorised owner and managers with your name, mobile number, User Number and the related service, booking, payment, points and voucher information. Simply browsing the shop does not do this.
Purpose & client history
The shop uses this information to handle your requested service or transaction, contact you about it, maintain your client and visit history, and provide related customer care. These necessary activities support the service you request; this notice is not consent to unrelated profiling or marketing.
The shop is a separate business and is responsible for its own use and protection of client information. Its service and transaction records may remain after account deletion when needed for recordkeeping, disputes or legal obligations. Ask the shop or info@codeonpetra.com about access, correction, retention, deletion or an objection to a particular use.
Do not enter unnecessary health details, identity-document numbers, passwords or payment credentials in booking notes. Any additional purpose requiring consent must be requested separately. Confirming this notice does not authorise promotional calls or messages.
Privacy — Partner, Shop & Employee Information
How information is collected and recorded
Partner account details are supplied during account registration and updates. Firebase Authentication handles sign-in credentials and account verification. The associated partner profile, shop membership and access role are stored in Firebase Firestore.
Shop owners and authorised managers enter or update shop details, staff settings, service listings and business records in Glamish Partner. These records are stored in shop-specific Firestore records. Client records may be entered by a shop or created and updated when a client uses Glamish services that generate a shop record. Point sales and other service or transaction records are recorded in the relevant shop records; some transaction and history records are generated by Glamish server functions.
The app captures an attendance photo with its in-app camera. It uploads the photo to Firebase Storage and saves the employee reference, check-in or check-out time and photo reference in the shop's attendance record in Firestore. If the attendance photo upload or record save fails, the app attempts to remove the uploaded photo.
Shop or service images selected for a gallery or listing are uploaded to Firebase Storage. The app stores their filenames, captions and related listing information in Firestore. Client and service notes, review replies and other text are saved with the corresponding shop record.
Information processed can include partner account identifiers, email and phone number; shop name, business address and exact map pin; employee names and roles; client display names, Glamish User Numbers or account identifiers and contact details when provided; service and visit history; Glamish Points activity, purchases, sale amounts and recorded payment methods; revenue, expenses, bills, inventory movements, payroll and incentives; photos, captions, notes and review replies; and operational logs.
How information is stored, accessed and shared
Firebase Authentication stores and verifies partner sign-in accounts. Firebase Firestore stores partner profiles and shop-scoped records, including client, service, attendance, sales, payroll and operational records. Firebase Storage stores uploaded image files. Firebase Cloud Functions process selected server-side actions, such as transaction updates, history and notification delivery. A partner's notification token and device platform are stored with the associated partner and shop so Glamish can send service notifications; the token is not made readable to other app users.
Private shop records are protected by Firebase sign-in and shop-membership/role checks. The current rules require a verified account associated with the shop for private operational records; access is limited to the shop records the account is authorised to use. Authorised Glamish administrators and service providers may access or process information as needed to operate, secure, support or maintain the service.
In Glamish, a shop and its listing information are shown to users only when the shop is public. The app uses the shop's visibility status to control whether it appears in user-facing discovery and listings. Separately, the current Firebase read rules allow direct, unauthenticated reads of shop information (including its map coordinates) and files stored under menu, home, gallery, employee-display and thumbnail paths; those rules do not check the shop's visibility status. This does not make a hidden shop appear in Glamish, but a person who obtains a direct document or file reference may be able to access it outside the app's visibility filter. Treat content in those paths as potentially public. Making a shop private in Glamish does not by itself make those underlying Firebase paths private.
Attendance photos and operational attendance records use shop-scoped locations protected by partner access rules. They are separate from public listing media.
We use these records to provide and secure Partner accounts, operate shop-management features, handle services and transactions, maintain client and business history, manage staff attendance and payroll, deliver notifications, and diagnose service issues. Shop, staff, client and transaction records are associated with the relevant account or shop so authorised users can use them for these functions.
Processing Purposes & Permissions
Information is processed to provide requested account, booking, transaction and shop-management services, communicate service updates, maintain records, prevent abuse and handle support requests. Applicable legal grounds may include a requested contract, legal obligations, permitted legitimate interests or specific consent where required.
A device permission or this privacy notice is not blanket consent to unrelated uses. Marketing and any other additional purpose must have its own applicable basis and required notice or permission. Refusing an optional permission may make that particular feature unavailable without preventing unrelated use.
Sharing and advertising
Accounts authorised for a shop can view the shop records allowed by their access role, including client and employee information. Google Firebase provides authentication, database, file storage, server functions and notification infrastructure; Google Maps provides map features. These providers may process information needed to operate those services, including technical or diagnostic information generated by their SDKs.
Glamish Partner does not include third-party advertising and does not use information to track you across other companies' apps or websites for advertising, or share it with data brokers for that purpose.
Location & Device Information
Current-location discovery uses device location when you choose that feature and grant permission. It helps resolve a supported area and nearby shops. You can instead choose a region or city manually and change location permission in your device settings.
The current app keeps region, city and current-location preferences on your device. It does not save your live discovery coordinates as a shop client location record.
Notification delivery uses device registration tokens. The app also processes operational and transaction activity needed to maintain records and investigate errors. Promotion interactions may be recorded for campaign reporting.
Location in Glamish Partner
The shop's exact latitude and longitude are saved in its shop information and are used to display or validate the shop's location. The shop coordinates are part of public shop information under the current database rules. At attendance check-in or check-out, Partner requests the device's current location and compares it on the device with the saved shop coordinates. The current implementation does not upload or save the live device coordinates as an attendance record. Attendance records store the check-in or check-out time and submitted attendance photo.
Service Providers & International Processing
Glamish uses Google Firebase for authentication, database, file storage, server functions and notification infrastructure, and Google Maps for maps. Their SDKs may process technical information such as device or platform identifiers, app interactions, diagnostics, crash reports and performance information to provide and maintain their services. The customer app also offers Google and Apple sign-in. Payment and administration services process the information needed for the transaction or business record involved.
Code on Petra Inc. is based in the Republic of Korea and the service supports participating shops in the Philippines. Authorised access and provider infrastructure can involve processing outside your country. Contact us for information about the recipient, processing location and safeguards applicable to your information.
Provider information:
Firebase: https://firebase.google.com/support/privacy
Google: https://policies.google.com/privacy
Apple: https://www.apple.com/legal/privacy/
Google Maps additional terms: https://www.google.com/help/terms_maps/
Retention, Security & Your Rights
Customer Account Deletion & Retained Records
Request deletion in My Info using Delete Account. The current workflow has a 14-day waiting period; permanent deletion runs in the daily cleanup after that period. Signing in before deletion starts allows the pending request to be cancelled.
Deleting the account removes the sign-in account and records stored under the customer account. It does not erase every shop or transaction record. Shop voucher-use history retains the User Number as its client identifier. Voucher-claim history in the administration system retains the User Number and mobile number for duplicate-claim checks. User Numbers are not reused, and re-registration does not restore prior claims.
Shop Records & Ending Access
Removing an employee's access or leaving a shop revokes that account's access but does not automatically delete the shop's attendance, payroll, payment, service, client or audit history. Shop records are retained for ongoing shop operations and may remain for transaction reconciliation, disputes, security or legal recordkeeping. Retention periods vary by record; there is no single fixed retention period for all Partner records. Contact the shop and info@codeonpetra.com to request access, correction or deletion review. Records that the shop or platform must retain may not be erased immediately.
Glamish and Glamish Partner use a shared authentication service. Where the same sign-in identity is used in both apps, deleting that identity through the customer account can affect Partner access. Contact info@codeonpetra.com before deletion if it is linked to an active shop.
Account and operational records are kept for their service purposes and may need to remain for transaction reconciliation, dispute handling, fraud prevention or legal recordkeeping after access ends. Retention depends on the record and purpose; account closure is not automatic deletion of every shop's records. Ask info@codeonpetra.com about a specific record and retention period.
Access controls and authenticated shop membership restrict non-public records. Protect your own device and credentials and report suspected unauthorised access promptly. No online service can promise absolute security.
Subject to applicable law, you may request access, correction, deletion, restriction or objection to processing, withdrawal of consent, or a copy of your information. Send requests to info@codeonpetra.com. Identity checks may be needed, and records that must lawfully be retained may not be immediately erased.
You may also raise a concern with an appropriate authority, including the Philippines' National Privacy Commission (https://privacy.gov.ph) for privacy concerns, or the Department of Trade and Industry consumer assistance service (https://consumercare.dti.gov.ph) for consumer concerns.
Material changes to this notice will be communicated appropriately. Where applicable law requires consent for a new purpose, we will request it separately. Publishing this notice alone does not record consent.
This notice is governed by the laws of the Republic of the Philippines. Privacy matters are addressed under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173) and applicable rules of the National Privacy Commission. Mandatory consumer, employment and data-protection rights and remedies are not waived.