A subprocessor is a company we use that handles personal information for us. Kepler uses the companies below to run the service. Each one handles information on our behalf, to help us run Kepler, as our Privacy Policy describes.
This list covers Kepler on the web, the browser extension, the mobile apps, connections through MCP and keplerbrowser.com.
The companies we use
| Subprocessor | What it does for Kepler | Information it handles | Location |
|---|---|---|---|
| Cloudflare | Runs Kepler’s servers, stores what you save and your chats with Kepler, and fetches the pages you save. Also ranks search results, sends our emails and checks that sign-in forms are used by people. Its AI Gateway is the route to the AI models we use, such as OpenAI’s and Anthropic’s, which write summaries and answers, build views and make search data from your content and questions. | Everything you add to Kepler, your account details, your IP address and request details, the emails we send you, and logs of requests to the AI models. | Worldwide. Cloudflare picks the data centre, usually near where a request or record starts. The AI models run in the United States and other countries where their companies operate. |
| Supabase | Keeps accounts and signs you in. | Your name, email address and profile photo, the spaces you belong to and your invitations, notification settings, device push tokens and billing references. | Sydney, Australia. Support and log data may also be handled in other countries. |
| Neo4j | Keeps a searchable copy of what you save, so Kepler can find it and answer questions about it. | The text of your saved pages and notes, summaries, search data made from them and your chats with Kepler. | Sydney, Australia. Neo4j staff in other countries may access it for support. |
| Stripe | Takes payment for paid plans. | Your email address and the payment details you enter on Stripe’s pages. Kepler never sees your card number. | United States, and other countries where Stripe and its service providers operate, including Ireland and India. |
| Klaviyo | Sends Kepler’s news and product updates. | Your email address and whether you receive our emails. | United States. Klaviyo staff in Australia, Ireland, Singapore and the United Kingdom may access it. |
| PostHog | Shows us how Kepler is used and where it breaks. | The screens and features you use, your device and browser, your IP address, your name and email address, and crash reports. On keplerbrowser.com: the pages you visit, and what you type into help search and feedback. | United States. PostHog’s companies in the United Kingdom and Germany may also process it. |
| Sentry | Tells us when something breaks on our servers. | Error reports, logs and traces from our servers, with account, space and link IDs and request details. | United States (Iowa). Sentry’s companies in Austria, Canada and the Netherlands may also access it. |
| Expo | Sends push notifications and app updates to the Kepler mobile app. Apple and Google carry the notifications to your phone. | Your device’s push token, and the notification text: a space’s name, who added a link, and the link. | United States. App updates also come through Cloudflare’s worldwide network. |
| DiceBear | Draws the default picture next to your name. | Your display name, or your email address if you haven’t set a name, and your IP address, in the request for the picture. | Germany. Pictures are delivered through bunny.net’s worldwide network. |
| TranscriptAPI | Gets the transcript of a YouTube video when you ask Kepler to summarise it. | The address of the video. | Croatia, and the countries where its service providers operate. |
