Skip to content

Privacy Policy

Last updated: 3 November 2026

1. Introduction

This Privacy Policy explains how GreenGrove Technologies ("we", "our", "us") collects, uses, and protects information when you use our services, including:

  • The GreenGrove Technologies marketing website
  • The EstateNotice mobile application
  • The EstateNotice admin portal

This policy applies to all users, including estate residents, administrators, website visitors, and the business contacts of our client agencies and estates.

1.1 Who is responsible for what

For the purposes of the Protection of Personal Information Act, 2013 (POPIA), each estate is the responsible party for the personal information provided to the service by or on behalf of that estate, including residents' phone numbers added to the estate's allowlist, emergency contacts, access codes, notices, documents and events. GreenGrove Technologies processes that information as operator, on the documented instructions given by the Client (the estate or its managing agent that signed the agreement with us) on behalf of the estate.

Residents and administrators who use the app accept our Terms and Conditions and this Privacy Policy themselves in the app when they first sign in, and again when we change them. GreenGrove Technologies is the responsible party for the information residents and administrators give us directly when they sign in and use the app, including for account administration. GreenGrove Technologies is also the responsible party for the business contact details of our client agencies and estates (billing contacts, signatories, the information officer and the address), which we use for the agreement, invoicing and reminders.

This means an estate does not need to collect separate written consent from its residents for them to use the app. The estate, through its managing agent, must tell its residents that it uses EstateNotice and that their phone numbers have been added to its allowlist, and must have collected their information lawfully.

2. Information We Collect

2.1 Marketing Website

When you visit our marketing website, we may collect:

  • Contact information you voluntarily provide (name, email, phone number, company name)
  • Technical information collected automatically (IP address, browser type, device type, pages visited, date and time)

2.2 EstateNotice Platform

When you use the EstateNotice mobile app or admin portal, we collect:

  • Phone number: Required for authentication. We store phone numbers in E.164 international format (e.g., +27 8X XXX XXXX).
  • Email address: Where your account has a confirmed email address, we store it and use it to sign you in: to check who is asking for a code, to limit repeated attempts and to deliver login codes (see Section 4).
  • User account information: Unique identifiers, account creation timestamps, and role assignments (viewer or admin).
  • Estate association: Which estate(s) you have access to and your permission level for each.
  • Activity logs: Actions performed within the platform are logged for security and audit purposes (see Section 8).
  • Access timestamps: When you authenticate and access the platform.

We also collect:

  • Your name: the first and last name you enter in your app profile. Your estate's administrators can see it.
  • Your read receipts: whether and when you opened a notice.
  • Your device identifier: a code that identifies your phone, used to deliver push notifications to it. We store it with your phone's operating system, the app version and when we last saw it. The app also creates a random code the first time it is used, which we use to limit repeated sign-in checks from one phone.
  • Our send logs: a record of the messages we send to you (sign-in codes, push notifications and email), with the time and whether each was sent.
  • If your estate sends you a link to its consent page: the full name, phone number, unit or address (optional) and email address (optional) you enter there. Your estate's administrators see them to approve or reject your request.
  • If your estate imports a list of the residents it expects to join: the phone number, name, unit (optional) and email address (optional) your estate's administrators enter for you.

2.3 Data Created by Administrators

Estate administrators may create and manage the following data within their estate:

  • Emergency contacts: Names, phone numbers, and descriptions for security, medical, fire, and other services.
  • Access codes: Gate PINs and facility codes (stored encrypted, see Section 5).
  • Estate notices: Announcements and alerts for residents.
  • Phone allowlist: Phone numbers permitted to access the estate's information, with optional labels.

3. How We Use Information

We use collected information to:

  • Provide the service.
  • Keep the service secure and prevent abuse.
  • Keep audit records for accountability and compliance.
  • Produce aggregated, de-identified statistics on how the app is used, to keep it working and improve it.
  • Respond to enquiries and send service messages.

We never sell personal information, and we never use estate data for marketing.

Invitations to join EstateNotice are service messages sent by your estate or its managing agent. They are not marketing.

4. Authentication

You sign in with a one-time code sent by SMS or email. In the app, we check that your phone number is on your estate's allowlist before we send the code. In the admin portal, we check that your phone number or email address belongs to an administrator of an active estate before we send the code. You enter the code to sign in. We do not store passwords.

Rate limiting: To prevent abuse, we track authentication attempts by phone number, email address and IP address. Excessive failed attempts may result in temporary lockouts.

5. Data Storage and Security

We implement multiple layers of security to protect your information:

5.1 Access Control

  • Role-based permissions: Users are assigned viewer or admin roles per estate.
  • Row Level Security (RLS): Database-level security ensures users can only access data for estates they belong to.
  • JWT authentication: All API requests are authenticated using secure tokens.

5.2 Estate Isolation

Access to estate data is restricted per estate: users can only view information for estates where they have been granted access, and members of one estate cannot see another estate's data through the app. This is enforced at the database level. GreenGrove Technologies staff can access estate data to run and support the service.

5.3 Encryption

  • Data in transit: All connections use TLS/HTTPS encryption.
  • Access codes: Sensitive access codes (gate PINs, facility codes) are encrypted at rest using PGP symmetric encryption before storage.

However, no method of transmission over the internet or electronic storage is completely secure. We cannot guarantee absolute security.

6. Third-Party Services

We use outside companies to run the service. We describe them by type, so that this page stays accurate when a company changes.

  • Cloud hosting and database provider: Database, sign-in, file storage (letters) and server functions. Holds all resident and administrator data. Where the data is stored or processed: Ireland, European Union.
  • SMS provider for login codes: Sends sign-in codes by SMS, and the code an administrator enters to confirm a change to their admin portal account. Receives the phone number and the code message. Where the data is stored or processed: United States.
  • Email provider: Sends sign-in codes by email. Receives email addresses and the message. Where the data is stored or processed: Email is sent from Ireland, European Union. The provider's main processing is in the United States.
  • Push notification service: Delivers notice alerts to phones. Receives a device token, the estate name and the notice title. Where the data is stored or processed: No location is shown in our accounts with these providers. They may process data outside South Africa.
  • Website and admin portal hosting provider: Hosts the website, the admin portal and our internal staff dashboard. Admin pages, staff dashboard pages and exports pass through it. Where the data is stored or processed: May be outside South Africa. Sign-in checks run at the provider's location nearest the user, which may also be outside South Africa.
  • Business email and office software provider: Our business email and files. Receives whatever residents and agencies email to us, holds the invoices and reminders we email to our clients, and holds the encrypted copy of a leaving estate's data until it is collected and deleted. Where the data is stored or processed: No data region is chosen in our account. It may store or process data outside South Africa.
  • Calendar booking provider: Handles demo bookings on our website. Receives the details you enter when you book a demo (for example your name, email address and answers about your estates), and adds the booking to our sales calendar with a video call link. Our demo page loads this provider's calendar as soon as it opens, so the provider also receives the usual technical details of your visit, such as your IP address and browser, even if you do not book. Where the data is stored or processed: No data region is chosen in our account. It may store or process data outside South Africa.
  • Staff sign-in provider: Our staff sign in to our internal dashboard with their work account. Receives staff identity only, no resident data. Where the data is stored or processed: No location is shown in our account. It may process data outside South Africa.

Our clients (the estate or its managing agent that signed the agreement) can ask us for the names of these providers by emailing support@estatenotice.app.

7. Cookies

The website and admin portal may use cookies or similar technologies for:

  • Session management and authentication
  • Remembering user preferences

You can control cookie settings through your browser preferences.

Marketing site analytics. The marketing website (estatenotice.app) uses the web analytics service of our website hosting provider. It does not use cookies: visitors are counted using a hash derived from the incoming request, which is discarded after 24 hours. It records the page's timestamp, URL and path, the referrer, filtered query parameters, an approximate location (country, region and city), the visitor's device operating system and version, browser and version, device type, and a "Book a demo" click event. This data is not tied to an individual or to an IP address, and cannot be used to reconstruct a visitor's browsing across other websites. It also uses that provider's page-speed service to measure how quickly pages load. Page-speed measurement does not use cookies. For each measurement it records the page's route and URL, the network speed, the browser, device type and operating system, the country, the page-speed measurement and what affected it, the version of the measuring script, and the time the measurement was received. This data is not tied to an individual or to an IP address, and cannot be used to reconstruct a visitor's browsing across pages.

8. Audit Logging

For security and compliance purposes, we maintain audit logs that record:

  • What is logged: Changes to access codes, estate notices, estate settings and events; removals from an estate's phone allowlist; changes to contact-category visibility; and members leaving an estate.
  • What is captured: The user who performed the action, timestamp, previous values, and new values.
  • Access: Audit logs are scoped to their estate and visible to estate administrators. GreenGrove Technologies staff can also access them to run and support the service.
  • Retention: Audit logs are append-only and are kept for compliance and security. When an account is deleted, the person is removed from the audit record and the event is kept. When an estate leaves the service, its activity history is deleted and a record of the deletion is kept.

9. Data Retention

We retain data as follows:

  • User accounts. Your account (your phone number, your first and last name, and your email address if your account has one) is kept until you ask for it to be deleted, even after you no longer have access to any estate. Removing your number from an estate's allowlist ends your access to that estate; it does not delete your account. To have your account deleted, see "Account deletion (erasure)" below.
  • Account deletion (erasure). When you ask us to delete your account, we delete it, and your number on every estate's allowlist, from our live systems. If you are the only administrator of an estate, or your estate has no administrator, some steps are done by hand and it can take longer; we tell you if it does. Content you published as an administrator (notices, letters, events, codes and documents) stays part of the estate's record, with your name removed. Some records are not deleted with your account and keep your details for their own period. They include: our sign-in code send logs, which keep your phone number for 12 months; your estate's import list and consent-page records, which keep your phone number, your name and, if given, your unit and email address, as described below; the records of push notifications sent to your phone, which keep its device identifier; the records we use to limit repeated sign-in attempts, which keep the phone number or email address used until our daily clean-up removes them, as described under "Rate limiting data" below; and copies in some of our system logs, which are not yet removed automatically when an account is deleted.
  • Removed phone numbers. When a phone number is removed from an estate's allowlist, access to that estate ends straight away, and the record is deleted 30 days after it is removed. Deleting it removes the allowlist record only. Other records that hold the number keep it for their own period. They include: your account, if you have ever signed in, which keeps your phone number and your first and last name until you ask for it to be deleted (see "User accounts" above); our send logs, which keep the phone number a sign-in code was sent to for 12 months; your estate's import list; and consent-page records. The last two are described below.
  • Invitations never used. A person who is invited but who never signs in is removed automatically after 30 days. The 30 days run from when the number was added to the allowlist, or from when it was last restored to it. For a number that was already on an allowlist when this rule started, they run from the day it started. Numbers are not removed this way while an estate has no administrator: they are kept until it has one. A number removed this way is then deleted 30 days later, as for any removed number. You or your estate can ask to be removed sooner.
  • Audit logs: Kept for compliance and security, as described in Section 8.
  • Consent-page records. A request made on your estate's consent page that the estate has not approved or rejected within 90 days is deleted. Once the estate approves or rejects it, it is kept as the record of that decision until the estate leaves the service.
  • Estate import lists. An entry on your estate's import list that is still waiting for your estate to act on it after 90 days is deleted. The other entries are kept until the estate leaves the service.
  • When an estate leaves. When an estate leaves the service and its information is deleted, every number on its allowlist is deleted with it, including numbers that were already removed. We keep only a record that a removal or deletion happened, with no number or name.
  • Rate limiting data. To limit repeated sign-in attempts and repeated requests on the consent page, we keep records of the phone number or administrator email address, the app's random code or the IP address used. A clean-up that runs once a day removes these records, at the latest at its first run after they are 24 hours old. When we block certain attempts, we also keep a record of the block, which the same daily clean-up removes at its first run after it is 7 days old. Attempts that are not blocked are not recorded this way.
  • Client business contacts. The business contact details of our client agencies and estates (see 1.1) are kept for as long as the agency or estate is our client, and after that for the period the law requires us to keep business records.
  • Administrator accounts. To delete an administrator account, email support@estatenotice.app.
  • Backups. Our database provider keeps a daily backup of our database for 7 days. A record deleted from our live systems is gone from those backups within 7 days.
  • Marketing inquiries: Retained as long as necessary to respond and for legitimate business purposes.

10. International Data Transfers

Some of your information is stored or processed outside South Africa by the providers described in section 6. Section 72 of POPIA sets the conditions for sending personal information outside South Africa. Our clients can ask us for the names of these providers and links to the terms they publish.

When an estate administrator or one of our staff uses a signed-in page, the check that they are signed in runs at our website hosting provider's location nearest them, which may be outside South Africa.

11. Your Rights (POPIA)

Under the Protection of Personal Information Act (POPIA) and other applicable laws, you have the right to:

  • Access: Request confirmation of whether we hold your personal information and obtain a copy.
  • Correction: Request correction or deletion of inaccurate, irrelevant, or outdated information.
  • Deletion: Request deletion of your personal information, subject to legal retention requirements.
  • Object: Object to processing of your personal information in certain circumstances.
  • Withdraw consent: Withdraw consent for processing where consent was the legal basis.
  • Lodge a complaint: Lodge a complaint with the Information Regulator if you believe your rights have been violated.

To exercise these rights, contact us at: support@estatenotice.app

Note: Estate administrators control access to their estate. To be removed from an estate's allowlist, contact your estate administrator directly.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Updates will be reflected by revising the "Last updated" date above.

For significant changes, we may provide additional notice through the platform or via email.

13. Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, please contact:

GreenGrove Technologies
Email: support@estatenotice.app
Location: Cape Town, South Africa

For POPIA-related inquiries, you may also contact the Information Regulator at inforegulator.org.za.

See it with your own estate’s notices.

Bring a recent notice. We’ll show you how it lands on residents’ phones.

Book a demo