Sub-processors
Who else touches your data
The providers behind the product, and what each of them can actually see.
Who processes what
These are the providers we use to run AskConcierge. The last column is the one that usually matters: whether that provider can see what an attendee actually typed.
| Provider | What they do for us | Where | Can they see an attendee’s question? |
|---|---|---|---|
| Supabase | The database and file storage the product runs on. | EU — AWS eu-west-1 (Dublin). | Yes — as typed |
| Vercel | Hosting and the serverless functions that answer questions. | EU — the deployment is pinned to dub1 (Dublin). | Yes — as typed |
| OpenRouter | Routes model calls to the language and vision models that write answers. | United States. | Yes — as typed |
| Firecrawl | Reads the organizer’s own website so the concierge can answer from it. | United States. | No |
| Tavily | Searches the public web when an organizer turns that on, for questions their own content cannot answer. Only when the organizer has enabled web search for that concierge. | United States. | Yes — but reworded by the model, not copied |
| Resend | Sends email — sign-in links, invitations, and alerts to the organizer. | EU — eu-west-1. | No |
| PostHog | Product analytics on our own marketing site and the organizer app, and the traces we use to debug and improve answers. | EU Cloud. | Yes — as typed |
This table is generated from the register the running product uses, not maintained by hand beside it. That is deliberate: this register exists because attendee text was once reaching a provider that appeared on no list anywhere, and a page maintained separately from the code would recreate exactly that failure.
What each one receives
| Provider | Personal data they receive |
|---|---|
| Supabase | Organizer accounts; attendee questions until the retention job deletes them. |
| Vercel | Requests in transit; operational logs. |
| OpenRouter | The question being answered and the organizer content retrieved for it. |
| Firecrawl | None from attendees — it receives URLs the organizer gave us. |
| Tavily | A search query. ⚠️ It is written by the model from the question, not copied from what the attendee typed — so it carries the subject of the question and not their words. |
| Resend | The recipient’s email address and the message. |
| PostHog | Organizer usage, behind consent. Attendee questions and the answers given, as LLM traces — and, inside the same traces, the organizer’s own material the answer drew on and the tone instructions they configured. |
Changes to this list
We will tell organizers before adding or replacing a provider that can see attendee content, so there is time to object. If you object on reasonable data-protection grounds and we cannot resolve it, you may end the affected concierge and we will refund the unused part of what you have paid.
Which language model answers a question is configuration rather than documentation — it can change without a code release. That is why this is a register the product resolves rather than a sentence in a contract, and why the row above names the router as well as the model behind it.
To be told when this page changes, write to contact@pulsierlabs.com and ask. We do not have a subscribe button for it yet, and we would rather say that than build a form that goes nowhere.
Something missing here? The FAQ covers the questions people ask most.
Version 1.0 · in effect from 23 August 2026 · English is the governing text
These documents were written by the people who built the product, against the code that implements them, and have not yet been reviewed by a lawyer. Every number in them is read from the part of the system that enforces it. Where we are unsure, we say so on the page rather than leaving it out. All documents