Who is responsible
The store using DANGOL decides why and how its customers' information is recorded and acts as the controller for that information. DANGOL, developed by ODERYN Studio, processes it to provide the store's service. The store is your first contact for a booking or customer-data request. Product and operator contact: oderynstudio@gmail.com.
Information processed
Depending on the store's use, records include names and nicknames, phone or messaging contact details, optional birthdays, customer tags and notes, inquiries, booking dates and services, attendance and visit history. Store accounts include user names, login identifiers, password hashes, roles, schedules, assignments and activity records. Payment receipts, approvals, refunds, daily closes and audit history record amounts, methods, actors and related booking references; DANGOL does not receive card credentials or automatically read bank accounts.
Purpose and visibility
The data supports inquiries, reservation confirmation, staff and resource allocation, customer service, payment recording, reconciliation and operational accountability. Owners, managers and staff see the information permitted for their roles and duties. A public booking link submits an inquiry to the store; it does not make all store records public or automatically confirm an appointment.
Hosting and optional services
The web service uses Cloudflare Workers and D1; data can be processed outside your country. AI parsing or translation is optional and requires configuration. When used, text is sent to the configured Anthropic-compatible service after the app masks recognized phone numbers, emails, account numbers and identity numbers; masking is not a guarantee that all personal details are removed. Review the text and avoid unnecessary sensitive information. Zalo OA/ZNS and web push process the contact or subscription details needed when the store enables those integrations.
Messages, imports and photos
Staff may paste or import a conversation to prepare a reservation draft. Reading a conversation from a messenger requires the staff member to supply it or enable a supported integration; DANGOL does not automatically read every KakaoTalk, WeChat or Zalo conversation. Screenshot OCR runs on the device. Text submitted and saved as an inquiry or booking becomes part of the store's records.
Retention
Customer and booking data remain until the store applies its retention rules or processes a deletion request. The configured cleanup task defaults to removing inbox messages after 180 days, message-send logs after 400 days and completed privacy-request records after three years; deployment settings and successful task execution affect these periods. Open requests and business ledgers are not erased by those cleanup rules. The store must explain any longer retention required for accounting, disputes or law.
Access, correction and deletion
Use the privacy link from the store's booking page, or contact the store, to request access, correction, deletion or withdrawal of consent. The store verifies the request before running customer erasure. That flow removes matched customer records and selected identifiers and free-text fields from bookings and related records. It does not erase every receipt snapshot, immutable ledger, staff action, privacy-request record or backup. See https://oderyn.com/en/dangol/delete-account for the scope and alternative contact.
Security, contact and changes
Access is controlled by accounts and roles, and public service traffic uses encrypted connections. Use individual accounts and protect exported files and backups. No system guarantees absolute security. If you send ODERYN a support email, we receive the message and attachments you choose to send to handle it. Contact the store or ODERYN to exercise applicable privacy rights. Material changes will be dated here.