LegalEffective November 15, 2026
Privacy Policy
runelay runs on your own computer or server, and your data stays there. This page explains the few places where anything passes through us, and what happens to it.
Who we are
runelay is an open source (MIT) MCP gateway: one MCP endpoint that gives your AI agents your connected accounts, skills and memories. It is maintained by Anderson Medeiros and the source is at github.com/Andsu-dev/runelay. It ships as a Docker image, a CLI and a desktop app.
In this policy, “we” means the maintainer of runelay.
runelay is not a hosted service
Each person runs runelay on their own machine or server. Connected-account tokens, memories, skills and settings are stored in your own instance, in a SQLite database, encrypted at rest with AES-GCM.
We have no access to any instance or to the data in it, and we do not collect it.
The OAuth broker at auth.runelay.com
The only part of runelay we host is the OAuth broker at https://auth.runelay.com, a Cloudflare Worker whose source is in apps/oauth-broker of the repository. It exists because some providers, like Google, do not allow dynamic client registration. It does two things:
- It relays the OAuth redirect (the authorization code and state) back to your own instance.
- It adds runelay’s client secret to token exchange and refresh requests and forwards them to the provider.
It has no database and stores nothing. It does not log authorization codes or tokens. Tokens only pass through it in transit, over HTTPS, and go straight back to your instance. PKCE makes a relayed code useless to anyone but your instance.
You can run your own broker and point your instance at it with RUNELAY_OAUTH_BROKER_URL.
Google user data
Each Google service is a separate connector with its own sign-in, and asks only for its own scopes (plus openid, email and profile to show which account is connected). Your instance calls Google’s REST APIs directly:
- Google Calendar (
calendar,calendar.events): list your calendars and events, create and delete events. - Gmail (
gmail.send): send email only. runelay cannot read, search or delete your mail. - Google Drive (
drive.file): create files and list the files runelay created. It cannot see the rest of your Drive. - Google Docs (
documents,drive.file): create, read and add text to documents. - Google Sheets (
spreadsheets,drive.file): create spreadsheets, read and write cells. - Google Slides (
presentations,drive.file): create, read and add slides to presentations. - Google Forms (
forms.body,drive.file): create forms and add questions. - Google Meet (
meetings.space.created): create a meeting space and return its link.
That data is accessed only by your own instance, only when your own agents call those tools, and only to provide the features you asked for.
We never sell it, never use it for ads, never use it to train AI models, and it is never transferred to us.
runelay’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access and deleting data
To revoke access, disconnect the account in runelay, or revoke it at myaccount.google.com/permissions.
To delete your data, remove the connection or remove your instance. The broker holds nothing, so there is nothing to delete on our side.
This website
runelay.com uses Cloudflare Web Analytics, which is cookieless and only reports aggregated numbers. We use no tracking cookies and show no ads.
Changes to this policy
If this policy changes, we update this page and the effective date above. Every change is visible in the GitHub repository.
Contact
Questions about this policy go to GitHub issues. Report security issues privately through GitHub private vulnerability reporting, as described in SECURITY.md.