Privacy Policy
Last updated: 2026-11-14
General provisions
The operator of QFlow (trade name: QFlow, the "Company") complies with applicable laws, including the Personal Information Protection Act and the Act on Promotion of Information and Communications Network Utilization and Information Protection. This policy applies to "QFlow," the SaaS service provided by the Company (the "Service").
1. Personal information collected
a. Required: email address, password (stored as a one-way hash), name, company name and role.
b. Optional: name (display name), language preference and business registration number (when registering company information).
c. Automatically collected: IP address, cookies, access logs (Service usage records), User-Agent and error information for diagnosing Service errors (including call stacks and request context, with collection limits and masking applied). Section 11 explains whether optional measurement tools are in use.
d. For paid subscriptions: payment-method information (card issuer, masked card number and payment-provider billing-key identifier) and payment records (order number, amount and payment date and time). The Company does not retain the full card number, expiry date or card password; these are processed by the payment provider, Toss Payments.
Required information is processed to enter into and perform the Service agreement, within the scope in which applicable law permits processing without separate consent.
2. Purposes of collecting and using personal information
a. Identifying and authenticating members.
b. Providing the Service, including tenant-level data isolation.
c. Processing payments (email address and payment-method information: card issuer, masked card number and payment-provider billing-key identifier — outsourced to the payment provider).
d. Customer support.
e. Providing marketing information, only with opt-in consent.
3. Retention and use periods for personal information
a. Member information: until account withdrawal. Cancellation of a paid subscription is distinct from account withdrawal or destruction of personal information. Statutory retention exceptions and actual destruction are handled separately under Section 7.
b. Transaction-related records: for transactions covered by the Act on the Consumer Protection in Electronic Commerce, records of contracts, withdrawal of offers, payments and supply of services are retained for five years, and records of consumer complaints and dispute handling for three years, under Article 6 of its Enforcement Decree. The exclusion for purchases by business operators for commercial activities, and the exception where their position and transaction terms are effectively those of consumers, are distinguished under Article 3 of that Act. Its retention periods are not applied uniformly to every business-to-business transaction.
Tax evidence: records constituting books or supporting documents under Article 85-3 of the Framework Act on National Taxes are retained for five years from the day after the statutory national-tax filing deadline for the taxable period to which the transaction belongs. Where that Article's seven-year rule for offshore transactions or special retention-period provisions apply, those rules are followed. This starting point is not the payment date, subscription cancellation date or account withdrawal date.
Retention scope: records needed to establish the transaction and identify the parties are distinguished. The statutory periods above do not justify retaining all recurring-charge billing keys, raw payment-provider responses or quality data. Internal retention periods for general inquiries are also distinguished from consumer complaint and dispute records that must be retained by law. Statutory retention exceptions and actual destruction are handled under Section 7; expiry of these periods does not itself automatically delete every copy.
c. Authentication and session records: records are cleaned up once three months have passed from the creation of an authentication audit record or the most recent activity of a session. This is the current cleanup rule for the authentication and session stores; it is not the retention period for all access records of personnel handling personal information, quality audit records, or error and operational logs.
d. Quality documents and record data within the Service (including FMEA): the retention policy set by the user (tenant) and the retention periods required by IATF 16949 and OEM customer-specific requirements (CSR).
e. General inquiries: the minimum records needed to respond to follow-up inquiries on the same matter are retained for up to six months after the inquiry is closed. If a summary of the response serves the purpose, a summary is kept instead of the original inquiry; only necessary parts of the original are retained. Unnecessary originals, attachments and excessive verification materials are destroyed without delay when no longer needed, even before the period expires.
f. Privacy-rights requests: the necessary minimum evidence of receipt, identity and representative-authority verification results, actions and replies is retained for up to one year after the request is closed. Links to identity are limited to what is needed to verify the processing outcome; this is not a rule for retaining all unnecessary original requests or identity-verification materials. Even necessary evidence is destroyed without delay when its retention purpose no longer exists, including before the period expires.
g. The periods above are upper limits under the Company's internal retention rules. The need to retain each record and the lawful basis for processing it are checked; unnecessary material is not retained merely because time remains in the period. Where another law imposes a retention obligation, or a separate lawful retention basis exists for an actual ongoing dispute, the necessary information, basis and period are specified separately, and the material is destroyed without delay when no longer needed.
These retention rules for inquiry and rights-request records apply only to inquiries and requests newly received on or after November 12, 2026. They do not extend retention of existing material or apply retroactively.
4. Provision of personal information to third parties
The Company does not provide personal information to third parties without the user's consent, except in response to a lawful request based on legislation.
5. Outsourcing the processing of personal information
The Company outsources the processing of personal information as follows to provide the Service.
a. Supabase — data storage (hosting, AWS Seoul region, ap-northeast-2).
b. Vercel — Service delivery (hosting, AWS Seoul region).
c. Toss Payments — payment processing.
d. Resend — sending email notifications.
e. Sentry — error logging (after masking personal information).
f. Optional measurement — Vercel Web Analytics visit statistics and Sentry performance tracing are not used. Retention and deletion of previously collected data are separate from stopping new collection.
g. Upstash, Inc. (a US entity; data storage: Tokyo region, Japan) — outsourced task: limiting request frequency (rate limiting) to prevent Service abuse — information processed: IP address and tenant identifier — retention: automatically deleted when the applicable rate-limit time window expires.
6. Overseas transfers of personal information
a. The Company stores the Service's principal data in Korea (AWS Seoul region, ap-northeast-2). Personal information is processed overseas only for the activities described below.
b. Resend, Inc. — destination country: United States (sending routed through the Tokyo region, Japan) / information transferred: email address, display name and language preference / timing and method: transmission over an information and communications network when notification, invitation or payment-information emails are sent / purpose: sending email on the Company's behalf / retention and use period: until the sending purpose is fulfilled (subject to the processor's published retention policy) / contact: the processor's privacy policy (resend.com/legal/privacy-policy) and privacy@qflowqms.com.
c. Functional Software, Inc. (Sentry) — destination country: United States / information transferred: technical logs generated when an error occurs (after masking personal information) / timing and method: transmission over an information and communications network when an error occurs / purpose: collecting Service errors and responding to incidents / retention and use period: 30 days from collection (up to 90 days depending on the plan) / contact: the processor's privacy policy (sentry.io/privacy) and privacy@qflowqms.com.
d. Upstash, Inc. — destination country: Japan (Tokyo region; a US entity) / information transferred: IP address and tenant identifier / timing and method: transmission over an information and communications network when the Service is called / purpose: limiting request frequency to prevent Service abuse / retention and use period: automatically deleted when the applicable rate-limit time window expires / contact: the processor's privacy policy (upstash.com/trust/privacy.pdf) and privacy@qflowqms.com.
e. Users may refuse these overseas transfers by contacting privacy@qflowqms.com. However, because the outsourced processing above is necessary to provide the Service, refusal may limit all or part of the related features, such as receipt of notification emails.
7. Destruction of personal information
a. The Company destroys personal information without delay when its retention period expires or its processing purpose is fulfilled.
b. When destroying personal information in electronic files, measures are taken to prevent its recovery or reproduction. Personal information that must be retained under other laws is subject to the retention basis, information categories and periods prescribed by those laws, and to the obligation to store and manage it separately from other personal information.
c. Automatic destruction of entire accounts or organizations' data is not operated. The responsible staff member handles withdrawal and deletion requests manually after checking the processing scope and statutory retention exceptions. Subscription cancellation or scheduling an organization for deletion does not itself complete actual destruction. Individual rights requests are distinguished from the handover procedure for organizational data.
d. The responsible staff member manually manages and destroys inquiry and rights-request records after checking the closure date, retention purpose, expiry date, exceptions and locations of copies. Remaining provider and backup copies are checked separately from the results of deletion actions. Internal verification or approval procedures do not postpone statutory deadlines for action or notification.
8. User rights
a. Users may request access to, correction or deletion of, or suspension of the processing of their personal information, or withdraw consent.
b. Requests may be submitted to privacy@qflowqms.com without registering, logging in or holding a paid subscription. Non-members, former users and duly authorized representatives may also make requests. The Company uses the minimum necessary information to verify identity, representative authority and the scope of the request.
c. Access is provided within 10 days of receipt of the request in accordance with applicable law. Where statutory grounds exist for restriction, postponement or refusal, the grounds and the procedure for raising an objection are provided within the same period.
d. Necessary action is taken without delay on requests for correction, deletion or suspension of processing. Within 10 days of receipt of the request, the Company notifies the requester of the action taken or the statutory grounds for refusal and the procedure for raising an objection.
e. When consent is withdrawn, necessary action, including destruction, is taken without delay in accordance with applicable law. If retention is required by law, the applicable exception and handling method are explained.
f. Grounds for refusal or non-action are notified without delay where the law requires notification without delay.
g. Individual rights requests are handled separately from termination and data-handover procedures for customer organizations.
9. Security safeguards
a. Member passwords are stored by the authentication service as individually salted, one-way bcrypt hashes. Plaintext passwords are not stored.
b. TLS encryption is applied to Service connections, and encryption at rest is applied to the principal data stores.
c. Cross-tenant access controls based on row-level security (RLS) and role-based permission management.
d. Modification and deletion of audit records are restricted through ordinary user paths, and hash-chain verification is provided.
e. Quarterly internal reviews.
10. Privacy officer
a. Name: Ki-Hyun Jung (Representative).
b. Contact: privacy@qflowqms.com.
11. Use of cookies
a. Essential cookies: cookies necessary to provide the Service, including maintaining login sessions and preventing CSRF.
b. Analytics cookies are not used. Optional Vercel Web Analytics visit statistics and Sentry performance tracing are not used either.
c. Errors are collected separately for Service diagnostics, with collection limits and masking applied. Stopping new collection by optional measurement tools does not mean previously collected data has been fully deleted.
12. Notice of changes
a. Additions, deletions or amendments to this policy are announced through Service notices at least seven days before taking effect, or 30 days beforehand if user rights are materially affected.
b. The corrections to confirmed facts and rights procedures announced on October 12, 2026 are reflected in this revision from October 20, 2026. Existing statutory rights and safeguarding obligations, and rights favorable to users under individual contracts, are not deferred until that date or retroactively restricted by this correction. The public launch date is determined separately.
c. The retention rules for inquiry and rights-request records announced on October 12, 2026 take effect on November 12, 2026, after 30 days of notice counted from the day after publication. These retention rules apply only to inquiries and requests newly received on or after November 12, 2026. They do not extend retention of existing material or apply retroactively.
d. The clarification of transaction and tax-record retention announced on October 14, 2026 is reflected in this revision from November 14, 2026, after 30 days of notice counted from the day after publication. Statutory retention obligations and user rights already in force are not deferred until that date. This correction alone does not extend retention of existing material or require blanket retention of material to which the legislation does not apply.