Loading Engineer Africa…
Local leadership. Shared possibility.Sign in
Loading Engineer Africa…
PRIVACY NOTICE · OCTOBER 27, 2026
This notice explains the information used by the Engineer Africa website and Engineering Lab. Questions and requests can be sent to contact@engineerafrica.org.
We store your profile, participation preferences, group requests, project applications, discussions and shared resources to help you take part. Public directory visibility is optional. Self-described skills are separate from reviewed qualifications. Project and organization access depends on an explicit role; an account does not grant access to private work.
Public enquiries contain the name, email, location or organization and message you choose to submit. They are stored privately for authorized reviewers. A secret receipt is saved in the submitting browser tab. Linking an enquiry to an account requires that receipt and verification of the same email address. Review notes are not public. Do not include sensitive personal data or community information you lack permission to share.
Newsletter signup is separate and optional. When available, it saves your consent and queues a confirmation email through Resend. You are subscribed only after you confirm the emailed link. We retain your subscription choice and confirmation date. The link can also unsubscribe you. Ordinary enquiry submission does not add you to a newsletter. Transactional messages and marketing choices are separate.
Contact us to request correction, deletion or account assistance. Some records may need to be retained for financial, legal, security or project accountability purposes. We will explain any applicable retention need when handling your request.
When optional analytics is configured and you allow it, server-verified actions can be measured using random identifiers. A completed donation includes its actual currency and amount and an opaque reference to prevent duplicate reporting. Messages, donor names, email addresses and private resource contents are not included. Declining analytics does not prevent participation or giving. Test and staging environments do not send production analytics.
Course discovery is public. An account is required for practice activities, assessments, saved work and participation, including free activities. Supabase processes your email address and sends a sign-in link. Authentication cookies maintain your session. Signing in with that link verifies access to the email address; it does not verify professional qualifications.
The practice lab stores your drafts, active lesson, completion evidence and up to 12 recent runs in your account so you can return on another device. Runs include practice requests, expectations, simulated responses and results. The server recomputes practice evidence and keeps save timestamps, revisions and request identifiers for recovery and abuse controls. Use examples rather than real customer information, passwords, private API keys or confidential code.
If you used an older browser-only version, you can explicitly import your own draft text after signing in. Existing account drafts are preserved when versions differ. Old browser completion claims, discovery flags and run reports are not imported as evidence. The old browser copy remains until you clear it yourself. New unsaved lab edits remain in the open page; a failed save is displayed and can be retried. Check that your work is saved before leaving.
Clearing browser data does not delete your account records. Reports you download remain in the download location until you remove them. Account information is used to provide access, associate records with the right learner and respond to support requests. See Supabase's privacy policy for information about its processing.
Onboarding is optional. If you provide a name, country, education or career stage, interests, skill level or goals, these fields are saved privately to personalize your learning. A temporary draft may be saved in this browser when an account save is interrupted. It is removed after a successful save or sign-out.
For skills assessments, we store your attempt, assigned questions, submitted answers, timestamps, score and feedback. These records support resuming an attempt, enforcing attempt limits and showing your history. Unsaved answers are also backed up in the current browser tab, associated with your account and attempt, so you can recover them after navigating away. This tab draft is removed after a successful save or when the tab's session storage is cleared. Course progress is a learning record, separate from assessment achievement.
Achievement credentials are private by default. If you enable sharing, anyone with the verification link can see the achievement, issue date, status and any display name you explicitly choose to publish. It does not reveal your email or answers. You can turn sharing off and contact us to request review or revocation of a credential. Previously saved copies or screenshots cannot be recalled.
When purchases are available, payment details are entered on the payment provider's hosted checkout (PayPal, Stripe, or Paystack when shown). Engineer Africa receives the payment status, purchase identifiers and information needed to associate purchased credits with your account. The website does not collect or store full card numbers.
Payment and credit records help us deliver purchases, reconcile balances, investigate errors and handle refunds. PayPal describes its processing in its privacy statement. Stripe handles information according to its privacy policy. Paystack explains its processing in its privacy notice. Paystack checkout in this release is limited to clearly labeled test transactions. A checkout marked unavailable does not take a payment.
You can make a one-time donation without an Engineer Africa account. The payment provider shown at checkout handles payment and payer details and issues its payment receipt. Stripe describes its processing in its privacy policy; PayPal donations remain covered by its privacy statement. We store the donation amount and currency, your privacy choice, checkout and payment references, payment, refund and dispute status, and relevant timestamps in our application database. For a campaign donation, we also retain the campaign purpose and terms shown for that donation. These records support payment verification, receipt recovery, recordkeeping and donation support.
The current browser tab saves a checkout identifier, a private receipt secret, the amount and your privacy choice in session storage. The identifier and secret let that tab retrieve the saved donation and continue its checkout. Our database stores a hash of the secret for verification. This storage is essential to guest receipt recovery and is separate from optional analytics. Clearing the tab's session storage removes that browser reference; it does not delete the donation records held by Engineer Africa or the payment provider. If the reference is unavailable, use your payment receipt when contacting us for help.
If you are signed in when you start a donation, we associate it with your account. Guests can later choose to link their saved donation after signing in with a verified email address. We record the “Keep my donation private” choice. Donor names and contact details are not published automatically, including when that choice is unchecked.
Monthly donations require an Engineer Africa account with a verified email address. Stripe or PayPal, as shown when you set up the donation, handles your recurring payment authorization and payment details. We associate the monthly donation with your account and store its amount, currency, privacy choice, subscription and plan references, payment provider and merchant identifiers, status, billing and cancellation timestamps, and verified payment, refund and dispute history. These records let you manage your monthly support and help us reconcile payments and investigate problems. Donation history is available through the account that started it. Donor names and contact details are not published automatically.
The current browser tab saves a monthly checkout request identifier, amount, privacy choice and account identifier in session storage to recover an interrupted request without starting a duplicate. Monthly history is also saved with your account. Clearing browser storage or signing out does not cancel a monthly donation or delete its records. See our payment and cancellation information for how to stop future payments. Cancelling does not automatically delete the history of earlier donations.
If the AI explanation feature is available and you submit a request, your question and relevant lesson context are sent to the configured Microsoft Azure AI service to generate a response.
Our application database stores the request identifier, a hash of the question and lesson identifiers, the generated answer, request status, and creation and completion timestamps, associated with your account. We also record the model, available token counts, and cost estimates for usage limits and Engineer Africa cost attribution. Missing provider usage is recorded as unknown. It also stores credit reservations, charges and returns in your credit history. This lets us enforce limits, account for credits and recover a saved answer when a response is interrupted. The original question text is not stored in our application database, although an answer may repeat information from it.
The free simulator does not require an AI request. Keep personal and confidential information out of questions. Microsoft describes its service processing in its Azure AI data privacy documentation. We do not promise that external processing occurs in your country.
Optional usage measurement sends limited events to Google Analytics only when configured and you opt in using the site's analytics control. We do not load third-party analytics scripts or send private page addresses, credential tokens or marketing referrers through this analytics path. These events help us understand visits and meaningful learning actions, such as completion of the free lab. You can use the free lab without opting in and can change your choice using that control.
Advertising measurement is off until you separately choose “Allow advertising measurement.” Your previous analytics choice does not enable it. When configured and allowed, a separate public page loads the Google Ads tag to save an ad click or measure a server-verified completed donation or community registration, then returns you to the site. It uses Google click identifiers, first-party advertising cookies, an opaque reference and the actual amount and currency for a completed gift. Google also receives browser and network information. We do not configure enhanced conversions, send names, email addresses or form answers, or enable remarketing or personalized advertising.
The tag runs on this separate public document, not inside the account or workspace application. We omit private page addresses, checkout secrets and account identifiers from its address, referrer and event payload. The page shares the site’s origin and is not a security sandbox: like other scripts on that origin, the Google tag has browser permission to access origin storage. You can decline or withdraw using “Advertising privacy choices”; withdrawal prevents new advertising events and removes the first-party linker cookies we can control. Previously sent information remains subject to Google’s policies. Blocking scripts, declining consent or leaving before measurement completes can prevent attribution without affecting your donation or participation.
Measurement events are not intended to include email addresses, names, submitted answers or private account content. Google's handling of information is described in its privacy policy. Essential session storage and saved account work operate separately from optional analytics.
If you email us, we receive the address, message and attachments you choose to send. Our hosting and infrastructure services may process technical request information, such as IP addresses and error logs, to deliver the site and diagnose problems.
We share information with the services needed to provide the features you use. We do not sell learner information or send it to Zof or another learning platform as part of this lab.
Legacy browser drafts remain on that device until they are cleared. Account, support and transaction information is retained as needed to provide the service, handle requests and meet applicable recordkeeping obligations. This notice does not promise automatic deletion after a fixed period.
You can ask to access, correct or delete information associated with your account by emailing us from the account address. We may need to verify the request. Some transaction or security records may need to be retained; we will explain any limits that apply. Clearing browser data or signing out does not itself delete your account.
For a request about a guest donation, email contact@engineerafrica.org with the payment-provider transaction reference or donation reference so we can locate the record and verify your request. Please do not send your browser's private receipt secret, passwords or payment credentials.
We will update the date on this notice when the described practices change. Please review it before using a newly introduced feature. For help, visit our contact page.