Privacy Policy
Effective date: 2026-10-14
Operator: Digital Loss Adjusters Co., Ltd., 2F, 158-1, Anam-ro, Dongdaemun-gu, Seoul 02473, Republic of Korea
Privacy protection officer: Younghyun Kim
Contact: hello@recogauge.com
1. Scope and purposes
RecoGauge checks publicly accessible pages for observable signals related to discoverability, clarity, structured data, presentation and trust. We process submitted URLs and public-page data to return a check, technical data to operate and protect the service, and inquiry data to respond to service questions and privacy requests. The current application does not require a user account, login or payment details.
The items below are processed without asking for consent. Their purposes and legal bases are:
| Items | Purpose | Legal basis |
|---|---|---|
| Ordinary personal information publicly displayed on a checked page (for example author, publisher or person names, site contact details, social profile host names, quoted title, description or Open Graph values, and page URLs; in a YouTube check, the public title, description, channel name and handle returned by the YouTube Data API) | Checking page structure, readiness and the consistency of author/publisher information | Article 15(1)(6) of the Personal Information Protection Act, within the limits in section 2 |
| Sensitive information or unique identifiers (Articles 23 and 24), for example on medical, private or government-ID pages | Outside the service's purpose; we do not intend to process it | No Article 23 or 24 basis is relied on. Such pages are excluded from the service's purpose; if we become aware of such information in anything we hold, we do not use it and delete it without delay |
| The URL you submit and the selected language | Performing the check you request | Article 15(1)(4) |
| IP address and the request/response metadata needed to serve a request | Security, protection against abuse of resources and fault diagnosis; not used for tracking or for decisions about individuals, and this basis does not cover a provider's own purposes | Article 15(1)(6) |
| Page-view and feature-usage statistics (section 7) | Understanding overall visits and feature use to operate and improve the service; not used to identify or follow individual visitors | Article 15(1)(6) |
| Inquiries about the service contract or steps you request before one | Answering the inquiry | Article 15(1)(4) |
| Other general inquiries | Giving the minimal reply you can expect | Article 15(1)(6) |
| Requests to exercise statutory rights (Articles 35 to 38) | Handling the request as the law requires | Article 15(1)(2) |
| Minimal follow-up records after a case is completed (up to 90 days, deleted earlier when no longer needed; original messages, attachments and identity-verification material are not kept by default) | Handling follow-up questions or objections about the completed case | Article 15(1)(6) |
2. Submitted and temporarily processed information
A check sends the entered URL, including its path and query, and the selected language to the scanning service. A check makes at most 20 HTTP GET requests in total to the target page and the resources below, counting every redirect hop; the service's internal Worker/Container traffic and DNS lookups (section 5) are not part of this count. It retrieves the page, then /robots.txt and /llms.txt from the site the page ends up on after redirects, and one sitemap: the sitemap address declared in that robots.txt, which can be on another host, or /sitemap.xml when none is declared. Each of these four retrievals follows up to five redirects, which can also lead to other hosts, and all of them share the check's limit of 20 requests and 20 seconds. Every address is checked against the same public-address rules before it is contacted. These requests use a fixed RecoGauge User-Agent and send no cookies or Authorization headers. Public pages may contain personal information about third parties. Public availability alone is not the basis. For ordinary personal information displayed on a public page, such as author or publisher names and contact details shown for the site, we rely on Article 15(1)(6) (legitimate interest). We use it only as far as needed to check page structure, readiness and the consistency of author/publisher information, in the public context in which it was displayed, and we minimise what is passed back in the result (see below). The service is not intended for pages containing sensitive information (for example about health, political views or sex life) or unique identifiers (for example resident registration numbers), such as medical, private or government-ID pages; please do not submit them. We do not use such information for any purpose and rely on no basis under Articles 23 or 24. We cannot technically stop such a page from being retrieved, because the full page is fetched through Cloudflare before any reduction, and filtering afterwards does not undo that retrieval. If we become aware of such information in anything we hold, we delete it without delay.
The full retrieved page (decoded body up to 2 MiB), including any third-party personal information it contains, is held in Cloudflare Container and Worker memory during the request, before results are reduced. That infrastructure may be located outside South Korea (section 9). Reducing the content afterwards does not avoid that initial processing. The target site's response headers, such as its cookies, are also held in memory but are not returned to you.
The result returned to your browser can contain values taken from the page that may be personal information:
- author, person, publisher or site names quoted as evidence;
- the host names of linked social profiles;
- visible-text word and character counts, without a raw text sample;
- the final URL and redirect URLs, including their query;
- product names, prices, dates and figures.
Fix examples use placeholders such as YOUR_NAME, YOUR_AUTHOR_NAME, YOUR_PHONE_NUMBER, YOUR_CONTACT_EMAIL and YOUR_OFFICIAL_SOCIAL_PROFILE_URL, and YOUR_PAGE_SUMMARY for description examples instead of the page's personal contact or profile values; the organisation name, logo and site URL are kept. Email addresses, phone numbers and postal addresses found in visible text are used only to note that they are present. The page title, author, meta description and Open Graph tag values are used during the check and are not returned as separate fields, but they can appear where a rule quotes them as evidence.
The application stores no copy of scan results on the server and keeps no long-term database of scanned HTML or page text. The application does not intentionally keep this data after the request ends. When the memory is actually freed by the runtime (memory management and garbage collection) has not been verified, there is no separate wipe step, and we do not claim immediate secure physical erasure. Cloudflare's own platform processing is outside the application's control. Infrastructure logs, browser records and inquiry messages are separate. Do not submit private links, credentials, tokens or URLs containing confidential personal information.
Channel checks also use public subscriber, view and video counts, and up to 20 recent public uploads. Thumbnail previews load the original image directly from Google’s i.ytimg.com in your browser, which sends normal network information such as your IP address. Suggested text is overlaid in the browser; the original image is not edited or saved.
YouTube link checks do not retrieve a web page. The server takes only the video or channel ID or handle from the entered address and looks it up over HTTPS in the YouTube Data API of Google LLC (section 9); that request carries no visitor IP address or cookies. The public details returned (such as title, description, tags, channel name and handle, visibility and whether captions exist) are kept for at most 30 minutes in the Cloudflare data-centre cache and memory so that the same check, the other language and the suggestions can reuse them, and they are not saved in the browser check history (section 3); the last check shown on screen may be kept in this browser as described in section 3. After a successful video check, the video's public title, description (first 1,500 characters), tags and channel name are automatically sent to Cloudflare Workers AI to write suggestions; the suggestions are kept the same way for at most 30 minutes.
RecoGauge's YouTube check uses YouTube API Services. See the YouTube Terms of Service and the Google Privacy Policy.
3. Browser storage
localStorage key rg.history.v1 may contain scan time (t), checked URL (url, including path/query), ruleset version (rv), overall score (score), area-score ratios (areas), scored-rule statuses (rules), page type (ct: website/article/product), and up to three leading improvement-group identifiers (top, each up to 60 characters). It does not contain full HTML, page text or full improvement explanations.
The application keeps at most ten records per URL and thirty recently checked URLs. It trims older records/URLs against a target stored JSON length of 150,000 character units, not an exact byte limit. There is no time-based history expiry. Records otherwise remain until history controls, browser settings or browser storage/lifecycle policies remove them.
Animation preference rg.motion.paused is stored separately as 1 or 0. Clearing check history removes rg.history.v1, not this preference; clear RecoGauge site data to remove both.
An EN/KR switch may temporarily put the current check result, in both languages, in sessionStorage key rg.carry. It holds the same values shown on screen (section 2), including the checked URL. The destination page reads and removes it and shows the same check in that language; no new check is made. For a YouTube check it also carries the title and thumbnail suggestions already received and which three are shown, and whether the YouTube check consent box was ticked. An unread value follows the browser's tab/session lifetime. These browser records are not synchronised to an operator user account or application database. A submission/recheck separately sends the URL to the service.
localStorage key rg.last.v1 keeps the last completed check of each tab (Website and YouTube) so that it can be shown again after a reload or a later visit in the same browser; no new check is made. It holds the same values shown on screen (section 2), in both languages, including the checked URL and any comparison result, and for a YouTube check the title and thumbnail suggestions already received and how many were shown; it does not hold the YouTube check consent tick. A new check of a tab replaces that tab's record. A record is no longer shown 30 days after its check and is deleted the next time a RecoGauge page is opened; clear RecoGauge site data to remove it sooner.
4. Technical data and logs
Cloudflare provides delivery, runtime and network services and may process IP address, browser/User-Agent, request time/method/URL, response status, approximate location and other network/security metadata. RecoGauge uses the IP supplied by Cloudflare as a rate-limit key (section 6). It does not intentionally write that visitor IP into its own application database or structured application log.
Structured application logs of the official public service contain only fixed fields: event type, API route (normalised to a fixed set of routes), status, outcome, duration, an edge-cache marker where applicable and an error category from a fixed list. A summary line is also written for normal successful requests to monitor latency and outcomes. These logs exclude the checked hostname, full URL path/query, page HTML or body, tokens, cookies, Authorization and other headers, visitor IP, request IDs, free-form error names and unknown request paths.
The Preview environment currently runs an earlier build. Its application logs may also contain a request ID, the checked hostname, the requested API path and free-form error names; they likewise exclude the full checked URL path/query, page body, cookies, Authorization values and visitor IP. A hostname can identify a person and is not automatically non-personal information. Not every log is therefore limited to the fixed fields above.
Platform invocation logs are disabled in the official public service configuration. Container logs are separate and can contain operational metadata. Application-log minimisation does not mean that every Cloudflare record excludes the same fields. Enabled Workers Logs have a standard retention period of up to seven days. Container logs inherit Worker observability by default and the documented standard retention is seven days. This period does not cover inquiry email, rate-limit counters, Cloudflare's own security records, public-resolver records or separate exports. Quotas, sampling, provider conditions and availability can affect collection; configured sampling does not guarantee a complete record of all activity. Provider expiry/eviction is not a promise of immediate secure erasure.
5. DNS and target-site networking
Production configuration sends scan retrievals from the Worker through a Durable Object to a Cloudflare Container using the Node fetcher. It uses system DNS lookup and validates returned addresses inside the connection lookup hook. The application does not explicitly call cloudflare-dns.com on that path, and the public-resolver description below does not apply to it. That resolution happens inside the Cloudflare Container environment covered by section 9; the resolver's location and retention are not established.
A Preview using the Worker fetcher explicitly makes server-side hostname and A/AAAA DNS queries over HTTPS to cloudflare-dns.com/dns-query. It does not add visitor IP, original URL path/query or page content to those query parameters. The resolver still receives the server request and network metadata. This is target/resource DNS resolution, not collection of all DNS activity on your device. The in-memory answer cache is capped at ten seconds and 256 hostnames.
Cloudflare's Public DNS Resolver documentation describes limited resolver logs deleted within 25 hours, with separate limited-sample and aggregate handling; some aggregates may be retained indefinitely. APNIC has limited access to anonymised resolver data. These statements apply to that documented public resolver only.
6. Sample cache and abuse prevention
The fictional Sample report is cached per language and ruleset for 600 seconds in the data-centre Cache API and per-isolate memory. This code does not replicate cache contents between data centres. The browser response uses Cache-Control: no-store. This is not a shared cache of a visitor's submitted website check or an account history.
Production is configured for separate limits of thirty Sample requests per sixty seconds and ten scan requests per sixty seconds, per client IP/API route. These limits use Cloudflare's rate-limiting service, which keeps counters keyed by client IP and route cached on the serving machine with an asynchronous backing store at that location. Sixty seconds is the counting window, not a deletion period; Cloudflare's public documentation does not state how long these counters are kept. In Preview, a limiter in the serving instance's memory is used instead; its entries are removed only when accessed again, when capacity is exceeded or when the instance ends. Cloudflare limits are best-effort and approximate per location, not exact global quotas or a guarantee against abuse. Required missing Production bindings cause an unavailable response, not permissive fallback.
7. Usage statistics
Since 2026-10-11 RecoGauge measures overall use of the site, not individual visitors. Neither measurement below sets cookies or assigns an identifier to a visitor or a browser. The only browser storage used for measurement is the current visit's record in one browser tab, described below.
- Page views (Cloudflare Web Analytics): on the EN/KR home, YouTube and policy pages the browser loads Cloudflare's Web Analytics script, which reports one page load: the page address without its query, the referring site, browser and device details, page-load timings and a random identifier for that page load only. Cloudflare processes the connection's IP address and approximate location to do this. The script loads only when the address has no query other than
utm_*campaign tags and the click IDs that ad platforms add to an ad's address (such asgclidorgad_source), and the referrer is empty, a site's home address, an app's name or one of these pages; other page views are not measured. RecoGauge sees only aggregate reports, such as counts by page, referring site, country and device. Cloudflare's documentation describes keeping full data for a short period and a sampled subset after that; the total retention period is not established by those materials. - Feature counters (
/api/events): the page sends a small event when a visit begins, a website or YouTube check starts, succeeds or fails, a result, the fixes or a title or thumbnail idea is copied, title and thumbnail ideas are generated, a recheck or comparison is used, or the Sample is opened. An event contains only the event name, the page language, the page type (website/article/product), the kind of YouTube address (video/channel), which line of an idea was copied (title/thumbnail), a coarse failure category and what started the check, plus the visit it belongs to: how the visit arrived (ad, campaign link, search engine, YouTube, another site, this site or direct), whether this browser held a last check result (rg.last.v1, section 3) when the visit began (new or returning), and theutm_source,utm_medium,utm_campaignandutm_contenttags of the link that opened it. It contains no URL, domain, page content, ad click ID, referrer address, IP address or identifier. So that a reload or a language switch is not counted as another visit,sessionStoragekeyrg.visit.v1keeps these visit values for that browser tab only; it holds no identifier and follows the tab's session lifetime. Cloudflare Workers Analytics Engine keeps these counters for three months. The client IP is used only in memory as the key of this endpoint's abuse limit and is not written to the counters.
Blocking the script or these requests, for example with a content blocker, does not affect any feature.
8. Inquiry email
Send service questions or privacy requests to hello@recogauge.com. Cloudflare Email Routing forwards messages to the designated Google (Gmail) mailbox. Inquiry data may include sender/recipient, name if supplied, subject, headers, body and attachments. Avoid sending secrets or unnecessary sensitive information.
Cloudflare describes Email Routing as forwarding without storing message content. Routing event information (sender and recipient, subject, message and session IDs, and processing information) has a documented 31-day retention. That is not the retention period of the delivered mailbox message. Email Sending preview and custom Email Worker storage are not established features of this service.
After an inquiry or rights request is completed, we keep only the minimum record needed, for no longer than 90 days, and delete it earlier when it is no longer needed. Original messages and attachments are kept within that period only where they are still needed; we do not keep everything for the full 90 days. Identity-verification material is deleted as soon as it is no longer needed. This period is separate from the seven-day logs in section 4.
9. International transfer of information
RecoGauge uses Cloudflare for website delivery, security, scan execution, logs and Email Routing, and a personal Google Gmail mailbox for inquiries. Current Preview scans use a Worker and Cloudflare’s public DNS-over-HTTPS resolver; YouTube checks also use Google’s YouTube Data API and Cloudflare Workers AI. The official public service uses Worker, Durable Object and Container execution and the Container’s system DNS resolver.
The basis for collecting and using personal information is distinct from the basis for international transfers. Legitimate interests under Article 15 of South Korea’s Personal Information Protection Act (PIPA), or the existence of a provider DPA, do not by themselves satisfy Article 28-8. Confirmed facts and unresolved scope are distinguished below.
Cloudflare, Inc.
| Recipient and contact | Cloudflare, Inc. |
|---|---|
| Purpose | Website delivery, scan execution and target DNS resolution, security, abuse prevention and rate limiting, operational logs, aggregate usage statistics (section 7), and forwarding inquiry emails; also writing YouTube title and thumbnail suggestions (Workers AI). |
| Information transferred or processed | IP address and browser, request and network metadata; submitted URLs; public pages and resources required for scans (which may contain third-party personal information); operational and security information; and the page-view and feature-counter data described in section 7. Preview public DNS queries use target/resource hostnames and DNS-query/network information. Email Routing uses sender/recipient addresses, subject/headers, body/attachments, and event metadata such as delivery, authentication and processing status. YouTube checks use the public video/channel details returned by the YouTube Data API (cached for up to 30 minutes) and, when suggestions are requested, the video’s public title, description, tags and channel name. |
| Timing and method | Information is processed electronically over the network on site access and each scan request. Preview target DNS queries use server-side HTTPS. Inquiry emails are forwarded via SMTP and routing events are processed on receipt. |
| Confirmed country information and limitations | Section 3 of Cloudflare’s South Korea privacy addendum lists the United States, United Kingdom, Singapore, Australia, Germany, Portugal, France, Japan, Canada, Netherlands, UAE, India, Mexico, Malaysia and Sweden as recipient countries for Cloudflare, Inc. and its subsidiaries. This is the addendum’s common recipient-country list; it is not presented as a confirmed complete list of processing countries for each RecoGauge execution, DNS, logging or Email Routing operation. Without data-localization options, logs may be processed in Cloudflare’s core data centers globally; RecoGauge does not use those options. Requests are generally handled by a Worker in a Cloudflare data center close to the visitor, and Cloudflare’s Containers documentation states that a scan container starts in the nearest location with a prepared image, which can be in a different country from the Worker or the visitor; RecoGauge does not restrict these locations. The complete country scope applicable to each flow is not established by the current materials. |
| Retention and use period |
|
| International-transfer basis and scope | PIPA Article 28-8(1)(3)(a) can apply where entrusted processing or storage is necessary to enter into or perform a service contract with the data subject and the required transfer details are published in the privacy policy. Because the required disclosures, including countries, remain incomplete, satisfaction of those conditions is not marked as established. This basis is not applied across the board to other people’s information on scanned pages or to inquiries unnecessary for contract performance. The separate transfer basis applicable to that information is currently unresolved. |
| Refusal, procedure and consequences | Not accessing the site avoids processing associated with site delivery; not requesting a scan avoids scan processing and target DNS queries; not sending an email avoids Email Routing. The corresponding site, scan or email-inquiry function cannot then be used. For information already processed, send access, deletion or processing-suspension requests to hello@recogauge.com under section 12. Refusal does not retroactively cancel a transfer or immediately erase every copy. |
| Official materials | Cloudflare Privacy Policy · South Korea privacy addendum · Customer DPA |
Google LLC (Gmail, YouTube Data API)
| Recipient and contact | Google LLC (personal Gmail mailbox service provider; YouTube Data API provider for YouTube checks) |
|---|---|
| Purpose | Receiving, storing and replying to inquiry and rights-request emails, and mailbox security and operation. Looking up the public details of a video or channel through the YouTube Data API for a YouTube check. |
| Information transferred or processed | Sender/recipient addresses, name if provided, subject/headers, body/attachments, and related account/service metadata. Scanned page content is not automatically copied into the inquiry mailbox. For a YouTube check: the video or channel ID or handle taken from the entered address (a server request without visitor IP address or cookies). |
| Timing and method | An email sent to hello@recogauge.com is received and stored when Cloudflare Email Routing delivers it over the network to the operator’s Gmail mailbox. Information is also processed during replies and mailbox operation. A YouTube check is looked up from the server over HTTPS when you request the check. |
| Confirmed country information and limitations | Google’s Privacy Policy describes processing on servers worldwide, potentially outside the user’s country of residence. It does not establish the country-name scope applicable to the current personal Gmail mailbox. Google LLC’s United States address is not used to claim United States-only processing, and Google Workspace’s United States/Europe data-region guarantees are not applied to personal Gmail. The processing locations of the YouTube Data API are not established by these materials either. |
| Retention and use period | The operator keeps inquiry/rights records for up to 90 days after handling is complete, deleting unnecessary originals and attachments earlier. Longer retention applies only where a specific legal retention obligation actually exists, within its required period and scope. Google describes system deletion as generally taking around two months, with encrypted backups potentially retaining data for up to six months, subject to exceptions and delays. The operator’s 90-day period does not guarantee simultaneous deletion of every Google system copy. |
| International-transfer basis and scope | PIPA Article 28-8(1)(3)(a) can apply where entrusted processing or storage is necessary to enter into or perform a contract with the data subject and the required transfer details are published. Because disclosures including the personal Gmail country scope remain incomplete, satisfaction of those conditions is not marked as established. General inquiries and rights requests are not all presumed necessary for contract performance, and an Article 15 processing basis does not replace a separate transfer basis. The transfer basis for information unnecessary for contract performance remains unresolved. The YouTube Data API lookup is treated the same way, and satisfaction of those conditions is not marked as established for it either. |
| Refusal, procedure and consequences | Not sending an email avoids transfer to the mailbox, but an email inquiry cannot then be received or answered. Send rights requests concerning information already processed to hello@recogauge.com under section 12. Such a request also passes through the same email routing and mailbox processing. You can also contact the recipient’s privacy inquiry address. Not checking a YouTube address avoids the YouTube Data API lookup. |
| Official materials |
10. Retention and deletion
Browser history/preferences have no time-based expiry, except the last check (rg.last.v1, 30 days after the check); use the controls and site-data settings in section 3. A language-switch URL is removed when read, otherwise governed by browser session handling. Scanned page processing is temporary runtime processing, not a verified immediate secure-wipe procedure. The fictional Sample cache has a configured 600-second lifetime. YouTube API details and suggestions are cached for at most 30 minutes. Workers/Container logs and Routing events follow the separate periods above.
When personal information we hold is no longer needed because its retention period has ended or its purpose has been achieved, we destroy it without delay unless another law requires retention. Inquiry and rights records are kept for no longer than 90 days after completion, as described in section 8. When they are deleted, we permanently delete the relevant messages from the mailbox, including its trash, remove copies we downloaded or saved, and keep only a minimal deletion record (date, type, count and result). We keep information beyond that period only where a law actually requires it, with the legal basis, period and minimum scope recorded and the information kept separately; a mere possibility of a dispute is not a reason to keep it. Deleted mailbox data may remain in Google's systems for the provider periods shown in section 9; we do not promise immediate irrecoverability of every provider copy.
11. Protection and limits
Code-level measures include public-address/port checks, redirect/size/timeout controls, connection-time address validation in Container mode, independent best-effort rate limits, minimised custom logs and browser security headers. Service access should use HTTPS. Retrieval of a permitted HTTP target is not TLS-encrypted merely because your access to RecoGauge uses HTTPS.
No Internet service guarantees absolute security or prevention of every DNS/network attack. A real DNS-rebinding attack has not been demonstrated in the technical verification and remains a residual risk. Administrative and mailbox access controls are operational measures; source code alone does not prove their maturity.
12. Your rights and requests
Send access, correction, deletion, processing-suspension or consent-withdrawal requests to hello@recogauge.com, identifying the relevant information, requested action and reply contact. A legal representative or authorised agent may also request. We ask only for the minimum information needed to verify identity or authority, and delete verification material once it is no longer needed; do not send unrelated sensitive documents merely to make a request.
We handle requests under the Personal Information Protection Act:
- Access: provided within ten days of receipt. Where access is lawfully postponed, restricted or refused, we notify you of the reasons and how to object within the same period.
- Correction/deletion: the action taken, or a legally permitted refusal with reasons and how to object, is notified within ten days of receipt.
- Processing suspension: the result, or the reasons for a lawful refusal and how to object, is notified within ten days of receipt.
- Consent withdrawal: where processing relies on consent, handled without delay.
These are calendar days, not business days.
The operator cannot remotely delete browser-only history/preferences; we provide history and browser-site-data deletion instructions. That does not waive rights concerning other information. Expired or unavailable records cannot be promised recoverable.
For personal information collected from a source other than you, we provide the collection source, processing purpose and information on your right to request processing suspension immediately upon request where required by law, subject to lawful exceptions.
For independent assistance:
- KISA Personal Information Infringement Report Center: 118, https://privacy.kisa.or.kr/
- Personal Information Dispute Mediation Committee: 1833-6972, https://www.kopico.go.kr/
These channels do not replace the operator's request handling or other legally available remedies.
13. Responsibility and updates
Privacy protection officer: Younghyun Kim. Contact: hello@recogauge.com. Operator: Digital Loss Adjusters Co., Ltd., 2F, 158-1, Anam-ro, Dongdaemun-gu, Seoul 02473, Republic of Korea.
We update this policy to reflect changes in practices or applicable requirements and show the effective date. Required notice or consent for changes follows applicable law. EN/KR Privacy, Terms and Contact use the same operator, contact and effective-date values.
The YouTube link check provisions (sections 1–3, 9 and 10) apply to the public service from 2026-10-12.