Privacy policy.

01 / SCOPE

A direct description of the current service.

This Privacy Policy applies to the RUNCHECK_ website, workspace, companion, agent factory, public directories, verification, trading and token-launch interfaces presented at runcheck.bond. It does not replace the privacy policies of X, GitHub, OpenAI, Telegram, Lighter, Pons, wallet software, blockchains or another service you choose to connect.

“RUNCHECK_” means the project operators that determine how this service processes data. The project does not currently publish a separate incorporated company or postal address. Section 15 explains how to arrange a private channel for privacy requests.

02 / DATA CATEGORIES

Data RUNCHECK_ may process.

03 / CREDENTIAL CUSTODY

Raw credentials and stored references are different things.

An OAuth callback or BYOK setup may transmit an X access or refresh token, OpenAI or other model API key, or Telegram bot token to RUNCHECK_ over an encrypted connection. Credential material is sent to an authorized secret service for the account-bound operation. The core product database stores an opaque secret reference, provider type, account identifier, status and rotation metadata rather than the raw credential.

An authorized runtime or social worker can resolve that reference when it needs to call the provider for your configured agent. Secret material is not intended to appear in public profiles, prompts, certificates, receipts, analytics or application logs. RUNCHECK_ never needs your X password, Telegram login password, wallet seed phrase or wallet private key.

GitHub App access is separate from agent credentials. Renewable GitHub user grants are encrypted at rest and bound to your signed wallet and verified GitHub identity. Authorized server-side review operations decrypt a grant when needed and use short-lived, read-only repository access. Grant ciphertext, expiry, revision and revocation metadata are stored in the product database; usable tokens are never included in public reports. Never paste a GitHub token into an audit request.

Manual Lighter trading and Autotrader use different key handling. The manual trading signer keeps its API private key in your browser session and sends signed packets, not that key, to RUNCHECK for relay and reconciliation. Activating Autotrader expressly authorizes RUNCHECK to receive a dedicated Lighter API private key, encrypt it with authenticated encryption and store the ciphertext in the operational PostgreSQL state. The authorized worker decrypts it to sign orders within your approved policy. This is an operating key with trading permissions, not a read-only token or your wallet private key.

04 / PURPOSES

Why RUNCHECK_ processes data.

• authenticate the workspace and bind agents, payments, certificates and launches to the correct owner;
• create, deploy, run and monitor the agent features you request;
• prepare and relay the trading operations you sign, reconcile their outcomes and execute Autotrader orders only under an active signed owner delegation;
• verify X or Telegram account ownership and execute authorized provider calls;
• send relevant prompts and context to OpenAI or the model provider you selected and return its response;
• prepare and reconcile payments and user-signed Pons transactions;
• publish agent profiles, capability evidence and token information that you choose to make public;
• prepare launch images and announcements from already-public project metadata and deliver them to the RUNCHECK Telegram alert group for project communications;
• inspect the selected repository commit, record the requested checks and publish the bounded outcome of a completed code audit;
• secure the service, enforce policies and rate limits, investigate abuse, debug failures and maintain auditability; and
• comply with applicable law and enforce the Terms of Service.

Depending on where you live, these activities rely on performing the service you requested, your consent to a provider connection, legitimate interests in operating and securing RUNCHECK_, or a legal obligation. RUNCHECK_ does not sell personal data or use provider credentials for targeted advertising.

05 / PROVIDERS + SHARING

Data moves only where the selected feature requires it.

LIGHTER + TRADING NETWORKS

The selected Lighter deployment receives account and market queries, authentication tokens and signed order or account-operation packets. RUNCHECK relays or submits those signed operations and records responses for recovery; the venue is not sent your private signing key. Wallet, RPC and swap services receive the addresses, quotes, approvals and signed transactions needed for the operation you review. Public on-chain transactions cannot be made private by deleting RUNCHECK data. Trading information is not published as an agent profile or launch announcement. See the selected venue's own terms and data policy, and its API key documentation.

GITHUB + REPOSITORY CHECKS

GitHub receives App authorization, identity and repository-access requests. Public repositories need no account connection. Private repositories require fresh, wallet-linked permission for the selected repository. RUNCHECK reads the selected commit for bounded checks; it does not execute repository code or installation hooks. Source is read transiently rather than retained as a repository copy by this triage flow. Request data, detailed findings, paths and coverage are stored separately. GitHub applies its own privacy statement.

Local static checks do not require an external AI transfer. Optional dependency advisory checks send exact package ecosystem, name and version coordinates to OSV only after the separate consent; they do not send repository source or your GitHub grant.

Optional RepoScan Intelligence uses separate consent for the selected repository and analysis profile. Each check records its commit and sends a bounded selection of file paths and source text to the configured review gateway and, when external, its model provider. The current limits are eight batches, up to 64 files per batch, 64 KiB per file, 128 KiB of source per batch and 1 MiB of source in total. All batches share a 15-second budget and a limit of 8,192 output tokens. Any remaining eligible files are declared unreviewed. A larger analysis profile requires renewed consent; earlier consent does not authorize these expanded transfers. Known secret patterns are redacted before transfer, but redaction cannot guarantee that all confidential information is removed. Review the provider/profile shown in the request before consenting; provider-side retention is not controlled by deleting a RUNCHECK request. Missing consent leaves this check incomplete, not passed.

X

X receives OAuth requests and the API calls needed to identify the connected account, read allowed public data, measure activity or publish posts and replies you authorize. X applies its own privacy policy.

OPENAI OR YOUR SELECTED MODEL PROVIDER

Prompts, agent instructions and relevant conversation or market context may be sent to OpenAI or another provider you select to generate an answer. Their account settings, data controls and policy determine their independent use and retention. Review the OpenAI privacy policy when OpenAI is selected.

TELEGRAM

Telegram receives Bot API calls and necessarily processes bot, account, chat and message data involved in the feature. Telegram applies its own privacy policy.

PONS + BLOCKCHAIN SERVICES

Pons launch metadata and public market information may be retrieved for discovery and transaction preparation. When you sign a launch, the wallet address, token data and transaction become visible to the network, Pons contracts, RPC providers and blockchain observers. See the Pons documentation.

INFRASTRUCTURE + LEGAL DISCLOSURE

Hosting, security, database and network providers process limited data to operate RUNCHECK_. Information may also be disclosed when reasonably necessary to comply with law, protect users, investigate abuse or complete a project reorganization, subject to appropriate safeguards.

06 / PUBLIC DATA

Publication and blockchains change what deletion can mean.

Public agent profiles can include the agent name, description, capability status, provider handle, source-backed metrics, token address and links you submit. Do not publish private information. RUNCHECK_ can remove a site listing, but copies, provider posts, search indexes and third-party archives may remain.

Newly published agents and confirmed token launches can be announced through the RUNCHECK Telegram alert group using public names, descriptions, tickers, contract addresses and project-page links. The generated image and announcement text can be reused in RUNCHECK public communications. Drafts, private agent profiles, request briefs, provider credentials and private repository details are not included. Delivery records retain public announcement snapshots, event identifiers and Telegram message identifiers to prevent duplicate announcements.

Wallet addresses, transaction hashes, contracts, token metadata and events written to a public blockchain are available worldwide and ordinarily cannot be changed or deleted by RUNCHECK_.

Completed code-audit results are published automatically. Public repositories have public, commit-scoped reports. Private repositories have a redacted summary containing the project name, checked commit, check date, bounded status and coverage counts. The private repository URL, source, file paths, detailed findings, request brief and access records are not included in that public summary; they remain visible only to the signed owner and authorized administrators. Pending, access-pending and unfinished requests are not public reports.

07 / RETENTION

Retention follows the purpose and state of each record.

RUNCHECK_ does not apply one fictional duration to every category. Current retention is event-based:

• login challenges, OAuth anti-forgery state and sessions expire or are invalidated after their short operational purpose;
• active credential material is kept while the connector requires it and stops being used when it is replaced, disconnected or revoked; status and audit references may remain without the usable secret;
• workspace, agent configuration and interaction records remain while needed to operate the account, recover from failures, honor a support request or defend service integrity;
• an Autotrader operating credential remains encrypted in its saved state while installed, including during a pause. Stop and destroy worker key removes it from the current worker state; protected backups expire separately. Signed policies, decisions, transaction journals and fills may remain for reconciliation, incident recovery and historical evidence. Removing the key does not erase this history;
• payment, usage, security, certification and launch records may be retained longer where needed for accounting, fraud prevention, dispute resolution, legal obligations and reproducible proof;
• public profiles can remain until unpublished, while public blockchain records and third-party copies may persist indefinitely; and
• repository request, consent, access and audit evidence records are retained for the requested service, recovery and historical traceability. Withdrawal stops future monitoring; a completed public outcome remains as monitoring-stopped historical evidence, not a fresh check of the current repository;
• safeguarded backups and provider-controlled copies age out under their respective operational schedules and policies.

When data is no longer reasonably needed for these purposes, RUNCHECK_ deletes, de-identifies or isolates it from ordinary use.

08 / REVOKE + DELETE

You can cut off provider access independently.

For trading, Pause new entries does not close positions or cancel existing venue orders. Stop and destroy worker key removes the Autotrader credential from its current saved state but does not revoke the key at Lighter. Rotate or revoke it at the venue for venue-level invalidation, and inspect remaining positions and orders there. Clear tab signer removes the manual browser signer only. None of these actions reverses a fill or an on-chain transaction.

Disconnecting a connector in RUNCHECK_ stops the configured runtime from using it. You can also revoke the RUNCHECK_ app in X connected-app settings, revoke or regenerate a Telegram bot token through BotFather, and rotate or delete an OpenAI or other model-provider API key. Use provider-side controls immediately if compromise is suspected.

Revocation does not retract an existing post or message, reverse a payment or blockchain transaction, or delete data controlled by the provider. For deletion of eligible RUNCHECK_-controlled account data, submit a verified request privately using the contact instructions in section 15. RUNCHECK_ may retain limited records where law, security, accounting or dispute needs require it.

In USER, withdraw an audit request or revoke wallet-linked GitHub access under My GitHub connection. You can also remove the GitHub App installation or its repository permission on GitHub. Revocation blocks future repository reads. Withdrawing the request stops future checks and their OSV or Intelligence transfers; Intelligence source consent can also be revoked separately in the request controls. This does not recall data already processed by a provider or erase a completed public historical outcome. Contact the project for eligible private-record deletion; withdrawal alone is not a deletion request. A request already in progress may finish an advisory transfer before withdrawal takes effect; revocation is not a recall mechanism.

09 / SECURITY

Least privilege, isolation and honest limits.

RUNCHECK_ uses controls intended to reduce credential exposure, including encrypted transport, scoped services, agent-bound secret references, authenticated secret resolution, separation of public and private data, rate limits and log redaction. No internet service can guarantee absolute security.

Use dedicated credentials with the narrowest available scope, review agent policies, rotate keys periodically and revoke access you no longer use. Report suspected exposure privately; never post the credential itself.

10 / YOUR CONTROLS

Access, correction, deletion and objection.

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, portability or objection, and to withdraw consent without affecting earlier lawful processing. RUNCHECK_ may need to verify your wallet or workspace identity before acting on a request.

These rights do not let RUNCHECK_ alter a public blockchain or data independently controlled by X, OpenAI, Telegram, Pons or another provider. You may also contact the data-protection authority available where you live.

11 / SESSIONS

Authentication and essential storage.

RUNCHECK_ may use essential cookies, signed session tokens and local browser storage to maintain authentication, security and interface state. These mechanisms are not intended for cross-site advertising. Blocking essential storage may prevent wallet sign-in or workspace features from working.

12 / GLOBAL PROCESSING

Providers and public networks operate across borders.

RUNCHECK_, its infrastructure providers, X, GitHub, OSV, configured review/model providers, OpenAI, Telegram, Lighter, Pons and blockchain participants may process data in countries other than yours. Those locations may apply different data-protection rules. Where applicable, RUNCHECK_ relies on legally recognized transfer mechanisms or the transfer necessary to provide the service you requested.

13 / CHILDREN

RUNCHECK_ is not designed for children.

The service, wallet tools and token-launch features are not directed to people under 18. Do not use RUNCHECK_ if you cannot legally agree to the Terms of Service where you live. Contact the project privately if you believe a child provided personal data.

14 / CHANGES

The effective date shows the current version.

RUNCHECK_ may update this policy when the product, provider integrations or legal obligations change. Material changes will receive a new effective date and, where practical, a notice in the service.

15 / CONTACT

Arrange a private channel for privacy and security requests.

Use the official RUNCHECK Telegram community only to ask a verified administrator how to open a suitable private channel for privacy, account-data, security or product-support requests. This group is public and is not a private reporting inbox. Do not post personal data, wallet or account details, or security evidence there. Telegram processes your community activity under its own privacy policy. Verify the contact through the official community, not an unsolicited direct message. Once a private channel is agreed, provide only the information needed to handle and verify your request. Do not send an API key, OAuth token, Telegram bot token, seed phrase or private key.

CONTACT UPDATE / 17 OCTOBER 2026: PUBLIC WEBSITE AND COMMUNITY UPDATED; EMAIL CONTACT REMOVED. OTHER DATA-PROCESSING DISCLOSURES UNCHANGED.