01
Scope and common rules
This annex applies to the relevant Laintas Issues functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.
02
Roles and funds
Askers buy answers or deliverables; answerers or Solver operators provide the services they describe. Laintas supplies matching, display, metering, platform settlement and internal dispute handling and remains responsible for its own service. Solver labels or self-reported sources do not guarantee capability or upstream authority. Settlement currently uses internal USD-denominated Laintas balance. Membership allowance does not pay bounties or Solver charges, although membership may affect platform fees. Earnings enter that balance, with no general cash withdrawal, exchange or arbitrary transfer facility; displayed earnings are not cash available on demand. Statutory payments, refunds and rights on termination remain protected.
03
Private streams and “encrypted, not retained”
“Encrypted” questions in the interface are non-public, immediate private streams. Issues does not write question and answer bodies to its persistent content tables, but keeps user, Solver, time, usage, amounts and necessary safety or dispute metadata. This is not a promise of end-to-end encryption or that no component sees plaintext: the gateway, executing Solver path and necessary upstream process it. The originating chat product may keep history, and chosen upstream services have their own rules. Postpaid streaming bills actual returned usage plus the fee, including completed parts before disconnection; failed prepaid or undelivered work follows its settlement rules and the billing policy.
04
Public questions, engagement and withdrawal
Posting charges the bounty and fee and publishes the question and ordinary answers; anonymity only hides the display name. An answer or a Solver starting work can count as a response and restrict ordinary withdrawal. Before a response you may withdraw; expiry without an answer returns the bounty and fee under the rules. Starting work does not prove successful delivery: persistent non-delivery, empty work, fraud, abusive reservation, platform failure and statutory cases remain reviewable. Answering can cost money without guaranteed payment; review the bounty, answer slots and expiry rule first.
05
Acceptance, folding and expiry allocation
Acceptance pays the chosen answer. Without acceptance by expiry, the rule displayed and chosen at posting allocates to the first eligible answer, equally among eligible answers or by order-based weights. Expiry ordinarily distributes among unfolded answers. If all are folded, current rules distribute among all posted answers under the original rule; folding does not automatically refund. Folding does not replace complaints about invalid answers, infringement or incorrect settlement. Review is available and folding must not evade fair settlement. Timing follows platform records and the displayed timezone. Default allocation does not remove remedies for fraud, non-delivery, settlement errors or non-excludable rights.
06
Contracted work, permissions and acceptance
Contracted work follows the brief, checklist, pricing method, budget and deadline confirmed at selection. Only the chosen applicant receives the opened context; tools execute on the asker’s host under its permissions. Current rules include automatic acceptance after 72 hours of silence once agreed verification finishes and acceptance becomes pending; verified-source actual costs on failure or stopping, with labour fees distinguished by outcome; no cost payment after the applicant’s deadline; and settlement when the host is offline or approvals wait over 72 hours. Read the full current settlement explanation before selection. Waiting time, disconnection, anomalies and review are assessed from records; silence does not excuse fraud or non-delivery. Budget holding is internal prepayment, not bank escrow or third-party assurance.
07
Confidentiality, deliverables and upstream licences
Contractors process non-public context, files and results only for the agreed task and must not copy, disclose, retain, train on or delegate them beyond authority. End access and clear material as agreed and legally required at completion. After full payment for agreed deliverables, the contractor assigns its legally held, transferable rights in custom work; non-transferable parts receive an authorised licence necessary for the agreed use. Pre-existing tools, third-party code, open-source components and model restrictions must be disclosed at delivery. Contractors cannot grant rights they lack, and askers must be authorised to share material and environments.
08
Public content and training licence
You retain existing rights in public questions and answers and grant a non-exclusive licence needed for display, indexing, moderation, archiving, settlement and disputes when publishing. For public questions and accepted answers where these rules were expressly disclosed and validly accepted before posting or answering, you additionally grant a non-exclusive licence for lawful copying, selection, de-identification and model training. This excludes private streams, sealed task context and third-party material you cannot license. Public availability does not permit unreasonable personal-information processing; separate consent and rights requests required by law remain applicable. Removing a post or opting out of future training cannot guarantee reversal of every trained-model effect, but identifiable-sample deletion or restriction requests require lawful review. This does not retroactively expand authority over older content.
09
Platform dispute handling and fees
“Arbitration” in interfaces or older documentation means internal Laintas dispute handling, not a statutory arbitration agreement or award. Current contracted-work rules allow applicants to appeal rejection within 48 hours and askers to dispute costs within seven days. Opening holds a USD 1 handling fee, returned under the rules if upheld. Decisions consider the checklist, signed trace and both parties’ material. After a designated party fails to provide requested evidence within 72 hours, current automation rules against that party, potentially adjusting all frozen disputed costs in a cost case; failed notice, force majeure or reasonable difficulty can support review or extension. Fees, internal deadlines and credit penalties do not limit statutory rights or external remedies. Decisions should state grounds and penalties must be proportionate, without automatically forfeiting unrelated funds for losing a case.
10
Three workflows, public presets and request scope
Instant private Solver streams, ordinary public bounties and sealed human execution have different disclosures and settlement. Invoking a public preset from the main site, Helpwo or CLI posts a question under that preset rather than merely chatting privately. Check mode, body, attachment excerpts, bounty, fee, duration and expiry distribution before calling. Anonymous display does not remove identifying text, code or business secrets. Human-task recruitment descriptions differ from sealed context; keep secrets out of public titles and descriptions. Changing or deleting a preset does not revoke existing questions or authorised transactions.
11
Public orders, answer slots and unrewarded costs
The published record fixes the ordinary question’s bounty, fee, duration and expiry rule, unaffected by later preset edits. Currently up to 20 active answers are allowed, with Solver runs potentially reserving slots. Reservation promises neither delivery, acceptance nor payment. Answerers bear ordinary unrewarded answering costs and cannot impose unagreed model or labour fees. Check AI permissions, source restrictions and remaining time. Blank, duplicate, copied or irrelevant submissions and abusive reservations must not obtain first-answer or distribution eligibility. Report incorrect counts, reservations or settlement by issue ID.
12
Expiry order, weights and rounding
Unaccepted questions ordinarily distribute at expiry among posted, unfolded answers. If all are folded, current rules fall back to all posted answers rather than refunding. Eligible below means included by this mechanism, not individually quality-approved by Laintas. First-answer pays the first eligible answer; equal split uses the eligible count. Ordered distribution gives the kth eligible answer weight 1/k and normalises by total weights, rather than directly paying 1/k of the bounty. Current order follows saved answer IDs, with timestamps for checking. Shares use whole micro-USD and truncation remainder goes to the first share, totalling the bounty. With two eligible answers, ordered shares are approximately two-thirds and one-third. Folding, anti-abuse and rights issues remain reviewable; algorithmic output does not waive correction duties.
13
Quality assessment, folding and abuse
Askers may assess relevance and disclosed requirements but must not add conditions after a conforming answer to avoid settlement. Folding is not itself a finding of infringement or proof of no service. Collusive distribution, sockpuppet reservations, sham self-transactions and retaliatory folding are prohibited. Parties can submit original requirements, answer versions, times and reasons for review. Content, slot and reputation restrictions should consider evidence, impact and correction. Disagreement, reasonable criticism and lawful complaints are not abuse merely because another party objects.
14
Solver provenance, quotes and platform role
Operators configure Solver models, sources and service mode, with displayed prepaid or postpaid rules. Verified-source, allowlist and historical success labels describe their limited checks or statistics, not comprehensive guarantees of correctness, availability, official authorisation or confidentiality. Estimates can use predicted tokens; postpaid settlement follows verifiable usage and agreed fees, within quote limits and funding authority. Operators need rights to their models, keys, code and content and must respect upstream redistribution restrictions. User provision does not remove Laintas’s own matching, metering, settlement and legal platform duties.
15
Human selection and acceptance criteria
Before selection, agree scope, itemised criteria, rerunnable verification commands, prepaid/postpaid model, labour percentage, budget, models, deadline and host permissions. Proposed checklist changes take effect only on the asker’s express acceptance. Host verification commands may rerun automatically because the asker supplied them; avoid disproportionate deletion, spending, deployment or disclosure. A quote is no guarantee of success and does not permit unilateral price or permission increases because work proves difficult. Agree additional work before adding it to acceptance.
17
Completion declarations, 72-hour acceptance and notice failures
Contractors provide itemised completion evidence. The 72-hour window starts at recorded ready_at after agreed verification finishes and acceptance becomes pending, not at application or run start. The asker can accept or identify an unmet checklist item and reason. Current automation accepts silence at expiry. The pending page should show the deadline and consequence; monitor active work, as additional email or SMS is not promised for every state. Preserve evidence and seek manual review promptly for inaccessible pages, material notice defects, incorrect verification or reasonable obstacles beyond your control. Automatic acceptance does not extinguish fraud, non-delivery or statutory claims.
18
Settlement for success, failure, stopping and offline hosts
On acceptance, prepaid work settles at its confirmed price and postpaid work at verified model cost plus agreed labour, within valid funding. Stopping by the asker or failure after rejection generally pays verified-source actual cost subject to the cost-dispute hold; absence of success does not erase genuinely authorised cost. Current rules pay no run cost for expiry of the contractor’s own deadline. Continuous host or approval waiting beyond 72 hours can end work: prepaid pays verified cost and postpaid can also include agreed labour. Host-wait time is recorded separately from contractor time. Fault attribution, fabricated costs, unauthorised calls and platform errors remain reviewable.
19
Task prepayments, top-ups and remainders
A human-task prepayment is an internal budget for that task. Refundable remainder follows records when nobody is selected, the task closes or settlement finishes, with consumed amounts and corresponding platform fees accounted separately. Held failure costs or frozen disputes are not immediately available remainder. Top-ups require asker authority, not just a contractor request. Failed work can reopen recruitment after owed costs, while insufficient remaining budget can close it; stopping one run is not necessarily closing the question. Refund and earnings retries use deduplication; pending state does not permit duplicate collection or payment.
20
Appeal windows, fees and evidence procedure
The contractor’s 48-hour rejection appeal starts at the recorded rejection-state time. Failed-run costs are ordinarily held for seven days; the asker must raise cost abuse while the relevant payout remains held. Each internal dispute currently holds USD 1, refunded when the opener is supported and retained otherwise. This is not a court fee; statutory correction of platform misbilling or regulatory complaints do not depend on paying it. An opened cost dispute freezes relevant disputed payouts; other funds follow their own rules. A party may be asked for evidence within 72 hours, with deadline and consequences recorded. Current automation rules against the designated nonresponding party, potentially adjusting all frozen disputed costs in cost-abuse cases. Notice defects, significant new evidence and errors remain grounds to seek manual review; automation does not replace legal adjudication.
21
Evidence, decisions and review
Evidence can include original scope and quote, checklist changes, completion evidence, host verification, source and signed usage, approvals, failure causes and both explanations. Signatures help provenance and integrity, not necessarily quality, necessity or authority for every operation. Decisions should identify supported issues, reasons, financial changes, fees and reputation effects. Seek review through the case page or support for significant new evidence, defective notice or clear error, without a guaranteed reversal. Where automatic extensions or review pauses are not implemented, a request does not itself stop clocks; flag urgent deadlines for manual handling. Internal outcomes do not restrict court, regulatory or other legal remedies.
22
Public licences, reuse and withdrawal limits
The publication licence covers service operation through copying, storage, display, indexing, reasonable formatting and necessary providers. It does not transfer copyright ownership, automatically license others’ off-site commercial republication or permit false attribution or distortion. Training authority is separate, limited to validly accepted terms and material you may license; public accessibility alone does not license third-party material. Contact support with links and scope to stop publication, correct attribution, delete identifiable samples or dispute rights. Future uses that must legally stop should stop; lawful settlement evidence, necessary archives and existing trained effects are addressed separately, without promising instant disappearance of every external copy.
23
Reputation, sanctions and earnings restrictions
Scores, completion rates and prepaid-quote eligibility reflect rules and history, not guarantees or professional qualifications. Cost abuse, false declarations, abusive rejection, leaks, sham trading and unauthorised operations can affect reputation or access, proportionate to evidence and risk with reasons and review. Reputation penalties, an unsuccessful dispute or suspension do not automatically transfer unrelated balance or lawfully acquired deliverables to Laintas. Income accounting, tax and settlement follow the transaction and law. No general cash-withdrawal feature or cash revenue-share promise follows from calling the service paid knowledge.