Terms of Service

WEB3 FZCO
DSO-IFZA, Dubai Silicon Oasis, United Arab Emirates
Licence 13052 · Dubai Integrated Economic Zones Authority (DIEZA)

العربية

Agreement and scope

These Terms of Service (the "Terms") govern access to GetAppBuilt, including its website, APIs, GitHub App, command-line tools, bounty records, review workflows, and configured smart-contract interfaces (together, the "Service"). In these Terms, "GetAppBuilt," "we," and "us" mean WEB3 FZCO, the legal operator of the Service.

By creating an account, connecting GitHub or a wallet, funding or claiming work, submitting evidence, or otherwise using the Service, you agree to these Terms and the Privacy Policy. If you use the Service for an organization, you represent that you may bind it. If you do not agree, do not use the Service.

The Service coordinates software work and records evidence. It does not replace the authority of a repository owner or maintainer, and it does not promise that a submission will be merged, deployed, published, or accepted by any third party.

Eligibility and accounts

You must be at least 18 years old, legally able to enter a binding contract, and permitted to use the Service under the laws that apply to you. You may not use the Service if you are subject to applicable sanctions or are located in a jurisdiction the Service or a payment provider does not support.

The initial fiat pilot is business-to-business only. Sponsors must act for a registered or licensed business. Initial payees must be a UAE company or UAE-licensed freelancer and complete payment-provider onboarding before payout.

Provide accurate information and keep your account, email, GitHub identity, wallet, and authentication methods secure. You are responsible for activity performed through your account unless you promptly report unauthorized access. Do not share access tokens, private keys, magic links, or operator credentials.

Email-only accounts may request or fund work. GitHub identity and repository authorization are required for GitHub-native actions such as private-repository access, maintainer checks, claiming developer work, and submitting implementation evidence.

Requests, backing, and bounties

A request describes a desired outcome before claimable work exists. Backing interest indicates demand but is not locked funding. A bounty is scoped, funded, and claimable work governed by a specific version of its acceptance criteria, non-goals, checks, payout, claim policy, and dispute standard (the "Locked Terms").

Do not begin work based only on a request or expression of backing interest. When a bounty is funded, later edits do not replace its Locked Terms unless the authorized parties and applicable contract flow permit the change. Funding does not grant a sponsor authority to merge code, approve payout alone, publish a deliverable, control another funder's contribution, or override a maintainer.

Repository owners and maintainers retain their normal GitHub authority. They may review, reject, or decline to merge a submission under their repository rules even if GetAppBuilt separately records that the Locked Terms were satisfied.

Funding, fees, payouts, and refunds

The funding screen and Locked Terms control the worker payout, sponsor-side platform fee, review budget, maintainer fee, stake, reserves, tax, and other charges for a bounty. Fiat prices shown as worker amounts are VAT-exclusive B2B prices. The checkout shows a maximum authorization covering the worker amount, the separate platform fee, possible VAT on each supply, and payment-provider fees. The exact captured amount may be lower. Existing funded bounties keep the fee and refund rules recorded in their Locked Terms, and the advertised worker amount is not reduced by the platform fee.

Funding may use supported assets on Ethereum Sepolia or, when enabled, a hosted payment-provider flow. Crypto funding and payout depend on wallet signatures, network confirmation, supported token contracts, and smart-contract state. Gas, wallet, exchange, banking, tax, payment-provider, and currency-conversion costs may be separate. GetAppBuilt does not collect raw card numbers; hosted providers handle card and payout-account details under their own terms.

The first public money launch uses hosted fiat checkout. Native USDC on Arbitrum One is a separate future rail shown as Coming soon. Each bounty uses one immutable funding rail after its first confirmed contribution; fiat and crypto funding, payout, refunds, and accounting are not mixed within one bounty.

Before a worker is identified, a fiat funding instruction is a conditional card authorization or offer, not payment for a worker service. Immediately before capture and before work starts, GetAppBuilt creates a separate Work Order for every sponsor, records an immutable allocation certificate, calculates the actual tax and fee components, captures only that amount, and releases unused authorization. Payment capture, invoice issue, service completion, and work acceptance can create different legal or tax dates.

Every sponsor-level Work Order is a separate concurrent supply. Each sponsor is a co-customer and legal recipient with enforceable rights to the allocated performance, delivery, evidence, review, applicable use or licence, correction, refund, and dispute process. Sponsor obligations are separate and several: no sponsor is jointly liable, jointly and severally liable, or responsible for another sponsor's shortfall. Allocations use the published proportional formula and deterministic whole-cent rounding and are never rewritten to shift a later shortfall to another sponsor.

The worker is the supplier and primary obligor for the worker service. The worker appoints WEB3 FZCO as disclosed agent, acting in the worker's name and for the worker's account, only to conclude Work Orders, collect and administer worker consideration, transmit project communications, administer the agreed acceptance and dispute process, and issue or transmit worker invoices and credit notes where legally permitted. The worker remains responsible for performance, warranties, intellectual-property provenance, and its own VAT and tax obligations. A worker invoice uses the worker's identity, TRN where applicable, and invoice sequence; WEB3's TRN is never substituted.

WEB3 FZCO is principal only for its separately defined platform and review-administration service and issues a separate platform invoice to every sponsor. Worker net consideration, worker VAT, platform net consideration, platform VAT, payment-provider fees, total collected, and the worker payable remain separate records. Receipt by WEB3 is credited only to the applicable Work Order. Whether and when it discharges the sponsor's worker-service payment obligation is the rule frozen in that Work Order; a card authorization alone never does.

A chargeback is payment evidence, not by itself a cancellation or reduction of the underlying price. A genuine post-tax-point price reduction, cancellation, return, or correction requires the affected legal supplier's sponsor-specific credit note. It does not alter any other sponsor's Work Order or invoice. Platform-fee earning and refund treatment follow the rule frozen in the applicable Locked Terms.

Funds become payable or refundable only under the Locked Terms, verified funding state, applicable timelocks, review and dispute outcomes, and provider or network confirmation. Chargebacks, sanctions holds, chain reorganizations, token-contract behavior, and payment-provider restrictions can delay or reverse a displayed status. You are responsible for your taxes and for providing any information lawfully required for payment or reporting.

GetAppBuilt is not a bank, deposit account, wallet, exchange, broker, investment adviser, escrow service, or tax adviser. Nothing on the Service is legal, financial, investment, or tax advice.

Submissions, licenses, and repository rights

Workers may submit pull requests, fork branches, patches, source or artifact links, test output, and other delivery evidence ("Submissions"). You represent that you have the rights needed to provide your Submission and that it does not unlawfully include another person's code, confidential information, personal data, secrets, malware, or restricted material.

You retain ownership of content you create. You grant GetAppBuilt a worldwide, non-exclusive, royalty-free license to host, copy, transmit, reproduce, analyze, and display that content only as needed to operate, secure, review, audit, and improve the Service and to resolve the relevant bounty or dispute. This license continues for retained audit evidence and backups after account closure.

The license delivered to a sponsor, maintainer, or repository is determined by the Locked Terms, the repository license, and the applicable Submission or pull-request terms. Payment by itself does not silently transfer copyright, patent rights, trademark rights, or repository ownership. Parties should put any assignment or special license in the Locked Terms before funding.

Feedback about GetAppBuilt may be used without restriction or compensation, but this does not transfer ownership of your Submissions or confidential repository content.

Review, decisions, and disputes

GetAppBuilt currently uses an operator-run review process. Reviewers compare a Submission with the Locked Terms and record evidence, checks, and a verdict. Review fees compensate verification work and are separate from the worker payout. Similarity, safety, quality, fraud, and AI-assisted signals are advisory unless a disclosed rule requires a hold; they do not silently approve or deny payment.

A product dispute asks whether the Submission satisfied the Locked Terms. The operator may request more evidence, preserve funds, apply a partial-credit or regression rule already in the Locked Terms, or record a payout or refund decision. A valid dispute fee is refundable as specified in the relevant bounty record.

A GetAppBuilt product determination is not a court judgment or a substitute for rights that cannot lawfully be waived. A repository merge decision, GitHub issue state, payment-provider chargeback, onchain transaction, and GetAppBuilt payout decision are separate events and may not occur together.

Acceptable use and safety

You may not use the Service to request, fund, perform, or distribute:

  • malware, ransomware, credential theft, backdoors, miners, or hidden telemetry;
  • unauthorized exploitation, access-control bypass, or private-data exfiltration;
  • abusive scraping, spam, harassment, fraud, impersonation, or deceptive activity;
  • content that infringes intellectual-property, privacy, confidentiality, or other rights;
  • activity that violates sanctions, export controls, payment-provider rules, or applicable law; or
  • attempts to evade security controls, manipulate reviews or reputation, create related accounts for abuse, or interfere with the Service.

Security work is allowed only when the repository owner has given explicit authorization and the bounty states a clear safe-harbor scope. Card funding for security bounties may remain unavailable until operator and provider controls approve it.

We may reject or hold a request, restrict access, preserve evidence, suspend an account, or report conduct when reasonably necessary to protect users, third parties, the Service, or comply with law. Where appropriate, users may appeal through the contact method published with the final operator details.

Third-party and blockchain services

The Service interoperates with third parties such as GitHub, wallet software, blockchain networks, RPC and storage providers, payment providers, and email services. Their terms and privacy notices apply to their services. GetAppBuilt does not control their availability, security, fees, policies, forks, outages, or decisions.

Public blockchains are transparent and generally immutable. Wallet addresses, token transfers, transaction hashes, and contract events can remain public even if GetAppBuilt deletes an offchain account. Transactions sent to the wrong address, network, token contract, or smart contract may be irreversible. Review transaction details in your wallet before signing.

Links and GitHub references do not mean GetAppBuilt endorses the linked repository, code, person, product, or content.

Service changes, suspension, and termination

We may change, restrict, or discontinue features, supported networks, assets, providers, or eligibility rules. We will not intentionally rewrite the recorded Locked Terms of an already funded bounty through a general Terms update. Urgent security, legal, provider, or network conditions may require immediate holds or suspension.

You may stop using the Service at any time and may request account closure through the contact method published in the Privacy Policy. Closure does not cancel existing obligations or erase public blockchain data, GitHub data, another party's records, or evidence we must retain for security, accounting, disputes, or legal compliance.

Provisions that by their nature should survive termination do so, including payment obligations, licenses needed for retained records, warranty disclaimers, liability limits, dispute terms, and governing law.

Disclaimers and liability

To the fullest extent permitted by law, the Service is provided "as is" and "as available." GetAppBuilt disclaims implied warranties of merchantability, fitness for a particular purpose, non-infringement, title, and uninterrupted or error-free operation. We do not warrant the quality, legality, security, originality, or fitness of a request, repository, sponsor, worker, reviewer, Submission, token, smart contract, or third-party service.

To the fullest extent permitted by law, GetAppBuilt and its affiliates, personnel, and suppliers are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, goodwill, opportunity, or digital assets. Aggregate liability arising from the Service will not exceed the fees you paid directly to GetAppBuilt for the Service giving rise to the claim during the 12 months before the event.

These exclusions do not apply where prohibited by law or to liability that cannot lawfully be limited, including liability arising from fraud or wilful misconduct. Nothing in these Terms excludes mandatory consumer rights or remedies.

You will indemnify GetAppBuilt and its affiliates and personnel from third-party claims, losses, and reasonable costs arising from your unlawful use of the Service, your Submission, your breach of these Terms, or your violation of another person's rights, except to the extent caused by GetAppBuilt' own breach or misconduct.

Governing law, changes, and contact

These Terms are governed by the laws of the United Arab Emirates, without regard to conflict-of-law rules. Subject to any mandatory consumer forum or other non-waivable right, the competent courts of the United Arab Emirates have exclusive jurisdiction over legal disputes arising from these Terms or the Service.

We may update these Terms to reflect product, legal, security, or provider changes. We will post the new date and, when a change is material, provide reasonable notice through the Service. Continued use after the effective date of updated Terms constitutes acceptance where permitted by law.

Questions or legal notices about these Terms may be directed to WEB3 FZCO at support@web3.consulting.