2. Information We Collect
We collect several types of information to operate, secure, and improve the Services.
2.1 Information You Provide to Us
We may collect the following information directly from you:
Account Information
- Name
- Email address
- Password (for non-SSO users)
- Role (individual, group member, institutional teacher, institutional student, institutional admin)
Payment Information
- Payments are processed by Stripe.
- SongBase does not store credit card numbers or banking details.
User-Created Content
Depending on your account type, you may create or upload:
- Custom translations
- Custom IPA database entries
- Forked or custom works
- Notes associated with works
- Audio recordings
- IPA exercises
- Exercise responses and progress data
- Comments on student work (teachers only)
Support and Communication
- Emails, messages, or other communications you send to us.
2.2 Information Collected Automatically
When you access SongBase, we automatically collect:
- IP address (through server logs and internal analytics)
- Browser and device type
- Operating system
- Referring URL
- Pages viewed
- Actions taken within the platform
- Session duration and timestamps
- Crash logs, errors, and diagnostics
- Authentication status (SSO, OAuth, or password)
These logs help us operate and secure the platform and improve performance.
2.3 Cookies & Tracking Technologies
We use the following:
- Session Cookies (for login and navigation)
- Functional Cookies (to remember preferences)
- Google Analytics (GA4)
- GA4 anonymizes IP addresses automatically and cannot store full IPs.
- GA4 does not allow SongBase to identify specific individuals.
- Internal SongBase Analytics System
- Tracks usage, exercises, interactions, and performance.
- Users can select anonymous internal tracking, which removes identifiable data from internal analytics.
What we do NOT use:
- Advertising cookies
- Third-party marketing trackers
- Behavioral advertising pixels
A separate Cookie Notice provides additional details.
2.4 Information from Third-Party Logins (OAuth)
If you sign in using Google, LinkedIn, or Facebook, we may receive:
- Name
- Email address
- Profile image (if provided)
- Authentication token
We do not receive your password.
2.5 Information from Institutional Single Sign-On (SSO)
When you sign in through your institution, we may receive:
- Name
- Email address
- Institutional affiliation
- Role attributes (teacher, student, admin)
Your institution controls the attributes it shares.
2.6 Information from Institutions
Institutions may send:
- Directory attributes
- License or seat data
- Admin user lists
- Optional usage or enrollment context