Your musical memories belong to you.

What Reeesound stores

When you use Reeesound, we may store:

• Songs and music links you share
• Written reflections and memory notes
• Voice note transcriptions
• Basic account information such as email and phone number
• Waves metadata needed for product functionality

Voice notes and audio

Voice notes sent to Reeesound may be temporarily processed to generate text transcriptions.

Reeesound is designed to prioritize long-term memory preservation through text and structured traces rather than permanent storage of raw audio recordings.

Audio files may be deleted after transcription and processing.

AI-assisted pathways

Reeesound uses AI systems to help generate possible pathways between memory traces inside your Waves.

These pathways are suggestions, not factual interpretations, diagnoses, or psychological evaluations.

The purpose of Sherpa is to help users revisit and explore their own memories through music.

Private by default

Reeesound is not designed as a public social platform.

Your Waves and reflections are intended to remain private unless you explicitly choose to share something externally.

Reeesound does not sell personal memory data to advertisers.

Security and infrastructure

Reeesound uses modern infrastructure providers and authentication systems to help protect user accounts and stored information.

Reasonable efforts are made to secure personal data and limit unauthorized access.

Contact

If you have questions about privacy, data handling, or account concerns, you can contact:

YouTube connection and data

Reeesound uses YouTube API Services to support Mixtape exports you request. Connecting is optional and takes place through Google’s authorization screen. Reeesound does not receive your Google password.

When you connect, Reeesound receives authorization credentials and identifies the YouTube channel associated with the connection. We store the channel identifier, granted permissions, connection status and relevant connection timestamps. A credential that allows continued authorized access is encrypted and stored on our backend. Short-lived access tokens are used server-side and are not stored as permanent connection records or returned to the Reeesound interface.

To support an export, Reeesound uses selected YouTube video identifiers and may access video titles, channel information, descriptions, durations and availability information. Our recording-selection tooling can search YouTube and inspect candidate video metadata.

When you request an export, Reeesound sends Google the playlist title, description and selected video identifiers. The description is based on your Mixtape summary and includes a Reeesound attribution and export reference. These details can reflect the meaning of your Reflection. The playlist is created as private.

Reeesound reads channel, playlist and playlist-item information to check the destination, confirm progress and recover interrupted exports. Recovery may inspect playlists in the connected channel to locate an export. Connection and export records are processed by Reeesound’s backend and database infrastructure. Google processes information sent to its services under the Google Privacy Policy.

You can request Disconnect YouTube from your YouTube connection settings. This blocks new authorized activity while Reeesound processes revocation and removes stored YouTube connection and export details, including playlist links. If revocation cannot be confirmed, the interface continues to show a pending state rather than reporting success.

Disconnecting does not delete playlists already created in your YouTube account. Your Reeesound Reflections and Mixtapes remain. Reeesound may retain a historical export receipt without the erased YouTube details; that receipt does not provide the old playlist link. Fresh authorization is possible once disconnection is confirmed.

You can also revoke Reeesound’s access through Google’s security settings. To ask about stored data or request deletion, contact [email protected].

Use of YouTube is also subject to the YouTube Terms of Service.

YouTube data retention and recovery

The music links and memories you share are distinct from information retrieved from YouTube. Reeesound does not use YouTube page or oEmbed lookups to enrich new music links with titles or artwork. Identifiable older YouTube enrichment is removed; independently sourced information and your own links, memories, Reflections and Mixtapes are preserved.

Necessary stored YouTube details are periodically verified or removed. Authorization checks are due daily, and retained channel and export details are due for verification after 25 days. Details that cannot be verified expire locally by day 29; details with unknown age are removed rather than assigned a new age. Temporary service failures can delay processing and require operator attention.

Periodic checks can detect loss of authorization through Google; detection is not instantaneous. When authorization is confirmed unavailable, Reeesound blocks its use and removes associated stored YouTube details. Removal or expiry can remove Reeesound’s playlist link without deleting the playlist from your YouTube account. A native historical receipt may remain.

Temporary selection and approval files are limited to 24 hours and are retired after use or expiry. Sensitive recovery backups may contain YouTube details and encrypted credentials from the time of backup. Our manual rollback-backup policy limits these copies to 24 hours or an earlier applicable deletion deadline. Longer-lived recovery material should exclude those details and credentials.

Restores are handled in isolation with authorized activity disabled. Newer deletion evidence and expiry rules must be applied before service resumes. If that evidence cannot be recovered, restored YouTube details and credentials are not reactivated. Authorization must be revalidated or connected afresh before authorized activity resumes.

Application diagnostics avoid YouTube payloads and credentials, and application access logs omit URL query values. Infrastructure providers also maintain operational logs under their own retention settings. These protections do not retroactively remove information from older logs or backups.