Skip to content

Privacy and collection notice

Updated 7 September 2026. Privacy is part of the operating model. This notice explains the account and support collection points and the community records the application can process.

Official details and processing arrangements require verification.

This is not a compliance certification or confirmation of approved provider contracts. Legal identity, Information Officer designation, processing locations, applicable PAIA arrangements and retention schedules must be verified by the site operator and relevant scheme before sensitive client use. A configured name or link below is operator-supplied and still requires verification.

Who is responsible and how to contact them

Levii is the product name, not a verified legal entity in this notice. Responsibility depends on who determines each processing purpose. Your scheme or managing agent may determine purposes for community records, while the service operator handles platform accounts and support. The purpose-by-purpose responsible-party and operator allocation has not been published here.

Legal identity and address: not yet published
Legal entity name unavailable. Official address unavailable.
Information Officer: not yet published
Name and designation unavailable. A verified Information Officer contact is unavailable.

Contact and support shows the configured general channel, or states clearly when none is available. General support is not presented as the Information Officer.

Required and optional information

  • Registration: name, username, email and password are required to create and secure an account and assess scheme access. Phone is optional. Without the required details we cannot create the account. Access remains subject to verification and approval; registration alone is not proof of entitlement to scheme records.
  • Sign-in and recovery: a username or email and password authenticate you. Recovery uses your registered email and a short-lived token. Passwords are stored as hashes; a reset changes the password, rotates remembered access and ends previous sessions. Existing two-step verification remains in place.
  • Support and enquiries: a name, reply contact and short description help the team respond. Scheme details are optional for an initial enquiry. Without a reply contact the team may be unable to respond. This contact page opens a configured channel; it does not itself collect a support form or issue a ticket.
  • Community records: authorised scheme teams may provide owner and unit details, contacts, accounts, documents, maintenance, communications and meeting records. These may come from you, your scheme, its managing agent or authorised service providers, rather than directly from a registration form.
  • Security and technical records: the application can record IP address, browser/device information, session activity, sign-in times and audit events to protect access and investigate faults. Session and anti-forgery cookies support sign-in and protect forms. Provider-specific tracking and retention settings have not been verified by this notice.

Purposes and choices

Information is used for account administration, access checks, replying to requests, community administration and security. The responsible party must identify and document the lawful basis for each actual purpose, including any applicable contract or legal obligation. This notice does not treat every purpose as consent, and submitting an access request is not blanket permission for unrelated marketing or AI sharing.

Provide only what is needed. Do not include other residents' personal records in an initial enquiry. Two-step verification remains optional to enrol; an account that has enrolled must still complete it. Automated owner matching can support access decisions; contact the scheme team to query an incorrect match or access outcome.

Recipients and processing locations

Depending on the enabled service and your scheme, information may be handled by authorised scheme staff, managing agents, support staff and contracted hosting, storage, mail, messaging, payment, monitoring or AI providers. Scheme assignments and role permissions are intended to limit access. This notice does not guarantee that every access boundary or provider arrangement has been independently verified.

The current provider list, contracts, processing countries and cross-border safeguards have not been published here. Do not assume all processing is in South Africa or that enabling a service establishes lawful transfer conditions. External AI sharing requires a separate authorised decision and review of the actual data, settings and provider terms.

Retention

Account, scheme, support, audit, export, provider and backup records can have different retention needs. The approved record-class schedule, deletion routines and backup/provider removal timelines have not yet been published. A password-reset token expires within 60 minutes and cannot be reused after a successful reset; expiry is not a promise that all associated logs or backups are deleted at that time.

Ask the responsible party about retention for your record. A deletion request requires assessment of legal obligations, third-party rights and evidence holds; it is not a promise to erase records that must lawfully be retained.

Access, correction, deletion and objection

Existing owners can use the owner privacy request workflow after sign-in to record access, correction, deletion or objection requests and follow their status. That workflow remains available; this public notice does not replace it.

Non-users, people unable to sign in and people requesting escalation can use the published Information Officer contact above. Where it is missing, the general contact page provides the configured support channel and its availability. Existing scheme members can also use the contact in their established scheme correspondence. Ask for acknowledgement, a reference and an expected response date. No verified response-time commitment is published here.

The team may need a proportionate identity and authority check before releasing or changing records, and may need to protect third-party information. Do not send identity documents or credentials in an initial message.

PAIA manual: not yet published

The applicable manual and request procedure remain to be confirmed and published. A dedicated public PAIA request link is not configured.

For independent information about complaints and statutory rights, visit the South African Information Regulator's POPIA resources and PAIA resources. These are regulator resources, not an endorsement of Levii.