LYRIFT / PRIVACY & YOUR CHOICES

Your orbit.
Your privacy.

What Lyrift uses, what stays on your PC, and what optional connections share.

Effective and last updated:
THE DESKTOP

Local by default.

Settings, presets, imported files, and caches live on your computer. Online features still contact their providers.

YOUR CONNECTIONS

Chosen by you.

Spotify authorization, Twitch requests, public uploads, and audio response depend on features you enable.

PLANNED INPUT DISPLAYS

Not active today.

Keyboard/controller visualizations are planned. This version does not enable that input monitoring.

01 / ABOUT THIS POLICY

A clear picture of Lyrift.

Lyrift is developed and operated by Blighted. This policy covers the Lyrift desktop product, its earlier music-presence releases, its product pages at blighted.world/Lyrift, and its optional connected service. Questions and privacy requests go to [email protected].

It describes the current implementation, including features in private testing. Whether a feature processes information depends on the build you use, your settings, and whether its service is available. A description here does not mean a testing or planned feature has been released.

The main blighted.world solar-system page can include a Twitch embed; the Lyrift product and privacy pages do not embed that player. Connected platforms process information under their own notices as well.

02 / INFORMATION USED

What the features need.

Information processed by feature
FeatureInformation and purpose
Local music and lyricsWindows media-session information such as song, artist, album, playback state, position, duration, and cover thumbnails, used to display your current track and synchronize lyrics.
Settings and presetsAppearance, presence text, image references, application/client IDs, imported artwork and LRC files, and chosen options, used to keep your configuration.
Optional account connectionsAuthorization credentials, granted permissions, connection status, and account identifiers. Spotify playback control additionally uses device/playback information when separately authorized.
Twitch requests (testing)Channel and viewer IDs/logins, request text or track links, timestamps, selected tracks, moderation outcomes, reward/redemption identifiers, and viewer balance records, used to handle requests, queues, cooldowns, and refunds.
Website and supportHosting/security services can process IP addresses, request details, browser information, and security events to deliver and protect the site. If you contact us, we receive the message and contact details you provide.

Earlier published desktop builds retain their original local data directory. Current Lyrift desktop builds use a separate Lyrift folder and copy existing local files across on first use without deleting the originals. Existing connection registrations and secure credential identifiers remain compatible while the new build is tested. The desktop uses local diagnostic logs for faults and connection troubleshooting. The product page includes no advertising or third-party analytics scripts; its intro uses browser session storage to remember that you have seen it. Visitor-counter support in the current hosting prototype is not connected to public tracking.

03 / CONNECTIONS & PROVIDERS

Local does not mean offline.

Spotify

Local Spotify desktop detection does not require Spotify account authorization. An optional developer connection reads the current track for matched artwork. Queue controls request additional playback-state and playback-control permissions separately. Spotify credentials are stored through the system credential vault rather than in ordinary settings files; Spotify passwords are not requested by Lyrift. Spotify account authorization happens in your browser.

Lyrics, artwork, and video

Lyric lookups send recording metadata to LRCLIB. Optional artwork matching can send song, artist, album, and duration information to Spotify, Apple’s catalog, MusicBrainz, and Cover Art Archive. Your IP address is visible to services your device contacts. Imported lyrics and artwork stay local unless you explicitly choose a sharing feature.

Optional experimental Canvas retrieval can contact Spotify services and video hosts; a separately supplied session credential, if used, is stored in the system vault. Public image upload sends your selected file to Catbox.moe only when you request it. Imported files are not automatically uploaded. Public uploads may remain accessible after you remove their local gallery entry.

Discord

Rich Presence uses the local Discord desktop connection to publish the track/lyrics or custom preset you choose. Lyrift does not request a Discord password or user token for this feature. Discord can process and display that activity to other people.

Twitch and the request service

Optional Twitch linking uses browser authorization and a desktop pairing session. Twitch access/refresh credentials are encrypted in the hosted service; the desktop stores its service-session credential in the system vault. When requests are enabled, subscribed channel chat events are processed to recognize commands and, if enabled, participation-based viewer balances. Request and transaction records are kept; this is not a general chat-transcript archive.

Stream overlays and audio

The Browser Source receives track information, artwork, lyric timing, and optional numeric frequency levels from a local overlay server on your PC. Spotify-only audio response is optional and targets Spotify desktop/process audio on supported Windows builds. That capture path does not use your microphone or game audio and does not save or upload an audio recording. Streaming software can capture anything you include in a scene.

Updates and hosting

Update checks and approved downloads contact GitHub. Website delivery and protection can involve Cloudflare and the operator’s hosting service. These providers can receive request metadata needed to provide their services.

04 / SHARING & VISIBILITY

You choose what goes on display.

Lyrift uses information to provide the selected features, preserve configuration, manage requests, troubleshoot faults, and protect the service. It has no data-sale or advertising-tracker integration. Information is shared with the service providers needed for a feature, with the channel owner/moderators who manage requests, or with viewers when you publish presence or overlays.

Your Discord activity, Twitch commands, bot replies, public image URLs, and broadcast overlays may be visible to others. Do not put private information in presence text, requests, or artwork you publish. Required legal disclosures or necessary security investigations may also involve information we control.

Provider notices: Spotify, Twitch, Discord, and Cloudflare. Lyrift is independently developed and is not endorsed by these services. Spotify is a third-party beneficiary of this policy, as required by its developer terms.

05 / STORAGE & RETENTION

Different data, different lifetimes.

  • On your PC: settings, presets, imported files, gallery references, and caches remain in the existing application data directory until removed or replaced. Private Lyrift development builds use %LOCALAPPDATA%\Lyrift on Windows, after a copy-first migration where a previous installation exists. Earlier released builds can retain their older data directory, and a legacy instance-lock file can remain there to prevent conflicting desktop sessions. Local fault logs rotate at approximately 500 KB with two backups; age depends on how much is logged.
  • Authorization: desktop vault credentials remain until disconnected, replaced, or revoked. Hosted pairing and authorization-state records expire after three minutes; service sessions expire after 30 days. Expiry cleanup occurs when the service runs; expiry does not guarantee immediate physical erasure from backups.
  • Requests: the testing ledger retains pending/unresolved requests and the latest 200 completed history entries per channel when saved. Short-lived deduplication, cooldown, and recent-track entries have bounded expiry. Viewer balances and moderation records have no timed automatic purge in this version; deletion requires an operator action.
  • Support, security, and backups: these can remain while needed to resolve the issue, protect the service, restore operations, or meet an applicable obligation. Hosting-provider retention follows the configured service and its notice; no single fixed duration is claimed for provider logs.

Disconnecting a service is not the same as deleting every cache or transaction record. For data held by the Lyrift operator, request deletion using the contact below. We review the records we control and explain any applicable retention or third-party limits.

Spotify’s developer terms require account access to stop and applicable Spotify personal data under our control to be deleted within five days after disconnection or a qualifying disconnection request. Removing credentials alone is not a claim that every local cache has been erased; the operator must also handle retained Spotify-derived personal data and backups as required.

06 / YOUR CHOICES

Stay in control.

  • Use Off mode to clear Lyrift presence, and disable overlays or audio response when you do not want them displayed.
  • Use Connections → Spotify → Disconnect to remove the stored Spotify authorization. You can also revoke access in your Spotify account’s app settings.
  • Use Connections → Twitch → Disconnect to end that desktop connection. If you are offline, server logout may not be confirmed; revoke the previously authorized Twitch integration in Twitch’s Connections settings to remove platform authorization. Other linked desktops have separate sessions.
  • After quitting Lyrift, you can remove local data files you no longer want. Deleting the data directory resets settings and removes local caches; vault credentials are separate, so disconnect accounts first.
  • Clear this site’s session storage to reset the intro preference. The product page does not set advertising cookies. Cloudflare or linked/embedded services can use security or platform cookies under their own policies; manage those in your browser and the relevant platform.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, or an objection to processing. Contact us to exercise a right or ask about your information. We may need enough information to verify the account or channel involved; do not email passwords, tokens, or private keys.

07 / PLANNED, NOT ACTIVE

Keyboard and controller displays.

A future optional input display is planned to visualize selected keyboard presses and controller buttons/axes in your desktop or stream scene. It is not implemented or enabled in the version described here.

The intended design is explicit opt-in, a visible active state, selectable inputs, and an easy pause/hide control. It is intended for live local visualization rather than recording typed messages, passwords, or an input history. If you broadcast the display, shown inputs can become public through your streaming software.

Before this feature is released, this section will be updated to identify the actual capture scope, permissions, storage, and transmission. This description does not authorize future background monitoring or promise capabilities that have not been built.

08 / SECURITY & LOCATION

Protecting the information we use.

The app uses a credential vault for supported desktop authorizations, and the hosted connection service encrypts its saved credential/session records. Access is limited through service authorization and administrative controls. No system can promise perfect security; keep your PC, app, and account permissions up to date.

The operator’s service is hosted in the United States. Connected providers may process information in other locations. Provider-specific safeguards and choices are described in their notices. Local-only features keep their local files on the PC you use.

09 / CHANGES & ELIGIBILITY

As the app evolves.

Lyrift is intended for users who meet the eligibility requirements of the connected services. It is not directed to children under 13, and we do not knowingly seek their personal information. Contact us if you believe such information has been provided.

We will update the effective date when practices change. New monitoring, account, or sharing features should provide notice and the relevant choices before use. This policy describes privacy practices; it does not replace platform terms or grant a right to broadcast copyrighted music.

10 / OPEN COMMUNICATION CHANNEL

Questions about your data?

Contact Blighted, the developer/operator of Lyrift, for privacy questions or access/deletion requests.

[email protected] ↗

Include the feature, channel/account identifier, and request. Never include your password or authorization tokens.