Terms of service

Miqra is provided by Pypapi Technologies Limited together with SonsHub Media. In these terms, "we" means those operators.

A "church" is the tenant organisation that pays (or trials) Miqra. A "user" is a person the church invited, or a member who signed in.

The person who registers a church is responsible for naming a controller contact, keeping admin users accurate, and paying the catalog price for the plan and add-ons they select.

Users must give a working email, keep passwords private, and tell us if a session is stolen. We may lock an account that looks compromised.

Churches decide which modules to switch on. Authentication, membership, and branches are always on. Other modules need a subscription or add-on from the live catalog.

Miqra stores church operations data: people, attendance, giving, sermons, messages, sites, and the other modules listed on the product page. It is not legal, pastoral, or financial advice.

Offline features queue work on the device and sync when the network returns. A queue is not a guarantee that every offline row will survive a wiped device.

Public church sites (a Miqra subdomain under usemiqra.app, and custom domains) show what the church publishes. The church is responsible for that content.

SaaS fees are in naira, billed through Paystack, using the live catalog amounts (kobo on the wire). Annual billing is the catalog's annual figure, not a made-up discount.

Trials last the number of days the catalog states. If a church does not subscribe, access to paid modules stops after the trial and any grace period.

Member tithes and offerings are the church's money. Miqra Pay may take a platform split at the processor. A church that uses its own gateway keys stays responsible for that Paystack (or other) account.

Refunds of SaaS fees follow the invoice and Paystack's outcome. We do not hold church offering float.

Users must follow the Acceptable use page: no abuse of other people's data, no spam, no illegal content, no attempts to read another tenant.

We may suspend a tenant or user that breaks these terms after we can reasonably show the breach. Pastoral emergencies at a church are the church's to handle; suspending SaaS access is a last step, not a ministry decision.

The Privacy policy and Data Processing Addendum apply. The church is controller of its member records. We are processor for that set, and controller for platform accounts.

You grant us a limited licence to host and display content you upload, only to run Miqra for that church.

Miqra, the M/Q mark, and the product code remain ours. Churches keep the sermons, photos, and text they upload.

Scripture text displayed by the AI Bible Presentation module remains under the licence of that translation. The module does not give the church a new publishing licence.

We aim to keep the service up, especially around Sunday peaks. We do not promise unbroken uptime.

To the extent Nigerian law allows, we are not liable for lost offerings, missed attendance counts, or ministry outcomes. Our liability for SaaS fees in a claim is capped at the fees the church paid us in the three months before the claim.

Nothing here limits liability for fraud or for death or personal injury caused by negligence where the law forbids that limit.

A church can cancel at period end in billing settings. A trial cancel can take effect immediately, as the product already does.

We can end the contract if invoices stay unpaid past grace, or if use is unlawful.

On exit, the church should export what it needs. After the retention described in Privacy, we delete tenant data we no longer have a legal reason to keep.

These terms are governed by the laws of the Federal Republic of Nigeria. Disputes start with a written notice to the published mailbox. Write to contact@usemiqra.app.