Elden Smash

Privacy Policy

Last updated: March 2026

Overview

Elden Smash or Pass is a fan-made game built by drewfoos. This policy explains what information is collected when you use the site and how it is stored and used.

Information We Collect

If you play without signing in

Your game progress (the order of characters and your smash / pass choices) is saved only in your browser's localStorage. This data never leaves your device and is not sent to any server.

If you sign in with Google

Signing in uses Google OAuth. We receive the following information from Google and store it in Firebase Realtime Database:

  • Your Google display name
  • Your Google profile photo URL
  • Your Google account email address (used only to identify your account)
  • Your smash / pass choices per character, so your history is preserved across devices and sessions
  • Your current position in the deck (which character you are on), for cross-device sync
  • A timestamp of when you last played
  • Any display name or tagline you manually set in your Settings

Vote Counts

Aggregate vote counts (total smashes and passes per character, with no personal identifiers) are stored in Firebase and used to power the live leaderboard and the “What Others Chose” display. These are not linked to your account.

Public Profiles

Your profile is private by default. If you opt in to a public profile in Settings, your display name, tagline, profile photo, and smash / pass history become visible to anyone with the link. You can turn this off at any time and your profile will immediately become private again.

How We Use Your Data

Your data is used solely to provide the game experience: saving your progress, showing your history, and enabling cross-device sync. We do not sell your data, share it with third parties, or use it for advertising.

Data Deletion

You can erase all your smash / pass history at any time from the Settings tab in your profile. This permanently removes your vote history from the database. To request full account deletion, contact us via GitHub.

Third-Party Services

The site uses the following third-party services, each with their own privacy policies:

Cookies & Tracking

This site does not use advertising cookies, tracking pixels, or analytics beyond what Firebase and Vercel collect for infrastructure purposes (e.g. error reporting, request logs). No third-party ad networks are used.

Changes

If this policy changes materially, the “Last updated” date above will be updated. Continued use of the site after changes constitutes acceptance of the revised policy.