Privacy Policy
What personal data Grindhouse collects, why, who it's shared with, how long it's kept, and your rights over it.
This policy explains how Sanjay Ahlawat, a sole proprietor in India trading as Ahlawat Solutions, who runs Grindhouse ("we", "us"), handles your personal data when you use grindhouse.gg and its cloud servers. We're the data controller (the "data fiduciary" under India's Digital Personal Data Protection Act, 2023). We collect only what's needed to run the Service, we don't sell your data, and we don't show ads.
1. What we collect
You give us
- Account: your email address, a password (stored only as a salted hash), and a display name.
- Match sharing: your Steam match-history authentication code and latest share code, if you add them, so we can fetch your matches. The code is stored encrypted.
- Uploads and creations: demos you upload (including demos for scouting other players), routes, lineups, strats, arenas, routines, goals and settings.
- Coach questions: what you ask the coach.
- Support tickets: what you write in a ticket in the app, the files you attach, and the app and system details sent with it (app version, operating system).
- Messages: what you send us by email.
From services you connect
- Steam: your Steam ID and public profile (name, avatar, profile link), and your CS2 matches and their demo files from Valve, including your Premier rating.
- FACEIT (if you link it): your FACEIT player ID, nickname, level, Elo, avatar, country and matches.
- Payment providers: your subscription status, the plan, amounts, dates, coupon used, and the provider's customer and payment references. We don't receive or store your full card or bank details.
- Discord (if you link it): your Discord user ID, display name and avatar, and the sign-in tokens Discord gives us (stored encrypted), so our Discord bot can give you roles and open ticket threads for you.
- Our Steam bot (if you add it as a Steam friend): your Steam ID, that you're friends with it, and the messages you and the bot exchange.
Collected as you use it
- Training data: sessions, scores, kills, reaction times and similar stats from your cloud servers.
- Server use: when your cloud servers run, their region and hours.
- Technical data: IP address, browser type and times of requests, in server logs and for rate limiting and security; the time you last signed in.
- Affiliate links: when you open the website through a creator's link (?ref= or /r/), we record a click: the creator's code, the campaign tag in the link, the page you landed on, the site you came from, the time, and a one-way hash of your IP address, browser and the day with a secret of ours, so we can count unique visitors. The hash can't be turned back into your IP address or browser. Your browser keeps the code and the click in local storage (gh_ref) so that, when you sign up or sign in, your account is linked to that creator (your "referral"), and a creator code you use at checkout does the same.
Matches include other players: their Steam names, IDs and in-game stats appear in your match pages, replays and scouting reports, as they do in CS2's own demos.
2. Why we use it
| Purpose | Legal basis |
|---|---|
| Run your account, sign you in, fetch and analyse your matches, start cloud servers, show stats, replays, leaderboards and coaching | Contract (providing the Service you asked for) |
| Take payments, manage subscriptions, refunds and invoices | Contract; legal obligation (tax and accounting records) |
| Send sign-in codes, security notices and billing messages | Contract; legitimate interest (keeping accounts safe) |
| Product news by email, only if you opted in | Consent (withdraw any time in Settings or with the link in the email) |
| Count affiliate clicks, link a referred account to the creator who sent it, and pay creators their commissions | Legitimate interest (running the affiliate program); contract (for affiliates) |
| Prevent abuse, fraud, cheating and repeated trials; keep the Service secure | Legitimate interest |
| Fix bugs and improve the Service, using aggregated or technical data | Legitimate interest |
| Meet legal requests and protect our rights | Legal obligation; legitimate interest |
We don't make decisions about you with legal or similarly significant effects by automated means alone. Leaderboards and practice ratings rank training results only.
3. Who we share it with
We share data only with the service providers we need to run Grindhouse, under contracts that limit their use of it to providing their service to us:
- Hosting and database
- Google Cloud (servers and database in Finland, in the EU)
- Network and security
- Cloudflare (DNS, TLS, protection against attacks)
- Email delivery
- Amazon Web Services (Amazon SES, EU region)
- Cloud game servers
- DatHost, which runs your CS2 servers; it receives your server's settings and the training files it needs, and sees the IP addresses of players who join
- AI coach
- One of Anthropic, OpenAI or OpenRouter, depending on the model we've chosen. It receives your question and the match and training data needed to answer it, which includes the names of the other players in those matches. Anthropic and OpenAI don't use API data to train their models by default. OpenRouter passes the request to the chosen model's own provider, whose data terms then apply
- Support replies
- When we answer a ticket, we may have one of the same AI providers draft the reply. The draft request includes the ticket's messages (including our internal notes), your display name, your plan and subscription status, and the app and system details sent with the ticket. A person reads, edits and sends every reply; nothing is sent to you automatically
- Discord
- If you link Discord: our bot gives you roles in the Grindhouse Discord server that show members of that server your plan (subscriber or trial) and your Premier tier or FACEIT level; it posts weekly leaderboards there and opens ticket threads for you. You can unlink Discord at any time in Settings
- Steam bot
- If you add our Steam bot as a friend, it sends you messages about your analysed matches through Steam (Valve). It only messages people who added it; send
!muteor remove it as a friend to stop the messages - Payments
- Whichever provider you pay with: Stripe, Paddle, Razorpay, Lemon Squeezy or Dodo Payments. Paddle, Lemon Squeezy and Dodo Payments act as merchant of record and are separately responsible for the payment data they collect
- Steam and FACEIT
- Valve and FACEIT, to sign you in and fetch your profile and matches
Affiliates. A creator you were referred by sees you in their referrals only as the first letter of your name followed by stars, with when you joined, whether you're on a trial or a paying customer, your plan and what they earned from your payments. They never see your email, Steam account or what you do in Grindhouse. If you're an affiliate, we keep your application (channels, audience, message, country), your payout method and details (encrypted) and your commissions and payouts.
What you make public is visible to other players: your display name, Steam avatar and scores on leaderboards (you can hide yourself in Settings → Privacy), and items you publish to the Community hub. Players you invite to your server see what happens on it.
We may also disclose data if the law requires it, to protect people's safety or our rights, or to a successor if the Service is transferred (we'll tell you first). We never sell personal data or share it for advertising.
4. International transfers
Our main servers are in Finland, in the EU; some providers process data in other countries, including the EU, the United States and wherever your cloud server region is. Where data leaves your country, we rely on the provider's legal safeguards, such as the European Commission's standard contractual clauses.
5. How long we keep it
- Your account and training data: for as long as your account exists.
- Support tickets: while your account exists, and up to 2 years after a ticket is closed, so we can follow up on the same problem.
- Steam bot messages: 30 days.
- Affiliate clicks: 400 days, then deleted. The gh_ref entry in your browser stays until it links your account to the creator (or can't), or until the link window runs out (30 days by default), whichever is first. If the creator's code gives a discount, it stays after linking until the window runs out, so the code can be filled in at your first checkout. You can clear it yourself at any time.
- Affiliate records: referrals, commissions and payouts are accounting records, kept for up to 8 years like payment records. When a referred player deletes their account, the referral stays without any link to them. When an affiliate deletes their account, the affiliate account is closed, its payout details are erased, and its commissions and payouts stay for accounting.
- When you delete your account (Settings → Privacy → Delete account): first, any paid plan is cancelled with the payment provider (this doesn't refund the current period). If that cancellation fails, nothing is deleted and you're told, so you're never left paying for an account that's gone. Then your profile, sign-in sessions, linked accounts (including Discord and its ticket threads), training data and files, demo uploads, goals, coach chats, support tickets and their files, scouting and other personal rows are deleted, and your Community items are unpublished (copies other players already added stay with them). Matches stay, because they belong to everyone who played in them, but they're no longer linked to an account of yours.
- Kept after deletion: payment records (for up to 8 years after the payment, as tax and accounting law requires); a record that a free trial was used, with your Steam ID stored only as a one-way hash, so trials can't be repeated; coupon redemptions; coach usage records (cost and outcome only, never the text); our admin audit log; cloud server usage and cost records; and shared match data.
- Server logs: kept for a short time for security, normally no more than 90 days.
- Backups: deleted data can stay in encrypted backups until they're overwritten, normally within 35 days.
6. Your rights
Depending on where you live (including under India's DPDP Act, the EU and UK GDPR and US state laws), you can:
- access a copy of your personal data and learn how it's used;
- correct data that's wrong (most of it you can edit yourself in Settings);
- delete your data, yourself in Settings, or by asking us;
- take your data with you in a machine-readable format: Settings → Privacy → Download my data gives you a zip with your account, your rows in every table (training sessions, ratings, goals, routines, coach chats, scouting dossiers, support tickets and their files, subscriptions and payments, your affiliate account with its commissions and payouts, your Discord link, your uploads) and your own line in each match you played. It never includes passwords, codes or tokens, our internal notes, or other players' data. You can download it once every 10 minutes;
- object to or ask us to restrict processing based on legitimate interest;
- withdraw consent, such as for product emails, at any time;
- nominate someone to exercise your rights if you die or can't (DPDP Act);
- complain to a data protection authority, such as the Data Protection Board of India or your local authority in the EU or UK.
Email [email protected] from your account's email. We answer within 30 days, and don't charge for it. We may ask you to prove it's your account first.
7. Security
Connections are encrypted with HTTPS, passwords are hashed, secrets such as match codes and payment keys are encrypted at rest, and access to the production systems is limited to the operator. No system is perfectly secure; if a breach affects your data, we'll tell you and the authorities as the law requires.
8. Children
Grindhouse is only for people 18 and older: you confirm your age when you sign up. We don't knowingly collect data from anyone under 18. If you think someone under 18 has given us data, email us and we'll delete it.
9. Cookies
We use no tracking or advertising cookies. Affiliate links keep one entry in your browser's local storage (gh_ref, above). See the Cookie Policy.
10. Changes
We'll post any change here and update the date at the top. For important changes we'll tell you by email or on the website before they apply.
10 November 2026: our servers and database moved from Microsoft Azure in India to Google Cloud in Finland, in the EU (Who we share it with, International transfers). What we collect, why, who else receives it and how long we keep it didn't change.
11. Contact and grievance officer
Data controller and grievance officer: Sanjay Ahlawat, proprietor of Ahlawat Solutions, operating Grindhouse, First Floor, H.No. 175/B, Bhatia Colony, Ballabgarh, Faridabad, Haryana 121004, India. Email [email protected]. More ways to reach us on the Contact page.