Privacy Policy
Introduction
NILDash is a NIL (Name, Image, and Likeness) deal intelligence platform designed for sports agents and college athletes. It provides tools for managing NIL opportunities, tracking outreach to brand partners, automating deliverable schedules, and communicating directly with sponsors through connected email and calendar integrations.
NILDash is operated by Compton Group LLC. This Privacy Policy explains how we collect, use, disclose, and protect information when you use the NILDash platform at https://mynildash.com (the "Service").
By accessing or using the Service, you agree to the collection and use of information described in this policy. If you do not agree with any part of this policy, please do not use the Service.
Information We Collect
We collect information you provide directly and information generated through your use of the Service:
Account Information
- Name and email address provided at registration
- Password (stored as a one-way cryptographic hash; we never store your plaintext password)
- Role (sports agent or athlete) and associated agent–athlete relationship
- Profile details such as sport, school, and social media handles (athletes)
Google Account Data (when you connect Google)
- Gmail address associated with the connected Google account
- OAuth refresh token allowing NILDash to send email and create calendar events on your behalf
- We request only the minimum necessary scopes:
gmail.sendandcalendar.events
Instagram Data (only when an athlete connects Instagram)
- What we collect from Instagram, why, and how to remove it is in Section 05.
Email and Calendar Content
- Subject lines, body text, and recipient addresses of emails composed and sent through NILDash
- Deliverable titles, due dates, and notes synced to Google Calendar
- Email send history stored in your NILDash account for tracking purposes
Usage Data
- Pages and features accessed within the platform
- Actions taken (e.g., deals created, emails sent, deliverables completed)
- Timestamps and activity logs used to improve the Service and provide analytics to agents
How We Use Your Information
We use the information we collect solely to provide, maintain, and improve the NILDash Service:
- Platform functionality: to authenticate users, power the dashboard, and enable core features such as pipeline management, AI analysis, and reporting
- Gmail sending: when an athlete connects their Gmail account, we use their OAuth token solely to send emails they compose in the NILDash portal, directly from their own Gmail address
- Google Calendar sync: when a user connects Google Calendar, we create and update calendar events corresponding to NIL deliverables they choose to sync
- Communications: to send transactional notifications (e.g., athlete invite emails, delivery confirmations) via our email provider
- Platform improvement: to understand how features are used so we can improve the product
- Security: to detect, prevent, and respond to fraud, abuse, or security incidents
- Business activity on NILDash: NILDash may show that a business has completed an NIL deal on the platform, without revealing the agent, athlete, or deal terms
Google API Services
NILDash uses Google API Services, including the Gmail API and Google Calendar API, to enable athletes and agents to send emails and manage deliverable schedules directly from their connected Google accounts.
Compliance with Google Policies. Our use of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements. Specifically:
- We use Google user data only to provide or improve the user-facing features of NILDash that are clearly described in this Privacy Policy
- We do not use Google user data for advertising purposes
- We do not allow humans to read your Google data except with your affirmative consent, for security purposes, or as required by law
- We do not transfer Google user data to third parties except as necessary to provide the Service (see Section 8) or as required by law
Scopes we request. NILDash requests only the minimum scopes necessary:
https://www.googleapis.com/auth/gmail.send: to send emails on behalf of the athlete from their own Gmail addresshttps://www.googleapis.com/auth/calendar.events: to create and update deliverable events in Google Calendarhttps://www.googleapis.com/auth/userinfo.email: to confirm which Google account was authorized
Disconnecting Google. Athletes and agents can disconnect their Google account at any time from the NILDash dashboard. Upon disconnection, the stored OAuth refresh token is immediately deleted from our database. We will not use revoked credentials to send email or access your calendar.
Instagram Data
An athlete can connect their Instagram account so that they and their agent see real numbers instead of numbers typed in by hand. We collect nothing from Instagram until the athlete taps Connect Instagram and approves access on Instagram.
What we collect. Only after the athlete approves, we collect:
- Their username and account type, and their profile details: display name, bio, website and profile picture
- Their follower count, following count and media count
- Their last 25 posts: caption, type, timestamp, likes and comments, and a link to each post
- Insights for those posts: reach, views, saves, shares, interactions, profile visits and follows, and watch time for reels
- Account insights for the last 30 days: reach, views, accounts engaged, interactions, follows and unfollows, and taps on the profile link
- Their audience: the age, gender and location (city and country) of their followers and of the people who engage with them, as Instagram reports it
An athlete who cannot connect can send us screenshots of their Instagram Insights instead. We read the same kinds of numbers from those images and treat them the same way.
Why we use it.
- To show the athlete and their agent accurate reach and engagement
- To build the athlete's media kit
- To match the athlete with brands that fit their audience
Who sees it. The athlete, and the agent the athlete connected their account for. We never sell it, and we never use it for advertising. A brand sees it only in what is sent to that brand to pitch the athlete: a pitch or the athlete's media kit can show numbers such as followers, reach and engagement. We never share it with a brand in any other way.
How we store it. Instagram access tokens are encrypted. We keep the data while the connection is active and refresh it each night. If the athlete removes NILDash in Instagram, we delete the access token and stop collecting right away; what was already collected is deleted when the athlete asks us to delete it, as below.
How to remove it.
- In NILDash: Disconnect on the athlete page in NILDash. The athlete's agent can do it for them. We delete the access token and everything we fetched from the account right away.
- In Instagram: go to Settings > Apps and websites, find NILDash and remove it. Then choose to send a data deletion request. Meta's data deletion callback tells us, and we delete everything we fetched from the account and give you a confirmation code.
- By email: write to contact@mynildash.com and we will delete it for you.
Checking a deletion request. The status page is
https://mynildash.com/api/instagram/deletion-status.
Meta gives you a link to it with your confirmation code. You can also enter the code on
https://mynildash.com/api/instagram/data-deletion.
Data Storage and Security
All NILDash data is stored on Railway, a U.S.-based cloud infrastructure provider, in a PostgreSQL database. Railway employs industry-standard physical and network security controls.
We take the following measures to protect your information:
- Password hashing: passwords are stored using bcrypt, a one-way hashing algorithm. We cannot recover or view your plaintext password.
- HTTPS: all data in transit between your browser and our servers is encrypted using TLS.
- OAuth token storage: Google OAuth refresh tokens are stored in the database with access restricted to the NILDash application server only.
- Authentication: user sessions are protected with signed JSON Web Tokens (JWTs).
- Access controls: agent accounts can only access their own athletes' data; athlete accounts can only access their own records.
While we implement commercially reasonable security measures, no system is 100% secure. In the event of a data breach that affects your personal information, we will notify you as required by applicable law.
Your Rights
You have the following rights with respect to your personal information:
- Access: you may request a copy of the personal information we hold about you
- Correction: you may request that we correct inaccurate or incomplete information
- Deletion: you may request deletion of your account and all associated personal data at any time
- Google integration disconnect: you may revoke NILDash's access to your Google account at any time from your NILDash dashboard or directly from your Google Account permissions. Upon disconnection, your OAuth token is immediately deleted from our systems.
- Data portability: upon request, we can provide your data in a machine-readable format
To exercise any of these rights, contact us at contact@mynildash.com. We will respond within 30 days. We may need to verify your identity before processing certain requests.
Third-Party Services
NILDash integrates with and relies on the following third-party services to operate. Each has its own privacy policy and data practices:
- Google (Gmail API, Google Calendar API, Google OAuth): Google Privacy Policy
- Anthropic (AI analysis features using the Claude API): Anthropic Privacy Policy
- Resend (transactional email delivery, e.g., athlete invite notifications): Resend Privacy Policy
- Meta (Instagram API, only for athletes who connect Instagram): Instagram Privacy Policy
- Railway (cloud hosting and database infrastructure): Railway Privacy Policy
We share your information with these providers only to the extent necessary to provide the Service. We do not authorize any of these providers to use your data for their own marketing or advertising purposes. Data shared with Google APIs is governed by the Google API Services User Data Policy described in Section 4.
Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, the Service, or applicable law. When we make material changes, we will:
- Update the "Last updated" date at the top of this page
- Notify registered users via email at least 14 days before the change takes effect, for changes that materially affect how we use your personal information
Your continued use of the Service after the effective date of a revised policy constitutes your acceptance of the changes. We encourage you to review this page periodically.
Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or how we handle your data, please contact us: