Account

Account pages are your personal control centre. Start at Account, then use Settings for deeper controls.

What Lives Where

My Account (/me)

Primary actions:

• My Photos: saved and tagged photo management.
• Profile Settings: profile visibility, profile photo controls, and tagged-photo gallery privacy.
• Purchase History: canonical order ledger and ticket ownership outcomes.
• Invitations: hub and staff invites.
• Shared details: hub-scoped details such as names or phone numbers you have shared with specific hubs.
• Connections: in-person and profile-based connections.

Connections: Remove or Block?

Use Connections or a profile’s action menu when you want to change how someone can contact you.

Connection controls have different behaviour depending on which action you choose.

• Remove connection ends the current connection. It also closes direct messaging between the two of you, but the other person can still send you a new connection request later.
• Block user is stronger. It removes the connection, closes direct messages, and stops that person sending you a new connection request until you unblock them.
• Unblock only removes the block. Unblocking does not restore the previous connection automatically.

Settings (/settings)

Sections to know:

• Profile and Privacy: name, username, profile visibility, avatar behaviour.
• Safety: report history, blocked people, moderation outcomes, and moderator follow-up markers.
• Alerts and Delivery: push/email controls and repair tools.
• App Preferences: theme and calendar-related controls.
• Security: passkeys, authenticator MFA, password, sign out, and deletion controls.

Safety (/settings/safety)

Use this page when you want one place for:

• Report history from the current Trust & Safety report surfaces,
• People you blocked,
• Moderation outcomes and visible case updates involving you.

Current report surfaces include:

• Chat messages,
• Photos,
• Incidents,
• User profiles,
• Hub profiles,
• Event pages.

What to expect:

• Reporting still starts from the relevant surface, such as a profile action menu, a hub page, an event page, a photo report action, or the existing chat/incident report flows.
• After you submit a report, the case appears in Report history.
• If moderators record an outcome or leave a visible note, it appears in Moderation outcomes.
• If a moderator opens a follow-up DM, Safety records that the case has a moderator message, while the actual conversation continues in Chat.
• You can unblock someone here without reopening the original profile or connection card.

Security Controls: Password, Passkeys, and MFA

Use these two pages together:

• Password: update your current password.
• Passkeys & MFA: add/manage passkeys and authenticator MFA.

What to expect:

• Passkeys can be added with an optional label.
• Passkeys can be renamed or removed later from the same page.
• Passkey sign-in does not ask for a separate authenticator MFA code afterward.
• MFA setup issues one-time backup codes; store them in your password manager.
• Authenticator codes refresh every 30 seconds. If one fails, wait for the next code before retrying.
• Disabling MFA requires your current password plus one challenge method (authenticator code or backup code).
• If you signed up through Google or another SSO flow and have never set a local password, Hubbaly asks you to create one first before MFA can be disabled.

Android note:

• On Android, enter your email on Login first, then tap Sign in with passkey for the most reliable provider prompt behaviour.

Delete account and personal data

When you delete your account from Settings, Hubbaly:

• Signs you out everywhere immediately,
• Removes your profile and sign-in data from active systems,
• Removes live memberships and account access tied to that user profile,
• Removes chat photos and GIFs you sent from normal chat immediately.

Conversation text may remain in chat history with the sender anonymised as Deleted user so the thread still makes sense to the people already in it.

Some limited records may still be retained where we still need them for payments, refunds, disputes, tax/compliance work, fraud or abuse prevention, and backups that have not yet expired.

If someone previously had access to removed media, or if a message was manually deleted before they reported it, Hubbaly can keep a short restricted evidence hold so eligible recipients can still report it. That evidence is not part of normal chat history.

If a report is filed, that evidence can stay in a restricted moderator-only review path for as long as the abuse/legal case needs it, and then for a short follow-up retention window before purge.

That restricted evidence view can preserve sender identity and previous usernames when moderators need that history to resolve a case safely.

Practical outcomes:

• Current and previous usernames tied to the deleted account stay reserved permanently and cannot be claimed by anyone else later.
• Your old email address can be used to create a fresh account later.
• A fresh account does not restore the deleted account’s old history.

Profile and Privacy Rules That Matter

• Keep your username stable. Mentions and profile links depend on it.
• Profile visibility controls who can open your profile.
• Photo visibility controls who can see your uploaded profile photo.
• Some profile access failures intentionally return Not found to protect privacy.

Shared details

Use Account -> Shared details when you want to see which hubs hold reusable details about you.

These are hub-scoped answers such as full name, phone number, organisation or group, or another operational detail a hub has asked for during interest, joining, invite acceptance, tickets, or events.

What to expect:

• Shared details are not a global Hubbaly profile.
• Details for one hub are not shared with other hubs.
• Answers are encrypted at rest and visible only to authorised Hub Admin roles in the hub that collected them.
• Each account row links back to that hub’s own Shared details page so you can review, update, or clear the stored values where access is available.
• If a hub later turns off extra detail collection, your existing shared details should still remain reviewable so you can clear information already held about you.

Purchase History: How to Read It Correctly

From Purchase History, track:

• Order status (Paid, Free, Comp, Partially refunded, Refunded, Failed, Expired),
• Per-order ticket ownership state (owned, transferred, reassigned, refunded, voided),
• Line-item and event context from order snapshots,
• Why a refund was partial or blocked.

If Something Looks Wrong

1. Confirm you are in the correct account and hub context.
2. Refresh once and reopen the affected page.
3. Check whether visibility or role scope explains the difference.
4. Capture URL + UTC time + screenshot and escalate if still incorrect.

Related Guides

• Chat and Notifications
• Purchases and Refunds
• Photos and Privacy
• Troubleshooting