> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buburuza.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage settings and get help

> Find available profile and notification settings and contact support.

These instructions cover the current web app. Check the selected space before changing company settings. Mobile screens may use different labels; do not assume a setting exists unless your app shows it.

<a id="profile" />

<a id="change-mobile-email" />

<a id="change-mobile-phone" />

<a id="edit-mobile-identity-and-nickname" />

## Profile and company details

Open **Settings** and select the profile or company area. Edit only the fields offered there, complete any identity check and save. For a locked verified field, [contact support](/support) and explain what needs correcting. Do not attach identity documents to an initial support message.

<a id="notifications" />

## Notifications

Open **Settings → Notifications** and review the categories shown for your account. Optional product messages and security notices have different controls. Changing a preference does not change a payment's status or remove an obligation.

If an expected notification is missing, check your account email and mail filters, and the device permission where push notifications are used.

<a id="appearance" />

<a id="mobile-privacy-display-options" />

<a id="read-phone-widgets-and-quick-actions" />

## Appearance and device settings

Use the appearance options available in your app. A display currency does not convert funds. Device widgets and travel-mode instructions from earlier drafts are not current product guidance. The platform has no travel-mode workflow; see [Onboarding and security](/onboarding-and-security).

<a id="updated-terms" />

## Updated agreements

When the app asks you to review updated agreements, open the documents shown and read them before accepting. Keep the acceptance result separate from payment or verification status.

<a id="contact-support" />

<a id="report-mobile-app-problem" />

<a id="close-account" />

## Get help

Use **Get help** or **Support** for account access, verification, a payment problem or an account-closure request. Choose the relevant topic and describe what happened. For a payment issue, include the existing transaction reference and the error you saw; do not submit the payment again just to obtain another reference.

Keep one-time codes, recovery material, private keys and full bank details out of the message. Support can direct you to a secure process if more information is needed.

<a id="share-feedback" />

<a id="mobile-updates-and-information" />

## Feedback

Use **Feedback** for product suggestions. If you need an answer about your account, use Support instead. See [Support](/support) for the current contact channels.


## Related topics

- [Buburuza product guides](/guides/index.md)
- [Buburuza](/index.md)
- [Onboarding and Security](/onboarding-and-security.md)
- [Sign in and protect your account](/guides/account-access.md)
- [Quickstart](/quickstart.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.