Nerve FAQ

We can't see your data, and neither can anyone on our team. When you ask a question, Nerve's system sends an API request to Meta, TikTok or Google and hands the answer straight to your screen. No person at Nerve looks at it, and no database keeps it. Think of a phone line: it carries the call, but it doesn't listen or record.

No. Only Nerve's system makes the API request, and the response goes straight to your screen. No human on our team sees it, and no database stores it.

Only when you ask it to. Before Nerve creates, updates, pauses or deletes anything, it tells you exactly what will change and waits for your yes. GA4 is read-only, so nothing there can be changed.

No. You sign in on Meta's, TikTok's or Google's own page and approve access there. Nerve receives a token, never your login details.

Yes. If you run several accounts, or a manager account with child accounts under it, Nerve asks which one you mean instead of guessing.

Meta, TikTok, Google Ads, and GA4. Each one works the same way: a live call to that platform's own API, every time.

No. Spend, impressions and creative details are pulled from the platform when you ask and aren't written to a Nerve database. They exist for the length of the request.

One thing: the encrypted token that lets Nerve make the next call on your behalf. It holds access, not data.

Every request goes to the platform's API again, so there is no stale copy on our side. What you see is as current as the platform's own reporting, which can still lag on some metrics.

It streams straight to your screen. Once the request completes, Nerve doesn't write it anywhere. Ask again and Nerve fetches it again.

Nerve tells you the account needs reconnecting. It won't fall back on old numbers, because there aren't any saved to fall back on.

A small one. With no stored copy, Nerve depends on the platform's API being available, and it's subject to that platform's own limits. That's the price of never holding your data.