Support
Tell us what happened. Give us the identifiers.
We handle account, transaction, data-rights, and technical questions for the U.S. marketplace by email.
Email hello@ineeddata.ai from the address tied to your account whenever possible. We do not currently offer phone or live-chat support.
Sign-in codes, Google sign-in, API keys, management links, and account security.
Email support →Bounties & submissionsContract setup, publishing, uploads, validation, samples, review, and acceptance.
Email support →Payments & payoutsAcceptance payments, contributor onboarding, delayed transfers, refunds, and disputes.
Email support →Privacy, safety & rightsPrivacy requests, prohibited data, copyright or license concerns, fraud, and security.
Email support →What to include
- Your ineeddata account email.
- The bounty, submission, report, payment, charge, or transfer ID involved.
- What you expected, what happened, and the approximate time it happened.
- The page URL, exact error message, and a screenshot when useful.
- For a rights report, the material at issue, your relationship to it, and evidence supporting the claim.
Clear identifiers let us find the frozen contract, audit trail, validation result, or Stripe event without asking you to resend sensitive material.
What never to send
- A one-time sign-in code.
- A complete API key, private management link, or submission token.
- A password from another service.
- A full card number, bank-account number, tax identifier, or identity document.
- An entire sensitive dataset when an ID, redacted screenshot, or small safe excerpt will explain the issue.
We will not ask for these secrets by email. If a credential was exposed, say which kind and when; revoke or replace it from the account controls where available.
Payment and payout help
For refund eligibility and chargebacks, read the Refunds & Disputes Policy. For a delayed contributor payout, confirm that Stripe onboarding shows ready in your account and include the bounty and accepted submission IDs.
Stripe may require the account holder to complete identity, tax, bank, or risk checks directly in Stripe’s interface. Send those details only to Stripe through the authorized onboarding flow, not to us by email.
Safety, privacy, and rights reports
Use a descriptive subject such as “Urgent security issue,” “Privacy request,” or “Rights report.” We may preserve access logs, freeze a bounty or payout, limit file access, and ask for more evidence while reviewing a credible report.
A report is not automatically shared publicly. We may share the minimum necessary information with the affected participant, Stripe, a service provider, counsel, or authorities when needed to investigate or comply with law.
Response and resolution
We prioritize account-security, payment, prohibited-data, and rights issues, but do not promise a fixed response time. Complex payment or rights reviews can depend on another participant, Stripe, a bank, or additional evidence.
Keep the original email thread and do not open duplicate requests for the same issue. We will tell you when we need more information and, where appropriate, explain the decision or next step.
Use your account email and put the bounty or submission ID in the message.