Device management gives you an inventory of the machines Sprecho runs on in your organisation, a policy that applies to all of them, and a way to shut one down when a laptop goes missing.
It sits in the Enterprise console at enterprise.sprecho.ai under Device Management, and is available to team owners and admins on the Enterprise plan.
What enrolment does
There is nothing to install and nothing to pre-configure. When someone signs in to Sprecho on a machine, the app enrols it into the team that account belongs to, and from then on it appears in your device list.
What is recorded is deliberately narrow:
| Stored | Not stored |
|---|---|
| A one-way hash of the OS device identifier, computed with a salt unique to your team | The raw device identifier |
| App version, OS version, update channel | Any dictation content |
| First and last seen timestamps, status | Location, network, browsing or file activity |
| Hostname — only if you enable it in the policy and the user consents | Hostname by default |
Because the hash uses a per-team salt, deleting the team destroys the salt and the hashes become underivable. The device is shown a plain-language notice explaining that its IT administrator manages the installation.
If you set a maximum number of devices per user, the oldest devices beyond that limit are revoked automatically.
The heartbeat
Each enrolled device checks in every six hours, and once immediately after sign-in. The check-in sends the device hash, the policy version it has already applied, and the current app version, OS version and update channel.
The server replies with the policy — but only when it has changed since the device last applied one — plus any pending action and the device's current status. So a policy change reaches the fleet within six hours without anyone polling constantly.
A device that has been offline for a while is not "gone". Devices that have not checked in for 60 days are revoked automatically, which keeps the inventory honest about which machines are actually in use.
What you can put in a policy
One policy applies to every device in the team. It covers:
- Locks — screen awareness, automatic learning, contributing anonymised training data, and whether personal use is allowed. Each can be left to the user, forced on, or forced off.
- Allowed languages and models — restrict what people can select.
- Allowed hours — a working-time window, with a warning by default rather than a hard block, in a time zone you choose.
- Updates — automatic updates on or off, the channel (stable, beta or a pinned version), and how long someone may keep working after a forced update is requested. See roll Sprecho out with Intune or Jamf.
- Data collection — whether hostnames, OS versions and app versions are collected. Hostnames are off by default.
- Audit retention — how long routine and security events are kept, with German commercial-record retention periods as the defaults.
- Maximum devices per user.
Every change to the policy is written to the audit log with a field-by-field record of what changed and who changed it.
Remote actions
From a device's entry you can:
| Action | Effect |
|---|---|
| Disable | The device stops allowing dictation but stays enrolled |
| Enable | Reverses a disable |
| Wipe | The app deletes its local data on that machine. The device stays in the inventory |
| Force update | The device installs a specific version, with the grace period from your policy |
| Remove | Revokes the device. It wipes its local data and stops working |
Actions are queued and applied at the next heartbeat, so allow up to six hours — or ask the person to sign out and in again if it is urgent.
Removing a device does not free the licence seat. The person keeps their seat and can sign in on another machine. To take the licence back, unassign it or remove them from the team — see how Enterprise licences and seats work.
The audit log
Every enrolment, policy change and remote action is logged, split into routine and security events. The log can be filtered by severity and date range and exported as CSV or JSON, which is usually what an auditor asks for.
If the team stops being Enterprise
Policies do not vanish the moment a subscription lapses. They stay in force for a 30-day grace period, and only then do the locks lift on devices. The policy itself is preserved, so restoring the plan restores the configuration.