Apple Adds Auto-Delete to Siri App in iOS 27

According to reporting by Bloomberg's Mark Gurman and follow-up coverage in The Next Web, 9to5Mac, MacObserver and 36Kr, Apple plans a standalone Siri app in iOS 27 that maintains searchable conversation history and offers auto-delete settings of 30 days, one year, or indefinite retention. Reporting says the app will accept both voice and text input, allow file uploads, surface web-sourced answers with images and formatted lists, and let users choose whether the app opens to a grid of prior conversations or a new chat. Bloomberg's reporting, as summarized by multiple outlets, says the assistant may still ship with a "beta" label, and that Apple intends to run a Gemini-powered Siri via its Private Cloud Compute, with Bloomberg reporting an annual payment of roughly 1 billion dollars for a custom 1.2-trillion-parameter Gemini model. Multiple outlets also report a system called Extensions that would let users route Siri queries to alternative chat models.

Industry-pattern observations: Conversation retention settings are a direct tradeoff between on-going personalization and user privacy. Limiting or automatically deleting history reduces the available context memory that many modern assistants use for multi-turn state, few-shot personalization, and lightweight retrieval-augmented responses. For practitioners, that means prompt engineering and session state management will become more important when working with assistants that expose short retention windows rather than long-term memories.

Industry-pattern observations: Routing requests through third-party models via an Extensions mechanism increases architectural complexity for integrators and raises interoperability questions. When mobile OSes support multiple backend models, teams that integrate with system assistants will need robust model-agnostic prompts, consistent input preprocessing, and careful handling of attachments and file parsing across provider APIs.

Public reporting frames Apple as advancing a privacy-first UX for conversational AI at a time when competitors are experimenting with temporary chat modes and persistent memories. The privacy design choices reported here align with wider market dynamics where vendors trade data persistence for legal and regulatory assurances, and where partnerships with large model providers reshape who controls inference and data flows.

Bloomberg's reporting that Apple is contracting for a custom Gemini variant and routing some workloads through Private Cloud Compute highlights a broader industry pattern where device vendors combine third-party frontier models with proprietary cloud stacks. That pattern affects latency, cost, and the surface area for compliance and data-protection controls that engineering teams must manage.

• •Watch WWDC 2026 for confirmation and official feature definitions, including whether Apple documents retention defaults and enterprise controls.
• •Observe developer documentation for the reported Extensions API to see how third-party models receive queries, what metadata is passed, and what privacy guarantees are documented.
• •Monitor any filings or follow-up reporting about the reported Gemini contract and Private Cloud Compute arrangements for details on data handling and training usage.
• •Track how the beta label is applied and whether telemetry or opt-in toggles are exposed to developers and enterprise admins.

For practitioners: If the reported auto-delete defaults are enforced at the platform level, teams building assistants, plugins, or integrations should plan for shorter-lived conversational context and design explicit state persistence strategies that respect user privacy settings.