01SIM
SecureTrack SIM Shield
Planned to detect supported physical SIM, eSIM, slot, subscription and default-network changes and alert verified contacts through approved channels.
Rihuum people, security operations and connected technology
Rihuum SecureTrack AI
Prepare before loss. Detect meaningful change. Recover safely.
A lawful, consent-based security and recovery platform direction for verified owners and authorised organisations—designed around enrolled devices, approved signals, accountable evidence and honest technical limits.
Current release status
SecureTrack AI remains in requirements, architecture, privacy and security design. A protected, assessment-only readiness workflow is now available to approved Rihuum owners; it contains no device telemetry, location or remote-command capability.
Planned modular product architecture
Target protection across devices, accounts, evidence and recovery.
These modules remain planned. Foundation 0.1 provides only the protected assessment workflow; future RME identity, tenancy, licensing and support capabilities require their own release gates.
02MOBILE
SecureTrack Mobile Agent
Planned for enrolled Android devices, subject to approved heartbeat, integrity, location, lost-mode and security-event release gates.
03COMPUTER
SecureTrack Computer Agent
Proposed for enrolled Windows, macOS and Linux systems after check-in, inventory, signing, update and eligible-action validation.
04ASSET
SecureTrack Asset Tags
Proposed to connect approved Bluetooth, NFC, QR, UWB or cellular accessories to registered assets after hardware and privacy validation.
05NETWORK
SecureTrack Network Guard
Planned only for customer-owned or explicitly authorised networks and equipment after monitoring and data-policy approval.
06INTEL
SecureTrack Recovery Intelligence
Proposed to correlate approved signals and prioritise human-reviewed recovery steps after model, security and legal evaluation.
07EVIDENCE
SecureTrack Evidence Vault
Planned for timestamped events and controlled evidence records only after stronger infrastructure, retention and access gates.
08ACCOUNT
SecureTrack Account Protection Centre
Proposed to guide approved account-protection and incident communications after workflow and support testing.
Platform reality
One recovery promise cannot fit every operating system.
SecureTrack will publish a tested compatibility matrix by edition, device, operating-system version, management mode and permission. Native platform recovery remains part of the response plan.
01ANDROID
First mobile product direction
A visible, pre-enrolled Android agent may use permitted check-ins, integrity, supported SIM/subscription events and carefully justified location. Background access, managed-device actions and Play policy require separate release gates.
02APPLE
Preparedness and managed devices
Consumer iPhone and iPad recovery remains owner-controlled through Apple Find My. A future enterprise edition may integrate supported supervised-device and MDM functions; no arbitrary consumer-device access is promised.
03WINDOWS
Enrolled agent and management integration
A pre-enrolled Windows agent may report authorised security and check-in signals. Enterprise actions depend on the supported management mode; continuous GPS or a universal Windows lost mode is not promised.
04MAC/LINUX
Later validated desktop scope
Future agents may support approved inventory, health, network and check-in events after compatibility, signing, update, privacy and support testing for published versions.
Target security and recovery journey
A controlled future workflow—not a map with unchecked power.
Every important action has an authorised actor, reason, evidence, permission boundary and audit record. High-impact operations require explicit approval.
Enrol
Verify ownership or management authority, register the device or asset, obtain notice/consent and establish trusted contacts.
Prepare
Confirm permissions, device health, recovery channels, account security, encryption, backups and a test alert.
Detect
Collect only approved signals, record their source and confidence, and apply human-reviewed escalation rules.
Protect
Guide account and data-protection actions; execute remote controls only on eligible, authorised managed systems.
Recover
Coordinate evidence, safe contact, law-enforcement or insurer engagement and approved return or containment steps.
Review
Close the incident, retain or delete data according to policy, learn from the event and improve readiness.
Planned commercial editions
Proposed protection models for future validation.
SecureTrack Personal
- Planned verified-device enrolment
- Planned trusted contacts and recovery readiness
- Proposed supported SIM and security alerts
- Proposed personal incident timeline and recovery report
SecureTrack Business
- Planned central asset inventory and endpoint agents
- Target role-based administration and policy
- Proposed bulk enrolment, geofences and audit
- Target incidents, reports, licensing and support
SecureTrack Enterprise
- Target multi-tenant management and APIs
- Proposed MDM, SIEM and service-desk integrations
- Proposed evidence vault and hardware trackers
- Target high-availability and enterprise deployment options
Honest capability
What SecureTrack is designed to do.
- Protect verified and enrolled devices or registered assets.
- Detect supported SIM, network, integrity and availability changes.
- Alert approved contacts through configured channels.
- Guide account protection, evidence preservation and safe escalation.
- Support authorised organisation policies and eligible managed actions.
Non-negotiable boundary
What it must never claim or enable.
- Secret tracking of arbitrary people, phones or computers.
- Universal location from a telephone number, IMEI, email or IP.
- Hidden recording, keylogging, credential theft or message interception.
- Guaranteed recovery, precision or persistence after every reset.
- Telecom or subscriber access without the operator and lawful authority.
Product questions
Clear answers before commercial promises.
Technical feasibility and lawful authority are validated for every platform, customer and jurisdiction before implementation.
01Can SecureTrack secretly track any phone or person?
No. SecureTrack is designed only for devices and assets that are owned, voluntarily enrolled or lawfully managed by the customer. A phone number, IMEI, email address or IP address alone does not give Rihuum lawful or technical access to an arbitrary device.
02Will it send the new SIM telephone number after a SIM change?
SecureTrack SIM Shield is intended to detect supported SIM, eSIM, slot and subscription changes. It can report a new telephone number only when the operating system or network lawfully exposes that number. Many devices and carriers do not provide it, so alerts may instead contain the available carrier, slot, connection, time, device-health and location signals.
03Can it protect laptops and computers without GPS or a SIM?
A future released computer edition may do so when the computer is enrolled and a supported agent remains operational. Any approved signals would provide approximate rather than guaranteed precise location.
04Does SecureTrack survive every uninstall or factory reset?
No product can honestly guarantee that on every consumer device. Managed enterprise controls may provide stronger persistence on eligible systems, while consumer recovery depends on permissions, platform policy, connectivity and whether the installed agent remains available.
05Can SecureTrack run permanently on shared hosting?
Shared hosting is suitable for the public website, documentation, lead capture and controlled non-sensitive demonstrations. Production device telemetry, privileged commands and evidence records require a migration gate to an environment with stronger isolation, queues, monitoring, secrets, backup and recovery controls.
Controlled product discovery
Help define a lawful SecureTrack lighthouse use case.
Rihuum is validating customer needs, platform limitations, privacy, security architecture, operating cost and measurable recovery value before committing a pilot. Website submissions enter the governed RME pipeline; only qualified enquiries can become controlled readiness assessments, with every safety gate initially pending.