Service Provider List
Last updated: August 9, 2026
This English version is provided for convenience.
The Japanese version is the authoritative text; if the two differ, the Japanese version prevails. 日本語版を読む
kumaaa LLC uses the following service providers to deliver loopkeep. This list shows each provider's role and whether it handles relayed event bodies or metadata.
Read this list together with our Privacy Policy.
Current service providers
| Provider | Role | Data handled |
|---|---|---|
| Clerk | Sign-in and account management | Does not handle relayed event bodies. Handles email addresses, basic profiles, and authentication and session data. |
| Sentry | Error monitoring for the gateway only | Relayed event bodies are not sent. Handles gateway error and performance data, such as request URLs, stack traces, and traces. Hook tokens are redacted before data is sent. |
| Vercel | Hosting for the website, docs, Console, and control-plane APIs | Does not handle relayed event bodies. Handles account, device, integration, workflow, webhook, run-request, and similar information processed through the Console and APIs, plus operational request metadata. |
| Cloudflare | Gateway and event relay through Workers, Durable Objects, and KV | Handles relayed event bodies and delivery metadata. Event bodies are used only to evaluate triggers and deliver them to devices, and may be held for up to 24 hours while undelivered. They are deleted after delivery or expiry. |
| Supabase | Postgres database hosting for the control plane | Does not store relayed event bodies. Stores account, device-pairing, integration, workflow-name and trigger-condition, webhook, and Console run-request records. Slack access tokens are encrypted; device and webhook tokens are stored as hashes. GitHub tokens are not stored. |
Contact
kumaaa LLC — legal@kumaaa.co.jp