Bounty Submission Terms
These terms apply when you use Askuno to pursue, claim, complete, or submit evidence for bounty work during the controlled beta. They supplement the Terms of Service and Privacy Policy.
Each bounty program controls its own rules.
Third-party bounty programs decide eligibility, scope, acceptable submissions, review timing, payment timing, payment amount, and final approval. You must follow the program rules, repository rules, platform rules, licenses, and maintainer instructions that apply to the work.
Askuno may help prepare or route submissions, but Askuno does not guarantee that a third party will accept, merge, approve, or pay for your work.
Payment depends on outside approval and payment.
External bounty payouts depend on the third-party program approving the work and paying the relevant recipient. Askuno may also require internal review, receipt confirmation, compliance checks, identity or contact checks, and owner approval before any user payout routing is considered.
No payout amount, timing, method, tax treatment, exchange rate, availability, or eligibility is promised by these beta terms.
Askuno can accept, reject, or defer evidence.
Askuno review discretion includes checking whether evidence is complete, relevant, safe, authorized, non-abusive, reproducible, and aligned with the third-party bounty rules. Review may be manual, delayed, or unavailable during the beta.
Askuno may reject duplicate work, stale work, unclear claims, unsafe code, work that appears generated without understanding, submissions that spam maintainers, or evidence that would expose secrets or violate another party's rules.
Submit only evidence you can share.
Evidence can include branch names, patch text, pull request links, private artifact links, test output summaries, reproduction notes, screenshots, and access notes. You are responsible for making evidence accurate, reviewable, and authorized.
Do not submit passwords, API keys, private keys, seed phrases, personal secrets, unreleased customer data, vulnerability details outside an authorized disclosure path, or private repository material you do not have permission to share.
Askuno-managed submission remains gated.
Askuno may prepare a managed pull request, bounty claim, status update, or outcome packet from your submitted evidence. Live GitHub writes, third-party bounty submissions, payment recording, banking, Wise, or credit-authority changes require explicit owner authority and the relevant operational gate.
You retain responsibility for the truthfulness, authorization, and safety of the evidence you submit.
Unsafe bounty behavior can stop access.
Askuno may suspend or close access, revoke tokens, withhold review, cancel a claim, or decline payout routing when work appears illegal, abusive, spammy, deceptive, unsafe, unauthorized, secret-bearing, or inconsistent with third-party program rules.
Service limits, bounty availability, claim reservations, and compute-credit caps can change during the beta.
Contact channel
For bounty support or review questions, email george@atumera.com.