개인정보 처리방침

데이터 처리 약속

• 클라이언트 사이드 도구의 원시 입출력은 브라우저에서 처리됩니다.
• 분석 이벤트에는 도구 식별자, 타임스탬프, 대략적인 지역만 포함됩니다.
• 도구의 원시 콘텐츠는 수집, 저장, 판매하지 않습니다.
• 민감한 도구에는 빠른 로컬 정리를 위한 데이터 삭제 동작을 제공합니다.

도구별 개인정보 안내

다음 도구들은 민감한 입력을 전적으로 클라이언트 사이드에서 처리합니다:

• JWT tools (jwt-encoder, jwt-decoder): header, payload, token strings, and signing secrets are handled client-side.
• HMAC generator (hmac-generator): message payloads and secret keys are hashed locally in your browser session.
• Hash tools (hash-generator, hash-compare-tool): source text and hash values are computed/compared locally.
• Email tools (email-validator, email-extractor): addresses and source text remain in-page unless you copy/export them yourself.
• Base64 image conversion (base64-to-image): Base64 payloads are decoded for preview/download without server upload.

수집 항목

• 도구 식별자 (예: json-formatter).
• 엣지 네트워크가 추론한 국가 코드 (예: US).
• 활성 언어 접두사 (예: /ne/...의 경우 ne).
• 방문 이벤트의 타임스탬프.

수집하지 않는 항목

• 도구의 원시 입력/출력 내용 없음.
• 공개 방문자에 대한 계정 프로필 없음.
• 개인 정보 판매 없음.

Languages & locale (Visitors)

UtilitySansar is available in multiple languages. When you switch language with the locale picker, we set a small cookie (us_locale) that remembers your preferred locale so we can serve the right translation on your next visit. The cookie stores only the locale code (for example "es" or "ja") — nothing else.

• The active locale prefix (e.g. /es/, /hi/) is included in analytics events alongside the tool slug.
• Locale detection may use the Accept-Language header on the very first visit; this header is not stored.
• You can change or remove the locale cookie at any time from your browser settings.
• Translations are static — your text input is never sent to a translation service.

Accounts & login providers (Signed-in users)

Signing in is optional. We support sign-in with the following identity providers, and we never store your password — the provider verifies you and tells us who you are.

• Google (OpenID Connect)
• GitHub
• Microsoft (Entra ID / personal accounts)

When you complete sign-in, we read only the following from your provider profile and store it on our account record:

• Provider user ID (an opaque identifier from Google / GitHub / Microsoft).
• Email address (used as your account identity).
• Display name, when present.
• Avatar / profile picture URL, when present.

After a successful sign-in we create a short-lived session and set a single HTTP-only, Secure cookie (us_session) that identifies the session on our server. We do not place any third-party cookies, and the session cookie carries no profile data of its own.

We request only the minimum scopes each provider needs to return your email, name, and avatar. We do not post on your behalf, do not read your repositories, mailbox, calendar, or contacts, and we do not request offline-access / refresh tokens.

You can sign out from the account menu at any time, which immediately destroys the session. If you would like your account record removed entirely, contact us through the report page and we will delete the stored profile and any account-scoped data within 30 days.

Third parties

We do not share account data, locale preference, or analytics events with advertisers or data brokers. The only third parties involved in a typical signed-in session are the OAuth provider you chose (Google, GitHub, or Microsoft) and our infrastructure host (Cloudflare). Each is contacted only to the extent needed to authenticate you or serve the page.

보관 기간

분석 이벤트는 최대 12개월 동안 보관된 후 삭제되거나 장기 추세 보고용으로 집계됩니다. 원시 분석 데이터에 대한 접근은 인가된 관리자에게만 제한됩니다.

Contact & terms

Questions about privacy, account deletion requests, or other concerns can be raised from our report page. See also our Terms of Use for the rules that govern use of the site.