Compliance & Disclaimers
Last updated: 28 September 2026
Azly builds software that touches regulated areas: tax invoicing in Kenya, payment collection, and electronic messaging. This page states clearly where our responsibility ends and yours begins.
1. eTIMS and tax compliance
Our eTIMS Compliance module assists with transmitting invoice data to the Kenya Revenue Authority's electronic Tax Invoice Management System, as required under the VAT Act 2013 (as amended), the VAT (Electronic Tax Invoice) Regulations 2020, and the Tax Procedures Act 2015. The module helps you meet your obligations; it does not assume them. Specifically:
- The legal obligation to issue compliant electronic tax invoices rests with the seller (taxpayer), not with Azly.
- Registration for eTIMS, the accuracy of transaction data, VAT calculations, and timely filing remain the taxpayer's responsibility.
- Only KRA can determine the validity of an invoice. A module cannot and does not guarantee acceptance of any particular invoice.
- The module is not a substitute for advice from a qualified tax adviser or accountant.
Where the module fails to transmit a compliant invoice due to a defect on our side, our responsibility is limited to fixing the defect and refunding fees as set out in the Refund Policy, and, where applicable, re-transmitting the affected invoices.
2. Payment gateways: integrator, not processor
Azly is a software integrator. We are not a payment processor, a payment institution, an acquirer, or an agent of any payment scheme. All payment processing performed in connection with our modules is carried out by the payment providers themselves: Paystack, Flutterwave, and the M-Pesa services operated by Safaricom, each under their own terms with the merchant. In particular:
- Azly never holds, receives, or settles customer funds.
- Card and mobile-money credentials are handled by the gateways' own secure flows, never by our software.
- Settlement times, disputes, chargebacks, refunds of gateway fees, and compliance with payment scheme rules are governed by the gateway's agreement with the merchant.
- Where a module records or reconciles payment data, it does so as a data processor for the merchant, per our Privacy Policy and DPA.
3. Messaging compliance
WhatsApp, SMS, and other messaging features operate through provider APIs (including the WhatsApp Business API) and are subject to each provider's policies and to communications law in the recipient's jurisdiction. The business sending messages is responsible for holding lawful opt-in consent and honoring opt-outs. Our modules provide the controls; using them lawfully is the operator's responsibility.
4. Marketplace relationships
Azly modules for GoHighLevel, HubSpot, monday.com, Pipedrive, and Shopify are developed and supported by Azly as an independent developer. The platforms are not involved in the development of the modules and do not endorse them beyond their standard marketplace review processes. Each platform's own terms continue to govern your use of the platform.
5. No professional advice
Nothing on this website, in our module listings, or in our documentation constitutes legal, tax, accounting, or regulatory advice. Content on this site, including blog posts, is general technical information. For advice on your obligations under Kenyan tax law, data protection law, or the law of any other jurisdiction, consult a qualified professional.
6. Contact
Compliance questions: hello@azly.io.