# TITAN Privacy Policy

Version: 1.3-review · Last updated: 4 November 2026

Effective date: [INSERT EFFECTIVE DATE AFTER BUSINESS AND LEGAL APPROVAL]

Status: Complete review text. The named privacy lead, suppliers and retention periods require confirmation before adoption. Reading or acknowledging this notice is not consent to every processing activity.

## 1. Who is responsible for your information

The controller identified for personal data used to run TITAN is Titan Star Tool Limited, RC9972219, at 2 Olokoro street, Umuahia, Abia, Nigeria. Contact [support@titanstartool.com](mailto:support@titanstartool.com) or [INSERT DATA PROTECTION OFFICER OR PRIVACY LEAD CONTACT]. The company name, contact address and support email are approved details. The company registration number is RC9972219. The named privacy lead remains to be confirmed. You may send privacy enquiries to the support email without signing in.

Account holders can presently submit a privacy enquiry through [Support and disputes](/support), selecting Support request and using a subject such as Privacy — access, correction or deletion. Do not attach identity documents to an ordinary support conversation. If you cannot sign in, the operator must provide a verified alternative contact before public launch; you retain the right to contact the NDPC independently.

TITAN determines how account, platform, security and support data is used for its own purposes. Sellers, independent providers and payment businesses may separately control information they need for their own supply, legal records and disputes. Their actual role must be explained; labelling a party a processor does not make it one. Processors acting only on TITAN's instructions require appropriate written terms and safeguards.

Official policy contact: Titan Star Tool Limited, 2 Olokoro street, Umuahia, Abia, Nigeria. Email: [support@titanstartool.com](mailto:support@titanstartool.com).

## 2. Scope and legal framework

This notice covers visitors, buyers, sellers, vehicle owners, drivers, riders, delivery companies, loaders, team leaders and people contacting TITAN. It also covers relevant information about recipients and authorised representatives supplied by another user. Tell those people that their information has been provided and direct them to this notice.

Nigeria's constitutional privacy protection, the Nigeria Data Protection Act 2023 and applicable NDPC instruments govern relevant processing. The NDPC's 2025 General Application and Implementation Directive must be included in the operator's compliance assessment; the older 2024 draft must not be treated as the final instrument. [NDPC explanation of constitutional and statutory privacy](https://dmc.ndpc.gov.ng/about-us/); [NDPC 2025 annual report confirming the directive](https://ndpc.gov.ng/wp-content/uploads/2026/02/Print_NDPC-Annual-Report-2025-1.pdf).

The account, order, verification, support and location functions described below exist in the current project. Live payments, continuous GPS tracking, behavioural advertising and a dedicated automated privacy-request portal are not active features. Any future use must be assessed and disclosed before introduction.

## 3. Account and contact information

We process names, email addresses, verification state, account identifiers and role applications to create accounts, communicate and authorise access. Passwords are stored as hashes rather than readable account passwords. We may process phone numbers, business addresses and recipient contact details where supplied through the relevant shop, service profile, delivery address or booking.

The principal basis for necessary account and requested service processing is steps requested before a contract or performance of that contract. Security and misuse prevention can rely on a documented legitimate interest where it does not override your rights. A particular statutory record or disclosure relies on the applicable legal obligation, not a generic assertion that all records are legally required.

## 4. Verification, business and vehicle information

Role applications and provider records can include identity evidence, business details, vehicle information, operating coverage, photographs, registration or licence information and verification outcomes. This information is used to assess eligibility, renew expiring documents and protect users against impersonation or unsafe services. Bank-account verification for settlement is a separate process.

Use only the designated private verification upload. We must collect no more information than needed, explain what is mandatory and restrict reviewer access. Necessity for the requested provider relationship and proportionate fraud prevention are the usual bases; a legal-obligation basis applies only where an identified requirement actually applies. Special-category information, biometrics or new identity-provider checks require a separate legal assessment and additional safeguards before use. TITAN does not currently promise biometric identification or comprehensive criminal-record screening.

## 5. Orders, payments and earnings

Order items, quantities, prices, seller and provider identities, bookings, delivery instructions, transaction references, charge amounts, refund requests and payout states support fulfilment, accounting and dispute resolution. The relevant bases are performance of the transaction, identified legal record obligations and proportionate interests in preventing errors and fraud.

Where payment processing is enabled, the selected payment provider handles its checkout and associated payment information. TITAN does not require you to put a full card number, CVV, banking password or OTP in a support ticket or policy record. Settlement records contain information such as account name, bank code, masked account digits and a recipient reference; the necessary account information is used with the provider for verification. The operator must identify its actual payment provider and applicable privacy notice before a real transaction. Current test records do not represent a live-money transaction.

## 6. Addresses and location

We use locations you select, saved addresses, destination zones, service coverage and booking directions to find available services and coordinate an agreed job. This is different from collecting a continuous device-location trail. Exact addresses and recipient details should be shared only when required for the accepted service, not exposed in a public provider directory.

The current website does not operate continuous GPS tracking. If device-location collection is introduced, the operator must first explain the purpose, precision, recipients, duration and relevant lawful basis, request any required browser or device permission and offer a practicable alternative where possible. Permission must not be treated as authorisation for unrelated tracking or advertising. Denying optional GPS permission must not silently authorise another tracking method.

## 7. Technical information and security records

Requests to the website and API may expose IP addresses, browser or device characteristics, timestamps, error information and security events to the server and hosting systems. Session and anti-forgery controls are used to keep sign-in and form submissions secure. Application audit records may record an actor, event, target and time.

Necessary operation and a documented legitimate interest in preventing abuse support proportionate technical processing. The operator must inventory the deployed hosting logs and retention settings; this notice does not assert that every possible technical identifier is retained. Do not place secrets or unnecessary personal data in logs. Persistent advertising identifiers or unrelated profiling must not be added under the label of essential security.

## 8. Support, communications and delivery evidence

Support cases may contain your subject, message, relevant order or charge reference, staff response and outcome. Delivery or work records may include descriptions and photographs showing condition, custody or completion. We use these to respond to your request, establish what happened, protect safety and resolve an actual dispute.

Please avoid unrelated people's faces, vehicle documents, payment details or private conversations in evidence. Redact irrelevant information where appropriate without falsifying the evidence. Staff notes must be restricted and a support conversation must not be made public. A new use such as advertising a delivery photograph needs its own lawful basis and, where appropriate, specific permission.

## 9. Lawful bases and optional consent

We select a basis for each purpose: a necessary requested contract, a specific legal duty, an assessed legitimate interest, valid consent for an optional purpose, or another basis the law permits in the particular circumstances. We must not rely on a broad acceptance checkbox to justify every activity. Vital-interest processing may be relevant to a genuine emergency, rather than routine marketing or convenience.

Where consent is required, explain the purpose and choices, leave the control unchecked, record the decision and make withdrawal as accessible as giving consent. Marketing consent must be separate from account creation, essential service messages and acknowledgement of this notice. Refusing optional marketing must not prevent a necessary purchase or support request. Withdrawal affects future consent-based processing and does not retrospectively invalidate a lawful past use.

## 10. Cookies, browser storage and saved-app files

- **Session and security cookies:** used to maintain sign-in and protect requests from forgery. Blocking them may prevent account operations. Their deployment configuration and lifetime must be included in the operator's cookie inventory.
- **Shopping preference:** the site stores a manually selected shopping location under titan-shopping-location in browser local storage so it can reuse that selection. Signed-in users may also save a preference to their account. Clear it through your browser's site-data controls or change the selected location.
- **Checkout reference:** titan-checkout-key in session storage helps avoid duplicating a checkout submission. It is removed after successful submission; clearing it while a request is pending may make reconciliation harder.
- **Offline application files:** a service worker caches fixed public shell assets such as icons, the logo and the offline page. It is designed not to put personalised pages, APIs or payment records into its shell cache. Remove saved site data or uninstall the saved app to remove the cached files.

No third-party advertising or analytics cookie integration was identified in the reviewed frontend. That finding must be rechecked for the actual hosted deployment, proxy, payment checkout and any later plugins. New non-essential tracking requires a proper explanation and any required prior consent. TITAN cannot control cookies independently set by another site you choose to visit.

## 11. Who receives information

- A seller receives the order and limited customer details needed to fulfil it, handle a legitimate return and keep required records.
- An accepted driver, rider, delivery company or loader receives the job details, relevant contacts and locations needed for that task. Other bidders should not receive unnecessary precise addresses or private documents.
- Buyers receive the provider and service information necessary to make a choice, recognise the authorised person and raise a complaint, rather than unrestricted access to verification files.
- Authorised staff receive information according to their support, verification, moderation or finance responsibilities.
- Payment, hosting, messaging, security and verification suppliers receive data required for their contracted service, subject to their actual controller or processor role. The approved supplier list remains [INSERT CURRENT PROCESSORS, SERVICES AND COUNTRIES].
- Regulators, courts, law enforcement, professional advisers or an insurer may receive relevant information where disclosure is legally justified, necessary and appropriately limited.

We must not sell customer contacts for unrelated marketing. A business restructuring requires a lawful, limited transfer and appropriate information to affected people; it does not erase the purposes and safeguards described here. Verify the authority and scope of an official request rather than treating every request as compulsory.

## 12. Storage, international transfers and processors

Hosting locations, support access locations and sub-processors must be documented before public deployment: [INSERT HOSTING PROVIDERS, DATA LOCATIONS AND TRANSFER SAFEGUARDS]. If data is transferred outside Nigeria, identify an applicable lawful transfer mechanism, assess the destination and recipient safeguards, and give users the required information. Do not assume that a foreign provider is adequate merely because it is well known or uses encryption.

Processor terms should address instructions, confidentiality, security, breach assistance, rights requests, sub-processors, deletion or return and audit arrangements. Transfer assessments and contractual safeguards must be kept under review. A future optional transfer based on consent must explain its specific implications rather than hiding it in general terms.

## 13. Retention and deletion

Keep information only for a documented purpose and justified period. The approved record-retention schedule is [INSERT RETENTION SCHEDULE AND REVIEW OWNER]. The operator must replace this field with category-specific periods or clear criteria before adopting the notice for public service. An unlimited keep-everything policy is not acceptable.

- Account and role records: retain for the active relationship, necessary closure work and an assessed period for legitimate disputes or legal obligations.
- Identity and verification documents: separate the verification result from the underlying document; remove unnecessary copies as soon as the justified verification or legal need ends.
- Orders, invoices, tax and payment records: apply the retention requirements actually relevant to the business and transaction, including the current tax framework and any documented litigation hold.
- Support, safety and fraud records: retain for resolving the case, appeals and a proportionate documented protection or legal need; periodically review sensitive allegations.
- Security logs and browser data: use a purpose-limited technical schedule and practical user controls. Do not retain every log for the lifetime of an account by default.
- Backups: apply a defined rotation and access restriction. A restored backup must not silently reintroduce data that should remain deleted from active use.

Deletion may be limited where a lawful record obligation, unresolved transaction or necessary legal claim remains. Explain the category, reason and review point. Where feasible, de-identify information instead of retaining an identifiable record. Closing an account does not automatically delete all financial or dispute records, and retention does not permit unrelated reuse.

## 14. Your rights and how to request them

Depending on the applicable law and circumstances, you may ask to be informed about processing, access your information, correct inaccuracies, erase information, restrict use, object to processing, obtain portable data where applicable, withdraw consent or challenge qualifying automated decisions. You can also complain to the NDPC and pursue available judicial remedies. These rights are subject to lawful conditions; they must not be dismissed through a blanket refusal. [NDPC rights and objectives](https://ndpc.gov.ng/faqs/).

To make a request, open a Support request at [Support and disputes](/support) and state Privacy — access, correction, deletion, objection or another right. Give the account email and enough detail to locate the data, without disclosing a password, card security code or full identity document. A representative should explain their authority. Requests need not use particular legal wording.

Staff must acknowledge the request, verify identity proportionately through an appropriate private channel, assess the applicable deadline and respond within the time required by law. If clarification, an exception or an extension is legally justified, explain it and the available complaint route. Do not charge a blanket access fee or use excessive identification demands to obstruct a request. Disclose third-party data only where lawful and redact it when necessary.

The existing support system can receive and record a signed-in request; it does not automatically export or erase data. Trained staff must carry out and record the response. A dedicated rights-request workflow and accountable privacy owner remain launch requirements. Locked-out or unregistered people can send requests to [support@titanstartool.com](mailto:support@titanstartool.com). [NDPC contact and resources](https://ndpc.gov.ng/).

## 15. Automated checks and human review

The platform uses rules for eligibility, permissions, availability, duplicate transactions and verification status. A software refusal can result from incomplete or stale information and is not a criminal finding. The reviewed system does not advertise AI profiling or automated credit scoring.

Where a decision based solely on automated processing has legal or similarly significant effects and the statutory protections apply, provide the applicable information and safeguards, including a way to request meaningful human consideration and contest the outcome. Assess new profiling or high-risk processing before deployment; do not introduce it through a silent policy change.

## 16. Security and breach response

Apply security measures appropriate to the risk, including access controls, private document handling, protected transport, secure authentication, auditability and tested recovery. The current code includes password hashing, session controls and CSRF protection, but effective protection depends on correct hosting, staffing and operations. No service can promise that a breach is impossible.

Report a suspected exposure through support or the verified privacy contact as soon as practicable, without redistributing exposed information. The responsible team must contain the incident, preserve relevant evidence, assess the risk, document decisions and notify the NDPC and affected people when required by law, within the applicable statutory deadlines. Suppliers must report relevant incidents promptly enough for the controller to meet its duties. The incident contact and escalation roster must be confirmed before launch.

## 17. Children, marketing and sensitive circumstances

The proposed platform is intended for adults aged 18 or above and does not recruit children for delivery or loading. If children's data is unexpectedly received, restrict use, assess the legal requirements and safely remove or otherwise handle it as required. Do not invite a child to submit additional identity data through a public channel.

Operational messages about an account, order, security incident or dispute are different from optional promotions. TITAN keeps an in-app inbox and can deliver optional account updates through email, browser push and Meta WhatsApp Cloud API when those channels are activated. These preferences are not consent to unrelated advertising. A future promotional programme must explain its channels and withdrawal method before enrolment.

Browser push requires your affirmative browser permission. TITAN stores the subscription endpoint, encryption keys, device subscription identifier and active state to route alerts. Browser and operating-system push services receive the information necessary for delivery. Lock-screen alerts use generic account-update text rather than order contents, addresses, payment amounts or support messages. You can disable alerts for a browser, switch off all browser alerts in your account, or revoke permission in the browser. Installed iOS web apps depend on the platform's Home Screen and notification-permission requirements.

WhatsApp requires a separate opt-in and confirmation from the number you supply. TITAN stores your international phone number, consent and verification times, and a short-lived hashed connection code. You confirm ownership by sending the prepared connection message to TITAN through WhatsApp; requesting a link alone does not enable account messages. Meta processes the phone number, approved message-template content and delivery information under its applicable terms. TITAN checks signed provider callbacks, records delivery state and honours STOP or equivalent supported opt-out replies. You can also turn WhatsApp updates off in your account. These notifications do not authorise marketing, and staff must not solicit account passwords, payment-card secrets or identity documents through notification messages.

The delivery queue records the channel, destination or device reference, limited attempt information, provider message identifier and delivery state. Pending alerts older than the configured delivery window (currently 24 hours) are not replayed indefinitely. This delivery window is not a blanket deletion schedule: the approved retention schedule must also address notification history, delivery records, inactive subscriptions and verified phone data. Disabling a channel stops future queued delivery; a message already handed to its provider may still arrive. Essential verification/security communications may follow a separate necessary-service basis. Confirm the actual SMTP supplier, Meta arrangements, browser-push providers and international-transfer safeguards in the supplier inventory before production activation.

## 18. Changes and accountability

Publish a revised version and explain a material change before relying on it where required. Obtain fresh, purpose-specific consent where a new activity requires it, rather than treating a new privacy-policy version as consent. Preserve the relevant historical notice and evidence of actual choices.

Before commercial adoption, the operator must complete its processing inventory, legal-basis assessments, processor and transfer records, retention schedule, response procedures and security testing. It must assess NDPC registration, a data protection officer, compliance filings and impact assessments under the current framework. This notice does not claim that registration, an audit or legal approval has already occurred.
