Privacy Policy — CEDA Innovation Management Portal prototype
Effective date: 12 November 2026
Policy version: 1.0
Prototype developer and privacy contact: Bokang Jobe, independent software developer, Botswana
Telephone: +267 76776814
1. Important notice — demonstration only
This Privacy Policy applies to the independently developed CEDA Innovation Management Portal demonstration at:
The public preview is not approved for real applicant or CEDA operational information. Use fictional test data only. Do not enter real names, personal contact details, identity or passport numbers, personal financial information, business-confidential information, real funding applications, evaluator notes, credentials or actual supporting documents.
The portal is currently an open prototype. Workspace roles and descriptions are not enforced as production permissions. The preview has a separate D1 identity database path for test-account and onboarding records; it is not a central applicant-application database or a private production document-storage service.
2. Who operates this prototype?
The prototype was independently designed and developed by Bokang Jobe, who currently publishes and maintains the public demonstration for evaluation and feedback. Bokang Jobe is an individual developer; this notice does not represent him as an incorporated company or as CEDA's appointed service provider, data protection officer or processor.
The prototype is not an official CEDA portal and is not represented as commissioned, operated, approved or endorsed by the Citizen Entrepreneurial Development Agency (CEDA). CEDA has not, by virtue of the prototype being available, assumed responsibility for data submitted to the demonstration.
If CEDA later adopts the solution or determines the purposes and means of processing information in a production service, the parties must document the correct controller and processor roles, lawful instructions, responsibilities and public-facing privacy notice before live information is processed.
This notice does not replace any privacy notice that CEDA may publish for its own official services.
3. What information may be processed?
3.1 Browser-local demonstration records
The current workspace preview stores most demonstration records in the browser. Depending on the workspace, these can include fictional organisation names, sample contact fields, innovation descriptions, funding amounts, application stages, role labels, test assessment scores, panel outcomes and sample workflow notes.
The workspace uses browser localStorage for demonstration state. These records are stored against the browser profile and website origin used to access the preview. They are not a central CEDA application record and are not automatically visible to CEDA or to another user on a different device.
3.2 Demonstration documents
The applicant document preview uses the browser's IndexedDB storage. The local document store can contain a file Blob and associated metadata such as file name, content type, file size, application reference, requirement reference and upload time.
These files remain in the current browser's site storage. They are not uploaded to a CEDA-controlled private evidence repository by the current preview. Other people who can access the same browser profile or device may be able to access browser-local demonstration records. Clearing browser/site data, changing browser profiles or using another device may make locally stored records unavailable.
3.3 Technical and hosting information
The portal and documentation are hosted using Cloudflare services. As part of providing network delivery, security and diagnostics, Cloudflare may process technical connection and request information, which can include an IP address, request time, browser or device information, requested URL and security or diagnostic events. Cloudflare processes this information under its own service terms, privacy documentation and account configuration.
The prototype developer does not make a guarantee that all infrastructure processing or logs remain in Botswana. Exact provider-side processing locations and retention are subject to Cloudflare's current services, settings and applicable terms. Review Cloudflare's Privacy Policy for provider information.
GitHub is used for source-code management and build/deployment workflows. It is not the intended repository for applicant records or uploaded prototype documents.
3.4 Identity and onboarding records
The preview deployment is configured to provision a Cloudflare D1 database named ceda-identity-preview for the separate identity-service implementation. When the database migrations have been applied and the identity endpoints are operating, this database may store fictional test-account information such as a user's name, email address, username, role and workspace assignments, account and onboarding status, invitation metadata, session metadata and identity audit events.
Passwords are processed by the identity service using a salted password hash; the raw password is not stored as a database value. Invitation and session tokens are generated as random values and stored in the database as hashes. An invitation token may be returned once to the authenticated person creating the invitation so it can be delivered to the intended test user. The identity API does not itself send invitation email.
The D1 identity database is centrally hosted through Cloudflare and is separate from the browser-local application and document stores. Use fictional names, addresses and email addresses for all test accounts. Do not use real applicant, staff or evaluator details. The identity database has no published automatic purge period at this prototype stage; test identity records may remain until they are manually cleared or the preview database is reset.
3.5 Cookies and session information
When the identity sign-in flow is configured and used, the portal may set a first-party cookie named ceda_identity_session. It is an authentication/session cookie, not an advertising cookie. The cookie is configured as HttpOnly and SameSite=Lax, and Secure when the request uses HTTPS. Its default lifetime is seven days; the server can be configured for a period between one and thirty days. The matching session token is stored in D1 as a hash rather than as the raw cookie token. Signing out revokes the matching session record and clears the cookie.
The public preview's workspace navigation remains open by default, and the existence of an identity database or sign-in screen does not mean that every workspace route is protected by enforced role-based access.
3.6 Direct communications
Where you contact Bokang Jobe by telephone or another communication channel, the information you choose to share may include your name, contact details, question, feedback or information needed to respond. Do not send identity documents, passwords, confidential applicant files or sensitive personal information through an ordinary telephone or messaging conversation.
4. Why is information processed?
Information is used only as needed to:
- make the demonstration and its user guides available;
- let a visitor explore and test the prototype using fictional records;
- diagnose errors, maintain service security and prevent misuse;
- respond to questions, technical feedback or policy requests sent directly to the developer; and
- document and improve the prototype using non-confidential test feedback.
The prototype is not intended to make a real eligibility, evaluation, adjudication, lending, funding or other decision about any person or business. It is not used by the developer to create advertising profiles or to make decisions about users based on personal characteristics.
5. Legal basis and data minimisation
Botswana's Data Protection Act, 2024 (Act No. 18 of 2024) requires personal-data processing to have a lawful basis and to be lawful, fair, transparent, purpose-limited, proportionate and secure. The Act came into operation on 14 January 2025.
The prototype is deliberately restricted to fictional test data so that it does not become an unintended collection point for real applicant information. If the service is redesigned to process real personal data, the responsible controller must identify and document the applicable lawful basis before collection. Consent will not be treated as a blanket substitute for any other legal or governance requirement.
6. Where is information stored?
- Workspace demonstration records: browser localStorage on the device and browser profile used for the preview.
- Local document demonstrations: browser IndexedDB on the device and browser profile used for the preview.
- Identity and onboarding test records: the Cloudflare D1 database
ceda-identity-preview, when its migrations and service binding are active. - Session information: a first-party browser cookie and hashed session record in D1, when sign-in is used.
- Infrastructure metadata: Cloudflare systems, subject to Cloudflare's platform settings and terms.
- Direct communications: the communication channel and device used by the person contacting the developer.
The preview deployment includes a D1 identity database path for test accounts, invitations, sessions and identity audit records, subject to successful migration and binding. It does not provide a central production applicant-application database or a private CEDA evidence-object store. Funding-evidence metadata schema foundations exist in the source project, but the public preview does not provide the private object-storage adapter and production evidence endpoints required for live supporting documents.
7. Sharing and disclosure
Bokang Jobe does not sell personal information collected through direct communications. Browser-local sample records are not intentionally shared with CEDA by the preview as a central application record.
Technical information may be processed by Cloudflare to deliver and protect the hosted service. Information may also be disclosed where required by applicable law or a valid legal process, or where reasonably necessary to investigate misuse, protect the service or protect the rights and safety of others.
Any future CEDA production deployment must document its own recipients, processors, sub-processors, written processing terms and disclosure rules.
8. International transfers
Cloudflare is an external hosting provider. Its infrastructure may process technical information in locations outside Botswana. The developer does not promise that all technical information is stored or processed exclusively in Botswana.
The Data Protection Act, 2024 contains requirements for transfers of personal data to third countries and international organisations. Before a production service transfers real personal data outside Botswana, the responsible controller must assess and implement a lawful transfer mechanism and any required safeguards. A production data-residency arrangement must be agreed with CEDA and the relevant hosting providers; no such CEDA-approved arrangement is claimed by this prototype notice.
9. Retention and deletion
- Browser-local demonstration records remain in the browser until they are removed by the user, browser storage is cleared, or the relevant application code removes them. The developer cannot remotely guarantee deletion of data stored only in your browser.
- Local document Blobs remain in IndexedDB until removed by the application or browser/site storage is cleared.
- D1 identity and onboarding test records may remain until manually cleared or the preview database is reset. There is no published automatic deletion schedule for these test records at this prototype stage.
- Direct communications are kept only for as long as reasonably necessary to respond, maintain a record of the discussion or deal with a legal or security matter.
- Provider-side technical logs are subject to the relevant hosting provider's retention controls and terms; the developer does not promise a specific provider log-retention period.
Do not use the prototype as a records archive or as the only copy of any information.
10. Security and prototype limitations
Reasonable measures are used to maintain the demonstration, but this is not a production security environment. In particular:
- preview access is open and workspace navigation is not an enforced role-based access boundary;
- browser localStorage and IndexedDB are not a secure document vault and are not encrypted by this application as a production evidence-storage control;
- the D1 identity database is a preview account store, not a CEDA-approved production identity service or a complete account-governance solution;
- the demo does not provide production-grade identity verification, central account governance, private evidence storage, formal records management or an approved incident-response service;
- public access to the same browser profile or device may expose locally stored test data; and
- third-party hosting-provider systems are governed by their own security controls and terms.
The prototype must not be used to store real personal data or confidential business information.
11. Your privacy rights and requests
The Data Protection Act, 2024 provides rights that may include access, rectification, erasure, restriction, data portability, objection and protections relating to certain automated decisions, subject to the conditions and exceptions in the Act.
To raise a privacy question or make a request about information directly handled by the prototype developer, contact:
Bokang Jobe
Telephone: +267 76776814
Please identify the relevant page or interaction and describe your request. Do not send a copy of an identity document unless a secure and proportionate verification method has first been agreed. The developer will assess the request, verify identity where reasonably necessary, and respond in accordance with the applicable law and the actual data locations.
If your concern relates to information held by CEDA in an official process or by another organisation, contact that organisation directly. You may also seek guidance or lodge a complaint with Botswana's Information and Data Protection Commission through its official channels.
12. Personal data breach
If you believe that real personal information has been exposed through the prototype, stop using the relevant workspace and contact Bokang Jobe at +267 76776814. The developer will assess the report, take reasonable steps within the systems under his control and cooperate with the relevant responsible controller or service provider.
Where the Data Protection Act's statutory conditions apply, the responsible data controller must notify the Commission without undue delay and, where feasible, within 72 hours of becoming aware of the breach; communication to affected data subjects may also be required where the statutory high-risk threshold is met. This notice does not claim that the developer can perform actions on behalf of CEDA or a hosting provider.
13. Children
The demonstration is not designed for children under 18. Do not submit children's information or use this open prototype as a service for children.
14. Changes to this notice
This notice may be updated when the prototype changes, hosting arrangements change, or the parties agree a different operational model. The current version and last-updated date will be shown at the top of this page. A production deployment must have a separately reviewed privacy notice reflecting the actual controller, processors, purposes, lawful bases, data locations, retention schedule and rights-request arrangements.
15. Legal references
This policy is intended to be read consistently with applicable Botswana law, including:
- Data Protection Act, 2024 (Act No. 18 of 2024) — including sections 19–25 (processing principles), 26–29 (lawful basis and consent), 37–49 (data-subject information and rights), 51–64 (controller/processor responsibilities and security), and 74–78 (international transfers).
- Data Protection Act (Date of Commencement) Order, 2025, S.I. No. 4 of 2025 — commencement on 14 January 2025.
This is a prototype-stage privacy notice for transparency and review. It is not a legal opinion, a compliance certification or a substitute for review by a Botswana-qualified legal practitioner and, where applicable, the responsible data protection officer.