Privacy Policy

For an operator's own account data (their staff's names, phone numbers, and payout details), Nantepa is the controller: we decide how and why that data is used, as described in this policy.

For a customer's booking data, a customer gives their own name and phone number directly to Nantepa at checkout. We don't collect it on an operator's instruction the way some marketplace platforms do. We act as controller for that data too, and share what's needed (the booker's name, phone number, and seat) with the specific operator whose experience was booked, so they can run that experience and identify their own passengers.

For any additional information an operator configures to collect from a customer at booking (for example dietary needs, an emergency contact, or a session/committee choice), the operator is the controller: they decide what's asked for and why. Nantepa acts as a processor for that data: we store and process it on the operator's instructions, and secure it as described in Section 8, but we don't decide what's collected and don't review the content of an operator's questions. See our Terms of Service, Section 9, for the operator's obligations around this.

For promotional messages, the operator decides who is messaged and what is said, and is the controller of the contact lists it chooses to import. Nantepa acts as a processor for that: we deliver the messages and keep the records of who agreed and who opted out, on the operator's behalf. For the consent and opt-out records themselves, and for the sign-in and account data in this section, Nantepa is the controller.

We only collect what the Service needs to work. We do not collect IP addresses, browser or device information, or advertising identifiers on our own servers.

From operators and staff: name, phone number, email address, role (business admin or staff), and payout details (bank/Mobile Money account and the resolved account holder name, used to connect a Paystack subaccount). Account sign-in itself (including any password) is handled entirely by Supabase Auth. Nantepa's own systems never see or store a password.

From customers: the name and phone number given at booking, used to identify the booking, send confirmations, and let the operator recognise a participant. Booking doesn't require creating an account or a password.

From an operator's own configured questions: whatever a customer answers to any additional field an operator adds at booking. The operator chooses the content of these fields, not Nantepa (see Section 1).

About messaging: whether you agreed to promotional messages from a particular business, how (at checkout, through an opt-in link, or an operator's imported list), when, and which wording you saw; any opt-out you make; and, if you sign up through a business's opt-in link, the phone number or email you give, which stays unconfirmed and is not used for promotions until you confirm it. If an operator imports a contact list, the names and phone numbers or emails in it.

About agreeing to our terms: the version of the Terms of Service you accepted at checkout and the time you accepted it, stored against your booking or registration.

About an operator's account with us: its message-credit history and any amount it owes Nantepa, with the reason for each item.

From Paystack, at payment: confirmation of success or failure and a transaction reference. We never see or store your Mobile Money PIN or full card details.

Automatically, via Google Analytics, using cookies: basic usage analytics, including pages visited, approximate location derived from IP address, and general device/browser information, to understand how the site is used. This is the only tracking or analytics service we use, and it involves data leaving Ghana to Google's own infrastructure (see Section 7).

The only cookies we use are set by Google Analytics (Section 2 and Section 6), to understand how the Service is used. We don't set any cookies of our own; your sign-in session is stored in your browser's local storage, not a cookie. If you'd rather not be tracked by Google Analytics, you can block it using your browser's cookie settings or a Google Analytics opt-out extension; this won't stop you from using Nantepa.

To create and manage accounts, process bookings, payments, and payouts, send SMS confirmations, and provide support.

To send promotional messages only where you agreed to them, to keep proof of that agreement, and to make sure we never message someone who has opted out.

To show that you accepted our Terms, and to manage what an operator owes us.

To detect and prevent fraud, abuse, or double-booking.

To improve the product, using aggregated, non-identifying usage data from Google Analytics.

SMS is delivered through mNotify, a Ghana-based provider, which receives the recipient's phone number and the text of each message in order to deliver it. Email is delivered through Resend, which receives the recipient's email address and the message. Delivery is not guaranteed. A failed message is logged internally but not automatically retried.

Service messages relate to something you already hold or to your account: a booking confirmation, a cancellation, a change to the experience, a deferred-payment reminder, or, for operators, a notice about their account or what they owe. You don't need to opt in to these, and they are not stopped by opting out of promotions.

Promotional messages are sent only if you agreed to receive them from that business. You can agree by ticking the optional box at checkout or by signing up through a business's opt-in link and confirming it. A business that imports its own contact list must confirm that it holds a valid consent for every contact in it. Every promotional message includes a link to stop further promotional messages from that business. Opening it takes one step, and Nantepa then keeps your opt-out and does not send you promotions from that business again, unless you later opt back in yourself. You can also withdraw consent by emailing us (Section 14).

We rely on a small number of service providers ("sub-processors") to run Nantepa. They may only use data to provide their service to us.

Supabase: database and authentication, including login credentials. Hosted in Frankfurt, Germany (AWS eu-central-1).

Render: hosts our backend application. Region to be confirmed and published here.

Vercel: hosts our frontend application.

mNotify (Ghana): SMS delivery.

Resend: email delivery: account and business notices, opt-in confirmations, and emails an operator sends to customers who agreed to them.

Paystack (Ghana): payments. Processes the payment amount and Mobile Money details directly, and reports success or failure to us. Where an operator offers no refunds, Paystack's split-payment feature settles that operator's share directly into their own account at the time of payment. Paystack also processes an operator's purchase of message credits and its payment of any amount it owes Nantepa. For every other operator, Paystack instead settles the full fare into Nantepa's own balance, and the operator's share is paid out separately by Paystack Transfer once the booking is no longer refundable. See our Terms of Service, Section 5, for what that means for how your money is held in the meantime.

Google Analytics: usage analytics, as described in Section 2 and Section 3. Unlike the providers above, this one is not scoped to only what a specific booking or account needs.

We do not sell personal data, and we do not use it for advertising.

Our database and authentication are hosted by Supabase in Frankfurt, Germany. Our backend runs on Render and our frontend on Vercel, each of which may process traffic through infrastructure outside Ghana. Some personal data is therefore stored or transferred outside Ghana. We take reasonable steps to ensure such transfers comply with the Data Protection Act, 2012 (Act 843), and will disclose the specific countries involved as part of our registration with the Data Protection Commission once complete.

Google Analytics data is processed by Google's own global infrastructure under Google's terms, separately from the providers above.

Phone numbers, email addresses, and names are encrypted at the application level before they are stored. To check whether someone agreed to messages, or opted out, without reading their contact details, we also store a one-way keyed code (a hash) of the phone number or email, which cannot be turned back into the original. This is in addition to Supabase's own storage-level protections (encryption at rest, and TLS while data travels between your device and our servers).

Information collected through an operator's own configured questions (Section 2) gets that same application-level encryption too, since it can include sensitive personal data depending on what an operator chooses to ask for.

Access to an operator's data is restricted to that operator's own staff, enforced at the application level. Platform staff cannot browse another operator's customer details.

No system can be guaranteed completely secure. If we discover that personal data has been accessed or taken without authorisation, we will notify the Data Protection Commission and the affected people as soon as we reasonably can, as required by Act 843.

Deleting your own account doesn't erase it immediately: it's recoverable for 14 days (sign back in to undo it), after which it's permanently erased or anonymised in an automatic daily sweep.

An operator deleting their business is different: it's immediate and cannot be undone through the Service. The business disappears from public booking straight away, though its experience and booking records aren't automatically purged, since they're needed for accounting, tax, and dispute-resolution purposes. Contact us to request permanent erasure of a closed business's records sooner than our normal retention period, or to reopen an account closed by mistake.

Records of consent, opt-outs, and which Terms version was accepted are kept for as long as we may need to prove that you agreed or to make sure we honour your opt-out. An opt-out is kept so that we don't message you again, even if you ask us to erase your other data. Unconfirmed opt-in sign-ups that are never confirmed are not used for messaging.

How to request erasure. Email us at the address in Section 14. Erasure requests are handled manually by our team: we verify the request, then permanently anonymise the relevant record. This is not an instant, automated process, and once completed it cannot be undone.

Under Ghana's Data Protection Act, 2012 (Act 843), you have the right to:

Be told what personal data we hold about you and get a copy of it

Ask us to correct inaccurate or incomplete data

Ask us to permanently erase your data, subject to the retention needs in Section 9

Give or withdraw your consent to processing, and object to processing in certain cases. For promotional messages, you can withdraw at any time using the link in any message, with no reason needed

Not be subject to a decision based solely on automated processing (we do not currently make such decisions)

Seek compensation where we have failed to comply with the Act and you have suffered as a result

Complain to the Data Protection Commission of Ghana if you believe we have mishandled your data

To exercise any of these, reach us at the email in Section 14. If you're a customer and the request relates to a specific booking, it's usually fastest to contact the operator directly, since they can see and act on their own experience's bookings, but you're welcome to come to us either way. For data collected through an operator's own configured questions (Section 1), the operator is the controller; contact them first. We'll still act on a request that reaches us instead, by relaying it to the relevant operator or acting on their instruction.

An operator can generate and download a copy of their own business data (experiences, bookings, customers, and revenue) at any time from their dashboard. This currently does not include a customer's answers to the operator's own configured questions (Section 2); contact us at the email in Section 14 to request these directly while we build them into this export.

Nantepa requires the person making a booking to be 18 or older (see the Terms of Service). This doesn't mean a minor can't take part as a participant, only that an adult must be the one who completes the booking on their behalf. We do not knowingly collect personal data directly from a child through any means other than appearing as a participant's name on a booking an adult made for them.

We may update this policy as the Service changes. If we make a significant change, we will update the "Last updated" date above and, where appropriate, notify affected users.

Questions or requests about this policy? Email us at tech@nantepa.com.