Privacy policy
Know what you share, who can see it, and how to stay in control.
Browsing is open to everyone. Approved listings are public. Live browsing location is optional. This app has no built-in advertising trackers or analytics. Optional interactive maps stay off until you allow them.
Who is responsible
The community service operator is VAN ZYL DEVELOPERS (PTY) LTD. The app was developed by VAN ZYL DEVELOPERS (PTY) LTD. The operator manages community submissions and privacy requests.
Registration number: 2026/722389/07
Address: Monte Carlo, Waboomsberg, Ceres, 6835, South Africa
Privacy contact: vanzyldevelopers.online@gmail.com.
Information used by the app
- Accounts: when Firebase is connected, Firebase Authentication handles email/password and Google sign-in. It provides an account identifier, display name, email, verification status and, where supplied, a profile photo URL. The app does not store your password in its listing database. Google and Firebase process authentication credentials through their own services.
- Contributions: the title, description, category, keywords, services, operating hours, availability, dates, venue, address, contact details, map pin, images and filenames you provide. A listing also records its owner identifier, owner display name, submission/update times, review status and any moderation feedback.
- Browser preferences: saved listing identifiers, your map/privacy preference, the dismissed location prompt and, in local demo mode, the demo profile and submissions.
- Technical connections: the hosting service, Firebase Authentication, Supabase and other services you choose to use receive information needed to deliver requests, such as IP addresses and browser/network details. Their technical logs and retention depend on the services configured by the operator.
Why this information is used
Account information supports sign-in, email verification, ownership and access control. Submitted information lets the operator review contributions and publish a useful directory and calendar. Contact details enable people to contact the listing owner. Search terms filter community information; nearby browsing uses your location to calculate distance. Technical processing supports delivery, security and troubleshooting.
You can browse without creating an account, sharing your location or enabling maps. Verified sign-in and required listing fields are needed to submit a contribution. Additional photos are optional except where a business submission requires a business image. Do not provide information you do not want published in the listing.
The operator must establish and document appropriate lawful grounds for its processing under South Africa’s Protection of Personal Information Act (POPIA). Optional map permission and browser location permission can be withdrawn. Giving permission for those features is separate from the processing needed to provide an account or a submitted listing.
What becomes public
Approved listings, their chosen contact details, location pins and images can be viewed without signing in. The approved listing’s underlying public data also includes its owner display name, owner identifier and timestamps. Your account email is not automatically used as a public contact field; you choose the email or phone number you add to the listing.
Public material may be indexed by search engines, shared, downloaded or copied by visitors. Administrators can review pending and returned submissions; the signed-in owner can manage their own contributions. Editing a published listing returns it to review. A hidden administration address still requires an authorised administrator role.
Only submit information you own or have permission to share. Avoid identity documents, medical records, private home details and children’s personal information. Schools and clubs should use an authorised adult’s organisation contact. A home-based worker or work-seeker can use an area or suitable public meeting place instead of a private home address.
Photos and posters
Images in local demo mode are stored in your browser. The shared directory uses Supabase for listing records and uploaded images, with Firebase Authentication for accounts. Images are held in a private storage bucket. Public image requests check that the listing is published; owner and administrator previews use temporary viewing links. There is no app-imposed image count limit; device space, provider file-size limits and storage or transfer quotas still apply.
Published images can be downloaded or copied. A copied temporary preview link may remain usable for up to two minutes after it is issued, even after a listing is unpublished. Deleting a listing attempts to delete its attached files; if the app reports a connection or deletion error, retry and contact the operator if it persists. Do not upload confidential material.
Optional live location
When you choose “Use my location”, your browser asks permission. Your device’s position is held in memory to estimate straight-line distances and updates while live location is active. This browsing position is not saved to your public profile or sent by the app to Firebase, Supabase or the address-search provider. Turn it off using the location control or revoke permission in your browser.
You can choose a starting address instead of device location. Its coordinates stay in this tab for approximate distance calculations and do not update as you move. They are not added to your profile or a listing. Turn off address distances or close the tab to clear this choice.
Choosing “Use my current position” in the submission form is different: those coordinates become part of your submitted listing and are public if approved. Use that button only at a business or venue whose location you intend to publish.
Maps, address searches and external services
Interactive OpenStreetMap maps load only after you allow optional maps and choose to display a map. The map provider then receives your IP address, connection details and the listing’s map coordinates. Change or withdraw this preference through “Cookie settings” in the footer. This prevents future embedded map loads; it cannot undo a request already sent.
When you request an address search to choose a browsing starting point or a listing map pin, the entered search text goes through the app’s server to the configured Photon-compatible provider, using Komoot’s public Photon service by default. Address searches do not require browser GPS permission. You can enter a listing’s coordinates manually instead. Address results and their query may be cached by the app server in memory for up to 24 hours and by your browser for up to 24 hours.
Directions links open Google Maps; phone, email, website and other external links use the service you choose. Those services have their own policies. Google/Firebase services authenticate accounts. Supabase receives account identifiers and signed authentication tokens to control access to shared listings and images. Declining optional maps does not disable these requested core features.
The connected Supabase project stores primary project data in London, United Kingdom (region eu-west-2), outside South Africa. Firebase/Google authentication, Vercel hosting and technical support may involve other processing locations. The operator must review provider agreements and applicable cross-border safeguards and update this notice if these arrangements change. This service does not promise South African-only processing.
Browser storage and offline pages
The cookie and browser storage policy explains local storage, IndexedDB, authentication persistence and the optional map choice. In local demo mode, test submissions and image files remain in this browser and are not uploaded to cloud services. Clearing site data removes local demo records, bookmarks and preferences. It does not delete cloud accounts or shared submissions.
The installed web app may cache visited public directory pages and app assets for offline use. Account, administration and submission pages, Firebase/Supabase requests and uploaded images are excluded from the app’s service-worker cache. Offline information may be out of date.
How long information stays
The app does not automatically expire or delete accounts, published listings, pending or returned submissions, or their images. They stay until the owner or operator removes them, subject to the configured provider’s storage and backup arrangements. Local demo records stay until deleted through the app or cleared in browser settings. Optional map choices expire after 180 days; other browser data is described in the cookie policy.
The operator must set and apply a retention schedule appropriate to the live service and any legal obligations. A request to remove information will be assessed against applicable rights and lawful retention needs. This preview does not promise a deletion deadline or that third-party caches and copies can be recalled.
Your choices and privacy requests
Use “My submissions” to edit or delete your contributions. Account deletion is handled by a request to the operator; there is no automatic account-deletion button in this version. Account deletion and listing deletion are separate, so identify both in your request if you want both removed.
Subject to applicable law, you may ask about information held about you, request access or correction, request deletion where appropriate, object to processing, or withdraw consent where processing relies on it. The operator may need to verify your identity before acting. Do not send identity documents through a public listing.
Send requests to vanzyldevelopers.online@gmail.com, including enough information to locate the account or listing.
You can also raise a privacy complaint with South Africa’s Information Regulator. Its official complaints page explains the current process and links to the eServices portal.
Security and changes
Firebase-verified accounts and Supabase database/storage access policies restrict contribution management. These measures do not make any online service risk-free. Report suspected unauthorised access or accidental publication to the operator promptly. The operator remains responsible for reviewing access, handling incidents and making any notifications required by law.
This notice describes the current app. The operator should update it when its processing, providers or contact details change. Read it together with the terms of use, cookie policy and disclaimer.