ST-DITTI SOLUTIONS LIMITED
PAASHCASH
DATA PROTECTION POLICY
NIGERIA
Document status: Approved
Organisation: ST-Ditti Solutions Limited
Product/platform: PaashCash
1. PURPOSE
This Policy establishes how ST-Ditti Solutions Limited (“ST-Ditti”) manages and protects personal data processed through PaashCash. It is designed to support compliance with the Nigeria Data Protection Act 2023 (“NDPA”), applicable regulations and guidance, contractual obligations and relevant sector requirements.
PaashCash provides or intends to provide travel-related services, including connections with travel agents and visa-support services, and digital transaction services such as utility bill payments, airtime purchases, mobile-data purchases and, where available and legally permitted, payments to participating betting or gaming platforms.
2. SCOPE
This Policy applies to directors, employees, contractors, temporary staff, consultants and service providers who access or process personal data for ST-Ditti or PaashCash. It covers paper and electronic records, customer communications, travel documents, account data, payment and transaction data, system logs and support records.
Every worker must follow this Policy and any supporting security, incident-response, acceptable-use, retention and access-control procedures.
3. GOVERNANCE AND RESPONSIBILITIES
3.1 Board and senior management
Senior management is accountable for ensuring appropriate resources, oversight and risk management. Management must approve material policies, assign responsible officers, review significant incidents and ensure that compliance is reflected in product decisions.
3.2 Policy owner / privacy lead
The company will appoint a responsible privacy lead and, where required by law or risk, a Data Protection Officer or other qualified support. The named owner will coordinate data inventories, privacy notices, rights requests, vendor reviews, training, breach assessments and compliance records.
3.3 Product and engineering
Product and engineering teams must build privacy and security into design and changes, restrict production access, protect credentials and secrets, document data flows, test security controls and avoid using real customer data in development or testing unless appropriately authorised and protected.
3.4 Operations and customer support
Operations and support staff must verify identity before disclosing account or transaction information, use approved systems, keep case notes factual and limited, avoid unnecessary downloads and escalate suspected fraud, privacy requests or incidents promptly.
3.5 Finance and transaction operations
Staff responsible for payments and reconciliation must access only the information required for their duties, use approved provider dashboards, reconcile transactions securely, protect transaction references and escalate discrepancies. No staff member may request or record a customer’s PIN or one-time passcode.
3.6 All personnel
All personnel must maintain confidentiality, complete assigned training, use approved devices and systems, report suspected incidents immediately and access personal data only for authorised business purposes.
4. DATA PROTECTION PRINCIPLES
Personal data must be:
-
processed lawfully, fairly and transparently;
-
collected for specified and legitimate purposes;
-
adequate, relevant and limited to what is necessary;
-
accurate and kept up to date where necessary;
-
retained no longer than necessary, subject to legal obligations;
-
protected by appropriate technical and organisational safeguards; and
-
processed in a manner that enables the company to demonstrate accountability.
5. DATA INVENTORY AND LAWFUL PROCESSING
The privacy lead, with product and operations owners, must maintain a record of processing activities identifying at least:
-
categories of individuals and personal data;
-
purposes and lawful bases;
-
collection points and data flows;
-
recipients and processors;
-
hosting and transfer locations;
-
retention criteria;
-
security measures; and
-
relevant risks and mitigations.
Before a new feature, vendor or use of data is launched, the responsible team must consult the privacy lead to confirm the purpose, lawful basis, notice, data minimisation and any need for consent or a data protection impact assessment.
6. SERVICE-SPECIFIC CONTROLS
6.1 Travel and visa-support data
Passport copies, identity documents, travel itineraries and visa-support documents must be treated as restricted-access data. Access should be limited to staff and the travel agent or provider who needs the information for the user’s requested service. Documents must not be sent through personal email accounts or unapproved messaging channels. Where feasible, use secure upload and sharing methods, record disclosures, and delete documents in accordance with the approved retention schedule.
6.2 Payment and transaction data
Transaction records must be protected against unauthorised access, alteration, loss or disclosure. Staff must use unique accounts, strong authentication and role-based permissions. Transaction investigations must be logged and limited to the necessary details. Sensitive authentication information, including PINs, passwords and one-time passcodes, must not be stored in support tickets, logs or spreadsheets.
Where payment services are provided by an external provider, ST-Ditti must document the provider’s role, security responsibilities, escalation path, reconciliation data and incident-notification process.
6.3 Utility bills, airtime and mobile data
Only the customer or account identifiers needed to fulfil, verify and support the requested transaction should be collected. Screenshots, bills and recipient details must not be retained in personal devices or informal chat groups unless explicitly authorised under a controlled process.
6.4 Betting/gaming-related payments
Before enabling any betting or gaming-related payment feature, management must obtain legal advice on the applicable licensing and regulatory position for the relevant jurisdictions and confirm that each participating platform and payment partner is appropriately authorised. Data must be limited to that needed to process and reconcile the transaction, prevent fraud, meet legal requirements and resolve disputes. PaashCash must not represent itself as a betting operator unless that is its actual, lawfully authorised role.
6.5 Customer support and complaints
Support staff must verify a requester’s identity before sharing account or transaction information. Requests for access, correction, deletion, objection or other privacy rights must be routed to the privacy lead. Complaints about failed or duplicate transactions must be documented with a transaction reference and shared only with providers who need the information to investigate.
7. ACCESS CONTROL AND CONFIDENTIALITY
The company must implement and periodically review:
-
role-based access based on least privilege;
-
unique user accounts and strong authentication, including multi-factor authentication where appropriate;
-
timely access removal when staff leave or change roles;
-
periodic review of privileged and production access;
-
secure credential and secret management;
-
confidentiality commitments for personnel and contractors; and
-
logging and review of sensitive access and administrative actions where technically feasible.
No employee should approve their own sensitive access request or perform an incompatible combination of duties without documented approval and compensating controls.
8. SECURITY CONTROLS
Controls must be proportionate to risk and may include:
-
encryption in transit and, where appropriate, at rest;
-
secure backups and recovery testing;
-
patching and vulnerability management;
-
endpoint protection and device controls;
-
secure software development and change review;
-
production/development environment separation;
-
logging, monitoring and alerting;
-
restricted data exports and secure disposal;
-
incident-response playbooks; and
-
periodic security testing and independent assessment where appropriate.
The company must maintain evidence of controls and not claim certification or audit completion unless supported by current records.
9. THIRD-PARTY PROVIDERS AND DATA PROCESSORS
Before engaging a provider that will access personal data, the relevant owner and privacy lead should assess its purpose, data access, security, reliability, location, subcontractors, incident response and regulatory standing as appropriate.
Written contracts should address:
-
documented instructions and permitted purposes;
-
confidentiality and security;
-
assistance with rights requests and incidents;
-
subprocessor controls;
-
international transfers;
-
retention, return and deletion at termination;
-
audit or assurance evidence; and
-
prompt incident notification.
A register of relevant providers must be maintained. It should include payment processors, banks, billers, telecom providers, cloud and hosting vendors, identity-verification providers, travel agents, customer-support tools, analytics tools and betting/gaming partners where enabled.
10. DATA SUBJECT REQUESTS
The privacy lead must maintain a process to receive, verify, assess, respond to and record requests under the NDPA. Requests must be handled within applicable legal deadlines. Identity verification must be proportionate and must not create unnecessary barriers.
If a request affects data held by a processor or partner, the privacy lead must coordinate with that party. Any refusal, extension or limitation must have a lawful basis and be documented.
11. DATA RETENTION AND DISPOSAL
The company must maintain a retention schedule approved by management and legal counsel. The schedule should distinguish:
-
account and profile information;
-
identity and visa-support documents;
-
transaction, accounting and reconciliation records;
-
support cases and complaints;
-
security logs and fraud investigations;
-
marketing preferences and consent records; and
-
employee/vendor records.
Records must be securely deleted, anonymised or destroyed when no longer needed, unless a legal hold or mandatory retention rule applies. Retention must not be indefinite by default.
12. PERSONAL DATA BREACH AND SECURITY INCIDENT RESPONSE
All personnel must report suspected loss, unauthorised access, disclosure, alteration, malware, account compromise or misdirected communication immediately to support@Paashcash.com.
The incident-response lead must:
-
Record the time, systems, data and people potentially affected.
-
Take proportionate steps to contain the incident without destroying evidence.
-
Assess the type and volume of data, likely consequences, affected individuals and continuing risk.
-
Involve engineering, management, legal counsel and relevant providers as needed.
-
Document the investigation, decisions, remediation and lessons learned.
-
Determine whether notification to the Nigeria Data Protection Commission, affected individuals, regulators, financial partners or law enforcement is required.
-
Make required notifications within the applicable legal time limits, including the NDPA’s breach-notification requirements where triggered.
-
Track corrective actions to completion.
The company must confirm who has authority to make notification decisions and maintain current contact details for key providers and regulators. Do not delay escalation while trying to prove an incident is serious.
13. INTERNATIONAL TRANSFERS
Before a provider stores or accesses personal data outside Nigeria, the business owner and privacy lead must identify the destination, data types, recipient, transfer mechanism and safeguards. Transfers must comply with the NDPA and applicable requirements. The company must keep records of relevant assessments and contractual protections.
14. TRAINING AND AWARENESS
Personnel must receive privacy and security induction before being granted material access to personal data and periodic refresher training thereafter. Training should cover phishing, passwords and multi-factor authentication, secure handling of passport and payment data, privacy requests, incident reporting, social engineering and approved communication channels. Completion records should be retained.
15. MONITORING, AUDIT AND COMPLIANCE
The privacy lead and relevant control owners should periodically assess compliance with this Policy, review access and vendor records, test incident processes and track remediation. The company must determine with counsel whether it is required to register with the Nigeria Data Protection Commission, appoint a Data Protection Officer, carry out a data protection impact assessment, file compliance returns or undertake independent audits based on its actual processing and legal status.
No employee may promise a regulator, partner or customer that an audit, certification or control exists unless the company has evidence.
16. POLICY VIOLATIONS
Violations may result in access suspension, retraining, disciplinary action, contract remedies or referral to relevant authorities, subject to applicable law and contractual terms. Suspected violations must be investigated fairly and documented.
17. REVIEW AND APPROVAL
This Policy must be reviewed at least annually and whenever there is a material change to services, data flows, legal requirements, providers or security risks.
18. COMPANY CONTACT DETAILS
ST-Ditti Solutions Limited
Product: PaashCash
Website: https://paashcash.com
Email: info@stdtsolutionsltd.com