Privacy policy
What we collect, and why
Last updated 1 September 2026. This is a placeholder summary written for a scaffold, not final legal copy. Replace it before launch.
On this page
1. What we collect
Your name, phone number, farm details and state at signup; the warehouses you book and the rent you pay; and photos or text you add to community posts and reviews.
2. How we use it
To run your bookings, show you relevant warehouses and prices, send rent and capacity alerts you've opted into, and improve which storage options we surface near you.
3. Payment information
Card and bank details are handled directly by Paystack, our payment processor. MORRTOWN never stores your full card number.
5. Your choices
You can edit your profile and notification preferences from Settings at any time, and request a copy or deletion of your data by contacting support.
6. Data retention
We keep booking and payment records for as long as required for accounting and dispute purposes, even after an account is closed.
7. What MORRTOWN staff can do
Anything you post publicly can be removed by MORRTOWN staff. That means community threads and the replies under them, and reviews you leave about a store. We remove a post when it breaks these terms, exposes someone's personal details, or is reported to us, and we can do it without notice. A deletion is permanent: the post and its replies are erased rather than hidden, so we cannot restore something once it is gone.
8. Staff replies and video comments
MORRTOWN publishes videos by linking to them on services such as YouTube; we do not host the files. Comments and likes you leave under a video are stored against your account and shown publicly with your name. Staff can reply to those comments, and a staff reply carries a MORRTOWN badge so you can tell an official answer from another farmer's. Watching a video may load it from the service hosting it, and that service applies its own privacy policy.
9. Staff access to your information
A small number of MORRTOWN staff can see your account details, bookings and payment records through an internal console, in order to run the platform and answer support requests. Access is limited to named addresses and protected by a separate password; it is not granted by signing in to the app.