Privacy Policy

Effective date: 21 October 2026 · Last updated: 23 October 2026

This policy explains how Hubpas Limited ("we", "us" or "our") handles personal information when you use Hubpas, including our Android app (package com.hubpasstudio.hubpas) and related web services. Features available to you may depend on your account, device and app version.

1. Information we collect

• Account and profile information: account identifiers, name, username, email address, telephone number, profile photo, biography, public city or district, optional private personal address (country, postal code, region, street address and city), age range, gender, interests, preferences, account type, subscription and verification status, and business or venue information that you provide. An address entered in the new Personal Address form is available to you in account settings and is not displayed on your public profile.
• Events and participation: event descriptions, addresses and coordinates, schedules, photos, video links, music selections, audience settings, invitations, RSVPs, comments, follows, saves, bookings, vendor or sponsor applications, and ticket or raffle-entry records, including ticket identifiers and draw results.
• Communications: messages and attachments you send, including photos, videos, voice recordings, documents, GIFs, contact cards and shared locations. We process call participants, call status, timestamps and duration, and the audio or video needed to connect calls. Sending a voice message uploads that recording.
• Wallet and payments: wallet identifiers, balances, funding and withdrawal details, payment telephone numbers, amounts, currencies, recipients, purchase and resale history, donations, refunds, transaction references and payment status. Wallet security records include PIN verification information, failed attempts and authentication results.
• Contacts, with permission: the names and telephone numbers of contacts you access through the app. Contact telephone numbers are sent in matching requests to find existing Hubpas users; contact details you choose to share or use for invitations are processed for those actions. Contact and match results may be cached on your device.
• Location, with permission: approximate or precise device location for maps, directions, nearby discovery and location-sharing features. Event addresses, profile cities and locations you enter manually are also processed. A location you choose to share is visible to its recipients.
• Device, activity and diagnostic information: IP addresses, device and browser information available to our services, app version, notification tokens, connection and error records, and activity such as event views, clicks, engagement and promotion performance.

2. How we use information

We use information to create and authenticate accounts; display profiles and events; provide discovery, invitations, chats, calls and location tools; issue and validate tickets; manage raffle entries and results; process bookings, wallet transactions and subscriptions; send service and account notifications; answer support requests; maintain security; investigate abuse or payment disputes; and operate, troubleshoot and improve Hubpas.

We also use profile preferences, interests, city or district, age range, gender and engagement where available to personalise discovery and match promoted events to an audience. Organisers receive promotion performance information such as views and clicks.

3. Device permissions and local storage

Camera access supports taking photos, video calls and scanning codes. Microphone access supports calls and voice recordings. Photo, video and file access supports attachments and uploads. Contacts access supports contact matching, invitations and contact sharing. Location access supports maps and sharing. Notification permissions support messages, calls, ticket and account updates. You can manage permissions in your device settings; declining a permission can prevent its related feature from working.

If you enable biometric authentication, your operating system verifies your fingerprint or face. Hubpas does not receive your fingerprint or face template. Where supported, a wallet credential may be saved in the device's secure credential storage for biometric unlocking.

Hubpas uses device storage, browser storage and caches for sign-in sessions, preferences, contact matches, ticket and wallet information, and pending messages or attachments awaiting upload. Clearing app data removes local copies but does not itself delete your server account. Our web authentication also uses verification tools such as Google reCAPTCHA where applicable.

4. Who receives information

• Other users and the public: profile and organiser details, public event content and content you publish may be visible to other users or visitors. Recipients receive messages, attachments, calls and locations you share. Public event content may be copied or shared outside Hubpas. Consider what you include in your profile and posts.
• Organisers and transaction participants: relevant attendee, booking, ticket, vendor, donation, raffle and payment information is used to fulfil purchases, manage participation, validate access and resolve disputes. Raffle results may display a winner's name and ticket number.
• Infrastructure and authentication providers: Google Firebase and Google Cloud provide authentication, databases, file storage, hosting, server functions and push notifications, and process relevant account, content, device and operational data.
• Payment providers: Monime and the financial institutions or mobile-money operators involved in a transaction process relevant payment, account, telephone, amount and transaction information. Payment providers may collect additional information directly through their checkout.
• Maps, media and communications providers: OpenStreetMap map services, Nominatim, Photon/Komoot and OSRM process map, search or route requests, which may contain coordinates or search text, together with connection information. Google Maps receives requests when you open its links. GIPHY receives GIF requests. Calling services, including configured SIP/VoIP services, Google or Twilio connection services, and Jitsi when used, process the information needed to connect communications. Opening embedded or linked third-party media can share connection information with its provider.
• Legal and safety recipients: we may disclose information when necessary to comply with applicable law or valid legal process, prevent fraud, protect users or enforce our terms. If ownership of Hubpas changes, relevant information may transfer as part of the change, subject to applicable privacy obligations.

Third-party services handle information under their own terms and privacy policies. Examples include Google, OpenStreetMap Foundation and GIPHY.

Safety reports and moderation: when you report content, we store your account identifier, the report reason and explanation, a limited snapshot of the reported item, the reported account identifier, and review decisions. Authorised platform reviewers can access these records; the reported user is not given your identity through the report feature. We also record community-rules acceptance, user blocks, event chat restrictions and account safety decisions. These records support safety, dispute handling and enforcement of our Community Rules.

5. Security and international processing

We use measures such as authenticated access, encrypted network connections, permission controls and payment authentication to protect information. No network service or device can be guaranteed completely secure. Do not share your wallet PIN, password or verification codes.

Hubpas and its providers may process or store information in countries other than where you live. Privacy laws in those countries may differ. Applicable legal requirements govern any required safeguards for international transfers.

6. Retention and deletion

We retain account and service information while needed to provide Hubpas and for relevant security, support, dispute resolution and legal obligations. Retention depends on the type and purpose of the record. Financial, ticket, fraud-prevention or legal records may need to remain after an account closes. Information retained for these purposes is limited to what is needed for those purposes. Copies held by other users, third-party services or in backups may not be removed at the same time as active account data.

To request deletion of your Hubpas account and associated personal information, email hubpasofficial@gmail.com with the subject Hubpas account deletion and your registered email address or telephone number. We may ask you to verify account ownership before acting. Do not send your password, wallet PIN, biometric information or verification codes. We will explain any information that must be retained and the reason for retention when handling your request.

7. Your choices and rights

You can edit available profile fields, adjust notification preferences, choose what to publish or send, and revoke device permissions in your device settings. You can request access, correction or deletion, or raise a privacy concern, by emailing our privacy contact. Depending on applicable law, you may also have rights to data portability, restriction, objection, withdrawal of consent or complaint to a data-protection authority. Withdrawing a permission or consent does not undo processing that has already occurred.

8. Children

Hubpas is intended for users aged 13 and over. If you believe a child below this age has provided personal information to Hubpas, contact us so we can investigate and address the account and information.

9. Changes and contact

We may update this policy as Hubpas changes. The date above identifies the current version. Material changes will be communicated through the app or another appropriate channel where required.

For questions about this policy, your information or a privacy request, contact Hubpas Limited at hubpasofficial@gmail.com.