Product and wallet workflow support
Include the Slingzero page you were using, the selected network, the complete public token or coin address, your wallet's public address when relevant, the transaction hash if one exists, and the exact error message. Explain what you expected and what happened. Screenshots are useful after any secret or unrelated personal information has been removed. Slingzero cannot recover a seed phrase, private key, lost wallet, or reverse a confirmed blockchain transaction.
Developer and agent integration help
For the public Token Pages API, MCP server, A2A agent, NLWeb endpoint, or discovery files, include the endpoint, HTTP method, response status, request ID, and a minimal sanitized request. Start with the Slingzero developer portaland OpenAPI specification. Never email API credentials, bearer tokens, cookies, wallet signature material, private keys, or seed phrases.
Security reports
Use the subject “Security report” and provide reproducible steps, affected URLs, expected impact, and a safe proof of concept. Avoid accessing data that is not yours, disrupting availability, moving assets, or publicly disclosing an unpatched issue. Review the Security page before testing or reporting.
Token Page and content reports
Token Pages are user-published. Include the exact page URL, network, complete token address, the specific text or media at issue, why it violates rights or platform rules, and evidence that lets Slingzero evaluate the report. A page's presence is not an endorsement, audit, verification, certification, or investment recommendation.
Privacy requests and response expectations
Identify the relevant Slingzero record or public wallet address and the right you want to exercise. We may need enough information to verify and locate the request, but you should not send secrets. Public blockchain and IPFS records may remain available independently of Slingzero. See the Privacy policy for the data categories, purposes, retention details, and available rights that apply to your location.
Send all requests to [email protected]. Use a descriptive subject and keep the full conversation in one thread so the relevant context and request ID remain available.