Privacy Policy

Marketing site

The marketing site uses Vercel Analytics to understand aggregate page and conversion activity. Marketing events are fixed action names and must not include prompts, code, API keys, credentials, or account identity.

Local inference

RunAnywhere's local SDK and accelerator paths execute on the device you choose. Wally is a separate, explicit hosted path.

The SDK sends usage telemetry to RunAnywhere so we can measure performance and fix problems: which model and framework ran, the device model, operating system and SDK version, timings, token and character counts, and whether a request succeeded or failed. Events are tied to a random device identifier the SDK stores on the device. Telemetry never includes the text of your prompts, the model's outputs, or your files; for text it records only lengths and counts.

Wally: zero data retention

Hosted requests send your prompts to RunAnywhere for processing. Production Wally runs with zero data retention (ZDR) by default for prompt and completion bodies: we do not store the text you send to a model or the text it returns, whether it arrives through the API, the Wally CLI or a coding agent. The one exception is the console playground, which keeps your recent conversations so they are there when you come back, as described under Console account data. Usage records, including token counts, timestamps, model, request ID, and spend, are separate from those bodies and are used for billing, abuse prevention, and support.

You can request deletion of account data by emailing us from the address on the account. Deleting an account does not itself delete usage or billing records we keep to meet legal, tax, and accounting obligations.

Console account data

Signing in with Google or GitHub gives us the account identifiers those providers share (name, email, avatar). Payment details are handled by Stripe; we do not store card numbers. The console keeps recent playground conversations in your own browser's storage so they are there when you come back. That history lives on your device, not on our servers. You can clear it from the console, and clearing your browser data removes it.

Model access applications

Some models require approval before an account can call them. When you apply, we collect your name, contact email, organisation or professional profile, intended use, the scope you are authorised to test, and your attestation that the scope is accurate. We use it to review the request and to prevent misuse. RunAnywhere staff who review applications can see it. We record each decision and the reason for it. Programme requests run with zero data retention for prompt and completion bodies, like every Wally request.

Who we share it with

Processors run parts of the service and each sees only what its job needs. Stripe takes payments. The account and billing database stores identity and ledger records. Cloud infrastructure providers host and serve the models. Vercel serves this site. The console is served at console.runanywhere.ai. PropelAuth handles sign-in, and Resend sends transactional email. We do not sell your data, and nobody outside that list receives it except where the law requires it or we must protect the service and its users.

Security and compliance

We take reasonable steps to protect your data, including encryption in transit and access controls. A SOC 2 Type 2 audit is in progress; we do not have a SOC 2 report yet.

To report a security issue, email security@runanywhere.ai.