Política de privacidade
Última atualização: 19 de abril de 2026
O UtilitySansar é projetado para manter privada a sua entrada nas ferramentas. A maioria roda diretamente no seu navegador, e não armazenamos o texto, os arquivos ou os segredos que você processa com elas.
Coletamos apenas telemetria agregada mínima para entender quais ferramentas são usadas e de qual região do país, para que possamos manter e melhorar o site.
Garantias de tratamento de dados
- Entradas e saídas brutas são processadas no navegador para ferramentas do lado do cliente.
- Eventos de analítica incluem apenas o slug da ferramenta, um carimbo de tempo e a região aproximada.
- Não ingerimos, persistimos ou vendemos seu conteúdo bruto.
- Há ações de Limpar dados em ferramentas sensíveis para limpeza local rápida.
Notas de privacidade por ferramenta
Estas ferramentas tratam entrada sensível inteiramente no cliente:
- 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.
O que registramos
- Slug da ferramenta (exemplo: json-formatter).
- Código de país inferido pela rede de borda (exemplo: BR).
- Prefixo de idioma ativo (exemplo: ne para /ne/...).
- Carimbo de tempo do evento de visita.
O que não registramos
- Sem conteúdo bruto de entrada/saída das ferramentas.
- Sem perfis de conta para visitantes públicos.
- Sem venda de informações pessoais.
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.
Retenção
Os eventos de analítica são mantidos por até 12 meses, depois excluídos ou agregados para relatórios de tendência de longo prazo. O acesso à analítica bruta é restrito a administradores autorizados.
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.
Safa privacy summary
Safa is a Chrome extension designed to block ads, trackers, and intrusive overlays while maintaining strong privacy protections.
Key privacy points
- Data collection. Safa does not collect, transmit, or store any personal data on external servers during the MVP. The extension stores only locally-managed information like your blocking preferences, site allowlists, and configuration settings — all remaining on your device via
chrome.storage.local. - Network activity. The extension itself makes no external requests. Instead, it relies on Chrome's declarative network rules that function within the browser engine itself.
- API usage. Safa's API retrieves only public configuration data like profile information and version details. This API does not receive any data from your browser.
- Permissions. Five permissions enable core functionality — network rule declaration, local storage, and tab access for the popup feature.
- Data retention. Settings persist locally until you uninstall the extension or reset to defaults; nothing remains on UtilitySansar servers.
Users concerned about privacy can report issues via the official report page.