Your BLUBO account and information

Who is responsible

Blubo Ltd operates BLUBO. Contact blubosupport@gmail.com about your account or information. The operator and registration information below identifies the current contact details and pending registration status.

This notice covers the BLUBO mobile app and related member support. It does not cover another company merely because it has the same founder.

Sign in and verification

BLUBO uses Google Firebase Authentication for email and password access and, when offered on your device, Google or Sign in with Apple. Your chosen provider confirms the identity used to sign in. BLUBO receives the verified email and account identifier needed to connect that identity to your BLUBO account; it does not receive your Google or Apple password. Firebase processes authentication credentials and the technical information needed for account access. Your Firebase password is not copied into a BLUBO password record.

With Hide My Email, Apple may supply a private relay address instead of your usual email. Matching email addresses do not automatically join separate accounts.

Starting registration can create a Firebase identity before you verify your email or complete a BLUBO profile. Unfinished signups do not currently expire automatically. You can ask for deletion even if you did not finish registration.

Phone sign in is not included. Signing in or verifying an email does not prove adulthood, legal identity or that someone is safe.

Account and profile information

• Your email, authentication identifier and account status support sign in, recovery and account security. They are not public profile information.
• Your chosen name, broad city or region, profile text, interests and prompts form your profile. They begin as a private draft. A new incomplete profile is not discoverable by other members.
• Photographs are scanned for malware and processed to check image format and integrity and remove embedded metadata. Once those checks pass, they are available according to your profile visibility choices without waiting for staff approval. Staff review can happen afterwards, and reported or prohibited content can be removed. These file checks do not assess nudity, identity or age.
• Support requests, reports, appeal records and selected evidence allow authorised staff to review a concern. Provide only the information needed for the request.
• Necessary service logs, authentication activity, device or app information, IP addresses and audit events support access control, fault investigation and abuse prevention.

Do not put your home address, financial credentials, identity documents or another person's private information in your profile. Dating preferences may reveal sensitive information. They are not supplied for advertising targeting.

To participate, sign in, enter your date of birth, add your name, city, intention and a photo, and accept the participation notice. Dates of birth showing an age under 18 are refused. We store your date of birth privately and record when you declared it; your full date of birth is not shown on your profile. This is not an independent age or identity check. Extra photos, interests and prompts are optional. Your visibility choices still apply, and you can pause discovery.

Discovery, connections and profile reveal

When discovery is available and you are eligible, BLUBO uses profile information, broad region, preferences, visibility and interaction choices to select the profiles you can see. The service records interests, passes, connections, reveal choices, blocks and reports to manage access and prevent unwanted contact. These actions are service information, not advertising signals.

Eligible members can see the profile information allowed by your current visibility settings. Clear profile photographs depend on those settings; where Privacy Shield applies, a connection and both members' reveal agreement are required. A connection requires mutual interest. Chat opens after the other member accepts the Chat request. Encrypted Chat also checks the accepted connection, applicable reveal choices and registered devices.

You can pause discovery, withdraw reveal permission, unmatch or block using the available controls. These choices restrict future authorised access. They cannot make someone forget information already seen or remove a copy they made outside the app. Your email, authentication details and private verification evidence are not public profile fields.

Paid visitor history and paid private browsing are not offered in this release. No one can purchase access to another member's private visits or concealed information through this notice.

Nearby discovery and location history

With your device permission, BLUBO reads your location while the app is in use to show people nearby. It does not request background location. You can use your town instead. We round the current position to three decimal places before sending and storing it, roughly one hundred metres at the equator; the device may provide a less precise reading. Each update replaces your saved current position.

Automatic location is the default, subject to your phone permission. BLUBO uses the phone’s town lookup service to suggest a town and asks before changing your saved town. Android and iPhone lookup services may send the rounded position to their service provider. A town you choose manually stays fixed until you switch back to automatic location.

Location history has its own Settings control and is on by default when you use location. It saves account-linked areas rounded to two decimal places, roughly one kilometre at the equator, at most once every ten minutes. These dated records are used for BLUBO location-usage analysis. They are linked to your account, not anonymous. A daily cleanup removes records older than 90 days. This history is stored by BLUBO and is separate from Google Firebase usage analytics.

Turning location history off stops new history without removing nearby discovery. Existing history remains subject to the 90-day cleanup. Choosing town-only discovery removes your saved current position and location history and stops further location updates until you choose to use location again. Account deletion also covers both. Copies in backups follow the recovery arrangements described below.

Other members receive rounded distance, never your coordinates, direction or a map point. Distances below the display floor appear as under 2 km. You can hide your distance. Staff member screens show your town, not coordinates. Distance rounding reduces precision but cannot guarantee that nobody can infer where you are. Your privacy export includes your saved current position and location history.

Moments, audiences and expiry

When Moments is available, you choose whether a Moment is for compatible eligible members, your connections or selected connections. The selected audience still needs current eligibility and access permission; selecting someone does not create a match or bypass a block. Text, photographs, poll choices, topics, reactions and votes are processed to provide the Moment and its interactions.

Moments and their photographs are not end-to-end encrypted. Authorised moderation staff can review submitted material, including poll questions and options. A submitted Moment may remain pending, be restricted or be rejected. A Moment must pass the relevant checks before another member can see it.

Moments expire after 24 hours from submission. The current posting limit is ten per day. Expiry or withdrawal removes ordinary audience access; it is not a promise of immediate erasure from every device, report, operational record or backup. Moderation records, your own management history and necessary evidence can remain for review. The account deletion route covers associated Moment information too.

Encrypted Chat and its limits

When encrypted Chat is available, message content is encrypted on a member's device and is intended to be read by the authorised participants' devices. BLUBO uses a maintained Matrix encryption implementation. After both members accept contact, registered devices signed by their owner identity can exchange encrypted messages. Comparing codes with the other member is optional and provides an additional check; ordinary Chat access does not mean that comparison took place. Changes to a previously verified identity are not silently accepted. An unavailable encrypted session does not fall back to ordinary unencrypted messaging.

End-to-end encryption does not conceal all service information. BLUBO and its messaging infrastructure process account and device identifiers, connection and room membership, encrypted events, delivery timing, technical logs, access decisions and any message expiry information needed for the feature. Profile information, Moments, support cases and reports have their own access rules and are not protected by Chat encryption.

Information you choose to include in a report or support request, including message excerpts, is disclosed to authorised staff for review. A recipient can also copy or disclose a conversation outside BLUBO. Encryption does not guarantee a member's identity, conduct or safety, prevent another camera from recording a screen or erase a recipient's independent copy.

Local encrypted caches, queued attachments, server ciphertext, reports and backups can persist after content stops appearing. BLUBO does not promise instant forensic erasure. Temporary message controls and screenshot prevention must not be assumed available unless your release explicitly offers them; this release does not sell those features.

Optional device notifications

Push notifications are optional. When delivery is available, you must enable the BLUBO preference and the device permission. BLUBO registers a device destination and stores its account association, platform, consent revision and delivery status. Google Firebase Cloud Messaging processes installation and delivery identifiers; on iPhone, Apple Push Notification service also participates in delivery.

Notifications use generic wording. BLUBO does not put message text, photographs, a match's name, verification evidence or report details in the notification payload. Opening a notification still requires authorised app access. Even generic wording can reveal that BLUBO is installed to someone who sees your device.

You can disable notifications or revoke a registered device without enabling or disabling analytics. Turning them off prevents future authorised delivery after the change is processed; an item already delivered to your device may remain there. Delivery can be delayed, fail or stop when a session expires. Notifications are not an emergency or time-critical communication service.

Private verification is a separate step

Identity verification is optional for participation. Live verification remains unavailable while Smile ID onboarding and provider arrangements are being completed. No completed live-person, photo-match or adulthood check is promised by this notice. Email verification, a photograph upload or a date of birth does not establish those checks. Members without completed checks remain unverified and do not receive a Verified badge. This release does not display that badge.

Before an enabled verification step asks for a fresh selfie, liveness capture or identity document, it must present a separate notice and obtain your explicit agreement to that processing. That notice must identify the actual provider, purpose, evidence required, processing locations, retention and deletion arrangements, and what declining means for participation. Your ordinary profile and this participation notice are not substitutes for that agreement.

Verification evidence is private and separate from member profile photographs. The provider's retention periods, any biometric enrollment and the method for verifying provider erasure are not yet confirmed for BLUBO. Do not send identity documents or verification images to the support inbox. Account suspensions and moderation decisions still apply; declining optional verification does not remove a suspension.

Usage analytics and your choice

Usage analytics is on by default. You can turn it off in App analytics, available from sign in and Settings, without losing account or dating features. A previously saved opt-out remains off after an update or restart.

Google Firebase Analytics receives app launches, session measurements, appearance changes and technical details such as app version, device information and an installation identifier. BLUBO's current custom events are app ready and appearance changed. BLUBO does not add member account identifiers, profile content, messages, photographs, contact details or coordinates to those events. Advertising identifiers and advertising storage remain disabled.

Turning analytics off stops subsequent collection on this device when the change succeeds and resets local analytics data and its identifier. It does not automatically erase information Google has already received. Contact BLUBO about deletion of previously collected analytics. The separate location-history setting does not change when you turn usage analytics off.

Live ads, paid subscriptions and ticket checkout are not enabled in this release. Usage analytics does not enable marketing messages, advertising or notifications.

Events and attendance choices

You can browse listed events and mark yourself interested or going. BLUBO stores that choice against your account so you can review and change it. Other members see how many active members marked going, not their names. These choices do not reserve a place, issue a ticket or guarantee admission.

Marking going does not agree to event photography, disclose your attendance to another member by name or permit unrelated marketing. Account deletion covers your saved event choices.

Providers and processing locations

Google Firebase Authentication handles account authentication and recovery. Google Analytics for Firebase provides optional usage measurement. Firebase Cloud Messaging and Apple Push Notification service support opted-in notifications when enabled. Encrypted Chat uses BLUBO’s messaging infrastructure; it is not a public social-media messaging account. Amazon Web Services hosts the BLUBO backend, database and private object storage in Stockholm, Sweden. Google states that Firebase Authentication processes data in the United States; optional analytics and messaging use Google service infrastructure, and iPhone push also uses Apple’s infrastructure. Your information can therefore be processed outside Ghana. A complete list of other processing and backup locations has not yet been published; you can request the available details from BLUBO.

See Firebase's privacy and security information for its service-specific processing details. Staff access must follow the permissions assigned to their role.

Retention, deletion and requests

You can ask for access to your information, corrections, deletion or a review of a privacy concern through member support. The operator must verify account control proportionately and protect information about other people. Never send a password, sign-in code or identity document by ordinary email.

The account deletion page explains the app path and an email request route that does not require reinstalling the app. The request covers the BLUBO member record, associated profile and media information, linked Firebase identity and relevant provider copies. Confirming in-app deletion closes ordinary account access while the request is processed. Uninstalling the app or signing out does not delete an account.

Apple linked accounts may require a fresh Apple confirmation so the app can revoke its Apple authorization before confirming deletion. That confirmation does not by itself mean that BLUBO has finished deleting the account and all associated information.

Account, profile and related social service records are retained while your account is open, subject to feature access and expiry rules. Removing content from view does not by itself erase all underlying records. Unfinished Firebase signups and withdrawn or rejected photo uploads do not currently have automatic expiry. You can request their deletion with the account, including when signup was not completed. Staff review the request and provider copies before confirming the result; a request is not an instant erasure of every copy.

Where a documented legal, safety, fraud or dispute reason requires restricted retention, the request may need further review. The system keeps a minimal deletion receipt, audit record and non-profile account reference after the ordinary account data is removed. Backups and provider records can persist beyond active-account deletion. Fixed backup expiry and other category retention periods have not yet been published; contact BLUBO for the status and remaining copies associated with your request.

You may also raise a concern directly with Ghana's Data Protection Commission. Contacting BLUBO first is not a condition of making a complaint.

Adults, security and changes

BLUBO is for adults aged 18 or older. A date of birth showing an age under 18 is refused. A verified email or declared date of birth alone does not prove adulthood. Suspected underage use can be reported in the app or to member support. No provider-backed age, live-person or photo-match result is created from your declaration.

No online service can promise absolute security. Material changes to this notice will be dated and explained. Changes do not silently make private content public or grant permission to reuse verification material.

Operator and registration information

Operator

Blubo Ltd.

Account and privacy contact

blubosupport@gmail.com.

Service address

A postal service address has not yet been published. Use the account and privacy email for correspondence and to request postal contact details.

Data Protection Commission registration

Registration is in progress and remains pending. No completed registration reference is claimed.

Support availability

Requests can be sent by email. Published support hours and a guaranteed response time have not been established. BLUBO is not an emergency service.