Draft Rules May Make Alisa an Undeletable System Assistant on Phones
Draft Russian rules reported around September 11, 2026 would push Yandex’s Alisa AI toward status as a system-level, effectively undeletable assistant on smartphones sold or configured for the domestic market. Coverage cited by 1RU describes Ministry of Digital Development engagement with market participants, notes Alisa’s weekly audience on the order of forty-one million, and flags RATEX industry pushback seeking delay. The proposal is about default device posture—not about opening model weights.
Filed under Policy and dated September 13, 2026, this AI4Russia briefing treats the Alisa mandate talk as Russian platform-regulation news separate from earlier open-model releases. Forcing a preinstalled assistant raises classic questions of competition, user consent, storage overhead, and whether rivals can still surface alternative assistants without friction. Handset makers and app stores would need clear technical specs if undeletable status becomes binding.
Why it matters: Russian consumers and enterprises already navigate app-store fragmentation and import-substitution pressure. A non-removable assistant can standardize voice and search entry points—but it can also entrench one vendor’s telemetry and ranking choices unless opt-down paths and auditing remain real.
What it means in practice
Russian product and compliance leads should inventory which device SKUs would carry a mandatory Alisa surface; confirm personal-data processing notices; assign a privacy owner; run time-boxed usability tests comparing mandatory versus optional assistant setups; and document how users disable network features even if the binary stays. Prefer contractual clarity on update channels and offline behaviour if connectivity fails.
Caveats come first. Drafts can be watered down; RATEX delay requests may succeed; and weekly audience figures are vendor-adjacent claims. AI4Russia therefore presents the undeletable-assistant idea as directional regulatory context until a final Minsifry instrument is published.
What to watch next: whether the ministry issues a formal draft for comment; how RATEX and OEMs respond on storage and competition grounds; and whether alternative assistants retain equal deep-link rights. Readers can continue on the AI4Russia homepage for related stories, or browse the Newsroom for additional briefings.
Bottom line: treat this update as orientation, not instruction. Russian on-device AI policy is contested and still early. Organizations that benefit most will test defaults carefully, measure user harm honestly, and keep humans accountable for consent and data flows.