Manage account settings and get help

Review scope: Linked public documentation checked October 30, 2026. Examples are proposed checks, not recorded OD results; use your account's current controls.

You will find the account controls, distinguish interface settings from story settings, and prepare a useful support request.

An account setting affects your use of the service. A character setting describes a fictional person. A chat setting affects a conversation. Keeping those scopes separate prevents an unrelated change from becoming your first attempted fix.

Before you begin

Open OD and sign in. Use your actual account's displayed labels and plan information. Prices, included credits, and available features can change.

Step by step

1. Open Profile. Find the account options shown there. If the menu is collapsed on your screen, expand it first.
2. Identify the setting's scope. A Persona belongs to your role in a chat; appearance fields belong to a character; the site's Language control concerns interface language.
3. Read the current value before editing. For a preference you may want to reverse, note its previous value.
4. Change one preference at a time. Save using the displayed control, then return to the area where the change should be visible.
5. Check account and generation costs in their own places. Read plan details before subscribing, and the operation's displayed cost before generating. Do not use a tutorial's example as a current price quotation.
6. Use the site's own account controls for account changes. Follow the current confirmation or recovery process. Writing “change my account” to a fictional character is not an account-management procedure.

The public site navigation exposes Profile, Language, upgrade controls, and Help Desk. Their position differs between layouts.

Separate your balance, plan allowance, and operation charge

Keep these three quantities distinct when following a review or tutorial:

The November 2 caption review of Best AI Reviews' September 20 video found balance/purchase narration at 0:00 and an image-cost description using “tokens” at 5:35. Neither establishes today's included credits, operation price or currency unit. Do not automatically treat a narrator's “tokens” as dreamcoins. AI Girlfriend Decoded's September 13 review also advises checking current checkout and operation costs at 6:26–6:42.

Current amounts were not verified for this review. Follow the account's current plan details and displayed quote rather than copying an older price. For a failed request, use the separately documented generation-failure guidance, retrieved November 1, and check actual account credit as described below. A quoted charge, a failed request and a confirmed refund are separate observations. See the video questions review for source and sample limits.

Language and storytelling are separate

Changing the interface language does not automatically rewrite a character definition or establish equal image-prompt performance in every language. For dialogue, make a direct request such as:

Please continue this conversation in Spanish while keeping the established
names, facts, and character roles.

The chat-language help article, edited November 5, 2025 and read October 31, 2026, says changing chat language can take several prompts. Check several ordinary replies rather than treating one response as a fluency test. For a continuing chat preference, see the separate Custom Instructions exercise. Preserve names, established facts, and the user's control while inspecting the language.

If you need to compare image-prompt languages, keep the character, scene, model, and other settings fixed. Do not attribute a changed result to language if you also changed the pose and model. The chat-language article does not establish equal image-generation performance across languages.

Keep a useful local backup

1. Open the character editor and copy your own important field text into a local file.
2. Label each block with its destination, such as APD or Scenario.
3. For an ongoing game, copy a concise current-state record and identify which accepted timeline it belongs to.
4. Save the exact prompt alongside any accepted image you can save through the site's controls.
5. Before deleting a character or conversation, check what the site's confirmation says will be removed.

This manual record helps you reconstruct a setup. It is not a guarantee of a full platform backup, native export, or complete automatic restoration.

Prepare a support request

1. Open Help Desk, or visit the Help Center.
2. Search the symptom before changing unrelated settings.
3. Record the feature, date/time and time zone, exact error, selected model if relevant, and what you expected. Include the request or media identifier when the interface exposes one; do not invent a missing ID.
4. For a coin or generation issue, include the operation and balance information the support form requests. The generation-failure article, retrieved November 1, 2026, describes automatic refunds for the failure categories it lists. Inspect the actual balance and generation history; an error message alone does not prove the credit has returned. If a documented refund is still missing after 15 minutes, follow its refresh/sign-in checks and contact support with the timestamp. An insufficient-balance message is a separate condition; do not repeatedly resubmit a paid operation to diagnose it.
5. Use a short reproducible description. Send the request through the site's actual support interface.

Example report:

Feature: Image editing
When: [date, time, and time zone]
Selected model: [label shown in my account]
Action: Changed the navy jacket to a green jacket
Problem: [exact error or observed result]
Expected: The jacket change without a new character
Evidence: [relevant image or error, if the form supports it]

Share only the evidence needed to reproduce the problem. Remove passwords, sign-in codes, payment details, and unrelated private conversation from screenshots or copied logs. A share link can expose material to its recipient; check its destination and visibility before including it. Use the service’s support form for account-specific information, not a public character description or community post.

Check your result

You should know whether you changed an account preference, a character, or a chat. For support, another person should be able to understand the issue without guessing which operation failed.

If something goes wrong

• A feature asks for a different plan: read its actual availability requirements; changing a prompt does not unlock it.
• An option does not save: look for a validation message and confirm the intended scope.
• A generation fails: preserve its error before retrying and follow current help guidance rather than submitting a large batch again.

Next: Testing and troubleshooting.

Back to the tutorial index