Proton Partners Setup and Privacy-Safe Messaging

- Privacy-focused support pages have no consistent affiliate recommendation strategy. - Copy mixes personal-privacy suggestions with enterprise account requirements. - Team cannot quickly identify where Proton links are currently used.

- No content governance layer for privacy affiliate links. - Lack of mapping between support categories and partner relevance. - Incomplete disclosure rollout across support layouts.

Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

- Use registry-based placement so Proton links only appear in relevant privacy/security topics. - Keep guidance neutral and avoid suggesting migration away from corporate-managed systems. - Add clear disclosure and status badges for partner links. - Review content quarterly for policy alignment and conversion quality.