Skip to main content

VEXPLOR Logic Studio — Privacy Policy

Effective date: October 11, 2026 (previously October 10, 2026)

This is an earlier version of this policy. For the current policy, see the current privacy policy.

1. Who we are and what this policy covers

This policy explains how WACE Inc. ("WACE", "we") handles personal information in VEXPLOR Logic Studio (the "Service"), a multi-tenant manufacturing operations service hosted on Microsoft Azure. It applies to people who sign in to the Service, to people who request a trial workspace on the introduction pages of the Service, and to personal information contained in data our customers store in it. Our website vexplor.com has its own privacy policy.

2. Our role

  • Customer data. Business records a customer stores in the Service (for example work orders, quality records or employee names in those records) belong to the customer. We process them only on the customer's instructions and only to provide the Service. The customer decides what is stored and is responsible for having a lawful basis for it.
  • Account and contract data. For contact and billing information of the people who sign our contract, we decide how it is used, as described below.
  • Information we process as the customer's processor: business data the customer enters, user accounts and roles, sign-in, session and security event records, user management records, usage records and support board records. We process it on the customer's instructions, and otherwise use it only for two purposes: keeping the Service secure and billing (counts that identify no one).
  • Information we decide on ourselves: subscription information (the purchaser and beneficiary contact details Microsoft sends us), temporary activation sign-in records and activation confirmation records, trial workspace requests, emails you send us directly, and WACE operator audit records.

3. Information we collect

  • Account information: email address, name, role (owner, admin, user or viewer), and, if the customer sets them, department code and employee number. Passwords and PINs are stored only as one-way (scrypt) hashes; we never store them in readable form.
  • Sign-in records: sign-in time, IP address, browser information (user agent), a device identifier (derived from the browser type and IP range), sign-in method (password, PIN or Microsoft), failed sign-in count and temporary lock time.
  • Session records: a hash of the session token, IP address and browser information (user agent).
  • Security event records: password changes and resets, turning two-step verification on or off and resetting it (including who did it), sign-ins from a new device, and signing out other sessions.
  • Password reset requests: a hash of the reset token and the IP address that requested it.
  • Two-step verification secret: the authenticator app secret key (TOTP).
  • User management records: the email of the person who acted, the email of the affected user, the action (add, role change, suspend, reactivate, password reset, administrator handover, two-step verification reset, unlock), the time, and the reason for a handover.
  • Operator audit records: what WACE operators did in the operations console (who, when, what, and the record affected) and, where needed, the reason.
  • Account language: the language used for security notification emails (Korean or English).
  • Sign-ins to the public demo account do not create sign-in or security event records.
  • Usage records: which screen was opened and from where (menu, search, favorites and similar), favorites and recently used screens, and in-app notifications.
  • Subscription information: the purchaser's and beneficiary's email addresses and Microsoft Entra tenant IDs sent to us by Microsoft, the subscription ID, plan and status, and the email of the person who activated the subscription.
  • Temporary activation sign-in records: name, email and Microsoft account identifier. They become unusable 30 minutes after they are created and are deleted as described in section 8.
  • Activation confirmation records: subscription ID, time of confirmation, version of the terms confirmed, email of the person who confirmed, and whether they agreed to subprocessing and to usage counts.
  • Trial workspace requests: company name, contact name, work email, phone number (optional), systems in use (optional), the work you want to see first (optional), whether you want pricing information, screen language, the time you consented to the collection and use of personal information, and the status and notes our operators add. We do not store the requester's IP address (the request limit is counted only in server memory).
  • Welcome email for a new administrator: the email of a new customer's first administrator (owner) and the company name. The token in the email's password-setting link is stored only as a hash.
  • Sign in with Microsoft (only if you choose it): the email values in the sign-in result Microsoft sends us (email, preferred_username, upn), your Microsoft account object ID (oid) and your organization ID (tid). Your name is also sent but we do not store it.
  • Customer data: whatever the customer enters or connects. We do not ask for sensitive categories of personal information and the Service is not designed to hold them.
  • Contact: posts on the in-service support board (author's email and name, title and message, and the address of the screen being viewed), and information you send us by email, such as your name, company and message.

4. How we use it

  • To sign you in, keep your session and enforce what your role may do.
  • To run the Service: show screens, store records, search them and send notifications.
  • To keep the Service secure: detect repeated failed sign-ins and investigate incidents.
  • To protect accounts: detect unauthorized sign-ins, send security notification emails (such as a sign-in from a new device or a password change), and support password reset and two-step verification.
  • To help customers meet their own obligation to keep access records: we keep sign-in records and user management records so that customer administrators can review them.
  • To check usage against the customer's plan: with the customer's consent, we look only at counts that do not identify anyone (accounts, records, storage and requests), never at the content of business data.
  • To reply to inquiries and manage our contract with the customer.
  • Trial workspace requests: to contact you about opening a trial workspace and, if you asked for it, to send pricing information. We send one confirmation email to the address you entered, and it does not repeat what you wrote.
  • First sign-in of a new administrator: to let the administrator set their own first password through the welcome email.
  • Sign in with Microsoft: to match the email we receive against an existing account and sign you in. We do not create new accounts this way.

We do not sell personal information and do not use customer data to train AI models. We do not provide personal information to third parties except to the subprocessors listed in section 6 or where the law requires it.

Legal basis: where WACE decides the processing, it relies on the following bases under the Korean Personal Information Protection Act.

  • Purchase and subscription management (purchaser email, Entra tenant ID and subscription information, including activation confirmation records): Article 15(1)(iv) and (vi).
  • Activation sign-in: Article 15(1)(iv).
  • Replying to inquiries: Article 15(1)(iv).
  • Checking for repeated free trials by the same organization: Article 15(1)(vi).
  • Security monitoring (failed sign-ins and IP addresses): Article 29, within the scope the customer has entrusted to us; detecting unauthorized access across several customers: Article 15(1)(vi).
  • Trial workspace requests: Article 15(1)(i) (the consent given with the request).
  • Welcome email for a new administrator and sign in with Microsoft: Article 15(1)(iv).

For information a customer enters in the Service, the customer is the controller and WACE processes it only as the customer's processor, on the customer's instructions.

5. AI answers

This Service does not currently use a language model, and search works without one. If we start using a language model, we will first list that subprocessor on this page as described in section 6.

6. Where data is stored and who processes it for us

  • Subprocessor Microsoft Corporation (a United States company): operates the Service's database (managed PostgreSQL), application and backups on our behalf. Storage location: Microsoft Azure, Korea Central region, Republic of Korea.

For customer data, we use subprocessors only as agreed with the customer in the service contract. Our sub-processor list is published at https://vexplor.com/en/subprocessors/logic-studio. We notify customer administrators at least 30 days before we use a new sub-processor, and the customer may object within that period. Our Data Processing Addendum for customers outside the Republic of Korea is at https://vexplor.com/en/dpa/logic-studio.

Security notification emails, password reset emails, trial request confirmation emails and new administrator welcome emails are sent from no-reply@vexplor.com through a mail server that WACE operates. No subprocessor is involved and no data is transferred abroad for these emails.

Sign in with Microsoft: only if you choose this method, Microsoft Corporation, as the identity provider, sends us the sign-in result (the items listed in section 3). We do not send personal information to Microsoft for this sign-in, and Microsoft's side of the sign-in is governed by Microsoft's privacy statement.

  • Storage location. Service data and backups are stored in the Republic of Korea (Azure Korea Central). WACE staff access it from the Republic of Korea. Separately from where data is stored, personnel of Microsoft Corporation, which operates the cloud infrastructure, may access it remotely from outside the Republic of Korea when needed for support or security, so we disclose this below as processing entrusted abroad. Visit statistics from the pre-login introduction pages are processed by Google LLC (Google Analytics 4) in the United States and other countries only with the visitor's consent (see section 12).

Processing entrusted abroad (Korean Personal Information Protection Act, Article 28-8(1)(iii)(a); the items listed in Article 28-8(2)):

  • Personal information transferred: the items in section 3 that are stored in the Service.
  • Countries: the United States and other countries where Microsoft support personnel are located.
  • When and how: during the subscription, when support or security requires it, by remote network access without moving where the data is stored.
  • Recipient and contact: Microsoft Corporation, One Microsoft Way, Redmond, WA 98052, USA. Privacy contact: Microsoft Privacy (same postal address; phone +1 425-882-8080; privacy request page https://go.microsoft.com/fwlink/?linkid=2126612).
  • Purpose and period: operating the cloud infrastructure, incident response and security, for the term of our agreement with Microsoft (data remains stored in the Korean region).
  • How to refuse and what happens: you can refuse by writing to contact@wace.me. Because the Service runs only on this cloud, if you refuse we cannot provide the Service and your account will stop being used.

7. How we separate customers

Every table is protected by database row-level security. A user of one company cannot read or change another company's rows; the database refuses the request. This is checked automatically on every deployment.

8. How long we keep it

  • Data the customer enters in the Service, user accounts, usage records, support board records and the purchaser's email: for the term of the subscription, and then for 30 days (the return-request period) from the later of the subscription end date and the date we receive Microsoft's cancellation notice. If you ask for your data back during that period, we keep it until the return is complete.
  • Temporary activation sign-in records (name, email and Microsoft account identifier): unusable 30 minutes after they are created, and deleted by a once-a-day job once they are more than 1 day past expiry (at most about 2 days).
  • Session records: 7 days from the day the session ends.
  • Service inquiry emails: 1 year from the day the inquiry is closed.
  • Access records of personal information handlers (sign-in records and security event records of WACE operators and of the accounts that handle business data, that is the owner, admin and user roles and on-site PIN sign-in): 1 year from the day they are recorded. We keep them under Article 8(1) of the Korean Standards for Ensuring the Safety of Personal Information, and the customer cannot shorten this period (deleted by a once-a-day job).
  • Sign-in records and security event records of other users (view-only viewer accounts): 1 year from the day they are recorded by default, for the security of the Service. From October 31, 2026, the customer may set a shorter period of at least 90 days (deleted by a once-a-day job).
  • User management records (granting, changing and removing access rights): 3 years from the day they are recorded, under Article 5(3) of the Korean Standards for Ensuring the Safety of Personal Information.
  • Operator audit records: up to 3 years from the day they are recorded. Records related to an ongoing incident investigation or dispute are kept until that matter is closed.
  • Password reset requests: usable for 30 minutes after they are created, and deleted automatically after one day.
  • Trial workspace requests: 1 year from the day we receive them (deleted by a once-a-day job, whatever their status). If you ask, we delete your request right away (the confirmation email explains how).
  • New administrator welcome links: usable once within 72 hours of sending, and deleted by a once-a-day job after they expire (at most about 4 days). The owner's email and the company name are kept as account and customer information for the period in the first item above.
  • Temporary sign-in with Microsoft records (verified email, oid and tid): usable once within 10 minutes, and deleted by a once-a-day job once they are more than 1 day old (at most about 2 days). Sign-in records only add the sign-in method (Microsoft) and are kept for 1 year like other sign-in records.
  • Two-step verification secret: until two-step verification is turned off or reset, or the account is deleted.
  • Account language: kept with the account and deleted when the account is deleted.
  • After a customer leaves, we delete its data within 5 days after the 30-day return period ends. However, access records (1 year) and records of access right changes (3 years) that the law requires us to keep are kept separately and deleted when their period ends.

Records kept by law: the subscription identifier, plan, amount and billing period used for billing reconciliation are kept for 10 years under Article 33(1) of the Korean Commercial Act and Article 85-3(2) of the Framework Act on National Taxes. These records contain no personal information such as the purchaser's email and are kept separately from Service data.

Deletion procedure: when a retention period ends, we identify what is to be deleted and delete it within 5 days, record the date and time, the items and the method, and the privacy officer checks the result. Automatic deletion jobs record their schedule and results.

Deletion method: data is deleted from the production database so that it cannot be restored. Automatic backups expire within 7 days of the deletion date, and we do not restore deleted information from them in the meantime. We do not keep paper records.

9. Deletion when a customer leaves

When a customer's tenant is deleted, we remove the customer's data from every table and the customer's accounts, sessions, notifications and usage records, and produce a deletion record listing what was removed. Access records and records of access right changes kept under section 8 are kept apart from other information and encrypted, without pseudonymization; only a minimum number of security staff can open them, every opening is recorded, and they are deleted beyond recovery when their period ends. Both records are also included in the data we return to the customer when it leaves.

10. Security

  • Encrypted connections (HTTPS) for all traffic.
  • Row-level security on every table; the application connects with a role that cannot bypass it.
  • Passwords and PINs stored only as hashes; session tokens stored only as hashes.
  • Accounts are locked temporarily after repeated failed sign-ins.
  • Access to production systems is limited to staff who need it.
  • Trial workspace requests can be viewed only by WACE operators in the operations console, and opening a request's details is recorded in the operator audit log (who opened it and when).

11. Your rights

You, or your legal representative, can ask to see, correct or delete your personal information, or to stop its processing. If your account was created by your employer (our customer), please contact your company's administrator first; we will help the customer respond. You may also have rights under the law of the country where you live. Contact us at the address below and we will respond within 10 days of receiving your request. You can also receive your own account, sign-in, security event and inquiry records as a file (JSON). If you ask us to delete your information, we delete your account information, and keep the access records and user management records described in section 8 separately, only for the rest of their retention period, before deleting them.

12. Cookies and analytics

After you sign in, the Service uses only a cookie that keeps you signed in (vc_session) and a cookie that remembers the screen language you chose (vc_lang, 1 year), and uses no advertising or analytics cookies or analytics tools. Only if you choose to sign in with Microsoft, one more cookie (vc_msl) is used for 10 minutes to check that the sign-in returns to the browser that started it. You can block or delete cookies in your browser settings; if you do, you cannot stay signed in to the Service.

On the introduction pages before sign-in (/ and /en on logicstudio.vexplor.com), we collect visit statistics (pages viewed, referral source, device and approximate region) with Google Analytics 4 analytics cookies only if the visitor consents in the banner. If you do not consent, no analytics cookies are used. We do not use advertising storage or personalized advertising. If you choose a language on the introduction pages, the same vc_lang cookie is used. If your browser sends a Global Privacy Control (GPC) signal, we treat it as not consenting to analytics cookies.

Google Analytics 4 is processed by Google LLC in the United States and other countries (sent over the internet at the time of your visit), and the statistics are kept for 14 months under the Google Analytics data retention setting. You can change your choice at any time with "Cookie settings" in the footer of the introduction pages; from then on, analytics cookies are no longer used.

13. Contact

Privacy officer: Dong Gul Bang (CEO)

Privacy and complaints: Management Support Department, WACE Inc.

150, Dongtanyeongcheon-ro, Building A, Units 1702 and 1706, Dongtan-gu, Hwaseong-si, Gyeonggi-do 18462, Republic of Korea

Email: contact@wace.me · Phone: +82 70-4730-0629

If you are in Korea, you can also contact the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr) or the KISA Privacy Infringement Report Center (118, privacy.kisa.or.kr).

14. Children

The Service is a business service and is not intended for children under 14. We do not knowingly collect their personal information.

15. Changes

If we change this policy, we post the new version and its effective date on this page. For material changes we also notify customer administrators before the change takes effect.

Revision history: first published October 6, 2026 · revised October 10, 2026 (information collected, purposes and legal basis, AI answers, retention and deletion, privacy officer).

Added the same day, October 10, 2026: analytics on the introduction pages (section 12, cookies and analytics; section 6, international transfer).

Added the same day, October 10, 2026: sign-in security features (section 3, information collected; section 4, purposes; section 6, security emails; section 8, retention).

Added the same day, October 10, 2026: trial workspace requests, new administrator welcome emails and sign in with Microsoft (section 1, scope; section 3, information collected; section 4, purposes and legal basis; section 6, emails and Microsoft sign-in; section 8, retention; section 10, security; section 12, cookies).

Revised October 11, 2026: our role (section 2), user management and operator audit records (section 3), basis for security monitoring (section 4), storage location and processing entrusted abroad (section 6), retention (section 8), deletion (section 9), response time for requests and export (section 11), cookies (section 12), residents of the United States (section 16) and individuals in Japan (section 17).

16. Notice to residents of the United States

  • We do not sell personal information and do not share it for cross-context behavioral advertising.
  • For information we process for a customer, we are that customer's service provider and processor. Please send requests about that information (access, deletion, correction and similar) to your company; we help the customer respond, and if you send them to us directly we forward them to the customer.
  • Categories of information we process: identifiers (email, name, account identifiers, IP address), professional information (role, department code, employee number), internet activity information (sign-in and usage records) and account sign-in information (passwords and PINs are stored only as hashes). Sources, purposes and retention periods are as described in sections 3, 4 and 8.
  • Requests about information we decide on ourselves can be sent to the contact in section 13. We will not treat you differently because you made a request.
  • The introduction pages treat a GPC signal as refusing analytics cookies (section 12).

17. Notice to individuals in Japan (Act on the Protection of Personal Information, Article 32)

  • Business operator: WACE Inc., CEO Dong Gul Bang; address in section 13.
  • Purposes of use: section 4.
  • Handling in foreign countries: WACE is in the Republic of Korea and data is stored in the Republic of Korea (Azure Korea Central); our cloud infrastructure subprocessor Microsoft Corporation is in the United States. In the Republic of Korea, the Personal Information Protection Act governs the processing of personal information in general and is supervised by the Personal Information Protection Commission; individuals have rights to access, correct, delete and suspend processing, and there are duties to notify and report breaches. The United States has no general federal privacy law; Section 5 of the Federal Trade Commission Act and state privacy laws apply. We have assessed these systems and apply the safeguards described in section 10.
  • Requests for disclosure, correction, suspension of use and similar: section 11. For information your company has entrusted to us, your company is the business operator handling personal information, so please contact your company first.
  • Contact and complaints: section 13.