Support

This page is the official support channel for questions, issues, and improvement suggestions while using FingerDoor. We aim to help you resolve problems quickly and keep sessions running smoothly.

Support Help FAQ FingerDoor

1. Support overview

Our top priority is to help FingerDoor run smoothly in real environments—classes, lectures, workshops, and live presentations. We focus on fast diagnosis and clear resolution, not just feature explanations.

Issues during a session directly affect the flow. We therefore try to provide guidance that is as quick and actionable as possible.

2. Before contacting us

Checking the items below first often leads to a faster resolution.

• Refresh the browser (F5) or reconnect
• Try a different browser (Chrome/Safari/Edge, etc.)
• Check display differences between mobile and desktop
• Confirm the roles: host screen vs participant screen
• Make sure you are not mixing the present screen with the join screen URL

3. Frequently Asked Questions (FAQ)

Q1. Can I use it without signing up?

Yes. FingerDoor is designed around a code/link-based join flow, so participants can join instantly without creating an account. This minimizes friction in live sessions.

Q2. Why does the host need to enter email and purpose when creating a session?

For stable and responsible operation, hosts are required to enter a host email and session purpose. This is a minimal measure for abuse prevention, incident response, and sending essential notices (security/policy/outages).

* We do not use the email for marketing/advertising. For details, see Privacy.

Q3. Can I prevent participants from seeing results?

Yes. In many setups, the result screen and the join/answer screen are operated separately. You can keep the present (result) screen for hosts or projection only, while participants submit answers without viewing results.

Because the exact setup depends on your URL structure and flow, contact support if you need guidance for your configuration.

Q4. Are responses stored?

FingerDoor is optimized for live participation. Data is stored only as needed under our operating policy. For retention and handling details, see Privacy.

Q5. The screen froze or an error occurred during class.

First try refreshing or reconnecting. If the issue persists, sharing the information below helps us diagnose much faster.

• Screenshot or a short video of the issue
• The URL you accessed
• Time the issue occurred
• Device (desktop/mobile) and browser
• Room code (if available)

Q6. Can I suggest improvements or new ideas?

Absolutely. Field feedback is our most important input. If you tell us “in what situation” and “what felt inconvenient,” we can evaluate priorities and follow up.

4. We welcome inquiries such as

• How to use the service
• Issue reports during classes/events
• Questions about result visibility and access control
• Feature requests and improvement suggestions
• Pre-inquiries for partnerships or group adoption

5. How to contact

Support is handled primarily via email. We aim to respond within 1–2 business days.

* An email address may be processed to reply to your inquiry. We do not use emails for advertising.

6. Email template guide

Including the items below helps us respond faster and more accurately. Not required—share what you can.

7. Operational notes

We continuously update features and policies to improve stability and service quality. Important changes are announced via the Terms, Privacy Policy, or official notices.

We see support not only as a help desk, but as a feedback channel to improve the service together. Please share even small inconveniences you notice on-site.

8. Related pages

• About
• Terms
• Privacy
• Partnership

Last updated: 2026-01-09