Privacy Policy

This policy covers the Runledge website, the Runledge Cloud control plane, and the Runledge data plane when operated by Runledge, Inc. (“Runledge”, “we”).

• Customer Data — workspace policies, approval proposals, action metadata and reported outcomes you submit to Runledge. For Customer Data, you are the controller and Runledge is your processor.
• Account Data — names, work emails, billing details and usage counts needed to run your account. For Account Data, Runledge is the controller.

Runledge stores submitted action metadata, approval proposals, policies and audit records in the backend. The current service does not provide a zero-data-retention mode or an automatic customer-configurable trace expiry.

• Send only the proposal fields and outcome metadata needed for your policies and reporting. Do not submit provider secrets or unnecessary personal data.
• Action receipts attest to recorded identity and time. They do not attest to the action body or independently verify provider execution.
• Audit exports include file hashes and a signed manifest of the export snapshot. They are not Merkle-chain receipts.

Contact us to discuss retention and deletion requirements before submitting sensitive data.

Provider credentials stay in your own integration. Runledge does not currently offer a provider credential vault, HSM or customer-KMS integration, or short-lived provider token leasing.

Workspace action API keys are stored hashed and can be scoped and revoked. Webhook secrets and service signing configuration are protected separately; these do not constitute a provider credential broker.

You retain all right, title and interest in Customer Data, your invariant definitions, policies and audit records. We claim no license to them beyond what is necessary to provide the service to you.

Authorized workspace users can export audit records and policies. Contact us for deletion requests and retention requirements; the current service does not provide a verified automated 30-day deletion guarantee.

Runledge never uses Customer Data, prompts, payloads, policies or audit records to train, fine-tune or evaluate any machine learning model — ours or anyone else’s. Runledge sits on the action plane; it does not call language models on your behalf unless you explicitly configure it to, and in that case your provider’s terms and your own zero-retention agreements apply.

The source includes a container build and Kubernetes manifests with an MCP transport sidecar. Customer-hosted deployment requires an independently operated compatible backend and authentication service, runtime secrets and release validation.

Your deployment configuration determines where records, authentication requests and telemetry travel. Running the container inside a VPC alone does not guarantee that no data leaves your network. An air-gapped appliance and published signed container images are not currently provided.

Runledge does not currently hold SOC 2, ISO/IEC 27001 or HIPAA certifications. We will update this section when an independent audit is complete.

Data is encrypted in transit with TLS and at rest by our hosting provider. Contact us if you need a Data Processing Agreement.

We do not sell or rent personal data. We share data only with sub-processors that help us run the service (such as cloud infrastructure and payments), under contracts at least as protective as this policy. A current list of sub-processors and our Data Processing Agreement are available on request, and we notify customers 30 days before adding a new one.

When you join our waitlist, we store your work email, company name and plan of interest so we can contact you about access. We use only essential cookies on this site. You can ask us to delete this information at any time.

Depending on where you live, you may have rights to access, correct, delete, or port your personal data, and to object to its processing. To exercise them, or to report a security concern, contact security@runledge.com. We respond within 30 days.