[
    {
        "q": "Why did Vyla transition from a web app to Vyla Home?",
        "a": "Web-based media centers are constantly vulnerable to datacenter IP blacklisting, upstream downtime, and web-browser sandbox limits. Transitioning to a native application permits decentralization directly over local networks with hardware-accelerated playback."
    },
    {
        "q": "Why does Windows SmartScreen flag the installer?",
        "a": "Windows SmartScreen flags newer binaries that have not yet accumulated arbitrary trust reputation telemetry or paid EV code-signing signatures. Every build is built transparently and verifiable directly on GitLab."
    },
    {
        "q": "How are my settings, bookmarks, and watch history protected?",
        "a": "All user data is stored locally in an AES-256-GCM encrypted database keyed to your device hardware profile. No usage logs, browsing history, or playback metrics are ever transmitted to external servers."
    },
    {
        "q": "How does the update mechanism ensure binary integrity?",
        "a": "Releases are validated against cryptographic checksum hashes pulled directly from the GitLab package registry before patching or staging executable files."
    },
    {
        "q": "Does Vyla Home require external runtime dependencies?",
        "a": "No. The application bundles its playback core, local server, and storage drivers in a self-contained runtime without requiring third-party libraries."
    },
    {
        "q": "Is Vyla Home open-source and free?",
        "a": "Yes. Vyla Home is free, community-driven, and maintains its repositories and release builds openly for public inspection."
    }
]