Privacy Policy
Effective: 3 September 2026
This policy explains how RaphaelLinkSphere processes information when providing the RLS platform and configured services to institutions and authorised users.
1. Who operates RaphaelLinkSphere
RaphaelLinkSphere (RLS) is currently operated by Steven Martin Ryan Venter, an individual based in South Africa.
Fraener Digital may appear as a payment-provider or storefront label. It is not a registered legal entity and is not the legal owner or operator of RLS.
2. Institutional data relationship
RLS is provided primarily through schools and other authorised institutions. Institutions determine the staff, parent, learner and institutional records entered into or used through their RLS environment.
RLS processes those records to provide the platform and its configured services. RLS does not claim independent ownership of learner or institutional records supplied through an institution.
3. Information processed
Depending on the modules and services an institution enables, RLS may process account and identity information, institution and membership information, role and access information, learning and assignment records, communications, operational records, uploaded files and evidence, support records, audit events and other information required for configured education and administration workflows.
RLS also processes technical information needed to operate and secure the service, such as session, request, diagnostic, security and operational-event information.
4. Why information is processed
Information is processed to authenticate users, provide institution-scoped workspaces, deliver configured education and administration features, support communications and operational workflows, store authorised files and evidence, provide governed platform functionality, maintain security and auditability, respond to support requests and operate the service.
Where AI-assisted functionality is enabled, relevant information may be processed to provide the requested governed AI feature. Availability and use of those features depends on institutional configuration and applicable platform controls.
5. Learners and minors
RLS is intended to be provided through institutions and is not designed as a direct-to-minor consumer contracting service.
Learner accounts form part of the relevant institution environment. The institution and, where applicable, parents or guardians are responsible for ensuring that the required authority, notices or permissions for learner use are in place.
6. Service providers and processing locations
RLS may use third-party infrastructure and service providers for functions such as hosting, databases, file storage, communications, payments and enabled AI or platform services.
Those providers may process information in locations outside South Africa. Appropriate contractual, technical and organisational measures are used where applicable, but no statement on this page should be read as a claim of a certification or legal status that has not independently been obtained.
7. Security
RLS uses institution-aware access controls, authenticated sessions, role and membership checks, protected storage workflows and auditable operational mechanisms where implemented.
No online service can guarantee absolute security. Security also depends on deployment configuration, institutional access practices, user behaviour and third-party infrastructure.
8. Retention and deletion
Information is retained for as long as reasonably required to provide the configured service, support institutional requirements, maintain necessary operational or security records, meet contractual obligations and comply with applicable legal requirements.
Retention requirements may differ by institution, record type, enabled module and applicable law. Institutions should contact RLS regarding account, export, deletion or retention requirements relevant to their environment.
9. Privacy requests and rights
Individuals may have privacy or data-protection rights under applicable law. The availability and scope of those rights depends on the circumstances and applicable legal requirements.
Because many RLS records are controlled through an institution environment, a request concerning institutional records may need to be handled with or referred to the relevant institution. RLS will respond to valid requests as required by applicable law.
10. Cookies and session technologies
RLS uses session and similar technical mechanisms where necessary to authenticate users, maintain secure application state and provide platform functionality.
This policy does not claim the use of advertising or behavioural-tracking technologies where those technologies have not actually been enabled.
11. Changes to this policy
This Privacy Policy may be updated when the platform, operating arrangements or applicable requirements change. The current version will be published on this page.
12. Contact
Privacy and legal enquiries may be sent to stevenventer7@gmail.com.
No unsupported compliance claim
This policy describes the current RLS operating and data-handling model. It does not claim that RLS, its operator or Fraener Digital holds a certification, accreditation or formal compliance determination that has not actually been obtained.