Skip to content
MergeRay/ docs

Search documentation

Local documentation search Tab to navigate · Esc to close

Source processing

Understand source transfer, temporary storage, retention and permissions.

On this page Do you keep my private code?When is my source removed?What remains after a review?Is my source used by AI?Access and publicationWhat are the deletion limits?Security reports

Do you keep my private code?

Public and private source reviews process your code temporarily for analysis. MergeRay does not maintain a permanent copy of your codebase or reuse a raw source cache between reviews. Code is held in memory and temporary analysis storage while a review runs.

Selected committed files and bounded Git proof objects are transferred over authenticated HTTPS. Paths, authors and commit messages can be present in metadata even when file contents are excluded. Secret screening is bounded and is not a guarantee that a submission is free of sensitive information.

When is my source removed?

Completion, failure, cancellation and timeout all trigger cleanup. The service clears its managed source buffers and releases their references. Temporary analysis files are removed as execution finishes, including when work ends after an error or cancellation.

  • Incomplete uploads expire after 10 minutes without requiring another request. A started review has a 30-minute overall deadline measured from acceptance. These are processing limits, not promised deletion deadlines.
  • A graceful shutdown waits for active execution cleanup. After a crash, temporary files can remain until the service restarts and cleans its own workspace. Storage failures can delay removal.

What remains after a review?

Results and request metadata are separate from raw source. They can include findings, coverage, file paths, source locations, revision identifiers, source manifests, digests and analysis policy. They remain sensitive repository information even though the durable run record contains no raw source bodies.

The current service provides a 24-hour window for retrieving an accepted run and handling retries consistently. Raw source is not kept for that window. Expired records are swept at startup, during new submissions and every minute while the service runs; downtime or storage errors can delay physical deletion.

GitHub Checks and job summaries follow the destination repository’s access and retention settings. Expiring a MergeRay run does not delete output already published to GitHub.

Is my source used by AI?

The public v1 source-review path does not call an AI or model service. Submitted source is processed for MergeRay analysis and service operation, not for AI or model training. User data and source are not sold or used for advertising.

This describes the current source-review path. Any future change to processing purposes or model use must be documented before it is presented as part of the product.

Access and publication

  • Same-repository Action permissions: contents: read, actions: read, pull-requests: read, checks: write and id-token: write.
  • GitHub publication credentials and service OIDC identity are separate. The service must recognize the exact approved workflow and repository.
  • The public entry point publishes a Check and job summary, not inline PR review comments. Do not execute untrusted PR scripts while credentials are present.

What are the deletion limits?

Temporary processing does involve storage. Cleanup does not guarantee immediate, irreversible erasure of every runtime or infrastructure copy. The 24-hour replay window is not a retention policy for every kind of workspace, account or billing data.

This documentation does not establish a storage region, encryption-at-rest assurance, backup deletion schedule or general customer deletion workflow.

Read the full source-processing policy

Security reports

Keep vulnerability reports and repository-sensitive details out of public issues. Follow the repository’s private reporting policy.

View support and security channels