Recala uses the providers below to run the service. Each one may process customer data for the purpose shown. This list covers providers that handle your content or account data; it does not cover Recala's own tools for writing code or internal notes. Pages on recala.co also load fonts from Google Fonts and style files from jsDelivr, which receive the visitor's IP address.
General Authorization
By using Recala, you give general written authorization for the providers listed on this page to process your data on our behalf. We do not send individual notices when the list changes. We update this page when we add or replace a provider, and the date at the top shows the latest change. If you have a concern about a provider, write to hello@recala.co. See also the Privacy Policy, the Terms of Service and the Security Overview.
Infrastructure
- Supabase
Purpose: database, authentication and file storage.
Data: account details, workspace settings, articles, uploaded documents and operational records.
Location: European Union (Frankfurt). - Railway
Purpose: application servers that run the Recala API.
Data: the data the API handles while it works, and server logs.
Location: European Union (Amsterdam, Netherlands). - Upstash
Purpose: live progress updates and locks for the Recala API.
Data: progress events of article runs (including the article topic and short error messages, kept for 24 hours), and lock and duplicate-submission keys. - Netlify
Purpose: hosting and delivery of recala.co.
Data: request details such as IP address, sign-in and sign-up form data passing through the web servers, and session cookies. - Cloudflare (Turnstile)
Purpose: abuse protection on sign-in and sign-up.
Data: the challenge response and the connection details needed to check it, such as IP address.
AI Model Providers
- Anthropic (Claude)
Purpose: reviewing and comparing article drafts in our quality checks. We are moving more language-model tasks to this provider.
Data: article drafts and briefs, passages of your knowledge material, brand information and author byline details.
Location: United States. - OpenAI
Purpose: language-model tasks such as planning, drafting and review of articles, and image generation.
Data: article briefs and drafts, image prompts, passages of your knowledge material and brand information. - Google (Gemini)
Purpose: some language-model and embedding tasks. We are moving away from this provider.
Data: prompts and passages of your knowledge material for those tasks.
Research and Brand Data
- Exa
Purpose: web research and topic discovery.
Data: search queries, company domains and page URLs. - Serper
Purpose: Google search results for topic and gap analysis.
Data: search queries, which can include topic, company and competitor names. - DataForSEO
Purpose: search-result and keyword data.
Data: keywords, queries and domains. - Firecrawl
Purpose: reading the content of public web pages when they cannot be read directly.
Data: URLs of public pages. - Brandfetch
Purpose: finding a company's logo and brand colors.
Data: the company domain.
Payments and Invoicing
- Stripe
Purpose: payments and subscriptions.
Data: billing name, email, address, tax ID where provided, subscription and payment events. Card details are entered with Stripe. - Holded
Purpose: invoicing and accounting.
Data: customer company name, billing contacts, invoice lines and tax ID.
Monitoring and Analytics
- Sentry
Purpose: error monitoring.
Data: error traces and messages, page and request URLs, browser details and a sample of performance traces, from the website and the API. Error events from the website are stored in the European Union (Frankfurt). - PostHog
Purpose: product analytics, only if you accept analytics cookies.
Data: your internal account ID (never your email or name), page views and feature usage.
Location: European Union (eu.i.posthog.com).
Services You Connect
These receive data only when you connect them to your workspace.
- Google (Sign-In and Search Console)
Purpose: signing in with your Google account, and reading your Search Console data if you connect it, and submitting your sitemap only if you give that extra consent.
Data: your Google name and email, and the Search Console data described in the Privacy Policy. - WordPress and other publishing destinations
Purpose: publishing approved articles to the site you connect, such as WordPress.
Data: article content, author byline and the access credential you provide.