docs: Add documentation about apply

README.md

@@ -62,4 +62,15 @@ The OpenFeature Events `ProviderStale` and `ProviderReady` events will be emitte
 
 Notes:
 - If a flag can't be resolved from cache, the provider does NOT automatically resort to calling remote: refreshing the cache from remote only happens when setting a new provider and/or evaluation context in the global OpenFeatureAPI
-- It's advised not to perform resolves while `setProvider` and `setEvaluationContext` are running: resolves might return the default value with reason `STALE` during such operations.
+- It's advised not to perform resolves while `setProvider` and `setEvaluationContext` are running: resolves might return the default value with reason `STALE` during such operations.
+
+## Apply events
+This Provider automatically emits `apply` events to the Confidence backend once a flag's property is read by the application. This allows Confidence to track who was exposed to what variant and when.
+
+_Note: the `apply` event reports which flag and variant was read by the application, but not which property the application has read from such variant's value._
+
+To avoid generating redundant data, as long as the flags' data returned from the backend for a user remains unchanged, only the first time a flag's property is read will generate an `apply` event. This is true also across restarts of the application.
+
+The Provider stores `apply` events on disk until they are emitted correctly, thus ensuring the apply data reaches the backend even if generated when there is no network available (assuming the device will ever re-connect to the network before the application is deleted by the user).
+
+<!-- Add link to the more detailed documentation on apply events in the Confidence portal once it's ready -->