1. Who controls your information
Before public launch, the company operating LiveRank must insert its complete legal name, address, privacy contact, and any required representative information here. This notice applies to the LiveRank website, accounts, and private workspaces.
2. Information we process
- Account information: name, email, password hash, plan, session records, memberships, and invitations.
- Billing information: subscription identifiers and billing status after a payment provider is connected. Full payment-card details should remain with that provider.
- Private workspace information: saved prospects, notes, tags, roster handles, import metadata, and team activity.
- Public creator intelligence: creator handles, display names, rankings, diamond totals, league, region, live status, history, and derived estimates or eligibility signals.
- Security and operations: request identifiers, timestamps, limited error records, IP-derived security signals, and device/browser information needed to protect and operate the service.
3. How information is used
Information is used to authenticate users, provide the shared rankings and private workspace, enforce plan and seat permissions, import rosters, prevent abuse, troubleshoot failures, communicate service matters, process subscriptions when enabled, and improve product reliability.
4. Roster uploads
CSV and XLSX roster files are parsed under strict size limits. LiveRank stores normalized creator rows needed for the workspace and does not intentionally keep the original uploaded workbook after processing.
5. Sharing
Private workspace data is available to authorized members of that workspace. Production vendors may process limited information for hosting, database storage, payments, transactional email, monitoring, and support under appropriate contracts. LiveRank should not sell private workspace data or use private notes to create a shared customer dataset.
6. Retention
Account and workspace data is retained while the account is active and for a documented period afterward for recovery, security, legal, and billing needs. Reset and invitation tokens expire quickly. The production retention schedule—including backup deletion timing—must be finalized and published before launch.
7. Security
The current product uses salted password hashing, opaque hashed session tokens, HttpOnly cookies, same-origin and CSRF checks, server-side authorization, rate limits, restricted uploads, and workspace-scoped access. No internet service can guarantee absolute security. Production launch additionally requires HTTPS, managed secrets, off-device encrypted backups, monitored alerts, and an incident-response process.
8. Your choices and rights
You may request access, correction, export, or deletion of account and private workspace information, subject to legal and security exceptions. Applicable privacy law may provide additional rights such as objection, restriction, portability, or appeal. A verified privacy-request channel and identity-confirmation workflow must be configured before public launch.
9. Cookies
LiveRank uses an essential session cookie to keep users signed in and protect account access. Optional analytics or advertising cookies should not be enabled without updating this notice and, where required, obtaining consent.
10. International use and children
Production hosting locations and any international transfer safeguards must be disclosed when selected. LiveRank is a business product and is not directed to children. Do not create an account if you cannot lawfully agree to its terms.
11. Changes and contact
Material changes should be dated and communicated appropriately. A monitored privacy email, business address, and jurisdiction-specific disclosures must be added before public launch.