Security and privacy model

After you authorize GitHub, GitSnap lists the repositories your account can access and reads the contents of the specific paths you select for publication. It does not clone repositories wholesale, and it does not read files you never selected.

Your account, the repositories you chose to sync, the publication records (repository, selected paths, entry file, access rules), the snapshot copies of the selected files, and a view log per link. GitHub authorization material is held encrypted and used only on your behalf.

Revoking the GitHub authorization from your dashboard removes GitSnap's access. Deleting a publication removes its snapshot, and the link stops resolving.

The published path set is authoritative. A request for a path that is not in the set is refused rather than merely absent from a listing, so guessing filenames does not reveal anything.

Slugs include a random suffix, published links never appear in the sitemap or in any public index on this site, and crawlers are only pointed at marketing and policy pages. An unrestricted link is still shareable by anyone who has it — treat it like any secret URL, and use access rules when that matters.

When a link is limited to email addresses or company domains, viewer identity is verified before any file is served, including individual assets fetched by the page. Unauthorized requests receive a 403 with no-store caching, and access is granted through short-lived, viewer-bound, HTTP-only cookies rather than shareable URL tokens.

Because snapshots do not follow your branch, a later commit cannot accidentally widen what is public. Updating what viewers see is always an explicit action.

Snapshots are screened at publish time for credential-harvesting and phishing patterns, and publishing is rate-limited per account. Published pages are served with hardened HTTP headers. Abuse can be reported to hello@lg-chipstack-ai.xyz.

Anything a browser renders can ultimately be inspected by the person viewing it. GitSnap adds deterrents against casual copying and never hands the viewer app raw file contents it does not need, but it cannot make content both visible and unreadable. Publish only what you are comfortable letting the recipient keep.