Users remain in control.

Disconnecting Rollup stops access across Profile, Query, and Search.

1. Stop processing new media and disable local Search when the user disconnects or revokes Photos access.
2. Remove Rollup’s local index, private derived representations, and cached Search results on disconnect.
3. Remove the user’s server-side Rollup context and representations used for Profile and Query.
4. Make subsequent Profile and Query service requests return 404 context_not_found.
5. Notify the host application so it can discard cached profiles, query answers, and local references and return to a non-personalized experience.

Client#

try await Rollup.disconnect()

Server behavior#

{
  "error": {
    "code": "context_not_found"
  }
}

Changes to photo access#

If the user narrows their Photos selection, stop using removed assets and invalidate affected local results and derived context. Coverage must reflect the remaining authorized history. Removing Rollup’s index does not delete the user’s original photos or videos.

Treat disconnect and revocation as cache invalidation events in your application. Cached Profile and Query responses must not keep personalization active after access has ended.