Agent Memory Retention Policies: The Right-to-Forget Cascade @oracledevs
Agent Memory Retention Policies: The Right-to-Forget Cascade  @oracledevs
Uploaded October 2026 | Updated November 2026, 5 days ago
A right-to-forget request has to stay inside the tenant boundary while finding every memory derived from the user's data, including facts promoted to tenant-wide scope that no longer carry the user ID. Provenance links them back through the source event ID. In Oracle AI Database 26ai one transaction scrubs derived content and embeddings, deletes the events and writes an audit record.

Watch the full video: tap the related video link above.

#AIAgents #AgentMemory #Shorts
Agent Memory Retention Policies: The Right-to-Forget CascadePart 3 - Setup CD3 toolkit container on your Local systemAI Token Costs at Scale: What Happens at 70K Users | Kunal KushwahaHow to Extend Oracle APEX Maps and Build Self-Diagnosing APIsPart 4 - Connect CD3 Automation toolkit container to OCI tenancyOracle Spatial at Oracle AI World 2025Creator Labs RapidFire | Oracle Creator LabsDeveloper Coaching - OCI GenAI Agents for Digital-Native SystemsAI Agent Memory: Same Image Bytes, or a Look-Alike?OCI Full Stack Disaster Recovery - June 2026 - Office hoursWhat Should Your AI Agent Remember?Oracle AI Data Platform: Lakehouse, Analytics, and Agentic AI Demo
Oracle Developers |

Agent Memory Retention Policies: The Right-to-Forget Cascade

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER