With Otukan, you decide who can access fleet data and administer the service. You choose where management data is hosted. Your administrators, help desk and auditors each get their own role. Otukan’s support staff reach your tenant only when you approve it, for a named case, and every action is logged where your auditors can read it. Otukan also maps the flows that hosting alone does not settle, such as backups, logs and the Apple and Google services that carry management traffic, and agrees retention, export and exit before the first device enrols.
Control map
Data storage, administrative access and key custody are three separate questions. Otukan answers each one explicitly, so data held in your chosen location is also administered by the people you choose.
| Control | What Otukan provides |
|---|---|
| Data storage | Management data, backups and logs held in the location you choose, with each store mapped |
| Platform services | A clear list of the platform services in the data path: Apple’s push notification service for Apple devices, and Google services for Android Enterprise |
| Administrative access | Your administrators administer the fleet; Otukan support acts only with your approval |
| Key custody | Custody of encryption and signing keys agreed per hosting option and written down |
| Certificates and tokens | Platform credentials held in your organisation’s accounts, not Otukan’s |
Platform credentials matter more than they first appear. For Apple devices, the push certificate and the Apple Business Manager token belong to an organisation account. For Android Enterprise, the enterprise is bound to an organisation’s Google account or domain. Otukan keeps these in your organisation’s name, which keeps any future move in your hands.
What a management service holds
Inventory (model, serial number, OS version), assigned user, installed managed apps, policy status and an event log of administrator actions. On personally owned devices the platforms limit what is visible by design, and Otukan holds only the user and device identifiers that management needs.
What you receive in writing
Otukan gives you a data-flow map per platform, the list of services that process fleet data and where each runs, and a sample of the administrator audit log. On a pilot tenant you can run a test export and a test deletion yourself. These answers become part of the contract.
Roles
Administrative access to a management service is access to every managed device: it can change policy, install apps and, on corporate-owned devices, wipe them. Otukan separates those rights.
- Fleet administrators. Change policy and app assignments for the groups they own.
- Help desk. Look up devices and run limited actions such as lock or passcode reset.
- Auditors. Read configuration and logs, with no right to change them.
- Break-glass account. Full rights for emergencies, credentials held under dual control, every use flagged for review.
Roles are scoped to device groups as well as to actions. A regional administrator can manage the devices in that region without reaching the rest of the fleet, and a help desk operator can lock a lost phone without being able to change policy. Separation of duties is built into daily work rather than added on top.
Supplier support access
Otukan support has no standing access to your tenant. When a case needs it, access is requested, approved by your administrator, limited in time and logged. The log is readable by your auditors, not only by Otukan, and Otukan tells you where its support staff are located.
Otukan’s wider approach to security and trust is covered on Otukan security and trust.
Lifecycle
Control over fleet data has to hold for the life of the contract and after it ends. Otukan agrees each duty below before rollout.
| Stage | What is agreed |
|---|---|
| Retention | How long device records, logs and backups are kept, and who can change that |
| Export | Which data you can export on request, in which format, and how often |
| Deletion | How data is deleted at contract end, including backups, and how deletion is confirmed |
| Device exit | How devices are released or moved to another service; on both platforms this usually means re-enrolment |
| Credentials | Transfer or revocation of platform accounts, certificates and tokens held for your organisation |
The exit plan is written before the first device enrols. Where the service runs, who operates it and how you leave are covered together on deployment and integrations. The parent overview is mobile device management.