whizzQ Branded / White-Label Application Addendum
Effective Date: September 15, 2026 Version: 2.0 Last Updated: September 15, 2026 This Branded / White-Label Application Addendum ("Addendum") forms part of the agreement between SCHEDMAD Private Limited, operator of the whizzQ platform ("SCHEDMAD", "whizzQ", "we", "us" or "our"), and the Merchant, business, organisation, brand owner or other commercial customer identified in the applicable Branded App Order Form ("Merchant", "Brand Owner", "you" or "your"). This Addendum applies where SCHEDMAD provides a Merchant-branded or white-label mobile application, web application or related branded consumer interface powered by the whizzQ platform (the "Branded Application"). This Addendum supplements the whizzQ Business & Merchant Terms, the applicable Branded App Order Form, whizzQ Privacy Notice, Data Processing Addendum and other incorporated policies. The Merchant's standard Merchant Onboarding & Order Form continues to govern the underlying whizzQ Merchant relationship.
1. Definitions
"App Store" means the Apple App Store, Google Play or another authorised application distribution platform through which a Branded Application may be published. "Brand Assets" means the Merchant's or Brand Owner's trademarks, logos, trade names, artwork, colour schemes, text, screenshots, icons, promotional materials and other brand elements supplied for use in the Branded Application. "Branded Application" means the Merchant-branded or white-label front-end application or interface configured by SCHEDMAD and powered by the whizzQ Platform. "Developer Account" means an Apple Developer Program, Google Play Console or other app-distribution account used to submit, publish, manage or distribute the Branded Application. "Merchant Developer Account" means a Developer Account legally owned or controlled by the Merchant or Brand Owner. "SCHEDMAD Developer Account" means a Developer Account legally owned or controlled by SCHEDMAD or whizzQ. "Platform" means the whizzQ backend, software, APIs, databases, scheduling engines, workflows, reusable components, infrastructure and related technology operated by SCHEDMAD. "Store Policies" means the current rules, agreements, review standards, technical requirements and policies of the relevant App Store or platform operator. "Store Materials" means app name, description, screenshots, icons, privacy disclosures, support URLs, keywords, age ratings, category selections and other information submitted to an App Store.
2. Nature of the Branded Application
The Branded Application is a configured branded front-end operating on or through the whizzQ Platform unless an Order Form expressly states otherwise. Provision of a Branded Application does not transfer ownership of the whizzQ Platform, source code, backend, APIs, databases, architecture, reusable components, algorithms or other SCHEDMAD technology to the Merchant. The Branded Application may present the Merchant's branding and consumer experience while relying upon whizzQ for functionality such as account services, scheduling, booking, queue management, communications, marketplace-related functionality, payments, analytics and other enabled services. The precise enabled functionality will be determined by the applicable Branded App Order Form, plan and technical configuration.
3. Preferred Publishing Model - Merchant / Brand-Owned Developer Account
The preferred and standard publishing model for a Branded Application is publication through a Developer Account legally owned or controlled by the Merchant or relevant Brand Owner. The Merchant is responsible for establishing, verifying, maintaining and renewing its Developer Account and for satisfying the relevant App Store requirements applicable to account ownership, legal entity verification, tax information, payment profile, authorised personnel and other account-level requirements. Where required, the Merchant must ensure that the individual acting as account owner, account holder or equivalent has authority to bind the Merchant or Brand Owner to the relevant App Store agreements. The Merchant must provide SCHEDMAD with the access reasonably required to configure, submit, update, maintain and support the Branded Application, using the roles and permissions available within the relevant Developer Account. Where technically possible, SCHEDMAD should be granted only the level of access reasonably necessary to perform the agreed services.
4. Optional Publishing Through a SCHEDMAD Developer Account
Where expressly agreed in the applicable Branded App Order Form, SCHEDMAD may publish the Branded Application through a SCHEDMAD Developer Account. Publication through a SCHEDMAD Developer Account is an operational arrangement and does not transfer ownership of the Merchant's Brand Assets to SCHEDMAD. The Merchant acknowledges that SCHEDMAD must protect the standing, security and compliance of its Developer Account, including other applications distributed through that account. Accordingly, SCHEDMAD may impose additional technical, content, privacy, security or operational requirements where reasonably necessary to protect its Developer Account, other applications, users or regulatory position. Where a SCHEDMAD Developer Account is used, the applicable Branded App Order Form may include additional publication, maintenance, account-risk or migration charges.
5. App Store Account Ownership and Control
The legal owner of a Developer Account retains primary control over that Developer Account subject to the App Store's own rules. Nothing in this Addendum requires either party to sell, lease, lend, transfer or assign a Developer Account in a manner prohibited by the relevant App Store. Any transfer of an Account Holder role, app ownership, developer account ownership or similar control must follow the formal process supported by the relevant App Store and is subject to that App Store's eligibility, verification and approval requirements. SCHEDMAD does not guarantee that Apple, Google or another platform operator will approve any requested account or app transfer.
6. Merchant Developer Account Responsibilities
Where the Merchant Developer Account model applies, the Merchant is responsible for: maintaining an active Developer Account; paying App Store membership or account fees; maintaining verified legal entity and contact information; keeping account credentials secure; maintaining payment or tax profiles where required; complying with Store Policies; and ensuring continuity of account ownership and authorised personnel. The Merchant must not revoke SCHEDMAD's required technical access while active maintenance services depend on that access, except for legitimate security or contractual reasons. If access is revoked or the Developer Account becomes suspended, expired, unverified or otherwise unavailable, SCHEDMAD is not responsible for resulting publication delays or application unavailability to the extent caused by that account condition.
7. SCHEDMAD Access to Merchant Developer Accounts
The Merchant authorises SCHEDMAD personnel designated for the project to access the Merchant Developer Account using App Store-supported team roles or permissions for the agreed services. SCHEDMAD will not intentionally use such access for unrelated applications or purposes. SCHEDMAD will take reasonable measures to protect credentials and access tokens under its control and will revoke or return access when no longer reasonably required. The Merchant remains responsible for maintaining the master account, primary legal ownership and other account-level controls that cannot or should not be delegated.
8. App Submission and Review
SCHEDMAD may prepare and submit the Branded Application to the relevant App Store where included in the agreed scope. App Store review is controlled by the relevant platform operator and is not controlled by SCHEDMAD. SCHEDMAD does not guarantee approval, publication date, review duration, search ranking, feature placement, category placement or continued availability. If an App Store requests changes, SCHEDMAD and the Merchant will cooperate to implement reasonable modifications within the agreed scope. Material rework, new functionality or compliance remediation outside the agreed scope may be separately chargeable.
9. Store Materials and Accuracy
The Merchant is responsible for the accuracy and legality of Merchant-specific information contained in Store Materials, including business claims, pricing claims, service descriptions, regulated-service statements, promotional statements and Brand Assets. SCHEDMAD may prepare Store Materials based on information supplied by the Merchant and may require the Merchant to review and approve them before submission. SCHEDMAD may refuse to submit Store Materials that it reasonably believes are unlawful, misleading, infringing or likely to create material App Store account risk. Privacy and data-safety disclosures must accurately reflect the actual data collection and processing of the relevant Branded Application.
10. Brand Assets and Trademark Licence
The Merchant retains ownership of its Brand Assets and associated intellectual-property rights. The Merchant grants SCHEDMAD a non-exclusive, worldwide, royalty-free licence for the duration of the relationship to use, reproduce, resize, format, adapt for technical presentation, display and submit the Brand Assets as reasonably necessary to design, publish, operate, support and promote the Branded Application. The Merchant warrants that it has all rights and permissions required to provide the Brand Assets and authorise their use. SCHEDMAD may remove or suspend Brand Assets where reasonably necessary to address an infringement claim, legal requirement or App Store enforcement risk.
11. SCHEDMAD Intellectual Property
SCHEDMAD retains all right, title and interest in and to the whizzQ Platform and all SCHEDMAD technology used to create, operate or support the Branded Application. This includes source code, object code, APIs, databases, schemas, backend services, reusable libraries, templates, workflows, algorithms, scheduling logic, queue logic, payment integrations, analytics, AI-enabled functions, development tools, documentation and improvements. Unless an Order Form expressly states otherwise, fees paid for a Branded Application are for configuration, branding, publication and access to the whizzQ-powered service and do not purchase source code or underlying Platform ownership. No implied licence to reverse engineer, copy, resell, sublicense or create derivative competing technology is granted beyond rights that cannot lawfully be restricted.
12. Customisations and Enhancements
Customisations developed specifically for a Merchant may include Merchant-specific configuration, design assets, workflows or integration work. Unless expressly agreed otherwise in writing, reusable code, generic features, frameworks, APIs, components, improvements and know-how developed while performing such customisation remain SCHEDMAD intellectual property. Merchant-owned Brand Assets and Merchant-provided content remain Merchant property. Any ownership transfer of a specifically commissioned deliverable must be expressly identified in the applicable Branded App Order Form.
13. Data Protection Roles
A Merchant-branded interface does not by itself make the Merchant the sole Data Fiduciary or give the Merchant exclusive rights over all Personal Data processed through the Branded Application. SCHEDMAD and the Merchant may each act as independent Data Fiduciaries for different processing purposes, and SCHEDMAD may also act as a Data Processor for specific Merchant-instructed processing as described in the whizzQ Data Processing Addendum. For example, the Merchant may independently process information for service fulfilment, while SCHEDMAD may independently process information for Platform account administration, security, fraud prevention, payment administration, legal compliance and other disclosed whizzQ purposes. The applicable whizzQ Privacy Notice, Merchant privacy disclosures and Data Processing Addendum govern the relevant processing roles.
14. Privacy Notice and App Store Privacy Disclosures
The Branded Application must display or make accessible appropriate privacy information for the actual data processing performed through the application. Where required, the Merchant must provide Merchant-specific privacy disclosures covering its independent processing. SCHEDMAD may provide or link to the whizzQ Privacy Notice for SCHEDMAD processing. The parties will cooperate to ensure Apple privacy labels, Google Play Data safety disclosures and similar App Store submissions reasonably reflect the actual implemented processing. Neither party should knowingly submit a privacy declaration that materially understates or misstates the application's actual data collection or sharing.
15. Merchant Customer Data
The Merchant does not acquire unrestricted rights over the wider whizzQ Marketplace Consumer database merely because a Consumer uses the Branded Application or books the Merchant. Merchant-Originated Customer Information remains subject to the role allocation set out in the Business & Merchant Terms and Data Processing Addendum. Marketplace-originated Consumer information may be available to the Merchant only to the extent reasonably necessary for service fulfilment, communication, lawful record-keeping and other authorised purposes. Bulk export may remain subject to whizzQ support-mediated entitlement, privacy and security review.
16. Consumer Accounts and Authentication
The Branded Application may use whizzQ account, authentication, OTP, login or identity-management functionality unless the Branded App Order Form specifies a different architecture. The existence of Merchant branding does not necessarily create a separate standalone consumer identity system owned exclusively by the Merchant. Where authentication depends on third-party services, SMS, email, Apple, Google or other identity providers, their availability and policies may affect functionality.
17. Payments and Marketplace Transactions
Where online payments are enabled, payment processing may use the same whizzQ payment architecture applicable to the Merchant, including Razorpay and Razorpay Route linked-account functionality where supported. Publication through a Merchant Developer Account does not by itself alter the payment, settlement, Platform Fee, cancellation or refund rules applicable under the Business & Merchant Terms and Booking, Cancellation, Refund & Payment Policy. App Store in-app-purchase requirements, if applicable to any future digital content or digital-service feature, may require separate technical and commercial treatment.
18. Communications and Notifications
The Branded Application may send push, SMS, WhatsApp, email or in-app communications through whizzQ or integrated providers where enabled. Transactional and service communications must be distinguished from promotional communications in accordance with applicable law and provider rules. The Merchant remains responsible for its independent promotional communications and any consent or registration requirements applicable to those communications.
19. Merchant Content and Regulated Services
The Merchant is responsible for content, claims, services and regulated activities presented through the Branded Application. The Merchant must maintain all licences, registrations, professional permissions and legal authority required to offer its underlying services. SCHEDMAD may require modification or removal of content that creates material legal, safety, App Store or developer-account risk. For healthcare or other regulated categories, general booking fields should not be used for clinical records or other restricted information unless SCHEDMAD expressly provides a feature designed for that purpose.
20. App Store Compliance
Each party must reasonably cooperate to satisfy applicable Store Policies relevant to its responsibilities. The Merchant is responsible for Merchant-specific business, content, regulatory, account and branding compliance. SCHEDMAD is responsible for reasonable technical compliance of the whizzQ-powered application within the agreed scope, subject to third-party dependencies and Merchant-provided information. Store Policies may change without notice to either party and may require updates, SDK changes, permission changes, disclosures or other remediation.
21. Mandatory Technical Updates
SCHEDMAD may require upgrades or technical changes to maintain compatibility with operating-system versions, security requirements, SDK requirements, App Store policies, payment-provider changes, API changes or other third-party dependencies. Routine compatibility updates may be included or separately chargeable according to the Merchant's plan or Order Form. Material redevelopment, new features or redesign beyond ordinary maintenance may require a separate estimate or Order Form.
22. Emergency Takedown and Protective Action
SCHEDMAD may suspend backend access, disable specific functionality, unpublish an application where technically within its control, or request the Merchant to take equivalent action where SCHEDMAD reasonably believes immediate action is necessary to address: a material security vulnerability; malware; unlawful content or conduct; material privacy breach; payment fraud; regulator direction; App Store enforcement; intellectual-property infringement; risk to a SCHEDMAD Developer Account; risk to other applications published through the same account; or material Consumer harm. Where reasonably practicable, SCHEDMAD will notify the Merchant of the basis for the action and cooperate on remediation. Where the Merchant Developer Account model applies and SCHEDMAD lacks authority to remove the app itself, the Merchant must reasonably cooperate with urgent lawful or security-related takedown requests. Emergency action should be proportionate to the identified risk.
23. Special Protection for SCHEDMAD Developer Accounts
Where the Branded Application is published through a SCHEDMAD Developer Account, the Merchant acknowledges that misconduct or non-compliance associated with one application may affect the entire SCHEDMAD account or other applications distributed through it. SCHEDMAD may therefore impose stricter content, privacy, security, operational and review controls for applications published through its own account. SCHEDMAD may immediately suspend, remove or restrict a Branded Application where continued publication creates a credible risk of suspension, termination, financial loss, reputational harm or enforcement against the SCHEDMAD Developer Account. Such protective action does not waive SCHEDMAD's other contractual rights.
24. App Store Rejection or Removal
If an App Store rejects, removes, suspends or limits the Branded Application, the parties will cooperate in good faith to identify the reason and determine reasonable remediation. SCHEDMAD does not guarantee that remediation will succeed. Where rejection is caused by Merchant Brand Assets, Merchant content, Merchant regulatory status, Merchant account status, Merchant conduct or Merchant instructions, the Merchant is responsible for associated remediation costs and consequences. Where rejection results solely from a material technical defect in SCHEDMAD's delivered application, SCHEDMAD will use reasonable efforts to correct that defect within the scope of the applicable service.
25. App Availability and Service Levels
App Store publication does not guarantee uninterrupted application availability. Availability may depend on App Store distribution, operating systems, whizzQ backend availability, cloud providers, communication providers, payment providers, internet connectivity and other third-party systems. Any committed service level applies only if expressly stated in an Branded App Order Form or SLA and will be subject to the exclusions stated there.
26. Security
SCHEDMAD will maintain reasonable technical and organisational safeguards for the whizzQ Platform and Branded Application within its control. The Merchant is responsible for securing its Developer Account, account-holder credentials, team-member permissions, devices, signing-related access under its control and Merchant-operated systems. Each party must notify the other without undue delay if it becomes aware of a material compromise that could affect the Branded Application or the other party's systems.
27. Signing Keys, Certificates and Platform Credentials
Control of application-signing keys, certificates, provisioning profiles and equivalent platform credentials will depend on the relevant App Store architecture and publishing model. Where the Merchant Developer Account is used, such credentials should ordinarily remain under the Merchant account or App Store-managed systems, with SCHEDMAD receiving only access reasonably required to build, sign or submit the application. Where SCHEDMAD Developer Account publication applies, SCHEDMAD may control the relevant signing and submission credentials. Neither party is required to disclose master credentials where role-based or platform-managed access can reasonably accomplish the required task.
28. App Transfer and Migration
At the Merchant's request, SCHEDMAD may assess whether a Branded Application can be transferred or migrated between Developer Accounts. Any transfer is subject to the relevant App Store's then-current eligibility requirements, technical limitations, account standing, legal-entity verification and formal transfer process. SCHEDMAD does not guarantee transferability of app identifiers, bundle identifiers, package names, signing relationships, entitlements, reviews, ratings, subscriptions, in-app purchases, user history, analytics history or other App Store assets. Where transfer is feasible, migration services may be separately scoped and charged. App transfer does not transfer the whizzQ Platform, source code, APIs, backend or other SCHEDMAD intellectual property.
29. Migration from a SCHEDMAD Developer Account to a Merchant Developer Account
Where a Branded Application was initially published through a SCHEDMAD Developer Account, the Merchant may request migration to its own eligible Developer Account. Such migration is not automatic and is subject to App Store rules, technical feasibility, Merchant account eligibility, payment of outstanding amounts and an agreed migration scope. The Merchant must establish and verify the destination Developer Account before migration can begin. SCHEDMAD may require settlement of reasonable migration fees and outstanding invoices before completing the transfer process.
30. Migration from a Merchant Developer Account
Where the Branded Application is published through the Merchant Developer Account, the Merchant retains control of that Developer Account after termination subject to App Store rules. Termination of the whizzQ relationship does not obligate SCHEDMAD to provide source code or a replacement backend. If the Merchant wishes to continue operating the application independently of whizzQ, a separately agreed migration, licence or replacement-development arrangement would be required and may not be technically available. Absent such an agreement, whizzQ-powered functionality may cease when the underlying whizzQ service terminates.
31. No Source Code Escrow or Transfer
Unless expressly agreed in a separate written instrument, this Addendum does not create a source-code escrow, source-code delivery obligation or right to receive the whizzQ source code upon termination, insolvency, app transfer or other event. Any source-code escrow or special continuity arrangement must be expressly negotiated and separately priced.
32. Subscription, Fees and Charges
Fees for the Branded Application may include setup, configuration, design, publication, maintenance, support, App Store administration, integration, migration, update or other charges described in the Branded App Order Form. App Store membership fees, third-party charges and Merchant Developer Account fees are the Merchant's responsibility unless the Branded App Order Form expressly states otherwise. Where SCHEDMAD Developer Account publication is used, the Branded App Order Form may specify additional charges for account administration and risk.
33. Non-Payment
If undisputed amounts relating to the Branded Application remain overdue, SCHEDMAD may suspend support, backend access, updates or other Branded Application services after reasonable notice where appropriate. Where the application is published through a SCHEDMAD Developer Account, continued non-payment may also result in removal or unpublishing of the Branded Application, subject to applicable law and reasonable treatment of active Consumer transactions. Where the application is published through the Merchant Developer Account, SCHEDMAD may disable the whizzQ backend or relevant service access even though the Merchant retains control of the App Store listing. Termination or suspension does not extinguish outstanding payment obligations.
34. Consumer Continuity on Suspension or Termination
Where suspension or termination may affect active bookings, paid transactions or pending refunds, the parties will cooperate reasonably to protect non-excludable Consumer rights and administer existing transactions. SCHEDMAD may retain limited backend functionality temporarily where reasonably necessary to process refunds, settlement, security or legally required records. The Merchant remains responsible for the underlying service and Consumer obligations arising from Merchant conduct.
35. Term and Termination
This Addendum begins when the Branded Application service is ordered or activated and continues for the applicable service term. Termination rights are governed by the Business & Merchant Terms and Order Form, together with any additional termination right stated in this Addendum. SCHEDMAD may terminate or suspend the Branded Application service for material breach, unlawful use, Developer Account ineligibility, serious security risk, App Store enforcement, repeated non-payment, intellectual-property infringement or another material risk that cannot reasonably be cured.
36. Effect of Termination
Upon termination: SCHEDMAD may cease operation and support of the Branded Application; backend functionality may be disabled; Store Materials may be removed where under SCHEDMAD control; SCHEDMAD access to Merchant Developer Accounts should be revoked when no longer required; outstanding amounts remain due; Consumer and payment obligations survive as applicable; and data will be handled under the Privacy Notice, Data Processing Addendum and applicable law. If the application remains visible in a Merchant Developer Account after whizzQ service termination, the Merchant is responsible for promptly removing, updating or replacing the application where it no longer functions accurately or lawfully.
37. Merchant Indemnity - Branded Application
To the extent permitted by law, the Merchant will indemnify SCHEDMAD and its affiliates, directors, officers, employees and authorised representatives against third-party claims, App Store sanctions, losses, penalties and reasonable legal costs arising from: Merchant Brand Assets that infringe third-party rights; Merchant content or advertising claims; Merchant regulatory or licensing failures; Merchant misuse of Personal Data; Merchant instructions that violate law or Store Policies; Merchant-controlled Developer Account misconduct; unlawful Merchant services; or other Merchant breach of this Addendum. The indemnity does not apply to the extent the claim is caused by SCHEDMAD's own fraud, wilful misconduct or liability that cannot lawfully be shifted.
38. SCHEDMAD Responsibility for Platform IP
SCHEDMAD is responsible for having the rights necessary to provide the whizzQ Platform and SCHEDMAD-developed components used in the Branded Application. Any SCHEDMAD indemnity for third-party intellectual-property claims will be governed by the Business & Merchant Terms or a specifically negotiated Order Form. SCHEDMAD is not responsible for claims arising from Merchant modifications, Merchant Brand Assets, Merchant instructions or third-party materials supplied by the Merchant.
39. Limitation of Liability
Liability under this Addendum is subject to the exclusions, limitations and aggregate liability cap stated in the Business & Merchant Terms or applicable Branded App Order Form, except to the extent applicable law prohibits such limitation. SCHEDMAD is not liable for App Store decisions, review delays, account suspensions caused by Merchant conduct, operating-system policy changes, third-party outages or other independent platform actions beyond SCHEDMAD's reasonable control. Nothing in this Addendum limits liability that cannot lawfully be limited.
40. No Guarantee of Commercial Performance
SCHEDMAD does not guarantee downloads, user adoption, app ranking, bookings, revenue, retention, ratings, reviews, search placement or other commercial results from the Branded Application. The Branded Application is a technology and distribution service, not a guarantee of marketing or business performance.
41. Confidentiality
Each party must protect non-public technical, account, credential, commercial and business information received from the other in accordance with the confidentiality obligations in the Business & Merchant Terms. Developer Account credentials, signing information, access tokens, unpublished builds and security information must be treated as Confidential Information.
42. Changes to App Store Rules
Apple, Google and other platform operators may amend their rules, verification requirements, fees, APIs, privacy disclosures, developer verification requirements and distribution systems from time to time. SCHEDMAD may update technical requirements or this Addendum where reasonably necessary to remain compatible with those changes. Material changes requiring new Merchant obligations will be communicated through reasonable means and, where appropriate, reflected in an updated Branded App Order Form or service scope.
43. Governing Law and Jurisdiction
This Addendum is governed by the laws of India. Subject to mandatory statutory rights and any valid arbitration provision in an applicable enterprise agreement, disputes arising from this Addendum are subject to the jurisdiction of competent courts at Vadodara, Gujarat, India.
44. Contact
SCHEDMAD Private Limited Operator of whizzQ Registered / Business Address: S-7, Second Floor, National Plaza, R.C. Dutt Road, Alkapuri, Vadodara, Gujarat 390007 Merchant Support: help@whizzq.app Legal Notices / Legal Contact: legal@whizzq.app Contractual Jurisdiction: Vadodara, Gujarat, India.
45. Branded App Order Form
The applicable Branded App Order Form records the selected publishing model, platforms, app scope, Developer Account details, commercial charges, maintenance/migration selections and other Merchant-specific implementation choices. Operational or commercial selections recorded there form part of this Addendum and the Merchant Agreement.