IndustryQuery Privacy Policy
IndustryQuery does not sell user data, inquiry data or lookup data. Existing hosting, security and inquiry processing described below remain in place.
Version: 2026-10-02.1 / Effective date: 2026-10-02
This policy applies to anonymous private web inquiries and the IndustryQuery service.
1. Scope and privacy contact
The operator and privacy contact responsible for IndustryQuery is 이주성 (Lee Joo-Sung). This policy covers the Portal, DEM/DET tool and inquiry functions. Privacy questions, complaints and rights requests: 웹 Contact / Web Contact. The private Gmail destination is not published.
2. Anonymous private web inquiries
Without registration, we receive category, subject (up to 120 characters) and message (up to 5,000 characters) to review and answer inquiries. There are no name, email or phone input fields and these items are not separately collected. Do not enter names, email addresses, phone numbers or other personal information in your message. Personal information voluntarily entered into free text may become part of the stored inquiry.
Use your receipt number and secret lookup key to check replies on the site. The receipt is random and not derived from personal information. The secret is shown once on the receipt screen and cannot be recovered if lost. We do not automatically store it in localStorage/sessionStorage or place it in a URL. There is no public inquiry board. Web inquiry notifications and replies are not sent by email.
Cloudflare Workers stores in D1 an internal identifier, receipt, salted hash verification values, category, subject, body, status, administrator answer and received/updated/answered/expiry timestamps. The new inquiry schema does not store the plaintext key, name, email, phone, source page or language.
3. Retention and deletion
Web inquiry retention and deletion follow the criteria below.
Web inquiries expire 90 days after receipt. Expired records immediately become unavailable to user and administrator lookup; a daily Cron cleanup deletes the inquiry and answer together in the same row. Under normal execution, physical row deletion can therefore occur up to approximately 24 hours after expiry. Legacy Contact records are also cleaned up using 90 days from their original receipt timestamp. Replies or edits do not extend retention.
Application cleanup logs contain only deletion counts. The operator must review failures and rerun cleanup. D1 recovery history is separate from active-row deletion; Free Time Travel provides a seven-day recovery window. After restoration, expired records must be deleted before reopening the service. This implementation creates no separate raw inquiry export or backup. D1 recovery history
4. Direct email inquiries
Web inquiries, privacy complaints and rights requests use Web Contact. Carrier representatives may email [email protected] regarding data use or integration. Direct emails are forwarded through the existing free Cloudflare Email Routing service to the operator’s private Gmail inbox. The sender address, subject, message, attachments and metadata needed for delivery are used to review and answer inquiries. Web inquiries are not forwarded to Gmail. Existing Gmail messages, labels and filters remain unchanged; the private Gmail address is not published.
Direct email inquiries are retained for no more than 90 days from receipt and are regularly deleted manually by the operator. Received mail, sent replies, archived messages and controlled copies are deleted manually, permanently from Trash when necessary. Gmail automatic deletion, Apps Script deletion and permission expansion are not used. Rights requests about existing mail also use Web Contact with minimum necessary verification. Direct emails and existing holdings are processed in Google LLC’s Gmail under Google’s global privacy policy and deletion/recovery/legal-retention criteria. This does not describe a Google/Gmail delivery path for new web inquiries. Provider deletion/backup retention does not extend the operator's90-day policy. Google policy · Google retention
5. Bot protection and administrator access
Cloudflare Turnstile is used for submission, reply lookup and administrator login. The server verifies security results and checks that the domain and action match. Security tokens are not stored in the inquiry DB. The provider processes signals including IP address, User-Agent, TLS fingerprint, sitekey and associated origin. Cloudflare describes itself as a processor for site protection and a controller for improving bot detection. Turnstile privacy contact: [email protected]. Turnstile policy
Administrator authentication uses a Worker secret and Web Crypto HMAC-SHA-256 sessions, active for this service. Cloudflare Access/Zero Trust is not used. Login POST has server-side temporary lockout. The session cookie expires after 20 minutes and is Secure, HttpOnly and SameSite=Strict. State-changing administrator APIs check Origin and CSRF; logout revokes the server session. The administrator secret is held only in a Worker secret, never in DB, source, URL or logs.
D1 stores only a session identifier hash and creation/expiry times, plus global login attempt counts and lockout times. IP/email is not stored as a limiting identifier. Sessions become unusable after 20 minutes; lockout metadata becomes eligible for cleanup 30 minutes after the last attempt, and daily cleanup removes remaining expired metadata. The cookie is needed for administrator login and is not set for public visitors. Controls include same-origin checks, typed input, parameter binding, salted lookup verification, no-store and plain text rendering.
6. Providers and international processing
Cloudflare, Inc. and its published subprocessors provide Workers/Pages hosting, request processing and security; D1 inquiry storage and deletion; Turnstile bot protection; and Web Analytics performance measurement. Existing DEMDET Workers KV and Browser Run remain used for official-source retrieval and shared caches. New web inquiries are neither emailed nor linked to carrier lookups. Subprocessor privacy contacts are available through Cloudflare and Google privacy, Oracle privacy. Recipient contacts: [email protected] and [email protected].
Transferred items: inquiry category, subject, body, receipt, verification hash/salt, answer, status and timestamps; administrator session hashes and lockout times; IP/browser/connection metadata needed for requests, Turnstile signals, and section 8 performance metrics. Timing/method: Internet/HTTPS transmission, processing and storage on page visits, security verification, inquiry submission/lookup and administrator handling. Necessary entrusted processing/storage for hosting, security and performance of the inquiry service uses the privacy-policy disclosure route in PIPA Article28-8(1)(3)(a). Cloudflare's independent Turnstile-improvement processing follows the provider's separate role and grounds; the operator's entrustment ground is not applied to every independent purpose. Article28-8 · Decree31 · Turnstile roles
Countries are disclosed by the officially published processing layer. Cloudflare's Korean addendum lists the United States, United Kingdom, Singapore, Australia, Germany, Portugal, France, Japan, Canada, Netherlands, UAE, India, Mexico, Malaysia and Sweden for Cloudflare, Inc. and group recipients. The latest subprocessor list also includes a Swiss group entity. Developer Platform infrastructure subprocessors are Google LLC (EEA, United States, Australia, India) and Oracle America, Inc. (United States, EEA, UK, Japan, Australia, Canada, Singapore). This is not a consumer Gmail inquiry-delivery route. The EEA comprises the27 EU countries plus Iceland, Liechtenstein and Norway. The stated subprocessor scope does not mean every inquiry is stored in every infrastructure service. Unused AI Gateway, Workers AI, Zero Trust, Email Security or support tools are not added as inquiry services. Korean addendum · Subprocessors
The inquiry D1 jurisdiction is us, restricting the database's storage/execution to the United States. Read replication is disabled. APAC is not described as a country. This setting does not restrict worldwide Workers/Pages request processing to the US. Cloudflare describes network/security metadata processing in the US and Europe and global edge processing. Its published global-edge country/territory scope, checked 2026-10-01, is: United Arab Emirates (AE), Albania (AL), Armenia (AM), Angola (AO), Argentina (AR), Austria (AT), Australia (AU), Azerbaijan (AZ), Barbados (BB), Bangladesh (BD), Belgium (BE), Burkina Faso (BF), Bulgaria (BG), Bahrain (BH), Brunei (BN), Bolivia (BO), Brazil (BR), Bhutan (BT), Botswana (BW), Belarus (BY), Canada (CA), Congo - Kinshasa (CD), Switzerland (CH), Côte d’Ivoire (CI), Chile (CL), Cameroon (CM), Colombia (CO), Costa Rica (CR), Cyprus (CY), Czechia (CZ), Germany (DE), Djibouti (DJ), Denmark (DK), Dominican Republic (DO), Algeria (DZ), Ecuador (EC), Estonia (EE), Egypt (EG), Spain (ES), Ethiopia (ET), Finland (FI), Fiji (FJ), France (FR), United Kingdom (GB), Grenada (GD), Georgia (GE), Ghana (GH), Greece (GR), Guatemala (GT), Guam (GU), Guyana (GY), Hong Kong SAR China (HK), Honduras (HN), Croatia (HR), Hungary (HU), Indonesia (ID), Ireland (IE), Israel (IL), India (IN), Iraq (IQ), Iceland (IS), Italy (IT), Jamaica (JM), Jordan (JO), Japan (JP), Kenya (KE), Kyrgyzstan (KG), Cambodia (KH), South Korea (KR), Kuwait (KW), Kazakhstan (KZ), Laos (LA), Lebanon (LB), Sri Lanka (LK), Lithuania (LT), Luxembourg (LU), Latvia (LV), Moldova (MD), Madagascar (MG), North Macedonia (MK), Mongolia (MN), Macao SAR China (MO), Mauritius (MU), Maldives (MV), Mexico (MX), Malaysia (MY), Mozambique (MZ), Namibia (NA), New Caledonia (NC), Nigeria (NG), Netherlands (NL), Norway (NO), Nepal (NP), New Zealand (NZ), Oman (OM), Panama (PA), Peru (PE), French Polynesia (PF), Philippines (PH), Pakistan (PK), Poland (PL), Puerto Rico (PR), Palestinian Territories (PS), Portugal (PT), Paraguay (PY), Qatar (QA), Réunion (RE), Romania (RO), Serbia (RS), Russia (RU), Rwanda (RW), Saudi Arabia (SA), Sweden (SE), Singapore (SG), Slovenia (SI), Slovakia (SK), Senegal (SN), Suriname (SR), Thailand (TH), Tajikistan (TJ), Tunisia (TN), Türkiye (TR), Trinidad & Tobago (TT), Taiwan (TW), Tanzania (TZ), Ukraine (UA), Uganda (UG), United States (US), Vietnam (VN), South Africa (ZA), Zambia (ZM), Zimbabwe (ZW).
This is the published network's potential edge scope, not the physical server location of each visit/inquiry or a claim that every record is sent to every country. It is separate from the US restriction for D1 storage/execution. This notice is updated when the published country/subprocessor scope changes. Official network countries/territories · PIPA metadata explanation · D1 location
Retention: active inquiries follow section 3's90-day expiry/daily cleanup; D1 Free recovery history has a7-day window; administrator sessions expire after 20 minutes and lockout metadata becomes eligible for deletion after 30 minutes. Section8 covers Web Analytics'7-day unsampled data and preceding6-month query window. Entrusted data follows DPA return/deletion on contract/service completion and legal exceptions. Independently processed security signals follow the provider's published purpose-necessity/legal-retention criteria; no unpublished fixed number of days is invented. DPA · Provider retention
Refusal and effects: not submitting an inquiry avoids international storage of its contents and use of the inquiry/reply service. Use section 9's web channel to request deletion or processing restriction of received records. Declining inquiries does not block provider security processing accompanying page access; users who do not want that processing may stop visiting the site. This policy is not described as a separate consent screen or legal-compliance certification.
EEA countries in the subprocessor scope: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Iceland, Liechtenstein, Norway. South Korea in the global-network list denotes domestic processing. The separately subscribed Enterprise China Network is not used and is excluded from that list. Direct emails pass through the existing Email Routing/MX delivery, routing and security service to the private Gmail inbox. Web inquiries use Web Contact separately and are not forwarded to Gmail. Such Cloudflare processing follows the above official country scope, contacts and purpose-based retention criteria. China Network availability
7. Language preference and lookup storage
The industryquery_language cookie stores only en/ko/ja/zh-CN/zh-TW/es/vi/id/pt-BR/th/de/fr to retain language choice: Domain=.industryquery.com, Path=/, Secure, SameSite=Lax and Max-Age=31,536,000 seconds (365 days). Browser language helps determine the initial language. pages.dev/local environments use industryquery.language.pages_fallback localStorage without a separate expiry.
DEM/DET stores lookup conditions/results in the tab's sessionStorage demdet.lookup.snapshot to restore on reload/BFCache return. The server processes tariff lookup conditions, official sources and shared caches. Inquiry content and direct email are not linked to tariff lookup. Browser settings can delete or block cookies/site storage, affecting language persistence and result restoration. Inquiry secrets are excluded from these storage functions.
8. Analytics and logs
As of 2026-10-01, industryquery.com uses Cloudflare Web Analytics with real-user performance measurement and automatic script injection enabled, including EU visitors. Recent measurement records were present. Free automatic injection covers the zone's subdomains/pages. Missing Pages build tags/tokens or an absent beacon in sampled HTML do not establish disabled analytics. This zone setting is not assumed to cover pages.dev/separate workers.dev staging; no separate analytics tag was observed in directly related staging source/samples.
Web Analytics measures performance timing/Core Web Vitals with country, host/path, referrer, device/browser/OS dimensions. Official documentation describes no cookie/localStorage-based individual tracking, no cross-site tracking and no query-string logging. Its beacon loads from static.cloudflareinsights.com; proxied sites report through HTTPS POST to their domain's /cdn-cgi/rum. Unsampled beacon data is retained for seven days before sampling; metrics can be accessed for the preceding six months. These are not guaranteed deletion dates for all related data. Tracking policy · Collection · Dimensions · FAQ · Free rules
All four Contact/DEMDET Workers in the production and development environments have Logs/Traces/Issues disabled and no export destinations. API Logpush is false with no tail consumers; domain Logpush is unsubscribed. These settings remain in place. New inquiry application console output contains only deletion counts, not titles, bodies, answers, secrets or cookies. Cloudflare connection/security metadata and edge analytics are separate provider processing; this does not establish that IP addresses are never processed. Metadata countries use section 6’s published provider scope; retention follows the published provider criteria in section 6, without inventing a fixed service-specific period. The general Free three-day Workers Logs period is not presented as retention for these disabled logs. Workers Logs · Metadata regions
9. Rights and changes
Data subjects and legal representatives may request access, correction/deletion, processing restriction and applicable withdrawal through Web Contact under applicable law. For anonymous inquiries, provide the receipt number without submitting the secret or unnecessary personal information. Necessary verification should use the protected lookup flow and minimum information; explain any applicable legal restriction. A lost key can make it impossible to establish the relationship between an anonymous record and a requester or to restore/provide it. This does not require a blanket waiver of legal rights.
Effective 2026-10-01. Changes to processing or this policy will be announced on this site.