Evaluate work app data controls by tracing every way corporate data can leave a work app, then checking who enforces the rule on each path. Otukan enforces it inside the protected app. It governs copy and paste, sharing and open-in, screen capture and local storage, with rules set per app and per screen, and keeps approved work-to-work paths open so staff can still do their jobs. Stored data is encrypted and cleared at sign-out. The controls apply on managed and personal phones alike, are built separately for Android and iOS, and cover only the work app’s data, never personal content.
Where these rules fit among other staff app controls is shown on enterprise application protection.
Threat and buyer task
Data rarely leaks through a dramatic breach on a phone. It leaks through ordinary actions that nobody governed.
The affected flows
A sales manager copies a customer’s details into a personal messenger. A nurse screenshots a shift list to send to a colleague. A contractor opens a quotation spreadsheet in a personal cloud app to read it offline. Each action is convenient, and each moves corporate data to a place your organisation cannot see, retain or delete.
The trust boundary
The boundary is the edge of the work app. Inside it, data is under your policy. Outside it, on a personal phone, it is under the phone owner’s control. Data controls decide what may cross that edge, in which direction and to which destination.
| Path out of the work app | Everyday cause | Otukan rule |
|---|---|---|
| Clipboard | Copying details into another app | Paste only into approved work apps |
| Screen capture | Screenshots to share or remember | Block capture on Android; cover content and report on iOS |
| Share and open-in | Sending a file for convenience | Approved destinations only |
| Local storage | Offline access and cached records | Encrypt, then clear at sign-out |
| Memory | Values readable while in use | Clear after use, watch for hooks |
Control fit
The app
The work app knows which screen is showing and what data is on it. That is why Otukan enforces rules in the app: it can treat a customer record differently from a menu, and act at the moment the user copies, shares or captures.
The operating system
Android and iOS each offer their own separation. Android provides the work profile on managed devices; iOS provides managed apps and managed open-in. Otukan works alongside these boundaries where they exist and applies its own rules where they do not, which is the usual case on personal phones. Screen capture control differs per platform, and each is described on its own. For device-level separation, see managed app integration.
The backend
Your backend decides how much data reaches the phone in the first place. The less a screen receives, the less there is to protect. Otukan’s data event records, which never include the content itself, help data protection teams see where rules are tested most.
Evaluation
Scenarios to rehearse
Build the pilot around the leaks your organisation has actually seen. Copy an account number from a customer screen and try to paste it into a personal note. Screenshot a patient list, then start a screen recording on the same screen. Share a contract from the work app to a personal cloud folder, then to the approved document app. Sign out and look for cached files on the test device. Each scenario should produce the expected block, the expected pass or the expected record, and each result is written down per platform.
Supported platforms
Ask for each control per platform, with the OS versions it has been tested on. Clipboard and capture behaviour changes between OS releases, so the matrix must be current.
Evidence
For each path, reproduce the leak in a test build and confirm the rule stops it. Then run the same step between two approved work apps and confirm it still works. Finally repeat install, update, sign-in and your most sensitive screen on the protected build.
User impact
Staff abandon tools that block their work. During the pilot, count blocked actions per screen and ask why each happened. Relax rules that stop legitimate work, tighten ones that catch real leaks, and publish plainly what the app controls and what it never touches.