1. When you read the dictionary
You can read NoCapWiki without creating an account. To deliver a page or search result, our hosting infrastructure processes technical request information such as your IP address, browser headers, requested URL and request time. We use this information to serve the site and diagnose security or availability problems.
The current application does not create visitor accounts or record page views or search queries in its dictionary tables. API Gateway access logging is not enabled. The application's AWS CloudWatch log group is set to delete its operational logs after seven days; those logs may contain technical error details.
2. When you contact us
If you email HOBOS, we process your email address, message and any information or attachments you choose to send so we can respond to privacy, content-correction or rights requests. Please do not send sensitive personal information unless it is necessary for your request.
We keep inquiry correspondence for one year after the request is resolved, then delete it, unless a longer period is required by law or needed for an active dispute.
3. Guest contributions and reports
Guest definitions, correction suggestions and issue reports are open without an account. Submitting is optional and is not required to read the dictionary. We do not ask guests for a name, email address or Google sign-in.
For a definition or correction, we process the Korean headword, English summary and explanation, example, translation, context and optional source URL you provide, your permission to publish, the target entry, receipt identifier and processing times. For a report, we process the target entry or definition, reason, details, receipt identifier and processing times. Do not include private personal information, confidential messages or source links containing access tokens.
We use these records to check safety, language, accuracy and rights, review or publish contributions, handle reports and prevent abuse. Definitions and corrections are sent to OpenAI for automated checks; report text is not. We retain the assessment and any editorial review snapshots with the private receipt. Every contribution currently requires an editor’s approval before publication. Reports do not automatically remove content. See the provider details below.
A published guest definition is labeled Guest contributor, without a profile link. We do not create a guest account or persistent guest identifier and do not automatically link a guest contribution to an account created later. Keep your submission reference for follow-up; we may need other evidence to verify a request concerning a guest submission.
Original submissions and reports, AI assessments and linked private review snapshots are retained for 90 days after resolution or the latest linked review snapshot, whichever is later. Unresolved submissions and reports are retained for 180 days after receipt. A necessary legal-dispute, rights-request or correction-review hold has a recorded reason and review date; a hold is reviewed by HOBOS and does not expire automatically.
A separate application worker checks eligible private records daily at 03:00 Korea Standard Time. Failed or uncertain runs and overdue holds are flagged to HOBOS for follow-up; an outage or hold can delay deletion. Cleanup audit records contain receipt identifiers, timestamps, counts and digests, not submission text or AI assessments. They are stored privately in AWS S3 with a 90-day expiration rule; lifecycle deletion is asynchronous. Operational logs expire after seven days. Provider backups and security logs are not instantly erased by this job.
Published dictionary articles and community definitions are separate from private receipts and remain available while we provide the service; cleanup unlinks a published definition from its deleted receipt, but does not delete the definition. Corrections and valid privacy or rights requests are handled separately and can require earlier removal. Inquiry emails follow the separate one-year period above. Public accounts and voting are not open; we will publish their actual retention and closure process before enabling them.
4. Service providers
Amazon Web Services (AWS) delivers the website and API and holds operational logs. The application server and dictionary database are configured in Seoul, Republic of Korea, with Supabase hosting the database. Public scripts, styles and fonts are stored in Amazon S3 and delivered through AWS CloudFront's global edge network, which may process technical delivery information outside Korea. CloudFront access logging is not enabled. Your browser does not connect directly to Supabase for dictionary pages.
Emails sent to our support address are routed through Cloudflare Email Routing and received in a Google Gmail mailbox. These providers process the information needed to deliver their services and may process it outside Korea. We do not sell your personal information.
The editorial desk uses Google Identity Services for authorized HOBOS operators only. Opening that page connects to Google to load its sign-in component. When an operator signs in, Google provides identity claims such as a verified email address, account identifier and basic profile information. Our server verifies the token and checks an explicit operator allowlist. We do not request access to Gmail, Drive or other Google account content, and signing in does not create a public profile or a visitor account in our database. An operator's verified account identifier is recorded with any editorial review actions, not with dictionary visits.
Google processes sign-in information under its Privacy Policy and may process it outside Korea. Guest forms do not require or load Google sign-in. Ordinary dictionary reading does not send article text to OpenAI or load Turnstile.
When an open contribution or report form loads, Cloudflare Turnstile processes technical signals such as IP address, browser information, TLS fingerprint and site origin to verify a human interaction and prevent abuse. Operators may also choose to start a Turnstile diagnostic. Our server sends the short-lived verification token to Cloudflare for validation; it does not store the token or forward submission text to Cloudflare. Cloudflare may process these signals outside Korea, including in the United States, under the Turnstile Privacy Addendum, including to improve Turnstile. Its retention is governed by its own notice, not our 90/180-day receipt policy.
To prevent the same verification from being reused across servers, we store a one-way SHA-256 hash of a successfully verified token and a security-cache expiry time in the database. We do not attach an IP address, email address, account identifier or submitted content to that record. Tokens are accepted for at most five minutes; cache expiry includes a one-minute safety margin. The application removes expired cache records during later valid verifications, so expired hashes can remain longer when the service is idle. These unusable hashes are separate from contribution content and inquiry correspondence.
When you submit a definition or correction, our server sends the contribution fields described above to OpenAI over HTTPS for safety and language assessment. We do not intentionally include your IP address, verification token or operator identity in that request. OpenAI may process the content outside Korea, including in the United States. Requests use response storage disabled (store: false); this is not Zero Data Retention. OpenAI’s API data controls documentation describes abuse-monitoring retention of up to 30 days by default, with legal or safety exceptions, and feature-specific retention such as prompt caching. Our private receipt deletion does not itself delete provider-held records.
5. Cookies and browser storage
NoCapWiki does not load Google AdSense scripts or set advertising cookies. Optional analytics cookies are used only after you select Allow analytics, as described below. Public dictionary pages do not load social sign-in scripts. Google sign-in is limited to the operator-only editorial desk; the resulting ID token stays in the page's memory, not in NoCapWiki cookies or local storage, and is cleared on refresh or sign-out. The site's navigation framework may use your browser's session storage to restore your scroll position; that information stays in your browser.
We publish an AdSense account-verification meta tag and an ads.txt file while Google reviews the site. These identify our publisher account; they do not load advertising scripts or set advertising cookies.
We have configured an English consent message for NoCapWiki in Google's consent management tool, including an option not to consent. It is not displayed while advertising scripts are disabled. Publishing that configuration is not the same as enabling advertising.
We will update this policy and any required consent notices before enabling advertising or public accounts.
6. Optional visitor analytics
If you select Allow analytics, we load Google Analytics 4 to understand visits, popular dictionary pages, referral sources, approximate geography and device or browser categories. Google receives technical connection information and page-view events with a pseudonymous cookie identifier. Google may process this information outside Korea under its Privacy Policy; see also how Google uses information from sites that use its services.
We do not load the analytics tag before consent or after a saved rejection. Choosing Reject analytics does not limit dictionary access. Use Analytics settings in the footer to change your choice. Withdrawing stops further collection in this page and removes this site's Google Analytics cookies; it does not automatically erase information already received by Google.
Our application sends public page paths and titles, with URL query strings and fragments removed. It strips referring URLs to their site origin and does not send your search text, email, form contents, operator account identifiers or events for administrator, submission and report pages. Automatic enhanced measurement, Google signals, granular city/device collection and advertising personalization are disabled for this integration. We do not send a signed-in user ID to Analytics.
The necessary nocapwiki_analytics_v1 cookie remembers your allow or reject choice for up to 180 days. If you allow analytics, _ga and a property-specific _ga_… cookie are configured for up to 180 days without extending their lifetime on each visit. Browser settings or deletion may shorten these periods. Google Analytics event-level and user-level data retention is set to two months; this setting does not delete standard aggregated reports, which may remain longer. See Google's retention documentation.
7. Your choices and rights
You may browse without submitting, reporting or emailing us. To ask about a contribution, report or email inquiry, or request access, correction, restriction or deletion, write to support@hobos.studio. Include a receipt reference or entry URL when available, not extra sensitive information. We may ask for evidence needed to verify that a request concerns you before acting on it. A public guest label alone does not prove authorship.
8. Operator and changes
NoCapWiki is operated by HOBOS (호보스), represented by Sungsu Choi (최성수). Business registration number: 848-11-02842. Business address: 서울특별시 서대문구 이화여대1길 42-10, 402호(대현동, 엔트라리움), Republic of Korea. Privacy and content inquiries: support@hobos.studio.
We will revise this page when our practices change and show the new effective date here.