Data Handling

Inputs, local files, external transmission, and retention duties for per-user DevHunt records.

What scan reads

scan requests repository, pull-request, commit, contribution, profile, organization, and optional profile README fields for the requested login through authenticated GitHub GraphQL queries. Those queries have no public-only visibility filter: results follow token/viewer access and can include private or internal-visible repository and pull-request data. Use a least-privilege token and confirm its token-visible scope before scanning.

What scan writes

The default raw directory is out/LOGIN/raw/. It can contain repos.jsonl, prs.jsonl, commits.jsonl, contributions.json, user_info.json, and an optional profile_readme.md. Treat every generated file as sensitive local data: records can contain identifiable author metadata and material derived from private or internal-visible sources.

What report writes

report reads those raw files and writes profile.json, top_repos.json, and chart files below out/LOGIN/. narrate can add a prompt file or generated narrative in the same per-user directory.

Retention and removal

The fixed source does not enforce a retention schedule. The operator must choose a purpose, use a least-privilege token, limit access, avoid committing generated per-user output, and remove raw, derived, prompt, and narrative files when that purpose ends.

External transmission

Scanning sends queries to GitHub. AI narrative generation sends profile-derived prompt material to the configured provider only when an API key is present. Review the prompt and provider terms before enabling that path.

Issue reporting state

Repository issue reporting is unavailable pending re-audit. Use the site search or Ask Docs for documentation questions; the restricted repository destination is intentionally not exposed here.