Harden SMS trigger permission and privacy UX #8

New issue

Open

opened 2026-09-16 01:09:38 +02:00 by morten-olsen · 0 comments

morten-olsen commented

2026-09-16 01:09:38 +02:00

Owner

Context

SMS receive/send adapters exist, but their permission, distribution-policy, and sensitive-payload behavior needs a deliberate user-facing contract.

Scope

Explain permission and platform availability before a workflow is enabled.
Surface store/distribution policy implications without implying unsupported availability.
Define sensitive SMS payload persistence and redaction behavior before storage.
Keep receive events and current-state/action contracts distinct.

Acceptance

Missing permissions and unsupported devices have actionable availability messages.
Sensitive sender/body data follows a documented persistence policy.
Activity/debug views do not expose more SMS data than the policy permits.
Existing SMS workflows fail explicitly rather than silently.

## Context SMS receive/send adapters exist, but their permission, distribution-policy, and sensitive-payload behavior needs a deliberate user-facing contract. ## Scope - Explain permission and platform availability before a workflow is enabled. - Surface store/distribution policy implications without implying unsupported availability. - Define sensitive SMS payload persistence and redaction behavior before storage. - Keep receive events and current-state/action contracts distinct. ## Acceptance - Missing permissions and unsupported devices have actionable availability messages. - Sensitive sender/body data follows a documented persistence policy. - Activity/debug views do not expose more SMS data than the policy permits. - Existing SMS workflows fail explicitly rather than silently.

morten-olsen added the

feature

label

2026-09-17 08:19:57 +02:00