Your data, handled with care.

HeyPew gives churches NFC tap tags, QR codes and simple web pages. This policy explains what personal data we collect, why, and the choices you have. We follow the Nigeria Data Protection Act 2023 (NDPA).

Last updated 17 November 2026

Who we are

“HeyPew”, “we” and “us” mean the team that runs the HeyPew service. To ask about this policy or your data, email us at hello@heypew.church.

For church administrators and people who ask us for a demo or an order, we decide how your data is used (we are the data controller).

For a church's own content and its guests, the church is responsible for what it publishes on its pages and for the details visitors send it through a connect card. We host these on the church's behalf (we are its data processor).

What we collect

When you request a demo, order tags or send us a message: your church's name, your name and role, phone number, your email (needed for a message, optional for a demo or an order), your message, and optionally your city, congregation size and the products, quantity and plan you're interested in.

When we create an account for you: your email address, your password (stored only in scrambled, hashed form, which no one can read), when you last signed in, and which church you manage.

What churches put on their pages: page titles, links, logos, cover photos and colours, and the bank account details a church chooses to show for giving. We count how often an account's details are copied, never who copied them or any amount given by bank transfer.

When someone gives online to a church: where a church takes gifts online, the giver's email address, their name if they choose to give it, the amount, the giving it was for, how it was paid (card, transfer or USSD) and when. The church's owner can see these. Card and bank details are entered on Paystack's page: we never see or store them.

When a visitor fills in a church's connect card: their name, phone number, their email address if they choose to give it, whether it's their first visit, and a prayer request if they choose to write one. This goes to that church's team, who may add a follow-up note. A church team member who asks for follow-up reminders gives us a phone number to send them to.

When someone taps a tag or opens a church page: the time, which tag or page, the type of device (phone, tablet or computer), the country, and how they arrived (NFC tap, QR scan or link). We do not store visitors' IP addresses or names, and we don't use tracking cookies on church pages. Visits from link-preview bots, such as WhatsApp's, aren't counted.

When a form is sent: to stop one connection flooding a form, we keep a scrambled code made from its IP address for up to a day. The code can't be turned back into the address.

On our own website and sign-in pages: which pages are viewed, from which country, and on what kind of device, counted without cookies. Church pages aren't included.

How we use it

  • To reply to your demo or order request, by phone, WhatsApp or email. This is necessary to take the steps you asked for.
  • To create and run your church's account, sign you in, and keep it secure. This is necessary to provide the service you signed up for.
  • To show churches how many people connected, and how, in their dashboard. This is in the church's legitimate interest and uses no personal data about visitors.
  • To pass a visitor's connect card to the church they sent it to, so its team can follow up. If the church has switched welcome messages on, we send the visitor one welcome message on its behalf, by WhatsApp or SMS, and by email if they gave an address, and we send reminders to the team members who asked for them.
  • To protect the service from abuse, for example by limiting how often one connection can request pages.

We don't sell personal data, and we don't use it for advertising.

Cookies

Church pages and our website don't use advertising or tracking cookies. When an administrator signs in, we use a cookie to keep them signed in. It's needed for the dashboard to work and is removed when they sign out.

Who we share it with

We use a small number of trusted providers to run HeyPew. They process data only on our instructions:

  • Supabase: our database, sign-in and file storage, hosted in London, United Kingdom.
  • Vercel: hosts our website and pages. Our servers run in London, and pages are delivered through its global network. Like most hosts, Vercel briefly processes visitors' IP addresses to deliver pages and block attacks. Vercel also counts page views on our own website, without cookies.
  • Meta (WhatsApp Business Platform): delivers welcome messages and team reminders on WhatsApp. It receives the phone number, the person's first name and the church's name.
  • Termii: delivers the same messages by SMS when WhatsApp can't. It receives the phone number and the message.
  • Paystack: takes card payments for plans and charges renewals. It receives the church owner's email address and the card details they enter on Paystack's own page, which we never see or store. We keep the amount, date and status of each payment. Paystack also takes online gifts to churches and pays them into the church's own bank account: it receives the giver's email address and the payment details they enter, and the bank account the church asks to be paid into.
  • Resend: sends our emails, such as sign-in links and welcome emails to visitors who gave an email address, and tells our team when a request or message arrives. Its servers are in Ireland.
  • Cloudflare: counts page views on our own website, without cookies and without storing IP addresses.

Because most of these providers are outside Nigeria, your data is transferred abroad. We only use providers with strong security and contractual data protection commitments, as the NDPA requires. We may also share data if the law requires it.

How long we keep it

  • Demo and order requests, and messages: for as long as we need them to serve your church, then deleted. Ask us and we'll delete them sooner.
  • Accounts and church pages: for as long as the church uses HeyPew. When a church leaves, we delete its account, pages, tags and visit records on request.
  • Connect cards: until the church deletes them or leaves HeyPew. To have yours removed, ask the church, or ask us and we'll pass it on.
  • Visit records: shown in the dashboard for the period the church's plan includes.

Keeping it safe

All traffic to HeyPew is encrypted (HTTPS). Passwords are hashed, sign-in links work only once and expire, and each church's data is kept separate at the database level, so administrators only ever see their own church. Access to our systems is limited to the people who need it.

Your rights

Under the NDPA you can ask us to:

  • tell you what personal data we hold about you, and give you a copy
  • correct anything that's wrong
  • delete your data
  • stop or limit how we use it, or object to a use
  • move your data to another service

To use any of these rights, email us at hello@heypew.church. We'll reply within 30 days. If a request is about a church's page, we may pass it to that church, since it controls that content.

If you're unhappy with how we've handled your data, you can complain to the Nigeria Data Protection Commission.

Children

HeyPew accounts are for adults acting for their church. We don't knowingly collect personal data from children. Church pages can be visited by anyone, and we don't collect personal data from visitors.

Changes to this policy

If we change how we use personal data, we'll update this page and the date at the top, and tell church administrators about significant changes. See also our terms of service.