Back to The Gateway

Contact and intake privacy

Intake should collect only what is needed to help.

The Gateway support, sponsor, appliance, MSP, evidence, and security paths should avoid credential custody and unredacted topology.

Minimize

Collect request type, deployment mode, hardware class, route/DNS/fallback goal, privacy posture goal, and redacted evidence.

Do not request

Private keys, tokens, passwords, full packet captures, unredacted topology, or credential custody by default.

Remote access

Remote access must be explicit, time-limited, revocable, logged, and approved for the specific request.

Retention

Retention expectations should be clear before support bundles or evidence are shared. Before attaching logs or screenshots, review the support bundle redaction guide. Website measurement should follow analytics privacy rules.

Security

Vulnerability reports should follow SECURITY.md, start with minimal detail, and should not be filed as public issues.

Separation

Sponsor, support, appliance, MSP, evidence, and security paths should stay distinct.

Next action

Use redacted intake for guided support.

Prepare request type, deployment mode, route/DNS/fallback goals, privacy posture goal, and redacted evidence. Review the redaction guide before attaching logs or screenshots.