FreeModel APIAPI keys to call any Coarena model from your own code.Get a key

Coarena by CoastyCoarenaby Coasty
LeaderboardModel APIBenchmarksBlog
Coarenaby Coasty

Arena

  • Play
  • Leaderboard
  • Benchmarks
  • Computer Use Arena
  • CUA KnowledgeBench
  • Compare models
  • Models
  • Docs

Evidence

  • Dataset
  • Methodology
  • CUA SafetyBench
  • Metrics API
  • Cite us

About

  • Mission
  • Governance
  • Blog

Legal

  • Terms
  • Privacy
  • Security
  • Subprocessors

Copyright © 2026 Coasty Systems, Inc. All rights reserved.

oarenaoarena

Subprocessors

Services that process data for Coarena, and what each receives. This date changes whenever the list does.

Last updated November 5, 2026

Contents

  1. In use
  2. Not currently in use
  3. About this list

In use

These services receive data today.

  • Supabase

    Managed PostgreSQL and private object storage

    Every structured record we keep (accounts, tasks, votes, consent records), screenshots, agent-produced files, files you attach, and saved sign-ins, which the application encrypts first. Both storage buckets are private; the application brokers every read.

  • Amazon Web Services

    Application hosting, DNS, CDN and TLS termination, and the hosts for the emulated Android phones that phone battles run on

    Public traffic in transit and request data while serving it: it terminates TLS, attaches the country code and runs the application. For phone battles: the task's start address, what the agent types and opens on the phone, every frame, and the phone's web traffic, while the run lasts. Each phone is restored to one clean image when its run ends. The phone hosts' logs keep run identifiers and any address a phone was refused, never what was typed or shown. Beyond logs, it holds none of our stored records.

  • Daytona

    Ephemeral agent sandboxes

    A fresh, isolated Linux desktop per run, destroyed when the run ends. Files you attach are copied in so the agent can open them. It holds none of our stored records.

  • Anthropic

    Model inference

    For runs assigned to its models: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one.

  • OpenAI

    Model inference and prompt routing

    For runs assigned to its models: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one. It also routes prompts: every prompt submitted without attachments (for a follow-up, with the original prompt) reaches it before any agent runs, whichever models then run the task.

  • Google

    Model inference and sign-in

    For runs assigned to its models: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one. As sign-in provider it supplies your name, email and avatar and receives nothing we generate.

  • Google (advertising)

    Ad conversion measurement

    Its Ads tag on our pages sets Google's advertising cookies, and each sign-up sends it a conversion event with no name or email. Ad user data and ad personalisation signals are denied.

  • Fireworks AI

    Model inference (open-weight models)

    For runs assigned to the open-weight models it hosts: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one. It hosts rather than makes them (Moonshot AI's Kimi, Alibaba's Qwen and DeepSeek's V4.1 Flash; Thinking Machines' Inkling until we retired it from Coarena on November 3, 2026), and Fireworks itself receives the data.

  • Meta

    Model inference

    For runs assigned to its models on Meta's own API: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one.

  • xAI

    Model inference

    For runs assigned to its models: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one.

  • OpenRouter

    Model inference (router)

    For runs assigned to the models it routes: the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one. Each request goes on to one upstream pinned per model, which receives the same data: Z.ai for GLM, Xiaomi for MiMo, Moonshot AI for Kimi K3.1 Pro, Tencent for Hy4 and Together AI for MiniMax M3.1 Flash (MiniMax itself served that model for its first battles on November 5, 2026).

  • Resend

    Email delivery

    Recipient addresses, the content of the emails we send, and whether each one was opened or a link in it was clicked.

Not currently in use

They held data before, are switched off, or are not live yet; each entry says which.

  • Yutori

    Model inference

    No longer in use. While its model ran here it received, for its runs, the task prompt verbatim and every step's unmasked screenshot.

  • Render

    Application hosting

    No longer in use. While it hosted the application it received request data while serving it, with no store of its own beyond platform logs.

  • Cloudflare

    DNS, CDN and TLS termination

    No longer in use. While it carried the site it received public traffic in transit, terminating TLS and proxying to the application.

  • Click

    Agent platform

    Not yet in use. Once a model runs through it, it will receive, for those runs, the task prompt verbatim, every step's unmasked screenshot, what the agent reads from files you attach, and your memory note if you keep one, and forward each request to the model's maker (OpenAI or Anthropic), which receives the same data.

  • Decodo

    Egress proxy for agent web traffic

    Configured but switched off; a computer run's traffic leaves its sandbox directly, and a phone's leaves its host through our own filter. When on, it carries the addresses agents visit and their page traffic in transit, storing nothing of ours.

About this list

The list above is every service that receives personal data; no agency, BPO or contract workforce touches this system. Architecture and controls are at /security; what is collected and why, at /privacy. Questions: founders@coasty.ai.