Developer Terms

These Developer Terms apply to anyone who builds apps on Queek or uses the Queek APIs. By selecting "I agree" when you become a developer, or by using the Queek APIs, you agree to these terms, to the Queek Terms & conditions and to the Queek Privacy Policy. If you use Queek on behalf of a company, you agree for that company.

"Queek" means Queekx Technology Limited.

"Queek APIs" means the Merchant API, the Headless API, webhooks, app extensions and the tools and SDKs Queek publishes for them.

"App" means software you register with Queek that merchants can install.

"Merchant" means a business that uses Queek and installs or authorises your App.

"Credentials" means API keys, access tokens, app signing secrets and private keys issued for your account or your Apps.

"Merchant Data" means any information you receive through the Queek APIs about a Merchant, its store or its customers, including names, email addresses, phone numbers, delivery addresses and order details.

You must be at least 18 years old and give accurate information. Apps you register belong to your developer account, not to any single store, and can be installed by any Merchant once they are available to them.

You are responsible for everything done with your account and your Credentials.

Use the Queek APIs only as documented and only to provide your App's service to Merchants.

Request only the access your App needs.

Do not circumvent rate limits or other controls (for example by rotating Credentials to avoid a quota), reverse engineer Queek to bypass its protections, scrape Queek outside the documented APIs, or use Queek for unlawful, infringing or misleading content.

Credentials are confidential. Do not share or sell them, and never place a secret key or private key in client-side code or a public repository. Signing secrets and private keys are shown once — store them securely.

Verify the signature on every webhook and request Queek sends to your App, and keep your App and its endpoints secure.

Queek may revoke any Credential that is exposed publicly or appears compromised.

Merchant Data belongs to the Merchant. For Merchant Data you receive, the Merchant is the controller and you act as the Merchant's processor: use it only to provide your App's service to that Merchant, and do not sell it or share it with anyone else.

Handle Merchant Data in line with the Nigeria Data Protection Act 2023 and any other law that applies to you, including any rules on transferring data outside Nigeria.

Stop using Merchant Data and delete it when the Merchant uninstalls your App or asks you to, unless the law requires you to keep it.

Protect Merchant Data: encrypt it at rest and in transit, and limit staff access to what they need to do their job.

Keep an incident-response process. If Merchant Data is lost, accessed or disclosed without authorisation, tell the affected Merchants and Queek without undue delay.

An App's first public listing is reviewed by Queek before Merchants can install it. Later versions release when you deploy them, unless they add access that needs review — such as customer data, checkout requirements or payments — in which case that version is reviewed first.

You submit a version for review when it is ready. Queek checks it automatically and a reviewer tests it on a store. A version in review cannot be changed; withdraw it to make changes.

When a version asks for access to customer, payment or checkout data, you confirm at submission that your App meets the duties in section 6. Queek may ask for evidence and may remove an App that does not meet them.

Apps in development can be installed only on dev stores you own.

The Queek APIs are versioned by path (for example /v1). Within a version, Queek only adds fields and endpoints; it does not remove, rename or repurpose them. A breaking change ships as a new version, and the older version stays available for at least 6 months after deprecation is announced in the changelog and response headers.

Rate limits may change. Queek announces a reduction in the changelog at least 14 days before it takes effect.

Queek reports availability on its public status page and makes no other uptime commitment. Webhooks are delivered at least once and may repeat — use the event id to ignore duplicates.

Queek may revoke Credentials, disable webhook endpoints, remove an App from listings or suspend API access if you breach these terms, abuse the Queek APIs or put Merchants or their customers at risk. Queek gives notice in the dashboard where it can, and acts without notice where delay would put Merchant Data at risk.

You may stop at any time by deleting your Apps. Sections 5, 6, 11 and 12 continue to apply after you stop.

You are responsible for every action your App takes through the Queek APIs, whether or not a person started it, including any document it creates, issues, changes, voids or credits in a Merchant's name, such as an invoice, a credit note or a payment record. Make sure your App takes such an action only when the Merchant has asked for it or set your App up to do it.

To the extent the law allows, you will indemnify Queek against claims by a Merchant, a Merchant's customer or a tax authority, and against the resulting losses and reasonable costs, including reasonable legal fees, to the extent they arise from: your App's breach of these terms or of the law; an action your App took through the Queek APIs that the Merchant did not authorise or that was wrong because of your App's design, data or error; or your App's handling of Merchant Data. This does not apply to the extent a claim arises from Queek's breach of these terms, its negligence or wilful misconduct, or a fault in the Queek APIs.

Queek will tell you promptly about a claim it asks you to cover, let you take part in or lead its defence with counsel reasonably acceptable to Queek, and give reasonable help at your cost. Neither of us will settle such a claim in a way that admits fault for the other or requires the other to pay, without the other's written consent, which will not be unreasonably withheld.

Queek records which App or API key issued, voided or credited an invoice, or recorded or voided a payment, and may show that record to the Merchant concerned or produce it where the law requires.

Sections 10 (Disclaimer of Warranties), 11 (Limitation of Liability) and 12 (Governing Law and Dispute Resolution) of the Queek Terms & conditions apply to the Queek APIs and to these terms.

Queek may update these terms. The date at the top of this page shows the latest version. When a change affects developers materially, Queek will ask you to accept the new version in the dashboard before you continue building.