Subprocessors
Last updated:
This list describes Storelift's data recipients, their purposes and processing locations. Optional AI engines carry an explicit condition; their listing does not confirm that they are currently active. Connections you choose are listed separately below.
| Company | What for | What it receives | Where |
|---|---|---|---|
| Amazon Web Services | Hosting, database, sign-in, the API and the collector; email delivery | All account data, including sign-in email and stored connection keys (encrypted with AWS KMS) | Frankfurt, Germany (eu-central-1); email from Stockholm, Sweden (eu-north-1) |
| Polar | Payments and invoices, as merchant of record | Billing email, plan, amount and customer id. Card details go to Polar directly | United States |
| Sign-in with Google, when you choose it | Your Google account email and name at sign-in | United States | |
| Microsoft (Clarity) | Usage analytics on public pages, loaded after the first click or key press | Clicks, scrolls and page views on public pages. Form input is masked; the dashboard carries none | United States |
| Anthropic | Storelift AI answers, review reply drafts, text suggestions and AI visibility checks | Depending on the feature: store details, keywords, review text, your question, conversation and page context, and relevant report data accessed within your permissions. Personal information included in these inputs may also be sent | United States |
| OpenAI — Conditional engine: receives questions only when configured and used for an AI visibility measurement. Listing it here does not confirm that it is currently active. | Optional AI visibility measurements | AI visibility questions built from the selected keywords and query context. Keyword text is sent as entered and can contain personal information. | Account-specific processing location has not been verified |
| Google (Gemini) — Conditional engine: receives questions only when configured and used for an AI visibility measurement. Listing it here does not confirm that it is currently active. | Optional AI visibility measurements | AI visibility questions built from the selected keywords and query context. Keyword text is sent as entered and can contain personal information. | Account-specific processing location has not been verified |
Services you connect
When you connect one of these, data flows between your own account there and Storelift because you asked for it. They act for you, not for us, so they are not subprocessors.
- Apple (App Store Connect, Apple Ads) — Reports and campaigns you connect with your own key
- Google (Play Console, Analytics, AdMob) — Reports you connect with your own Google account, read-only
- RevenueCat — Subscription figures you connect with your own key
- Slack — Alerts sent to the channel you choose
- Telegram — Alerts sent to the chat you connect
- Discord — Alerts sent to the Discord channel you connect
- Adapty — Subscription events Adapty sends to your Storelift webhook
- PostHog — Daily users, sessions and countries you connect with your own key, read-only
- Amplitude — Daily users, sessions and countries you connect with your own keys, read-only
- AppLovin MAX — Ad earnings you connect with your own report key, read-only
- Superwall — Subscription events Superwall sends to your Storelift webhook
Get notice of changes
We email this list 30 days before a new subprocessor starts processing personal data. One email per change.
AI visibility engines
AI visibility questions are built from the keywords you track; the keyword text is sent as written. Alongside Anthropic, the API measurement supports OpenAI and Google Gemini. The table names the optional engines and the conditions under which questions can reach them. It does not establish their current activation, accepted account terms, retention settings or processing location. Copying a question into an assistant's web interface and manually importing its answer is a separate workflow; Storelift does not make a provider API call in that workflow.
What changed
- — Listed the supported OpenAI and Google Gemini engines with their conditions. This inventory clarification does not establish activation, an account configuration or a processing start date.
- — Described when the OpenAI and Google Gemini engines receive AI visibility questions; no new provider added in this update.
- — Clarified the input and report data sent to Anthropic; no new provider added in this update.
- — List published at /legal/subprocessors/.