Verified Botswana facts
Give readers a recipient-first permission map that minimises disclosure and preserves control without suggesting that more access improves approval chances.
Evidence and limits
A verified provider channel, visible request, relevant purpose and responsible privacy explanation must align before a permission is granted.
Questions before signing
Copied branding, broad device access or a false upload destination can expose identity, relationships, location and account data before fraud is noticed.
Decision worksheet
Verify the service outside the app, challenge each permission, protect authentication secrets and withdraw or report access that lacks a supported purpose.
Find the legal provider before entering the app
Find the legal provider and official contact through an independently verified path. Compare developer or publisher name, complete domain, service name and destination with information controlled by that provider. The Bank of Botswana licensed-bank page can assist with the narrow legal-name question for banks; it does not approve software or links. A message that knows personal details is not proof of authority. Do not install, sign in, upload documents or send money while identity is unresolved. Record the verified route privately so a later replacement link can be checked against it.
List every door the app asks to open
List identity fields, contacts, call information, messages, location, photos, files, camera, microphone, account data and device permissions separately. Capture when the request appears and whether the app can continue without it. Do not grant a bundle merely because the operating system presents one button. A permission name may be broad, so ask what information is actually collected. Keep passwords, PINs, one-time codes and account access outside this list because they should never be shared as application evidence. Unknown access remains closed.
Attach a stated purpose to each requested permission
Write the provider's explanation beside the door and compare it with the named application stage. Camera access for a user-initiated document capture differs from continuous access; location used for one stated check differs from background tracking. Do not invent a helpful purpose where none is supplied. Ask whether a less intrusive method is available without assuming it must be accepted. Granting unrelated access does not demonstrate honesty, affordability or eligibility. If necessity cannot be explained by the responsible service, keep the door shut and pause the application.
Identify every recipient and onward route
The provider name on screen may not reveal who stores, verifies or receives the data. Look for responsible disclosures about recipients, service providers, location and retention. Authenticate a third-party verification step before following it. Do not send the same identity file to several addresses to overcome a failed upload. Record only the recipient and purpose in the control map, not the private contents. Where onward sharing or ownership is unclear, label it unresolved. Convenience does not justify exposing a household's information to an unknown chain.
Keep financial display values in their proper lane
An app may display an amount, instalment or other financial figure before a formal proposal exists. Note whether the value is an input, illustration, estimate or written term. Use Botswana pula and BWP only when that denomination is stated; the Bank of Botswana currency page cannot assign currency to a private screen. Do not treat a colourful number as approval or availability. Fees, insurance, term and total payment remain unknown until responsible evidence establishes them. Price questions belong in a separate proposal review, not in the decision to grant device access.
Protect authentication secrets and live account control
A legitimate application question does not require the reader to reveal a password, PIN, one-time code or remote account control to Credizen or an unverified person. Confirm any account-linking process directly with the responsible institution and understand what authority it grants. Do not read a code aloud to somebody who initiated an unexpected contact. If credentials were exposed, use the institution's independently verified security route promptly and record the incident without circulating the secret again. Application urgency is never a reason to surrender authentication.
Note each permission decision and withdrawal route
Note the permission, purpose, recipient, date, duration and method for changing the choice. A ticked box should not become a forgotten permanent state. Review operating-system and in-app settings after the relevant task is complete. Withdrawal may affect a service, so check the responsible explanation rather than promising that nothing will change. Revoking device access does not necessarily erase data already sent; ask how retention and deletion requests are handled. Keep acknowledgements privately and never send the underlying identity or account files to Credizen.
Use the emergency shutoff when signals conflict
Stop when legal identity, destination, purpose, permission scope or financial wording conflicts. Close the app, preserve non-sensitive evidence such as the public address or screenshot context, and contact the institution through a route found independently. Do not continue merely to see whether approval appears. If money or credentials may be at risk, use the appropriate provider security and complaint channels. The Bank of Botswana consumer information may help frame a bank complaint within its stated scope, but Credizen cannot investigate an account or reverse a transaction.
Close the audit before resuming the application
Mark each door allow for one supported purpose, deny, revoked or unresolved. Confirm that the remaining access matches the current stage and authenticated recipient. Recheck the official channel immediately before transmitting documents. A clean audit does not prove that the service is affordable, suitable or likely to approve the request; those decisions require separate written evidence and household review. Resume only when identity and handling are clear. Otherwise preserve the stop decision and consider an alternative verified channel rather than weakening the control map.