Support
Send the information support can safely use
Use your customer or reseller support area for account-specific help whenever possible. Public email is shown only when a valid support address is configured by the operator.
Last reviewed
Include
- Your account email
- Customer-safe operation or transaction reference
- Desktop version and Windows version
- Model, Android version, and build shown by the app
- Exact customer-facing error message and time
Do not send
- Passwords or recovery codes
- Private service files or confidential credentials
- Full ADB logs containing sensitive device data
- Unredacted payment data or unrelated personal information
Contact channel
If no public support email is configured, sign in and open a support ticket so the request is linked to your account safely.
What happens next
Support first verifies the account or customer-safe reference, then routes the request to account, compatibility, billing, reseller, or security review. Response time depends on the evidence required and whether a connected-device result must be checked.
Security reports
For a suspected vulnerability, include the affected URL or app version, concise impact, and safe reproduction steps. Do not access other users’ records or attach secrets.
Prepare a useful support request
Describe the expected result, the exact customer-facing result you received, and the last safe step completed before the problem appeared. Include the local time and time zone so support can correlate the request with protected server records without asking for private logs.
For model or compatibility questions, copy the complete Pixel product name and Android build shown by trusted device information. For billing or operation questions, use the customer-safe reference from the portal instead of sending full identifiers, payment details, passwords, or confidential service files.