hub.man Platform Terms

Version 2026-09-29

These terms are being finalised with counsel. If they change materially, you will be asked to accept the new version before continuing.

1. About these Terms and the parties

1.1 These Platform Terms ("Terms") are an agreement between:

(a) hub.man, a company incorporated in the Federal Republic of Nigeria, with its registered office at (to be confirmed) ("hub.man", "we", "us"); and

(b) the organisation that creates or operates a hub account on the hub.man platform ("the Hub", "you").

1.2 The individual who accepts these Terms confirms that they are authorised to bind the Hub. If they are not, they must not accept these Terms or use the Service.

1.3 The Service is provided to businesses and organisations for use in the course of their activities. It is not offered to individuals acting as consumers. The Hub's own members use the Service through the Hub, under the Hub's own terms with them (see clause 14).

1.4 The agreement between hub.man and the Hub consists of the following, in this order of precedence if they conflict:

(a) any order form or written agreement signed by both parties (for example, for the Network plan);

(b) the Free Plan Addendum, while the Hub is on the Free plan and only for the matters it covers;

(c) the data protection terms in clause 12 and Schedules 1 to 3, for any matter concerning personal data;

(d) these Terms; and

(e) the plan descriptions, caps and prices on the Pricing Page.

2. Definitions

2.1 In these Terms:

(a) Account means the Hub's tenant account on the Service.

(b) Owner means a user with the owner role on the Account. Admin means a user with an admin role. Owners and Admins together are Authorised Admins. Staff means any user the Hub gives a staff, admin or owner role.

(c) Member means an individual to whom the Hub gives access to the Service as a member of the Hub, or whose data the Hub puts into the Service (including guests, visitors, applicants and event attendees).

(d) Hub Data means all data, content and files that the Hub, its Staff or its Members put into the Service, or that the Service generates specifically for the Hub. Member Data means the personal data within Hub Data.

(e) Service means the hub.man platform, including the web applications, the Hub's public pages, emails sent through the platform, APIs and related support.

(f) Plan means the subscription tier the Hub is on (for example, Free, Starter, Growth, Scale or Network), with the features, caps and fees described on the Pricing Page.

(g) Pricing Page means the hub.man pricing page published at https://hubman.app/pricing, as updated under clause 7.

(h) Subscription Term means each monthly or annual billing period of a paid Plan.

(i) Member Payment means a payment made by a Member to the Hub using the Service's payment features. Platform Fee means the percentage fee described in clause 9.

(j) Payment Gateway means a third-party payment provider supported by the Service, currently Paystack and Stripe.

(k) Lapsed means the state described in clause 10.1. Read-only Mode means the restricted access described in clause 10.2.

(l) Data Protection Laws means all laws on the processing of personal data that apply to a party's processing under these Terms, including those listed in clause 12.10.

(m) Controller and Processor have the meanings given in the applicable Data Protection Laws. Under the South African Protection of Personal Information Act 2013 (POPIA), "Controller" means "responsible party" and "Processor" means "operator". Personal data includes "personal information" under POPIA.

(n) Sub-processor means a third party engaged by hub.man that processes Member Data for the purpose of providing the Service.

(o) Security Incident means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Member Data that hub.man or its Sub-processors process.

(p) Service Data means technical and usage information about how the Service operates and is used (for example, performance metrics, error logs, feature usage counts). Where Service Data contains personal data, clause 12.3 governs it.

3. The Service

3.1 hub.man will provide the Service to the Hub under these Terms. The features included in each Plan are those described on the Pricing Page.

3.2 hub.man may change, improve or retire features. During a paid Subscription Term, hub.man will not materially reduce the core functionality of the Hub's Plan without at least 30 days' notice. If such a reduction materially harms the Hub, the Hub may terminate and receive a pro-rata refund of prepaid fees for the unused part of the Subscription Term.

3.3 Some features may be labelled beta, preview or experimental. They are provided as-is, may change or be withdrawn without notice, and are excluded from any commitment in clause 17.

3.4 The Hub may choose to connect third-party services (for example, a calendar provider, a custom domain registrar or a door-access system). The Hub's use of those services is governed by its own agreement with the third party. hub.man is not responsible for third-party services the Hub chooses to connect, except where that third party is a hub.man Sub-processor.

4. The Account and Authorised Admins

4.1 Each Account must have at least one Owner at all times. Owners may appoint and remove Admins and other Staff, and assign roles.

4.2 The Hub is responsible for:

(a) everything done through its Account by its Staff, and by anyone using its Staff's credentials;

(b) keeping credentials confidential and removing access promptly when a person leaves or no longer needs it; and

(c) keeping the Owner's contact details accurate, because hub.man sends legal, billing and security notices there (clause 25).

4.3 hub.man may treat any instruction given by an Authorised Admin through the Service, or from the Owner's registered email address, as an instruction of the Hub.

4.4 If there is a dispute about who controls the Account (for example, between former and current management of a Hub), hub.man may ask for reasonable evidence of authority and may restrict changes to the Account until the dispute is resolved. hub.man is not required to decide internal disputes of the Hub.

4.5 hub.man personnel will access the Account and Hub Data only as needed to provide support the Hub requests, maintain and secure the Service, prevent abuse, or comply with law.

5. Trial

5.1 Each Hub may use one free trial of 30 days. During the trial, the Hub receives the features described for the trial on the Pricing Page. No payment card is required to start a trial.

5.2 A trial is available once per Hub. hub.man may refuse a further trial where it reasonably believes an organisation is creating new Accounts to obtain repeated trials.

5.3 When the trial ends, the Hub may choose a paid Plan or, where offered, accept the Free Plan Addendum and move to the Free plan. If it does neither, the Account becomes Lapsed under clause 10. hub.man will not charge the Hub automatically at the end of a trial unless the Hub has chosen a paid Plan and provided payment details.

5.4 The trial is provided as-is. Clause 17 does not apply to it, and the liability cap for trials in clause 19.4 applies.

6. Subscriptions, billing and renewal

6.1 Paid Plans are billed in advance, monthly or annually as the Hub chooses, in the billing currency set for the Account. Prices are those shown on the Pricing Page for that currency when the Hub subscribes or renews, subject to clause 7.

6.2 Renewal. A paid Subscription Term renews automatically for a further period of the same length unless the Hub cancels before the renewal date. For annual Subscription Terms, hub.man will send a reminder to the Owner at least 14 days before renewal.

6.3 Caps. Each Plan has caps (for example, on active members and locations), as published on the Pricing Page. Reaching a cap does not remove existing Members, locations or records. It prevents new ones above the cap until the Hub upgrades or reduces usage.

6.4 Upgrades and downgrades. Upgrades take effect immediately, and the price difference is charged pro rata for the rest of the current Subscription Term. Downgrades take effect at the next renewal date.

6.5 Usage-based charges. Some features are charged per use (for example, identity checks and SMS), at the rates on the Pricing Page. These are billed in arrears or deducted from prepaid credit, as the Service describes.

6.6 Discounts. Discounts (for example, for nonprofit, university or government-backed hubs) are granted on application at hub.man's discretion. hub.man may require evidence of eligibility and may end a discount at the next renewal if the Hub no longer qualifies.

6.7 Late or failed payment. If a payment fails, the Account enters a grace period of 7 days, during which all features remain available. If payment is still outstanding at the end of the grace period, the Account becomes Lapsed.

6.8 Refunds. Fees are non-refundable, except where these Terms expressly provide a refund (clauses 3.2, 7.3, 12.5(d) and 22.4) or where the law requires one.

7. Price changes

7.1 hub.man sets Plan prices, caps, usage rates and Platform Fee rates, and may change them.

7.2 hub.man will give the Owner at least 30 days' written notice before a price increase or a less favourable change to caps or fees takes effect for the Hub. A change takes effect from the Hub's next renewal date after the notice period ends. The price of an annual Subscription Term already paid will not change during that term.

7.3 If the Hub does not accept a change, it may cancel before the change takes effect. Cancellation takes effect at the end of the current Subscription Term. If a change must take effect during a Subscription Term (for example, because of a change in law or in a Payment Gateway's charges to hub.man), the Hub may terminate and receive a pro-rata refund of prepaid fees.

7.4 Local-currency prices are set in a price book. They are not automatic conversions from another currency, and they may be reviewed periodically. Any review that increases a price is a change under clause 7.2.

8. Taxes

8.1 All prices and fees exclude value added tax, goods and services tax, sales tax, digital services tax and similar taxes. The Hub must pay any such taxes that apply to its purchases, in addition to the fees.

8.2 If the law requires the Hub to withhold tax from a payment to hub.man, the Hub must increase the payment so that hub.man receives the amount it would have received without the withholding, unless the parties agree in writing that the Hub will instead provide an official withholding tax receipt or credit note within 30 days of payment.

8.3 The Hub must provide accurate tax details (for example, its tax identification number and any VAT registration) so hub.man can issue valid invoices.

8.4 The Hub is solely responsible for taxes on its own sales to Members, including taxes on Member Payments.

9. Member payments, Platform Fees and Payment Gateways

9.1 The Hub may use the Service to take payments from Members, using a supported Payment Gateway.

9.2 The Hub is the seller. Each Member Payment is a transaction between the Hub and the Member. hub.man is not a party to it and is not the seller, merchant of record, agent for collection, or payment service provider. The Hub is responsible for its prices, receipts, refunds, cancellations, chargebacks, disputes, and compliance with consumer and pricing laws in its dealings with Members.

9.3 Payment Gateways are independent third parties. Payment Gateways provide their services under their own terms, which the Hub must accept where they require it. hub.man does not control, and is not responsible for, a Payment Gateway's availability, fraud screening, fund holds, settlement timing, currency conversion, fees or decisions. Gateway fees are separate from hub.man's fees.

9.4 Flow of funds. Member Payments settle from the Payment Gateway to the Hub's own gateway account or sub-account. hub.man does not receive or hold Member funds, except for the Platform Fee where the Payment Gateway deducts it at settlement.

9.5 Platform Fee. Each successful Member Payment carries a Platform Fee at the percentage shown on the Pricing Page for the Hub's Plan on the date of the payment. The Platform Fee is calculated on [the gross amount paid by the Member / the amount after gateway fees — confirm]. It is collected by deduction at settlement through the Payment Gateway or, where that is not possible, invoiced monthly in arrears.

9.6 Refunds and chargebacks. If the Hub refunds a Member Payment, or a chargeback is upheld, the Platform Fee on that payment [is not returned / is credited to the Hub's next invoice — commercial decision required], except where the refund results from an error in the Service.

9.7 Changes to Platform Fee rates are subject to clause 7.

9.8 Wallets and stored credit. If the Hub offers Members a wallet, credit balance or prepaid credit through the Service, any balance is an obligation of the Hub to the Member. hub.man provides the recording software only. The Hub is responsible for whether any stored-value arrangement it offers needs a licence or approval under the law that applies to it.

10. Lapse, read-only access and data export

10.1 The Account becomes Lapsed if:

(a) the trial ends and the Hub has not chosen a paid Plan or moved to Free;

(b) a paid subscription is cancelled or ends without renewal and the Hub has not moved to another Plan; or

(c) a payment remains unpaid at the end of the grace period in clause 6.7.

10.2 While Lapsed, the Account is in Read-only Mode:

(a) Staff can sign in, view and export Hub Data, but cannot create new operational records;

(b) Members keep read access to their own history;

(c) public booking and sign-up pages are paused; and

(d) integrations, scheduled emails and campaigns may be paused.

10.3 No deletion because of lapse. hub.man will not delete Hub Data because the Account is Lapsed. Hub Data is kept until one of the following happens:

(a) the Hub instructs hub.man to delete it (in whole or in part, including in response to a Member's request);

(b) the Account is closed under clause 22 and the export period in clause 22.5 has ended; or

(c) the law requires deletion.

10.4 Choosing a Plan restores full access for that Plan immediately.

10.5 Export right. The Hub may export Hub Data at any time, including while on Free, while Lapsed, and during the export period after termination (clause 22.5). Exports are available through the Service's self-serve tools in a commonly used, machine-readable format (for example, CSV or JSON). hub.man will give reasonable help with an export the tools cannot produce. It may charge its standard rates for work beyond reasonable help, as agreed with the Hub in advance.

11. Acceptable use

11.1 The Hub must not, and must ensure its Staff and Members do not, use the Service to:

(a) break any law, or infringe any person's rights, including privacy and intellectual property rights;

(b) upload or send unlawful, defamatory, harassing, hateful or sexually exploitative content, or any content that exploits or endangers children;

(c) send unsolicited bulk messages, or send messages to people who have not agreed to receive them where the law requires consent;

(d) carry out fraud, money laundering, terrorist financing, or payments for prohibited goods or services;

(e) upload malware, or probe, scan or test the Service's security without hub.man's written permission;

(f) access or attempt to access another hub's data or Account, or get around tenant isolation, caps, attribution or other technical limits;

(g) resell, sublicense or provide the Service to third parties as a service bureau, except as a Plan expressly allows (for example, a Network plan for a hub network);

(h) overload the Service, or use automated means to access it except through the published APIs and within their limits; or

(i) collect identity or verification data for any purpose other than the one disclosed to the Member.

11.2 hub.man may remove content or restrict features to the extent needed to stop a breach of this clause, and will tell the Hub what it has done and why, unless the law prevents it.

12. Data protection

12.1 Roles.

(a) For Member Data, the Hub is the Controller and hub.man is the Processor.

(b) For the personal data of the Hub's Authorised Admins and Staff that hub.man uses to manage the Account, bill the Hub, provide support, keep the Service secure, and communicate with the Hub, hub.man is an independent Controller. That processing is described in hub.man's Privacy Notice at https://hubman.app/legal/platform-terms.

12.2 Instructions. hub.man will process Member Data only on the Hub's documented instructions. The Hub's instructions are these Terms, the Hub's configuration and use of the Service, and any other written instructions the parties agree. hub.man will tell the Hub if it believes an instruction breaks Data Protection Laws. If the law requires hub.man to process Member Data otherwise than on the Hub's instructions, hub.man will tell the Hub first, unless the law prohibits it.

12.3 Limits on hub.man's use. hub.man will not:

(a) sell, rent or trade Member Data, or exchange it for money or other valuable consideration;

(b) use Member Data to market hub.man's or anyone else's products or services to Members;

(c) use Member Data for advertising, profiling or tracking across hubs; or

(d) [use Member Data to train artificial intelligence models for any purpose other than providing the Service to the Hub — confirm against the AI-assist implementation and any AI Sub-processor's terms].

hub.man may use Service Data to operate, secure, support and improve the Service. Where Service Data contains Member Data, hub.man will use it only for those purposes, keep it to the minimum needed, and not disclose it except to Sub-processors.

12.4 Personnel. hub.man will ensure that everyone it authorises to process Member Data is bound by a duty of confidentiality.

12.5 Sub-processors.

(a) The Hub gives hub.man general authorisation to engage Sub-processors. The current list is in Schedule 2.

(b) hub.man will impose data protection obligations on each Sub-processor that are at least as protective as those in this clause 12, and remains responsible to the Hub for its Sub-processors' performance.

(c) hub.man will give the Owner at least 30 days' notice before adding or replacing a Sub-processor, except in an emergency needed to keep the Service running or secure, in which case notice will follow as soon as practicable.

(d) The Hub may object on reasonable data protection grounds within that notice period. The parties will discuss the objection in good faith. If they cannot resolve it, the Hub may terminate the affected part of the Service and receive a pro-rata refund of prepaid fees.

(e) Payment Gateways process payment data to provide their own regulated services, and may act as independent Controllers for that data under their own terms. They are listed in Schedule 2 for transparency.

12.6 International transfers. Member Data may be processed outside the country where the Hub or its Members are located, including in the locations listed in Schedule 2. Where Data Protection Laws restrict such transfers, hub.man will ensure a lawful transfer mechanism is in place before the transfer (for example, an adequacy decision, appropriate contractual safeguards, or standard contractual clauses approved under the applicable law).

12.7 Assistance. Taking into account the nature of the processing, hub.man will give the Hub reasonable assistance with:

(a) responding to Members exercising their rights (access, correction, deletion, objection, portability and similar), mainly through the Service's self-serve tools;

(b) data protection impact assessments and consultations with regulators relating to the Service; and

(c) meeting the Hub's security and breach notification obligations.

If a Member contacts hub.man directly about Member Data, hub.man will refer them to the Hub and will not respond on the Hub's behalf unless instructed or required by law.

12.8 Deletion and return. At the end of the Service, hub.man will make Member Data available for export under clause 22.5 and then delete it under clause 22.6, unless the law requires hub.man to keep it.

12.9 Information and audit. hub.man will make available the information reasonably needed to show compliance with this clause 12, including security documentation and summaries of independent assessments where available. If that information is not enough to meet the Hub's legal obligations, the Hub may carry out an audit, not more than once in any 12 months, on at least 30 days' notice, at its own cost, during business hours, subject to confidentiality, and in a way that does not compromise other hubs' data or the security of the Service.

12.10 Applicable laws. Each party will comply with the Data Protection Laws that apply to it, including, where applicable:

(a) the Nigeria Data Protection Act 2023 and regulations and directives issued by the Nigeria Data Protection Commission;

(b) the Kenya Data Protection Act 2019 and its regulations, supervised by the Office of the Data Protection Commissioner;

(c) the Ghana Data Protection Act 2012 (Act 843), supervised by the Data Protection Commission;

(d) the South African Protection of Personal Information Act 2013, supervised by the Information Regulator; and

(e) the EU General Data Protection Regulation and the UK GDPR, where the Hub, or its processing of Member Data, falls within their scope.

12.11 Registration. Each party is responsible for its own registration, notification or fee obligations with a data protection regulator. hub.man will maintain the registrations it is required to hold as a Processor [confirm which registrations hub.man holds or needs].

12.12 GDPR processing terms. Where the GDPR or UK GDPR applies, this clause 12 and Schedule 1 are intended to meet the requirements for a contract between a Controller and a Processor. Where Member Data subject to those laws is transferred to a country without an adequacy decision, the relevant standard contractual clauses are incorporated by reference [module and annex details to be completed by counsel].

12.13 Sensitive data. The Service's identity verification feature processes identity document and verification data, which may include biometric data. Some Data Protection Laws treat this as sensitive or special category data. The Hub must only enable identity verification where it has a lawful basis and has given Members any notice the law requires, and must not otherwise put sensitive personal data into the Service unless the feature is designed for it.

13. Security and incidents

13.1 hub.man will implement and maintain appropriate technical and organisational measures to protect Member Data, taking into account the state of the art, the cost of implementation, and the nature, scope and risks of the processing. These measures are outlined in Schedule 3 and may be updated, provided the overall level of protection is not reduced.

13.2 The Hub is responsible for its own security in using the Service, including managing user roles, protecting credentials, securing its own devices and connected systems, and deciding what data it puts into the Service.

13.3 Security Incidents. If hub.man becomes aware of a Security Incident, it will:

(a) notify the Owner without undue delay, and in any event within 48 hours of becoming aware of it;

(b) give the information reasonably available about the nature of the incident, the categories and approximate number of Members and records affected, the likely consequences, and the steps taken or proposed; and supplement it as more becomes known;

(c) take reasonable steps to contain the incident and reduce its effects; and

(d) cooperate reasonably with the Hub's investigation and its notifications.

13.4 As Controller, the Hub decides whether to notify regulators and Members. hub.man will not notify the Hub's regulators or Members about a Security Incident on the Hub's behalf unless the Hub asks it to, or the law requires it.

13.5 Notifying or responding to a Security Incident is not an admission of fault or liability by hub.man.

14. The Hub's obligations to its Members

14.1 The Hub is responsible for its relationship with its Members, including the terms on which it gives them access to the Service. hub.man is not a party to those terms. Members are not third-party beneficiaries of these Terms.

14.2 The Hub must:

(a) have a lawful basis for all Member Data it puts into, or collects through, the Service;

(b) give Members a privacy notice that meets Data Protection Laws. The notice must explain that the Hub uses service providers to run its platform, including cross-border processing where it applies;

(c) obtain and record any consent the law requires. This includes consent for newsletters and marketing sent through the Service, for identity checks where consent is the lawful basis, and before making a Member's profile publicly visible (the Service keeps profiles private by default);

(d) respond to Members' data protection requests, using the Service's tools and hub.man's assistance under clause 12.7;

(e) obtain verifiable consent from a parent or guardian before processing a child's personal data, where the law requires it, and not use features unsuitable for children with Members under the age of majority;

(f) comply with consumer, pricing, anti-spam and electronic communications laws in its dealings with Members;

(g) moderate communities, events and other shared spaces it runs, and act on reports of misuse; and

(h) ensure its Members comply with clause 11.

14.3 The Hub is the sender of emails, newsletters and campaigns it sends through the Service. It is responsible for having the right to send them and for honouring unsubscribe requests.

15. Intellectual property

15.1 hub.man and its licensors own all rights in the Service, including its software, design, documentation and the hub.man name and marks. These Terms give the Hub no rights in them other than the right to use the Service as these Terms allow.

15.2 The Hub (or its Members or licensors) owns all rights in Hub Data. The Hub grants hub.man a non-exclusive, worldwide licence to host, copy, process, transmit and display Hub Data only as needed to provide, secure and support the Service and as these Terms otherwise permit.

15.3 The Hub grants hub.man a licence to use the Hub's name, logo and branding within the Service and on the Hub's public pages, as the Hub configures them.

15.4 If the Hub gives feedback or suggestions, hub.man may use them without restriction or payment. hub.man will not identify the Hub as their source without the Hub's consent.

15.5 The Hub must not copy, modify, reverse engineer or decompile the Service, except to the extent the law allows despite this restriction.

15.6 hub.man will not name the Hub as a customer in its marketing without the Hub's prior consent. This clause does not restrict the attribution described in the Free Plan Addendum.

16. Confidentiality

16.1 Each party will keep confidential the other party's non-public information that is marked confidential or that a reasonable person would understand to be confidential. It will use that information only to perform or exercise rights under these Terms, and disclose it only to personnel, advisers and Sub-processors who need to know it and are bound by equivalent duties.

16.2 This obligation does not apply to information that is or becomes public without breach, was already lawfully known, is independently developed, or is lawfully received from a third party without restriction.

16.3 A party may disclose confidential information where the law, a court or a regulator requires it. Where legally permitted, it must first give the other party notice and a chance to object.

16.4 Member Data is also protected by clause 12, which prevails if the two conflict.

17. Availability and support

17.1 hub.man will use reasonable efforts to make the Service available and to fix faults promptly. hub.man does not offer a service level agreement, uptime commitment or service credits unless it has agreed one in a signed written agreement with the Hub.

17.2 hub.man may carry out planned maintenance and will give notice where practicable. It may carry out urgent maintenance without notice.

17.3 The Service depends on third-party infrastructure, including hosting, email and Payment Gateway providers, and on internet and power infrastructure. hub.man is not responsible for unavailability caused by events outside its reasonable control (clause 26.4).

17.4 Support is available through the channels and at the levels described for the Hub's Plan on the Pricing Page.

18. Warranties and disclaimers

18.1 Each party warrants that it has the authority to enter into these Terms.

18.2 hub.man warrants that it will provide paid Plans with reasonable skill and care. If the Service does not conform to this warranty, the Hub's remedy is for hub.man to use reasonable efforts to correct the non-conformity. If it cannot do so within a reasonable time, the Hub may terminate the affected Plan and receive a pro-rata refund of prepaid fees.

18.3 Except as these Terms expressly state, and to the extent the law allows, the Service is provided "as is" and "as available". hub.man gives no other warranties, whether express or implied, including warranties of merchantability, fitness for a particular purpose, or uninterrupted or error-free operation.

18.4 The Service is a tool. It does not give legal, tax, accounting or regulatory advice. Identity verification results come from third-party sources and may be incomplete or wrong. The Hub remains responsible for its own decisions.

19. Limitation of liability

19.1 Nothing in these Terms limits or excludes liability that cannot lawfully be limited or excluded, including for fraud, or for death or personal injury caused by negligence.

19.2 Clauses 19.3 to 19.5 do not limit:

(a) the Hub's obligation to pay fees, Platform Fees and taxes;

(b) the Hub's indemnity in clause 20.1; or

(c) either party's liability for wilful misconduct.

19.3 Neither party is liable for any indirect or consequential loss, or for loss of profit, revenue, business, goodwill or anticipated savings, however it arises.

19.4 Each party's total aggregate liability arising from or in connection with these Terms, in any 12-month period, is limited to:

(a) for a paid Plan, the subscription fees the Hub paid or must pay to hub.man in the 12 months before the event giving rise to the claim; and

(b) for a trial or the Free plan, USD 100 or its equivalent in the Hub's billing currency.

19.5 Data protection claims. For claims arising from a breach of clause 12 or 13, each party's total aggregate liability is limited to [two times the amount in clause 19.4 / a fixed amount — commercial decision required]. This separate cap does not increase the amount available for other claims.

20. Indemnities

20.1 The Hub will defend and indemnify hub.man against third-party claims, including claims by Members and regulators, and any resulting losses, fines (where the law allows them to be indemnified), damages and reasonable legal costs, to the extent they arise from:

(a) Hub Data, or the Hub's instructions to hub.man;

(b) the Hub's or its users' breach of clause 11 or clause 14;

(c) the Hub's dealings with Members, including Member Payments, refunds, chargebacks and stored credit; or

(d) the Hub's failure to meet its obligations as Controller.

20.2 On paid Plans, hub.man will defend the Hub against any third-party claim that the Service, as provided by hub.man, infringes that party's intellectual property rights, and will pay any resulting damages or settlement hub.man approves. This does not apply to claims arising from Hub Data, third-party services the Hub connects, or modifications or combinations hub.man did not make. If such a claim is made or likely, hub.man may modify the Service, obtain a licence, or terminate the affected feature and refund prepaid fees for it.

20.3 The party seeking an indemnity must promptly notify the other in writing and give it reasonable cooperation and control of the defence and settlement. No settlement admitting fault by the indemnified party may be made without its consent.

21. Suspension

21.1 hub.man may suspend all or part of the Account, or a user's access, where reasonably necessary:

(a) to prevent or respond to a security threat, or a threat to the Service or other hubs;

(b) because of a serious breach of clause 11;

(c) to comply with law or with an order of a court or regulator; or

(d) for non-payment, after the grace period in clause 6.7 (in which case the Account becomes Lapsed rather than suspended).

21.2 hub.man will limit the suspension to what is reasonably necessary, give notice (in advance where practicable), and restore access once the reason has been resolved. Suspension does not remove the Hub's right to export Hub Data under clause 10.5, unless export would itself continue the harm or break the law.

22. Term and termination

22.1 These Terms start when the Hub accepts them and continue until the Account is closed under this clause.

22.2 The Hub may cancel its paid subscription at any time through the Service. Cancellation takes effect at the end of the current Subscription Term, after which the Account becomes Lapsed. The Hub may close its Account entirely by written request from an Owner.

22.3 Either party may terminate these Terms by written notice if the other party:

(a) materially breaches these Terms and does not remedy the breach within 30 days of notice; or

(b) becomes insolvent, enters administration, liquidation or a similar process, or stops carrying on business.

22.4 hub.man may terminate these Terms for convenience on at least 90 days' notice. If it does, it will refund prepaid fees for the unused part of any Subscription Term.

22.5 Export period. After termination or closure, the Account stays in Read-only Mode for 90 days so the Hub can export Hub Data, unless the Hub instructs earlier deletion.

22.6 Deletion. After the export period ends, hub.man will delete Hub Data from the live Service within 30 days, and from backups within its backup retention cycle (currently [BACKUP RETENTION PERIOD — confirm]), unless the law requires hub.man to keep it. hub.man will confirm deletion in writing on request.

22.7 Clauses 8, 9.2, 9.6, 10.5 (for the export period), 12 (for as long as hub.man holds Member Data), 15, 16, 19, 20, 22.5 to 22.7, 24 and 26 survive termination.

23. Changes to these Terms

23.1 These Terms are versioned. Each version shows its date in the version field. hub.man will keep previous versions available at https://hubman.app/legal/platform-terms.

23.2 Non-material changes (for example, clarifications, corrections, or changes that do not reduce the Hub's rights) take effect on the date stated in a notice sent to the Owner or shown in the Service. The notice will be given at least 14 days in advance where practicable.

23.3 Material changes are changes that reduce the Hub's rights or increase its obligations in a meaningful way, or that change how Member Data is processed. For these:

(a) hub.man will notify the Owner at least 30 days before the change takes effect, with a summary of what is changing;

(b) an Authorised Admin must accept the new version through the Service to continue using the Service after the effective date;

(c) if the new version has not been accepted by the effective date, the Account will move to Read-only Mode until it is accepted. The Hub keeps its export right, and no Hub Data is deleted; and

(d) instead of accepting, the Hub may terminate and receive a pro-rata refund of prepaid fees for the unused part of the Subscription Term.

23.4 A change required by law, by a regulator or by a Payment Gateway may take effect sooner, if that is required. hub.man will give as much notice as it reasonably can.

23.5 hub.man will record each acceptance, including the version accepted, the user who accepted it and the time.

24. Governing law and disputes

24.1 These Terms, and any dispute or claim arising from them (including non-contractual disputes), are governed by the laws of the Federal Republic of Nigeria.

24.2 The parties will first try to resolve any dispute through good-faith discussion between senior representatives for 30 days after one party notifies the other of the dispute.

24.3 If the dispute is not resolved, it will be finally resolved by arbitration under the Arbitration and Mediation Act 2023 of Nigeria. The seat will be Lagos, there will be a single arbitrator, and the proceedings will be in English. [Alternative for counsel: exclusive jurisdiction of the courts of Lagos State.]

24.4 Either party may seek urgent interim relief from any competent court.

24.5 This clause does not deprive the Hub, its Members or any regulator of the protection of mandatory laws of the country where the Hub is established, including Data Protection Laws.

25. Notices

25.1 hub.man will send notices to the Hub by email to the Owner's registered address and, where appropriate, in the Service. The Hub is responsible for keeping that address current.

25.2 The Hub must send notices to hub.man by email to hello@hubman.app. Formal legal notices, including notices of breach, termination or legal proceedings, must also be sent by courier to hub.man, (to be confirmed).

25.3 An email notice is treated as received on the next business day after it is sent, unless the sender receives a delivery failure message. A courier notice is treated as received on the date of delivery.

26. General

26.1 Entire agreement. The documents in clause 1.4 are the whole agreement between the parties about the Service and replace any earlier understandings. Terms on the Hub's purchase orders do not apply.

26.2 Assignment. The Hub may not transfer these Terms without hub.man's written consent, which will not be unreasonably withheld. hub.man may transfer these Terms to an affiliate, or to a successor in a merger, acquisition or sale of all or substantially all of its relevant business, on notice to the Hub.

26.3 Subcontracting. hub.man may use subcontractors, subject to clause 12.5 for Sub-processors, and remains responsible for them.

26.4 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control. Such events include failures of power, internet or third-party infrastructure, natural disasters, civil unrest, government action and industrial action (other than by the affected party's own staff). This clause does not excuse payment obligations.

26.5 Severability. If any part of these Terms is found invalid or unenforceable, the rest remains in force, and the affected part will be applied as closely as possible to its original intent.

26.6 No waiver. A failure or delay in exercising a right is not a waiver of it.

26.7 Relationship. The parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency or employment relationship.

26.8 Electronic acceptance. The parties agree that accepting these Terms electronically through the Service has the same effect as a signature.

26.9 Anti-corruption and sanctions. Each party will comply with anti-bribery and anti-corruption laws that apply to it. The Hub confirms that it is not subject to sanctions that would make it unlawful for hub.man to provide the Service to it.

26.10 Language. These Terms are written in English. Any translation is for convenience only, and the English version prevails.

Schedule 1. Details of processing

S1.1 Subject matter and duration. Provision of the Service to the Hub, for the term of these Terms and the export and deletion periods in clause 22.

S1.2 Nature and purpose. Hosting, storage, organisation, retrieval, transmission, display and deletion of Member Data to enable the Hub's operations. These include membership management, bookings, check-in, events, communities, directories, support, payments, communications, programmes, learning, visitor management, access control integration, identity verification, analytics and exports, as enabled for the Hub's Plan.

S1.3 Categories of data subjects. Members, applicants, guests, visitors, event attendees, and the Hub's Staff (to the extent their data is Member Data and not account data under clause 12.1(b)).

S1.4 Categories of personal data. Contact details; profile information the Hub or Member provides; membership, booking, attendance and check-in records; communications and support content; payment records (not full card details, which the Payment Gateway handles); wallet balances; programme and learning records; and, where the Hub enables identity verification, identity document and verification data.

S1.5 Sensitive data. Identity verification data, which may include biometric data, only where the Hub enables that feature. Any other sensitive data only as the Hub decides to collect, subject to clause 12.13.

Schedule 2. Sub-processors

S2.1 The following Sub-processors are authorised at the date of this version. [Engineering and counsel to confirm each entity, its processing location and the transfer mechanism before publication.]

S2.2 Third-party services the Hub connects itself (for example, its own calendar account) are not Sub-processors (clause 3.4).

Schedule 3. Security measures (outline)

S3.1 [To be completed with verified controls only. Engineering must confirm each item before publication. Do not publish any measure that is not in place.] Proposed headings:

(a) tenant isolation: every record is scoped to a tenant, and access checks are enforced server-side on every request;

(b) role-based access control for Staff, with least-privilege roles;

(c) encryption of data in transit;

(d) encryption of data at rest [confirm with hosting provider];

(e) secrets held in environment configuration, not in the database;

(f) authentication controls [confirm multi-factor options];

(g) logging and audit trails for administrative actions;

(h) backups and recovery [confirm frequency and retention];

(i) vulnerability management and dependency updates;

(j) personnel confidentiality and access limited to need; and

(k) incident response procedure supporting clause 13.3.