Privacy
Last updated July 14, 2026
1. Information stored in your browser
Scorvia uses browser local storage for sport and view preferences, shortlists, comparisons, scout notes, and imported CSV player records. This information stays in the browser unless you intentionally export and share it.
2. CSV files
CSV imports are parsed locally in the browser. The current app does not upload the file to an application server. You are responsible for avoiding sensitive or unauthorized personal data and for complying with the rules that apply to your organization.
3. Information the host may process
The hosting provider may receive ordinary technical request data such as IP address, browser information, requested URL, timestamp, and error or security logs. Review and configure the privacy settings of the host used for deployment.
4. External font requests
The current interface may request web fonts from Google Fonts. That provider may receive technical request information such as an IP address. Self-host the fonts before launch if your organization requires all assets to remain first-party.
5. Payments and analytics
The current Scorvia interface does not collect payment information and does not initialize a product analytics SDK. If accounts, analytics, payments, email, cloud sync, or live data providers are added later, this notice must be updated before those features launch.
6. Clearing or exporting local data
You can export database views and shortlists from the app. You can remove locally stored data by clearing site data in the browser. Clearing site data may permanently delete notes, imported records, and shortlists.
7. Security
Local storage is not an encrypted vault. Do not store passwords, authentication tokens, payment data, medical records, highly confidential scouting information, or other sensitive personal data in notes or CSV imports.
8. Children and athlete data
Recruitment work can involve minors. Do not collect, infer, publish, or share information about a minor unless your organization has a lawful basis, appropriate consent where required, and suitable safeguarding controls.
9. Contact
Add the operator’s legal name and privacy contact before public commercial launch. That contact should handle access, correction, deletion, objection, and data-rights requests where applicable.