What Counts as “Shared”

• Deploying the same config across multiple personal and work devices without glyph scope
• Forwarding or copying a config file to another operator or unauthorized system
• Running an issued tunnel outside the assigned jurisdiction or regional bias
• Allowing another user to route traffic through your device (e.g. via tethering or hotspot)

Risks Introduced by Sharing

• Zone Drift: routing logic fractures across mismatched geographies
• Device Variability: untrusted hardware undermines fingerprint mapping
• Audit Collapse: logs lose clarity and operator identity becomes untraceable
• Bandwidth Bleed: multiple sessions drain node provisioning pools
• Tier Erosion: sponsors may lose Tier status due to glyph misuse

Infrastructure Hygiene

• Each config is calibrated to region, role, and fingerprint
• Duplication introduces entropy and trust ambiguity
• Nodes monitor config lineage for signal behavior anomalies

Lifecycle Enforcement

• Shared configs may auto-expire based on entropy scoring
• Node anomalies can trigger silent lockout or Tier rollback
• EcoVPN reserves the right to revoke any duplicated config without notice

Protect Your Glyph

• Treat your config like a cryptographic key, singular, entangled, and non-transferable
• Reissue glyphs only via sponsor review channels
• Monitor usage patterns and jurisdiction fidelity weekly

“When two endpoints share a glyph, only one remains trusted.”