docs(rokt): session management guidance for the kit

kits/rokt/rokt/README.md

@@ -1,4 +1,4 @@
 # Rokt Kit Integration
 
 This directory contains the [Rokt](https://docs.rokt.com/) integration for the [mParticle Android SDK](https://github.com/mParticle/mparticle-android-sdk).
 
@@ -74,6 +74,36 @@
 )
 ```
 
+## Session management
+
+Rokt sessions are managed automatically. Placements shown to the same user share one session, and **the kit ends the Rokt session whenever the mParticle user changes**:
+
+| Identity transition | Rokt session |
+|---|---|
+| Anonymous user is identified (e.g. unknown on the payment page, known on the confirmation page) | **Kept** — same person, in-session state survives |
+| A different user identifies or logs in | **Ended** — the next placement starts a new session |
+| The current user logs out | **Ended** |
+
+No integration code is needed for this behaviour.
+
+### Self-service terminals (kiosks, shared devices)
+
+Where a queue of unrelated customers uses one device, the recommended pattern is to **log the user out (or identify the next customer) between transactions** — the kit resets the Rokt session at that boundary, so each customer's placements and events land on their own session.
+
+A manual reset is also available for explicit control, called on the Rokt SDK directly:
+
+```kotlin
+import com.rokt.roktsdk.Rokt
+
+Rokt.clearSession()
+```
+
+Notes:
+
+- The new session begins on the **next** `selectPlacements` call; `clearSession` only ends the current one.
+- Calling `clearSession` with no active session (or before init) is a no-op, and it is safe to combine with the automatic behaviour — both converge on the same idempotent reset.
+- Avoid enabling Rokt experience caching on shared terminals: a cached experience belongs to the customer it was fetched for.
+
 ## Documentation
 
 [Rokt integration](https://docs.rokt.com/developers/integration-guides/android/overview)