Privacy Policy

Unlike traditional web applications, Ritmo does not require or maintain a user registration framework. We do not collect, request, or store your:

• Legal name, username, or profile identifier.
• Email address, physical mailing address, or phone contact details.
• Account authentication details (passwords, social media login keys).
• Financial, payment method, or premium billing records.

To optimize performance and track your learning milestones without administrative logging overhead, the Application leverages your local hardware device storage. Your learning metrics—including accumulated hours listened, active difficulty level selections, individual song history, and dictionary item preferences—are processed and saved strictly within your web browser's sandboxed partition using native web platform mechanisms (such as localStorage or IndexedDB).

• Control over data: This data remains entirely under your custody. You can permanently erase all tracked metrics at any time by clearing your browser's site footprint, empty-caching your application data, or deleting the PWA from your hardware system.
• Data loss hazard: Because this data is not backed up on remote database clusters, wiping your web browser data cache, factory resetting your smartphone or desktop computer, or migrating to a new physical device will result in the permanent deletion of your metrics history.

If you explicitly execute an optional multi-device sync or progress merge feature inside the setting panel, the Application generates a temporary, encrypted text string token. This handshake payload transmits your local metrics to a transient, non-persistent, serverless key-value memory layer (such as Redis) to allow another device to read and merge the data.

• This temporary sync code features an automatic Time-To-Live (TTL) expiration window of ten (10) minutes.
• The transmission payload is permanently deleted from the transient server container the instant the second device successfully inputs the verification token, or immediately upon expiration of the ten-minute limit.

The Application interfaces with external media interfaces to render audio streams and visual metadata components. When you interact with these assets, your hardware browser environment shares technical network endpoints directly with third-party servers.

• YouTube API & player embedding: Audio snippets and tracking markers are generated using the public YouTube Embedded Player interface wrapper (react-player). Your device communication, IP address routing, and background data transfer during these play sequences are governed exclusively by the external YouTube Terms of Service and Google Privacy Policy.
• Public media CDNs & asset proxies: To populate layout cover graphics without hosting static repository content, the Application utilizes open proxy routes referencing the public Spotify Content Delivery Network (CDN). Loading these graphic layers exposes standard browser headers and network routing requests to those public asset distribution networks.
• Hosting & edge telemetry: The infrastructure assets are deployed and hosted via serverless edge networks (such as Vercel). These hosting entities automatically generate baseline structural server logs containing system asset performance indexes, client browser signatures, and network IP routing addresses solely to optimize technical request pathways and prevent security exploits. These system logs are completely decoupled from your internal localized learning statistics.
• Google Analytics (GA4): The Application uses Google Analytics 4 to collect anonymized usage data, including page views, song play events, and difficulty level filter interactions. Google Analytics sets cookies in your browser to distinguish sessions and report aggregated behavioral patterns. No personally identifiable information is transmitted. Data collected is governed by the Google Privacy Policy. You may opt out at any time by enabling "Do Not Track" in your browser settings, using a browser-level ad blocker, or installing the Google Analytics Opt-Out Browser Add-on available at tools.google.com/dlpage/gaoptout.

The Application functions purely as an educational tool analyzing real-world public media and language structures. We do not knowingly compile, request, or target tracking metrics toward individuals under the age of thirteen (13). If a minor has utilized a local device configuration, parents or legal guardians can wipe the accumulated footprint instantly by clearing the physical browser cache on that specific machine.

This privacy framework has been compiled and engineered to protect user privacy under data minimization standards. Any formal operational disputes, regulatory compliance claims, or execution inquiries emerging from this software architecture shall be interpreted and governed under the laws of the State of Arizona, United States, and will be processed exclusively within municipal courts located in Scottsdale, Arizona.

The developer reserves the definitive right to adjust or update this Privacy Policy to mirror engineering refactors or external API constraint changes. When adjustments occur, the modification date at the top of this document will be updated. Continued usage of the application canvas following an updated version index represents full acceptance of the amended operational policies.

If you discover an error inside the automated translation components, or if you have specific compliance questions regarding the localized telemetry layers, you may submit feedback or report software bugs by accessing our public feedback channel link located in the discovery page footer components.