External transmission policy
OUEN Co., Ltd. (“we”) uses services run by other companies on this website — to display the type, to provide the enquiry forms and keep them from being abused, to show a map and a video, and to measure how the site is used. When you open a page that uses one of them, information is sent from your device to that company. Who receives it, on which pages, what we and they use it for, what is sent and how to stop it are set out below.
The background videos on this site are served from our own servers, so nothing is sent outside for them.
Google Fonts (web fonts)
Who receives it — Google LLC
Where it happens — Every page of this site. It is sent as soon as the page opens.
What we use it for — Displaying the typefaces used for the headings and body text.
What the recipient uses it for — Google says it uses the information it collects to provide its services and to maintain and improve them (Google Privacy Policy, “Provide our services” and “Maintain & improve our services”).
What is sent — Your IP address, the type of browser, OS and device, and referrer information (depending on your browser’s settings, either this site’s origin or the URL of the page).
Cookies — On 17 October 2026, opening this site in a fresh browser profile, we saw no cookies stored by this service. It may differ with your settings or if the company changes how the service works.
How to stop it — We do not offer a setting for this. To stop it, block requests to fonts.googleapis.com and fonts.gstatic.com, for example with a browser extension. The typefaces then fall back to your browser’s defaults; the content is still readable.
The company’s privacy policy — Google Privacy Policy
HubSpot (forms)
Who receives it — HubSpot, Inc.
Where it happens — The pages carrying the contact, document request, guidebook, pre-validation and job application forms. It is sent as soon as the page opens.
What we use it for — Displaying the form and receiving what you enter in it.
What the recipient uses it for — HubSpot says it uses the data to provide the service to us (showing the form and holding what is submitted) and to run, improve and protect its own services (HubSpot Privacy Policy).
What is sent — An identifier stored in a cookie, your IP address, the type of browser, OS and device, referrer information, and whatever you enter in the form if you submit it. Loading the form also sends HubSpot information about how its own form is running, including errors, to its servers (api.hubspot.com, app-na2.hubspot.com, metrics-fe-na1.hubspot.com, metrics-fe-na2.hubspot.com, exceptions-na2.hubspot.com and static.hsappstatic.net).
Cookies — On 17 October 2026, loading the ten pages that carry a form, we saw cookies stored on the domains hsforms.net, hsforms.com, hubspot.com and hsappstatic.net.
How to stop it — Disabling cookies does not stop the request that loads the form; your IP address and the rest are still sent. To stop the request, block those domains, for example with a browser extension. The form will then not appear, so please write to the address below instead.
The company’s privacy policy — HubSpot Privacy Policy
reCAPTCHA (keeping the forms from being abused)
Who receives it — Google LLC
Where it happens — The pages carrying the contact, document request, guidebook, pre-validation and job application forms (ten pages in Japanese and English). It is sent as soon as the form appears, not only when you press submit. It is loaded by the HubSpot form, as reCAPTCHA Enterprise.
What we use it for — Keeping machines from submitting the forms in bulk.
What the recipient uses it for — Google says that from 2 April 2026 we are the data controller for reCAPTCHA and Google acts as our processor, handling the data under the Google Cloud terms of service and the Cloud Data Processing Addendum (reCAPTCHA FAQ). It says the information collected is processed only as far as needed to provide, maintain and improve the service and for general security purposes, is not used for any other purpose, and is not used for personalised advertising by Google (Google Cloud).
What is sent — Your IP address, the type of browser, OS and device, and referrer information. Google also says it collects hardware and software information, such as device and application data (see the Google Cloud page above). Which signals the “risk analysis” uses, and the full list of them, is not published.
Cookies — Google says that when reCAPTCHA runs it sets a cookie it needs for that risk analysis (_GRECAPTCHA) (reCAPTCHA FAQ). On 17 October 2026, opening the ten pages that carry a form in a fresh browser profile — without submitting anything — we saw no such cookie stored.
How to stop it — We do not offer a setting for this. To stop it, block requests to google.com (including its subdomains) and www.gstatic.com, for example with a browser extension. The forms may then fail to submit, so please write to the address below instead.
The company’s terms — Google Cloud terms of service, Cloud Data Processing Addendum and the reCAPTCHA FAQ. From 2 April 2026 Google asks sites to drop their references to the Google Privacy Policy for reCAPTCHA, so this section does not cite it (it still applies to Google Fonts, Google Maps and YouTube below).
Google Tag Manager
Who receives it — Google LLC
Where it happens — Every page of this site, including the password-protected operating video library. It is sent as soon as the page opens.
What we use it for — Managing and loading Google Analytics 4 and Microsoft Clarity (below) in one place. Tag Manager does not itself measure how the site is used.
What the recipient uses it for — Google says it uses the information it collects to provide its services and to maintain and improve them (Google Privacy Policy).
What is sent — Your IP address, the type of browser, OS and device, and referrer information.
Cookies — On 17 October 2026, opening each page in a fresh browser profile and scrolling to the end, we saw no cookies set by Tag Manager itself (the services below do set cookies).
How to stop it — We do not offer a setting for this. To stop it, block requests to www.googletagmanager.com, for example with a browser extension. Google Analytics 4 and Microsoft Clarity below are then not loaded either.
The company’s privacy policy — Google Privacy Policy
Google Analytics 4
Who receives it — Google LLC
Where it happens — Every page of this site. It is loaded through Google Tag Manager and sent as soon as the page opens.
What we use it for — Seeing which pages are read and how much, to improve what we write and how the site is arranged.
What the recipient uses it for — Google says it uses the information it collects to provide its services and to maintain and improve them (Google Privacy Policy). We have not switched off GA4’s advertising features (Google signals). Google says information obtained through those features may be used to deliver ads and measure their effect. In the requests we actually observed, data is also sent to a domain Google uses for advertising (stats.g.doubleclick.net) — watching the requests does not tell us which setting causes that.
What is sent — An identifier stored in a cookie, your IP address, the type of browser, OS and device, referrer information, the pages you open and what you do on them.
Cookies — On 17 October 2026, opening each page in a fresh browser profile and scrolling to the end, we saw _ga and _ga_D3CQ4M9DZF set on this site’s own domain, and _gcl_au as well on the pages that carry a form (Google describes that cookie as one used by its advertising features). It may differ with your settings or if the company changes how the service works.
How to stop it — Use Google’s Google Analytics Opt-out Add-on. Disabling cookies stops the cookies but not the tag itself, so your IP address and the rest are still sent. To stop the requests, block www.googletagmanager.com, analytics.google.com and stats.g.doubleclick.net, for example with a browser extension. Ad personalisation can be changed in Google’s ad settings.
The company’s privacy policy — Google Privacy Policy
Microsoft Clarity
Who receives it — Microsoft Corporation
Where it happens — Every page of this site. It is loaded through Google Tag Manager and sent as soon as the page opens.
What we use it for — Seeing which parts of a page are read and where people get stuck, to improve the pages.
What the recipient uses it for — Microsoft says it uses the information it collects to provide, operate and improve its services (Microsoft Privacy Statement). Microsoft also states that personal data collected or received through Clarity is handled for the purposes of Microsoft Advertising, and requires site owners to disclose this to visitors (Clarity Terms of Use, 4.4(b)). In the requests we actually observed, data is also sent to a Microsoft advertising domain (c.bing.com), and an identifier (MUID) is stored on the bing.com domain.
What is sent — An identifier stored in a cookie, your IP address, the type of browser, OS and device, referrer information, and what you do on the screen (clicks, scrolling, mouse movement).
Cookies — On 17 October 2026, opening each page in a fresh browser profile and scrolling to the end, we saw _clck and _clsk set on this site’s own domain, and MUID, MR, SRM_B, CLID, ANONCHK and SM set on the clarity.ms and bing.com domains. It may differ with your settings or if the company changes how the service works.
How to stop it — Disabling cookies stops the cookies but not the tag itself (Microsoft says basic measurement continues without cookies). To stop the requests, block clarity.ms (including its subdomains) and c.bing.com, for example with a browser extension.
The company’s privacy policy — Microsoft Privacy Statement
HubSpot (recording what you view)
Who receives it — HubSpot, Inc.
Where it happens — Every page of this site. It is sent as soon as the page opens. This is separate from showing the forms above: it records what you view across the site. On pages without a form, a script that collects form input (hscollectedforms) is loaded as well.
What we use it for — Knowing which pages someone read before they wrote to us, so our reply fits what they were looking at.
What the recipient uses it for — HubSpot says it uses the data to provide the service to us and to run, improve and protect its own services (HubSpot Privacy Policy).
What is sent — An identifier stored in a cookie, your IP address, the type of browser, OS and device, referrer information, and the pages you open.
Cookies — On 17 October 2026, opening each page in a fresh browser profile and scrolling to the end, we saw hubspotutk, __hstc, __hssc and __hssrc set on this site’s own domain. It may differ with your settings or if the company changes how the service works.
How to stop it — Disabling cookies stops the cookies but not the tracking code itself, so your IP address and the rest are still sent. To stop the requests, block js-na2.hs-scripts.com, js-na2.hs-analytics.net, js-na2.hs-banner.com, js-na2.hscollectedforms.net, forms-na2.hscollectedforms.net and track-na2.hubspot.com, for example with a browser extension.
The company’s privacy policy — HubSpot Privacy Policy
Cloudflare (measuring page speed)
Who receives it — Cloudflare, Inc.
Where it happens — Every page of this site. The site is served from Cloudflare’s network, and Cloudflare automatically inserts a script that measures page speed (the script is served from static.cloudflareinsights.com; the measurements themselves are sent to this site’s own domain at /cdn-cgi/rum). It is sent twice: when the page has finished loading, and when you leave the page (as Cloudflare describes it).
What we use it for — Seeing how fast the pages are in the conditions our visitors actually browse in, so we can improve them.
What the recipient uses it for — Cloudflare describes this as something that helps you understand the performance of your web pages as experienced by your site visitors, and states that it does not collect or use your visitors’ personal data (About Cloudflare Web Analytics).
What is sent — Performance values taken from the browser’s Performance API, the page URL, referrer information, the type of browser, OS and device, and the IP address that any request carries. Cloudflare states that it does not log the query string (everything after ?) in the URL (Cloudflare Web Analytics FAQ).
Cookies — On 17 October 2026, opening each page in a fresh browser profile and scrolling to the end, we saw no cookies set by this feature. It may differ with your settings or if the company changes how the service works.
How to stop it — We do not offer a setting for this. To stop it, block requests to static.cloudflareinsights.com, for example with a browser extension. It does not affect how the site is displayed.
The company’s privacy policy — Cloudflare Privacy Policy
Google Maps
Who receives it — Google LLC
Where it happens — Company. The map is marked for lazy loading, so the request is made when your browser begins loading it — as the map comes near the screen, for instance.
What we use it for — Showing where our office is.
What the recipient uses it for — Google says it uses the data to show the map and to provide, maintain and improve its services (Google Privacy Policy).
What is sent — Your IP address, the type of browser, OS and device, and referrer information.
Cookies — On 17 October 2026, opening the Company page in a fresh browser profile and scrolling to the end, we saw no cookies stored for the map. It may differ with your settings, whether you are signed in to Google, or if the company changes how the service works.
How to stop it — We do not offer a setting for this. To stop it, block requests to www.google.com, maps.googleapis.com and maps.gstatic.com, for example with a browser extension. The address is also written out in text on the Company page.
The company’s privacy policy — Google Privacy Policy
YouTube (video)
Who receives it — Google LLC
Where it happens — The Japanese pages that carry a product video: the home page, Inspection Designer, the no-code inspection flow column and the operating video library. The English pages carry no YouTube embed. The thumbnail is marked for lazy loading, so the request to i.ytimg.com is made when your browser begins loading it — as it comes near the screen, for instance. The video itself is not loaded until you press play.
What we use it for — Showing a video that introduces the product.
What the recipient uses it for — Google says it uses the data to deliver the video and its thumbnail and to provide, maintain and improve its services (Google Privacy Policy).
What is sent — When the thumbnail loads: your IP address, the type of browser, OS and device, and referrer information. If you play the video: the above, plus information about your viewing.
Cookies — On 17 October 2026, opening the home page, Inspection Designer and the no-code inspection flow column in a fresh browser profile and scrolling to the end, we saw no cookies stored for the thumbnail (we did not test the operating video library, or playback). The video is loaded in privacy-enhanced mode (youtube-nocookie.com).
How to stop it — The video itself is not loaded unless you press play. To stop the thumbnail as well, block requests to i.ytimg.com, for example with a browser extension.
The company’s privacy policy — Google Privacy Policy
About analytics
On 17 October 2026 we added Google Analytics 4 and Microsoft Clarity, loaded through Google Tag Manager, and HubSpot’s tracking code directly on the site. Cloudflare, which serves this site, also inserts a script that measures page speed. They are described in the sections above.
We do not use a consent banner. Instead of asking for consent, this policy sets out who receives what, and each section says how to stop it.
The hosts and cookies above are what we measured on 17 October 2026 by watching the actual requests. What is listed under “What is sent” and “What the recipient uses it for” comes from each company’s published documents — we did not inspect the contents of the requests (their headers or bodies). The measurement was made under one set of conditions (a fresh Chrome profile, no extensions, no video played, not signed in to Google), so it may differ in another browser, while signed in to Google, or with tracking protection turned off. We did not measure inside the password-protected operating video library (the tags are loaded there the same way).
Changes to this policy
If the services we use are added to or changed, we will update this policy and say so here.
Who to contact
OUEN Co., Ltd., personal information enquiries
E-mail: [sales■ouenx.com] Please replace ■ with @.
Please also see our Privacy Policy for how we handle personal information, and our Information Security Policy for how we manage it.