Security & Your Data

    Scrim data is the most sensitive asset a team owns. Here is how it is handled.

    Handing your practice games to an outside platform is a real decision, and “trust me” is not an answer. This page states what is actually true about how Prolytics stores and separates your data, so you can check it against whatever your organization requires before anything is connected.

    Team isolation is enforced in the database

    Separation between teams is applied by row-level security policies in PostgreSQL, not by hiding buttons in the interface. A request for another team's scrims does not return filtered data — it returns nothing, because the policy never matches.

    Your scrims, your drafts, your notes and your scouting reports are readable by accounts belonging to your team. No other customer's account can reach them, whatever they type into a URL.

    Accounts are created by invitation, with roles

    There is no public signup. Accounts exist because someone with authority on your team invited them, and every account carries a role — coach, analyst or player — that decides what it can see and change.

    You decide who on your staff gets access to what. Removing someone removes their access immediately.

    Where your data comes from

    Your own games reach Prolytics through your organization's GRID account. Professional match data comes from GRID, public competitive history from Leaguepedia, and solo queue data from the Riot API.

    Prolytics is not endorsed by or affiliated with Riot Games.

    Your data stays yours

    Ask and your data is exported to you. Ask and it is deleted. Neither request needs a reason, and neither is treated as a retention conversation.

    Nothing about your games is used to build features, statistics or benchmarks for another team. Your scrim history is not a product input.

    Agreements

    A data processing agreement is available and will be signed on request. If your organization has a security questionnaire, send it over — it gets a real answer rather than a marketing one.

    If something goes wrong that affects your data, you hear about it from me directly, quickly, and in plain language.

    Still have a question?

    Ask it before you commit to anything. I would rather answer a hard question now than have your staff wondering about it mid-split.