XOPOZ

Brand Speech Library for Text-to-Speech Module

Each feature has SHORT, MEDIUM, and LONG versions. Extract as needed.

Usage Guide: Each section below contains three versions of the same feature description. SHORT (5-15 seconds) for quick mentions and ads. MEDIUM (20-40 seconds) for feature highlights and presentations. LONG (45-90 seconds) for detailed explanations and tutorials. All text is optimized for natural speech. No scene descriptions, no formatting cues. Pure spoken content.
PART 1: CORE IDENTITY

What is XOPOZ

Short
XOPOZ is a privacy-first GPS team tracker for professionals. Your locations stay encrypted. Your data stays yours. No Google dependency. No surveillance. Just secure team coordination that works everywhere.

Medium
XOPOZ is a secure GPS team tracking application built for professionals who operate in the field. Unlike consumer trackers that sell your data and drain your battery, XOPOZ encrypts every GPS position with military-grade cryptography before it ever leaves your device. The server never sees your real coordinates. Your team members are the only ones who can decrypt your location. XOPOZ works without Google Play Services, runs on any Android device, and gives you complete control over your map tile servers. It is tracking done right.

Long
XOPOZ is a professional GPS team tracking application designed from the ground up with one principle: your location data belongs to you. In a world where most tracking apps harvest your GPS positions, sell them to data brokers, and depend entirely on Google's infrastructure, XOPOZ takes a fundamentally different approach. Every single GPS coordinate is encrypted on your device using AES 128 bit encryption with team-specific keys before anything is transmitted. The server stores only encrypted blobs that are mathematically impossible to decrypt without your team's key. Even if the server were compromised, your locations would remain completely confidential. XOPOZ uses direct Android GPS APIs instead of Google Play Services, which means it works on any Android device, including custom operating systems and degoogled phones. You can configure your own map tile servers for satellite imagery, terrain maps, or even air-gapped military deployments. The battery optimization system intelligently switches between high-precision GPS and low-power network tracking based on your movement patterns. When you are still, it sleeps. When you move, it wakes up instantly. XOPOZ is not just another tracking app. It is a professional tool built for teams who need reliability, privacy, and performance in the field.

The XOPOZ Difference

Short
Most trackers watch you. XOPOZ protects you. End-to-end encrypted locations, zero Google dependency, adaptive battery management, and you choose your own map servers. This is the anti surveillance tracker.

Medium
Here is what makes XOPOZ different from every other GPS tracker on the market. First, encryption is not optional. Every GPS position is encrypted before transmission, and the server cannot decrypt it. Second, there is no Google dependency. XOPOZ talks directly to your phone's GPS hardware, so it works on any Android device. Third, the battery system is intelligent. It wakes up fast when you move and sleeps slowly when you stop. No constant polling draining your battery. Fourth, you control the maps. Use OpenStreetMap, your own private tile server, or any raster tile source you want. And fifth, privacy is the default. Nothing is shared until you explicitly choose to share it.

Long
Let me walk you through what separates XOPOZ from every GPS tracking solution available today. The architecture is fundamentally different. While apps like Life360 store your raw GPS coordinates on their servers, sell aggregated location data to advertisers, and require Google Play Services to function, XOPOZ inverts the entire model. The encryption happens first, on your device, before any data moves. Each team generates a unique 16-byte cryptographic key. That key never touches the server. A SHA 256 challenge hash proves you hold the key without revealing it. The result is that even XOPOZ itself cannot see where you are. Only your team members, who hold the same key, can decrypt your position. There is no Google Play Services dependency. XOPOZ uses Android's native Location Manager API to talk directly to your phone's GPS chip. This means it works on GrapheneOS, LineageOS, Huawei devices without Google services, and any standard Android phone. The battery optimization system uses a strategy called wake up fast, sleep slowly. When you are stationary, XOPOZ drops to network-only positioning and activates hardware motion sensors that consume almost zero power. The moment you start moving, full GPS activates within seconds. After five minutes of being still, it gradually reduces power consumption. This means XOPOZ can run all day on a single charge during field operations. And you are never locked into a specific map provider. You can configure any raster tile server, whether that is OpenStreetMap, a corporate map server, satellite imagery, or even an offline tile cache for areas with no internet connectivity.
PART 2: SECURITY AND ENCRYPTION

End-to-End GPS Encryption

Short
XOPOZ encrypts every GPS coordinate with AES 128 bit encryption before it leaves your device. The server stores only encrypted data. Only your team can see your location. Zero knowledge architecture.

Medium
Every GPS position in XOPOZ goes through hardware-accelerated AES 128 bit encryption before it is transmitted. Your latitude and longitude are packed into a 16-byte structure along with a 64-bit initialization vector generated from multiple entropy sources including device identity, timestamps, and cryptographic random numbers. This means the same location encrypted twice produces completely different ciphertext. The server stores only these encrypted blobs and has no way to decrypt them. Each team has its own independent encryption key, so even if you belong to multiple teams, your position is encrypted differently for each one. Complete cryptographic isolation.

Long
The GPS encryption in XOPOZ is built on a two-tier cryptographic architecture. At the foundation sits the Android Keystore hardware security module, which generates and protects a master key using AES 256 bit encryption with GCM mode. This master key cannot be extracted from the device, not even by the operating system. It protects all secondary keys, including the team encryption keys and the local device key. When a GPS position is captured, the coordinates are converted to unsigned microdegrees and packed into a 16-byte block alongside a split 64-bit initialization vector. This IV is generated from a combination of device identity, nanosecond-precision timestamps, and cryptographic random numbers, ensuring that identical coordinates produce different encrypted outputs every single time. The block is then encrypted using hardware-accelerated AES 128 in a single-block operation for maximum performance. On a modern device like a Pixel 7, this encryption runs at over 30,000 operations per second, making it essentially invisible in terms of battery and performance impact. For messaging, XOPOZ uses AES 128 CBC mode with random initialization vectors and PKCS7 padding, adding a protocol wrapper with version information, payload length, and CRC32 integrity validation. The team keys are stored in encrypted form in the device's private storage, protected by the hardware master key. When a new team is created, the client generates a fresh 16-byte key, creates a SHA 256 challenge hash, and sends only the hash to the server. The key itself stays on the device and is shared with teammates through a group ticket, a specially formatted string containing the team identifier and the base64-encoded key. This is true zero-knowledge encryption. The server proves team membership through challenge matching without ever seeing the key.

Device Security Architecture

Short
Each XOPOZ device receives a unique server-assigned security identifier. All communication is tied to this identity. Encryption keys are stored in the Android hardware security module. Your data is protected even if the phone is stolen.

Medium
XOPOZ assigns every device a unique Security Identifier, or SecId, upon registration with the server. This identity is server-controlled and cryptographically bound. It cannot be spoofed, transferred, or modified by the client. All GPS data and messages are routed using this SecId, creating a complete audit trail. The encryption keys that protect your positions are stored inside the Android Keystore hardware security module, which is physically isolated from the rest of the device. Even if someone roots your phone or extracts the file system, they cannot access the master key that protects your team keys. Position records are cryptographically linked to specific devices, and any tampering with device-to-position associations is immediately detectable.

Long
The device security architecture in XOPOZ operates on multiple defensive layers. When a device first connects to the server, it sends a hardware fingerprint and receives a globally unique Security Identifier, known as the SecId. This identifier is the cornerstone of all subsequent authentication. Messages are routed from source SecId to target SecId, with the server validating sender identity before relaying any data. This prevents impersonation attacks and creates a verifiable chain of custody for all location data. The cryptographic key hierarchy starts with a single AES 256 master key generated inside the Android Keystore hardware security module. This key is bound to the application's signing certificate and the device's unique identifier. It survives app updates and device reboots, but cannot be extracted, even by applications with root access. This master key protects all secondary keys through AES GCM encryption. The local device key encrypts GPS positions stored on the device itself. Team keys, one per team, encrypt positions that are shared with team members. All these secondary keys are stored as encrypted base64 strings in the application's private storage. The same physical device can belong to multiple teams simultaneously, and its position is encrypted differently for each team using independent keys. This means compromising one team's key reveals nothing about positions shared with other teams. XOPOZ also implements secure deletion. When data is erased, files are overwritten with hexadecimal FF bytes before being unlinked from the file system, preventing forensic recovery of sensitive data.

Privacy Controls

Short
XOPOZ gives you two independent privacy switches. One controls whether your location is saved locally. The other controls whether it is shared with your team. Both default to off. You choose what to share.

Medium
Privacy in XOPOZ is not an afterthought. It is the architecture. You get two independent controls. The Local Save Permission determines whether your GPS positions are stored on your device as a history trail. The Push Location Permission determines whether your positions are encrypted and shared with your team. These two switches operate independently, giving you four distinct privacy modes. Full tracking with local history and team sharing. Private tracking where you keep a history but appear offline to your team. Team-only mode where your team can see you but you keep no local records. And maximum privacy where GPS is collected but nothing is stored or shared. Changes take effect immediately. There is also an intraday tracking feature that lets you define working hours, so tracking only happens between specific times of the day.

Long
XOPOZ implements one of the most comprehensive privacy control systems in any tracking application. At its core are two independent permission switches that create a matrix of four privacy configurations. The Local Save Permission controls whether GPS positions are written to your device's encrypted storage. When disabled, your current position is still available for the map display, but no trail history is recorded. The Push Location Permission controls whether your encrypted positions are transmitted to the server for your team to see. When disabled, your team members see your status as offline, even if you are actively using the app. These switches can be toggled at any time with immediate effect. For professionals who need business-compliant tracking, the intraday tracking feature adds time-based controls. You can set a start time and a stop time, and XOPOZ will only track within those hours. Outside the configured window, GPS requests are blocked at the engine level. When the tracking window ends during an active session, the GPS session terminates immediately. When the window reopens, tracking resumes automatically through screen activation, motion detection, or device activity. A red intraday blocked indicator appears on the map during restricted hours. The Teams interface shows a persistent warning banner when push location is disabled, so you are always aware of your sharing status. All consent is explicit. When you create or join a team, you must check a mandatory privacy agreement before proceeding. Your opt-in date is recorded and displayed in Settings for audit compliance. XOPOZ is fully GDPR compliant, implementing the right to access, rectification, erasure, data portability, and withdrawal of consent. When you choose to delete your data, XOPOZ performs secure destruction with byte overwriting before file removal, and triggers server-side deletion of your position records. Deletion is permanent. There are no hidden backups.
PART 3: GPS AND LOCATION

GPS Tracking and Movement Detection

Short
XOPOZ tracks your position in real-time using direct GPS hardware access. It detects movement with a 50-meter threshold and shows your direction with a precision heading line. No Google services needed.

Medium
XOPOZ bypasses Google Play Services entirely and communicates directly with your phone's GPS chip through Android's native Location Manager API. This gives you satellite-level positioning accuracy on any Android device, including phones running custom operating systems. The movement detection engine uses a 50-meter distance threshold combined with a speed check of 1.9 kilometers per hour. When you are moving, your map icon changes from a static circle to a directional arrow showing your heading. You can configure your location history trail to span anywhere from one hour to thirty-one days, and the trail is rendered directly on the map as a visual path of where you have been. Location data is cached in memory for instant access by the user interface, with a file-based backup for persistence across app restarts.

Long
The GPS implementation in XOPOZ is designed for professionals who need reliable, accurate positioning without external dependencies. Instead of relying on Google's fused location provider, XOPOZ communicates directly with the Android Location Manager API. This provides pure GPS satellite positioning with professional-grade accuracy, and it works on every Android device regardless of whether Google Play Services is installed. The movement detection engine evaluates each new position against a dual threshold: 50 meters of displacement and a minimum speed of 1.9 kilometers per hour. This combination filters out GPS noise while accurately detecting real movement. When movement is detected, the map icon transitions from a 128-pixel static circle to a 256-pixel directional arrow, giving you an immediate visual indication of a team member's heading. The speed indicator appears only when you are moving and uses a one-minute sampling period for accurate calculation, displayed in kilometers per hour. The compass system uses the rotation vector sensor, which combines accelerometer, gyroscope, and magnetometer data for high-precision heading. An exponential moving average filter smooths the compass readings, and an outlier accumulation system with a one-second timeout prevents compass freeze during rapid direction changes. A full-length heading line extends from your position to the edge of the screen, allowing you to identify distant targets by simply pointing your phone. Location history is configurable from one hour to approximately thirty-one days, with a default of twelve hours. The trail renders on the map as a connected path. Each position includes coordinates with six decimal places of precision, accuracy in meters, timestamp, and battery level. Positions are cached in memory for instant UI access, backed by encrypted file storage, and periodically cleaned based on your configured retention period.

Battery Optimization

Short
XOPOZ uses the wake up fast, sleep slowly strategy. Hardware motion sensors detect when you move. GPS activates instantly. When you stop, power consumption drops by up to ninety percent. All-day tracking on a single charge.

Medium
Battery life is critical for field operations, and XOPOZ addresses this with an intelligent multi-layer power management system. There are two power modes: Active mode uses high-precision GPS combined with network providers for maximum accuracy. Power Save mode drops to network-only positioning to conserve energy. The transition between modes is automatic. When you are moving, XOPOZ stays in Active mode. After five minutes of being stationary with the map hidden, it transitions to Power Save. The key innovation is hardware-accelerated wake detection using the significant motion sensor, which operates at near-zero power consumption. The instant this sensor detects movement, full GPS reactivates. Opening the map also immediately activates GPS. The result is network-only mode reduces power consumption by up to ninety percent compared to continuous GPS while maintaining the ability to wake instantly when needed.

Long
XOPOZ implements what we call the wake up fast, sleep slowly architecture. This is a multi-sensor, context-aware power management system that adapts in real-time to your activity patterns. At the top level, there are two power states. Active mode engages both GPS and network providers for high-precision positioning, delivering updates at configurable intervals as frequent as every ten seconds when the map is visible. Power Save mode disables the GPS hardware entirely and relies on cell tower and Wi-Fi network positioning, which consumes a fraction of the power. The transition logic is carefully tuned. When any movement is detected, whether through the significant motion hardware sensor, a screen activation event, or an explicit map interaction, XOPOZ switches to Active mode immediately. There is no delay. GPS comes online within seconds. The transition to Power Save, however, is deliberately gradual. A five-minute stationary timer must expire, and the map must not be visible. Brief stops at traffic lights or momentary pauses do not trigger the transition. This asymmetry is by design. Fast activation ensures you never miss a position update when it matters. Slow deactivation prevents unnecessary power cycling that would actually increase battery consumption. The significant motion sensor is a hardware component that operates without waking the CPU. It draws almost no power and can detect when you start walking, driving, or otherwise moving. XOPOZ registers a listener for this sensor whenever it enters Power Save mode, and re-arms it after each trigger. A one-minute rate limiter prevents excessive wake-ups from sensor noise. Screen state monitoring adds another layer. When the screen turns on after an extended period, XOPOZ proactively acquires a fresh location, with a twenty-minute rate limit to prevent battery drain from frequent screen toggles. The GPS hardware itself powers down within two to four seconds after the last position acquisition in Power Save mode, with a fifty-second safety timeout. Performance benchmarks show that network-only mode reduces location-related power consumption by up to ninety percent while maintaining the ability to deliver accurate positioning within seconds of detecting movement.
PART 4: TEAM FEATURES

Device-Focused Teams

Short
XOPOZ treats each device as an independent tracking entity. A person with two phones appears as two separate entries in the team. Track equipment, vehicles, and individual devices, not just people.

Medium
Unlike traditional trackers that group everything under a person's name, XOPOZ uses a device-centric architecture. Each physical device is its own team member with its own identity, encryption, and visibility controls. If someone has a work phone and a personal phone, both appear as separate entries in the team roster. This opens up powerful use cases. You can track vehicles by placing a device in each one. You can monitor equipment in the field. Each device has its own color, emoji icon, and ticker abbreviation for quick identification on the map. Visibility controls are per-device, so you can show or hide individual devices within a team without affecting others.

Long
The device-focused architecture is one of the most distinctive design decisions in XOPOZ. Most GPS tracking applications model their teams around people. One person equals one entry in the roster. XOPOZ takes a fundamentally different approach. Each physical device is treated as an independent tracking entity. When a user registers multiple devices, each one appears as its own entry in the team member list. A user with three devices creates three roster rows, each with independent GPS tracking, independent encryption, and independent visibility controls. This architecture enables use cases that person-centric trackers simply cannot handle. A construction company can place dedicated devices in each vehicle and track their fleet as individual team members. A logistics operation can attach tracking devices to equipment and shipments. A search and rescue team can issue devices to volunteers and see each device individually on the map. Each device gets its own server-assigned Security Identifier, its own display name and emoji ticker for quick visual identification, its own color coding, and its own per-team visibility toggle. The same device can belong to multiple teams simultaneously, with its position encrypted independently for each team using different keys. On the map, team members appear as circular icons when stationary and directional arrows when moving. Each icon shows the device's ticker abbreviation and is colored according to its assigned color. Online devices show a thin white border, while offline devices display a thick red border at seventy percent opacity. Tapping any device icon centers the map on that device's position with a smooth animation. The distance from your main device to any team member is calculated in real-time and displayed with smart formatting, showing meters for short distances and kilometers for longer ones.

Team Creation and Joining

Short
Creating a team generates a unique encryption key. Share a group ticket with your teammates. They paste it in, the keys match, and encrypted location sharing begins. The server never sees the key.

Medium
Team creation in XOPOZ is a two-phase cryptographic process. First, you create the team on the server, which assigns a team identifier and adds your device automatically. Second, your device generates a unique 16-byte encryption key, creates a SHA 256 challenge hash, and sends only the hash to the server. The key stays on your device, stored in the Android Keystore. To invite teammates, you share a group ticket, which is a specially formatted string containing the team identifier and the base64-encoded key. When a teammate pastes this ticket, their device extracts the key, stores it locally, generates the same challenge hash, and sends it to the server. The server compares the hashes. If they match, membership is granted. At no point does the encryption key touch the server. From that moment, all team members can encrypt and decrypt each other's GPS positions.

Long
The team creation workflow in XOPOZ is designed around a principle of zero-knowledge authentication. Here is exactly how it works. When you create a new team, XOPOZ first registers the team name with the server. The server assigns a unique team identifier and automatically adds your device as the first member with administrator privileges. Then your device generates a random 16-byte encryption key using a cryptographic random number generator. This key is the foundation of all position sharing within the team. Your device then computes a SHA 256 hash of the string XOPOZ concatenated with the 16-byte key, producing a challenge hash. Only the challenge hash is sent to the server. The server stores this hash and uses it to verify future team join requests. The actual encryption key is stored locally in the Android Keystore hardware security module, encrypted by the master key. To invite a teammate, you generate a group ticket. This is a formatted string enclosed in square brackets, following the pattern XPZ, dash, team identifier, dash, and the base64-encoded encryption key. You share this ticket through any secure channel, a text message, a printed card, or a verbal exchange. When your teammate pastes this ticket into XOPOZ, the app validates the format, extracts the team identifier and encryption key, stores the key in the Android Keystore, generates the same SHA 256 challenge hash, and sends it to the server. The server compares the new challenge with the stored challenge. If they match, it proves the new member holds the correct key without the key ever being transmitted to the server. Membership is granted, and encrypted location sharing begins immediately. This design means that even a complete server compromise would not reveal team encryption keys. The server holds only challenge hashes, which are one-way cryptographic functions that cannot be reversed to recover the original key.

Emergency SOS System

Short
XOPOZ includes a built-in emergency alert system. Send an SOS to your entire team with your GPS position and a custom message. Recipients get a full-screen alarm with your location and a direct navigation option.

Medium
The emergency SOS system in XOPOZ is designed for high-stress situations. When you trigger an SOS, you select a team, optionally write a message, and your current GPS position is automatically included. The message goes through two layers of encryption, one for the GPS coordinates and one for the message payload, both using your team's specific key. When a teammate receives the alert, their phone displays a full-screen alarm that appears even on the lock screen, plays an emergency ringtone, and shows the sender's identity, message, and coordinates. One tap takes them directly to your position on the map. The interface uses double-sized fonts, emergency red colors, and strategically positioned buttons designed for users under stress.

Long
The XOPOZ emergency SOS system provides team-based emergency communication with two-level encryption and a stress-optimized user interface. The workflow is intentionally multi-step to prevent accidental activation. You open the navigation drawer, select Send SOS, choose a team, optionally compose a custom message, and confirm the send. Your current GPS coordinates are automatically encrypted and embedded in the alert payload. The SOS message uses the EMERGENCY ALERT message type, which receives priority handling throughout the system. The payload goes through two independent encryption operations. First, your GPS position is encrypted using the team's AES 128 key with the standard coordinate encryption process. Then the entire message payload, including your custom text and the encrypted position, is encrypted again using AES 128 CBC mode with a random initialization vector and PKCS7 padding. A CRC32 integrity check is appended to detect transmission corruption. The message is delivered through the standard messaging infrastructure. When a teammate's device polls for new messages and receives the emergency alert, the Location Service detects the EMERGENCY ALERT type and triggers the alarm workflow. The receiving device launches a full-screen alarm activity that appears on the lock screen, wakes the device, and plays the system emergency ringtone. The interface is specifically designed for stress situations. All fonts are doubled in size. The background is emergency red with white text. The cancel button is positioned at the extreme left and the action button at the extreme right, with minimum touch targets of 120 density-independent pixels. The alarm shows the sender's device identifier, the team context, and the custom message. A stop alarm button silences the ringtone, and a close button navigates directly to the sender's last known position on the map. It is important to note that SOS messages are delivered through the same server infrastructure as all other messages, which means internet connectivity is required. This is not a replacement for calling emergency services. It is a team coordination tool for situations where your team needs to know your position and status immediately.
PART 5: MAP AND NAVIGATION

Map and Navigation System

Short
XOPOZ uses OpenStreetMap with full support for custom tile servers. Three navigation modes. Tracking, free navigation, and distance measurement. Plus a precision compass with a full-screen heading line.

Medium
The map module is the primary interface of XOPOZ. It provides three navigation modes. Tracking mode auto-centers on a selected team member with each position update. Free navigation gives you full manual control of pan and zoom. Measurement mode lets you place multiple points and calculate real-time distances between them. The map supports any raster tile server, not just OpenStreetMap. You can configure private servers, satellite imagery, terrain maps, or even offline tile caches. Each server can have multiple styles like street view, satellite, and terrain, with dynamic style switching through URL template tokens. The compass uses the rotation vector sensor for high-precision heading, displayed as a full-length red line from your position to the screen edge. Volume buttons control zoom, which is essential for outdoor use with gloves.

Long
The map module serves as the command center of XOPOZ. Built on OpenStreetMap with the OSMDroid library, it provides a flexible, customizable mapping experience that is independent of any commercial map provider. Three distinct navigation modes cover different use cases. Tracking mode locks the map view to follow a selected device, automatically re-centering with each new position update while preserving your zoom level. It stays active until you manually interact with the map. Free navigation mode gives you complete manual control for exploring the map without interruption from position updates. Measurement mode activates a multi-point distance tool with real-time metric display and a grid overlay for precision reference. The map tile server system gives you complete freedom over your map source. You configure a server name, base URL with a style token placeholder, minimum and maximum zoom levels, tile size, image format, and attribution text. The style system supports multiple visual modes per server, such as satellite, street, and terrain views, with instant switching. This opens up use cases that Google Maps based trackers cannot touch. Military operations can use private, air-gapped tile servers. Enterprise deployments can use corporate map infrastructure. Field teams in remote areas can load offline tile caches. The compass and heading system deserves special attention. It uses the rotation vector sensor, which combines accelerometer, gyroscope, and magnetometer data for superior accuracy. An exponential moving average filter smooths the readings, while an outlier accumulation system prevents the compass from freezing during rapid direction changes. The heading is displayed as a solid red line that extends from your position all the way to the edge of the screen. By zooming out, you can see what you are pointing at from street level all the way to continental scale. The compass background turns green when you are within ten degrees of north. It only appears when the device is held relatively flat, below thirty degrees of tilt, and is hidden in landscape mode to prevent orientation errors. For outdoor use, volume buttons control map zoom, so you can navigate one-handed while wearing gloves. A single press moves one zoom level. Holding the button starts continuous zoom after a 250-millisecond delay. Seven floating action buttons provide quick access to share location, add a point of interest, center on your position, zoom controls, trail visibility, and measurement mode.

Custom Map Servers

Short
XOPOZ lets you use any raster tile map server. Corporate servers, military maps, satellite imagery, offline tiles. You are not locked into Google Maps or any other provider. Complete map independence.

Medium
One of the most powerful features of XOPOZ is complete map server independence. You can configure any raster tile server as your map source. This includes public OpenStreetMap servers, commercial satellite imagery providers, corporate internal map servers, military mapping infrastructure, and even locally hosted offline tile caches. Each server configuration includes a base URL with a style token for dynamic styling, minimum and maximum zoom levels, tile size, image format support for PNG, JPEG, and WebP, and custom attribution text. You can switch between multiple servers and styles on the fly, giving your team access to the best map data for their specific environment.

Long
Map independence is a core design principle of XOPOZ. While most GPS tracking applications lock you into Google Maps, Apple Maps, or a single mapping provider, XOPOZ gives you complete control over your tile source. The custom map server system lets you configure any raster tile server that follows standard web mapping conventions. You set the server name for display purposes, a base URL that includes a style token placeholder for dynamic style switching, minimum and maximum zoom levels to match the server's available detail, the tile size in pixels, the image format including PNG, JPEG, and WebP, and an attribution text for proper map data crediting. The dynamic style system is particularly useful. A single map server can offer multiple visual presentations, such as a standard street map, satellite imagery, a terrain overlay, or a night mode. By embedding a style token in the URL template, XOPOZ can switch between these styles without changing the server configuration. This is a game-changer for several professional use cases. Military and government teams can point XOPOZ at their secure, classified mapping infrastructure. Enterprise organizations can use their internal Geographic Information System servers with proprietary data layers. Teams operating in areas with limited connectivity can pre-load offline tile caches in the MBTiles format and run entirely without internet access. Researchers can overlay specialized geographic data sets. And privacy-conscious teams can avoid routing any map tile requests through commercial services. The default configuration uses OpenStreetMap, ensuring immediate usability out of the box. But the architecture ensures you are never dependent on any external service for your mapping needs.
PART 6: POINTS OF INTEREST AND GEOFENCING

Points of Interest Management

Short
Save locations as points of interest organized in folders. Private points for yourself, shared points for your team. Up to ten thousand points with full import and export in JSON format.

Medium
XOPOZ provides a dual-tier point of interest system. Private points are stored locally and organized in your personal folder hierarchy. Shared points belong to a team, and when any member adds a point, the entire team gets instant access. You can create points at the map center with a single tap, set a custom name, description, and configurable radius from 10 to 500 meters. Points are organized in alphabetically sorted folders with drag-and-drop reorganization. You can long-press a point on the map and drag it to a new position. The system supports up to 100 folders with 100 points each, for a total capacity of ten thousand points. Full JSON export and import preserves the complete folder hierarchy for backup and cross-device transfer.

Long
The point of interest system in XOPOZ goes well beyond simple map pins. It provides a dual-tier architecture with independent private and shared collections. Private points of interest are stored locally on your device in an encrypted, hierarchical folder structure. They are visible only to you and can be exported and imported via JSON files for backup or transfer to another device. Shared points of interest are associated with a specific team. When any team member creates a shared point, every other member of that team immediately has access to it. This collaborative model is ideal for field teams who need to mark and share significant locations in real-time. Creating a point is straightforward. The red cross-hair at the center of the map marks the exact creation location. You provide a name with a minimum of one character, an optional description, and a configurable radius from 10 to 500 meters with a default of 100. Each point records its coordinates with six decimal places of precision, creation and update timestamps, the creator's identity, privacy status, and team association. Points are organized in a folder hierarchy. The default Main folder always appears first, followed by custom folders in alphabetical order. Folders are expandable and collapsible. Drag-and-drop lets you move points between folders with haptic feedback and visual highlighting. On the map, you can long-press any point marker for one second to initiate a drag-and-drop repositioning, and the coordinates update automatically when you release. The system supports up to one hundred folder groups and one hundred points per group. Export produces a JSON file that preserves the complete folder hierarchy, all point metadata, and timestamps. Import includes smart merge functionality that keeps the newest version of duplicate points based on timestamps. Team-based shared collections are managed through a separate tab with team selection and dynamic collection loading, with the last-used team and collection pre-selected for convenience.

Geofencing System

Short
Set up automatic alerts when team members enter or leave specific areas. XOPOZ uses reverse geofencing where detection happens on the device, not the server. End-to-end encrypted, battery efficient, and privacy compliant.

Medium
The XOPOZ geofencing system uses a unique reverse architecture. Instead of a server monitoring positions against boundaries, the monitored device itself performs the detection and sends encrypted notifications. You configure a geofence by selecting which team members to monitor, which points of interest define the boundaries, and whether to trigger on entry, exit, or both. A five-minute temporal hysteresis prevents alert storms from boundary oscillation. Detection leverages the existing GPS acquisition system, adding zero additional battery overhead. Events are encrypted with the team key and queued locally when offline, with no time limit on queue persistence. They are automatically delivered when connectivity returns.

Long
XOPOZ implements what is known as reverse geofencing, a fundamentally different approach from traditional server-side geofencing. In a conventional system, the server receives raw GPS positions from all devices and checks each position against defined boundaries. This requires the server to have access to unencrypted location data, which conflicts with privacy-first design. In the XOPOZ model, the monitored device itself performs the boundary detection locally. When a geofence is configured, the monitoring device tells specific team devices which areas to watch. Those devices continuously compare their own GPS positions against the defined boundaries using a circular area calculation based on the point of interest's center coordinates and configurable radius. When a boundary crossing is detected, the device generates an encrypted notification using the team's AES 128 CBC key and sends it through the messaging infrastructure. Configuration follows a who, where, what model. Who selects which team members and devices to monitor, with collapsible team sections and device-level granularity. Where selects the trigger areas from your private and shared points of interest. What defines the trigger condition: enter, leave, or both. A confirmation screen shows a natural language summary of the complete configuration before activation. A five-minute temporal hysteresis prevents the common problem of rapid alert cycling when someone lingers near a boundary. The minimum interval between entry and exit events for the same geofence is five minutes, eliminating noise without missing legitimate crossings. All geofence events are stored in the encrypted message database with details including event type, device name, geofence name, and timestamp. The event history view shows entries in reverse chronological order with smart time formatting. Tapping any event navigates to the device's current position on the map. Because detection runs on the monitored device using the existing location system, there is zero additional GPS overhead. And because events are queued locally when the device is offline with no time limit on queue persistence, no geofence crossing is ever lost. Events are automatically delivered when network connectivity returns.
PART 7: DATA MANAGEMENT AND COMPLIANCE

Data Export and Portability

Short
Export your location history in GPX format for navigation apps or CSV for data analysis. Export your points of interest in JSON with full folder hierarchy preserved. Your data is always portable.

Medium
XOPOZ ensures you are never locked in to the platform. Your location history can be exported in two formats. GPX, the GPS Exchange format, produces standard files compatible with any navigation application, complete with timestamps, track segments organized by session, and device metadata. CSV export creates spreadsheet-compatible files optimized for statistical analysis and data visualization tools. Points of interest export in JSON format preserves the complete folder hierarchy, all metadata, and creation timestamps for full restoration on another device or import into other mapping tools. All exports use Android's Storage Access Framework, so you choose exactly where to save your files.

Long
Data portability is a fundamental right under GDPR, and XOPOZ implements it thoroughly. Your location history can be exported in two industry-standard formats. The GPX format, which stands for GPS Exchange, produces XML files that are compatible with virtually every navigation and mapping application in existence. Each export includes complete timestamps, track segments organized by recording session, and metadata identifying the user and device. The CSV format produces clean, tabular data with headers optimized for import into spreadsheet applications, statistical analysis tools, and data visualization platforms. This is ideal for researchers who need to process location data programmatically. Points of interest are exported in JSON format, which preserves the complete hierarchical structure of your folder organization, every piece of point metadata including coordinates, names, descriptions, radii, privacy flags, team associations, and all creation and modification timestamps. The import function includes smart merge logic that compares timestamps when duplicate points are detected and keeps the most recent version. All exports use Android's Storage Access Framework, which means the system file picker opens and you choose the exact save location and filename. XOPOZ uses proper MIME types for each format. GPX files are marked as application GPX plus XML. CSV files as text CSV. JSON files as application JSON. This ensures the files open in the correct application when accessed later. Combined with the secure deletion capabilities and the privacy controls, XOPOZ gives you complete ownership of your data lifecycle, from creation through storage, sharing, export, and permanent destruction.

GDPR Compliance and Data Protection

Short
XOPOZ is fully GDPR compliant. Minimal data collection, explicit consent for everything, configurable retention periods, secure deletion with byte overwriting, and complete data portability. European privacy values built into the architecture.

Medium
XOPOZ implements GDPR compliance at the architectural level, not as an afterthought. Data collection is minimal: only GPS coordinates, accuracy, timestamp, and device identifier. All consent is explicit, with mandatory privacy checkboxes before team creation or joining. Data retention is configurable from 1 to 30 days, with automatic cleanup. Deletion is thorough: local files are overwritten with hexadecimal FF bytes before removal, database records are overwritten with fake coordinates before deletion, and server records are permanently removed. There are no hidden backups. Android backup is explicitly disabled in the app manifest. Every GDPR data subject right is implemented: access, rectification, erasure, portability, and withdrawal of consent.

Long
XOPOZ takes GDPR compliance beyond the checklist approach. Privacy protection is embedded in the technical architecture from the ground up. The principle of data minimization means XOPOZ collects only what is strictly necessary: GPS coordinates, positional accuracy, timestamps, and device identifiers. No phone numbers. No contact lists. No browsing history. No advertising identifiers. Registration requires only an email address and password. The consent framework is explicit and granular. Creating or joining a team requires checking a mandatory privacy agreement. Your opt-in date is recorded and displayed in Settings. The dual privacy switch system provides real-time control over local storage and team sharing independently. Consent can be withdrawn at any time by disabling either switch or leaving a team. Data retention is user-configurable from 1 to 30 days, with automatic cleanup of expired records. The three-tier deletion system covers server history, local data, and complete account deletion, each with explicit confirmation and no recovery option. Secure destruction goes beyond simple file deletion. Local files are overwritten with hexadecimal FF bytes before being unlinked from the file system. Database records are overwritten with fake coordinate data before row deletion. This prevents forensic recovery of sensitive location data. Android backup is explicitly disabled at the manifest level. The backup rules XML excludes all data domains: shared preferences, databases, file storage, cache, and external storage. The data extraction rules prevent cloud backup and device-to-device transfers for Android 12 and later. This means your encrypted team keys, GPS data, and authentication tokens are never included in any system backup. Server-side logging is equally privacy-conscious. Logs never contain GPS coordinates or location data. Application logs automatically strip precise coordinates to integers, reducing six-decimal-place positions to whole numbers that provide no meaningful location precision. Logs contain only API access patterns, authentication events, system diagnostics, and performance metrics. XOPOZ processes data solely on the legal basis of user consent as defined in GDPR Article 6 paragraph 1 subparagraph a. There are no third-party processors involved in location data processing. XOPOZ acts as the data controller with full responsibility for compliance.
PART 8: SETTINGS AND CONFIGURATION

Intraday Tracking

Short
XOPOZ supports business-compliant time-based tracking. Set working hours for location monitoring. Outside those hours, GPS is blocked at the engine level. Perfect for employee privacy during off hours.

Medium
The intraday tracking feature lets you define a daily window during which GPS tracking is active. You set an independent start time and stop time, ranging from 1 AM to 11 PM. Outside this window, GPS requests are blocked at the engine level, not just paused. If an active tracking session is running when the stop time arrives, it terminates immediately. When the start time arrives, tracking resumes automatically through screen wake-up, motion detection, or device activity. No background timers are needed. A red intraday blocked label appears on the map during restricted hours. Real-time validation warns you if the start time is equal to or later than the stop time. This feature is essential for organizations that need to comply with employment regulations requiring tracking only during working hours.

Long
Intraday tracking is a business-compliance feature that addresses the legal and ethical requirements of employee location monitoring. Many jurisdictions require that employee tracking only occur during working hours, and XOPOZ implements this with precision. The feature provides two independent controls. The start time switch enables a configurable start hour from 1 to 23. The end time switch enables a configurable stop hour from 1 to 23. You can use start-only, end-only, or both for maximum flexibility. The configuration interface provides real-time feedback in plain language. With both controls active, it might read: Tracking is enabled between 08:00 until 18:00 every day. With only a start time: Tracking starts at 08:00 until midnight every day. If you configure the start time to be equal to or greater than the stop time, the text turns red with an exclamation mark indicating an invalid configuration. Enforcement happens at the GPS engine level. During restricted hours, the GPS location engine actively refuses location requests. This is not a UI layer filter. The system physically will not acquire GPS data outside the configured window. If an active GPS session is running when the stop time arrives, the session terminates immediately. There is no grace period. Tracking resumes when the window reopens, triggered by screen activation, hardware motion detection, or device activity events. No background timers need to run during the restricted period, which means zero battery impact during off hours. The map interface provides clear visual feedback. A red intraday blocked label appears below the GPS status indicator during restricted hours and automatically disappears when the tracking window reopens. This ensures both the device user and anyone glancing at the screen can immediately understand the current tracking state. All intraday configurations are limited to same-day periods. Overnight windows are not supported, which simplifies the logic and matches the most common business use case of daytime working hours.

Device Configuration and Personalization

Short
Customize each device with a unique name, color, emoji icon, and two-to-four-character ticker. Choose from one hundred curated device emojis. Changes apply instantly across all team views and the map.

Medium
XOPOZ lets you personalize each device for instant visual identification. Set a device name that defaults to your hardware model but can be customized freely. Choose a background color from a predefined palette that appears on map icons and team rosters. Select a device ticker, a two-to-four-character abbreviation that appears inside the map circle for quick identification. And pick an emoji icon from a curated selection of one hundred device-related emojis spanning smartphones, tablets, gaming devices, audio accessories, cameras, and smartwatches. The emoji selection interface uses a five-column scrollable grid with Android devices prioritized in the first twenty positions. One tap applies the emoji immediately. All changes propagate instantly across every interface, including the map, team roster, and notification displays.

License System

Short
XOPOZ uses a simple license model. No ads, no data selling, no freemium tricks. A straightforward license gives you access to all features with a defined device limit and expiration date.

Medium
The XOPOZ business model is transparent and respectful. There are no advertisements. There is no data monetization. There are no hidden upsells or feature gates. A license grants full access to all capabilities with a maximum device count and an expiration date. The license status is clearly displayed in Settings with the type, expiration date, active or expired indicator, and a manual refresh button. License information is cached locally for 30 days and refreshed automatically when the cache expires. The system enforces device limits at the point of device registration, preventing you from adding more devices than your license allows. Demo licenses are available for evaluation with the same feature set but limited duration.
PART 9: TECHNICAL EXCELLENCE

OS Kill Detection and Diagnostics

Short
XOPOZ detects when Android kills the tracking service in the background and shows you exactly when it happened. It educates users about operating system behavior instead of letting them blame the app.

Medium
Modern Android aggressively terminates background apps to save battery, and users often blame the tracking app for gaps in their location history. XOPOZ solves this with an innovative diagnostic system. Every time a GPS position is successfully acquired, the app updates a service life file with the exact timestamp. This file is deleted during a normal shutdown. If the file exists when the app starts, it means Android killed the service unexpectedly. XOPOZ then shows a clear, evidence-based popup explaining that the device's battery optimization terminated the tracking at the recorded time, along with instructions on how to exempt the app. This protects the app's reputation and empowers users to fix the real problem.

Long
One of the most frustrating aspects of Android GPS tracking applications is the aggressive background process termination that modern Android versions perform for battery preservation. Users see gaps in their tracking data and naturally assume the app is broken. XOPOZ addresses this head-on with an advanced diagnostic system that detects exactly when the operating system kills the tracking service and educates the user about what happened. The mechanism is elegant. A dedicated troubleshooting class maintains a service life file that records the timestamp of every successful GPS location callback. This file is updated continuously while the service runs and is explicitly deleted during a clean shutdown sequence. When the app starts and finds this file still present, it means the previous session did not end cleanly. The system recovers the last recorded timestamp and presents a blocking dialog to the user with evidence-based information. The dialog explains that the device's battery optimization terminated the tracking service at the specific recorded time. It clarifies that this is a device behavior, not an application malfunction. And it provides actionable guidance on how to configure the device to exempt XOPOZ from battery optimization. This system operates independently of shared preferences and relies solely on file system persistence, ensuring accuracy even if other app data is corrupted or cleared. The business impact is significant. It shifts the narrative from "the app is broken" to "my device killed the app." It reduces support tickets about tracking interruptions. It empowers users with specific, actionable solutions. And it builds trust by being transparent about the limitations of background operation on modern Android devices.

No Google Dependency

Short
XOPOZ works without Google Play Services. Direct GPS hardware access. OpenStreetMap for mapping. No Google tracking. No Google analytics. Complete independence from Big Tech infrastructure.

Medium
XOPOZ is designed from the ground up with zero dependency on Google services. GPS positioning uses Android's native Location Manager API, which talks directly to the phone's GPS hardware. Mapping uses OpenStreetMap with full support for custom tile servers. There is no Google Analytics, no Firebase, no Google Cloud Messaging, no Admob, no Google authentication. This architecture means XOPOZ runs perfectly on degoogled phones like GrapheneOS and LineageOS. It works on Huawei devices that lack Google services. It works in countries where Google services are restricted. For privacy-conscious users and organizations, this is not just a feature. It is a fundamental architectural guarantee that no Google infrastructure is involved in tracking your position.

Long
The decision to build XOPOZ without any Google dependency was deliberate and foundational. Most GPS tracking applications rely heavily on Google's infrastructure. They use Google's Fused Location Provider for positioning, which routes through Google's servers. They use Google Maps for visualization, which sends every map tile request to Google. They use Firebase for push notifications, Google Analytics for usage tracking, and often Google authentication for sign-in. Each of these dependencies creates a data pipeline to Google's servers. XOPOZ eliminates all of them. GPS positioning uses Android's native Location Manager API, a standard Android component that communicates directly with the phone's GPS chip and network positioning infrastructure without involving Google's fusion algorithms or data collection. Mapping uses the OSMDroid library with OpenStreetMap data, or any raster tile server you configure. Tile requests go to whatever server you choose, not to Google. Push-based messaging uses the app's own polling architecture through a periodic Worker that checks for new messages every fifteen minutes. Authentication is handled by XOPOZ's own backend with RSA 256 signed JWT tokens. There are no analytics services, no crash reporting services, and no advertising frameworks from any provider. This architecture is not just about privacy ideology. It has practical benefits. XOPOZ works on GrapheneOS, CalyxOS, LineageOS, and any other Android distribution that strips out Google services. It works on Huawei and Honor devices that ship without Google Mobile Services. It works in regions like China where Google services are blocked or restricted. For military and government use cases where Google infrastructure is not permitted in the operational environment, XOPOZ functions without compromise. The smaller dependency footprint also means a smaller attack surface, fewer potential points of failure, and a more predictable application behavior across the diverse Android ecosystem.
PART 10: ELEVATOR PITCHES

10-Second Elevator Pitch

Short
XOPOZ is encrypted GPS team tracking for professionals. No Google. No surveillance. Just secure, battery-efficient location sharing that works on any Android device.

30-Second Elevator Pitch

Medium
XOPOZ is a privacy-first GPS team tracker built for professionals in the field. Every GPS position is encrypted on your device before transmission. The server never sees your real coordinates. It works without Google Play Services, so it runs on any Android phone. The battery system intelligently switches between high-precision and low-power modes based on your movement. You can use any map server you want, from OpenStreetMap to your own private infrastructure. And privacy is the default. Nothing is shared until you explicitly choose. XOPOZ is how GPS tracking should work.

60-Second Elevator Pitch

Long
Imagine you are running a field team. Maybe it is a search and rescue operation, a construction crew, an expedition, or a group of journalists in a conflict zone. You need to know where everyone is, but you also need to know that location data is not being harvested, sold, or exposed. XOPOZ solves this. Every GPS position is encrypted with military-grade AES cryptography on the device itself, using team-specific keys that the server never sees. Even if someone breaches the server, they get nothing but meaningless encrypted blobs. XOPOZ does not use Google Play Services. It talks directly to the GPS hardware. It runs on degoogled phones, custom operating systems, and devices without any Google infrastructure. The battery optimization learns your movement patterns. When you are still, it conserves power. When you move, it activates instantly. You can track all day on a single charge. You choose your own map servers, set up points of interest with your team, configure geofence alerts, and even send encrypted emergency SOS messages with your GPS position. Privacy is not a marketing promise. It is the architecture. Nothing is shared until you opt in. Consent is explicit. Deletion is permanent and forensically secure. XOPOZ is tracking done right.

Two-Minute Full Pitch

Long
Let me tell you about XOPOZ. It is a professional GPS team tracking application, but it is fundamentally different from anything else on the market. The problem with existing trackers is simple. They work against you. Life360 sells your location data to data brokers. Google Maps shares your movements with advertisers. Most tracking apps drain your battery, require Google services, and store your raw GPS coordinates on their servers where anyone from hackers to government agencies can access them. XOPOZ inverts the entire model. Every single GPS coordinate is encrypted on your device before it goes anywhere. The encryption uses AES 128 bit with unique keys per team, generated locally and stored in the Android hardware security module. The server receives only encrypted data blobs. It stores them, relays them, but cannot decrypt a single one. Even a complete server breach reveals zero location information. XOPOZ talks directly to your phone's GPS hardware through Android's native APIs, completely bypassing Google Play Services. This means it works on any Android device. GrapheneOS. LineageOS. Huawei. Phones in countries where Google is blocked. Phones in military environments where Google infrastructure is not permitted. The battery system uses what we call the wake up fast, sleep slowly strategy. Hardware motion sensors that consume almost zero power detect when you start moving and instantly activate full GPS tracking. After five minutes of being stationary, the system gradually reduces to network-only positioning, cutting power consumption by up to ninety percent. You can run XOPOZ all day in the field on a single charge. The map is completely independent. Use OpenStreetMap out of the box, or configure any raster tile server you want. Your own corporate maps. Satellite imagery. Military mapping infrastructure. Offline tile caches for areas with no connectivity. The team system is device-focused. Each physical device is its own entity in the team, which means you can track vehicles, equipment, and individual devices independently. Teams are secured with cryptographic challenge authentication. The server proves membership through SHA 256 hash matching without ever seeing the encryption key. Additional features include encrypted emergency SOS alerts with stress-optimized user interfaces, a dual-tier point of interest system with private and shared team collections, a reverse geofencing system that runs detections on the device to protect privacy, granular privacy controls with intraday tracking for business compliance, data export in GPX and CSV formats, and complete GDPR compliance with secure file deletion. XOPOZ is built in Europe with European privacy values. No ads. No data selling. No surveillance capitalism. Just a transparent license model and a tool that respects its users. This is GPS tracking done right.
PART 11: AUDIENCE-SPECIFIC PITCHES

For Search and Rescue Teams

Medium
When you are coordinating a search and rescue operation, you need to see every volunteer's position in real-time without worrying about battery life, connectivity gaps, or data security. XOPOZ gives you that. Every volunteer's device appears individually on the map. Battery-optimized tracking runs all day. The encrypted SOS system lets anyone in the field send an emergency alert with their exact GPS position to the entire team. Geofence alerts notify you automatically when someone enters or leaves a search zone. And if Android kills the tracking in the background, XOPOZ detects it and tells the volunteer exactly how to fix their device settings. No Google dependency means it works on any phone your volunteers carry.

For Mountain Guides and Expedition Leaders

Medium
Leading a group through mountain terrain requires constant awareness of where everyone is. XOPOZ tracks each device independently on your map, so you see every client and every guide as a separate marker. The compass with its precision heading line helps you navigate by pointing your phone toward your destination, visible from close range all the way to the horizon. Battery optimization means your phone lasts the full expedition. Volume button zoom lets you navigate the map with gloves on. Your clients' locations are encrypted and never visible to the server. Configure your own offline map tiles for areas without cell coverage. And if something goes wrong, the SOS system sends an encrypted alert with coordinates to every team member instantly.

For NGOs and Humanitarian Organizations

Medium
Operating in sensitive regions means your staff's location data must be protected from every possible threat, including your own infrastructure being compromised. XOPOZ encrypts every GPS position on the device before transmission. Your server stores only encrypted blobs that are useless without the team key, which never touches the server. There is no Google dependency, so it works in any country regardless of tech infrastructure. Intraday tracking ensures staff are only monitored during working hours for employment compliance. The dual privacy system gives each team member independent control over their local storage and team sharing. All data handling is GDPR compliant with secure deletion and zero hidden backups. Staff locations stay protected even in the worst-case scenario.

For Journalists and Activists

Medium
Your location is your security. XOPOZ keeps GPS data encrypted on your device by default, with sharing only when you explicitly choose. There are no Google Play Services in the chain, which means no Google infrastructure sees your movements. The device-focused architecture means if you need to wipe a phone, the encryption keys go with it. Nothing recoverable stays on the server. Each team uses independent encryption keys, so compromising one team reveals nothing about another. Secure deletion overwrites files before removal, preventing forensic data recovery. Privacy controls let you appear completely offline to your team at any moment with a single switch. For journalists and activists, this is not just a feature list. It is a survival toolkit.

For Privacy-Conscious Consumers

Medium
If you have ever looked at what Life360 or Google Maps does with your location data and felt uncomfortable, XOPOZ is the alternative you have been waiting for. No ads. No data brokers. No Google services anywhere in the app. Every position is encrypted before it leaves your phone, and the server literally cannot see where you are. Only your team members, using the same encryption key, can decrypt your location. You control what gets saved locally and what gets shared, independently. You set how long data is retained. And when you delete something, it is overwritten and gone permanently. XOPOZ is tracking on your terms. Made in Europe with European privacy standards.
PART 12: FEATURE QUICK-FIRE LIST

Complete Feature Summary for Narration

Long
Here is the complete list of XOPOZ features. End-to-end AES 128 bit GPS encryption with team-specific keys. Two-tier key hierarchy with Android Keystore hardware protection. Zero-knowledge server architecture where encryption keys never leave the device. SHA 256 challenge-based team authentication. Device-focused team architecture where each device is an independent entity. Direct Android GPS API with zero Google Play Services dependency. Custom map tile server support with dynamic style switching. Three map navigation modes: tracking, free, and measurement. Precision compass with full-screen heading line using rotation vector sensor. Hardware volume button zoom for gloved outdoor use. Intelligent battery optimization with wake up fast, sleep slowly strategy. Hardware-accelerated motion detection for near-zero-power wake triggers. Automatic power mode switching between high-precision GPS and network-only positioning. Real-time movement detection with 50-meter threshold and directional arrows. Configurable location history trails from one hour to thirty-one days. Encrypted emergency SOS alerts with stress-optimized double-sized UI. Reverse geofencing with on-device boundary detection and encrypted notifications. Five-minute temporal hysteresis for geofence stability. Dual-tier point of interest system with private and team-shared collections. Up to ten thousand points organized in one hundred folders. Drag-and-drop POI organization and map-based repositioning. Dual independent privacy controls for local storage and team sharing. Four privacy configuration modes from full tracking to maximum privacy. Intraday tracking with configurable working hours and engine-level enforcement. GDPR-compliant data handling with secure byte-overwrite deletion. GPX and CSV data export with Android Storage Access Framework. JSON point-of-interest export with full hierarchy preservation. OS kill detection and user education system. Role-based team management with creator, admin, and member roles. Per-device visibility controls with hierarchical team tree view. One hundred curated device emoji icons for visual identification. Real-time distance display to team members with smart meter and kilometer formatting. Server-assigned device Security Identifiers for anti-spoofing protection. Configurable GPS refresh rates from ten seconds to ten minutes. Audio notification system with custom sound selection. Three-tier data deletion covering server, local, and complete account. Android backup protection disabling all system backup mechanisms. Offline geofence event queuing with unlimited persistence and automatic delivery. Cross-team device support with independent encryption per team. License management with device limits and expiration tracking. English language interface optimized for international professional use. Made in Europe with European privacy values and GDPR compliance.