Skip to content
Documentation navigation

Start here

Product

Integrations

SDK

MCP

Security and privacy

Public and internal data

Upweight's public boards, roadmaps, and published changelogs are customer-facing. Do not put confidential material in request titles, descriptions, or public comments. RevenueCat explains optional revenue matching and classification privacy. Revenue information is non-public and accessible to authorised owners and admins, including through MCP; SDK responses contain no revenue fields. Pausing public submissions does not hide the board list or public roadmap. See Public boards.

Customer identity and email

Board customers sign in separately from workspace owners. An app integration supplies an app-user identity; do not describe that identity as independently verified by Upweight. SDK profile responses expose whether an email exists, not the email address itself. SDK-supplied email is unverified; see Shipped-update emails for eligibility and unsubscribe rules. Public conversation may show a customer's display name. Avoid including customer email addresses in public request content.

Credentials and keys

For AI-client access, read the MCP overview, client setup, and MCP troubleshooting.

When you connect App Store Connect, the private key is encrypted at rest. Key ID and Issuer ID are stored as identifiers, not encrypted secrets. MCP tokens are stored as SHA-256 hashes. SDK publishable keys are stored as a hash and prefix, with the plaintext shown only once when issued. Copy a new key at that point and keep account access limited to the people who need it.

These protections are specific storage controls, not a claim of end-to-end encryption or compliance certification.

Read the privacy policy for data-handling information and the terms for service terms. Use the contact details published in the privacy policy for privacy questions. See Team and roles to review team access.

For in-app feedback, see the SDK overview, Swift SDK guide, and HTTP API reference.

Last reviewed