Privacy Policy
Effective date: [to be set at launch]
Draft for founder review before launch. Items marked [confirm] need a decision or a detail (company name, contact addresses, retention periods). This draft is not legal advice — have it checked against the Nigeria Data Protection Act 2023 and current NDPC guidance before going live.
Errandly is a campus errand and delivery platform. Students (“buyers”) post errands, and other verified students (“runners”) complete them, with payment held by us until delivery is confirmed. Because strangers are trusting each other with money and their doorstep, we ask for a little more information than a typical app — and we take the responsibility that comes with that seriously. This Privacy Policy explains, in plain terms, what we collect, why, who can see it, how long we keep it and what you can ask us to do with it.
By creating an account or joining our waitlist, you acknowledge the practices described below. Where we rely on your consent (for example, to process your matric number and student ID photo), we ask for it separately and you can withdraw it at any time — see Your rights. Your use of Errandly is also governed by our Terms of Service.
We are the data controller for the personal data described here. We follow the Nigeria Data Protection Act 2023 (“NDPA”), the Nigeria Data Protection Regulation 2019 (“NDPR”) and guidance from the Nigeria Data Protection Commission (“NDPC”).
What this Privacy Policy covers
This policy covers personal data we collect through the Errandly website and app, our waitlist, and when you contact us. “Personal data” means any information that identifies you or can reasonably be linked to you. It doesn't cover the vendors your runner buys from (a cafeteria or filling station has its own practices) or your bank.
Personal data we collect
Categories of personal data we collect
We only collect what we need to run errands safely and pay people correctly. The table below lists every category.
| Category (and examples) | Why we collect it | Who else can see it |
|---|---|---|
| Account and contact details — full name, email address, phone number, your password (stored only as a secure hash by our authentication provider), and whether you use Errandly as a buyer, runner or both. | To create and secure your account, let you sign in, and let you and the other person on an active order reach each other. | The other person on an active order sees your name and phone number. Our hosting and authentication providers process it for us. |
| Student verification — your matric number and a photo of your student ID card. | To confirm every user is a real student, keep one account per student, and make people accountable on a peer-to-peer platform. | Only Errandly administrators. Never other users. See below. |
| Order details — what you asked for, the vendor, your delivery location and notes, receipts and handover photos uploaded by runners, order status and timestamps, and your delivery PIN. | To fulfil the errand, reconcile variable costs (like petrol), confirm delivery and resolve disputes. | The buyer and runner on that order. The delivery PIN is shown only to the buyer. Administrators can see order details when reviewing a dispute, but not the PIN. |
| Payment and payout details — amounts you pay or earn, your Errandly wallet history, and (for people who receive payouts) your bank name, account number and the account name returned by your bank. | To hold payments in escrow, pay runners, process refunds, and check that payouts go to an account in your own name. | Our payment provider, Bachs, and the banks involved in the transfer. We never see or store your card number — Bachs handles payment entry. |
| Trust and safety records — ratings you give and receive, reports, disputes, and any account restrictions and the reasons for them. | To keep the platform safe, spot repeated problems and resolve complaints fairly. | Administrators. The person you rate or report never sees who reported them. You can always see your own restrictions and why. |
| Technical data — IP address, browser and device type, and essential cookies that keep you signed in. | To keep your session working, prevent abuse (for example, limiting repeated sign-in attempts) and fix errors. | Our hosting provider processes it for us. |
| Waitlist sign-ups — name, email, phone and matric number. | To tell you when Errandly launches at your campus and to give early verification priority. | No one outside Errandly. |
| Messages to us — anything you send our support team. | To help you. | Our email provider processes it for us. |
Your matric number and student ID photo
These are the most sensitive things we hold, so they get extra protection. We use them for one purpose: verifying that you are a student (and making sure one student has one account). Specifically:
- Your ID photo is stored in a private storage area that has no public web address. When an administrator needs to check it, our system creates a link that expires after 60 seconds, and every view is recorded in an access log.
- Your matric number is encrypted before it is stored. Uniqueness checks use a one-way fingerprint, so we can tell a matric number is already registered without decrypting anyone's.
- We remove location data (EXIF/GPS) from your ID photo when you upload it.
- Only Errandly administrators can access them. Other users — including the people you buy from or run for — never see your matric number or ID photo.
- We don't use your ID photo for facial recognition or any other automated identification.
- If your ID is rejected and you upload a new one, the old photo is deleted.
Where your personal data comes from
- From you, when you sign up, verify your student status, place or run an order, add bank details, rate, report or contact us.
- Automatically, when you use the app (technical data and order timestamps).
- From other users, when a runner uploads a receipt or handover photo for your order, or someone rates or reports you.
- From our payment provider and your bank, which confirm whether a payment succeeded and return the name registered to a bank account.
Why we use it and our lawful basis
Under the NDPA we need a lawful basis for each use of your data:
- To provide the service you asked for (performance of a contract): accounts, orders, escrow, payouts, delivery confirmation and support.
- Your consent: processing your matric number and student ID photo for verification. You give it during sign-up and can withdraw it — but because verification is what makes Errandly safe, withdrawing it means we'll have to close your account.
- Our legitimate interests in keeping the platform safe and preventing fraud: rate limiting, trust and safety records, payout name checks and access logs. We balance these against your rights and keep them proportionate.
- Legal obligations: keeping financial records and responding to lawful requests from authorities.
We don't sell or rent your data
We do not sell, rent or trade your personal data, and we do not share it with advertisers or data brokers. We don't run advertising trackers on Errandly.
Automatic account restrictions
To protect students, our system automatically pauses an account from accepting tasks when it receives reports from several different people within a short period (for example, two different people in 24 hours). One person reporting someone repeatedly can never trigger this on their own. When it happens:
- The restriction is temporary and you are always told why in the app.
- A person — not the system — reviews it, aiming to do so within 24–48 hours, and lifts, adjusts or confirms it.
- You can contest it by contacting us. You can still place orders as a buyer while it's reviewed.
A negative wallet balance (for example, from an unused transport advance) is a financial record only — it does not restrict your account.
How we protect your data
- All connections to Errandly use HTTPS encryption.
- Matric numbers, bank account numbers and delivery PINs are encrypted in our database.
- Database access rules ensure each user can only read their own records, and only administrators can access verification data.
- Student ID photos, receipts and delivery photos are kept in private storage and only shown through short-lived links after a permission check.
- Sign-in, sign-up, ordering and other sensitive actions are rate-limited to slow down attacks.
- Administrator access to sensitive data is logged.
No system is perfectly secure. If a breach affects your personal data and is likely to put your rights at risk, we will notify the NDPC within 72 hours of becoming aware of it, as the NDPA requires, and tell you without undue delay.
How long we keep your data
We keep personal data only for as long as we need it for the purposes above [confirm periods before launch]:
| Data | How long we keep it |
|---|---|
| Student ID photo | While your account is open, then deleted within 90 days of closing your account. A rejected photo is deleted when you replace it. |
| Matric number | While your account is open and for 12 months after closure (to stop banned accounts re-registering). After that, we keep only the one-way fingerprint. |
| Account and contact details | While your account is open, then up to 12 months after closure to handle any late disputes. |
| Orders, payments, payouts and wallet history | 6 years, because Nigerian law requires us to keep financial records. |
| Receipts and delivery photos | 12 months after the order is completed or its dispute is resolved. |
| Ratings, reports and restrictions | While your account is open and 12 months after closure. |
| Waitlist sign-ups | Until 6 months after we launch at your campus, or until you ask us to delete it. |
| Security logs (including administrator access logs) | Up to 2 years. |
| Rate-limit records (IP address) | Up to 24 hours. |
Storage and transfers outside Nigeria
Some of our providers store or process data on servers outside Nigeria [confirm hosting regions]. When that happens we rely on the transfer safeguards allowed by the NDPA — such as the provider's contractual data protection commitments and the adequacy of the destination's protections — and we keep the same protections described in this policy.
Age requirement
Errandly is for university students aged 18 or older [confirm]. We don't knowingly collect personal data from anyone under 18. If you believe someone under 18 has signed up, contact us and we'll delete their data.
Your rights under Nigerian law
Under the NDPA you have the right to:
- Be informed about how we use your data (this policy).
- Access a copy of the personal data we hold about you.
- Correct data that is wrong or incomplete.
- Delete your data, where we don't need to keep it for a legal reason (for example, financial records).
- Restrict or object to certain uses, including uses based on our legitimate interests.
- Data portability — receive the data you gave us in a commonly used format.
- Withdraw consent at any time, without affecting what we did before you withdrew it.
- Not be subject to a decision based solely on automated processing that significantly affects you — which is why every automatic restriction is reviewed by a person.
To use any of these rights, send a request through our support form (choose “My data / privacy request”), ideally while signed in to the account concerned so we can confirm it's you. We'll respond within 30 days. You also have the right to complain to the Nigeria Data Protection Commission (ndpc.gov.ng).
Changes to this policy
If we make a significant change, we'll tell you in the app and by email or SMS before it takes effect. The effective date at the top shows when this policy was last updated.
Contact us
Questions, requests or complaints about your personal data — including for our Data Protection Officer — go to:
Errandly — Data Protection
Privacy requests: support form → “My data / privacy request”
Everything else: errandly support
Dedicated Data Protection Officer email: [confirm before launch]
Address: Malete, Kwara State, Nigeria [confirm]