Keep every lead, every article and every account, whether you stay or go.
The Command Center reads accounts you already own, through access you grant and can revoke in your own consoles. Leads land in your sheet and content in your Drive the moment they are made, so nothing waits on an export.
Which of my accounts do you read, and how?
Three ways in, and every one of them is access you grant. Google Analytics 4, Search Console, Google Ads and your Business Profile are read through a manager invitation you add in each console and can remove in the same place. Your CRM, Stripe, your booking platform and your email platform are connected by our team from the inside, with access you grant during setup; there is no wizard and nothing for you to paste. Your website's forms reach the screen through the lead sheet your own site writes. We never hold a password of yours.
Each source is read for a specific set of things. Analytics gives sessions, sources, pages and key events. Search Console gives queries, impressions, clicks, average position and top pages. Google Ads gives campaign spend, conversions, cost per conversion and the account's change history. Your Business Profile gives reviews, rating and listing performance. Your CRM gives pipeline stages and sources. Stripe gives payments, subscriptions and recent charges, read only. Your booking platform gives jobs and the job pipeline. Your email platform gives campaign statistics. The Integrations page carries the full list, one page per connection.
Each source has a freshness ceiling, and the screen states it. Your CRM, Stripe, your booking platform, website leads and email statistics read live. Google Ads and Analytics intraday figures run hours behind, on Google's schedule. Search Console publishes two to three days after the fact. Meta reports on Meta's schedule.
Not read on any account: your email inbox, your calendar, your customers' card data. Stripe holds the cards; we read the payment record. A phone call counts as a lead only when your CRM records it.
Where is my data stored?
In five places, and the two worth keeping are yours. Your dashboard snapshot, the numbers on the screen, is served from a managed cloud service. Your lead rows live in the lead sheet your own website writes, in your Google account. Your content is filed as Google Docs in a Drive folder that is yours. Your connection map, the record of which of your accounts is which, is a per-client record with us; it is what keeps an owner with two businesses from ever seeing a merged number. Lead outcomes and the requests you send from the screen are kept server-side behind the same gate as everything else.
A copy of your numbers also ships with the page. Every night at 12:01am Central one job writes a fallback snapshot for every client and deploys it with the dashboard, so there is something to read the instant it opens. A failed pull or a failed syntax check leaves the previous page up. Nothing empty or broken is ever deployed.
The demo is the exception, and it holds nothing of anyone's: the company on demo.trulata.com is fictional and every number is illustrative.
How old is the number I am looking at?
As old as the stamp beside the title says. Open your dashboard and it renders last night's snapshot before any network call returns, then fetches the live payload from a cache. If that payload is older than five minutes, a pull of your sources starts behind the page and the numbers swap in when it lands. Ten people opening at 9am cause one pull.
Hover the stamp and it says one of two things: the numbers were pulled live when you opened the page, or the live refresh was unreachable and you are reading the last saved snapshot. Staleness is never invisible.
Refresh starts a real pull. Press it and our service begins reading your sources and answers at once; a pull takes 2 seconds to a little over 3 minutes depending on which accounts you connect, and the page reloads when the stamp moves. It never shows an error. A slow source, an unreachable service or a timeout all end in a reloaded page whose stamp says how old the data is.
Who can see my numbers?
People who hold a seat on your account, and the TruLata team that runs it. Nobody else. Your dashboard is its own site on its own hostname behind its own gate. A person passes two checks before a byte of it is served: an access gate that confirms who they are, and our seat list that confirms they belong on this account. Sign-in is a single-use link from login.trulata.com sent to the address on the seat.
Take a new office manager. Open the Team view, type their email, choose Member or Admin, press Invite. They receive a sign-in link and they are in. When they leave, press Remove beside their address, and within 30 seconds every request from it gets a refusal page. The view shows seats used against seats on your plan and says so when the plan is full. Seats by plan: three on Starter, three on Launch, ten on Growth and unlimited on Command.
Another client cannot see your dashboard. A login minted for one dashboard and presented to another is refused, and that refusal never relaxes. Before every deploy, a preflight fails if another client's name appears anywhere in your instance. That check exists because it happened once, in a file a client could read.
If our seat service does not answer, you stay in. A person who has already passed the access gate is allowed through and the decision is logged, so a blip on our side never locks you out of your own numbers. Two refusals hold in every case: a wrong audience and a login with no email identity.
Can anything on the screen change my accounts?
No. The screen writes to four places, and none of them is your ad account, your CRM, your website or your Business Profile. Ask a question in the assistant view, where it is offered. Set a lead outcome. Request a website change. Request a content, keyword, category or targeting change. Everything else reads.
A lead outcome is the one that touches your own data. On the Leads view, mark a row as not a lead, choose why (existing customer, spam or sales pitch, wrong number, out of area, other), add a note, and it is written to that lead's record. Marked rows are used to claim Google refunds and to sharpen targeting.
A request goes to a person. It lands with your TruLata team, is logged with who sent it, and a person makes the change in the account that holds it. Stripe is read only on every instance; nothing here creates a charge or a refund. Budget and bid changes in your ad account are made by a person, never by a scheduled job, and every change there is read the next morning by the change watch.
What does the assistant see when I ask it a question?
Your question and your own numbers. Where the Ask view is offered, the question goes to a model API together with the same data every view on your dashboard renders, fetched per request, so the answer matches what you are looking at. Nothing from another client is in that context, because nothing from another client is in your instance.
The view is being reworked and is not offered on every account until it answers reliably. The Platform page says so rather than hiding it. Where it is offered, it sends your question and returns an answer, and it changes nothing in your accounts.
What runs on my data when nobody is at a desk, and what waits for a person?
Five jobs run on a schedule whether anyone is at a desk. Every night at 12:01am Central the fallback snapshot is baked for every client from one registry. Every morning at 7:05am ET the ads change watch reads your Google Ads change history and the account's user list, because a change event does not record who was granted access. Every morning at 7:20am ET, where your forms feed the lead sheet, the lead watch runs five checks on the lead flow. Where the content engine runs, on Launch, Growth and Command, topics pass a demand gate on real search volume and each piece is filed as a Google Doc in your Drive. Where the outbound engine runs, on Command, prospects are sourced weekly to the target profile set with you.
The lead watch exists for one shape of failure. On one account, a tag change silently stopped every conversion for six weeks. 21 real leads landed on the sheet while Ads reported zero, and the owner paused the campaign that carried every counted lead and cut its budget 90 percent. The watch reads the sheet because a form submission is a fact and a tag firing is not.
What waits for a person: budget and bid changes in your ad account, and every change request from the screen. Prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged with the draft, the mailbox and the time. Replies are classified, and a not-interested reply or a bounce suppresses the address.
What happens to my data if I stop?
You keep everything worth keeping, because it was written to your accounts as it was made. Content went to your Drive folder as each piece was filed. Leads went to the sheet your own site writes. Both were in your Google account from the first day, and they stay there.
Leaving is three actions. You remove our manager access on your Analytics property, your Search Console site, your Ads account and your Business Profile, in the same consoles where you granted it. Your seat list is emptied, so no sign-in link works against your dashboard. Your snapshot and your connection map are removed from our service. Every tier is month to month, so there is no term to run out.
There is no export to request. The snapshot on our service is a rendering of your accounts, and your accounts are still yours.
What should I check before I buy?
Open demo.trulata.com and look at four views. There is no form in front of it, the company is fictional, every number is illustrative, and the code is the same engine every client runs.
Leads. Rows arrive newest first, and the note above them says each one is also emailed to your team the moment it arrives. Click a row for the full message, the phone, the email and the page it came from. On your instance the same view reads the sheet your site writes and filters out our own test submissions before you see the list.
Integrations. On the demo every source shows Connected or Connect. On your instance the view lists what is integrated and nothing that is not, and a request for another connection goes to your team.
Team, then Website. Team shows seats used of plan seats and the invite box with the roles Member and Admin. On Website, press Request a website change and a box opens that says it goes straight to your TruLata team; on the demo the send is simulated and the toast says so. Those boxes and the outcome control on Leads are the write surface, and you can find all of it in ten minutes.
Your data, in one table.
| What | Where it lives | When you leave |
|---|---|---|
| Dashboard snapshot | Managed cloud service, with a nightly fallback copy shipped with the page | Removed from our service |
| Lead rows | The lead sheet your site writes, in your Google account | Yours |
| Content | Google Docs in your Drive folder | Yours |
| Connection map | With us, one record per client | Removed from our service |
| Google account access | Manager invitations you grant | Removed by you, in each console |
| Inbox, calendar, card data | Not read | Never held |
Content lands in your Drive and leads land in your sheet the moment they are made, so leaving is revoking access, not negotiating an export.
Questions, answered.
Do you read my email?
No. Neither your inbox nor your calendar is connected on any account. The only mail involved is the one your own form handler sends your team when a lead arrives.
Where are my leads stored?
In the lead sheet your own website writes, in your Google account. The Leads view reads it newest first, and your team is emailed each submission the moment it lands.
Can another client see my dashboard?
No. Each dashboard is its own site on its own hostname behind its own gate. A login for one dashboard presented to another is refused, and a preflight before every deploy fails if another client's name appears anywhere in your instance.
What does the assistant send to the model?
Your question and your own dashboard's numbers, fetched per request so they match the screen. Nothing from any other client.
Can you change my ad account or CRM from the dashboard?
No. Nothing on the screen writes to Ads, your CRM, your site or your Business Profile. A request goes to a person and is logged, and budget and bid changes are made by a person, never by a scheduled job.
How do I know how old a number is?
Read the stamp beside the title. It shows the time of the pull on screen, and hovering it says whether the numbers were pulled live when you opened the page or the live refresh was unreachable and you are reading the last saved snapshot.
What do I keep if I leave?
Your Drive folder of content, your lead sheet, and your own accounts with our manager access removed by you in each console. There is no export to request.
Do you hold card data?
No. Stripe holds it. We read payment records, never cards, and the connection is read only.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.