What the policy controls
A policy can only narrow what the app’s code turned on: it never turns on capture that the
app turned off, and never unmasks what the app masks.
Replay and text masking apply to session replay, which no Apsio SDK ships yet.
How fast a change arrives
A change reaches the edge within about two minutes. Each device then picks it up at its next fetch: the next launch, or within 15 minutes while the app is open. Devices that are offline keep using the last policy they received.Disabling an app
Disabling an app turns its kill switch on at once, whatever its policy says, and the ingest endpoint stops accepting its data. Enabling it again restores the policy.What your plan adds
Two states of your organization override the policy at the edge, for every app:- At your plan’s cap (the trial’s 25k sessions, Solo’s 10k, or the spend cap you set on Pro), session sampling is served as 0%: new sessions send no detail, while crashes, errors and session counts keep flowing. Your own sampling rate comes back when the cap lifts. See Pricing.
- When the trial ends without a plan, the kill switch is on, and the ingest endpoint
answers
402.