What Aimwise collects, why, who else sees it, and how to make us delete it. Aimwise is a Discord bot that generates coaching reads from Valorant screenshots you upload.
The data controller for the personal data described here is [LEGAL ENTITY], [BUSINESS ADDRESS]. To exercise any right in this policy, open a ticket in the Discord server.
2. What we collect
Account data
Your Discord user ID — the numeric ID, which is how your account and history are keyed.
Your Riot ID, if you choose to set one with /link. This is optional and used for display only.
Your subscription tier (free, pro, or elite) and the Stripe customer and subscription identifiers associated with it.
Match data
The statistics read from each screenshot you submit: map, result and round score, agent, ACS, kills, deaths, assists, ADR, headshot percentage, KAST, econ rating, first bloods and first deaths.
The coaching read generated for that match.
The Discord CDN link to the screenshot you uploaded, so the read can display the source image. We store the link, not a copy of the image; the file itself lives on Discord's servers under Discord's control.
Whether you shared a given review to a server channel, and when.
Clips
If you attach a clip on a paid tier, we download it, extract a small number of still frames, send those frames to our AI provider for analysis, and delete the downloaded file and the extracted frames from our server once the read is generated. We do not retain clips.
Server data
For each server the bot is installed in: the server ID and name, its allowlist status, and a monthly count of reviews used.
Channel and role IDs you configure for the welcome, auto-role, and shared-reviews features.
If someone applies to add Aimwise to a server: the Discord username, server name, server ID, approximate member count, and the reason given on the application form.
Operational logs
Our server keeps ordinary application logs and a record of AI usage and cost per request, used to enforce spending limits and to debug failures.
3. What we do not collect
Your email address. Stripe holds a billing email; we do not store one.
Your payment card details — those go directly to Stripe and never reach us.
Messages you send in Discord, other than the commands you run with the bot.
Anything from other Discord servers, or any data from the Valorant game client or the Riot API.
Advertising identifiers. We run no advertising and no analytics. See Cookies & Tracking.
4. Why we use it, and our legal basis
If you are in the UK or the EEA, the UK GDPR and EU GDPR require us to name a legal basis for each use:
To generate coaching reads — performance of our contract with you.
To store match history and compute pattern analysis — performance of our contract. Pattern analysis is the feature; without stored history the bot cannot do it.
To enforce tier limits, server caps, and spending caps — our legitimate interest in keeping the Service running and affordable.
To take payment and manage subscriptions — performance of our contract, and compliance with our tax and accounting obligations.
To review server applications and operate the allowlist — our legitimate interest in controlling quality and cost during beta.
To investigate abuse and keep the Service secure — our legitimate interest in protecting the Service and its users.
We do not use your data to train AI models, and we do not sell it.
5. Who we share it with
We share the minimum each provider needs to do its job:
Anthropic — the extracted match statistics, your match history, and (for clip reviews) the extracted frames are sent to the Claude API to generate your read. See Anthropic's Privacy Policy.
Stripe — handles checkout and recurring billing, and holds your payment details directly. See Stripe's Privacy Policy.
Discord — the platform the bot runs on. Every message, DM, and uploaded file passes through Discord, and uploaded files are hosted on Discord's CDN. See Discord's Privacy Policy.
Our hosting provider — runs the bot and stores its database.
We may also disclose data where we are legally required to, or where it is necessary to establish, exercise, or defend legal claims.
6. International transfers
Our providers above operate in the United States, so your data is transferred outside the UK and EEA. Those transfers rely on the safeguards each provider has in place — typically the European Commission's Standard Contractual Clauses and the UK Addendum, as described in their own privacy documentation.
7. How long we keep it
Match history and coaching reads — kept while your account exists, so pattern analysis can work. You can clear them yourself at any time with /dev clear-history, or ask us to.
Account and subscription records — kept while your account exists. Billing records are kept by Stripe for as long as tax and accounting law requires, typically six to seven years.
Clips and extracted frames — deleted as soon as the read is generated.
Server applications — kept while the server is on the allowlist, and for a reasonable period after a decision.
Operational logs — kept only as long as needed for debugging and cost control.
8. Your rights
Depending on where you live, you have some or all of the following rights over your personal data:
Access — get a copy of what we hold about you.
Rectification — have inaccurate data corrected.
Erasure — have your data deleted.
Portability — receive your data in a machine-readable form.
Restriction and objection — limit or object to processing based on our legitimate interests.
Withdraw consent — where we rely on consent, withdraw it at any time, without affecting processing already carried out.
Complain — to your data protection authority. In the UK that is the ICO; in the EEA it is your national supervisory authority.
If you are a California resident, you also have the right to know what we collect, to request deletion, to correct inaccurate data, and not to be discriminated against for exercising those rights. We do not sell or share personal information as those terms are defined under the CCPA/CPRA.
How to exercise them
Delete your match history yourself at any time with /dev clear-history. For anything else — a copy of your data, full account deletion, or a correction — open a ticket in the Discord server. We will respond within 30 days.
9. Children
The Service is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child under 13 has used the Service, open a ticket and we will delete the account and its data.
10. Automated processing
Coaching reads are generated automatically by an AI model. This is automated processing, but it produces written feedback about a video game and has no legal or similarly significant effect on you. We do not use it for profiling that affects your rights, and we make no decisions about you on the basis of it beyond enforcing the plan limits described in the Terms.
11. Security
Access to the bot's database and to our providers' dashboards is restricted to the people who operate the Service. Data in transit is encrypted. No system is perfectly secure, and we cannot guarantee absolute security — but if a breach affects your data and the law requires us to tell you, we will.
12. Cookies
This website sets no cookies, runs no analytics, and loads no third-party assets — the Inter typeface is served from our own domain rather than Google's CDN. Details in Cookies & Tracking.
13. Changes
We may update this policy. For material changes we will give notice in the Discord server before they take effect. The "last updated" date at the top always reflects the current version.
14. Contact
Open a ticket in the Discord server for any privacy question or request.