Use this page for questions about the StudyAid ZA website, correction reports and privacy requests concerning this service. Your message is stored for operator review and the form provides a reference receipt. The portal does not make funding decisions or collect applications. For a programme's eligibility, application status, documents or outcome, contact that programme through the official details on its own website.
Choose the right place for your question
A service enquiry concerns something this portal can investigate, such as a broken link, a misleading label, a planning feature or an unclear explanation. A programme enquiry concerns the provider's own rules or decisions. Keeping these separate helps you reach someone able to act. If you are unsure which route applies, ask whether the answer would require access to a provider's application system or authority over its funding rules.
StudyAid ZA cannot look up an NSFAS application, approve a bursary, extend a provider's deadline or confirm that a university received your documents. Use the official provider website for those tasks. When contacting a provider, identify the current application cycle and use its authorised support route. You do not need to send a copy of that conversation or your application evidence to this portal merely to use its directory.
Send a useful correction report
For a factual correction, identify the StudyAid ZA page and the particular wording or date that appears wrong. Include a link to the current official source if you have one. Explain whether the issue concerns the academic year, applicant category, deadline, coverage or destination link. A report that names the exact difference is easier to assess than a general statement that an entire programme listing is outdated.
Do not assume that an older official document proves a current notice is wrong. Compare the study year and publication context first. Where two current official sources conflict, describe the conflict rather than choosing a date without explanation. Your report can make the uncertainty visible for review, but the provider still needs to resolve its own instructions. Until then, avoid making a time-sensitive application decision based solely on a portal summary.
Describe a technical problem clearly
If a feature is not working, say which page you were using, what you selected and what you expected to happen. Include the visible error wording if it contains no private information. Device type and browser name can help explain a display or storage issue. You do not need to provide passwords, sync keys, screenshots of private accounts or complete browser history to describe a website problem.
For a planning issue, explain whether it concerns the local browser copy or an optional manual save or load. Describe the sequence of actions without including the bearer key itself. If a revision conflict appears, mention that wording and whether another device recently saved changes. This helps distinguish a protection against overwriting from a failed save. Preserve important application references separately while any technical issue is being considered.
What the enquiry form asks for
The form asks for an email address, topic, message and explicit consent to send the enquiry for handling. A name is optional. Use the message to explain the service issue and provide the page or official link relevant to it. The form has no attachment feature. It is not intended for applications, supporting evidence or a collection of identity records, even when your question relates to study funding.
Check your email address before submitting if you want the operator to have a way to contact you. Providing an address does not subscribe you to updates or create an account. Consent is part of submitting this particular message; it is not permission for an unrelated mailing campaign. If you do not wish to provide enquiry details, you can continue reading the public pages and using official provider links without sending the form.
Keep private application evidence out
Do not include an identity number, bank account details, login credentials, a private sync key or copies of financial and academic records in an enquiry. A concise description of the issue is normally enough. For example, a broken upload button belongs with the programme operating that application portal, while a wrong link on StudyAid ZA can be reported by naming the directory entry and the intended official destination.
If you want to ask about privacy, describe the feature involved and quote an existing enquiry reference where relevant. Do not send identity documents to prove a request unless a necessary, proportionate verification approach has first been explained. The contact form is not a secure substitute for a provider's formal application channel, and sending private records here will not move an application forward or create a funding case.
Understand the reference receipt
After a successful submission, the page provides a reference receipt. Save that reference in your own records if you may need to follow up or ask about the message later. It identifies the enquiry for service handling; it is not a bursary application reference or proof that a funding body received anything. If the form reports a failure, do not assume the message has been accepted merely because you completed the fields.
There is no automatic email receipt. The email address you enter is available for operator handling of the enquiry, but an immediate message will not arrive from a connected mailing system. No response time or reply is guaranteed. If your issue has an application deadline, act through the official provider in parallel rather than waiting for a response from this portal before protecting your application position.
How messages are reviewed and retained
Enquiries are stored outside the public web root for operator review through cPanel. This means they are not intended to appear as public website pages or directory entries. Access for service handling is different from publishing your message. Nevertheless, keep what you submit proportionate to the issue, because a short useful enquiry creates fewer unnecessary private records than a complete history of your funding circumstances.
The service targets a ninety-day retention period for enquiries. Cleanup is triggered by new submissions, so it is not a promise that every record disappears at an exact clock time on its ninetieth day. Hosting technical logs are separate from the message store and may follow the hosting provider's own handling. Read the privacy page for the distinction between enquiry records, optional planning sync and aggregate page counting.
Privacy requests and follow-up
Use the same form for a request about your enquiry or another feature of this service. State what you want reviewed, such as access to an enquiry, correction of a detail or removal of a message. Quote a previous reference when available and describe the feature involved without attaching identity records. The operator may need enough context to locate the record and understand the request before taking an appropriate action.
For a synced plan you control, use the explicit server-plan erase action when you want the server copy deleted. Clearing local browser data alone does not do that. If you lost the private key, explain the situation without assuming the service can recover access by email; the sync feature has no email account or recovery process. The form provides a route to raise an issue honestly, while the available action depends on the records and access involved.
CONTACT THE WEBSITE OPERATOR
A clear question is a good start.
Use this for website feedback, corrections or a privacy request. For a funding decision or application status, contact the official provider directly.
This page explains how to use information and organise your next step. An organisation’s current application instructions and written agreement determine its own requirements.