Summary
The mobile core is the network’s real-time engine: it authenticates your SIM/eSIM, applies live policy/priority, routes voice/SMS/data, and keeps sessions going as you move.
It touches transient operational signals to make service work, but it doesn’t have to become a long-term, identity-linked archive, that outcome is a back-office (OSS/BSS) design choice.
In our model, the “brain” (OSS/BSS) is built to avoid identity-linked archives. We also run anonymous signup & systems, don’t collect PII, keep operational records minimal and short-lived, and don’t monetize customer data.
When we use a host’s radios for coverage, the host sees radio events and cell context, but does not receive PII or any identity mapping from us. Mass surveillance doesn’t work here; targeted access must follow court-supervised, multi-party process.
The REALLY PrivateCore™ includes our own mobile core, OSS/BSS, anonymous signup and systems, our own locked down servers (not vulnerable cloud) and an included VPN.
The critic’s question
“Isn’t the mobile core where my personal data and history live?”
Answer: No. The core is the live switchboard/engine for connectivity. Account, history, retention, and sharing are governed by the OSS/BSS ‘brain’—and our brain is designed to avoid identity-linked archives.
What the mobile core does
Authenticate & attach – Confirms your SIM/eSIM can join the network.
Apply live policy/QoS – Enforces plan rules (priority, throttling/deprioritization, roaming permissions).
Route traffic – Sets up voice/SMS control and data paths to the internet and interconnects.
Maintain mobility – Keeps calls and data alive across cell/technology changes (LTE ↔ 5G).
Enable features – Coordinates modern call paths (e.g., VoLTE/VoNR where available), Wi-Fi Calling behavior, emergency calling logic.
Under the hood: what the core actually handles
Registration & reachability – Keeps your phone “known” so it can be paged for incoming calls/SMS/data.
Session management – Sets up/tears down data sessions; maintains them during movement and handovers.
Fine-grained policy – QoS/priority per line/flow; gating/shaping based on plan and conditions.
Addressing & routing – IP allocation and traffic steering through user-plane nodes; path selection for roaming/interconnect.
Voice/SMS plumbing – Call setup/teardown via IMS for VoLTE/VoNR; SMS over LTE/5G control; emergency call handling.
Security at attach – Cipher/integrity negotiation; resistance to legacy downgrades where devices allow.
Slicing / APN/DNN selection – Choosing the right data network/slice when applicable.
Real-time charging signals – Emits usage events so plan rules work (the brain determines retention, and we keep it short-lived).
Logs & usage data: what exists vs. what matters
The core necessarily touches (transient by nature):
Session state & signaling (attach, bearer setup, handovers, policy decisions).
Counters/usage signals for live enforcement (e.g., throttling triggers).
Operational metrics (health, alarms, KPIs).
Where privacy risk usually appears:
Turning those signals into a long-lived, identity-linked dossier—that typically happens in traditional OSS/BSS. It’s a design/retention choice, not an inherent property of the core.
Our posture:
Anonymous signup & systems; no PII collected.
No subscriber-identity mapping kept and no centralized, identity-linked archive.
Minimal, short-lived operational records with published ceilings and automated deletion.
Strict interface controls (field whitelists; minimal exports).
No data monetization.
What a host network can still see (and what it can’t)
When a host provides radios for coverage:
The host can see (radio/operations level):
Radio events: attaches/detaches, handovers, paging responses.
Cell/site context: which tower/sector served a device at moments in time.
Operational identifiers used for RF/service continuity and the host’s own operational logs.
Basic volumes/timings for RF management (e.g., connection start/stop times, data amounts).
The host cannot see via us:
No PII from us.
No subscriber-identity mapping from us. We don’t create or keep a table tying a person to network identifiers—so we don’t send any.
No centralized, identity-linked archive via us. There’s no one-stop dossier exposed through us.
No data-monetization feeds.
Practical meaning:
The host has radio-layer logs like any network, but not a join to personal identity from us.
To target an individual, authorities must use due process across multiple parties (host, apps/clouds, banks, device forensics, etc.). There’s no bulk, one-stop handover from us.
Why this matters
Reliability: The core’s millisecond-level decisions keep calls stable and data flowing.
Privacy: The presence of a core doesn’t require a dossier. That outcome depends on the brain’s (OSS/BSS) retention and export choices—ours avoid identity-linked archives by design.
Honest limits
PSTN isn’t end-to-end encrypted. We favor modern, encrypted legs where available (e.g., VoLTE/VoNR), but the PSTN path includes non-e2e segments by nature.
Roaming/interconnect posture varies. Older paths can reduce security on some segments; we document device/network guidance and prefer modern legs
Compromised endpoints leak. Device-level hygiene still matters; the core can’t fix malware/spyware on a handset.
Proof & verification (in progress)
Architecture diagram separating control/user plane and showing where live policy/auth happen.
Call-/data-path captures demonstrating modern legs on supported devices.
Retention Matrix (core-related logs) with short ceilings and automated deletion test results.
Interface inventory confirming which core signals exist only transiently and do not become an identity-linked archive.
Transparency counters summarizing lawful requests received/complied/narrowed/rejected (core-relevant scope).
Join the only carrier that makes privacy non-negotiable.
