Fund the Bit
Fund the Bit
ExploreHow it worksSafetyCreators
Sign inApply

Policy center

Creator-approvedNo dangerous daresCreator responsibilityRefund reviewPrivacy basicsReport a concern

We've got your back.

These rules are built for fans and creators to make fun things happen safely and fairly.

Report a concern

Policy center

Safe bits. Clear rules.

Refunds when the bit does not land

Challenge funding needs a clear review path: canceled campaigns, expired campaigns, safety issues, failed payment states, and disputes all need traceable handling.

Refunds
Creator-approvedEvery campaign is reviewed by real people.No dangerous daresZero tolerance for harmful or risky prompts.Creator responsibilityCreator fulfillment belongs to the creator, not the website.Refund reviewIf something is off, the team reviews it.Privacy basicsPayment cards stay with Stripe, not Fund the Bit.Report a concernReports go into review without external notifications.

When fans may be eligible

Refund eligibility depends on the campaign state, payment state, creator completion, optional proof outcomes, and safety review.

  • Campaign expires before funding or is canceled before completion.
  • Admin review finds a safety, policy, creator completion, optional proof, or payment issue.
  • Payment capture, settlement, webhook, or reconciliation fails.

How review works

Refund decisions should be handled from admin tools with audit logs and Stripe reconciliation.

  • Support gathers context, then admin reviews campaign, report, completion, optional proof, and payment records.
  • Destination charge refunds may require transfer reversals depending on the Stripe flow.
  • Refund and dispute decisions should be documented before communicating final status.

What is not allowed

Refunds cannot turn the product into a raffle, prize pool, or speculative betting mechanic.

  • No fake urgency or pressure to pledge.
  • No refund promise before the review is complete.
  • No live refunds or payout changes without explicit approval.

Support path

Fans should use report/support flows when something looks unsafe, inaccurate, or incomplete.

  • Report a concern from challenge pages or the report page.
  • Support macros are drafted for refund, canceled challenge, optional proof rejected, and payout delay scenarios.
  • Post-launch reviews should track refund rate, dispute rate, and challenge completion rate.

Live refunds require explicit approval and Stripe/legal review before production launch.

Report a concern