WelcomeScore Privacy Policy: Public Audits and Community Data

01

Scope and plain-language summary

This Privacy Policy explains how WelcomeScore, an ETHIOR project, processes information when you use the hosted WelcomeScore service, including public repository audits, optional Algofox reviews, the Hall of Fame, and the Dev Lounge. It applies to the canonical hosted service and does not automatically apply to forks, third-party websites, linked services, or modified deployments.

02

Information the service processes

Feature	Information processed	Purpose
Repository audit	The repository path you enter and the public GitHub metadata needed for the six published checks, such as public files, README/setup signals, license metadata, issue-label results, and recent push status.	To calculate and display the requested contributor-readiness score.
JavaScript Health	For an explicit public GitHub check, the repository path and allowlisted public signals: root package metadata, selected configuration-file paths, workflow indicators, and starter-label names. The dashboard does not return raw manifests or workflow bodies, and it does not read local files. The optional CLI reads the selected local project directory but does not upload source files, package manifests, environment values, repository credentials, or analytics to WelcomeScore.	To produce a requested JavaScript and TypeScript package-maintenance report.
Optional Algofox review	A normalized audit context: repository path, score, grade, primary language, documented check outcomes, and permitted focus checks. The feature does not send raw README bodies, issue text, source code, browser-submitted metrics, Hall data, or Lounge data to a review provider.	To generate an opt-in, evidence-bound review.
Review rate limit	When enabled, a salted hash derived from a network identifier and a short request-count window. The raw IP address is not stored in the review-rate-limit record.	To protect the opt-in review endpoint from excessive use.
Share With Purpose receipt	Only after you explicitly create one: a signed, dated subset of public audit facts—repository path, score, grade, selected passed-check labels, selected open good-first-issue count, default branch, issue time, and expiry. It excludes raw README/code/issue content, browser identity, workspace notes, AI review content, Hall/Lounge data, and credentials.	To provide a tamper-evident public link for the contributor context you chose to share.
Hall of Fame	An eligible public repository’s audit information when a visitor explicitly chooses to add it.	To display a public, eligibility-based ranking record.
Dev Lounge	The anonymous message, quoted-reply snapshot, optional score card, reaction choice, temporary browser-generated developer handle/avatar, session-scoped identifiers, short-lived signed interaction proof, and salted network-rate bucket needed for temporary chat and abuse protection. The raw network identifier is not stored in the rate record.	To provide a lightweight 24-hour community discussion experience and protect it against automated or excessive requests.
Lounge reports and moderation	The reported message identifier, report category, optional limited detail, a private structured moderation decision, confidence band, policy category, provider/model label, and action timestamp. If AI review is configured, only the reported public message and report category are sent to that provider; the reporter identity, raw network data, unrelated chat history, and credentials are excluded.	To review private safety reports, prevent clear high-severity abuse, and maintain a limited owner audit trail.
Visitor verification	When enabled, a Cloudflare Turnstile challenge token is sent from the browser to WelcomeScore’s server for one-time validation. WelcomeScore does not store the token in the Lounge database.	To distinguish ordinary visitor activity from automated form abuse.
My Contributor Workspace	A repository path, chosen contributor action, optional private note, local work state, return preference, and a small public-audit snapshot when you explicitly save a plan. This feature stores the information only in your current browser.	To let you resume a private contributor plan and choose when to request a fresh public audit.

03

Retention and deletion

Public GitHub scoring data, including explicit JavaScript Health requests, is cached briefly to reduce repeated upstream requests. JavaScript Health reports are generated from requested public signals and are not stored as an account profile or report history.

Private review-cache entries store a normalized context hash and a validated review result. Deterministic review entries are retained for up to 24 hours; validated provider-review entries are retained for up to seven days. Cache retention can be shorter if an entry expires or is cleared through normal operations.

Dev Lounge messages and related temporary chat records are designed to expire after 24 hours. Quoted-reply snapshots may remain only for the same limited retention period. Private report, structured moderation, and salted rate-limit records are designed to expire after 30 days. Signed interaction proofs are short-lived and are not stored as a Lounge record. Browser-local identity details are stored in your browser and can generally be removed by clearing the site’s local storage or browser data.

My Contributor Workspace plans, including optional private notes and saved audit snapshots, remain only in the browser where you saved them. WelcomeScore does not receive, sync, sell, profile, or publish those workspace records. You can clear an individual plan, clear all plans from the workspace, or clear site storage through your browser.

A Share With Purpose receipt is created only after an explicit request. It is a signed public URL, so anyone with the link can view its limited public-audit snapshot until its 21-day expiry. WelcomeScore does not create a receipt index, user share history, receipt-issuance log, or share/click analytics for this feature. An expired receipt no longer displays its score or audit facts.

Public Hall of Fame records may remain available while they satisfy the service’s documented freshness and eligibility rules. Because they relate to public repositories, removal and correction requests should be made through the canonical project repository with enough public context to locate the record.

04

Service providers and public disclosure

WelcomeScore obtains public repository information from GitHub. The hosted application and permitted product data are operated through its deployment and database services. Optional repository reviews and event-driven private Lounge report reviews may use configured AI providers; the service sends only the constrained context described above and uses a stateless provider setting where supported. When configured, Cloudflare Turnstile processes visitor-verification challenges; its processing is governed by Cloudflare’s own terms and privacy disclosures.

Information submitted to the Dev Lounge is visible to other Lounge participants for its retention period. A Hall of Fame entry is public once a visitor explicitly adds an eligible repository. A Share With Purpose receipt is public only if a visitor explicitly creates and shares its link; opening the composer does not create it. External sharing websites are separate services governed by their own policies. WelcomeScore may disclose information where reasonably necessary to operate the service, protect users or infrastructure, investigate abuse or security concerns, comply with applicable law, or enforce the published terms.

WelcomeScore does not sell a user’s private information through the application. However, external services and links are governed by their own terms and privacy practices. Review their policies before providing them any information.

05

Your choices and responsibilities

You may choose not to submit a repository, request a JavaScript Health check, run the local CLI, request an optional review, save a private contributor plan, request a fresh audit, create or share a dated audit receipt, add an eligible Hall entry, post in the Lounge, attach a score card, react, or follow an external link. My Contributor Workspace does not set reminders or run checks on its own; you choose when to resume work or clear local plans. Do not use the Lounge for private conversations, personal information, credentials, transactions, recruiting, legal advice, security reports, or sensitive content.

You are responsible for ensuring that you have permission to submit any repository path, message, score card, or other content. If you believe public content in a project-controlled feature is inaccurate, unlawful, infringing, or harmful, use the conduct and support routes described below. Do not post sensitive reports publicly.

06

Security and policy updates

No internet service can guarantee absolute security. WelcomeScore uses practical separation of browser-safe and server-only credentials, private review-cache permissions, signed interaction proofs, server-side visitor-verification checks when configured, and limited retention, but you should still avoid sharing sensitive information. Automated moderation is a safety support, not a guarantee that harmful material will be detected or removed. For a suspected vulnerability, follow SECURITY.md rather than posting publicly.

ETHIOR may update this policy as the product changes. Material updates will be reflected on this page and in the source repository. Continued use after an effective update is subject to the updated policy to the extent permitted by law.

07

Questions and reports

For a non-sensitive policy question or correction request, use the canonical WelcomeScore repository. For security reports, use the private route in SECURITY.md. For conduct concerns, use the process in CODE_OF_CONDUCT.md.