Setup
The app connects to TaraSec services and learns which gateway is responsible for the current network. Connection testing makes the network relationship visible rather than silently assuming a gateway.
TARASEC APP
The TaraSec App is being developed as the owner and manager interface to a TaraSec gateway: see security status, receive AI-assisted assessments, manage approved access and interact with protection and recovery functions without handing the app direct access to the global TaraSec database.
The app also contains several safe demo setups that show how threat information follows traffic from a unit, through a gateway, to a receiving node.
ONE APP, DIFFERENT ROLES
The app connects to TaraSec services and learns which gateway is responsible for the current network. Connection testing makes the network relationship visible rather than silently assuming a gateway.
A user can inspect the gateway's current assessment for a unit, including severity and assessment source, and use recovery-oriented functions where permitted.
Privileged gateway functions require manager access. The app requests access using an email address, verifies that address and waits for a gateway administrator to approve the manager before credentials become active.
The design allows a manager to remain informed about threats to a managed LAN even when the phone is elsewhere, rather than requiring the app to be physically connected to that LAN.
MANAGER ACCESS
A manager request does not become active merely because somebody knows an email address. The email address must be confirmed and an already authorised gateway administrator must approve the request.
If the verification message is lost or delayed, the app can request a new verification email. Resending rotates the verification token so the previous link is no longer valid.
Once approved, the app activates a gateway manager session. The gateway remains the security boundary for manager operations; the app does not receive direct database credentials.
AI IN THE APP
The app can present the gateway's latest AI-assisted assessment, including category, severity, confidence, summary and the relevant unit, network-node or IP-observation findings.
A gateway owner can choose to enable detailed AI using an account or API token the owner pays for. This avoids requiring TaraSec to centrally fund a full AI assessment for every participating gateway.
Before the local AI call, the gateway can combine its detailed local evidence with compact intelligence from the TaraSec DB server: independent sightings, global threat history, known network nodes and candidate botnet relationships.
After assessment, the gateway automatically reports structured findings back to TaraSec so independent gateway observations can strengthen global botnet and campaign detection.
THE OWNER KEEPS CONTROL
The planned AI configuration lets an authenticated owner or manager choose a provider/model, save or test the gateway's credential, enable or disable assessment and request an assessment when needed.
The secret is stored locally at the gateway and should not be returned to the app after it is saved. It is never included in assessment reports sent to the TaraSec DB server.
This separation also means the gateway AI implementation can evolve: a commercial API, private service or local model can provide the assessment while the app continues to consume the same structured TaraSec result.
REQUEST FOR ASSISTANCE
The manager interface can submit and review Request for Assistance entries for its gateway. A protected service can ask participating networks to help reduce traffic according to defined threat thresholds.
This complements AI assessment rather than replacing it: TaraSec can use richer unit-level and cross-network evidence to help upstream participants distinguish traffic, while each participant remains responsible for its own enforcement policy.
SECURITY & PRIVACY
The app talks to authorised service endpoints. It should not contain credentials that allow direct unrestricted access to TaraSec's global database.
Manager sessions are validated by the gateway. Privileged actions remain tied to an approved gateway relationship.
TaraSec can present security state using owner and unit identifiers without requiring the app to reveal the subscriber's personal identity.
AI confidence, evidence and later reassessment remain visible. A model result is not automatically a permanent infection label.
APP PRIVACY & ACCOUNT CONTROL
Read what account, hotspot, usage and technical information the TaraSec App and connected services may process, why Android requests location permission for nearby Wi-Fi discovery, and how information is protected and retained.
Global TaraSec subscribers can request deletion of their account and associated personal information. The deletion page explains verification, what is deleted and which limited records may need to be retained.
WHY THE APP AND AI BELONG TOGETHER
The app gives the owner visibility and control over the gateway. The gateway AI turns detailed local evidence plus TaraSec's shared context into a structured assessment. That result can then contribute back to the wider network without sharing the owner's AI credential.