Privacy Policy

Basso

Basso is a voice-training app. This section applies to every version of Basso: App Store, Google Play, Samsung Galaxy Store and Huawei AppGallery.

Basso is published by Şinasi Demirel under the Tiki Studios name. For Basso, the data controller is Şinasi Demirel (Tiki Studios), the individual publisher. You can reach us at support@tikistudios.io.

The short version

• Basso never uploads your voice or recordings. Microphone audio is analyzed on your phone in real time and is never uploaded to us or anyone else. Optional recordings stay on your device, and your phone's own backup may include them.
• No account in the App Store, Google Play and Galaxy Store versions; subscriptions there use RevenueCat's anonymous app-user ID. The Huawei version uses HUAWEI ID sign-in and a pseudonymous billing account, described below. Basso never receives your Huawei password and does not ask for your email, name or profile photo.
• Your detailed training records stay on your device. Selected numeric pitch measurements and usage events are sent to Firebase Analytics, as described below.
• No ads in the app; ad measurement you control. Basso shows no advertising. To learn which of our own ads bring people to Basso, the App Store and Google Play versions use Adjust, and on iPhone and iPad Apple Ads attribution. In the EEA, the UK and Switzerland this needs your consent; everywhere you can turn it off in Settings → Ad measurement. It never happens for users under 18.
• Analytics is switched off for users under 18. Until the birth-year screen, the first onboarding events are held in memory and discarded for anyone under 18.

Data kept only on your device

These records are stored on your device, in a local database or as temporary files. They are not sent to our Huawei billing server. Selected numbers and usage events go to Firebase Analytics as described in the next part.

• Voice audio. Voice tests and exercises stream microphone audio straight into Basso's on-device pitch analysis. The audio is discarded as it is analyzed. Two optional features keep audio, which Basso keeps on your device and never uploads. Record & compare saves one temporary recording (a WAV file of up to about 10 seconds) so you can play your take back against the coach's, deleted automatically when you close the feature. The Voice Time Capsule, if you choose to keep recordings, saves the passage you read in your first voice test and in each weekly voice test so you can hear your progress later. You can delete all capsule recordings at any time, with or without a subscription, in Settings → Delete voice recordings; this also stops new ones being saved.
• Voice measurements: median pitch and pitch percentiles in hertz, pitch stability, lowest comfortable pitch, voiced ratio, ambient noise level, a measurement-quality flag, your device model and the local hour of the test.
• Profile and settings: your birth year (used only for the under-18 protections described below), whether you are under 18, your goal, daily practice time, language and reminder times.
• Training progress: your program, completed sessions and exercises, settings, and a local copy of your subscription status.
• Speak Check: texts you write to practice reading aloud, and the summary of each take (share of speaking time in your target pitch zone, median pitch, duration). They are never uploaded and never included in analytics.
• Favorites: exercises you star in the library.
• Voice Match: your take is analyzed while you read and is not kept. Only its scores (melody, pace, overall) and the line it was for are stored. The reference lines come with the app.
• Challenges and goals: the start date of the 30-Day Voice Challenge or the number of days you chose for a monthly goal. Your progress is worked out on the device from your completed sessions.

Reminders are scheduled by your phone's operating system; no server is involved. Share cards, including "Your year in voice", are created on your device and leave it only through the app you choose to share to.

Your phone's operating system may back up eligible app data, files (including Voice Time Capsule recordings) and preferences, or move them to a new device, under your backup settings. We do not store these copies. Clearing Basso's storage or uninstalling it does not necessarily remove an existing backup; manage those copies with your backup provider.

Data that leaves your device

Firebase Analytics (Google). Basso records usage events:

• app opens;
• onboarding start, each onboarding screen you reach (a fixed step name), the time you spend on it and whether you go on, skip it or go back, your goal and daily practice-time choice, age confirmation, and finishing onboarding;
• your onboarding answers: "That's me" or "Not me" for each of four fixed quick-check statements (for example whether your voice gets quieter in meetings), and "Sounds right" or "Not sure" for each of the three results shown after the voice test (your pitch, how much it moves and your starting lion stage). They are sent as fixed identifiers with yes/no values, never as text. The same fixed answers, and whether you allowed the microphone, are also attached to the event for the screen you leave;
• the first-day tour of the Today screen: when it starts, which step you see, and whether you finish or skip it (and at which step);
• microphone-permission result and whether the ambient-noise check passed before a test;
• voice-test completions with a measurement-quality flag, and skipping the low-range test;
• viewing your result and your plan, and which training track you were assigned (track name and the version of the configuration that chose it);
• weekly re-tests, paywall views, trial starts, purchases (product identifier only) and restores;
• session starts and completions (session identifier and duration) and completed exercise blocks;
• sharing, notification opens, settings changes, and whether the notice suggesting a speech-language pathologist was shown to you.

Voice-test and re-test events include pitch values in hertz (median and low-range pitch, and the change from your baseline). Events never contain audio, free text, names or contact details. They are linked to a random Firebase app-instance ID, together with device model, OS version, app version and approximate location derived from your IP address (such as country, region or city). No GPS permission is used.

If your birth year shows you are under 18, Basso does not collect analytics. Before you enter your birth year, the events from the first onboarding screens are held only in the app's memory. They are sent once you confirm an adult birth year, and discarded if you are under 18 or close the app first. App opens and Firebase's own automatic events (such as the first-open event) are not held back.

Firebase Crashlytics (Google). If Basso crashes, a crash report is sent with the technical details of the crash (the stack trace and the device state at the time), your device model, OS and app version, linked to a Crashlytics installation ID. Crash reporting is off in debug builds.

RevenueCat. In the App Store, Google Play and Galaxy Store versions, RevenueCat manages your subscription under an anonymous app-user ID that RevenueCat generates. Basso never signs you in to RevenueCat, and we do not link this ID to your identity. The store processes the payment; we never see your card details or your store-account identity. Once you confirm an adult birth year, RevenueCat also:

• sends subscription events (free trial started, purchase or renewal, cancellation or its reversal, expiry, billing problem, plan change) to Firebase Analytics, linked to the same random Firebase app-instance ID, so we can see whether people who finish onboarding go on to subscribe;
• records each time one of Basso's purchase screens is shown.

Neither happens for users under 18.

Manage subscription. With an App Store or Google Play subscription, Settings → Manage subscription opens a screen provided by RevenueCat. There you can restore purchases and cancel through your store, and on iPhone and iPad also ask Apple for a refund or change plans. If you cancel there, it may ask why, with a choice from a short list; RevenueCat stores your choice with the anonymous app-user ID.

Apple Ads attribution (iPhone and iPad only). After you confirm an adult birth year, Basso asks Apple's AdServices framework for an attribution token and passes it to RevenueCat. RevenueCat exchanges it with Apple, and Apple says whether the install came from an Apple Ads campaign. If it did, Apple also returns the campaign, ad group, keyword and ad identifiers and the country or region. RevenueCat keeps this with the anonymous app-user ID, so we can see which of our own Apple Ads campaigns lead to trials and subscriptions. This attribution uses no advertising identifier, is not combined with data from other companies' apps or websites, and does not depend on Apple's tracking prompt. The Android and Huawei versions do not do this, and it never happens for users under 18.

Ad measurement (Adjust). The App Store and Google Play versions use Adjust (Adjust GmbH, Berlin, Germany) to measure which of our ads lead people to install Basso, use it and start a trial or subscription. Adjust is not used in the Galaxy Store and Huawei versions, on our own test devices, or for users under 18, including anyone who entered an under-18 birth year during the current app session.

• What Adjust receives from the app: an Adjust device identifier; on Android, the Google Advertising ID (unless you have deleted or limited it in your device settings) and the Google Play install referrer; on iPhone and iPad, the identifier for vendors and, only if you allow tracking in Apple's tracking prompt, the identifier for advertisers (IDFA); Apple's SKAdNetwork and AdAttributionKit postbacks; your IP address, device model, OS and app version, and install and app-open times. It also receives these moments: onboarding finished (with its number of steps and duration), your first voice test finished (that it happened, without any result), a purchase screen shown (which one, and where it was opened from), a free trial started and a paid purchase completed (with the product, without the price), a training session finished (with its identifier and duration), your first finished session, and a weekly voice check-up finished.
• What RevenueCat sends Adjust: your subscription events (purchase, free trial started, trial converted, trial cancelled, renewal, cancellation, expiry and plan change) with the product, currency and revenue after store commission and estimated taxes, linked to the Adjust device identifier. To do this, Basso gives RevenueCat the Adjust device identifier and the device identifiers above (the IDFA only after you allow tracking), stored with the anonymous app-user ID; when Adjust attributes your install to an ad, Basso also gives RevenueCat the names of that ad network, campaign, ad group and creative. A refund reaches Adjust only as a cancellation, without an amount.
• Never sent to Adjust: audio, pitch or other voice measurements, training records, your birth year, names or contact details.
• What it is for: linking an install, and what follows it, to the ad campaign that led to it, and reporting those results to the ad networks we advertise with (Meta, Google, TikTok and Apple) so they can measure and improve our campaigns. We do not sell your data.
• Your choice: in the EEA, the UK and Switzerland, Adjust starts only if you allow it right after you enter your birth year: on Android when Basso asks, and on iPhone and iPad by allowing tracking in Apple's prompt. Your choice is passed to Google as its consent signals. Elsewhere it starts after you confirm an adult birth year. Everywhere you can turn it off at any time in Settings → Ad measurement, which also withdraws your consent. On iPhone and iPad you can also refuse or withdraw tracking in Apple's prompt or in iOS settings. Adjust's privacy policy: https://www.adjust.com/terms/privacy-policy/.

Apple refund requests. If you ask Apple for a refund of a Basso subscription, Apple may ask us for information about the purchase. RevenueCat answers for us: whether the subscription was delivered, whether a free trial was offered, and that you agreed to this in our Terms. It sends no usage data. We do not ask Apple to refuse your refund; Apple makes the decision.

Google Play chargebacks. If you dispute a Google Play charge for Basso with your bank or card issuer, Google may ask us about the purchase. RevenueCat answers for us that a free trial was offered and that we have no preference about the outcome. It sends no usage or account data; Google makes the decision.

Huawei version only. Huawei In-App Purchases has no subscription-management service we can use from the app, so the Huawei version uses our own billing server instead of RevenueCat:

• When you buy or restore a subscription, Basso uses HUAWEI ID to sign you in. Huawei gives the app a single-use authorization code with the identity permissions needed to prove you own the subscription. Our server redeems it with Huawei and turns your app-specific HUAWEI ID OpenID into a pseudonymous Basso billing ID: a one-way hash of Basso's app ID and that OpenID. The server does not keep the raw OpenID or Huawei's access and refresh tokens. We never receive your name, email or phone number.
• The server issues its own short-lived session for that pseudonymous ID. No Firebase Authentication account is created, and the app does not contact Google sign-in. A pseudonymous ownership hint on your device is used only to clear stale access after you switch accounts; it does not grant access.
• The server stores that pseudonymous ID, purchase-intent identifiers with their product and times, subscription identifiers and purchase tokens, the product, payment environment, subscription status, expiry and verification times. Signed receipts, price and currency are processed to validate a purchase, but the complete signed receipts are not kept. We use these records to verify that you own the subscription and that it is paid, to restore interrupted purchases, and to stop receipts being replayed or moved between accounts.
• To prevent reuse and abuse, the server also keeps hashed authorization-code identifiers and IP-address or rate-limit identifiers. The hosting may process request metadata and operational logs. Huawei purchase notifications only update subscription records that were already verified; an unsigned notification cannot grant access.
• Voice audio, your birth year and your training progress are never sent to this server.
• The server runs on Hetzner in Helsinki, Finland. Its records are stored in Google Firebase Firestore in Frankfurt, Germany. Google decides where else it processes data under its own Firebase terms, so the Frankfurt location does not mean Analytics data stays in Frankfurt.
• Huawei processes the payment; Basso never receives card or bank details.
• You can delete this account in the app under Settings → Delete Basso billing account. See Delete your Basso billing account for what is deleted and what is kept.

We do not sell personal data, and we do not share Basso data with anyone other than the providers named in this section.

Problem reports. If you tap Report a problem, Basso opens an email to support@tikistudios.io in your own mail app. The email is prefilled with diagnostics: app version and build, store and flavor, OS version, device manufacturer and model, language, the time in UTC, your subscription status and expiry as stored on the device, and your training position (program and track, current session and week, the Home card shown, your last completed session and its time, completed-session count and streak). In the App Store, Google Play and Galaxy Store versions it also includes the RevenueCat app-user ID; in the Huawei version it includes the pseudonymous Basso billing ID when you are signed in, and RevenueCat is not contacted. You can read and edit it before sending. If no mail app can open it, Basso copies the report to your clipboard and shows the support address. Nothing is sent unless you send it. When you do, your mail provider and our support mailbox process your address, your message and the diagnostics to help you. The diagnostics never include card details, passwords, payment PINs, purchase tokens, signed receipts or voice recordings. Anything else you add is part of your message.

What Basso does not collect

• Your voice audio: it is processed on your device and never uploaded.
• Names, contact details or passwords: the app never asks for them. The Huawei version processes the pseudonymous identity described above. If you email us, we receive your email address and your message.
• Cross-app tracking without your permission: Basso has no ad networks in the app. Advertising identifiers are used only for the Adjust ad measurement above: the Google Advertising ID on Android, and the IDFA on iPhone and iPad only if you allow tracking. The only other ad-related data is the Apple Ads attribution record.
• Precise location, contacts, photos or other device data beyond what this section describes.

How Basso uses data

We use the data above to run and improve Basso: to see which features are used and how people progress through the programs, to fix crashes, to manage subscriptions, and to measure which of our own ad campaigns lead to installs and subscriptions. We do not show ads in Basso, we do not build profiles of you, and we do not target ads to you individually. Ad networks receive campaign results only so they can measure and improve our own campaigns.

Where Basso data is processed

Google Firebase, Hetzner, RevenueCat, Adjust and Huawei each process the Basso data described above. Their infrastructure may process data outside your country, including in Europe, the United States and other locations, under their own terms. The regions chosen for the Huawei billing server and its database do not decide where every provider processes data. Their privacy information:

• Google Firebase: https://firebase.google.com/support/privacy and https://policies.google.com/privacy
• RevenueCat: https://www.revenuecat.com/privacy
• Adjust: https://www.adjust.com/terms/privacy-policy/
• Huawei: https://consumer.huawei.com/en/privacy/

Microphone

Basso asks for microphone access only to analyze your voice on your device. You can turn the permission off in your phone's settings. Voice tests and exercises then stop working, but the rest of the app keeps working.

Age

Basso is for people aged 13 and over. During onboarding Basso asks for your birth year. The birth year, and whether you are under 18, are stored only on your device. Users under 18 get no analytics collection, none of RevenueCat's analytics links (subscription events, purchase-screen views and Apple Ads attribution) and no ad measurement.

If you are a parent or guardian and believe a child under 13 is using Basso, contact support@tikistudios.io.

How long Basso keeps data

These periods apply to Basso instead of the general ones above.

• On-device data (voice measurements, profile, progress, settings) stays in the app's storage until you clear it or uninstall Basso. Phone backups are kept separately and are managed through your backup provider.
• Temporary files (the Record & compare recording and share-card images) are deleted automatically by the app or the operating system.
• Analytics and crash data are kept under our Firebase project settings and Google's processing terms. Crashlytics keeps crash reports for 90 days before deleting them. See https://firebase.google.com/support/privacy.
• App Store, Google Play and Galaxy Store purchase records are kept by RevenueCat under the anonymous app-user ID to manage and restore your subscription. On iPhone and iPad the Apple Ads attribution record is kept with them, as is any answer you give to the cancellation question in Manage subscription.
• Huawei billing account: when you delete it, the server removes your purchase intents and the stored payment tokens, status and expiry, and the app ends its session. Automatic billing sign-in stays off afterwards, even after reinstalling. To stop another account from claiming your old purchase, and to let you restore it yourself later, the server keeps minimal hashed proofs that you own the subscription and the purchase intent, and a deletion marker. A purchase-intent proof holds only the pseudonymous owner, the product, its issue time and the linked subscription hash; no payment token or original intent ID is kept. Signing in, buying or restoring again can create a new Basso billing account. Your HUAWEI ID and Huawei's own store records are controlled by Huawei; deleting the Basso billing account does not delete them or cancel your subscription.
• Huawei anti-abuse records: authorization-code markers expire after 10 minutes and rate-limit counters after 2 days. Expired records can stay until maintenance removes them, because automatic periodic cleanup is currently off. Application logs rotate within three 1 MB files per container, so how long they last depends on how much is logged. Proxy access logging is off. The billing server has no configured volume backups, Firestore backup schedules or point-in-time recovery. None of this changes Google's own processing and deletion periods.
• Ad measurement data is kept by Adjust under its data-processing terms with us.
• Support emails are kept only as long as needed to handle your request.

Deleting your data

• On your device: clear Basso's storage or delete the app. To delete only the Voice Time Capsule recordings, use Settings → Delete voice recordings. Your phone's backups may keep a copy until those backups are deleted.
• Analytics, crash and purchase records: email support@tikistudios.io. We delete what we can link to your app-instance ID or purchase ID.
• Ad measurement data: turning off Settings → Ad measurement stops further collection. To have the existing Adjust record deleted, email support@tikistudios.io.
• Huawei billing account: use Settings → Delete Basso billing account in the app. The steps, and what is kept, are on Delete your Basso billing account.

Your rights in Basso

You have the rights described in the general part of this policy. For Basso: for on-device data, delete the app or its data; for the Huawei billing account, use the signed-in deletion in Settings; for other provider records, or for access and correction requests, email support@tikistudios.io. We must check that the request is about your own record. Deleting a billing account does not cancel the subscription at the store. You can also complain to your local data-protection authority.

Security in Basso

Voice audio is processed on your device. Detailed training records stay in the app's private storage, protected by your phone's app sandboxing and encryption. The analytics events and subscription records that leave your device are protected by Google, Hetzner, RevenueCat, Adjust and Huawei under their security and data-processing terms. No method of sending or storing data is completely secure.

Pipzi

Pipzi is a 52-week speed-reading training app. You don't need an account, and the reading you do stays with you.

The short version

• No account. Pipzi never asks for your email or password.
• Your books and progress stay on your device.
• Free and Lite plans show ads through Google AdMob. Pro has no ads.
• Usage statistics can be turned off in Profile → Settings.
• Ad measurement you control. Adjust tells us which of our ads bring new readers; you can turn it off in Settings.

Data kept only on your device

• The name you choose, reading language, daily goal, reminder time and other settings.
• Your progress: lessons, streaks, reading speed and comprehension results (including your Effective Reading Speed), league position, gems, quests and items.
• Books and texts you add: EPUB or PDF files you import, "My Book" measurements, and texts you save in your pocket (scanned pages, articles fetched from links, text shared from other apps or pasted). They stay on your device. Deleting the app removes all of it.

Reminders are scheduled by your phone's operating system; no reminder data leaves your device.

Camera, links and sharing

• Scanning a page uses your device's camera through the system document scanner (VisionKit on iOS; Google's document scanner on Android). Text is recognised on your device. Pipzi does not keep the photos and never sends them to us.
• Adding a link causes Pipzi to download that page directly from its website on your device. The link and the extracted text are not sent to us.
• Text you share from another app is handed to Pipzi on your device and waits in your pocket.
• Paragraph Mode (offered only in Turkey) is shown based on your device's region and time zone, checked on your device.

Usage statistics and crash reports

To understand which parts of Pipzi help people read better and to fix problems, the app uses Google Firebase:

• Firebase Analytics records app events (for example opening the app, finishing a lesson, making a purchase, running a weekly check), including your reading results as numbers (baseline ERS, weekly ERS, "My Book" speed, league rank), device model, OS version, app version, language and an approximate region. Events are linked to a random app-instance ID and never contain the text you read, book titles or your name.
• Firebase Crashlytics sends crash reports with technical details of the device state at the time of the crash.
• Firebase Remote Config downloads app settings, such as the free plan's daily energy numbers, linked to your app-instance ID.

You can turn off analytics and crash reporting together in Profile → Settings → Share usage data.

Advertising

On the free and Lite plans, Pipzi shows ads from Google AdMob: an optional video that gives you one more lesson, and at most one full-screen ad after a lesson or a daily reading. There are never ads during a reading, after the weekly check, or on Pro. AdMob receives your device's advertising identifier (if you allow it on iOS), IP address, device information and ad interactions. In the EEA, the UK and Switzerland Google's consent form asks for your choices before any ad is requested; you can change your choices at any time in Profile → Settings → Ad privacy choices. On iOS, Pipzi asks for App Tracking Transparency permission only after you agree to the relevant consent purposes; without it, ads are not personalised.

Ad measurement

Pipzi uses Adjust (Adjust GmbH, Berlin, Germany) to learn which of our own ads bring people to Pipzi and lead to a trial or a subscription. Adjust receives an Adjust device ID; on Android, the Google advertising ID (unless you deleted it) and the Play install referrer; on iPhone and iPad, the identifier for vendors and, only if you allow tracking when Apple asks, the advertising identifier (IDFA); Apple's ad attribution token (which Apple Ads campaign, if any, led to the install); Apple's SKAdNetwork and AdAttributionKit postbacks; your IP address, device model, operating system and app version; install and app-open times; and these in-app events: finishing the reading test, finishing onboarding, finishing your first lesson and every later lesson, finishing the weekly test, seeing the subscription offer, starting a trial and subscribing (with the plan's name, never a price). RevenueCat sends Adjust your subscription events (trial, purchase, renewal, cancellation, refund, with product, price and currency), and keeps which campaign brought you (ad network, campaign, ad group and ad) so purchases can be reported by campaign. When you turn ad measurement off, Pipzi tells RevenueCat to stop sending your events to Adjust. Adjust passes campaign results to the ad networks we advertise with (Meta, Google, TikTok and Apple) so they can measure our campaigns. Adjust never receives the texts or books you read, your reading results, your name or your contact details.

In the EEA, the UK and Switzerland, Adjust runs only if you agree to it in Google's consent form, where it is listed among the partners, and Pipzi passes your choices on to Google. You can change them at any time in Profile → Settings → Ad privacy choices. Elsewhere you can turn ad measurement off at any time in Profile → Settings → Ad measurement. On iPhone and iPad, Pipzi asks Apple's tracking question only once, for ads and ad measurement together.

Subscriptions

Pipzi Pro and Lite are sold through the Apple App Store or Google Play. We use RevenueCat to verify and manage subscription entitlements. RevenueCat receives the store's purchase receipts, a random app user identifier and when a plans screen is shown to you (to compare offers); not your name or email. We never see your payment details. Gem packs are bought through the same stores and RevenueCat. If you have a plan, Profile → Settings → Manage subscription opens RevenueCat's subscription screen; anything you choose or answer there (for example a reason for cancelling, or a refund request) goes to RevenueCat and the store. While ad measurement runs, Pipzi also gives RevenueCat your Adjust device ID and the device identifiers listed under "Ad measurement", so that RevenueCat can send your subscription events to Adjust.

Subscription events in Google Analytics. When Share usage data is on, Pipzi gives RevenueCat your random Firebase app-instance ID. RevenueCat then sends subscription events (free trial started, purchase, cancellation, renewal resumed, expiration, billing problem, plan change) to Google Analytics, linked to that ID. We use them to see whether the app works for subscribers. They contain no name, email or reading text. Turning Share usage data off removes the ID from RevenueCat.

Apple Ads attribution (iOS). When Share usage data is on, Pipzi on iPhone and iPad lets RevenueCat collect Apple's ad attribution token. It tells us which Apple Ads campaign, ad group and keyword, if any, led to the install. It does not use your advertising identifier and needs no tracking permission. Turning the setting off stops this from the next launch. While ad measurement runs, Adjust also receives this token (see "Ad measurement").

Apple refund requests. If you ask Apple for a refund of a Pipzi subscription or gem pack, Apple may ask us for information about the purchase. RevenueCat answers for us with consumption information only, as Apple defines it, such as whether and how much of the purchased content was used, how long you have used the app, and counts of your purchases and refunds. We do not ask Apple to refuse your refund; Apple makes the decision.

Age

Pipzi is for people aged 13 and over and is not directed to children.

Deleting your data

• On your device: delete the app. Reset progress in Settings clears your progress but keeps your settings and purchases.
• Analytics, crash, purchase and ad-measurement records: email support@tikistudios.io. Pipzi has no account, so tell us the approximate date you installed the app and your platform, and we will delete what we can link to your app-instance ID, purchase ID or Adjust device ID. Turning off ad measurement stops further measurement.

PromptMaster

PromptMaster teaches you to write better prompts for AI tools through short daily lessons.

The short version

• No account and no PromptMaster server.
• The prompts you write are scored on your device and are never sent anywhere or saved. Only the score is kept.
• The free plan shows ads through Google AdMob. Premium has no ads.

Data kept only on your device

• An optional name, your role, language and reminder settings.
• Your progress: XP, streak, active days, hearts, gems, completed lessons and best scores, questions to review, saved templates and league data.

You can clear this in Profile → Reset. Reset keeps your language, Premium status, reminder preferences, and the per-device counters for rating requests and paywall displays. Everything else — progress, XP, streak, hearts, gems, completed lessons, scores, badges and saved templates — is deleted.

Data that leaves your device

Firebase Analytics, Crashlytics and Remote Config (Google). PromptMaster records screen views and usage events (onboarding steps and answers you pick from a list, lessons started and finished, paywall views, purchases, rewarded ads, ad errors, rating requests), and crash reports. Events never contain your name or the text of your prompts. Remote Config sets how often ads may appear and which optional introduction steps are shown; we use it to compare a shorter introduction with the full one, and every version is part of the app. This data is linked to a random app-instance ID, plus device model, OS version, app version and approximate country. It starts when you open the app, based on our legitimate interest in keeping the app reliable and improving it.

Google AdMob. The free plan shows a full-screen ad after some lessons and optional rewarded videos. AdMob receives your device's advertising identifier (if you allow it), IP address, device information and ad interactions. Google's consent form asks for your choices before any ad is requested where the law requires it. You can reopen it under Profile → Ad privacy settings. On iOS, PromptMaster asks for tracking permission only after you have agreed to the relevant consent purposes; without it, ads are not personalized.

RevenueCat. Manages your Premium subscription under an anonymous ID. Payments are processed by the App Store or Google Play. RevenueCat also stores which introduction version you saw, and it sends subscription status events (free trial started, renewed, cancelled, expired, billing problem) to Firebase Analytics, linked to the same random app-instance ID, so we can see whether the app works for subscribers. On iOS, RevenueCat receives Apple's ad attribution token, which only tells us whether the install came from an Apple Ads campaign; it does not use your advertising identifier and needs no tracking permission. When the free plan shows an ad, RevenueCat also receives, under the same anonymous ID, the ad format and where in the app it appeared, whether it loaded, was shown, was tapped or failed to load, and the revenue Google reports for it. This lets us compare ad and subscription income. Your advertising identifier is not sent to RevenueCat. If you use Manage subscription in Profile, RevenueCat's screen lets you restore purchases and cancel through your store, and on iPhone and iPad also ask Apple for a refund or change plans. If you cancel there, it may ask why, with a choice from a short list; RevenueCat stores your choice with the anonymous ID.

Apple refund requests. If you ask Apple for a refund of a PromptMaster subscription, Apple may ask us for information about the purchase. RevenueCat answers for us with purchase and delivery details, such as whether the subscription was delivered and whether a free trial was offered. We do not ask Apple to refuse your refund; Apple makes the decision.

Huawei version. The AppGallery version uses Huawei In-App Purchases instead of RevenueCat and signs you in with HUAWEI ID to confirm your purchase. Purchase checks happen on your device; we do not run a server for them.

Age

PromptMaster is for people aged 13 and over (16 and over in the EEA if local law requires it for consent to ads).

Deleting your data

• On your device: use Reset or delete the app.
• Analytics, crash and purchase records: email support@tikistudios.io.

MaskedTalk

MaskedTalk is an anonymous chat app for adults aged 18 and over. Its Child Safety Standards and Account Deletion pages are at https://maskedtalk.live/child-safety and https://maskedtalk.live/delete-account.

Data you give us

• Account: email address and password. Email addresses are not verified by email, and we do not send marketing email.
• Profile: username, date of birth, gender, bio, country and city (chosen from a list), interests and an optional profile photo. Other users see your username, profile photo, bio, interests and the age shown on your profile. Your email address is never shown to other users.
• Content: messages, photos, videos and voice notes you send, stories you post, games you play in chat, and reports and blocks you make.
• Calls: voice and video calls are one-to-one and are not recorded. We keep call metadata: who called whom, when and for how long.
• Optional Spotify connection: if you connect Spotify, we receive the access needed to show the music you choose to share.

Data collected automatically

• Safety and anti-abuse data: IP address, user agent, device model, OS version, a device fingerprint and a hash of your email address. We use these to enforce bans, stop fake and duplicate accounts and investigate abuse.
• Usage data: in-app events, recorded in our own database and in Firebase Analytics, linked to your user ID, country and plan.
• Crash and performance data through Firebase Crashlytics and Performance Monitoring, linked to your user ID.
• Push-notification token through Firebase Cloud Messaging, to deliver message and call notifications.

MaskedTalk does not collect GPS location and does not use advertising identifiers or show ads.

Where data is processed

• Our servers: MaskedTalk's database, file storage and real-time services, and its voice and video call server, run on infrastructure we operate on Hetzner in Helsinki, Finland. To connect calls, your device contacts Google's public STUN servers, which see your IP address.
• Google Firebase: analytics, crash reporting, performance monitoring and push notifications.
• RevenueCat: subscription and purchase management, linked to your MaskedTalk user ID. Apple and Google receipts are also checked by our server.
• Purchase events in Google Analytics (Android): RevenueCat processes your purchase and subscription data: what you bought, when, and whether it renews, is cancelled or expires. It also receives your Google Play country, the app version and your app language, and when a paywall or purchase screen is shown to you. We give RevenueCat the random Firebase app-instance ID of your install; RevenueCat uses it to send purchase events (purchase, renewal, cancellation, billing problem, expiration) to Google Analytics for Firebase, linked to that ID. We use this to manage subscriptions and to see which offers work. These events contain no name, email address or message content. If you tap Manage subscription on the Plus screen while your subscription is active, RevenueCat's subscription screen lets you restore purchases and cancel through Google Play. If you cancel there, it may ask why, with a choice from a short list; RevenueCat stores your choice with your app user ID. We do not sell your data.
• Moderation tools: when content is reported or our systems flag an account, our moderation team reviews it in a private Slack workspace (Slack Technologies). Review cards include the usernames and IDs involved, the report reason and description, and the reported conversation. When investigating a report, moderators can look up account details, including email, date of birth, gender, location, bio, message content and attachments, session IP addresses, user agents and device fingerprints.

Safety and moderation

• You must be 18 or older. Sign-up checks your date of birth and our database rejects accounts under 18.
• Profile photos and stories are checked automatically by an image-moderation model running on our own servers. Bios and story text are filtered for abuse, spam and shared contact details.
• Private chats are not automatically scanned. Messages and media sent in private chat are reviewed by our moderation team only when they are reported or an account is under investigation.
• We have zero tolerance for child sexual abuse material and exploitation. We remove it, ban the account and report it to the authorities, as described on our Child Safety Standards page.
• We aim to review reports within 24 hours.

How long we keep data

• Stories: removed one hour after they expire.
• Messages and media, call records: deleted after 30 days.
• In-chat games: deleted after 24 hours.
• Push tokens: deleted after 90 days without use.
• Reports and moderation records: kept as long as needed to keep the platform safe. If you delete your account, reports you made or received are kept without your account attached.
• Banned accounts: when a banned account is deleted, we keep the email address in anonymized form to stop the same person from returning.

Deleting your account

Go to Settings → Account → Delete account and confirm with your password. Your account enters a 30-day grace period, during which you can sign in to restore it. After 30 days, your account and the content linked to it are permanently deleted. Details are on https://maskedtalk.live/delete-account.

To get a copy of your data, email support@tikistudios.io from the address on your account.

Wickstart

Wickstart (formerly First15) helps you give a personal goal fifteen minutes of focused attention. This section covers its App Store and Google Play versions.

The short version

• No Wickstart account and no Wickstart cloud sync. Your private tasks, rituals and session history stay on your device.
• No ads. Wickstart does not use Apple’s advertising identifier (IDFA) or Google’s advertising ID.
• Usage analytics and crash reporting are optional and off by default. You can change the choice together in Settings → Usage & crash reports.
• After onboarding, Wickstart requires a Wickstart Pro subscription. Subscriptions are managed by RevenueCat and the store where you bought them.
• The Fitil sticker pack and animated Fitil packs included with Pro are delivered from the app itself. Using them sends nothing to Tiki Studios.

Data kept on your device

Your ritual names, task text, categories, chosen guides, schedules, reminder and haptic preferences, completed-session records, check-in answers, optional session notes and next steps are stored in the app's private storage. Wickstart uses them to run your rituals and calculate your progress. Guides are included in the app and work offline. Wickstart does not send your private tasks to an AI service.

App blocking on iOS. If you enable Screen Time, Apple's Family Controls picker lets you select individual apps. Wickstart stores opaque selection tokens on your device and shares the minimum selection and timing data with its own Screen Time extensions. Ritual names and private task text are not included in this shared blocking data. Wickstart cannot read the content of the selected apps.

App blocking on Android. If you choose to enable Wickstart's accessibility service and accept its current in-app disclosure, Wickstart uses app identity and window identity, type and focus to determine which app you are using. It compares that identity with your chosen distractions and shows its own pause screen during your ritual. Android grants a broader window-access capability; Wickstart uses it only for this app-detection purpose. Wickstart does not inspect, analyze, store or send screen text, messages, passwords, browsing content, taps or other apps' content. App/window identity metadata stays in a small temporary on-device memory cache and is discarded when the service stops; it is not sent to us or to analytics. Updated access requires a new affirmative review rather than silently reusing older consent. Blocking is optional, timer-only use works without it, and you can skip, disable the service in Android settings, or uninstall at any time.

Pro expiry kept for blocking. App blocking is part of Pro. So that a renewal that happens while the app is closed does not switch your blocking off, the blocking rules on your device keep the end date of your current Pro period plus a 7-day renewal grace. On iOS this date is stored with the rules Wickstart shares with its own Screen Time extensions; on Android it stays in the app's private storage. When the app sees that Pro has ended, it stops blocking at once. This date stays on your device and is not sent to us.

Reminders are scheduled locally by your operating system and use generic text. If you start a free trial and notifications are already allowed, Wickstart schedules one local reminder two days before the trial ends; it does not ask for notification permission for this. The app excludes its private ritual/history storage from the backups it controls. Device or system behavior outside the app is subject to your device provider's settings.

A share card and a JSON export are created only when you request them. A share card omits your task text unless you explicitly choose to include it. An export contains your private ritual and session data, including saved notes and next steps, so choose where to save or share it. These files leave the device only through the destination you choose; we do not receive them automatically.

Fitil stickers and animated packs

The Fitil sticker pack and the animated Fitil packs are included with Pro. Their artwork is bundled in the app; nothing is downloaded from or sent to Tiki Studios when you use them, and no ritual, task or session data is included.

• WhatsApp on Android. When you tap Add to WhatsApp, Wickstart asks WhatsApp to add the pack. WhatsApp then reads the pack's name and sticker images from Wickstart through the app's sticker provider, which only apps holding WhatsApp's sticker permission (com.whatsapp.sticker.READ) can read. Wickstart also asks WhatsApp whether the pack is already added, to show its status. Stickers you have added are kept by WhatsApp under WhatsApp's own privacy policy.
• WhatsApp on iOS. When you tap Add to WhatsApp, Wickstart places the pack on your device's pasteboard, limited to this device and set to expire shortly, and opens WhatsApp, which imports it.
• iMessage. Wickstart's Messages extension shows the stickers in Messages. To decide whether they are unlocked, it reads only a Pro-status record (whether Pro is active and when it expires) that the app stores in its own App Group on your device.
• Animated GIFs. When you share or save an animated Fitil GIF, Wickstart hands the file to your device's system share sheet. Where it goes is your choice.

Data that leaves your device

Optional Firebase Analytics (Google). After you enable Usage & crash reports, Wickstart sends events about screens and onboarding, blocking-permission results, ritual and guide use, fifteen-minute sessions and check-in outcomes, progress views, sharing, settings and purchase flows. Events use predefined categories, public guide IDs, counts, durations and result codes. They never contain your task text, session notes, next steps, ritual names, selected-app identifiers, exported data or free-text error messages. Google processes a random app-instance identifier, app and OS version, device information and approximate geographic information derived from the connection. Wickstart does not enable advertising-related data collection or personalized advertising.

Optional Firebase Crashlytics (Google). With the same choice enabled, Wickstart sends technical crash reports and predefined diagnostic error codes to help us fix failures. Reports include stack traces, device/OS and app version, and a Crashlytics installation identifier. They do not include your private task text, session notes, next steps, ritual names, selected apps or exports. Automatic report uploading stays disabled; Wickstart sends retained reports only while the current choice authorizes it. Turning the choice off stops new optional events and diagnostic submissions. An upload already started cannot be recalled. Reports retained during an opted-out period are discarded rather than sent when you later opt in. Information already received by Google is subject to its retention rules and your rights described above.

RevenueCat. RevenueCat manages subscription status using an anonymous app-user identifier. It receives purchase and transaction information needed to verify access, check free-trial eligibility, restore purchases and prevent duplicate claims, together with technical app and device information. On iOS, its SDK can also send Apple's vendor identifier (IDFV), when available. IDFV is different from the advertising identifier (IDFA). RevenueCat can derive country from the network connection and receive the store's country information. We do not send your task text, session notes, next steps, ritual names, selected apps or session history to RevenueCat. Apple or Google Play processes payments; Wickstart never receives your card details. Subscription checks run independently of the optional Usage & crash reports choice, because the app needs them to open past onboarding.

Support. If you email support@tikistudios.io, we receive the message and any attachments you choose to send. Wickstart does not automatically attach private tasks or diagnostic archives.

Retention of Wickstart provider data

For Wickstart, the following periods apply to the optional reports described above. Google Analytics event-level data retention is set to 2 months and user-level retention to 14 months. New activity resets the user-retention period. These controls do not set the retention period for aggregated reports. Resetting local analytics data does not delete information already received by Google.

Firebase Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal from its live and backup systems. This is not a guarantee that every copy disappears exactly on day 90.

RevenueCat keeps subscription and purchase records to verify access and restore purchases. Local deletion does not erase those records. You can request provider-data deletion through support; deleting a RevenueCat customer does not cancel an App Store or Google Play subscription, and provider deletion may be processed asynchronously.

Deleting and exporting your data

Settings → Export my data (on Android: Export my local data) lets you save your private ritual and session data. Settings → Delete local data removes the app's private ritual/history data and saved app selections, stops its own blocking and reminders, and resets the optional usage choice. It does not cancel a store subscription or delete purchase records held by the store or RevenueCat. Use Manage subscription to cancel a subscription through your store account.

For requests concerning information already sent to service providers, contact support@tikistudios.io. Deleting Wickstart or its local data removes the app's local records; it does not erase records already held by service providers or cancel a subscription. We may need your platform, purchase reference or relevant installation identifier to locate provider records and verify your request. Do not send us your password or full payment details. We respond within 30 days, or sooner where the law requires.

Age

Wickstart is for people aged 13 and over and is not directed to children. It does not make medical or therapeutic claims.

LiftAlong

LiftAlong is a home strength training app. This section explains what LiftAlong specifically collects and how.

The short version

• No ads and no advertising identifiers. On iPhone and iPad, if you installed LiftAlong from one of our Apple Ads campaigns, Apple tells us which campaign it was.
• Usage analytics, without your training records. Firebase Analytics shows us how people move through the introduction and the LiftAlong Pro screens. It never receives your email, the dates in your plan, your session history or camera data.
• Training data stays on your device unless you turn on cloud backup.
• An optional email address is used only to authenticate you via a one-time sign-in code; we do not collect passwords.
• Camera is used only for the experimental chair-tracking feature and processed on-device only; video frames are never uploaded.

Data kept only on your device

• Your training plan selections, session history, repetition counts, load values, resistance settings, effort responses and programme progress.
• Your reminder preferences.

This data is stored only on your device unless you explicitly turn on cloud backup.

Optional account

If you choose to create an account, we collect your email address to send you a sign-in code via Supabase. We do not collect a password. Authentication tokens are stored in your device's secure storage (iOS Keychain / Android Keystore).

Your account data is stored on Supabase infrastructure in Frankfurt, Germany (EU). Supabase is subject to GDPR and acts as a data processor under a data processing agreement with us.

Optional cloud backup

If you turn on cloud backup, your training data is sent over HTTPS to a dedicated row in our Supabase database. Cloud backup is off by default and requires an account. You can pause or delete cloud backup at any time in Settings.

Camera — chair-tracking

The experimental chair-tracking feature requests camera access only when you explicitly activate it. Video frames and pose landmarks are processed on-device only. No camera frames or landmarks are uploaded or stored remotely. A completed set may retain the detected repetition count and any manual correction you enter.

Analytics and Remote Config (Firebase)

LiftAlong uses Firebase Analytics and Firebase Remote Config (Google). Analytics records:

• the introduction steps you complete, how long each takes, and the answers you pick from a list there: your experience level, your home equipment, whether to include floor work, how the example set felt, how many days a week you train, and whether you start free or view the plans;
• the first workout you save, once only: whether you finished all its sets, and which program or studio workout it was (never the name of a workout you made yourself);
• when you view the LiftAlong Pro plans, and when a purchase starts, completes, is cancelled or fails;
• subscription events sent by RevenueCat (see Subscriptions).

Events never contain your email, your name, the dates in your plan, your session history, repetition counts, load values or camera data. They are linked to a random app-instance ID, plus your device's operating system, app version and approximate country. Analytics does not use your advertising identifier (the IDFA on iOS, the advertising ID on Android), and advertising storage and ad personalization are turned off.

Remote Config decides which optional introduction steps are shown. We use it to compare a shorter introduction with the full one. Every version is part of the app; Remote Config never changes prices, unlocks content or adds features.

The legal basis is our legitimate interest in understanding and improving LiftAlong (see How and why we use data).

Subscriptions

LiftAlong Pro subscriptions are processed through your App Store (iOS) or Google Play (Android) account. We use RevenueCat to verify and manage subscription entitlements. RevenueCat receives your app user ID (or an anonymous install ID if you have no account), your subscription status and purchase history. RevenueCat's privacy policy is at revenuecat.com/privacy. We do not receive your payment card details.

RevenueCat also stores which introduction version you saw, and it sends subscription status events (free trial started, renewed, cancelled, expired, billing problem, plan changed) to Firebase Analytics, linked to the same random app-instance ID, so we can see whether LiftAlong works for subscribers. If you use Manage subscription in Settings, RevenueCat's Customer Center may ask why you are cancelling; your answer is kept by RevenueCat with your app user ID.

Apple Ads attribution (iPhone and iPad only). LiftAlong asks Apple's AdServices framework for an attribution token and passes it to RevenueCat. Apple then says whether the install came from an Apple Ads campaign. If it did, Apple also returns the campaign, ad group, keyword and ad identifiers and the country or region. RevenueCat keeps this with your app user ID, so we can see which of our own Apple Ads campaigns lead to trials and subscriptions. No advertising identifier is used, it is not combined with data from other companies' apps or websites, and there is no tracking prompt.

Apple refund requests. If you ask Apple for a refund of a LiftAlong Pro subscription, Apple may ask us for information about the purchase. RevenueCat answers for us with purchase and delivery details, such as whether the subscription was delivered and whether a free trial was offered. We do not ask Apple to refuse your refund; Apple makes the decision.

What we do not collect

LiftAlong does not use advertising identifiers, cross-app tracking, location, contacts, microphone or advertising networks. No data is used to show you ads.

Reminders

If you turn on reminders, they are scheduled as local notifications on your device. No push tokens are sent to our servers.

Age

LiftAlong is not directed at children under 13. If you believe a child under 13 has given us personal data, contact legal@tikistudios.io and we will delete it promptly.

Deleting your data

• On your device: uninstalling the app removes all locally stored training data.
• Cloud backup and account: go to Settings → Delete account. Your cloud training data is deleted immediately and you are signed out. This does not cancel a store subscription.
• Email and auth records: contact legal@tikistudios.io to request full deletion of auth records held by Supabase.