Contact
Talk directly to Paydirt.
Email hello@paydirt.ai. Messages go to the team responsible for the product, SDK, API, Slack app, and MCP service.
Implementation
Include the app platform, subscription provider, SDK version, bundle identifier, expected trigger, and what you observed. Never email production API keys, access tokens, or customer feedback.
Security
Use “Security” in the subject. Send an initial description and reproduction steps without live customer data. We will arrange a safer channel when needed.
Privacy and deletion
Identify the Paydirt account and app, describe the access or deletion request, and use the email address associated with the account so ownership can be verified.
Billing and product
Tell us which workflow you are evaluating—RevenueCat cancellation feedback, Slack delivery, agent analysis, or recurring reports—and the outcome you need.
What happens next
Paydirt reviews support messages during United States business days. Urgent security reports are prioritized. A useful implementation report includes the exact route or form, timestamp, non-secret request identifier, expected result, actual result, and whether the event came from a development, TestFlight, or production build. Screenshots are welcome after personal data and credentials are removed.
Agents should begin with the public documentation and structured error resolution hint before contacting support. If the hint does not resolve the issue, include the response's stable error code and request ID. Paydirt will never ask for a Slack bot token, RevenueCat secret key, or account password by email.