Porta Support

Before contacting support

• Update to the build you are testing and reproduce the issue once.
• Record the Porta version and build number, platform version, device model, and the time of the failure.
• Describe the action, expected result, actual result, and whether the same host works from another SSH client.

Keep secrets out of the report

• Do not send passwords, private keys, passphrases, API keys, recovery codes, access tokens, or raw provider credentials.
• Redact public and private IP addresses, usernames, repository URLs, local paths, terminal output, push targets, and account identifiers unless they are essential to the diagnosis.
• Use the smallest diagnostic excerpt that still shows the failure and include a trace identifier when Porta displays one.

Safe diagnostic allowlist

• Include only Porta version/build, operating-system version, device model, UTC timestamp, feature name, redacted error code, and a Porta trace identifier when one is shown.
• Do not attach automatic archives: Porta does not currently offer a public support-bundle exporter.
• Never include terminal content, commands, environment values, hostnames, IP addresses, usernames, repository paths, keys, tokens, or credentials.

Account and billing

• For sign-in, include the identity provider and the point where the flow stopped, but never include an authorization code or token.
• Subscriptions purchased through Apple or Google are managed by that store. Include only the store, product name, and redacted transaction timing in a support request.

Response expectation

Porta does not publish a support SLA yet. Include a reply address and mark genuinely time-sensitive requests in the subject; support will confirm when triage begins.

Delete your Porta account