Teams changed.
Keep your setup.

No. Call State never asks for a Microsoft login and never receives, stores or uses Microsoft access or refresh tokens — the short-lived keys an app uses to stay signed in. It is an independent tool, not affiliated with Microsoft, and never signs in to Teams for you. You sign in with your Call State email and password only. See what leaves your computer.

Because the permission is broad: your operating system cannot limit it to one program. Call State uses it only to read the buttons in your Teams window — not to read other programs, and not to read your screen contents. You can take it away in your system settings; the app then cannot show your Teams status. See what leaves your computer.

No. Call State does not join your meetings, so it cannot hear or record anything. It does not record audio or video, take screenshots, read your screen, messages, files or documents, or create transcripts. It does not read your calendar or contacts either. It reads only the fixed names and on/off states of the buttons in your Teams window. See what leaves your computer.

Your account holds your email address, a value made from your password — never the password itself in readable form — and plan and billing details. The keys that keep you signed in are Call State’s own and stay in the password safe of your operating system. Payments run through Stripe: you type your card details on the Stripe payment page, they go straight to Stripe, and Call State never sees them.

Your status travels through the Call State service so your other devices can show it. The service handles it in readable form, protected on the way by the same encryption as any secure website. It is not a setup where only you can read it. The service only passes it on: no stored status, no history, no sale, no advertising. Only clients signed in to your account receive it.

Not automatically. Your tool must support the retired local Teams connection, and compatibility depends on the features it uses. Test your own setup with Teams Emulation during the 7-day Paid trial before subscribing. The compatibility guide explains the retired API and the replacement.

Start with the desktop app for Mac or Windows, Microsoft Teams and a Call State account. No Microsoft login is involved. Complete the permissions setup and connect your chosen display or automation. Status sharing and commands require a working connection to the Call State service.

No. Dedicated Call State plugins for both platforms are planned and are not available in either plan today. A Paid subscription gives you Teams Emulation for compatible existing tools, not access to those planned plugins. Test your existing tool during the 7-day trial before subscribing.

Browser extensions are planned, not available yet. Chrome and Edge are the first browser targets; Firefox and Safari remain under consideration. The desktop app is the starting point today.

Controls depend on a reachable Teams meeting interface. A blocking dialog, a minimized meeting window or missing permissions can prevent an action. Call State cannot guarantee control when Teams makes the relevant button unavailable. In the status data, “whether a control can be used right now” tells you whether the button can be pressed at this moment; if it cannot, Call State refuses the action instead of pretending it worked.

You move to Free unless you choose a paid subscription. The desktop app, CLI and REST remain available, but Teams Emulation turns off and you need to sign in again every 24 hours. Free accounts without any paid subscription are deleted after 30 days without use; accounts that ever paid are deactivated instead, so their invoices stay available.