Security & trust
Controls behind your code context.
Access and isolation
HTTPS protects public connections. Accounts use salted password hashes and revocable sessions. Provider credentials are encrypted at rest. Customer graph generations use isolated databases; website sessions and agent keys select the account on the server. Agent keys have explicit read or repository-management permission, expiry and revocation. The operator workspace is separately authorized.
Repository processing
We copy authorized GitHub/GitLab branches to a private, bounded checkout, extract supported structure and publish an isolated graph. We do not run customer code, follow symlinks, initialize submodules or download Git LFS content. Temporary checkout files are removed after the job. Retrieval includes provenance and the indexed revision; consider incomplete coverage and inferred relationships when using results.
Feedback and closure
Images are decoded and bounded before storage and are served through authenticated routes. Verified customer closure revokes access immediately; scheduled erasure removes active data and expires application backups. A separate erasure ledger prevents reactivation through backup restore. See Privacy.
Report an issue
Email support@weeyuga.com with safe reproduction steps. Avoid accessing another user’s data or exploiting beyond what is needed to describe the problem. We make no claim of independent certification or an agreed SLA unless expressly contracted.