Settings & account

The Settings page collects the small handful of account-scoped controls in one place: your profile read-out, the interface language toggle, and the account-deletion flow.

Where the page lives

• Path: /settings
• From the header: click your profile avatar in the top-right → Settings.

The page is split into two cards: User Information at the top and the red-bordered Danger Zone at the bottom.

Screenshot pending — the /settings page showing the User Information card and the Danger Zone card with the Delete Account button.

User Information

This card is read-only by design. It shows two fields lifted directly from your Google profile:

A note at the bottom of the card reads: "If you wish to change your information, please contact support." If you need to update either field — say, your institution rolled your email over — email luida@cluster.mu directly.

Language

The Web Console supports English and Japanese. The toggle isn't on the Settings page itself — it's in the page header, immediately to the left of your profile avatar.

• Click the globe icon in the header.
• Each click toggles between EN and JA. The label shows the target language (so when you're in EN, it reads "JA"; in JA it reads "EN").
• The choice is persisted in a NEXT_LOCALE cookie that lasts one year. The page refreshes immediately to apply the new language.

If you visit a deep-link without the cookie set, the console falls back to your browser's Accept-Language header, then to English. Only en and ja are supported.

Danger Zone — Delete account

The bottom card has a red border and contains a single action: Delete Account.

What happens when you click it:

1. A confirmation dialog appears asking you to type your username (the display name from Google) verbatim.
2. The Delete Account button stays disabled until the typed username matches exactly.
3. Once you confirm, the console issues DELETE /api/delete-account with your user ID.
4. On success, you're signed out and redirected to the public landing page.

The deletion goes through a single Prisma call: client.user.delete({ where: { id: userId } }). There is no archive, no soft-delete, and no undo.

What gets deleted, what gets left behind

The schema's User → Experiment relation does not have onDelete: Cascade configured. Practically, that means:

• Your User row is deleted. Sign-in records, profile fields, role.
• Account rows linked to your user (the OAuth provider tokens) are deleted alongside the user.
• Experiment rows you owned stay in the database but lose their owner. Their data — Answers, SessionMetadata, customData in S3 — also stays in place.
• Questionnaire and Question rows linked to those experiments stay.
• Custom log files in S3 (one folder per experiment) stay.

In other words, deleting your account orphans your experiments rather than wiping them. This is intentional — it lets the LUIDA team transfer ownership to a collaborator if you leave a project — but it's worth being aware of.

Before you delete

If you have ongoing studies, consider these alternatives first:

• Just sign out. The header dropdown has a Sign Out option. Your account stays intact and you can come back any time.
• Pause data collection. Edit your experiments and flip Status to TESTING (or set maxSessionCount to a small number). New participants stop joining; existing data stays accessible.
• Transfer ownership. Email luida@cluster.mu with the experiments you'd like reassigned and the email of the new owner. The team can move them.
• Download data first. If you do plan to delete, grab any data you still need from each experiment's detail page. See Web Console → Downloading data.

Any of those avoid the orphaning problem entirely.

Where to go next

• Researcher onboarding — sign-in, waitlist, the email gate.
• Creating an experiment — the main reason you're here.
• Web Console → Downloading data — grab questionnaire answers, participant info, and custom logs before any account changes.