Privacy Policy
Last updated: October 11, 2026
Echoraum is a self-hostable service for organizing and sharing YouTube music and videos. This instance is operated by Elara. This policy describes how the Echoraum application handles information. Elara manages this instance's servers, database, and uploaded images. Hosting, access logs, backups, and any additional services depend on the instance operator.
Information it handles
- Account information. When you register, you provide a username and password. Passwords are stored as hashes, rather than readable passwords. The service also stores your account ID, permissions, and whether your account is enabled. Registration does not require an email address.
- Optional profile information. You can provide a display name, biography, pronouns, and profile image. Uploaded profile images are stored on the instance.
- Posts and songs. The service stores your post titles, song titles, YouTube video or playlist links, song order, author information, and post creation and update times.
- Sign-in and security information. The service processes authentication tokens and stores session records to keep you signed in and revoke sessions. The backend records the IP address forwarded by the frontend during registration, together with an account counter and expiry time, to limit repeated signups. The frontend uses the client address resolved by its server; depending on hosting configuration, this may be a proxy address. Administrators can also maintain a signup IP allowlist. For password changes and two-factor verification, the service stores IP addresses with attempt counters and expiry times. It also stores failed password-change and two-factor verification counts and temporary account blocks. Password-change attempt tracking applies whether or not you enable two-factor authentication.
- Two-factor authentication. When available and enabled, the service stores an encrypted authenticator secret and hashes of one-time recovery codes. It processes the authenticator or recovery codes you submit for sign-in and security changes. It also stores temporary login challenge hashes and expiry times, verification attempt counts, temporary account blocks, and the last accepted authenticator time step to prevent code reuse.
- Technical information. Servers and hosting providers receive connection information when you visit, such as your IP address and request details. Error logs may contain technical information used to investigate failures. When the operator configures monitoring, the frontend server and backend can send diagnostic traces to a monitoring service. These traces can include request routes or URLs, HTTP methods and response statuses, timing, error details, trace identifiers used to connect related requests, and service version and deployment information. URLs and error details may contain identifiers or information associated with your activity.
How information is used
Information is used to create and authenticate accounts, display profiles and posts, save and update your music collections, retrieve YouTube titles, remember playback preferences, verify two-factor authentication, limit repeated password-change and verification attempts, prevent automated abuse, manage accounts, and diagnose service problems. Instance administrators can manage users, disable accounts, and delete accounts and their posts.
Protecting your information
Changing your password requires a signed-in session and verification of your current password, plus an authenticator or recovery code if you have enabled two-factor authentication. Failed attempts can temporarily block further attempts for your account or network address. The service asks browsers not to cache authentication responses. Browser security rules restrict scripts, embedded content, and other resources, prevent other sites from framing Echoraum pages, and instruct browsers to use HTTPS after receiving the policy over a secure connection.
Public information
Your username, optional profile information and image, and posts are available through public pages without signing in. Posts identify their author and show their song titles and YouTube links. Search engines and other visitors may index, copy, or share this information. Only publish information you are comfortable making public.
Cookies and browser storage
Echoraum uses a refreshToken cookie to keep you signed in. It is configured for HTTPS, cannot be read by page scripts, and uses a strict same-site setting. It expires seven days after it is set or renewed. Signing out removes this cookie. Changing your password, enabling or disabling two-factor authentication, or replacing recovery codes signs out all sessions and removes the cookie in the browser making the change. Access tokens and temporary two-factor login challenges are held in page memory. The setup secret and newly issued recovery codes are displayed in the settings page without being saved to browser storage by Echoraum.
Your autoplay-next-song preference is saved in your browser's local storage under echoraum-autoplay-next-song. Your privacy-enhanced YouTube playback preference is saved under echoraum-privacy-enhanced-playback. These preferences remain until you change them or clear site data. You can control cookies and local storage through your browser settings, although blocking the sign-in cookie prevents persistent sign-in. Third-party services may use their own cookies or similar technologies.
Third-party services
YouTube and Google. Echoraum loads thumbnails from Google's servers, embeds YouTube players, and uses the YouTube IFrame Player API for playback controls. These requests can occur when a thumbnail or player loads, before you press play. Google may receive your IP address, browser information, the site's origin or referrer, and information about the content loaded or played, and may use cookies under its own policies. The backend also sends submitted YouTube links to YouTube's oEmbed service to retrieve titles. Echoraum does not ask you to connect a Google account. See the Google Privacy Policy and YouTube Terms of Service .
Cloudflare Turnstile. When configured, sign-in and signup forms load Cloudflare Turnstile to detect automated requests. Cloudflare processes network, browser, and device signals for verification. The backend sends the verification token and the network IP address it receives to Cloudflare to validate the challenge. See Cloudflare's Privacy Policy .
Authenticator apps. The two-factor setup QR code is generated locally in your browser. Scanning it or entering the setup secret shares that secret and your Echoraum username with your chosen authenticator app. How that app stores, syncs, or backs up this information depends on the app and its settings.
Monitoring services. When monitoring is configured, diagnostic traces are sent from the servers to the collector chosen by the instance operator. The operator may host it themselves or use a third-party provider. Traces help investigate errors and measure service performance. The provider, processing location, access arrangements, and retention depend on the instance. Contact Elara for details about this instance.
Hosting and administration. The instance operator and their hosting providers may access information needed to run and maintain the service. Their storage locations and processing arrangements vary by instance. Third-party providers may process information in countries other than your own.
Retention and deletion
Account information and posts remain stored until updated or deleted. Signup IP counters expire after a 21-day counting period and are removed by scheduled cleanup. Separately maintained signup IP allowlist entries remain until an administrator removes them. Session records can remain in the database after tokens expire or are revoked; token expiry does not itself delete those records.
Password-change and two-factor verification IP counters share a five-minute window; expired entries are removed by scheduled cleanup. Temporary account blocks last five minutes. Account failure counts and block timestamps may remain stored until a later security operation updates or clears them, or the account is deleted. Expiry of a block does not itself delete these values. Pending authenticator setup secrets expire after ten minutes, and login challenges expire after five minutes. Expiry prevents their use but does not itself delete the stored values. Disabling two-factor authentication clears the active and pending secrets and recovery-code hashes. Using a recovery code removes its hash; replacing recovery codes invalidates the previous set.
Deleting an account through an administrator removes its account record, posts, and session records from the active database. Unused uploaded profile images are removed by scheduled cleanup. Backup, log, and diagnostic trace retention depend on the operator and any monitoring provider. Deleting an account does not automatically remove records already held in logs or monitoring systems. Copies made by search engines, other visitors, or third-party services are outside Echoraum's control.
Your choices and privacy requests
You can edit your profile, replace or remove your profile image, edit or delete your posts, change your password, manage two-factor authentication when available, sign out, and clear saved browser data. Recovery codes are shown once when issued; save them somewhere secure if you enable two-factor authentication. To request account deletion, a copy of your information, or help with a privacy question, contact Elara at elara@elaraspace.net. Account deletion currently requires an administrator. Additional privacy rights may apply depending on your location and the operator's obligations.
Changes to this policy
This policy may be updated as the service or the instance's practices change. The date above identifies the latest revision.