Installed
Mack remains in control
Orbit separates identity, access, permission, and approval. Sensitive communication and account changes keep the rules that apply to that exact destination and action.
Orbit Security
Control should be understandable before it is powerful.
Orbit Security brings together access boundaries, local observations, recent blocked requests, and known gaps. It is designed to show where protection is active, partial, or unavailable—not to turn missing information into reassurance.
Installed
Private information stays scoped
Private profile information and credentials are separated from page content and public conversation. A message from outside the private owner context cannot grant new authority.
Partial by provider
Connections preserve identity
Google accounts, WhatsApp, Instagram, Discord, Contacts, files, and other connected areas retain separate identities and boundaries. Being connected on one service does not authorize another.
Installed
Changes remain recoverable
Protected updates use review, saved-state checks, verified installation, and rollback material. Failed or uncertain operations are reconciled before they are repeated.
Current protections
Security is more than a scanner.
Identity and communication
Contact bindings use observed provider identity rather than trusting a name or profile image alone. Public conversations stay within their audience and cannot create private development authority. Outgoing communication follows its configured review rules.
Accounts and services
Connected accounts remain separated by provider and account. A connection proves an available route; it does not mean Orbit may perform every possible action. Authentication challenges and provider limits remain real.
Files and storage
Supported file operations use bounded locations, trusted-path checks, source-preserving behavior, and reviewed transfers. A drive being visible does not automatically make it writable.
Private storage and recovery
Protected information uses private stores and operating-system-backed key handling where supported. Authentication failures preserve unreadable information for recovery instead of quietly replacing it. Encryption cannot protect an already-unlocked computer from an attacker who controls it.
Evidence and release safety
Plans, code, tests, installed behavior, and owner acceptance are different stages. Orbit’s release process preserves that distinction so an unfinished feature cannot become a public security promise.
Honest coverage
What Orbit Security does not currently claim
No complete malware scan or endpoint detection service
No packet capture or network perimeter enforcement
No automatic whole-computer isolation
No active home camera or alarm monitoring without setup
No tested full-backup restoration coverage
No proof that every connected provider feature is available
The current local security view is a partial monitoring and control layer. On Fedora, Windows-only Firewall, Defender, and BitLocker readings are unavailable and remain unknown.