Help & Support

    Find what you're looking for below. We've answered the most common questions in our resources — chances are your answer is already here.

    Quick Links

    Common Questions

    Most questions are already answered in our FAQ — from how the app works to privacy and health concerns.

    Learn About Snoring

    In-depth, evidence-based articles covering causes, risks, and solutions.

    Reduce Your Snoring

    Practical, research-backed tips you can try tonight to lower your Snore Score.

    Policies & Legal

    Troubleshooting

    Microphone not working?

    Make sure you've granted microphone permission in your browser settings. On iOS, use Safari. On Android, use Chrome. Check that no other app is using the microphone at the same time.

    Score seems inaccurate?

    Background noise (fans, traffic, pets) can affect results. Place your phone 30–60 cm from your head on the nightstand. Run sessions for at least 30 minutes — a full night gives the best data. See our FAQ on accuracy.

    Screen turns off during test?

    SnapSnoreScore uses the Screen Wake Lock API to keep your screen active. If it still turns off, check your device's battery saver or power management settings — these can override the wake lock on some Android devices.

    History or data disappeared?

    All data is stored in your browser's localStorage. Clearing browser data, using incognito/private mode, or switching browsers will reset your history. Unfortunately, we cannot recover this data as it only exists on your device.

    Want to delete your data?

    Go to History and tap "Clear" to remove all session data. Since everything is stored locally, deletion is permanent and immediate — we have no copies.

    Still Need Help?

    If you've checked the resources above and still have a question, bug report, or feedback, feel free to reach out. We typically respond within a few business days.

    snapsnorescore@gmail.com

    Please include details about your device, browser, and what you were doing when the issue occurred.