1. Introduction

Goosebumps ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service.

2. YouTube API Services

This Service uses YouTube API Services to provide video playback and search functionality. By using our Service, you are also agreeing to be bound by Google's privacy policies:

• Google Privacy Policy
• YouTube Terms of Service

3. Information We Collect

3.1 Personal Information

You sign in with your Google account (see 3.8). We do not ask for or store a password. With your account we keep:

• Email address
• A username — a random placeholder until you choose your own public name

3.2 Skin Conductance (EDA) Data

Skin conductance — also called Electrodermal Activity, or EDA — is a measure of how much your skin sweats, which rises when you react to something. We collect and store:

• Skin conductance measurements from a supported Wear OS watch with a built-in EDA sensor (sessions recorded before October 2026 may also hold measurements from an Arduino-connected EDA sensor, which is no longer supported)
• Timestamps of emotional spikes and responses
• Baseline skin conductance values
• Video playback synchronization data

As with heart rate below, the watch app streams skin conductance to the phone over the Wearable Data Layer and the phone forwards it to our backend. The watch app does not transmit data directly to our servers.

3.3 Heart Rate Data

From your heart rate sensor (Wear OS watch, Bluetooth chest strap, or other BLE heart rate monitor), we collect:

• Real-time heart rate (BPM) readings while a session is active
• Detected heart-rate spikes and their timestamps relative to video playback
• Resting / baseline heart rate values used to calibrate spike detection

On Wear OS, the watch app reads heart rate from the device's built-in sensor and streams it to the phone over the Wearable Data Layer; the phone forwards the values to our backend. The watch app does not transmit data directly to our servers.

3.4 Skin Temperature and Watch Temperature

On supported Samsung Galaxy watches, the watch app measures the temperature of the skin under the watch about every 10 seconds while a listening session is active. With each measurement we also record the watch's own temperature readings (the sensor's surrounding temperature and the battery temperature) and whether the watch is charging, because a warm watch warms the skin it reads. These readings are stored with each song you listen to and are shown to you before a song when your wrist is still cold. Watches without this sensor send none.

3.5 Movement Data

While a song plays, the watch app reads its motion sensors (accelerometer and step counter) so that movement, such as walking or adjusting your wrist, is not mistaken for an emotional reaction. With each heart rate reading we store how much you were moving, your step rate and a movement label (for example "walking" or "fidgeting"). We do not record your location.

3.6 Your Answers About Your Reactions

After a song, the app replays the moments where it detected a reaction and asks whether you got goosebumps or wept, and which emotion you felt. We store your answers, the emotion words you choose or type, and any moments you mark as missed.

3.7 Video Interaction Data

We collect information about your interactions with YouTube videos:

• Video IDs and titles of songs you listen to
• Playback duration and timestamps
• Search queries for finding music

3.8 Google Account Data (when signing in with Google)

If you choose "Sign in with Google" on the web or Android app, Google shares the following with us via OAuth:

• Your Google account email address
• Your Google profile name and avatar URL
• A stable Google account ID used to link your sign-ins

We do not request access to your Gmail, Drive, Calendar, contacts, or any other Google service data. You can revoke our access at any time from your Google account permissions page.

3.9 Camera Data (Optional, web app only)

If you turn on the camera in the web app, it reads your facial expression about once a second while a song plays:

• The analysis runs entirely in your browser. Camera video and images are never stored or sent to our servers.
• Only the result is sent to our servers and stored with that listen: an expression label (such as "happy" or "surprised"), how confident the analysis is, and the moment in the song.
• The camera is off unless you turn it on, and you can turn it off at any time.

3.10 Mobile App Data (Android Phone & Wear OS)

The Goosebumps Music Android phone and Wear OS apps collect and process the following on-device data to deliver core functionality:

• Foreground service state: The phone app runs a foreground service while a listening session is active so that heart-rate streaming and video synchronization continue while the screen is off. Android shows a persistent notification while the service is running.
• Currently playing media metadata: When YouTube is playing in the background on Android, the app reads the current track's title and (where available) video ID from the system MediaSession to keep playback in sync with your physiological data. We do not access media from other apps unrelated to the current listening session.
• Bluetooth and nearby-device permissions: Used solely to discover and connect to your heart-rate sensor or Wear OS watch. We do not scan for, identify, or store information about other nearby devices or people.
• Floating overlay (Android only): If you grant the "draw over other apps" permission, the phone app can show a small "Next Song" overlay that launches the next YouTube video. The overlay does not capture screen contents.

3.11 Chrome Extension Data

The optional Goosebumps Chrome extension reads YouTube playback state (current video ID, title, and play/pause status) from the active YouTube tab so that spike detection can be aligned to what you are watching. The extension does not read content from other tabs, does not use the YouTube Data API, and does not transmit browsing history.

3.12 Cookies and Local Storage

We use cookies and browser local storage to:

• Maintain your login session (session cookies)
• Store authentication tokens
• Remember your preferences and settings
• Enable YouTube video playback functionality

YouTube also sets its own cookies when videos are played. Please refer to the Google Privacy Policy for information about their cookie usage.

3.13 Technical Information

We automatically collect:

• Browser type and version
• Device information
• IP address (for security purposes only)
• Usage patterns and interactions with the Service
• Android app logs: at the end of each song, the phone app sends its own diagnostic log messages (what the app was doing, connection and sensor status, errors) to our servers, labelled with your user ID, username, phone model and app version. They are used only to find and fix problems. The app can read only its own log messages, not those of other apps.
• Error reports: when something goes wrong in the web app, a report of the error, your browser type, the page address and your user ID is sent to us so we can fix it.

4. How We Use Your Information

We use the collected information to:

• Provide and maintain the music analysis Service
• Authenticate your identity and manage your account
• Synchronize physiological data with video playback
• Detect and analyze emotional spikes during music listening
• Calculate emotional compatibility with other users
• Generate personalized music recommendations
• Conduct our own in-house research into how musical chills work, using your heart rate, skin conductance, and listening history. This research is not reviewed by a university or an ethics board. Anything published from it describes patterns across many listeners and never identifies you — see the consent screen shown when you first open the app, and our research page
• Improve and optimize the Service performance
• Communicate important updates or changes to the Service
• Ensure compliance with our Terms of Service

5. How We Share Your Information

5.1 With Other Users

We may share limited information with other users for compatibility matching:

• Your username (publicly visible)
• Emotional compatibility scores (aggregated data only)
• Shared song preferences (if you participate in compatibility features)

5.2 With Third Parties

We share data with the following third-party services:

• YouTube/Google: Video IDs and search queries are sent to YouTube API Services to retrieve video content and metadata
• Google Cloud Platform: Our backend runs on Google Cloud Run and stores account information, physiological data (skin conductance, heart rate, skin temperature and movement), and session history in Google Cloud SQL (PostgreSQL), encrypted in transit and at rest. Android app logs are kept in Google Cloud Logging. Google acts as a data processor on our behalf.
• Google Sign-In: If you choose to sign in with Google, your email, profile name, avatar, and Google account ID are received from Google via OAuth and stored to link your sign-ins.

We do NOT sell your personal information or physiological data to advertisers or other third parties.

5.3 Legal Requirements

We may disclose your information if required by law, court order, or government regulation, or if necessary to protect our rights, property, or safety.

6. Data Retention

We retain your information as follows:

• Account data: Retained while your account is active, plus 30 days after deletion
• Heart rate, skin conductance (EDA), skin temperature and movement measurements, and your answers about your reactions: Stored until you delete your account, for historical analysis, compatibility matching, and research
• Android app logs: Deleted automatically after 30 days
• Error reports: Kept until you delete your account
• Video playback history: Retained for personalized recommendations
• Session cookies: Cleared when you log out or after 30 days of inactivity
• Camera video and images: Never stored (processed on your device only); expression labels are kept with the listen they belong to

7. Your Rights and Choices

You have the right to:

• Access: Request a copy of your personal data
• Correction: Update or correct inaccurate information
• Deletion: Permanently delete your account and all associated data at any time. Sign in and visit our Account Deletion page to delete everything yourself in one click — no email required. If you can't sign in, email jesseboulard@goosebumpsmusic.app and we'll delete your account within 30 days.
• Data Portability: Export your heart rate and skin conductance (EDA) data in a standard format
• Opt-Out: Turn off the camera or compatibility matching features at any time
• Revoke Consent: You can revoke YouTube API access by visiting Google security settings

8. Data Security

We implement security measures to protect your information:

• Sign-in through Google, so we never handle a password
• HTTPS encryption for all data transmission
• Secure session management with HTTP-only cookies
• Database encryption at rest (via Google Cloud SQL)
• Regular security audits and updates

However, no method of transmission over the Internet is 100% secure. We cannot guarantee absolute security of your data.

9. Children's Privacy

Our Service is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Last Updated" date. Your continued use of the Service after changes constitutes acceptance of the updated policy.

11. Contact Information

If you have questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:

• Email: jesseboulard@goosebumpsmusic.app
• Response Time: We will respond to all inquiries within 7 business days

12. Third-Party Links

Our Service contains links to YouTube and other third-party websites. We are not responsible for the privacy practices of these external sites. We encourage you to read their privacy policies when visiting them.