Alpha informational notice

Terms & Privacy

A plain-language summary of how Bounty HTR works today, how we protect your information, and what future agreements will cover.

No agreement checkbox is required during alpha. This notice is informational and is not the final binding user or payment agreement. Before real-money features require binding terms, we will present them separately for review and explicit acceptance.

Last updated August 20, 2026

Alpha status and purpose

Bounty HTR is currently an alpha product and is expected to move into beta. Features, availability, rules, and timelines may change as the platform is tested. We will be candid about limitations, including bounty liquidity, completion times, and any feature that is simulated, limited, or unavailable.

This page records current practices and planned safeguards. It does not replace a bounty's own written terms, a payment provider's terms, or a future agreement that requires your explicit acceptance.

Accounts and acceptable conduct

Provide accurate account information, protect your credentials, and use Bounty HTR only for lawful work. Do not impersonate others, interfere with the service, evade access controls, manipulate invite rankings, or use the platform to exploit, deceive, harass, or harm another person.

The current authentication system allows one Bounty HTR user account per unique email address. Sign-in identities that use the same verified email may be linked to that one account. A phone number is optional at signup and is not displayed on your public profile.

We may restrict or suspend access when reasonably necessary to protect users, investigate abuse, comply with law, or preserve the integrity of bounties, records, and payments. Final suspension and appeal rules will be included in binding terms before production launch.

Bounties, submissions, and creative rights

Sponsors are responsible for describing the requested work, reward, deadlines, milestones, acceptance criteria, allowed tools, and required evidence clearly. Creators are responsible for submitting work they have the right to provide and for following the agreed brief.

Ownership, licenses, confidentiality, human-only requirements, revisions, and acceptance should be stated in each bounty. Unless a bounty or later binding agreement says otherwise, posting or submitting content does not automatically transfer ownership. Low-effort automated output may be rejected when a bounty requires genuine human creative work or a documented process.

Moderation and dispute tools support evidence-based review, but alpha outcomes may still require manual handling. We do not promise that every bounty will receive submissions or be completed.

Money, ledgers, refunds, and privacy

During alpha, money features may be disabled, limited, or run in test mode. Before real-money transactions are enabled, applicable fees, payout rules, refund rights, dispute procedures, identity checks, provider terms, and required legal agreements will be shown clearly.

When money moves, Bounty HTR's authoritative records will use an auditable ledger. Entries will be tracked and immutable: a completed financial record will not be silently rewritten, and corrections will use explicit compensating entries. Transaction details will remain private except when access is needed by the parties to a transaction, authorized operators and service providers, or law and safety processes.

Sponsor refunds and creator payout eligibility will follow the bounty state, documented milestones, payment-provider results, and applicable law. No browser display alone is proof that funds moved.

Privacy: what we collect and why

We collect only information reasonably needed to operate and secure Bounty HTR. This may include your email address, display name, handle, optional phone number, profile content, bounty and submission activity, invite attribution, support messages, security events, device and connection data, and transaction records when payment features are active.

We use this information to provide accounts and marketplace features, prevent fraud and abuse, keep records accurate, operate the invite leaderboard, deliver requested communications, support users, improve reliability, and meet legal obligations.

We will never sell your personal data. We may share limited information with vendors that process it for us, payment and identity providers you choose to use, transaction counterparties when necessary to complete a bounty, or authorities when legally required or needed to protect rights and safety. Vendors may use the information only for the service they provide to Bounty HTR under appropriate restrictions.

Your privacy choices

Bounty HTR does not currently use personalized advertising. If personalized ads are introduced, they will be off by default and available only through a clear, separate opt-in. You will be able to decline without losing ordinary marketplace access and withdraw that choice later.

You can manage available profile visibility and communication settings in your account. You may also ask for access to, correction of, or deletion of eligible personal information. Some security, dispute, tax, transaction, and immutable ledger records may need to be retained for legitimate operational or legal reasons; where a record cannot be erased, access will remain limited.

We use reasonable administrative, technical, and organizational safeguards, but no online system can promise absolute security. Please report suspected account compromise or privacy issues promptly through the Help page.

Changes, questions, and future agreements

We may update this notice as the alpha changes. The current version and update date will remain on this page. Material privacy changes or new binding obligations will receive a clearer notice than a silent page edit.

Before Bounty HTR asks you to enter a binding production agreement, the final terms will identify the responsible legal entity, eligibility rules, governing law, dispute process, payment obligations, and effective date. You will have an opportunity to review those terms before deciding whether to accept.

Questions or privacy requests can be started through FAQ / Help. Do not include passwords, payment credentials, or other secrets in a support message.