Last updated September 21, 2026
This is an interim document written in plain language by the team that runs the app. It has not been reviewed or certified by an attorney. It describes what the app does today and will be replaced when a reviewed version exists.
Team Panda is a private operations app for one team: tasks, vehicle pre-checks, fleet, stock, sales, contracts, customers and a read-only money view. There is no public sign-up. An admin creates each seat, and only signed-in, active seats can see any data.
Your seat: name, email address, role and the permissions your admin gave you. Your password is handled by our authentication provider; the app never sees or stores it in readable form.
The records the team enters: tasks, pre-check answers, vehicles, stock items and adjustments, sales, contracts and payment schedules, customer contact details, and feature requests. Records are tagged to a company, and a seat only sees the companies it belongs to.
Connecting QuickBooks is optional and only a seat with the Money connect permission can do it. We request one scope, com.intuit.quickbooks.accounting, and use it read-only.
What we read: the company name, open invoices and open bills (number, customer or vendor name, dates, total, balance, currency) and the Profit & Loss report. We keep a cached copy so the Money page can show it, and only seats with the Money permission who belong to the linked company can see it.
What we never do: create, change or delete anything in QuickBooks, request payment scopes, or move money.
The QuickBooks access and refresh tokens are stored server-side only and are never sent to the browser. Disconnect on the Money page erases the stored tokens and hides that company’s cached data. You can also remove the app’s access from inside your Intuit account at any time.
When a QuickBooks request fails, we log Intuit’s transaction id (intuit_tid), the HTTP status and Intuit’s error message so the problem can be traced. Tokens and financial figures are not written to those logs.
The app is hosted on Vercel, and its database and sign-in run on Supabase. QuickBooks data comes from Intuit when a company is connected. The booking page embeds Calendly. If an admin turns on the optional AI assistant, the question you type and the context it needs are sent to OpenRouter to get an answer, and team documents an admin attaches are read from Google Drive.
We do not sell data, show ads, or share data with anyone for marketing.
Records are hidden (archived) rather than erased so the team keeps its history, and ledgers such as stock adjustments are append-only. Removing a seat turns the sign-in off; it does not erase the history that seat created. There is no self-serve erase yet: to have your data corrected or removed, ask your team admin.
The app sets the cookies needed to keep you signed in. It sets no advertising or tracking cookies.
Ask your team admin, who is the person that gave you your sign-in. When this page changes, the date at the top changes with it. Using the app is also covered by the Terms of Use.