OBIBA / TRUST
Security
Practical guidance for protecting your account, reviewing payments and reporting security concerns.
Last updated: 16 October 2026
hello@obibajk.com1. Protect your sign-in
Use a strong, unique password wherever a password is required. Keep your account PIN and one-time codes private. Enable the device and account protections available to you, keep recovery information current and avoid using shared devices for financial activity. If an available feature uses native device authentication, review the permission and device settings before enabling it.
2. Check every payment
Confirm the recipient and destination independently, especially after a request to change bank or mobile-money details. Check the amount, currency, fees and network before authorising a transfer. Never send a payment solely because someone creates urgency or claims it is needed to unlock a prize, refund or account.
3. Recognise impersonation
Treat unsolicited requests for passwords, PINs, one-time codes, private keys or remote access as suspicious. Use www.obibajk.com and contact hello@obibajk.com directly rather than following an unexpected message link. A familiar display name, logo or social profile is not proof that a message is genuine.
4. Lost devices and suspected account access
Contact hello@obibajk.com promptly with the subject “Security incident” if your device is lost or you suspect unauthorised access. Secure your email account and contact your mobile operator if your SIM may have been compromised. Include the time and a brief description, but do not email credentials or identity documents. A support request does not itself confirm that an account has been locked or a payment stopped.
5. Payment disputes
If a transaction looks wrong, retain the reference, time, amount and relevant messages, then report the issue. Do not repeat a pending payment to test whether it worked. Recovery depends on the payment rail, status, applicable rules and investigation; no recovery outcome should be assumed until confirmed.
6. Permission and agent safety
Only enable permissions needed for a feature. Where delegation is available, use dedicated budgets, approved recipients and appropriate approval limits. Review and revoke unused permissions. An AI-generated suggestion is not proof of recipient identity, a valid quote or authorisation to move money.
7. Responsible vulnerability reporting
To report a suspected vulnerability, email hello@obibajk.com with the subject “Security vulnerability”. Include the affected page or app version, a description and safe reproduction steps. Do not access another user’s account, extract personal information, disrupt services or conduct unauthorised testing. Stop testing if you encounter personal data and report what happened without sharing that data. Reporting does not imply permission to test or a promise of a reward.
8. Privacy and incident communication
The Privacy Policy explains how to raise information-access, correction and deletion requests. If an incident affects your information, notification and remediation obligations depend on the facts and applicable law. Verify any incident message through the official contact address before following instructions.
9. What this page establishes
This page provides security guidance and reporting routes. It is not an independent audit report, security certification, insurance guarantee or statement of regulatory approval. Specific technical safeguards and provider arrangements must be assessed against the production service; no online service can eliminate every risk.