Account devices, localization, and accessibility
Signed-in devices and sessions
Authentication sessions and notification-device registrations are separate records. The reader Profile does not currently provide a cross-device session inventory. Signing out ends the current session; changing the password keeps the current session and revokes the other sessions and refresh credentials. These actions do not delete stories, purchases, or Creator drafts. If account access looks unfamiliar, change the password and contact human support without pasting device tokens, login codes, or authentication secrets.
Language, region, and currency
Mystrix chooses language from the stored account preference, then the app or browser request, then English. Currency can also depend on account and region and is confirmed by the checkout display. Changing display language does not convert a completed payment or rewrite story language.
The website and Android reader Profile editors let you save your billing country code, state or province code, city, and postal code. Enter a two-letter country code such as `CA`; leave fields blank when they do not apply. Save all four together. Mystrix uses this saved location to check whether PayPal and native one-time purchases are available under its current tax policy. An unsupported or missing location keeps those checkouts unavailable until you correct it. If your new location changes the tax on an active PayPal subscription, Mystrix pauses its renewals. You keep access through the period already paid for and can approve a new PayPal checkout for the same plan under the current tax quote.
Mystrix Marketing also collects these billing details inside campaign creation and before payment on an existing unpaid campaign. Saved details are prefilled and can be corrected there; you do not need to leave Marketing for Profile. Billing location belongs to your account and is separate from the countries in your campaign's audience targeting. The form explains that card checkout supports Canadian billing locations.
Reader accessibility settings
Supported clients expose reader typography, line spacing, narration, and platform accessibility semantics. These settings change presentation and input access, not the story's authored content or consequences. Device-level text scaling, screen readers, reduced motion, and notification permissions can also affect the experience.
On the website, opening the inline Profile editor moves keyboard focus into its first available form control. Selecting Cancel hides that editor and returns focus to the Edit control, so keyboard and assistive-technology users keep their position on the page.
Performer rights and pay
Signed-in accounts can open Performer rights & pay from Creator Tools, or from a Story's Rights & licences menu. Reader website Profile links directly to that workspace in Creator. Android and iOS Creator also offer the performer workspace in their navigation; it does not require a Story or a separate creator identity. This account workspace covers submitted voice performances and likeness images: choose voice rights, likeness rights, or both; upload the exact recording or image for review; inspect its status; manage licence history and revocation; and inspect attributed uses, voice-performance requests, statements, payments, and payout settings. Creators can discover only approved media that still fits the selected Story and current licence scope. Expert audio/video contributions are a separate workflow in the same workspace and can carry only the specific voice or likeness permission recorded in that contribution.
When settings do not match across devices
Confirm the same account and app are in use, save the setting, and reopen the screen. Some settings are app-specific or session-local by design. If one device still disagrees, report the app, screen, device platform, expected value, and returned value without including device tokens or login codes.