Sub-processors.
Every third party that can access data we process on your behalf, why it is in the path, and what it can see.
The register
| Service | What it does | What it can access | Status |
|---|---|---|---|
| Railway | Application hosting, Postgres database, Redis, and the edge in front of themThe API, workers and dashboard run here; the database and Redis are plugins on the project’s private network. No separate CDN sits in front — the ingest endpoint is reached directly. | Everything: analytics aggregates, account records, session digests. Its edge also terminates TLS, so it sees request IP addresses in transit — the ones FunnelSights itself never stores. | In the path today |
| Resend | Transactional and digest emailUsed for team invitations and the weekly digest, over Resend’s SMTP interface. | Account names and email addresses, and the content of the emails themselves. | In the path today |
| Paddle | Payment processing and merchant of record for subscriptionsOn the account side rather than the analytics path — Paddle never touches the data your sites send. It is the seller of record for the transaction, so it issues the invoice and handles the tax. | Your name, email address, billing address and payment details, and the record of each payment. Paddle holds the payment details; no card number reaches FunnelSights. | In the path today |
| OpenRouter | Model inference for the optional AI featuresReachable only when the LLM switch is on. While it is off, nothing in the product sends data to a model, and this row does not apply to you. | The aggregated report figures included in a prompt. No raw events, and no visitor-level data — none exists to send. | Only when enabled |
| GA4, Search Console and Google Ads connectorsReachable only when the third-party connector switch is on. This is data FunnelSights retrieves from your own Google account at your instruction. | OAuth tokens for the Google properties you connect, and the reporting data retrieved from them. | Only when enabled | |
| Calendly | Calendly connectorReachable only when the third-party connector switch is on. | The API credential you supply, and the booking aggregates retrieved with it. | Only when enabled |
Where processing happens.
United StatesProcessing region
FunnelSights runs on Railway in the United States. The application services and the Postgres database holding your analytics data are deployed there, so processing and storage happen in the US.
For visitors and customers in the EU or UK that is an international transfer, and a contract covering it needs an appropriate safeguard such as standard contractual clauses. It also means FunnelSights cannot be described as EU-hosted.
Visitor location
Location is read from the geo headers an edge proxy adds to the request. No separate CDN fronts the ingest endpoint and no local geolocation database is configured, so where those headers are absent no location is recorded at all. Either way the IP address itself is never stored.
What sits behind this.
Most of what these services could theoretically see, FunnelSights never collects. No cookies, no stored IP addresses or user agents, and no identifier that survives 48 hours.
What we collect, in fullGet a clearer view.
Start with a look at the product — no account needed.