Frequently Asked Questions

Common questions.

Quick answers about accounts, payments, GDPR, and play. Each entry has a stable anchor — link directly to a question if you need to share an answer.

Account

How do I sign up?

Visit /signup, choose an email + password, and pick a handle. Your handle is the public URL form (e.g. /community/creator/<handle>); your displayName is shown alongside. You must confirm you are at least 16 years old to create an account.

I forgot my password.

Go to /forgot and enter your email. The platform mints a single-use reset token (today the token surfaces in-product as a local-first stub; once the email-delivery boundary lands the token will arrive in your inbox).

Payments

How do I request a refund?

Find the purchase on /community/purchases and click Request Refund. Refunds requested within 24 hours of purchase with no save progress are auto-approved; later requests go through the creator (7-day window) and then admin escalation.

Is my payment information safe?

The platform never stores raw card numbers. When the live payment provider lands, payment data is held by the processor (Stripe or equivalent) with industry-standard PCI compliance. We hold only the order ID, listing slug, price, and entitlement state.

GDPR & Privacy

What data do you keep about me?

See the Personal Data Inventory in the spec or your GDPR export. The platform never stores IP addresses; user-agent strings are sha256-hashed.

Playing

My saves aren't loading.

Saves are stored in your browser's localStorage and are scoped to the current device + sign-in account. Switching browsers or signing out clears the device's save cache. Cloud-saves (cross-device sync) land in a future release. If a save slot reports as corrupted, the runtime offers a Discard / Export Raw fallback.

Audio isn't playing.

Most browsers block audio until the player interacts with the page. Click anywhere in the player surface, then audio should resume. Check the pause-overlay Settings tab for volume controls.

AI dialogue is stuck.

AI-driven runtimes are only available in connected exports; the runtime depends on the LLM provider being reachable. If the provider is unavailable, the runtime falls back to a generic response and surfaces a notice. Check the AI-assisted dialogue badge for provider status.