Privacy policy
This policy explains what data Loot handles, why, who it is shared with, how long it is kept and how you can use your rights. It covers the app (app.lootdeep.com), this website and Loot Collect (the PC app and the Chrome extension).
1. Who we are
Loot (Loot DeepTracker) is a management and data analysis system for poker teams. Each team uses Loot in its own space, isolated from other teams. The people who use it are the team's members: leader, manager, coach and player.
Loot is run by its founder, Matheus Teixeira. Contact for any privacy matter, including as the data protection officer under Brazil's LGPD: contato@lootdeep.com.
2. Who decides about your data
- Your account data (login, name, email, language, security and app usage): Loot is the controller.
- Data the team records or receives about its work with players (ledger, tournaments, hands, lessons, contracts, messages, videos): the team is the controller. Loot processes this data on the team's behalf, as a processor (GDPR) or operator (LGPD), only to provide the service to the team.
If your request is about data your team controls, you can talk to the team directly or write to us; we will pass it on to the team and help answer it.
3. What data we handle
- Account and profile: email, name, nick, photo, language, country, time zone, phone and Discord (optional), date of birth (optional; you can hide your birthday) and notification preferences.
- Team membership: role, level, date you joined the team, deal, player profile and notes from management.
- Ledger: accounts and nicks on poker networks, balances per network, transactions (reloads, withdrawals, returns, transfers), makeup, splits, payouts, debts, costs, wallets (including crypto wallet addresses) and proof images.
- Tournaments: the Sharkscope CSV files imported by the player or by management, with the network, date, buy-in, prize, finishing position and type of each tournament.
- Hand histories (HH): the files the player sends in the app, through Loot Collect on the PC or through the Loot Collect extension from GG's PokerCraft. A hand also contains the nicks and actions of the other players at the table, as they appear in the file. Loot uses this only for the stats and study of that player and their team, together with the notes on opponents that the person writes.
- Calendar and lessons: events, lessons, attendance, coach availability, lesson payments and lesson reports.
- Communication: internal chat and group messages, messages from management, the Board, Results, hand discussions, polls, reactions and attached images.
- Contracts: the team's contract templates and PDF contracts and the record of each signature (who signed, when, and the IP address and browser used), which serves as proof of acceptance.
- Video library: the lesson videos from YouTube or Vimeo that the team links to Loot, who can watch each one, and what each person watched: the parts seen, the time, the playback speed, the replays and where they stopped.
- Battle and goals: challenges between players on the team, rating, ranking and performance goals.
- Applications: if you apply to a team through its link, what you fill in on the form (such as contact details, phone, Discord and answers), and the hands and Sharkscope CSV you send.
- Usage and security: the date of your last access and the country of the connection (Loot stores only the country, as reported by Vercel; this record does not store the IP address or the city), the list of countries you connected from with the last date for each, the IP address used for a few minutes to limit attempts at sign-up, password changes and other sensitive requests, server technical logs and, when support asks for it, the Loot Collect log.
- Push notifications: the subscription address your browser creates when you turn on notifications on your phone or PC.
- Usage analytics: see section 6.
- YouTube and Vimeo connections: see sections 7 and 8.
Almost all of this comes from you or your team. Loot does not buy data and does not match your data against outside databases.
4. Why we use it and on what legal basis
- Providing the service the team signed up for (showing the ledger, tournaments, stats, lessons, chat and video library to those allowed to see them): performance of a contract (GDPR art. 6(1)(b); LGPD art. 7, V) and, for team data, the team's instructions.
- Keeping Loot secure (login, rate limits, isolation between teams, abuse investigation): legitimate interest (GDPR art. 6(1)(f); LGPD art. 7, IX).
- Understanding usage and fixing errors with analytics: legitimate interest.
- Measuring Loot's ads on Instagram and Facebook, with the Meta Pixel on the website: your consent, given in the website's cookie notice (GDPR art. 6(1)(a); LGPD art. 7, I).
- Sending service emails and alerts (invitations, bell alerts, reports, team announcements): performance of a contract. Non-essential emails have an unsubscribe link in the footer, and you choose your alerts in the notification preferences.
- Connecting the team's YouTube or Vimeo: the authorization management gives on the Google or Vimeo screen.
- Complying with the law and answering requests from authorities: legal obligation.
Loot does not sell data, does not use app data for advertising and does not use your data to train artificial intelligence models. Loot's ratings, scores and analyses are readings of past data for the team and the player; Loot makes no automated decisions that have legal effects on you.
6. Analytics and cookies
In the app. Loot uses PostHog (servers in the European Union) to learn which pages and buttons are used, how long people spend on each page and where errors happen. The record includes your Loot identifier, email, nick, team and role, plus technical browser data. PostHog also records the session (what is on screen and the clicks) so we can find errors. Recording is set up to capture nothing you type and to hide money values on the finance screens.
On the website. The website uses Vercel Web Analytics, which counts visits in aggregate and does not use cookies. If you accept cookies in the website's notice, it also loads the Meta Pixel, from Meta (the owner of Instagram and Facebook). The pixel records the visit, whether you saw the plans and whether you clicked to talk to us, so we can measure Loot's ads. Meta also handles this data under its own privacy policy and may link it to your Instagram or Facebook account. Without your consent, the pixel does not load. You can change your choice at any time under "Cookies" in the website footer.
Cookies and local storage. The app uses cookies to keep you logged in and to record your last access at most every 10 minutes. PostHog stores an identifier in the browser. The website stores the language you chose and your cookie choice in the browser. With your consent, the Meta Pixel stores Meta cookies in the browser. The YouTube and Vimeo players, when they play a video inside Loot, may use their own cookies under Google's and Vimeo's policies. The app does not use advertising cookies. Blocking PostHog in your browser does not remove any app feature.
7. Google and YouTube
A team's management (leader or manager) can connect the team's YouTube channel to Loot's video library by signing in with Google (OAuth). Only management can connect, change and disconnect it.
What Loot asks Google for, and why
https://www.googleapis.com/auth/youtube.readonly(always): to read the team's channel (ID, name and address), its playlists (name and number of videos) and video data (title, description, thumbnail, duration, publish date, visibility, whether embedding is allowed, processing status and age restriction). With this, Loot lists and syncs the videos every hour and plays each video inside Loot, in YouTube's embedded player, for the people management has allowed.https://www.googleapis.com/auth/youtube.upload(only when the team turns on lesson uploads): to publish to the team's own channel the lesson recording that the coach or management chooses to send through Loot. The video is published as Unlisted, with embedding allowed, in the Education category, with the title and description the person wrote. The file goes from the browser straight to YouTube: it does not pass through Loot's servers and is not stored on them.
Loot does not read comments, subscribers, messages, channel analytics, watch history or data from other channels, and does not edit or delete videos on the channel.
Where it is kept and who sees it
The access token is stored encrypted on Loot's server, in Supabase Vault. It never goes to the browser and is used only for that team. Loot's database keeps the video data listed above to build the video library. The videos are seen by the team members management has allowed; the team's staff see all of them.
How to disconnect and delete
Management can disconnect at any time in Manage the video library › Sources › Disconnect. When it disconnects, Loot revokes the token at Google and deletes it from the Vault. You can also remove Loot's access on your Google Account security page: https://myaccount.google.com/permissions.
After a disconnection made in Loot, we delete the data received from the YouTube API through that connection within 7 days. If access is revoked directly at Google, we delete it within 30 days. While the connection exists, this data is refreshed every hour and is never kept more than 30 days without being refreshed. If you ask for deletion at contato@lootdeep.com, we delete it within 7 days.
Limited Use
Loot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Google data is used only for the video library features described above.
- Loot does not use Google data for advertising, does not sell it and does not use it to train artificial intelligence models.
- Loot does not transfer this data to third parties, except the providers that run the service (section 5), when the law requires it, or to protect the security of the service.
- No one at Loot reads this data except with your permission, to investigate abuse or a security issue, or when the law requires it.
Loot uses YouTube API Services. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google handles your data under the Google Privacy Policy.
8. Vimeo
Management can also connect the team's Vimeo account. Loot asks for the public and private scopes to read the account's videos, including unlisted ones, and play them inside Loot. When the team turns on lesson uploads, it also asks for upload, create, edit and interact: to create the lesson video, create the "Loot" folder, allow Loot's domain for embedding and put the video in the folder. The token is stored encrypted in Supabase Vault, and disconnecting in Manage the video library › Sources revokes it at Vimeo. Use of Vimeo is subject to Vimeo's Terms of Service and Privacy Policy.
9. Automatic translation
For teams that subscribe to automatic translation, the text of messages is sent to the Anthropic API (Claude model), which returns the translation in each reader's language. The translation is stored with the message. Under the API's commercial terms, Anthropic does not use this text to train models. Each person chooses in their profile whether to read translations. Messages written from countries or regions where Anthropic's service is not available are never sent to it; Loot knows this from the country in the profile and the country of the connection.
10. How long we keep data
- Account and team data: for as long as your account and the team exist in Loot. When a team stops using Loot, we delete its data at the team's request, except what the law requires us to keep.
- Chat: text is kept while the player is on the team. Images disappear after 7 days (images in pinned messages stay). Results disappear after 24 hours. When someone leaves the team, their history is kept for 90 days pending any request and is then deleted.
- Loot Collect: the original file is deleted as soon as it is processed; if processing fails, it is kept for up to 7 days for diagnosis. The app log sent to support is deleted after 7 days.
- Applications: the hands of a rejected application are deleted right away; the rest is kept for the period the team has set, and the applicant can ask for deletion earlier. Abandoned drafts are deleted after 30 days.
- YouTube data: as described in section 7.
- Rate limit counters: a few minutes.
11. Security
Each team is isolated in the database by row-level access rules. All traffic uses HTTPS. YouTube and Vimeo tokens are stored encrypted in the Vault. Proofs, contracts, hands and attachments are kept in private storage, and access follows each person's role. No system is immune to failure; if an incident affects your data, we will notify you, the team and the authorities as the law requires.
12. International transfers
Loot's database is in Brazil (Supabase, in São Paulo). For people in the European Union, storing data in Brazil is itself an international transfer, covered by the safeguards below. Some of the providers in section 5 process data outside Brazil and the European Union, for example in the United States. In those cases we rely on the contractual safeguards these providers offer for international transfers, as the GDPR and the LGPD require.
13. Your rights
Under the GDPR (European Union) and the LGPD (Brazil), you can ask for: confirmation that we process your data, access, correction, deletion, portability, information on who we share it with, restriction or blocking, and objection to processing. Where processing depends on your consent, you can withdraw it at any time.
You can correct much of it yourself in your profile. For anything else, write to contato@lootdeep.com. We reply within 15 days, and within one month at most for requests under the GDPR. If the request concerns data your team controls, we pass it on to the team and help answer it. You can also complain to your data protection authority in the European Union (in Portugal, the CNPD) or to the ANPD in Brazil.
14. Minimum age
Loot is for people aged 18 or over who are old enough to play poker where they live. We do not knowingly process data of minors; if it happens, we delete it.
15. Changes to this policy
The version date is at the top of this page. When a change is significant, we will tell you in the app or by email before it takes effect.