Privacy Policy

The data controller ("veri sorumlusu" under the Turkish Personal Data Protection Law No. 6698, "KVKK") is:

• Company (trade name): Newyares Teknoloji Bilişim Sanayi İç ve Dış Ticaret Anonim Şirketi
• Registered address: Fikirtepe Mahallesi, Rüzgar Sokak No: 44A, A1 D: 197, 34720 Kadıköy / İstanbul, Türkiye
• Email: [email protected]

This company is the developer of LevelUp. "We", "us" and "LevelUp" in this policy mean this company. Our full operator details, including the responsible person, our tax ID and our phone number, are on our Support page.

• Data protection contact: [email protected], for all privacy questions.

This section lists our data by purpose. For each purpose it gives the legal basis we rely on: the KVKK Art. 5 condition and, for users in the EU/EEA, the GDPR Art. 6(1) basis. The sections after this one explain each topic in more detail.

How we collect it

• From you, when you use the app: for example your nickname (the name others see), your answers in onboarding, your quests, weekly reviews, comments and reports.
• Automatically from the app on your phone: identifiers, app version, app language, time zone and usage events.
• From service providers: RevenueCat tells us whether you have LevelUp Pro, based on your App Store or Google Play purchase. Firebase confirms that requests come from your account.
• From other users: reports about you or your content.
• From you by email, when you write to us.

Most collection is electronic and automated, through the app, our servers and the providers listed in Service providers. Some is not automated: emails you send us, reports sent to us by email, and the notes and decisions of our moderators are handled by people.

What you have to give us

• To use the app at all: the app creates your account and sends its account ID and an installation ID with each request. The app cannot work without them.
• A nickname: onboarding asks you for one. It does not need to be your real name. Others see it if you publish or comment.
• Everything else is optional: AI plans, usage analytics, notifications, a profile photo, publishing and commenting. Saying no only means that feature is not used.

1. Your account and the app's core features

Why: to create and run your account, and to give you quests, tasks, XP, levels, character classes, emblems, skills and streaks, the level-ups shown to you, and the comparison of streak goals.

Support ID: a short code such as ABCD-EFGH, made for your account so that you can quote it when you write to us. It is not a secret and gives no access to your account. The app shows it at Profile › Settings › Help & ContactProfile›Settings›Help & Contact and on the “Account suspended” screen.

When you set your streak goal, the app may show how other players' goals compare. That view uses totals from at least 50 players and never shows anyone's own goal.

Legal basis: necessary to perform our contract with you (our Terms of Use): KVKK Art. 5/2(c); GDPR Art. 6(1)(b).

2. AI plans

Why: to write a quest plan or rebuild next week with Claude, only if you allow it. Full details are in AI plans (Anthropic Claude).

What we keep on our servers: your AI consent record (when you allowed it, the consent version, where in the app you allowed it, and when you turned it off), AI plan-writing records, plan suggestions and week proposals, request records, generation logs, usage logs and monthly usage counters.

Legal basis: your explicit consent, given by tapping “Allow”: KVKK Art. 5/1 (açık rıza); GDPR Art. 6(1)(a); and, for any health details you include, KVKK Art. 6/3(a); GDPR Art. 9(2)(a). The logs we keep to run, check and fix the feature: our legitimate interest, KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

3. Free offers and fair use

Why: to give the free onboarding AI plan and the free weekly-rebuild preview only once per account and per device, to apply the monthly fair-use limits on Pro AI features, and to prevent abuse.

Data: the installation ID (see Device identifiers); a record of each free offer claimed, holding a keyed hash of the installation ID, your account ID, a random request code from the app and the time; and a monthly counter per AI feature.

Legal basis: our legitimate interest in preventing abuse of free offers and keeping AI costs fair: KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

4. Community (Explore)

Why: to let you publish quests, like them, comment, reply and join copies of them, and to show you community quests.

Data: published quests and their public details (like count, how many people joined, which quest a copy came from, when the quest was created or published); comments and replies (up to 1,000 characters, with the time and any edit time); who liked a quest or comment and when, and who joined a quest (stored on our servers, never shown, only the counts are public); the quests you marked "Not interested" (up to 100); and your Explore search text (not stored in our database; our own request log replaces it with "[redacted]", but our hosting provider's own logs still record it, see Server logs). Details are in Public community content.

Blocking: the accounts you blocked and when you blocked each one (up to 1,000), stored with your account. See Moderation and safety.

Personal suggestions: the “Trending in Community” section on Home picks community quests using the life areas from onboarding, your own quests, your character class, your skill tiers and your "Not interested" choices, and leaves out quests you joined or reported. It is not used for ads.

Legal basis: contract, KVKK Art. 5/2(c); GDPR Art. 6(1)(b). Personal suggestions: our legitimate interest in showing relevant quests, KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

5. Moderation and safety

Why: to keep the community safe, handle reports, enforce the Community Guidelines, meet legal duties to act on illegal content reported to us, and defend legal claims.

Data: reports (what was reported, who reported it, the reason, optional details up to 500 characters, where the report came from, whether it came from a trusted reporter and whether it was marked urgent, its status, its review deadline and its handling history, including moderator notes up to 500 characters); the moderation state of accounts and content (hidden items, suspension time and the moderator's note up to 500 characters, a locked nickname and the name before a reset); keyed hashes of the installation IDs of the last 10 app installations your account was used from and, if an account is suspended, a ban list of them (see Device identifiers); legal-hold copies of content reported for child safety or for intimate images shared without consent; alerts to the moderation team; and reports sent by email by people without the app. Details are in Moderation and safety.

Reports about AI plans: when you report an AI plan, the report holds a copy of the plan (see Telling us about a bad plan).

Accepting the Community Guidelines: when you accept the Community Guidelines in the app, we record the version you accepted (currently 2026-11-01) and when.

Legal basis: our legitimate interest in a safe community, KVKK Art. 5/2(f); our legal obligations where a law requires action on content, KVKK Art. 5/2(ç); and establishing, exercising or defending legal rights for legal-hold copies, KVKK Art. 5/2(e). GDPR Art. 6(1)(f) and, where EU law requires it, Art. 6(1)(c).

Automatic checks of community text: before a quest title, description or task label, a comment or a nickname is published, it is checked automatically by Anthropic's Claude, whether or not you turned on AI plans. We also store the last nickname that passed the check. See Automatic checks of community text. Legal basis: our legitimate interest in keeping the community safe and meeting the app stores' content rules, KVKK Art. 5/2(f); GDPR Art. 6(1)(f). The check does not rely on your consent. For health details, see Sensitive information.

6. Notifications

Why: to send the reminders and messages you choose, and to show them in the in-app inbox. Details are in Notifications.

Legal basis: reminders and level-up messages, contract, KVKK Art. 5/2(c); GDPR Art. 6(1)(b). "Updates & offers" (marketing): your consent, KVKK Art. 5/1 and Law No. 6563 Art. 6; GDPR Art. 6(1)(a).

7. Home-screen widgets

Why: to show your quests and streak on your home screen or lock screen and let you tick off tasks there. Details are in Home-screen widgets.

Legal basis: contract, KVKK Art. 5/2(c); GDPR Art. 6(1)(b).

8. Purchases and LevelUp Pro

Why: to sell and manage LevelUp Pro, unlock Pro features and restore purchases. Details are in Purchases.

Legal basis: contract, KVKK Art. 5/2(c); GDPR Art. 6(1)(b); and legal obligations where a law requires us to keep records, KVKK Art. 5/2(ç); GDPR Art. 6(1)(c).

9. Usage analytics

Why: to understand how the app is used so we can improve it. Details are in Usage analytics.

Legal basis: our legitimate interest in improving the app, KVKK Art. 5/2(f); GDPR Art. 6(1)(f). Analytics is on by default in every country, including the EU and EEA, and you can turn it off at any time (see Usage analytics).

10. Security, abuse prevention and running the service

Why: to keep the service secure and working, stop abuse, find and fix errors, and complete account deletions.

Data: server request logs and error logs (see Server logs); short-lived data kept only in our servers' memory and never written to the database: request counts per IP address or account, used to limit request rates (kept for up to 60 minutes), and a 60-second copy of your account's basic status (user ID, language, suspension, Support ID, whether it is being deleted) so requests are answered quickly; the record of an account deletion, so that it can finish on our servers; and records of account-deletion steps that failed at a provider (see Deleting your account).

Legal basis: our legitimate interest in security and a working service, KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

11. App updates

Why: to deliver app fixes quickly. Each time the app starts, it asks Expo whether an update is available. Expo receives your IP address, your platform, the app's version and which updates are installed, and a persistent random ID for this installation.

Legal basis: our legitimate interest in keeping the app working and secure, KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

12. Support, rights requests and legal claims

Why: to answer your questions and requests, handle privacy and deletion requests, take reports from people without the app, and defend legal claims.

Data: what you send us: your email address, any name you give, your message and attachments, and details from the app that help us find your account.

Legal basis: support requests: contract, KVKK Art. 5/2(c); GDPR Art. 6(1)(b). Data-protection requests: our legal obligation, KVKK Art. 5/2(ç); GDPR Art. 6(1)(c). Content reports from people without the app, and legal claims: our legitimate interest and establishing, exercising or defending rights, KVKK Art. 5/2(f) and (e); GDPR Art. 6(1)(f).

13. This website

Why: to deliver the pages of this website securely. See This website.

Legal basis: our legitimate interest in running the website, KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

Data kept on your phone

The app also keeps some data on your phone. Some of it is a copy of what is on our servers, and the installation ID is also sent with the app's requests (see Device identifiers):

• the sign-in session of your Firebase account;
• the installation ID, in the iOS Keychain or Android secure storage;
• a random weekly-answer ID and counter;
• local settings, such as your analytics choice, app language and notification choices;
• your onboarding answers while onboarding is in progress, including the answers that never reach our servers;
• a copy of your account and quests so the app opens fast;
• the widget data and widget key (see Home-screen widgets);
• cached images;
• while an account deletion is being completed: a random deletion ticket, with your Firebase user ID and internal user ID until the app learns how the request ended. If the deletion is still running on our servers, only the ticket stays, until our server answers that the deletion has finished (or no longer knows the ticket). With the ticket the app can only ask whether the deletion has finished, without signing in; it gives no access to anything.

Deleting your account clears most of this. See Deleting your account for what stays. Your phone's own backup (iCloud or Google) may include some of this app data, depending on your settings with Apple or Google.

What LevelUp does not collect

• No ads and no advertising SDKs. No advertising ID. No tracking across other companies' apps or websites.
• No crash-reporting or session-recording tools.
• No email address or phone number in the app. We only get your email address if you write to us.
• No contacts, no health data from Apple Health (HealthKit) or Health Connect, and no precise (GPS) location. Google Analytics estimates a rough region from your IP address (see Usage analytics), and the app sends your time zone.
• The app never turns on your camera or microphone. You pick a profile photo through your phone's photo picker, which gives the app only the photo you choose.

Sensitive information

We do not ask for health information. Please do not put health or medical details, or other sensitive details, into quest titles, extra details for the AI, task labels or comments. The app says next to the extra-details box: “Don't include health or medical details.”

If you do include such details, they are handled like the rest of that text: sent to Anthropic for an AI plan if you allowed it, and shown to everyone if you publish them. For an AI plan, the basis we rely on for such details is the explicit consent you give on the AI screen (KVKK Art. 6/3(a); GDPR Art. 9(2)(a)). That screen does not name health details separately, so please keep them out of your goal and notes.

Text you publish is also checked by Anthropic's Claude before it appears (see Automatic checks of community text), so health details in it reach Anthropic for that check too. That is one more reason to keep health details out of anything you publish.

Before anything is sent for an AI plan, the app asks “Plan with AI?” (when you create a quest, under the header “AI & your data”). It says: “LevelUp's AI plans are written by Claude, an AI made by Anthropic. Nothing about your quest is sent for a plan until you allow it.”

So your plans are written by an AI, not by a person. This section repeats what that screen says and adds the details.

Separately, text you publish in the community (quests, comments and your nickname) is checked by Anthropic's Claude before it appears, whether or not you allow AI plans. That check is described in Automatic checks of community text.

Who receives it

The app says: “Anthropic (Claude), the AI service that writes the plan. It stores the data in the US and may process it in other countries.”

That is Anthropic PBC, a US company, through its Claude API. LevelUp currently uses a model from the Claude Haiku family. Anthropic processes this data as our service provider (processor) under its Commercial Terms and Data Processing Addendum. How this data is protected when it leaves Türkiye is explained in International transfers.

What we send

For a new plan (in onboarding or when you create a quest), the app says: “For an AI plan: your goal or quest title, any extra details you wrote, the category, your schedule (weeks and days per week), your starting level and your app language.”

For a weekly rebuild, the app says: “For a weekly rebuild: this quest's title and category, the tasks of the week you finished and of the next one (including the ones you wrote yourself), how many tasks you completed and over how many days, and whether the week felt too easy or too hard.”

And: “Never your name, email or account details.”

In more detail:

• New plan: the title (up to 80 characters; in onboarding your goal becomes the title), your extra details (up to 500 characters, only if you wrote some), the category, the number of weeks (up to 12) and days per week (up to 7). Your starting level and app language go in as short instructions to the AI ("write every task in this language").
• Weekly rebuild: also the week number, the quest's total weeks, days per week and total number of tasks, plus your app language as an instruction. Only the answers “It was too easy” and “It was too hard” start a rebuild; “It was just right” never does.
• Never sent to Anthropic for a plan: your nickname, your account IDs, your installation ID, your device details, your quest description or your other quests. Our requests to Anthropic carry no user identifier.
• But: anything you type into a title, the extra details or a task label is sent exactly as you wrote it. That is why we ask you not to include health or other sensitive details (see Sensitive information).

Why

The app says: “Only to write a plan that fits you, or to rebuild next week around how this week went. The result comes back to LevelUp, and you can edit it.”

AI plans are suggestions. You can edit, remove or add tasks. We do not use the AI to make decisions about you.

When anything is sent

• Nothing for a plan before “Allow”. If you tap “Not now”, nothing is sent to Anthropic for a plan and our servers keep no record of it. If usage analytics is on, the app tells Google Analytics that you chose “Not now” and on which screen (see Usage analytics). The app says: “Not now sends nothing - you can still write the plan yourself.” For a weekly rebuild: “Not now sends nothing and keeps next week as it is.” These lines refer to what goes to Anthropic.
• When you tap “Allow”, we save when you allowed it, the consent version (currently 2026-10-25) and where you allowed it (onboarding, new quest, weekly review or settings). Our server checks this record before every AI plan request. If what we send changes in a meaningful way, we update the consent version and the app asks you again before anything more is sent for a plan.
• The free AI plan is offered only during onboarding. If you choose “Not now” there, you can still write your plan yourself. The app then says: “You chose not to use AI for this plan, so your quest tracks progress without XP. Adding one of these gives you a plan with real rewards, and you can keep both.”
• Turn it off at any time: Profile › Settings › Privacy & Data › AI plans (Anthropic)Profile›Settings›Privacy & Data›AI plans (Anthropic). The app says: “LevelUp stops sending your quest details to Anthropic for AI plans and weekly rebuilds, and a plan that's still being written is stopped. Plans you already have stay in your quests.” If tasks of that unfinished plan were already showing, they are removed from the screen.
• What turning it off does not undo: what was already sent to Anthropic. If you turn AI plans back on, the app shows the consent screen again first.

What Anthropic does with it

• No training. Anthropic does not train its models on this data (Anthropic Commercial Terms, Section B).
• Anthropic's retention. Anthropic deletes API inputs and outputs automatically within 30 days. If content is flagged under its Usage Policy, Anthropic may keep it for up to 2 years, and its trust and safety classification scores for up to 7 years (How long Anthropic stores data, page updated 2026-07-01).
• Where. Anthropic stores this data in the United States. It may process it in the United States, Europe, Asia or Australia, and safety review and support may happen wherever Anthropic operates (Where Anthropic's servers are).
• Safeguards. Anthropic's Data Processing Addendum includes the EU Standard Contractual Clauses. Anthropic lists its own sub-processors at anthropic.com/subprocessors. See International transfers.
• Rules of use. AI plans must follow Anthropic's Usage Policy.

What LevelUp keeps

The app says: “Anthropic doesn't use this data to train its models and keeps it for up to 30 days (longer only if it's flagged for breaking its usage policy). LevelUp keeps its logs of AI requests for up to 90 days; your plan itself stays in your quest.”

The 90 days covers our AI request and usage logs; the other records below have their own periods.

In detail:

All of these are deleted when you delete your account. Anthropic's own copy follows Anthropic's retention above.

“Notify me when it's ready” for a new plan: if you ask to be notified when a plan is ready, we send a push notification that includes your quest title cut to 40 characters (see Notifications).

AI plans can be wrong

• AI plans are written automatically. They may be inaccurate, incomplete or out of date. Check a plan before you rely on it.

• Where the app shows its AI notice, it reads: “AI-generated, may contain mistakes; check before relying on it.” On fitness, sports and cooking plans, and on plans without a category, it adds: “Not medical advice: check with a doctor first.”

The app shows this notice under every plan the AI wrote: when you review a new plan while creating a quest, in the onboarding preview, and on the weekly-rebuild screens. Plans you write yourself do not carry it.

Safety rules and young users

Safety rules in every plan. The instructions we give the AI ask for safe plans: no extreme dieting or rapid weight loss, no long fasts, no purging or diet pills, no dangerous stunts or training through pain, no illegal, sexual or self-harm content, no diagnosis or medication advice, and extra care when you mention a condition. If there is no safe version of a goal, the AI declines.

Refusals. Requests that mention self-harm or eating-disorder wording, or very long fasts, are refused before anything is sent to the AI. The AI can also refuse. The app then says: “The AI won't write a plan for this goal. Try a safe, healthy version of it, or write the tasks yourself.” For sensitive topics it adds: “If you're struggling with eating or with thoughts of hurting yourself, please talk to a doctor or a local support line. You don't have to go through it alone.” Helplines by country are listed in our Community Guidelines.

Using AI plans safely:

• Read every plan before you start, and change what does not fit you.
• Keep health and medical details out of what you type.
• Talk to a doctor before a new exercise or diet programme.
• If a plan looks unsafe, do not follow it, and tell us.

Young users. LevelUp is for ages 13 and over (see Children and young users). Users under 18 can use AI plans. They fill in a form; they do not chat with the AI.

Telling us about a bad plan:

• In the app, tap “Report this plan” under an AI plan you think is harmful or wrong. It sits under every plan the AI wrote: when you review a new plan, in the onboarding preview and on the weekly-rebuild screens. Choose a reason (Dangerous advice, Self-harm or suicide, Sexual content, Violence or illegal activity, Hate speech, or Something else) and, if you like, add details (up to 500 characters). The report goes to our moderators.
• What the report stores: a copy of the plan, so that a moderator can still see it after the plan itself expires. The copy holds where the plan came from (new quest, onboarding or weekly rebuild), its title, category and task texts; for a new plan also the app language and the extra details you gave the AI; for a rebuilt week, the quest and the week number. The report also holds your reason, your details and your account as the reporter. It is kept with no time limit set, and the copy and your details are removed when you delete your account (see How long we keep data).

Our statement on safety and young users, with the safeguards that are live today and how to report child-safety concerns, is in Children and young users.

Automatic checks of community text

Before text you write appears in the community, it is sent to Anthropic (Claude) for an automatic check against our Community Guidelines. The app says so in the Community Guidelines sheet and the share sheet: “Nicknames, quests and comments are checked automatically by Anthropic's Claude before they're published.”

When it runs:

• when you share a quest: its title, description and every task label;
• when you write or edit a comment or a reply;
• on your nickname the first time it becomes public (with your first shared quest or comment), and on every later rename once you have accepted the Community Guidelines. Never during onboarding;
• on the new tasks of a shared quest's rebuilt week, when you apply it.

What is sent: only the text, what kind of text it is (nickname, quest title, description, task or comment), where it is about to appear and your app language. No account ID, installation ID or other user identifier is sent. LevelUp uses a model from the Claude Haiku family for this check.

What it looks for: sexual content, hate, harassment (including strong profanity), self-harm and eating-disorder behaviour, violence or illegal activity, spam (including pretending to be LevelUp or its team), and someone's personal information, such as a phone number or address.

What happens next:

• Text that passes is published.
• Text that does not pass is not published, and the app says so, for example: “This doesn't meet our Community Guidelines. Change it and try again.” A quest you tried to share stays as it was, a new comment is not posted, and an edited comment keeps its old text. The message does not say which rule the text broke; you can ask us by email.
• A rebuilt week whose tasks do not pass is not applied: “The new week's tasks don't meet our Community Guidelines, so your current week stays as it is.”
• If your nickname fails its first check, it is removed and the app asks you to choose a new one: “Your nickname doesn't meet our Community Guidelines, so we reset it. You can choose a new one in your profile, then try again.” Others then see the app's default name (in English, “Adventurer”). A new name that fails is refused and your old name stays: “That nickname doesn't meet our Community Guidelines. Try another one.”
• If the check cannot be reached, nothing is published and the app asks you to try again: “We couldn't check this just now. Try again in a moment.”
• If the check fails for another reason, for example a configuration error on our side, a request the check service refuses, or an answer from it that cannot be read, the text is published without being checked, and we log the failure so that we can fix it. A nickname let through this way counts as checked and is not checked again unless you change it.

Separate from AI plans. This is a separate purpose from AI plans. It is part of keeping the community safe, so it runs whether or not you turned on AI plans, and it is not covered by the AI plan consent. With AI plans off, the app says under Privacy & Data: “Your nickname, shared quests and comments are still checked by Anthropic's Claude, as the Community Guidelines say.” There is no setting to turn the check off; it applies only to what you publish. Before your first post, comment or rename, the app asks you to accept the Community Guidelines, which describe the check (see Moderation and safety).

What LevelUp keeps: no copy of the text and no record of the check in our database. When a text is rejected, our server log gets a line with where it was (for example "comment"), the field and the categories found; when the check fails, a line with the reason and Anthropic's request ID. Neither line holds the text or a user ID. Separately, your account stores the last nickname that passed the check (it is never shown), so that an unchanged name is not checked again. It is kept until a new name passes, until a name fails its first check (then it is cleared), or until you delete your account; it also stays when a moderator removes your name. Anthropic's no-training rule, retention and locations above apply in the same way.

Legal basis: our legitimate interest in keeping the community safe, as listed under Moderation and safety; the check does not rely on your consent.

LevelUp uses Google Analytics for Firebase to understand how the app is used. Under Privacy & Data the app says: “Sends usage events, like which screens you open, to Google Analytics so we can make LevelUp better. Never the text you write. Turn it off and nothing is sent.”

What the app sends, while analytics is on:

• screens you open and how you move through onboarding (steps, time spent, whether you left and came back);
• the options you tap in onboarding: how you heard of LevelUp, what gets in your way, your rhythm, your starting level, the life areas you picked, days and weeks, and whether you added details;
• only the length of your nickname, goal and extra details, never the text;
• your character class, your streak goal, your notification choices and reminder hour;
• quest events with LevelUp's internal quest ID, the category, the number of weeks and days, task counts and XP;
• whether you allowed or declined AI plans and on which screen, and when you reach a monthly AI limit;
• paywall events: shown, closed, purchase started, cancelled, completed, failed or restored, and where you opened it;
• share-card events: what you shared and which template.

The app does not send the text you write: no quest titles, task labels, comments or names.

What Google Analytics collects by itself: an app-instance ID, your device model, operating system and version, app version, language, a rough location (country, region or city) estimated from your IP address, first open, sessions and engagement. It may also record in-app purchase events automatically.

What we do not do:

• We do not give Google Analytics a user ID or user properties. The internal quest ID in some events could let us match those events to a quest in our database.
• Advertising ID collection is turned off: the iOS app is built without advertising-ID support, and collection is off on Android. Ad storage and ad personalisation signals are off.
• No tracking across other companies' apps or websites, and no ads. That is why the app never shows Apple's tracking prompt.

Your choice: analytics is on by default. Turn it off at Profile › Settings › Privacy & Data › Share usage analyticsProfile›Settings›Privacy & Data›Share usage analytics. When it is off, the app sends no events. The choice is saved on your phone, not in your account, so it stays after you delete your account.

The notice at first launch. The introduction screens show, under their button: “By continuing, you agree to our Terms of Use and Privacy Policy. We collect usage analytics to improve LevelUp; you can turn them off anytime in Settings.” If analytics is on, the app sends events from the first introduction screen on, while this line is on screen.

How long: Google Analytics keeps event-level and user-level data for 14 months. Totals in Google's standard reports, which no longer show individual events, are not affected by this setting. Deleting your account resets the app-instance ID, so new events are not linked to old ones. Events already collected stay until that period ends.

Installation ID. The app reads the iOS identifier for vendor (IDFV) or the Android ID, or a generated ID if neither is available, and stores it in the iOS Keychain or Android secure storage. It is sent with requests as an installation ID: with every request the app makes while signed in, only to LevelUp's servers.

We use it for three things:

• (a) Free offers once per device. To make sure the free onboarding AI plan and the free weekly-rebuild preview are given once per device, a keyed hash of it is stored. This hash is kept after account deletion, with no time limit set; the delete screen says so. Because we hold the key, it is pseudonymous personal data, even though it is not linked to your account.
• (b) Storing the raw value. The raw value is held with a free onboarding AI plan only while that plan is being written, and erased as soon as it is finished or stopped (a plan not finished after 15 minutes is stopped). It is also held for up to 60 days with home-screen widget keys (see Home-screen widgets).
• (c) Making suspensions stick. Each time the app connects your account to our server, we store a keyed hash of the installation ID with your account, for the last 10 installations it was used from. If your account is suspended, these hashes go on a ban list, and any account that later connects from one of those installations is suspended automatically, including a new account made after deleting the old one; the installations that account was used from then go on the list too (see Moderation and safety). The ban-list entry is kept after account deletion, without the link to the account. It is removed only when a moderator lifts the suspension of an account that was used on that installation; a deleted account's own suspension can no longer be lifted, so the entry may stay indefinitely. The delete screen of a suspended account says so.

The installation ID is not written to our request logs. It stays on your phone after you delete your account.

Legal basis: our legitimate interest in preventing abuse of free offers, in securing widget access and in keeping suspended users from coming back: KVKK Art. 5/2(f); GDPR Art. 6(1)(f).

Other identifiers:

• Account IDs: the Firebase user ID of your anonymous account and LevelUp's internal user ID. "Anonymous" here only means there is no sign-in. These IDs are pseudonymous personal data: they are not your name, but they link everything in your account.
• Weekly-answer ID: a random ID made by the app, sent with each weekly review answer so our server can put repeated or late answers from the same phone in the right order. It is stored with the quest until the quest or account is deleted. If the quest is under a legal hold (see Moderation and safety), the copy kept for that hold includes it. The ID on your phone stays after you delete your account.
• IDs made by the providers' SDKs: a Firebase installation ID and push token (Google), the Google Analytics app-instance ID, RevenueCat's own device data (RevenueCat uses your Firebase user ID as its customer ID), and Expo's random ID for this installation.

None of these identifiers are used for advertising or for tracking you across other companies' apps or websites.

Explore is public inside the app. Everyone using the app can see:

• with each quest you publish and each comment you write: your nickname, initials, level, character class and Pro badge (if you have LevelUp Pro), and an internal ID the app uses if someone reports the account;
• published quests: title, description, category, schedule, the task labels with their XP, and when the quest was created or published. Your progress (which tasks you ticked off) is not shown;
• comments and replies, with their date and whether they were edited;
• like counts and how many people joined a quest. Who liked or joined is not shown.

Your nickname becomes public when you first publish a quest or write a comment. The name you choose in onboarding is sent to our server even if you never publish. It does not need to be your real name.

Not public: your profile photo, your onboarding answers, your private quests, your progress, your weekly reviews and your Explore searches.

When content goes away:

• Unpublishing a quest removes it from Explore.
• Deleting a quest also deletes all comments on it.
• Deleting a comment removes it; other people's replies to it stay.
• Copies others joined: when someone joins your published quest, they get their own copy of its title, category and tasks (not the description, and not your name). Those copies stay after you unpublish or delete the quest, or delete your account, without your name.
• If an account is suspended, its quests and comments are hidden.

Reports.

• How to report: anyone can report a quest, a comment or an account in the app, from the “…” menu, by choosing a reason and adding optional details (up to 500 characters). People without the app can report by email (see Report content).
• What we store: the report, the reason, the details, who reported it (no one, for an email report), where it came from, whether the reporter counted as trusted and whether the report is urgent, its status, a 24-hour review deadline and the handling history, including moderator notes.
• One report per item: each person's report about the same item counts once.
• You stop seeing it: when you report a quest or a comment, you stop seeing it straight away, whatever the outcome. Reporting an account does not hide that account's quests or comments from you.

Automatic steps:

• Trusted reporters only. Automatic steps follow only reports from a trusted reporter: an account that is at least 24 hours old and has finished onboarding. Reports that a moderator enters from email notices also count as trusted. We store with each report whether it was trusted.
• Trusted reports for child safety, intimate images shared without consent, or sexual content hide the item at once while we review it.
• Any item is hidden once 3 different trusted reporters have reported it.
• A reported nickname is removed and locked while we review it, on the same rules. Others then see the app's default name (in English, “Adventurer”). We keep the name from before the reset until a moderator decides.
• A report from a newer account hides nothing by itself and does not count toward the 3. If its reason is child safety, intimate images or sexual content, it is marked urgent and goes to the front of our queue.
• Child-safety and intimate-image reports always alert our team at once, whoever sent them.
• Content from LevelUp's own official account is never hidden automatically; a moderator is alerted instead. Once one person has made 5 trusted reports for child safety, intimate images or sexual content within 24 hours, their further reports with those reasons no longer hide anything or remove a name at once; they are marked urgent and still count toward the 3.

A person on our moderation team reviews reports. We aim to review every report within 24 hours. A moderator may restore the item, remove it, remove a nickname, or suspend the account. After a moderator removes a name, others see the default name and you can choose a new one. If a moderator dismisses a name report, the old name comes back.

Suspensions. A suspended account cannot use LevelUp, and its quests and comments are hidden. You can still delete the account. A suspension does not by itself delete your push tokens or notification settings, so reminders and, if you turned them on, “Updates & offers” messages may still be sent. To stop them, turn off notifications for LevelUp in your phone's settings. We store the time and a note: the moderator's, or for an automatic suspension a note naming the ban-list entry that triggered it. We do not currently show the reason in the app or send an automatic notice of the outcome to the person who reported or was reported; you can ask us by email.

The “Account suspended” screen shows your Support ID, and the email that its “Contact support” button starts already includes it.

Suspension carries over to the same phone. When an account is suspended, the hashed installation IDs it was used from go on a ban list (see Device identifiers). An account that later connects from one of those installations is suspended automatically, without a person reviewing it first, including a new account made after deleting the suspended one. The installations that account was used from then go on the ban list too, so the suspension also reaches its other phones. This applies to anyone who uses LevelUp on such a phone, for example a phone shared with someone else, and the app shows them the same “Account suspended” screen. The ban-list entry stays after the account is deleted, without the link to the account. Lifting the suspension of an account removes the entries for the installations it was used from, including entries left by a deleted account.

Alerts to the moderation team. New reports send an alert to our moderation panel, a web app we run for our moderators, hosted by Vercel Inc. (location: US). The alert holds only the report ID, the reason, what kind of item it is and its ID, the review deadline and any automatic action. For a report about an account, that ID is the account's internal user ID; for a report about an AI plan, it is the internal ID of the plan or week proposal. Alerts never include the reported text or the reporter's details. The alert messages are kept in the panel (see How long we keep data).

Legal-hold copies (child safety and intimate images). When something is reported for child safety or for intimate images shared without consent, we keep a copy of it and of who posted it, so it can be given to the authorities if needed:

• for a quest: the whole quest, including its tasks, weekly answers and owner;
• for a comment: the whole comment and its author;
• for an account: the Firebase user ID, sign-in type, nickname, initials, any previous name, profile photo link and creation date.

The copy is kept while the report is open and for 1 year after we act on it. It is deleted if the report is dismissed. Only the moderation tools can read it. It is also kept if the content or account is deleted while the report is open.

After you delete your account: reports you sent are kept without your identity and without the details you wrote. Reports about you or your content are kept as a moderation record without your identity, the details text or your account ID, and open ones are closed. Child-safety and intimate-image reports that were not dismissed keep their details and target; the report itself has no end date, even after the evidence copy expires. See Deleting your account.

Authorities. We may report illegal content, and give a legal-hold copy, to the competent authorities when the law requires it or to protect someone from serious harm.

Blocking. You can block another user from the “…” menu on their quest or comment (“Block [name]”). Neither of you then sees the other's quests or comments, and neither of you can comment on the other's; the other person is not told. We store your list of blocked accounts with your account, with the time of each block (up to 1,000 accounts). Unblock someone at Profile › Settings › Blocked UsersProfile›Settings›Blocked Users. An entry is deleted when you unblock the account, when you delete your account, or when the blocked account is deleted. Reports still work across a block.

Community Guidelines acceptance. Before your first shared quest, comment or reply, and before you change your nickname after onboarding, the app asks you to accept the Community Guidelines. In the share sheet you tick “I agree to the Community Guidelines and the Terms of Use.”; before a comment, a reply or a rename, a Community Guidelines sheet asks you to tap “I agree”. We record the version you accepted (currently 2026-11-01) and when. If a new version needs a new acceptance, the app asks again before your next post.

Automatic checks before publishing. Quest titles, descriptions and task labels, comments and nicknames are checked automatically by Anthropic's Claude before they are published. Text that fails is not published, and a nickname that fails its first check is removed (see Automatic checks of community text).

What we store when you allow notifications:

• for each phone: the Firebase Cloud Messaging (FCM) push token, platform, notification permission, time zone, app language, app version and build number, when the phone was last seen, and when the token stopped working, if it did;
• your notification settings: “Quest pace reminders” and “Streak at risk” (on by default), “Updates & offers” (off by default), your reminder hour (7 pm by default) and your time zone;
• an in-app inbox of level-ups, reminders and product news;
• a delivery record for each send decision, including skipped ones: the text, the in-app link, the result per phone and, if skipped, why;

The Firebase SDK may create a push token on your phone before you allow notifications. LevelUp's server receives it only after you allow them.

Reminders are part of the app. To decide when to remind you, our server uses your time zone, your reminder hour and your task activity. We send at most two reminders a day, two hours apart. A reminder may name your quest (cut to 28 characters) and your next task (cut to 48 characters). A plan-ready notification includes your quest title cut to 40 characters. Level-up messages appear only in the in-app inbox.

“Updates & offers” is marketing and is off unless you turn it on. Next to the switch the app says: “Turning this on is your consent to marketing messages. You can turn it off any time.” When you turn it on, we record when, the consent text version and where you turned it on. When you turn it off, we stop sending, and we keep the record of your earlier consent as proof.

Who carries the messages. Push text passes through Google (Firebase Cloud Messaging) and, on iPhone, Apple (Apple Push Notification service). Depending on your phone settings, notifications can show on your lock screen.

Your choices: Profile › Settings › NotificationsProfile›Settings›Notifications, and your phone's notification settings for LevelUp.

LevelUp's widgets for iOS and Android show your quests and streak on your home screen or lock screen and let you tick off tasks.

• On your phone: a copy of your active quests (titles, task labels, XP, whether done and when), your streak and week, your character's equipment, your internal user ID and app language. On iPhone it is kept in a storage area shared only with LevelUp's widget; on Android, in the widget's storage. Quest titles and task labels can show on your lock screen.
• Widget key: the app gets a key that lets the widget read your active quests and activity and tick off tasks, and nothing else. Our server stores only a hash of the key, the raw installation ID, and when it was last used. A key expires 60 days after it is issued. While you use the app, it gets a new key every 7 days, which replaces the old one.
• Widget keys are deleted when the app signs out of your account, when you delete your account, or if the account is suspended. Deleting your account also clears the widget data on your phone.
• To stop it, remove the widget from your home screen or lock screen.

• Payments: Apple (App Store) or Google (Google Play) process payments for LevelUp Pro. LevelUp never sees your card or payment details. Apple and Google handle your purchase as independent controllers under their own privacy policies.
• RevenueCat manages subscriptions for us. It receives your Firebase user ID as its customer ID, plus your store transactions and purchase history, device data from its SDK and your IP address.
• On our servers: whether you have Pro and until when, and the time of the last store event. For each RevenueCat event we keep only its ID, type and status, for 30 days. We do not store purchase details.
• Pro badge: if you have LevelUp Pro, a Pro badge shows next to your name on what you publish (see Public community content).
• Restore: the restore option on the paywall, or in subscription management at Profile › Settings › LevelUp ProProfile›Settings›LevelUp Pro, links an existing purchase from your store account to your current LevelUp account.
• Account deletion: we delete your RevenueCat customer record when you delete your account. That does not cancel your subscription; see Deleting your account.

We do not sell your personal data, and we do not share it for advertising.

Most of the companies below process data for us under contract, as processors. Apple and Google as app stores act on their own account.

Anthropic PBC (Claude API)

• What for: AI plans and weekly rebuilds, only after you allow it.
• Also: automatic checks of community text before publishing, a separate purpose that does not depend on the AI plan setting. For these checks only the text, its kind, where it will appear and the app language are sent, with no user identifier (see Automatic checks of community text).
• Data: see What we send.
• Where: stored in the US; may be processed in the US, Europe, Asia or Australia.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in Anthropic's DPA.
• Note: no training on this data; deleted within 30 days (up to 2 years if flagged; classifier scores up to 7 years).

Google: Firebase Authentication

• What for: your anonymous account and checking that requests come from it.
• Data: your Firebase user ID, sign-in tokens, device and app details, IP address.
• Where: United States and other countries where Google operates.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in Google's data processing terms.

Google: Firebase Analytics (Google Analytics)

• What for: usage analytics, which you can turn off.
• Data: usage events, app-instance ID, device and OS details, rough region from your IP address.
• Where: United States and other countries where Google operates.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in Google's data processing terms.
• Note: advertising ID off.

Google: Firebase Cloud Messaging, and Apple: Apple Push Notification service

• What for: delivering push notifications.
• Data: push token and the notification text.
• Where: United States and other countries where Google and Apple operate.
• Transfer safeguard: for Google, KVKK standard contract (controller to processor) and EU Standard Contractual Clauses in Google's data processing terms. Apple delivers notifications to iPhones as part of iOS, under its developer terms with us.

Google: Firebase Storage

• What for: storing your profile photo.
• Data: the image file, in a folder named after your Firebase user ID.
• Where: Google Cloud us-east1 (South Carolina, US).
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in Google's data processing terms.
• Note: shown only to you in the app.

RevenueCat, Inc.

• What for: managing LevelUp Pro subscriptions.
• Data: your Firebase user ID, store transactions and purchase history, device data, IP address.
• Where: United States.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.
• Note: your customer record is deleted when you delete your account.

Apple and Google (App Store, Google Play)

• What for: app distribution and payments.
• Data: purchase data.
• Where: United States and other countries.
• Transfer: you buy directly from Apple or Google under their terms; we send them no data for the purchase.
• Note: independent controllers for your purchase.

MongoDB, Inc. (MongoDB Atlas)

• What for: our database, and search in Explore.
• Data: all the server data described in this policy.
• Where: AWS eu-central-1 (Frankfurt, DE).
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.

Salesforce, Inc. (Heroku)

• What for: hosting our servers (API) and their logs.
• Data: all traffic between the app and our servers, and the request logs.
• Where: EU (AWS eu-west-1, Dublin, IE).
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.

Vercel Inc. (our moderation panel)

• What for: hosting our moderation panel, a web app we run that receives moderation alerts from our server.
• Data: report ID, reason, the kind and ID of the reported item (for a report about an account, its internal user ID; for a report about an AI plan, the internal ID of the plan or week proposal), review deadline. Never the content.
• Where: US.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.

Expo (650 Industries, Inc.)

• What for: checking for app updates.
• Data: IP address, platform, app version and installed updates, a persistent random ID for this installation.
• Where: United States.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.

Images in the app. The category photos (from Unsplash) and the app's other images and icons are built into the app. A photo for a category we add later is fetched by our server from Unsplash and served to the app from our own servers. Your phone does not contact Unsplash, and we send Unsplash no user data, so it is not a recipient of your data.

Vercel Inc. (this website)

• What for: hosting this website.
• Data: visitors' IP address and browser details.
• Where: US.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.
• Note: see This website.

Google Workspace (our support inbox)

• What for: receiving and answering your email.
• Data: your email address, your message and attachments.
• Where: US.
• Transfer safeguard: KVKK standard contract (controller to processor); EU Standard Contractual Clauses in the provider's data processing terms.

Same protection. We confirm that every third party listed here that receives user data from LevelUp, including our analytics provider, the SDKs in the app, our AI provider (for every purpose listed above) and our hosting and database providers, is required by its agreement with us or its terms to give that data the same or equal protection as this policy describes.

Taking back consent and deleting your data. You can turn off AI plans, usage analytics and marketing notifications at any time; see Your choices. You can delete your account in the app or ask us to delete it; see Deleting your account.

Other recipients:

• Other users see what you publish (see Public community content).
• Authorities and courts: the Turkish public prosecutor, police and courts, the competent authority of another country for a case that involves it and, for users in the EU, the authorities of the EU country concerned or Europol, when the law requires it, or to protect someone from serious harm.
• Our legal and professional advisers, where needed to establish, exercise or defend legal claims.
• A buyer or successor, if our business or LevelUp is sold or merged, under this policy.

We are based in Türkiye. Our service providers are outside Türkiye, mostly in the United States, so using LevelUp means your data is transferred abroad.

• Under KVKK (Art. 9, as amended by Law No. 7499): for each service provider abroad listed above with a “Transfer safeguard” line, we rely on the standard contract announced by the KVKK Board (controller to processor). We do not rely on your consent for these transfers. Apple's push service is different: Apple delivers notifications to iPhones under its developer terms with us.
• For users in the EU/EEA: when you use LevelUp from the EU or EEA, you give your data directly to us in Türkiye. For data that goes from the EU/EEA to a country without an adequacy decision, our providers' data processing terms include the EU Standard Contractual Clauses; Anthropic's Data Processing Addendum includes them.
• You can ask us for a copy of the safeguards we use; write to [email protected].

Deletion runs right away; expired data is removed automatically by the database shortly after its time is up. The first table below lists data that goes when you delete your account. The second lists what stays after that, and for how long.

Data that goes when you delete your account

AI plan you reported: the copy of the plan in your report, and the details you wrote, are kept with the report with no time limit set, until you delete your account.

Support ID: until you delete your account.

Blocked accounts: until you unblock them or delete your account; an entry also goes when the blocked account is deleted.

Community Guidelines acceptance: until you delete your account.

Last nickname that passed the automatic check: until a new name passes, a name fails its first check, or you delete your account.

Data that stays after you delete your account

Database backups: we do not keep backups of our database.

Automatic checks of community text: Anthropic's copy follows Anthropic's retention above. LevelUp keeps no copy of the text and no record of the check in its database; the only trace is a server log line without the text or a user ID, in our hosting provider's live log buffer (see Server logs).

In the app: Profile › Settings › Privacy & Data › Delete accountProfile›Settings›Privacy & Data›Delete account.

Without the app: see Request account deletion.

How it runs. Your account is closed at once: it can no longer be used, its sign-in is turned off and its widget keys stop working. From then on nothing more about the account is sent to Anthropic. Our servers then delete its data. If that cannot finish at once, it finishes on its own on our servers, usually within minutes; while it keeps failing, our servers retry it, at most an hour apart, until it is done. The app then tells you that the deletion is in progress (“Deletion in progress”) and tells you again once it has finished (“Account deleted”). If deleting your files in Firebase Storage, your RevenueCat record or your Firebase account fails at the provider, that step is retried once about 20 minutes later and otherwise finished by hand (see What we keep, and why).

What gets deleted

As listed in the app:

• Your profile, level, character and skills
• Your quests and progress, including the ones you shared with the community
• Your comments and likes, and the comments on your quests
• Your AI plans, reminders and notifications
• Your profile photo

This also removes you from the like and join lists on other people's quests and from other users' block lists, and deletes your widget keys, your Firebase account, all your files in Firebase Storage and your RevenueCat customer record. On your phone the app clears your local data and widget data and resets your Google Analytics app-instance ID.

What we keep, and why

The app lists:

• “A marker for this device, so a new account can’t claim the free AI plan or the free weekly rebuild preview again. It isn’t linked to you.”
• “Reports you sent, without your name, so moderators can still act on them.”
• “Reports others sent about you or your posts, without your name or account, as a record for moderators.”
• “Copies of your shared quests that others already joined. They’re theirs now and don’t show your name.”
• “If something you posted was reported for child safety or for intimate images shared without consent, a copy with your account ID is kept while the report is open and for up to a year after it’s resolved.”
• Only if the account is suspended: “A marker for this device, because this account is suspended: a new account made on it is suspended too. It isn’t linked to you.”

Two corrections: the device markers are not linked to your account or your name, but they are tied to the phone, so they are pseudonymous data rather than “not linked to you”. And reports you sent lose the details you wrote, as explained below. The legal-hold copy also applies when your account itself was reported.

What these mean in detail, and how long each is kept:

• Device marker (free offers): a keyed hash of this phone's installation ID. It is not linked to your account or your name, but it is linked to the phone, so it is pseudonymous data. Kept indefinitely.
• Ban marker, only if your account was suspended: the hashed installation IDs your account was used from stay on the ban list, without the link to your account, so a new account made on those installations is suspended too. Kept until a moderator lifts the suspension of an account used on one of those installations; your deleted account's own suspension can no longer be lifted, so possibly indefinitely.
• Reports you sent: kept without your identity and without the details you wrote, and without the copy of an AI plan you reported. Child-safety and intimate-image reports that were not dismissed keep their details, also with no end date. No time limit is set.
• Reports about you: kept as a moderation record without your identity, the details text or your account ID; a report about your account itself points to a new random ID instead of yours. Open reports are closed. Child-safety and intimate-image reports that were not dismissed keep their details and target; the report itself has no end date, even after the evidence copy expires. No time limit is set.
• Copies others joined: they belong to the people who joined and stay until they delete them.
• Legal-hold copy: a copy of the reported item (for an account: your nickname, any previous name and profile-photo link) and of who posted it, kept while the report is open and for 1 year after we act on it; if no moderator has decided yet, it stays until they do. If the report is dismissed, the copy is deleted. A copy of a quest includes its tasks and weekly review answers.

Also kept for a while:

• Usage analytics already collected stays in Google Analytics until its retention period ends (14 months).
• Anthropic's copy of AI requests: up to 30 days (up to 2 years if flagged; Anthropic's trust and safety classifier scores up to 7 years).
• Moderation alerts in our moderation panel about reports concerning you or your content. They hold only IDs (for a report about your account, its former internal ID) and the reason, and stay in the panel (see How long we keep data).
• Server logs: only briefly, in our hosting provider's live log buffer (see How long we keep data). We keep no database backups.
• The deletion record: your internal user ID and Firebase user ID until a second clean-up pass about 20 minutes after your data is removed (longer if the removal keeps failing); after that, for 30 days, only hashes of the app's deletion tickets, where the deletion came from (app or support), its times, the number of attempts and the outcome, so the app can learn how it ended.
• If a step at a provider fails (Firebase Storage, RevenueCat or the Firebase account), we keep your Firebase user ID, the failed step and the error until a retry about 20 minutes later succeeds, or until we finish that step by hand.
• Apple and Google keep their own records of your purchases.
• On your phone: the app keeps your app language, your analytics choice, the installation ID and the weekly-answer ID and counter, and, until our server confirms that the deletion has finished, the deletion ticket (see Data kept on your phone). Deleting the app removes most of the data it stores on your phone. On iPhone, the installation ID may stay in the Keychain even after the app is deleted, so a reinstall on the same phone uses it again.
• Support email you sent us (see How long we keep data).

Your subscription

Cancel in your store account:

• iPhone or iPad: Settings › [your name] › Subscriptions.
• Android: open the Google Play app, tap your profile icon, then Payments & subscriptions › Subscriptions.

The delete screen also has a “Manage subscription” button.

• AI plans: Profile › Settings › Privacy & Data › AI plans (Anthropic)Profile›Settings›Privacy & Data›AI plans (Anthropic). The app says: “Off. Nothing is sent to Anthropic for AI plans or weekly rebuilds; they ask you first. Your nickname, shared quests and comments are still checked by Anthropic's Claude, as the Community Guidelines say.” See When anything is sent.
• Usage analytics: Profile › Settings › Privacy & Data › Share usage analyticsProfile›Settings›Privacy & Data›Share usage analytics. Off means no events are sent.
• Notifications: Profile › Settings › NotificationsProfile›Settings›Notifications. Turn reminders and “Updates & offers” (marketing) on or off and pick your reminder hour.
• Phone permission: turn notifications for LevelUp off in your phone's settings at any time. Your choices in the app are saved but nothing reaches you.
• Widgets: remove LevelUp widgets from your home screen or lock screen.
• Nickname and photo: change your name or photo from the Profile menu (“Edit Nickname”, “Update Profile Picture”).
• What you publish: unpublish or delete quests, and delete your comments, at any time.
• Automatic checks of community text: there is no setting to turn them off. They apply only to what you publish, so not publishing is the only way to avoid them (see Automatic checks of community text).
• Blocking: block someone from the “…” menu on their quest or comment, and unblock them at Profile › Settings › Blocked UsersProfile›Settings›Blocked Users.
• Delete your account: Profile › Settings › Privacy & Data › Delete accountProfile›Settings›Privacy & Data›Delete account. See Deleting your account.

Under KVKK (Art. 11)

You have the right to:

• (a) learn whether we process your personal data;
• (b) ask for information about it if we do;
• (c) learn why we process it and whether it is used for that purpose;
• (ç) know the third parties in Türkiye or abroad to whom it is transferred;
• (d) ask us to correct it if it is incomplete or wrong;
• (e) ask us to erase or destroy it under the conditions of KVKK Art. 7;
• (f) ask us to tell the third parties who received it about a correction, erasure or destruction;
• (g) object to a result against you that comes only from automated analysis of your data;
• (ğ) claim compensation if you suffer damage from unlawful processing.

The Turkish notice under KVKK is the KVKK Aydınlatma Metni.

Under the GDPR, for users in the EU/EEA

If you are in the EU or EEA, you also have the right to access your data (Art. 15), correct it (Art. 16), have it erased (Art. 17), restrict its use (Art. 18), receive it in a portable format (Art. 20), object to processing based on legitimate interests (Art. 21), and not be subject to a decision based solely on automated processing that significantly affects you (Art. 22). Where we rely on your consent, you can withdraw it at any time; this does not affect what we did before.

Automated steps. Some moderation steps run automatically, without a person deciding first: hiding an item or removing a nickname after reports from trusted reporters, and suspending an account that connects from an installation on the ban list (see Moderation and safety). A person on our team reviews reports and the steps they trigger, and can reverse them. A suspension because of a phone on the ban list does not go to a person unless you ask. In every case you can ask for a person to look at the decision, give your view and contest it, free of charge, by email (KVKK Art. 11(1)(g); GDPR Art. 22(3)); see How to use your rights.

The automatic check of community text can also refuse to publish what you wrote, or remove a nickname, with no person involved. The app then says only that the text doesn't meet our Community Guidelines, without naming the rule; you can ask us to look at it again by email.

How to use your rights

Write to [email protected].

Because LevelUp accounts have no sign-in, we need a way to match your request to your account:

• Include your Support ID. You find it in the app at Profile › Settings › Help & ContactProfile›Settings›Help & Contact (tap it to share or copy it) and on the “Account suspended” screen. An email you start from Help & Contact › Email supportHelp & Contact›Email support, or from Contact support on the suspended screen, already includes it at the end of the message. It is how we find your account.
• If you no longer have the phone or the app, we may not be able to identify your account. We will tell you if that is the case.

Formal KVKK applications. Under the KVKK application communiqué (Veri Sorumlusuna Başvuru Usul ve Esasları Hakkında Tebliğ), you can also apply in Turkish:

• in writing, to our registered address above;
• by email to [email protected], signed with a secure electronic signature or a mobile signature.

You can also simply write to us by email with your Support ID, as described above: we handle those requests too, and we do not ask for your Turkish ID number for them. Before we act on such a request, especially one for a copy of your data, we may ask you questions that only the account holder can answer.

A formal application must include:

• your name and surname, and your signature if it is on paper;
• your Turkish ID number or, for foreign nationals, your nationality and passport or ID number;
• your address for notices;
• your email address or phone number, if you have one;
• your request.

Response times. Under KVKK we answer within 30 days, free of charge unless the communiqué allows a fee for the cost of the reply. Under the GDPR we answer within one month; this can be extended by two more months for complex requests, and we will tell you if it is.

Complaints.

• KVKK: if we refuse your application, our answer is not enough, or we do not answer in time, you can complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) within 30 days of our answer, and in any case within 60 days of your application.
• GDPR: you can complain to the data protection authority in the EU/EEA country where you live or work, or where you think the problem happened.
• To contest a moderation decision, email us at [email protected].

Minimum age. LevelUp is for people aged 13 and over. It is not directed to children under 13, including for the purposes of the US Children's Online Privacy Protection Act (COPPA), and we do not knowingly collect data from them. The app has no age check today.

You can turn off the permissions you gave (AI plans, usage analytics and “Updates & offers”) at any time in Profile › SettingsProfile›Settings. If you are under 18, we suggest reviewing them with a parent.

If we learn that an account belongs to a child under 13, we will suspend the account and then delete it and its data. If you are a parent or guardian and think your child under 13 uses LevelUp, email [email protected] with the subject "Child under 13". If you can, include the account's Support ID (in the app at Profile › Settings › Help & ContactProfile›Settings›Help & Contact): we find and delete accounts by it. That is all we need to delete the account. If you ask us for a copy of the child's data instead, we will also ask you to show that you are the child's parent or guardian.

Our statement on safety and young users. We are committed to complying with the child-safety and privacy laws that apply to LevelUp, including KVKK and, for users in the EU and EEA, the GDPR. In particular:

• AI disclosure: AI plans are written by Claude, an AI made by Anthropic, not by a person. The app says so before anything is sent for a plan.
• Live safeguards:
  • Consent before any data goes to the AI for a plan
  • Safety rules in plan generation, with refusals and a pointer to a doctor or a local support line
  • Reporting of quests, comments and accounts in the app, and by email for people without the app
  • Automatic hiding at once for child-safety, intimate-image and sexual-content reports from trusted reporters, and after 3 trusted reports for anything; child-safety and intimate-image reports always alert our team at once
  • Human review, with a 24-hour review target
  • Removal of content, name removal and suspensions, which carry over to new accounts on the same phone
  • No private messages and no public images: profile photos are not shown to other users
  • Blocking other users
  • Automatic checks of community text before it is published
  • “Report this plan” under every AI plan
• Safety resources: our Safety page explains how to use LevelUp and AI plans safely; helplines by country are in our Community Guidelines.
• Reporting child-safety concerns: in the app, report the quest, comment or account with the reason “Child safety”. Without the app, see Child safety and Report content. Do not send us the material itself.

We protect your data with technical and organisational measures, including:

• Encryption in transit: the app talks to our servers over HTTPS (TLS), and our servers use encrypted connections to our database and to our AI, sign-in and subscription providers.
• Access controls: your account's private data is returned only to the app signed in to your account.
• Moderation tools are protected by a secret key, and only they can read legal-hold copies.
• Profile photos are shown only to their owner in the app. The stored file sits behind a private link that we do not share with other users; anyone who had that link could open the image.
• Limits on request rates and strict checks on everything the app sends.

We do not claim any security certification. No system is perfectly secure. If a breach affects your personal data, we will notify the KVKK Board within 72 hours of learning of it and, where the GDPR applies, the competent data protection authorities as it requires. We will tell you as soon as reasonably possible in the app, for example in its inbox, and, where we cannot reach you there, with a notice on this website.

• Request logs: our servers log each request to them: your IP address, the date and time, the method, the address requested (IDs in the address and technical settings such as the app language included), the status, the response size, the referrer and the user agent. Explore search text is written as "[redacted]", and any other query text that is not on a fixed list of technical settings is dropped. Our hosting provider's (Heroku's) own logs still record the full address, including search text. Sign-in tokens and the installation ID are not logged.
• Error logs can include internal user IDs, Firebase user IDs and error details.
• Retention: today these logs go only to Heroku's live log buffer (EU (AWS eu-west-1, Dublin, IE)), which keeps them for at most one week. We keep no long-term copy.

This website sets no cookies and uses no analytics, trackers or third-party embeds. Fonts and images are served from this site.

• Web host: Vercel Inc. delivers this website. Like any web server, it processes your IP address, browser details (user agent), the page requested and the time, to deliver the pages and protect them from attacks. It is located in US and keeps these logs for a limited period for security and operations, as set by Vercel Inc..
• Email: our support inbox is hosted by Google Workspace. When you email us, it processes your email address, your message and attachments, and the technical details of the email.
• Opening these pages from the app: the app shows them in your phone's in-app browser. That browser may keep its own history under your phone's settings.

When we change this policy, we update the version, the effective date and the change log at the top of this page. If a change is significant, we will also tell you clearly before it takes effect, on this page and, where we can, in the app, and ask for your consent again where the law requires it. If what we send to Anthropic for AI plans changes, the app asks for your permission again before sending anything more for a plan.

For privacy questions and requests, write to [email protected], or use Profile › Settings › Help & ContactProfile›Settings›Help & Contact in the app. Who we are: Who is responsible for your data; our full operator details are on the Support page.