Privacy Policy

Converza ("Converza", "we", "us") provides a platform that sits above a business's WhatsApp channel and turns the conversations that happen there into a customer record, a sales pipeline, campaigns, automations and payments.

This policy covers the Converza website, the application at your workspace, and the interfaces that connect them to WhatsApp, payment providers and contact services.

Two relationships run in parallel and it matters which one you are in. When you sign up, create a workspace and use the product, we decide how your account data is handled and this policy governs that directly. When you load your customers into a workspace and message them, you decide what happens to that data and we act on your instructions. In the language of most data protection law, we are the controller of your account data and the processor of your customer data.

Creating and running a workspace involves a small amount of information about you:

• Identity: your name, email address and, if you add one, a phone number, job title and profile photo.
• Workspace: the business name, category, address, website, business hours and time zone you enter.
• Team: the members you invite, the role you give each one, and which team they belong to.
• Preferences: your language, time zone and notification settings.
• Correspondence: what you write to us when you ask for support.

Your password is never one of these. Authentication is handled by our identity provider, which holds your credentials. Converza receives only a verified identifier for the signed-in user.

The substance of a workspace is the record of your customers. Depending on which features you use, that includes:

• Contacts: phone number, name, email if given, source, tags, location, birthday, lifetime value and opt-out status.
• Messages: the inbound and outbound messages that pass through your connected WhatsApp channel, with timestamps and delivery state.
• Deals: product or service, value in naira, stage, owner, and the history of stage changes.
• Submissions: the answers people give on your landing pages, forms, lead magnets and QR codes.
• Bookings: session, service, client, time, duration and status.
• Payments: amount, reference, method and status of payments made through links you create.
• Automation runs: which contact entered which flow, where they reached, and where the run stopped.

This data belongs to you. We hold it to operate the features you turned on, and for no other purpose. We do not sell it, we do not share it with advertisers, and we never use one workspace’s customers to market to another.

Running a service produces some data whether or not anyone types it in:

• Technical: IP address, browser and device type, and the pages requested, kept in server logs.
• Product analytics: which pages are viewed and how the application performs, used to find slow screens and broken flows.
• Security: rate limiting counters on public endpoints, so a form cannot be flooded.

We do not use advertising cookies and we do not run third party trackers for advertising purposes.

We rely on four grounds, depending on what the data is for:

• Performance of a contract: everything needed to give you the service you signed up for, including running your workspace, sending what you asked to send, and taking payment for your plan.
• Legitimate interests: keeping the service secure, preventing abuse, understanding how the product performs, and communicating about the service you use. We weigh these against your interests and do not rely on them where they would override your rights.
• Consent: optional integrations such as Google Contacts sync, which do nothing until you connect them and stop when you disconnect.
• Legal obligation: keeping financial records where the law requires it.

Where you are the one deciding, as with the customers you message, the lawful basis for contacting them is yours to establish. See the section on your responsibilities.

When you connect a WhatsApp number, Converza stores the messages that pass through it. That is what makes the product work: a contact cannot be saved automatically without seeing the message that arrived, and a campaign cannot be measured without knowing who replied.

Two routes exist. You can link the number you already use by scanning a QR code, in which case the connection runs through a service we operate on your behalf. Or you can connect an official WhatsApp Business account, in which case messages flow through the provider’s interface directly.

Either way, message content is stored in your workspace and is subject to the same isolation as every other row. WhatsApp itself is operated by Meta under its own terms, and your use of the channel is also governed by those.

Payments are processed by Monnify. When you create a payment link for a customer, we send Monnify the amount, a reference we generate, and the customer’s name and email so it can present a checkout.

Card numbers never reach Converza. We do not see them, store them, or have any way to retrieve them. What comes back to us is confirmation that a payment succeeded, its amount, its reference and its method.

The same applies to your own plan payments. We record what was paid, for which plan and when, which is what the invoices in your billing screen are built from.

Converza is assembled from services that each hold one part of the picture, and each receives only what its job requires:

• Application hosting and analytics, which see requests and performance data.
• A managed Postgres database, which holds your workspace rows.
• An identity provider, which holds your sign-in credentials and never gives them to us.
• WhatsApp, for sending and receiving messages on your channel.
• Monnify, for payments, which sees an amount and a customer email but never your chat history.
• Google Contacts, only if you switch that sync on, which receives the contact cards you choose to push.

We use these providers to run the service, not to enrich anybody’s data set. None of them is permitted to use your data for their own marketing.

Converza runs on infrastructure that may process and store data outside Nigeria, including in Europe and the United States. Moving data across borders is normal for cloud software and is how the service is delivered to you at speed.

Where a transfer leaves a jurisdiction whose law restricts it, we rely on the transfer mechanisms our providers put in place, such as standard contractual clauses.

The most important protection is structural rather than procedural. Every table in the database enforces row level security, which means a request scoped to one workspace cannot read another workspace’s rows even if the application asked it to. Isolation does not depend on the application remembering to filter.

Beyond that:

• Traffic is encrypted in transit, and data is encrypted at rest by our database provider.
• Access inside a workspace follows the role you assigned: owner, admin, agent or viewer.
• Every inbound webhook is signature checked before anything is written, and an endpoint with no signing secret configured refuses the request rather than trusting it.
• Public endpoints are rate limited.
• A small number of our engineers can reach production data to keep the service running. That access is limited to what an incident requires.

No system is beyond compromise, and we will not claim otherwise. If a breach affects your data, we will tell you and the relevant authority as the law requires.

Your workspace data stays for as long as the workspace exists. Deleting a workspace deletes the contacts, messages, deals, forms, submissions, automations, bookings and invoices attached to it.

Removing a member from a workspace ends their access immediately and keeps a record of the membership so the history of who did what remains readable.

Server logs are kept for a short operational period. Financial records are kept for as long as tax and accounting law requires, which is longer than the rest.

Depending on where you live, you have some or all of the following rights over data we hold about you:

• Access: a copy of what we hold.
• Correction: to fix anything inaccurate.
• Deletion: to have it removed, subject to records we must keep by law.
• Portability: to receive it in a form you can take elsewhere.
• Objection and restriction: to object to processing based on legitimate interests, or to ask us to pause it.
• Withdrawal of consent: for anything you consented to, at any time, without affecting what happened before.

Much of this you can exercise yourself inside the product: edit or delete any contact, export your analytics, or delete the workspace outright.

For anything the product does not let you do, write to privacy@converza.site. We answer within thirty days. If you are unhappy with our answer you may complain to your data protection authority, which in Nigeria is the Nigeria Data Protection Commission.

When you message people through Converza, you are the one deciding to contact them, and the obligation to have a lawful basis for that is yours.

In practice that means:

• Having permission, or another lawful basis, to message the numbers in your workspace.
• Telling those people who you are and what you will use their information for.
• Honouring an opt-out promptly. Converza records opt-outs and excludes those contacts from campaigns, but the obligation to respect the request is yours.
• Answering requests those people make about their own data. We will help you where the product cannot.

Converza is a business tool and is not directed at children. We do not knowingly collect data from anyone under sixteen. If you believe a child’s data has reached us, tell us and we will remove it.

If this policy changes in a way that affects what we do with your data, we will tell you rather than quietly amend the page. The date at the top always reflects the current version.

Questions about this policy, or a request about your data, go to privacy@converza.site. For anything else, hello@converza.site reaches us.

Converza, Lagos, Nigeria.