Privacy policy

We have not appointed a data protection officer. Send every question about personal data to the email address above.

• You need an account to use the app. You sign in with Google or Discord. We store your email address, name, avatar address and your account ID at that provider. We never see your password.
• The app recognises text from a part of your screen on your own computer. Screen images never leave your computer. If you turn on crash reports, a report can contain a short piece of game text that the app was processing at the time.
• Kaption is free. We do not take payments, so we hold no card data.
• We do not use Google Analytics or ad pixels, we do not show ads and we do not sell data. We measure site traffic with our own statistics and with Cloudflare Web Analytics.
• In the referral program we store the IP address, browser and country of a person who signs up through a referral, to detect fraud.
• We set only two cookies ourselves, and both are for signing in.

• Screen images, screenshots or gameplay recordings.
• Payment card data. We do not take payments.
• Game login data. The app does not connect to the game client or the game servers.
• Keystrokes or mouse movements. The app only reacts to the shortcuts it registers with the system.
• Advertising data. We do not use Google Analytics, Facebook Pixel, Hotjar or ad trackers, and we do not profile you for marketing.

You create an account by signing in with Google or Discord.

• Google gives us your name or profile name, email address, profile picture address and Google account ID (scope openid email profile).
• Discord gives us your username, email address, avatar address and Discord account ID (scope identify email).

We also store when the account was created, when you last signed in and the account status (for example free beta). If you came to us through a partner or campaign link, at sign-up we also store that source and the country that Cloudflare derives from your IP address.

Purpose and legal basis: running your account and providing the service, Art. 6(1)(b) GDPR (contract, that is our Terms). We store the acquisition source under Art. 6(1)(f) GDPR. Our legitimate interest is knowing which channels bring new players.

How long: until the account is deleted.

Giving this data when you sign in is voluntary, but without it you cannot create an account or use the app.

When you activate the app on a computer, we store:

• the Windows computer name, which you later see in your device list,
• SHA-256 hashes of three hardware identifiers: the processor ID, the motherboard serial number and the serial number of the first disk. The app computes the hashes on your computer, so the numbers themselves never reach us,
• when the device was activated, last connected and removed, and the keys the app uses to encrypt translation packs on your computer.

While the app runs, it contacts our server about once an hour to confirm the activation. With that call it sends how many seconds the subtitles ran since the previous call. We store that number only for people who signed up through a referral (see "Referral program"). For everyone else we store only the time of the last call.

When the app downloads a translation pack, we store the account, device, file and time of the download, a hash of the IP address with a salt that changes daily, and the general client and system type (for example Windows, desktop).

Purpose and legal basis: the two-device limit per account and binding translation packs to your computer, Art. 6(1)(b) GDPR. Detecting abuse and protecting the packs from copying, Art. 6(1)(f) GDPR (our legitimate interest).

How long: device data until the account is deleted. A device you remove from the list stays in our records marked as removed, because we check it for referrals. Download entries are deleted automatically after 90 days. You can remove devices yourself on your account page.

The app captures the part of the screen you select, recognises the text in it and matches it against a translation pack. This happens on your computer. We do not send screen images to ourselves or to anyone else.

In the folder %APPDATA%\Kaption the app keeps its settings, the device activation data (protected with Windows DPAPI), the translation packs (encrypted and bound to your computer) and the log file app.log (up to 10 MB plus one older copy). We have no access to these files. We see them only if you send them to us yourself, for example as a diagnostic bundle, or to the extent described in "Crash reports".

The app also connects directly to servers that are not ours:

• gitlab.com: it downloads public game text files for Genshin Impact and Honkai: Star Rail shared by the community,
• enka.network, gi.yatta.moe, sr.yatta.moe and static.nanoka.cc: it downloads character, weapon and item icons for the characters tab.

These services see your IP address and the technical data of the request, as with any download. We give them no data about you or your account. The app downloads updates and the installer from our file server files.kaption.one, run by Cloudflare.

Crash reports are off by default. We send them only if you tick the option at first launch or later in Help › Privacy. You withdraw consent with the same switch. It takes effect at once and does not affect the lawfulness of reports sent before.

A report contains:

• the error: its type, message and stack trace,
• messages from the app log written at error level, up to 2,000 characters each. Such a message can contain a short piece of game text the app was recognising at the time,
• the app version and basic data about the system and runtime, for example the Windows and .NET versions,
• a random device activation ID. It lets us group reports from one installation and, when needed, link them to your device in our database.

A report does not contain your email address or any screen image.

GlitchTip (Burke Software and Consulting LLC, USA) receives and stores the reports on our behalf. It keeps them for 90 days, its default retention period, and then deletes them automatically.

Legal basis: your consent, Art. 6(1)(a) GDPR.

You can send feedback from the app: from the first-run wizard, from Settings or from the tray icon menu. We store the message (up to 2,000 characters), the account ID and email, the app type and version, a hash of the IP address with a salt that changes daily, and the general client and system type. One IP address can send 5 messages a day.

A copy of the message goes to our private Discord channel with a short account ID and without the email address, so we see it sooner.

When you write to contact@kaption.one, we process your email address and the correspondence. Zoho hosts our mailbox. When you write to us on Discord, we see your name and message, and Discord processes them under its own terms.

Purpose and legal basis: answering you and improving Kaption, Art. 6(1)(f) GDPR (our legitimate interest).

How long: feedback from the app is deleted from our database automatically after 90 days. We keep the Discord copy, emails and Discord messages for as long as we need them to handle the matter.

When someone signs up through your link or enters your code, we store the link between the two accounts, the code used and the date. About the invited person we also store:

• the IP address at the moment of sign-up or code entry,
• the browser identifier (the User-Agent header, up to 300 characters) and the country that Cloudflare derives from the IP address,
• the total time they used the app with subtitles on and the number of days they used it. The app sends this data with the calls described in "Devices, translation packs and downloads".

The referrer sees on their dashboard only a masked email address of the invited person (for example ab*@g*.com) and the referral status. They do not see IP addresses or device data.

How we detect abuse:

• When an invited account is activated on a computer the referrer uses (the same hardware hash, or 2 of the 3 identifiers), the system automatically cancels the referral and disables the referrer's code. The code stops working and no further milestones are granted.
• When an invited person connects from the same network as another person invited by the same referrer (the same IP range: /24 for IPv4, /64 for IPv6), the system only marks the referral for manual review. A shared connection at home or in a dorm does not count against anyone by itself.
• A person hands out the rewards, after checking the claim.

The first of these decisions is made automatically. If you think it is a mistake, for example because two people play on one computer, write to us. A person will review it.

Purpose and legal basis: running the program and giving rewards to the referrer, Art. 6(1)(b) GDPR (the program rules in the Terms). We process the invited person's data, including the IP address and usage time, under Art. 6(1)(f) GDPR. Our legitimate interest is counting active referrals honestly and preventing fraud.

How long: while both the referrer's and the invited person's accounts exist. Deleting either account deletes the referral record together with the IP address. Entries in the program's internal event log (random account IDs, the code and the country, with no email or IP addresses) are deleted or anonymised together with the account.

When you claim a reward, you choose a delivery method and give the data it needs: your PayPal email, the email to which we send an Amazon gift card, or your HoYoLAB UID and server region. We encrypt it in the database (AES-GCM). Only Kaption's administrator can decrypt it, to send the reward. We also store the claim status, dates and the delivery confirmation, for example a transaction number or card code, also encrypted.

Our private Discord channel may get a notice about the claim, with the account ID and the delivery method but without contact data.

To send the reward, we give the provider only what it needs: the email to PayPal, the email to Amazon if Amazon sends the card, or the UID and region to the HoYoverse store. These companies process the data under their own terms.

Purpose and legal basis: delivering the reward, Art. 6(1)(b) GDPR. We keep the documents needed for tax settlement under Art. 6(1)(c) GDPR.

How long: claim data until the account is deleted. Settlement documents, where the law requires us to keep them, until the tax liability lapses, as a rule 5 years from the end of the year in which the tax payment was due (Art. 86 § 1 with Art. 70 § 1 of the Polish Tax Ordinance).

When you submit a video on Discord or by email, we process your Discord name or email address, the channel name, the video link and its public statistics, the agreed rate and the payout details you give us. If we show your video on kaption.one, we credit it with the channel name and a link.

In the "Kaption in action" section we also show parts of YouTube recordings, credited with the author's channel name and a link to the video. The channel name may go to an AI model that helps us write clip descriptions (see "Who receives data").

Purpose and legal basis: the cooperation and the payout, Art. 6(1)(b) GDPR. Tax settlement, Art. 6(1)(c) GDPR. Crediting authors, Art. 6(1)(f) GDPR (our legitimate interest in correct attribution).

How long: for the cooperation and until claims from it lapse. Settlement documents for as long as tax law requires. The credit for as long as the video stays on the site.

When you fix Polish subtitle lines from the app or on the translator page, we store, linked to your account:

• your profile: the display name you choose (until you choose one, a pseudonym we give you), whether you are shown on the leaderboard, your role (translator, reviewer, or blocked from taking part) and, if you give it, an email address for payouts,
• what you send: suggested lines with the English line they are for, the translation shown at the time, the speaker and the previous line when the app sends them, whether a fix is for every speaker or only for a woman or a man, your notes, glossary terms and your votes on other people's suggestions. For suggestions sent from the app, also which of your devices sent them,
• the reviewers' decisions on your suggestions and terms, with the reason they give,
• your points, the month they count toward, and the amounts calculated and paid to you from the pool.

Your display name (the pseudonym until you choose a name), points and number of accepted suggestions appear on the public leaderboard, and reviewers see your display name next to your suggestions. This is on by default. You can turn it off in your profile at any time; the leaderboard then leaves you out and reviewers see only the pseudonym. We do not show the name from your Google or Discord account unless you choose it as your display name. The Kaption administrator also sees your account email and payout email. Accepted lines reach every Kaption user in the app and in translation packs, always without your name. For donations to the pool we record the amount, the date and the platform, and a donor name only if the donor agrees to have it shown on the pool page. Donation platforms process donors' data under their own terms.

Purpose and legal basis: running the program, points and payouts, Art. 6(1)(b) GDPR (the rules on the community page). Showing you on the leaderboard by default, Art. 6(1)(f) GDPR (our legitimate interest in crediting translators for their work and keeping the points behind the pool transparent); turning it off in your profile is how you object. Moderation, preventing abuse and handling reports about lines, Art. 6(1)(f) GDPR (our legitimate interest in correct and lawful subtitles). Payout and tax records, Art. 6(1)(c) GDPR.

How long: the profile, your votes and your points until your account is deleted. Suggestions, glossary terms and reviews stay after that as part of the translations, with no link to you or your devices. Payout amounts stay on the pool page without your name. Settlement documents, where the law requires us to keep them, until the tax liability lapses, as a rule 5 years from the end of the year in which the tax payment was due.

The daily puzzles of the guess games (Gendle, Stardle, Zendle, Wuwdle) never leave your browser. Ranked play works differently: you play it signed in, and our server keeps the puzzle and the score. For each ranked puzzle we store, linked to your account:

• the game, the mode and the day, the character picked as your answer and the data the feedback needs,
• your guesses with the time our server received each one, the puzzle's time limit and how long you took, the number of guesses, the result, the points and your streak,
• timing flags (a puzzle solved faster than a person can, guesses less than a second apart) and, if we review a result, our decision and its reason,
• your leaderboard profile: the nickname you choose, if any, whether the boards show you and, if we block you from ranked play, the reason.

The leaderboards are public. They show your place, points and number of solved puzzles under a name made from your account ID ("Player 3f9a2c") until you choose a nickname. On the leaderboard page you can change the nickname, go back to the numbered name or untick showing at any time. The boards then show "Hidden player" instead, and that choice stays until you change it. The Kaption administrator also sees your account email next to your results.

Before a ranked puzzle starts, Cloudflare Turnstile checks that a person is playing, not a script. The check runs in your browser from challenges.cloudflare.com and sends Cloudflare technical signals from your browser and your IP address. Our server then sends the check's token and your IP address to Cloudflare to confirm the result. We keep neither. To block abuse we also count ranked requests per account and per IP address (see "Logs and request limits").

Purpose and legal basis: ranked play and the leaderboards you join by playing it, Art. 6(1)(b) GDPR. Showing you on the boards by default, the timing checks, Turnstile and blocking cheats, Art. 6(1)(f) GDPR (our legitimate interest in fair boards). You can object to being shown at any time by unticking it.

How long: until your account is deleted. Deleting the account deletes your ranked results and your leaderboard profile.

Cloudflare runs kaption.one. On every visit it processes your IP address and the technical data of the request, to deliver the site and protect it from attacks.

Our statistics. To know where visitors come from, the site sends our server a short entry every time you open a page and when you click a download link. The entry holds the page address, the site you came from (its address and path, without parameters), UTM parameters and ad click IDs from the link (for example gclid), window and screen size, and the browser language and time zone. Our server adds the country, the general browser and system family, the device type, a hash of part of the IP address with a salt that changes daily, the Cloudflare request ID and a daily visitor key: a hash of part of the IP address and the browser header that changes at midnight UTC. It lets us count a visit once a day; we store neither the IP address nor the browser header themselves. Nothing is stored permanently in your browser for this: the site keeps the source of your visit (UTM parameters, the referring site) in tab storage until you close the tab. We do not link these entries to accounts, and we delete them automatically after 90 days.

When you arrive through a partner link (with the src parameter), we store the source, the page, the country, a hash of part of the IP address and the daily visitor key, once a day per source. We delete these entries after 90 days too.

Cloudflare Web Analytics. Our pages load the Cloudflare Web Analytics script, which counts visits and measures page load speed. According to Cloudflare, it uses no cookies and no browser storage.

Logs and request limits. Our API server keeps technical request logs at Cloudflare (time, request address, result and technical data, which can include the IP address) for no longer than 30 days. To block abuse, we count requests per IP address. The counters contain the IP address and expire on their own after 2 minutes to 2 days.

YouTube videos. On the home page, in guides and on character pages we show video thumbnails. They load from YouTube's image server (i.ytimg.com), so Google sees your IP address. The YouTube player itself loads only after you click: on character pages in privacy-enhanced mode (youtube-nocookie.com), elsewhere from youtube.com. Only then can YouTube set its own cookies. Google acts here as a separate controller.

Purpose and legal basis: running and securing the site and knowing where players come from without outside ad tools, Art. 6(1)(f) GDPR (our legitimate interest). You can object to this (see "Your rights").

Supabase runs the vote for the next languages. When you open the home page, your browser creates a random value, keeps it in browser storage and computes a SHA-256 hash from it together with your screen size, language, time zone and number of processor cores. The hash goes to Supabase to show your votes and block double voting. With a vote we store only the language, the hash and the date, without IP address, email or account. Without the random value in your browser, the hash cannot be linked to you.

Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in a fair vote). How long: indefinitely.

The vote for the next game. On the supported games page you can vote for the next game Kaption should support. With each vote we store the game, the time and a voter code. The code is a SHA-256 hash, made with a secret value only our server knows, of the day (UTC) and either your Kaption account ID, when you vote while signed in, or your network address (an IPv4 address, or the first half of an IPv6 address). We don't store the address or the account ID, and the code changes every day. It lets us count one vote per game per day. A nightly job deletes each vote on the second night after it was cast; only the number of votes per game stays, with no codes. To block scripted voting we also count vote requests per network address (see "Logs and request limits").

Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in a fair vote). How long: a vote with its code at most 51 hours; the number of votes per game indefinitely.

The waitlist form is no longer on the site. If you joined it earlier, Supabase may still hold your email address, site language and sign-up source until we delete the list or you ask us to delete them. Legal basis: your consent, Art. 6(1)(a) GDPR. You can withdraw it by writing to us.

On the My build page you enter a game UID and we show cards with your build. Our server fetches the data from Enka.Network (enka.network), which reads the public character showcase: what the game shows anyone on your profile, meaning your nickname, account level, characters and their gear. Enka.Network gets only the UID you enter from us. The card preview is drawn in your browser, so character art and icons we do not host ourselves load straight from enka.network or yatta.moe; those services then see your IP address and the technical data of the request. A background image you pick for a card never leaves your device: the page puts the card on it in your browser. After each read the page also remembers in your browser storage (kaption_build_memory) the UID, your nickname and the characters it showed (up to 60 per UID, for the 8 UIDs read last), so it can list your recently checked UIDs under the UID field and a later read can list the characters that have left your showcase. This never leaves your device. "Forget remembered" on the page deletes it for that UID, and so does the × next to a UID under "Recently checked".

The Today page can read the same showcase when you enter your UID there, to show which of your characters' talents you can level that day. It works through the same server and under the same rules described here, and it keeps the result in the same browser storage; "Remove from this browser" on that page deletes it.

The Kaption app for Windows reads the same showcase for its daily "What to farm today" card. When you save your Genshin Impact UID in Settings › Characters, the app keeps it in its settings on your computer and reads the showcase through the same server and under the same rules, at most once per server day (the day turns over at the 04:00 server reset). The request carries no account or device data. The app keeps a trimmed copy of the result on your computer in %APPDATA%\Kaption\Genshin\showcase.json: character names, their levels and talent levels. Nothing is read before you save the UID. "Remove UID and data" in Settings › Characters deletes both the UID and that copy.

The result stays in Cloudflare's cache (Workers KV) for as long as Enka.Network says, at least 5 minutes, and finished card images for up to an hour. Then they expire on their own. We do not store UIDs or results in a database, link them to a Kaption account or use them for statistics. To limit abuse, one IP address can read at most 30 UIDs a minute; the counter with the IP address expires after 2 minutes. The request URL (with the UID) can end up in the technical request logs described in "Website, statistics and logs".

A share link for a card (/s/<game>/<uid>/<character>) contains the UID. Anyone who opens it sees the same public data.

Purpose and legal basis: showing the public game data you ask for by entering a UID or opening a link, Art. 6(1)(f) GDPR (our legitimate interest). A UID alone usually does not identify a person, but together with a nickname it can, so we treat it as personal data. Enka.Network processes game data under its own terms: Enka.Network privacy policy.

How long: results only for the cache periods above, the request URL in the request logs for up to 30 days. We keep nothing else from this tool.

We set two cookies ourselves, both only after you sign in:

• kaption_session: an HttpOnly cookie with the session token, valid for 30 days from sign-in,
• kaption_signed_in: a marker with the value 1 that tells the site whether to ask the server about your account. Valid for the same time.

Both are strictly necessary to provide the service you ask for, which is signing in. That is why they need no consent (Art. 399(3) of the Polish Electronic Communications Law of 12 July 2024 and Art. 5(3) of Directive 2002/58/EC) and why we show no banner. Signing out removes both. We process the data in these cookies under Art. 6(1)(f) GDPR (keeping you signed in).

Cloudflare, which protects the site, may set its own security cookies when needed (for example __cf_bm or cf_clearance) to tell people from bots. YouTube can set its cookies only after you click the player.

The site also keeps a few entries in browser storage. You can delete them at any time in your browser settings. In persistent storage (localStorage):

• kaption_lang: the site language you chose,
• kaption_lang_banner_dismissed_v1: you closed the language suggestion bar,
• kaption_legal_notice_2026_11: you closed the notice about the updated Terms and Privacy policy,
• kaption_ref and kaption_src: a referral code or a partner source from a link (with UTM parameters), for 30 days. We use them only when you create an account, to credit the person or partner who invited you,
• kaption_src_dismissed: you closed the partner welcome banner, for 7 days,
• kaption-voter-salt, kaption-voted, kaption-votes and kaption-votes-ts: the random value for the voter hash, your votes and cached vote results,
• kaption-game-votes: the games you voted for today from this browser and the vote counts we returned, so the page remembers your votes when you reload it. Entries from earlier days are removed on your next visit,
• kaption_card_presets: card settings you saved under a name on the My build page, until you delete them,
• kaption_build_memory: the UIDs you checked on the My build and Today pages (the 8 read last) with each player's nickname, the time of the last read and the characters those pages showed you, per game and UID (up to 60 per UID), until you click "Forget remembered" or the × next to the UID under "Recently checked" (My build), or "Remove from this browser" (Today),
• kaption_today: the server, the game filter, the "Only my characters" switch and the UID you picked on the Today page, until you clear your browser data,
• kaption_guess: your guesses in the daily Guess the character puzzles, per game and mode (each day kept for 400 days), whether you answered the skill bonus right, and your totals per game and mode (puzzles played and solved, number of guesses, streaks), until you clear your browser data. It never leaves your browser,
• kaption_guess_ranked: the ranked switch from an earlier version of the guess game pages. The pages no longer have it, and your next visit to a guess page removes the entry,
• kaption_guess_legend: you closed the colour hints box on the guess game pages, until you open it again,
• kaption-waitlist-joined: a marker that you joined the old waitlist.

In tab storage (sessionStorage), which is cleared when you close the tab, we keep kaption_attrib_first and kaption_attrib_last: the first and the latest source of your visit in that tab (UTM parameters, the referring site, ad click IDs). When you leave a ranked puzzle to sign in, we also keep kaption_guess_return there: the puzzle page to bring you back to. The entries kaption_anon, kaption_pv_dedup, kaption_src_hits, kaption_attrib_first and kaption_attrib_last that earlier versions of the site kept in localStorage are removed on your next visit.

Processors. These companies process data on our behalf under data processing agreements as required by Art. 28 GDPR:

• Cloudflare, Inc. (USA): the site (Pages), the API server (Workers), the database (D1), files (R2), request counters and cache (KV), request logs, Web Analytics and the human check before ranked puzzles (Turnstile). Privacy policy
• Supabase Pte. Ltd. (Singapore): language votes and the old waitlist. Privacy policy
• Burke Software and Consulting LLC, trading as GlitchTip (USA): crash reports, only with your consent. Privacy policy
• Zoho: the contact@kaption.one mailbox. Privacy policy

Other recipients. These companies process data as separate controllers, under their own terms:

• Google: sign-in with Google, YouTube thumbnails and player. Privacy policy
• Discord: sign-in with Discord, our community server and private channels with notices about feedback and reward claims. Privacy policy
• GitLab, enka.network, yatta.moe and nanoka.cc: servers from which the app downloads public game data and icons. They see only your IP address and the technical data of the request.
• Enka.Network: the source of public game data for the "My build" tool. It gets only the UID you enter, from our server. Privacy policy
• PayPal, Amazon and HoYoverse: only if you choose them for a reward.
• Public authorities: when the law requires it.

Services that receive no user data. We produce translations of game text, guides, team suggestions, update notes and some images with AI models in Microsoft Azure OpenAI. We send them game text and game data and, for promo clip descriptions, the public name of the channel we credit. We do not send them any data about Kaption users: no email addresses, IP addresses, feedback or screen images. The server that prepares translation updates runs on Oracle Cloud and handles game data only.

We do not sell data and do not share it with advertisers.

Some providers are based outside the European Economic Area (in the US or Singapore) or operate globally: Cloudflare, Supabase, GlitchTip, Zoho, Discord, Google and Microsoft. When data leaves the European Economic Area, we rely on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework (for companies certified under it) and otherwise on the standard contractual clauses adopted by the Commission. You can get a copy of these safeguards by writing to us.

• Account, the acquisition source linked to it, devices (including removed ones), referrals and reward claims: until the account is deleted.
• Translation pack download entries: 90 days.
• Feedback from the app: 90 days in our database. The Discord copy, emails and Discord messages: as long as needed to handle the matter.
• Site statistics and visits from partner links: 90 days.
• The "My build" tool: results in the cache for as long as Enka.Network says, at least 5 minutes; card images up to an hour; the request counter with your IP address 2 minutes.
• Request logs at Cloudflare: up to 30 days. Request counters: 2 minutes to 2 days.
• Crash reports: 90 days.
• Language votes: indefinitely. Waitlist: until we delete the list or you ask us to remove your address.
• Next-game votes: each vote with its voter code at most 51 hours; the number of votes per game indefinitely.
• Creator cooperation: for the cooperation and until claims from it lapse.
• Ranked play in the guess games: results and the leaderboard profile until the account is deleted.
• Community translations: the profile, votes and points until the account is deleted; suggestions, glossary terms and reviews after that too, with no link to you. Donation records: for as long as the pool runs and the accounting rules require.
• Settlement documents for rewards and creator payouts: until the tax liability lapses, as a rule 5 years from the end of the year in which the tax payment was due.
• One-time sign-in data (OAuth state): 10 minutes. Revoked tokens: until they expire.

You have the right to:

• access your data and get a copy (Art. 15 GDPR),
• have it corrected (Art. 16 GDPR),
• have it erased (Art. 17 GDPR),
• restrict processing (Art. 18 GDPR),
• data portability for data you gave us, where we process it on the basis of a contract or consent (Art. 20 GDPR),
• object to processing based on our legitimate interest (Art. 21 GDPR),
• withdraw consent at any time, without affecting the lawfulness of earlier processing (Art. 7(3) GDPR),
• lodge a complaint with a supervisory authority (Art. 77 GDPR).

You can also ask for a person to review an automatic cancellation of a referral.

To use these rights or delete your account, write to contact@kaption.one from the email address linked to your account. We delete the account on your request. Together with it we delete devices, download entries, referrals, your referral code, reward claims, your community profile with its votes and points, and the acquisition source, and we delete or anonymise the entries in the referral program's event log. We keep only what the law requires us to keep. We also delete your feedback from our database and, if you ask, its Discord copies. You can remove devices yourself on your account page. We reply within 30 days.

Kaption is not aimed at children under 16. Under Art. 8 GDPR, people under 16 in the EU need a guardian's consent when a service relies on consent. If you believe a child gave us data without that consent, write to us and we will delete it.

When we change this policy, we change the date at the top. We flag material changes on the home page for at least two weeks. We do not announce minor edits separately.

If you think we process your data unlawfully, you can complain to:

If you live in another EU country, you can also turn to the data protection authority there.