Legal

Terms & Privacy

How SemaHub protects personal data, and the terms for using SemaHub for customer messaging, bulk SMS, transactional messaging, OTP and future WhatsApp services.

Document owner
SemaHub management and Data Protection Officer
Version
1.0
Review cycle
At least annually and upon material legal, regulatory or service change
Privacy contact
info@techcraft.co.tz +255 745 470 673

Document structure

This legal pack contains a public-facing privacy policy and binding platform terms. The schedules form part of the Terms and are intended to support customer onboarding, regulatory due diligence and controller-processor contracting.

Part A

Data Protection and Privacy Policy

1Purpose and scope

1.1This Policy explains how SemaHub ("we", "us" or "our") collects, uses, stores, discloses and protects personal data when a person visits our website, opens an account, buys messaging credits, uses our dashboard or application programming interfaces, receives support, or receives a message sent through our platform.

1.2The Policy applies to SMS, bulk messaging, transactional notifications, one-time passwords, delivery reporting, contact management, integrations and any WhatsApp or other communications channel subsequently made available through the platform.

1.3For account, billing, security, marketing and website data that we determine how and why to process, SemaHub acts as a data controller. For recipient telephone numbers, contact lists, message content and campaign instructions uploaded by a customer, SemaHub ordinarily acts as a data processor on behalf of that customer, which remains the data controller. SemaHub may independently control limited messaging metadata where required for security, fraud prevention, billing, regulatory compliance or the establishment and defence of legal claims.

2Governing principles

We process personal data lawfully, fairly and transparently; for explicit, specified and legitimate purposes; in a manner limited to what is necessary; accurately; for no longer than needed; in accordance with data-subject rights; securely; and subject to lawful cross-border transfer safeguards. These commitments reflect the Personal Data Protection Act, Chapter 44 and the Personal Data Protection Personal Data Collection and Processing Regulations, 2023.

3Personal data we process

Account and identity
Examples
Name, company, job title, username, signature, identity and registration documents
Primary source
Customer or authorised user
Contact
Examples
Email address, telephone number, business and billing address
Primary source
Customer or authorised user
Billing and transaction
Examples
Invoices, payments, tax information, credit balance and purchase history
Primary source
Customer and payment provider
Recipient and campaign
Examples
Telephone numbers, contact attributes, groups, consent fields, campaign name and message content
Primary source
Customer as controller
Messaging metadata
Examples
Sender ID, recipient network, timestamps, message or segment count, routing, status, error and delivery receipts
Primary source
Platform, operators and upstream gateways
Technical and security
Examples
IP address, device and browser data, authentication events, API keys, audit logs and suspected abuse indicators
Primary source
Automated platform collection
Support and communications
Examples
Tickets, calls, emails, feedback and troubleshooting material
Primary source
Customer or user
Website data
Examples
Cookie identifiers, session data and usage analytics
Primary source
Browser or device
Compliance data
Examples
Consent evidence, opt-out records, customer declarations, sender-ID documents and regulatory correspondence
Primary source
Customer, regulator or platform

4Purposes and lawful grounds

Provide and administer the service
Data used
Account, recipient, content and messaging metadata
Lawful ground or justification
Performance of contract; customer instructions
Route and deliver messages
Data used
Recipient number, sender ID, content and routing metadata
Lawful ground or justification
Performance of contract; legitimate operational purpose
Process payments and accounting
Data used
Billing and transaction data
Lawful ground or justification
Contract and legal obligations
Secure the platform
Data used
Technical, audit and messaging metadata
Lawful ground or justification
Legal obligation and legitimate interest in preventing fraud and misuse
Meet regulatory duties
Data used
Identity, content and compliance records
Lawful ground or justification
Compliance with law and lawful regulatory requests
Support customers
Data used
Account, technical and support data
Lawful ground or justification
Contract and legitimate interest
Improve reliability and capacity
Data used
Aggregated usage and performance data
Lawful ground or justification
Legitimate interest; anonymisation where practicable
Send SemaHub marketing
Data used
Business contact and preference data
Lawful ground or justification
Consent where required; right to object and opt out
Establish or defend claims
Data used
Relevant account, transaction, message and audit records
Lawful ground or justification
Legal obligation and legitimate interest

5Customer-controlled recipient data

5.1Customers decide whose contact data is uploaded, why messages are sent and what each message says. Each customer must provide its own privacy notice, establish a lawful ground, obtain and record any required consent, honour opt-outs, maintain accurate lists and avoid uploading data that is excessive or unlawfully obtained.

5.2SemaHub does not acquire ownership of customer contact lists or use them to advertise SemaHub or another customer’s products. We process such data only to provide, secure and support the service, comply with law and exercise legal rights.

5.3A recipient who wishes to challenge the purpose, accuracy or legality of a customer campaign should contact the identified sender. SemaHub will assist the relevant customer and may directly act where required by law or necessary to prevent harm.

6Consent and direct marketing

6.1A customer sending promotional or direct-marketing messages must obtain valid consent before transmission unless another lawful exception clearly applies. Consent should be freely given, specific, informed, demonstrable and capable of easy withdrawal.

6.2Marketing messages must identify the sender and commercial purpose, use an approved sender ID, and provide a clear, functional and reasonably accessible method to opt out. An opt-out must be honoured promptly and the number placed on a suppression list so that it is not re-imported into a marketing campaign.

6.3Transactional messages may be sent only where genuinely necessary for the requested service or relationship. A customer may not label advertising as transactional to bypass consent or opt-out requirements.

7Disclosure and recipients

We may disclose only the personal data necessary to the following recipients: mobile network operators, messaging aggregators, hosting and infrastructure providers, payment processors, professional advisers, auditors, support providers, regulators, courts, law-enforcement bodies, and a successor in a lawful corporate transaction. Providers acting for us must be bound by confidentiality, security and data-protection obligations appropriate to their role. We do not sell recipient lists.

8International transfers

Where processing or a service provider would transfer personal data outside Tanzania, SemaHub will assess the transfer, implement appropriate legal, contractual and technical safeguards, and obtain any permit or approval required from the Personal Data Protection Commission. A customer must not configure an integration or instruct a transfer that would cause an unlawful cross-border transfer.

9Retention and deletion

We retain personal data only for the purpose and period that can be justified, subject to legal preservation, tax, telecommunications, audit, dispute and regulatory requirements. The following are our default operational periods.

Queued message content
Default operational period
Until delivery attempt is completed, then up to 90 days for troubleshooting
End-of-period action
Secure deletion or irreversible anonymisation
Delivery and routing metadata
Default operational period
24 months after transmission
End-of-period action
Delete or aggregate unless legal hold applies
Customer contact lists
Default operational period
Life of account and up to 30 days after verified deletion or termination request
End-of-period action
Secure deletion from active systems and expiry from backups
Consent and opt-out evidence
Default operational period
Life of the campaign relationship plus 5 years
End-of-period action
Delete after claims and regulatory period
Account and support records
Default operational period
Life of account plus 5 years
End-of-period action
Delete or minimise
Invoices and financial records
Default operational period
Period required by applicable tax and accounting law
End-of-period action
Secure deletion after statutory period
Security and authentication logs
Default operational period
12 months, or longer for an active investigation
End-of-period action
Delete or aggregate
Suppression list
Default operational period
For as long as necessary to prevent unlawful re-contact
End-of-period action
Retain minimal hashed or restricted record

10Information security

SemaHub applies risk-based technical and organisational measures, including role-based access, multi-factor authentication for privileged access, encryption in transit, protected secrets, network and application controls, logging and monitoring, backup and restoration procedures, vulnerability management, change control, staff confidentiality, supplier due diligence, incident response and periodic testing. No internet service is risk free; customers must secure their credentials, integrations, endpoints and authorised users.

11Personal data breaches

11.1We maintain procedures to detect, contain, investigate, document and remediate suspected personal data breaches. Where SemaHub acts as processor, we will notify the affected customer without undue delay after confirming a breach affecting customer personal data and provide reasonably available information to support the customer’s assessment and notification duties.

11.2Where SemaHub acts as controller, we will notify the Personal Data Protection Commission without undue delay when required and will notify affected data subjects where required by law or directed by the Commission. We may provide information in phases as the investigation develops.

12Data-subject rights

Subject to the Act, applicable exceptions and identity verification, a data subject may request information about processing; access; correction; erasure or destruction; restriction or prevention of harmful processing; cessation of direct marketing; review of certain automated decisions; and any remedy or compensation available under law. Requests may be sent to info@techcraft.co.tz. If SemaHub processes the data solely for a customer, we may refer the request to that customer and assist it in responding.

13Children and sensitive personal data

The platform is not intended for independent use by children. Customers may not upload or use children’s data, financial transaction data, health data, biometric data or other sensitive personal data unless the processing is strictly necessary, lawful, properly authorised and protected by enhanced safeguards. SemaHub may require a data protection impact assessment and written approval before such use.

14Cookies and analytics

The website may use essential cookies for authentication, security and preferences and, where enabled, optional analytics cookies. Non-essential cookies will be managed through an appropriate consent mechanism. Details of active cookies, providers and durations must be maintained in the website cookie notice.

15Complaints and contacts

Questions, rights requests and complaints may be sent to: Data Protection Officer, SemaHub, email info@techcraft.co.tz, telephone +255 745 470 673. A person may also lodge a complaint with the Personal Data Protection Commission. We encourage the person to contact us first so that we can investigate promptly.

16Changes to this Policy

We may update this Policy to reflect legal, regulatory, security or service changes. Material changes will be notified through the platform, email or another reasonable channel before or when they take effect. The current version and effective date will remain available on the platform.

Part B

Messaging Platform Terms and Conditions

These Terms form a binding agreement between the customer identified during registration or in an order form ("Customer") and SemaHub. By creating an account, signing an order form, integrating an API or using the Service, the Customer confirms that it has read, understood and accepted these Terms, including all Schedules.

1Definitions and interpretation

Applicable Law
Meaning
All laws, regulations, licence conditions, regulator directions and binding operator requirements applicable to a party or the Service in Tanzania and any relevant destination country.
Authorised User
Meaning
A person whom the Customer permits to access its account or API credentials.
Customer Data
Meaning
Any data, recipient list, content, instruction or material submitted by or for the Customer.
Message
Meaning
An SMS, OTP, transactional notification, WhatsApp communication or other electronic communication submitted through the Service.
Recipient
Meaning
A person or endpoint to which the Customer directs a Message.
Regulator
Meaning
TCRA, the Personal Data Protection Commission, a court, law-enforcement authority or other competent authority.
Sender ID
Meaning
The approved numeric or alphanumeric identity displayed or associated with a Message.
Service
Meaning
The SemaHub messaging dashboard, APIs, routing, delivery reporting, contact tools, integrations and related services.
SMS Segment
Meaning
A billable unit determined by encoding, character count and operator rules; one displayed long message may contain several segments.

1.1Headings aid navigation and do not affect interpretation. "Including" means including without limitation. If an order form conflicts with these Terms, the order form prevails only where it expressly identifies the clause being varied. The Data Processing Addendum prevails for personal-data processing matters.

2Eligibility and authority

2.1The Customer represents that it is legally capable of entering the agreement and that the person accepting it has authority to bind the Customer. Individual users must be at least 18 years old.

2.2The Customer must provide accurate onboarding, beneficial ownership, tax, business, sender-ID and use-case information and promptly update it. SemaHub may perform know-your-customer, sanctions, fraud, credit, regulatory and use-case checks and may refuse or condition activation where risk cannot reasonably be managed.

3Account security

3.1The Customer is responsible for all activity conducted through its account, API keys and Authorised Users, except to the extent caused by SemaHub’s breach. Credentials must be unique, confidential and securely stored. API keys must not be embedded in public code or client-side applications.

3.2The Customer must immediately notify SemaHub of suspected unauthorised access, credential compromise, fraudulent traffic or security incident. SemaHub may rotate credentials, restrict access or suspend traffic to protect the Service and its users.

4Service description and changes

4.1SemaHub will provide the Service with reasonable skill and care, subject to network availability, upstream providers, maintenance, lawful filtering, destination-country rules and these Terms. Unless a signed service-level agreement states otherwise, delivery times and delivery success are not guaranteed.

4.2SemaHub may modify routes, interfaces, limits or features for security, compliance, interoperability or service improvement. We will provide reasonable advance notice of a materially adverse change where practicable, but may act immediately where required by law, a carrier or urgent security risk.

4.3WhatsApp and other third-party channels are subject to the applicable provider’s policies, template approval, pricing and account decisions. Access may be changed or withdrawn by that provider independently of SemaHub.

5Customer role and responsibility for Messages

5.1The Customer alone determines the recipients, purpose, timing and content of its Messages. The Customer is the originator and, for recipient data and campaign content, ordinarily the data controller. SemaHub transmits Messages on the Customer’s documented instructions and does not pre-approve or adopt their meaning merely by processing them.

5.2The Customer must ensure that every Message, list and campaign complies with Applicable Law, the Acceptable Use Rules, its own published privacy notice and any sector-specific rules applying to banking, insurance, health, education, gambling, elections, financial services or another regulated activity.

5.3Automated controls, sampling or a failure by SemaHub to block a Message do not constitute legal approval and do not reduce the Customer’s responsibility.

6Consent, lawful basis and recipient lists

6.1Before uploading a number or sending a Message, the Customer shall have and document an appropriate lawful basis. For promotional or direct marketing, the Customer shall obtain valid prior consent unless a specific lawful exception applies and can be demonstrated.

6.2The Customer shall retain evidence showing the recipient, date, time, source, wording and channel of consent; the privacy notice presented; the sender or brands covered; and any withdrawal. SemaHub may request a representative sample or full evidence where a complaint, audit or risk indicator arises.

6.3The Customer shall not use purchased, rented, scraped, harvested, randomly generated or third-party lists unless it can demonstrate a lawful collection source and valid authority for the specific sender, purpose and channel. A number being publicly visible does not by itself constitute marketing consent.

6.4The Customer shall maintain a suppression list, honour opt-outs promptly, and prevent a person who opted out from being re-added through a later import. Where a reply-based STOP mechanism is unavailable, the Message must provide another clear and reasonably accessible opt-out route.

7Sender IDs and sender identification

7.1The Customer may use only a Sender ID approved by SemaHub, the relevant mobile networks and authorities. The Customer shall provide genuine supporting documents and may use a brand, name or mark only with the owner’s authority.

7.2The Customer shall not spoof, imitate or misrepresent another person, public body, bank, mobile operator or brand. Each Message must clearly identify the sender where the Sender ID or content could otherwise be ambiguous.

7.3Sender-ID approval is not approval of every future Message. SemaHub may disable a Sender ID following a complaint, expiry, changed use case, regulator or carrier instruction, misleading use or inadequate supporting information.

8Content standards and prohibited uses

8.1The Customer shall comply with Schedule 2. Prohibited activity includes fraud, phishing, impersonation, malware, unlawful financial solicitation, harassment, threats, incitement, unlawful discrimination, obscene or exploitative content, intellectual-property infringement, deceptive promotions, unlawful political or electoral messaging, evasion of filtering, traffic pumping and any communication that violates a recipient’s privacy or other rights.

8.2The Customer must not use the Service to collect passwords, PINs, one-time passwords, card credentials or other authentication secrets through deceptive or unauthorised means.

9Customer records and audits

9.1The Customer shall keep sufficient records to demonstrate compliance, including consent, privacy notices, list provenance, opt-outs, sender-ID authority, campaign approvals, complaints and regulatory permissions, for the applicable legal period and at least five years after the relevant campaign where no longer period applies.

9.2On reasonable notice, or immediately following a complaint, regulator inquiry or suspected serious breach, the Customer shall provide requested compliance evidence. SemaHub may conduct a proportionate audit, restrict traffic pending evidence and disclose required information to a competent authority.

10Data protection

10.1Each party shall comply with the Personal Data Protection Act, Chapter 44, its Regulations and other applicable privacy law. Each shall maintain required registration with the Personal Data Protection Commission and appoint a data protection officer where required.

10.2Schedule 1 applies where SemaHub processes Customer Data as processor. The Customer’s instructions must be lawful. SemaHub is not required to perform an instruction that it reasonably believes violates law and may suspend it while seeking clarification.

10.3The Customer shall not upload sensitive personal data or children’s data without SemaHub’s prior written approval, a documented lawful basis, enhanced controls and any necessary impact assessment.

11Fees, taxes and credits

11.1The Customer shall pay the prices shown in the applicable order, dashboard or price list. Prices exclude VAT and other taxes unless expressly stated. The Customer bears bank, mobile-money and currency-conversion charges.

11.2SMS is charged per segment, not necessarily per displayed Message. Standard GSM encoding typically permits 160 characters for a single segment and fewer characters per segment for concatenated or Unicode Messages. Emojis and certain characters may cause Unicode encoding and additional charges.

11.3Unless the applicable price plan states otherwise, credits are prepaid, non-transferable and not redeemable for cash. A Message accepted for routing may be chargeable even if it is later undelivered because of an invalid number, switched-off device, full inbox, carrier filtering, expiry, roaming or another condition outside SemaHub’s control.

11.4SemaHub may correct billing errors. The Customer must dispute an invoice or usage charge within 30 days, identifying the transaction and basis; undisputed amounts remain payable. Late amounts may lead to suspension and lawful collection costs.

12Availability, delivery and support

12.1Delivery depends on mobile networks, internet connectivity, devices, routing partners, content filters and recipient status. A delivery receipt reflects information provided by downstream systems and is not proof that a particular person read or acted on a Message.

12.2SemaHub may schedule maintenance and will use reasonable efforts to communicate planned material interruptions. Emergency maintenance may occur without advance notice. Service levels apply only if set out in a signed service-level agreement.

13Monitoring, filtering and regulatory cooperation

13.1To the extent permitted by law, SemaHub may use automated and manual measures to detect spam, fraud, abuse, anomalous traffic, prohibited content and security threats. Such measures do not create a duty to monitor every Message.

13.2SemaHub may block, quarantine, delay, limit or disclose Messages and related records where reasonably necessary to comply with law, an operator or Regulator instruction, protect recipients or networks, investigate complaints, prevent harm or enforce these Terms.

13.3Where legally permitted, SemaHub will notify the Customer of a disclosure request. SemaHub may preserve records subject to a legal hold and shall not be required to delete data that lawfully must be preserved.

14Suspension and termination

14.1SemaHub may immediately suspend some or all Service access where there is suspected fraud, unlawful content, absence of consent evidence, compromised credentials, payment default, excessive complaints, risk to a network or person, a regulator or carrier direction, or a material breach. Where the risk permits, SemaHub will state the reason and allow a reasonable opportunity to cure.

14.2Either party may terminate a recurring service on the notice stated in the order form, or 30 days if none is stated. Either party may terminate for a material breach not cured within 14 days after written notice, unless the breach is incapable of cure or requires immediate termination.

14.3On termination, access ends, unpaid charges become due, and Customer Data will be returned or deleted in accordance with Schedule 1, subject to legal retention and backup cycles. Clauses intended by their nature to survive shall survive, including fees, confidentiality, liability, indemnities, dispute resolution and lawful record retention.

15Intellectual property

15.1SemaHub and its licensors retain all rights in the platform, software, APIs, documentation, routing configuration, trademarks and improvements. The Customer receives a limited, non-exclusive, non-transferable right to use the Service during the agreement for its internal lawful business purposes.

15.2The Customer retains rights in Customer Data and grants SemaHub the limited rights necessary to host, process, transmit, secure and support it. The Customer warrants that it has authority to provide Customer Data and Message content for those purposes.

15.3The Customer shall not reverse engineer, copy, resell outside an authorised reseller agreement, interfere with, benchmark for publication without consent, or use the Service to build a competing service, except to the extent a restriction is prohibited by law.

16Confidentiality

16.1Each party shall protect the other party’s non-public business, technical and security information using at least reasonable care and use it only for the agreement. Confidentiality does not cover information lawfully public, already known without duty, independently developed or lawfully received from another source.

16.2A party may disclose confidential information where legally required, provided it gives advance notice when lawful and discloses only what is required. These obligations continue for five years after termination, and indefinitely for trade secrets and personal data to the extent required by law.

17Warranties and disclaimers

17.1Each party warrants that it will comply with Applicable Law and has authority to enter the agreement. SemaHub warrants that it will provide the Service with reasonable skill and care and maintain reasonable security measures.

17.2Except for express commitments, the Service is provided on an "as available" basis. To the fullest extent permitted by law, SemaHub disclaims implied warranties of uninterrupted availability, universal delivery, merchantability, fitness for a particular purpose and compatibility with every third-party system. Nothing excludes a warranty or consumer right that cannot lawfully be excluded.

18Customer indemnity and regulatory liability

18.1The Customer shall defend, indemnify and hold harmless SemaHub, its directors, officers, employees and lawful subcontractors from third-party claims, investigations, losses, damages, reasonable legal costs, compensation orders, operator charges and regulatory fines or penalties, to the extent arising from: (a) Customer Data, Message content or recipient selection; (b) absence, invalidity or inadequate evidence of consent or another lawful basis; (c) failure to honour an opt-out; (d) unlawful list acquisition, disclosure or cross-border transfer; (e) misuse of a Sender ID, brand or intellectual property; (f) the Customer’s sector-specific violation; (g) an Authorised User’s misuse; or (h) the Customer’s breach of these Terms or Applicable Law.

18.2The indemnity does not apply to the extent a claim, fine or damage resulted from SemaHub’s breach of law, breach of the Data Processing Addendum, gross negligence, wilful misconduct, unauthorised processing, failure to follow lawful Customer instructions or failure of controls that SemaHub expressly undertook to maintain.

18.3No clause transfers or removes a statutory obligation or regulatory liability that Applicable Law places directly on a party. If a Regulator imposes a fine directly on SemaHub because of Customer conduct, the Customer’s reimbursement obligation applies only to the extent legally recoverable and causally attributable to that conduct, after allowing the Customer reasonable participation in the response where legally permitted.

18.4The indemnified party shall notify the indemnifying party promptly, provide reasonable cooperation at the indemnifying party’s cost, and not settle a claim in a way that admits wrongdoing or imposes non-monetary obligations on the indemnifying party without consent, not to be unreasonably withheld. Delay in notice reduces liability only to the extent it materially prejudices the defence.

19Limitation of liability

19.1Nothing limits liability for fraud, wilful misconduct, gross negligence, death or personal injury caused by negligence, unlawful disclosure or misuse of personal data, breach of confidentiality, infringement of the other party’s intellectual property, unpaid fees, Customer indemnity obligations, or any liability that cannot lawfully be limited.

19.2Subject to clause 19.1, neither party is liable for indirect, consequential or special loss, or loss of profit, revenue, anticipated savings, goodwill or business opportunity, except where such loss forms part of a third-party claim covered by an indemnity.

19.3Subject to clause 19.1, each party’s aggregate liability arising in any rolling 12-month period shall not exceed the fees paid or payable by the Customer for the Service during that period. If the parties sign a corporate order or service-level agreement, they may agree a different cap appropriate to the risk and insurance available.

20Force majeure

Neither party is liable for delay or failure caused by events beyond its reasonable control, including widespread network failure, operator outage, internet disruption, natural disaster, war, civil disturbance, epidemic, government action or utility failure, provided the affected party takes reasonable steps to mitigate. Payment obligations already accrued are not excused.

21Notices

Legal notices must be sent to the addresses stated in the order form and to info@techcraft.co.tz. Operational notices may be given through the dashboard or registered account email. A party must keep its contact details current.

22Governing law and dispute resolution

22.1These Terms are governed by the laws of the United Republic of Tanzania.

22.2The parties shall first attempt in good faith to resolve a dispute through senior representatives within 30 days after written notice. If unresolved, the dispute shall be finally resolved by a single arbitrator under the Arbitration Act, 2020. The seat shall be Dar es Salaam, the language shall be English, and the arbitrator shall be agreed by the parties or appointed under the applicable statutory procedure.

22.3Either party may seek urgent interim or protective relief from a court of competent jurisdiction. Nothing prevents a data subject from exercising statutory complaint rights or either party from cooperating with a Regulator.

23General provisions

23.1The Customer may not assign the agreement without SemaHub’s prior written consent, not to be unreasonably withheld. SemaHub may assign it as part of a merger, reorganisation or sale of substantially all relevant business, subject to continued data-protection safeguards.

23.2The parties are independent contractors. No agency, partnership, employment or fiduciary relationship is created.

23.3A failure to enforce a right is not a waiver. If a provision is invalid, it shall be modified to the minimum extent necessary and the remainder remains effective. The agreement is the entire agreement on its subject and may be amended as provided in these Terms or by signed writing.

23.4SemaHub may update online Terms for legal, regulatory or service changes. Material changes will be notified reasonably in advance where practicable. If a material change substantially disadvantages the Customer, the Customer may terminate the affected recurring Service before it takes effect, subject to payment of accrued charges.

Schedule 1

Customer Data Processing Addendum

1Roles and instructions

1.1The Customer is controller and SemaHub is processor for Customer Personal Data described in this Schedule, unless the parties document a different role for a particular activity. Each party remains independently responsible for processing for which it determines purposes and means.

1.2SemaHub shall process Customer Personal Data only on documented lawful instructions in the agreement, order form, platform configuration and Customer support requests, unless processing is required by law. SemaHub shall inform the Customer of a conflicting instruction where legally permitted.

2Processing details

Subject matter
Description
Provision, security, support, billing and improvement of the contracted messaging Service.
Duration
Description
For the agreement term and the deletion or return period, subject to lawful retention.
Nature
Description
Collection, receipt, organisation, storage, retrieval, transmission, delivery reporting, restriction, deletion and support access.
Purpose
Description
To send Customer-directed Messages, manage recipients, report delivery, secure accounts, prevent abuse and support the Customer.
Data subjects
Description
Recipients, prospects, customers, employees, contractors, Authorised Users and persons appearing in support material.
Personal data
Description
Names where supplied, telephone numbers, contact attributes, consent and preference data, message content, sender IDs, delivery metadata, IP addresses and account identifiers.
Sensitive data
Description
Not intended. Permitted only with prior written approval, lawful basis, documented necessity and enhanced safeguards.
Frequency
Description
Continuous or as initiated by the Customer.
Return and deletion
Description
At termination or verified request, subject to legal holds, backup cycles and limited regulatory records.

3Processor obligations

  • Ensure persons authorised to process Customer Personal Data are bound by confidentiality and receive appropriate training.
  • Maintain the measures described in Schedule 3 and adapt them where risk materially changes.
  • Assist the Customer, taking into account the nature of processing, with data-subject requests, breach assessment, impact assessments and consultations with the Commission.
  • Maintain records necessary to demonstrate compliance and provide reasonable audit information.
  • Notify the Customer without undue delay of a confirmed breach affecting Customer Personal Data.
  • Delete or return Customer Personal Data at the end of service, unless retention is required by law.

4Subprocessors

4.1The Customer gives general authorisation for SemaHub to use subprocessors needed for hosting, communications routing, payment, monitoring and support. SemaHub shall maintain a current subprocessor list available on request from info@techcraft.co.tz and give reasonable notice of a new subprocessor that materially affects processing.

4.2The Customer may object on reasonable data-protection grounds within 10 business days. The parties will seek a practical solution; if none is available, either party may terminate the affected Service without penalty other than accrued charges. SemaHub remains responsible for imposing materially equivalent protection obligations on subprocessors.

5Cross-border processing

SemaHub shall not make or authorise a cross-border transfer of Customer Personal Data contrary to Tanzanian law. Where a transfer is necessary, the parties shall cooperate on the PDPC permit, assessment, consent, contractual safeguards and technical measures required for that transfer. The Customer shall disclose destination-country requirements arising from its own configuration or recipients.

6Security incidents

6.1SemaHub’s notice will include, as information becomes reasonably available: the nature of the incident; affected data and approximate scale; likely consequences; containment and remediation; and a contact for follow-up. Notification is not an admission of fault.

6.2The Customer shall notify SemaHub within 12 hours of discovering an incident involving the Customer account, credentials, integration or data that could affect the Service, recipients or regulatory reporting. The parties shall coordinate communications and preserve evidence, but each retains its own legal notification duties.

7Audit

No more than once annually, unless a breach, Regulator or material compliance concern justifies more, the Customer may request relevant policies, certifications, summaries or a remote audit. An onsite audit requires reasonable notice, confidentiality, minimal disruption and reimbursement of SemaHub’s reasonable costs unless it reveals a material SemaHub breach. Audits shall not expose another customer’s data or compromise security.

Schedule 2

Acceptable Use and Messaging Compliance Rules

1Mandatory campaign controls

Lawful purpose
Customer requirement
Document the purpose and applicable lawful ground before transmission.
Consent evidence
Customer requirement
Retain who, when, how, what wording and which sender or purpose was authorised.
Sender identification
Customer requirement
Use an approved Sender ID and identify the sender and purpose clearly.
Opt-out
Customer requirement
Provide an accessible withdrawal route and maintain a suppression list.
List hygiene
Customer requirement
Remove invalid, duplicate, opted-out and unlawfully sourced contacts.
Timing
Customer requirement
Send non-urgent marketing only during reasonable daytime hours and comply with applicable quiet-hour directions.
Content approval
Customer requirement
Apply internal review for regulated, sensitive, financial, political or high-volume campaigns.
Complaint handling
Customer requirement
Maintain a contact point, investigate promptly and provide evidence to SemaHub when requested.
Data minimisation
Customer requirement
Upload only the fields necessary for the campaign and avoid sensitive data in message text.
Testing
Customer requirement
Test templates, links, segmentation, opt-out and encoding before a large send.

2Prohibited uses

The Customer must not use or permit the Service for:

  • unsolicited marketing, spam or repeated contact after withdrawal;
  • fraud, phishing, impersonation, social engineering, account takeover or deceptive collection of credentials;
  • false, misleading or unsubstantiated claims, pyramid schemes, unlawful investment or lending promotions;
  • malware, harmful links, evasion of security controls or interference with networks;
  • harassment, threats, extortion, incitement to violence, unlawful discrimination or hate content;
  • obscene, exploitative, sexually abusive or child-endangering material;
  • unlawful gambling, controlled goods, contraband or criminal activity;
  • political, electoral or public-order communications without documented legal and regulatory approval;
  • misuse of emergency, government, bank, operator or public-service identities;
  • traffic pumping, artificial message generation, route manipulation or bypass of rate, content or sender-ID controls;
  • infringement of privacy, confidentiality, intellectual property or other rights; or
  • any use prohibited by TCRA, the PDPC, a mobile operator, WhatsApp or another destination-channel provider.

3High-risk use cases

The following require prior written disclosure to and approval by SemaHub: banking or mobile-money alerts; OTP at material scale; health information; children’s data; debt collection; gambling; political or electoral messaging; emergency alerts; international traffic; financial promotions; and unusually high-volume campaigns. Approval may be conditional and does not replace the Customer’s legal review.

4Enforcement

SemaHub may warn, rate-limit, block, suspend, terminate, preserve evidence, refuse refunds for prohibited traffic, notify an upstream provider or Regulator, and recover reasonable investigation and remediation costs. Enforcement will be proportionate to urgency, harm, recurrence, evidence and legal obligations.

Schedule 3

Security and Incident Management Commitments

Minimum commitments

Governance
Minimum commitment
Assigned security and privacy responsibility, policies, risk reviews and staff confidentiality.
Identity and access
Minimum commitment
Least privilege, privileged-access MFA, access reviews, strong authentication and prompt revocation.
Application security
Minimum commitment
Secure development practices, code review, dependency management, change control and testing.
Infrastructure
Minimum commitment
Hardened configurations, segmentation where appropriate, patching, protected administrative interfaces and capacity monitoring.
Data protection
Minimum commitment
Encryption in transit, controlled secrets, data minimisation, retention controls and protected backups.
Logging and detection
Minimum commitment
Authentication, administrative and messaging-event logs; anomaly monitoring; time synchronisation; protected audit trails.
Vulnerability management
Minimum commitment
Regular scanning, risk-based remediation and penetration testing appropriate to service maturity and exposure.
Availability
Minimum commitment
Backups, restoration tests, redundancy appropriate to contracted service and documented recovery procedures.
Suppliers
Minimum commitment
Risk-based due diligence, written obligations and periodic review of critical subprocessors and routes.
Incident response
Minimum commitment
Documented triage, containment, investigation, evidence preservation, communication, recovery and lessons learned.
Business continuity
Minimum commitment
Critical dependency mapping, escalation contacts and periodic continuity exercises.
Secure disposal
Minimum commitment
Deletion or irreversible sanitisation of data and media when no longer required.

Incident severity and response targets

Critical
Example
Active compromise, large-scale disclosure, fraudulent mass messaging or material service-wide outage
Initial internal response target
Immediately and within 30 minutes
High
Example
Confirmed unauthorised access, significant abuse or major degradation
Initial internal response target
Within 1 hour
Medium
Example
Contained vulnerability or limited operational incident
Initial internal response target
Within 4 business hours
Low
Example
Minor issue with no confirmed data or service impact
Initial internal response target
Within 1 business day

These are internal response targets, not guaranteed restoration times. Contractual service levels must be stated in a signed service-level agreement.

Schedule 4

Customer Compliance Declaration

Declaration

The undersigned confirms on behalf of the Customer that, before using production messaging services, the Customer has implemented and will maintain the following:

  • a documented lawful purpose and lawful basis for every messaging use case;
  • valid and retrievable consent evidence for direct marketing where required;
  • a privacy notice covering collection, messaging, recipients and processors;
  • a functional opt-out method and controlled suppression list;
  • approved and non-misleading Sender IDs supported by genuine documents;
  • internal review and approval of message templates and recipient lists;
  • security controls for accounts, API keys, integrations and Authorised Users;
  • a process to notify SemaHub promptly of complaints, investigations and incidents;
  • records sufficient to demonstrate compliance to SemaHub and regulators; and
  • authority to accept the Terms and the Customer indemnity obligations.
Annex

Legal and regulatory references

Framework

This document was prepared by reference to the following framework current at September 2026. The official text and later amendments prevail:

  • Constitution of the United Republic of Tanzania, 1977, including the right to privacy under Article 16.
  • Personal Data Protection Act, Chapter 44, originally Act No. 11 of 2022 and in force from 1 May 2023.
  • Personal Data Protection (Personal Data Collection and Processing) Regulations, 2023, Government Notice No. 449C.
  • Personal Data Protection (Complaints Settlement Procedures) Regulations, 2023.
  • Electronic and Postal Communications Act, Chapter 306.
  • Electronic and Postal Communications (Consumer Protection) Regulations, 2018.
  • Electronic and Postal Communications (Value Added Services) Regulations, 2018.
  • Electronic and Postal Communications (Tele-Traffic) Regulations and the 2023 amendments concerning SMS traffic and sender identities.
  • Electronic Transactions Act, 2015 and Cybercrimes Act, 2015, where applicable.
  • Current TCRA directions, mobile-network sender-ID requirements and destination-channel policies.

Key statutory risk summary

Failure to register
Relevant statutory consequence
Collection or processing without PDPC registration is prohibited and may attract the general statutory penalty.
Administrative non-compliance
Relevant statutory consequence
PDPC may issue enforcement and penalty notices; the Act provides an administrative fine up to TZS 100 million.
Unlawful disclosure by a company
Relevant statutory consequence
The Act provides a corporate criminal fine from TZS 1 million up to TZS 5 billion.
Unlawful disclosure by an individual
Relevant statutory consequence
The Act provides a fine from TZS 100,000 up to TZS 20 million, imprisonment up to ten years, or both.
Unlawful destruction, deletion, concealment or alteration
Relevant statutory consequence
The Act provides a fine from TZS 100,000 up to TZS 10 million, imprisonment up to five years, or both.
Compensation
Relevant statutory consequence
A data subject may be entitled to compensation, and PDPC may order compensation in addition to a penalty.
Corporate officers
Relevant statutory consequence
An officer who knowingly and wilfully authorises or permits a corporate offence may also be liable.
Unsolicited marketing
Relevant statutory consequence
TCRA consumer-protection rules require customer consent and proper identification for SMS marketing; carrier and regulatory sanctions may also apply.

Questions about these terms?

Contact our Data Protection Officer for privacy questions, data-subject requests or complaints.