Pilot tenant
Olakunle Gadget and Phone Accessories
Trust-first Android management
Control company devices without crossing privacy lines.
A commercial EMM foundation for small businesses—built around consent, guarded actions, tenant separation, and clear evidence of every administrative change.
Foundation readiness
Core experience mapped
Interface, guardrails, device model, and policy structure are now represented.
Pilot fleet
Device readiness
Recent evidence
Trust activity
Company-owned Android
Devices
Representative pilot records only. No hardware is enrolled in this console.
| Device | Ownership | Policy | Status | Last check-in | Actions |
|---|
No demo devices match this filter.
Clear rules, visible impact
Policy library
Policy templates are readable before assignment. No silent changes.
Active pilot
Baseline Secure
For general company-owned phones used by staff.
- Screen lock and encryption required
- Managed Play apps only
- Automatic security updates
- USB debugging blocked
Ready to test
WorldStore Kiosk
For dedicated counter devices running approved store tools.
- Single-purpose app allowlist
- System navigation restricted
- Remote support notice shown
- Scheduled update window
Phase 2
Private Work Profile
For employee-owned devices, keeping personal and work spaces separate.
- Only work apps are administered
- Personal photos remain private
- Work data can be removed alone
- Employee disclosure required
Temporary and accountable
Enrollment
Every demo token expires quickly and carries no password or private key.
QR enrollment for company-owned devices
- 1Confirm ownership
The customer confirms the device belongs to their organization.
- 2Show disclosure
The administrator reviews what the policy can and cannot access.
- 3Create a short-lived token
A one-time QR token is generated for the approved device.
- 4Verify compliance
Enrollment appears in the audit log before policies are applied.
usgraje3ldu.org
The selected domain is preserved for this project. DNS connection remains a separate, deliberate publishing step.
✓
Domain chosenOwner-approved project identity
✓
Secure static packageNo credentials or customer data embedded
3
Cloudflare Pages deploymentWaiting for connected publishing access
4
Custom domain activationComplete only after deployment succeeds
Evidence over promises
Audit log
Every simulated administrative event records its actor, target, and outcome.
EventActorTimeResult
PlayKingdom trust contract
Power must stay accountable.
Device management is legitimate only when ownership, consent, scope, and consequences are visible.
AFoundation posture
No hidden surveillance
No SMS content, call content, personal photos, microphone, or camera collection.
Least privilege
Administrators see only the information needed to protect enrolled work devices.
Guarded destructive actions
Wipe operations require explicit confirmation, a stated reason, and an audit event.
Tenant separation
One customer must never be able to read or control another customer’s devices.
Clear employee notice
People are told what is managed before enrollment, using plain language.
No financing lock abuse
The platform will not become a payment-enforcement or coercive device-locking tool.
Phase 1 collection boundary
What the production service may need
Allowed for operations
- Device identifier and model
- OS and security patch level
- Assigned policy and compliance
- Administrative audit events
Outside the boundary
- Personal messages and calls
- Personal media and documents
- Advertising identifiers
- Continuous location history