← Back to Kai-zo-ro

Privacy Policy

Effective date: 17 October 2026  ·  Version 1.15

Version 1.15: in the phone app you can now switch on reminders. They are off until you switch them on, they are planned on your phone, and nothing about them is sent to us. To time them, the app keeps on your phone the time you first opened it on each of the last 28 days, and deletes it when you switch reminders off (sections 4 to 8, 16 and 19). Players under 18 choose their reminder time themselves and never get one between 21:00 and 07:00. No new data reaches us. Version 1.14: we now back up our database once a day instead of once a week, still keeping each backup for 30 days, so that if we ever have to restore one, we can delete again every account deleted since it was made (section 16). It also says plainly that players who see you on the Global or Country leaderboard can send you a friend request (section 4), and that the age question asks you to confirm your answer and, if you are under 16, asks again after 24 hours (section 19). No new data is collected. Version 1.13: a name is hidden after three reports only when they are about the name itself or about threats or harassment, and the app tells you if yours is hidden (section 5). Version 1.12: Kai-zo-ro is now for people aged 16 and over. The app asks your age once and keeps only your age range (16–17, or 18 and over) on your device; it is not sent to us (section 19). Also, when a player reports a hero for threats, harassment or sharing contact details, our server emails our mailbox an alert at once, without any player's name or friend code, so a person can act the same day; the alert about a new quest proposal no longer carries its text or the author's name either (sections 5, 9 and 16). This version also adds a short version at the top, describes our international transfers provider by provider (section 18), and covers a handover of Kai-zo-ro to another person, not only to a company (section 22). No new data is collected. Version 1.11: a community quest can have a photo, which the app loads from our database provider, Supabase; like any server, it sees your IP address when it sends the photo (sections 8 and 9). No new data is collected about you. Version 1.10 describes the monthly Free and Premium leaderboards and quest proposals: your monthly score and place, the quests you propose and our decisions about them, reports about published quests, and how long each is kept (sections 4, 5, 6, 8, 9 and 16). Nothing changes for guests, and your quest history still stays on your device. Version 1.9 describes what we keep when we suspend an account or reset a hero name: the end date, and for a suspension the reason shown to you, removed once it ends (sections 4, 5 and 16). Version 1.8 described the backups of our database, which we now make ourselves: an encrypted copy once a week, kept for 30 days (sections 16 and 17). No new data is collected from you. Version 1.7 added one new check: a hero name with contact details, a link or a username for another app is hidden from other players like a name with a blocked word (section 4). It also wrote down things that already happened but weren't described here: emails you send us and how long we keep them (sections 4, 5, 6, 9 and 16), a hero hidden from the leaderboards after an impossible jump in XP (section 4), who can access your data (section 17) and your right to object (section 14). No new data is collected. Version 1.6 added the blocked-word check, and version 1.5 renamed the app from Ascend to Kai-zo-ro. The website address (ascendquests.com) is unchanged for now.

This Privacy Policy explains how Kai-zo-ro ("Kai-zo-ro," "the app," "we," "us") collects, uses, stores and protects information when you use the Kai-zo-ro mobile application and the website at ascendquests.com ("the Site"). It applies to all current versions and platforms of the app.

1. Identity of the controller

The controller of your personal data is Ludvík Šajtar, an independent developer based in the Czech Republic, who develops and operates Kai-zo-ro. Kai-zo-ro is not a registered company and has no company number yet. You can reach the controller using the contact details in Section 23 below.

2. Contact

For any question about this policy, your data, or to exercise any of the rights described below, email ascendhelps@gmail.com. This inbox is monitored by the developer.

3. Scope

This policy covers all versions of the Kai-zo-ro app across platforms (Android and iOS, once published) and the ascendquests.com website, including the account deletion page.

4. What data is collected

What is collected depends entirely on how you use Kai-zo-ro. We state plainly, category by category, what stays on your device and what (if anything) reaches a server.

If you play without an account (guest mode — the default)

• Nothing is sent anywhere. All data — your hero (name, level, XP, streaks, titles, avatar), quest history, daily and weekly analytics, an on-device error log, and any custom avatar or background images you add — is stored only in your device's local storage (localStorage/IndexedDB).
• No account or sign-up is required to use the app.

If you create an optional account

• Your email address and a password (see Section 17 for how the password itself is handled).
• Your account's internal user ID.
• A synced copy of a limited, allow-listed set of your hero's score and progress fields — things like your hero name and title, level, XP, streak, Flame Shields, unlocked titles and badges, your chosen quest categories and category progress, totals such as how many quests you have completed (overall and per category) and the date of your last completion, your chosen avatar and cosmetics, a creator code or referral if you entered one (kept so that a creator can be credited once a creator program exists — none is running yet), whether you joined the Kai-zo-ro Premium waitlist, and account/onboarding status. The full technical list is enforced server-side so it cannot silently grow.
• Your country, but only if you explicitly choose one — it is never inferred from your IP address, GPS, or device locale.
• A friend code we generate for your account, your list of friends, and any friend request, block, or report you make or receive.
• If we suspend your account or reset your hero name, the date the measure ends, and for a suspension the reason we show you in the app. This is removed automatically once the measure ends.
• Your score on the monthly Global leaderboard for each month — the XP your hero earned that month, as your app reports it when it syncs — and whether you were on the Free or the Premium leaderboard that month. When a month ends, we record the final places of the top 25 of the Free leaderboard and the top 50 of the Premium leaderboard, because those players may propose a quest the next month.
• Quest proposals: if you propose a quest, we store its title and description, its category, difficulty, estimated time and language, which version of the rules you accepted, the leaderboard place that gave you the right, and our review decision and its reason, linked to your account. Please don't put personal information about yourself or anyone else in a quest; if you do, we'll remove it before publishing.
• If you report a published quest, the report and the reason you chose.

If you switch on reminders (phone app only)

• Reminders are off until you switch them on in Settings. The app then plans them on your phone with your phone's own notification system. No reminder is sent from our servers, and no push service of Apple or Google receives anything from us.
• To time the daily reminder, the app keeps on your phone the time you first opened it on each of the last 28 days, together with your reminder settings (the times you chose and your quiet hours). This never leaves your phone: it isn't synced, included in an export or used for analytics. Switching reminders off deletes the times.

If you email us

• If you write to us (for support, to report something, or about your data), we receive your email address, what you write and anything you attach, such as your friend code or a screenshot. This is the same whether or not you play or have an account.

Regardless of account status, the following are not uploaded: your quest history (the list of quests you have completed), daily XP log, weekly and monthly reports, focus history, your age range from the age question (Section 19), your reminder settings and the times you open the app, and any custom avatar or background image you add. They stay on your device.

What other users can see

Your email address is never shown to anyone else, including friends. If you add a friend, they can see your hero's name, avatar, level, rank, streak, country (if you set one), and score. Appearing on the Global or Country leaderboard is a separate, opt-in choice that defaults to off — creating an account does not put you on either leaderboard; you turn it on yourself in Settings, and can turn it off again at any time. Friends can always see your hero regardless of this leaderboard setting. While you're on the Global or Country leaderboard, players who see you there can open your hero card and send you a friend request. A friend request carries no message, Kai-zo-ro has no chat, and nothing changes until you accept it; you can also decline it or block the player. Anyone you give your friend code to can send you a friend request; while it is pending, each of you sees the other's hero name and country (if set). If three different players report a hero name, or the name contains a word on our list of blocked words, contact details or a link, other players see "Hero" followed by the last four characters of that hero's friend code instead of the name. This check is automatic: our server runs it each time the name is shown to someone else, and the app runs the same check on your device when you choose a name. If your XP goes up faster in one day than the game allows, you are hidden from the Global and Country leaderboards automatically. Your friends still see you, the app tells you why, and a person can lift it if it was a mistake. On the monthly Global leaderboard, other players can see whether you're on its Free or its Premium list. If a quest you proposed is published, other players see it with your hero name as its author; nobody sees a proposal before we publish it, and nobody else sees who reported a quest.

5. Why each type is collected

• Email and password — to let you sign in and recover access to an optional account. We also use your email to send messages about your account, such as sign-in and deletion codes, and to tell you the reason if we take action on your account under our Community Guidelines.
• Synced score/progress fields — so your level, XP, streak and title are consistent if you use the app on more than one device, and so the leaderboards stay fair: an impossible jump in XP in one day hides a hero from Global and Country until it's checked.
• Country (if chosen) — to place you on the Country leaderboard if you opt into leaderboards, and to show your country next to your hero to friends and on leaderboards.
• Friend code, friend list, blocks and reports — to provide the optional friends and leaderboard features you choose to use, and to let you block or report another user. Reports are reviewed by a person to enforce our Community Guidelines; a report of threats, harassment or shared contact details also sends our mailbox an alert, without any player's name or friend code, so it is read the same day; a name reported as offensive, or for threats or harassment, by three different players is hidden automatically until the reports are resolved, and the app tells you if yours is, and a name containing a blocked word, contact details or a link is hidden automatically until it is changed. If a person decides to suspend an account or reset a name, the end date (and the reason, for a suspension) is kept so the measure works and the app can show it to you.
• Monthly leaderboard scores and places — to run the monthly Free and Premium leaderboards, and to know who may propose a quest the following month.
• Quest proposals and reports about quests — to review proposals, publish the ones we accept, credit you as the author, and handle reports and appeals about them. When you send a proposal, or report a published quest, our server emails our own mailbox a short alert so a person reviews it; the alert about a proposal doesn't contain its text, your hero name or your friend code.
• Emails you send us — to answer you, to handle a request about your data, to act on a report, and to establish or defend legal claims if there is a dispute.
• Local-only analytics (if you opt in) — to help us understand, in aggregate on your own device today, which parts of the app you actually use.
• Local error log — to help diagnose crashes and bugs if you choose to report one to us.
• Reminder times (if you switch reminders on) — to send your daily reminder about 5 minutes before you usually open the app, and to skip it on a day you've already opened it.

6. Legal basis (EU)

• Contract — processing your email, password and synced progress is necessary to provide the optional account and sync feature you requested. Showing your hero to friends and, if you switch it on, on the leaderboard is also part of providing the feature you asked for — you can turn your leaderboard visibility off again at any time in Settings. So are the monthly leaderboards and the month-end places that decide who may propose a quest, and reviewing and publishing a quest you asked us to consider.
• Consent — local analytics collection is opt-in and relies on your explicit consent, which you can withdraw at any time.
• Reminders — keeping the times you open the app on your phone to time your reminders relies on your consent: you give it by switching reminders on and withdraw it by switching them off, which also deletes the times.
• Legitimate interest — limited technical processing (such as the security and abuse-prevention measures described in Section 17) relies on our legitimate interest in keeping the service secure and available. Reviewing reports and enforcing our Community Guidelines, including the automatic checks described in Section 4, relies on our legitimate interest in keeping the community safe for everyone who uses it. Answering emails you send us relies on our legitimate interest in helping you.
• The age question — asking your age when you first open the app, and keeping only your age range on your device, relies on our legitimate interest in keeping Kai-zo-ro for people aged 16 and over, as our Terms and data protection law for children expect (Section 19).
• Legal obligation — handling a request about your data, and keeping a record of how we handled it, is required by data protection law.

7. How data is collected

Directly from you (account sign-up, choosing a country, typing your hero name). Automatically by the app, on your device only: the analytics described above, only once you opt in; the time you first open the app each day, only while reminders are on; and the on-device error log, which records app errors (with email addresses removed) so you can choose to send them to us. We do not currently receive any data automatically from Apple or Google (such as platform age signals) — Kai-zo-ro is not yet listed in either store.

8. Storage and location

• On-device: quest history, analytics, error log, reminder settings and times, and any custom images — and, until you create an account, everything else too — stored locally on your device and not transmitted.
• Photos of community quests: stored with Supabase in the EU (Frankfurt, Germany) and loaded by the app from there when a community quest with a photo is shown. They are photos, not data about you; loading one tells Supabase your IP address, as any request does.
• Server-side (optional account only): your account record, the synced score/progress fields and the other account data listed in Section 4, hosted with Supabase in the EU (Frankfurt, Germany). Requests to the Kai-zo-ro API pass through Render, also hosted in the EU (Frankfurt, Germany) — see Section 9.
• Emails you send us: in our mailbox, a Gmail account (see Section 9).
• Data in transit is encrypted (TLS). Data at rest is encrypted by our database provider. See Section 17 for more on security.

9. Third parties and processors

We use a small number of processors, each acting only on our instructions and bound by their own data processing terms. Consistent with Apple's requirement, we confirm that each of the processors below provides the same or equal protection of your data as required by this policy.

Processor	Purpose	What it receives	Region
Supabase	Database and authentication for optional accounts; storage of the photos of community quests	Email, hashed password, account ID, synced score/progress fields, monthly leaderboard scores and places, friend code, friend list, blocks, reports, quest proposals; when the app loads a community quest's photo, the request for it, including your IP address	EU (Frankfurt, Germany)
Amazon Web Services (Amazon SES)	Sending transactional emails only — sign-up confirmation codes, password-reset codes, account-deletion confirmations, and copies of new quest proposals, quest reports and alerts about reports of threats or harassment sent to our own mailbox	Your email address and the transactional message content. The alerts sent to our own mailbox don't contain any player's name or friend code, or the text of a proposal	EU (Frankfurt, Germany); contracting entity Amazon Web Services EMEA SARL, Luxembourg
Cloudflare	Hosting and DNS for ascendquests.com	Technical request data (such as IP address) needed to deliver and protect the website	Global network; request routing
Render	Hosting the Kai-zo-ro API (api.ascendquests.com)	Requests to the API, including IP address, access token, and the synced account data in transit	EU (Frankfurt, Germany); contracting entity Render Services, Inc., USA

Our mailbox. Emails you send to ascendhelps@gmail.com, our replies, and the copies of quest proposals, quest reports and alerts about reports of threats or harassment our server sends us are kept in a Gmail account. In the EEA, Gmail is provided by Google Ireland Limited, which processes these emails under Google's own terms and privacy policy. It isn't in the table above because we use an ordinary Gmail account, which doesn't come with a separate data processing agreement like the providers above.

10. Analytics

In-app analytics are opt-in and off by default. You're asked during onboarding, and you can change your choice any time in Settings → Privacy & Data. When on, events are recorded only on your device (capped at 500 events) and are not sent anywhere today. Turning analytics off immediately deletes everything already recorded on your device. There is no cross-app or cross-site tracking, and no advertising identifiers are used.

11. Advertising

The current version of Kai-zo-ro shows no ads and uses no advertising network, advertising identifier, or ad-based tracking.

We plan to add optional rewarded ads: a short video you can choose to watch in exchange for a bonus, such as rerolling a quest or doubling the XP from one. They will only ever play when you tap to watch one — there will be no banner, pop-up or interstitial ads — and Kai-zo-ro Premium members won't see ads at all. They will be non-personalized: chosen from the app's context and your approximate (city-level) location, never from your activity in other apps or on websites, and we will not ask to track you across other companies' apps.

Before rewarded ads launch, we will update this policy to name the ad provider, describe what data it processes and why, and explain your choices, including asking for your consent where the law requires it.

12. AI

Kai-zo-ro does not use any third-party AI provider to process your personal data.

13. Account data

Creating an account is entirely optional. Guest mode — the default — requires no account and no email. If you do create an account, it links an email and password to your existing local hero so your score and progress can sync; see Section 4 for exactly what is and is not synced.

14. User rights

Depending on your location, you may have the right to access, correct (rectify), delete (erase), restrict, or receive a copy of (port) your personal data, to object to certain processing, and to withdraw consent at any time. You can exercise any of these rights by emailing ascendhelps@gmail.com. We reply within one month; if a request is complex, we may need up to two more months, and we'll tell you within the first month if so. Please write from the email address on your account, so we can confirm the request is yours. In addition:

• Access / portability: the app can export your hero data as a JSON file at any time, with no request needed (Settings → Privacy & Data → Export Data). For a copy of what we hold on our server, email us.
• Erasure: see Section 15, Data deletion.
• Your right to object: where we rely on our legitimate interest (security, moderation, answering your emails, see Section 6), you can object at any time by emailing us. We'll then stop, unless we have compelling reasons that outweigh your interests (for example, keeping a moderation decision in place while a serious breach of our Community Guidelines is being dealt with).
• Complaints: if you are in the Czech Republic or elsewhere in the EU, you may lodge a complaint with your local supervisory authority. In the Czech Republic this is the Úřad pro ochranu osobních údajů (ÚOOÚ), www.uoou.cz.

15. Data deletion

You can delete your Kai-zo-ro account at any time, in two ways. Deleting it removes your account and the data linked to it from our database straight away. Your sign-in record (email address and password hash) is removed from our authentication provider in the same step. If a technical issue prevents the immediate deletion of an authentication record, limited information may remain temporarily while the issue is being resolved. We do not use the retained record for normal account activity after the account has been deleted, and we take reasonable steps to remove it when required. Section 16 also lists the copies that can remain for a limited time afterwards — in our providers' logs and in our own encrypted backups — and how long.

1. In the app: Settings → Privacy & Data → Delete Account → type DELETE to confirm.
2. On the web, without the app or a working sign-in: ascendquests.com/delete-account/. If you can sign in, the page deletes your account immediately. If you can't, enter the email on your account and follow the confirmation link we send.

Uninstalling the app alone does not delete a server-side account — use one of the methods above. Deleting a guest-mode hero (no account) is done entirely on-device by clearing the app's data, since nothing about it exists anywhere else.

16. Data retention

Data category	Retained while	Deleted
Account profile (including your email address and sign-in record), synced score/progress, friend code, friend list, blocks, reports	Account is active	Within 30 days of account deletion (for the sign-in record, see the technical-issue case in Section 15)
Custom avatar / background images you add (with or without an account; never uploaded)	Stored only on your device	When you remove them or delete the app's local data
Encrypted backups of our database (a copy of the account data above), which we make once a day and keep on the operator's own computer in the Czech Republic	30 days	Automatically, once a backup is 30 days old (the most recent one is kept until a newer one replaces it)
Backups kept by our database provider (Supabase), if our plan includes them (the current plan doesn't)	For the backup retention period of that plan	Automatically, when that period ends
Local analytics events (opt-in)	Capped at 500 most recent events	Immediately, when you turn analytics off
Local error log	Capped at 100 most recent entries	When you clear the app's local data
Reminder settings and the time you first open the app each day (phone app, only while reminders are on)	The last 28 days, on your device only	The times when you switch reminders off; both when you reset your progress or delete your account
API and database logs (such as IP address and account ID, kept by Render and Supabase to run and protect the service)	For the log retention period of our plan with each provider	Automatically, when that period ends
Sign-in and account activity records kept by our authentication provider (Supabase Auth — for example sign-in and account-deletion events, with IP address and account ID)	For the log retention period of our plan with Supabase	Automatically, when that period ends
Website request data (such as IP address, handled by Cloudflare to deliver and protect ascendquests.com)	Under Cloudflare's own retention policy	By Cloudflare, under its policy
Your monthly leaderboard scores (with Free or Premium) and the month-end places of the top 25 / top 50	13 months	Automatically after 13 months, or with your account
A quest proposal waiting for review	Until we decide	With your account, if you delete it first
A rejected quest proposal and our reason	90 days after the decision, so you can contest it	Automatically after 90 days, or with your account
A published quest	While it is published, and afterwards as our record of what we published	Your proposal and its link to you are deleted with your account; the published quest can stay, without your name
Reports about a published quest	12 months	Automatically after 12 months, or with the reporter's account
Emails you send us, and our replies (and the copies of quest proposals, quest reports and report alerts our server sends us)	Until your question, report or request is dealt with	12 months after it is resolved, unless a dispute or an open request needs them for longer
A suspension or a hero-name reset on your account (its end date, and the reason shown to you for a suspension)	While the measure lasts (at most 90 days for a suspension, 30 days for a name reset)	Automatically, within an hour after it ends, or with your account
Our records of moderation decisions (date, friend code, what we decided and why)	While the decision could still be contested	12 months after the decision
Our records of requests about your data (what was asked, when, and how we answered)	To show we handled your request properly	3 years after the request

We do not keep a general "as long as necessary" retention period for account data — the 30-day deletion window above is our concrete commitment for our own database. A deleted account stays in our backups until they are deleted after 30 days. We use a backup only to restore the database after a failure, and if we ever have to restore one, we delete again every account that our records show was deleted after that backup was made. Copies held in our providers' logs and backups are kept only for the retention periods of our plans with those providers, and are then deleted automatically.

17. Security

• Data in transit is protected with TLS encryption.
• Data at rest is encrypted by our database provider. Our own backups of the database are encrypted too (AES-256), with a passphrase only the operator holds.
• The app never reads the database directly: apart from signing in, which talks to our authentication provider, every request goes through our own API, which checks who is asking and shows other players only the limited profile described in Section 4. In the database, row-level security is enabled on every table, and the database provider's automatic public data API is switched off.
• Passwords are hashed by our authentication provider; we never see or store a plaintext password.
• Only the operator (Ludvík Šajtar) can access the database, its backups, the server logs and our mailbox. Nobody else works on Kai-zo-ro today.
• If a data breach affecting your personal data ever occurs, we are committed to notifying affected users and the relevant supervisory authority as required by applicable law.

18. International transfers

Your account data is stored in the EU (Frankfurt, Germany). Some of our providers are companies outside the European Economic Area, or may reach the data from there. Each transfer is covered as follows:

• Supabase (Supabase Pte. Ltd., Singapore): the European Commission's Standard Contractual Clauses, included in its data processing terms.
• Render (Render Services, Inc., USA): certified under the EU–US Data Privacy Framework; its data processing terms also include the Standard Contractual Clauses.
• Cloudflare (Cloudflare, Inc., USA): certified under the EU–US Data Privacy Framework; its data processing terms also include the Standard Contractual Clauses.
• Amazon Web Services (Amazon Web Services EMEA SARL, Luxembourg): emails are sent from the EU (Frankfurt); any transfer outside the EEA is covered by AWS's data processing terms.
• Gmail (Google Ireland Limited): Google may store the emails in our mailbox outside the EEA, under the safeguards described in Google's own privacy policy.

You can request a copy of the relevant safeguards by emailing ascendhelps@gmail.com.

19. Children's privacy

Kai-zo-ro is for people aged 16 and over and is not directed at children. When you first open the app, it asks your age without suggesting an answer. If you are under 16, it doesn't let you continue: it keeps only the time on your device when it may ask again, 24 hours later, and not your answer. Before that, it asks you to confirm the age you typed, so a mistake can be corrected. If you are 16 or over, the app keeps only whether you are 16–17 or 18 and over, on your device; it is not sent to us. We do not knowingly collect personal data from anyone under 16. If we learn that we have, we delete the account and the data linked to it promptly. A parent or guardian who believes their child has provided us with personal data can contact ascendhelps@gmail.com to request its removal.

Some players are under 18, so we treat everyone with the care we would give a younger player: the Global and Country leaderboards are off until you turn them on, other players never see your email address, there is no chat, hero names are filtered, and we never use your data for personalised advertising. Reminders are off until you switch them on; players under 18 choose the time themselves, get at most one a day and none between 21:00 and 07:00, and no reminder ever mentions streaks, points or the leaderboard.

20. California / US state privacy rights

We do not sell or share personal information, as those terms are defined under the CCPA/CPRA and similar state laws (Virginia, Colorado, Connecticut, Utah, and others). We collect only the categories of data described in Section 4, plus the technical request data (such as IP address) described in Sections 9 and 16. If you are a resident of a US state with its own privacy law, you may have the right to know what personal information we hold about you, to request its deletion, to correct inaccurate information, and to not be discriminated against for exercising these rights. You (or an authorized agent acting on your behalf) can exercise these rights by emailing ascendhelps@gmail.com.

21. Cookies

Neither the Kai-zo-ro website nor the app uses cookies or web beacons. The app uses localStorage/IndexedDB on your device, as described throughout this policy.

22. Changes to this policy

If we make a material change to this policy — particularly any change to what we collect — we will update the effective date above and, where the change affects consent you already gave (such as analytics), re-prompt you for that consent in the app. We encourage you to review this page periodically.

If Kai-zo-ro is handed over to another person or to a company that will run it (see Section 17 of the Terms of Service), that person or company becomes the controller of your data. We'll tell you at least 30 days in advance, in the app and, if you have an account, by email, and you can delete your account before the handover.

23. Contact

Kai-zo-ro is developed and operated by Ludvík Šajtar, an independent developer based in the Czech Republic. For any question about this policy or your data, email ascendhelps@gmail.com.