Privacy Policy for KL Status Maker

Last updated: September 30, 2026

KL Status Maker ("the app") is developed by George Komen. This policy explains how the app handles user data.

Summary

KL Status Maker does all video, photo and audio processing on your device, and every feature except the optional AI tools works without an account. Those tools are AI captions, AI music and AI photos: each requires you to sign in with Google, and each sends the text you type to Google Cloud to be answered — see the Accounts and sign-in and AI features sections below. If a caption, a generated picture or a generated music track is offensive or wrong, you can report it, which sends the text behind it — what you typed, and what the model wrote — to the developer for review; the picture and the audio themselves are never sent. Your videos and audio files are never uploaded, with or without an account. Neither are your photos, with two exceptions you choose one photo at a time: the AI photo restyle tool sends the photo you pick to be restyled, and only when you confirm it, and the AI picture chat sends a photo you attach to it, once, at the moment you attach it — see AI photo restyle and Attaching a photo to the AI picture chat below. The app displays no ads of any kind — see the Advertising section below. It also uses Google Firebase Analytics to understand app usage — see the Analytics section below — Google Firebase Crashlytics to receive crash reports — see the Crash Reporting section below — and offers an optional auto-renewing subscription and optional AI credit packs processed by Google Play Billing — see the Subscriptions and purchases section below.

What the app does

KL Status Maker lets you select a video from your device, split it into clips, and save or share the resulting clips. It also lets you replace a video's audio track with a different audio file you choose, edit a video (trim, filters, volume, speed, background music, stickers), edit a photo (rotate, crop, adjust, blur, draw, text, stickers, on-device background cutout, and AI restyle), turn a set of photos into a slideshow video or a collage with optional background music, type a short status and pick a background to render it as an image or a video, and burn a text caption onto an existing photo or video.

All of that video/audio/image processing happens locally on your device using Android's Media3 library and on-device rendering — your videos and audio files are never uploaded anywhere, and neither are your photos except for the two cases described below: a photo you choose to restyle with the AI photo tool is sent to be restyled, once, when you confirm it, and a photo you attach to the AI picture chat is sent once, when you attach it.

The app also offers optional AI tools that use the internet — AI captions, AI music and AI photos — and they are the only parts of the app that send anything off your device: the text you type is sent to Google Cloud to be answered, and AI music and AI photos send back an audio file or a picture that is saved on your device. AI photos is also the one tool that can send something other than text, and it can do so in two ways: if you use it to restyle a photo you already have, that photo is sent, and if you attach a photo to its chat to ask about it, that photo is sent too — see AI photo restyle and Attaching a photo to the AI picture chat below. The photo editor's Cutout tab (background blur, background replace and auto-crop) is not one of them: it runs entirely on your device, needs no account, and sends nothing. All of them are described in the AI features section below.

Data we collect

If you don't sign in — which is how every feature except the AI tools works — the app itself collects no personal information: no name, no email address, no location.

If you do choose to use the AI features and sign in with Google, the app collects and stores the following on servers the developer operates using Google Firebase and Google Cloud:

• Your Google account identifier (a unique ID) and the email address on that account, together with the times the account was created and last signed in.
• Your AI credit balance.
• A record of each AI request you make: what type it was, whether it succeeded, how many credits it cost, and when it started and finished.
• A record of each AI credit purchase: which product was bought, how many credits it granted, and when it was redeemed.
• A photo you choose to restyle with the AI photo tool, or to attach to the AI picture chat, is sent, and is not stored by this app. It is held in memory for the length of that one request and is passed to Google to be checked and answered; the developer's own servers write no copy of it, so there is none kept against your account and none there for you to export or delete. Google may keep a copy in one case that is outside the developer's control — see What Google may keep, and when below. Only the photo you picked is sent, and only when you confirm the restyle or attach the photo. See AI photo restyle and Attaching a photo to the AI picture chat below.
• Any AI output you choose to report: the text itself — a caption, or, for a generated picture or music track, the words the model wrote for it — the prompt that produced it, the reason you picked, and any note you write. Nothing is reported unless you tap "Report" on a particular item — see Reporting AI content below.

Your AI conversations — the prompts you type, the captions generated from them, the music chats with the briefs and lyrics they agreed, and the photo chats with the descriptions they settled on — are otherwise kept on your own device, and the developer's servers store none of them. The same is true of what those tools produce: every generated audio file and every generated picture lives on your device only. What you type is sent to Google to be answered, and Google may keep a message it flags — see What Google may keep, and when below. Filing a report is the one thing that sends any of that text to a server the developer operates, and it sends only the text you reported and the prompt behind it — never an image, generated or your own.

Separately from all of the above, the Google Firebase Analytics SDK collects app usage data — see Analytics below. The Google Firebase Crashlytics SDK collects crash/diagnostic data — see Crash Reporting below. No advertising identifier is collected by the app or by any SDK in it, because the app shows no ads — see Advertising below.

Artwork on the home screen

The buttons on the app's home screen can carry a photograph behind their labels. Those photographs are part of the app itself: they are installed with it and read from inside it, so the app makes no request for them and there is no download to describe.

Earlier versions fetched this artwork from the developer's Google Cloud Storage the first time the app opened, and re-checked it on later launches. That was removed in September 2026, when the pictures were bundled into the app instead.

Accounts and sign-in

An account is optional. It is only needed for the app's AI tools (AI captions, AI music, AI photos, and buying the AI credits they spend); every other feature works without signing in, and the app never asks you to sign in to use them.

Signing in uses Google Sign-In through Firebase Authentication. The app receives your Google account identifier and email address, as listed above. It does not receive or store your Google password, and it does not request access to your Gmail, Google Drive, contacts, or any other Google service.

You can sign out at any time from the Account section of the app's Settings screen. Signing out ends the session on your device and does not delete anything — see the next section for that.

Accessing and deleting your account data

Two controls live in the Account section of the app's Settings screen:

• Export — produces a single JSON file containing everything stored for your account (your sign-in record, your credit balance, your AI request history, your purchase history and any AI content you have reported), plus everything the AI tools saved on your device — your AI caption conversations, your AI music chats, your AI photo chats, and the index of the music tracks and pictures you generated. You can save it or send it anywhere. This is how to exercise the access and data portability rights described under Your rights below, without having to contact anyone.
• Delete — permanently deletes your account: your sign-in record, your credit balance, your AI request history, and everything the AI tools left on your device: your AI caption conversations, your AI music chats, your AI photo chats, your AI music library and your AI photo library — the generated audio files and picture files included. Reports you filed about AI content are kept with your user ID removed, so they no longer identify you (see Reporting AI content below). It takes effect immediately, cannot be undone, and any unspent AI credits are forfeited rather than refunded (the app tells you the balance before you confirm). Videos, photos and music tracks you have already saved into your device's own Movies, Pictures and Music folders are not affected — those are your files, and deleting an account is not a request to delete the media you made with it.

Deletion can also be requested without the app — for example after uninstalling it — at https://kl-video-splitter.web.app/delete-account, which also lists exactly what is and is not deleted.

AI features

AI captions. When you use "Generate with AI" and describe the caption you want:

• The text you type is sent to a small backend the developer operates on Google Cloud Functions. If you are continuing an existing conversation, the earlier prompts and chosen captions from that same conversation are sent along as context.
• That backend passes your text to Google's Gemini model through Google Vertex AI, which generates the caption options and returns them to the app.
• A record that the request happened — its type, outcome, credit cost and timestamps — is stored against your account. The prompt text itself and the generated captions are not stored on the developer's server; the app saves them on your device. Two things sit outside that: a caption you explicitly report, which is sent to the developer's server together with its prompt (see Reporting AI content below), and a prompt that Google's own safety checks flag (see What Google may keep, and when below).
• Your photos and videos are never sent. This feature works from your typed description alone.
• Your prompt is checked against a content filter before the request is sent, and by Google's own model safety filters when it is answered.

Google acts as a processor for this on the developer's behalf, under Google Cloud's terms. See Google's privacy policy and Google's Vertex AI documentation for how prompts sent to the model are handled by Google.

AI music. When you use "AI music" from any of the app's audio pickers and describe the track you want:

• The text you type is sent to the same backend on Google Cloud Functions. If you are continuing an existing chat, the earlier messages and the direction you picked from each are sent along as context, and so are the titles and tags of the tracks you have already generated — that last list is what lets the model offer you a track you already own instead of charging you for a near-identical second one.
• That backend passes your text to Google's Gemini model through Google Vertex AI to plan the track (and, in the "with vocals" mode, to write its lyrics), and then to Google's Lyria model to generate the audio, which is returned to the app.
• A record that the request happened — its type, outcome, credit cost and timestamps — is stored against your account, exactly as for captions. The message text, the lyrics, and the generated audio are not stored on the developer's server: the app saves the chat on your device, and the track on your device and into your device's own `Music/KLStatusMaker` folder so it shows up in your music apps. Your message is sent to Google to be answered, and Google may keep one it flags — see What Google may keep, and when below.
• Your photos, videos and your own audio files are never sent. This feature works from your typed description alone.
• Your message is checked against the same content filter as a caption prompt, before the request is sent, and the text the model writes back is checked again before you see it.
• A generated track has a "Report" action, the same one captions and generated pictures have. What it sends is the words behind the song — its title, the tags the model wrote, and, for a sung track, the lyrics it reports having actually sung — together with the message that produced it. The audio file itself never leaves your device.

AI photos. When you use the AI photo option from the app's photo pickers and describe the picture you want:

• The text you type is sent to the same backend on Google Cloud Functions. If you are continuing an existing chat, the earlier messages and the direction you picked from each are sent along as context, and so are the descriptions of the pictures you have already generated — that last list is what lets the model offer you a picture you already own instead of charging you for a near-identical second one.
• That backend passes your text to Google's Gemini model through Google Vertex AI, which plans the options you read and then generates the picture, and returns it to the app.
• Before you see it, the generated picture is checked by Google Cloud Vision, which reads the image itself and also reads any words the model drew into it. A picture that fails that check is discarded and the credits are returned.
• A record that the request happened — its type, outcome, credit cost and timestamps — is stored against your account, exactly as for the other AI tools. The message text and the generated picture are not stored on the developer's server: the app saves the chat on your device, and the picture on your device and into your device's own `Pictures/KLStatusMaker` folder so it shows up in your gallery. Your message is sent to Google to be answered, and Google may keep one it flags — see What Google may keep, and when below.
• Generating a picture from a description does not send any photo of yours. That mode works from your typed description alone: the app sends words and receives a picture, never the other way round. Two other things do send a photo of yours, both only when you choose to: restyling a photo you already have, which is the other mode of this same tool, and attaching a photo to the picture chat so it can answer questions about it. Both are described next.
• Your message is checked against the same content filter as a caption prompt, before the request is sent, and the text the model writes back is checked again before you see it.
• Google attaches its own markers to the picture recording that it was made by AI. The app saves and shares the picture exactly as it was generated, so those markers are still there in the copy in your gallery and in any copy you share. A video, collage or text status you then *make* from that picture is a new file drawn from scratch, so it does not carry them — the same as with any editor.

AI photo restyle (one of the two features that send a photo you already have). The photo editor has a restyle tab. When you open it, describe the look you want and confirm it:

• The photo you are editing is sent. It is one of two places in this app that send a photo you took — the other is attaching one to the picture chat, described below. It is sent once, when you tap the confirm button on the restyle you asked for — not while you type, not while you chat about it, and never in the background. Up to that point the feature works like every other AI chat: only text is sent.
• What is sent is the photo as it looks in the editor at that moment, resized down before it leaves the device, and nothing else about it: no filename, no location, no camera information, no date.
• It goes to the same backend the developer operates on Google Cloud Functions, which passes it to Google Cloud Vision to be checked and then to Google's Gemini model through Google Vertex AI to be restyled. The restyled picture comes back to the app.
• The developer does not retain it. The photo is held for the length of that one request and is not written to the developer's storage, and there is no copy on the developer's servers afterwards — which is also why a report about a restyle cannot include it (see Reporting AI content below). Google may keep it in the one case described under What Google may keep, and when below.
• A record that the request happened — that it was a restyle, its outcome, its credit cost and its timestamps — is stored against your account, exactly as for the other AI tools. That record does not contain the photo or anything derived from it.
• A photo may show other people. If you restyle a photo of someone else, you are the one choosing to send it, and this app cannot tell who is in a photo, whether they agreed, or how old they are — it does not try to. Nothing in the app detects faces or identifies anyone, and no restyle is ever started without you confirming it. Please only restyle photos you are entitled to send.
• The restyled picture is saved on your device and into your device's own `Pictures/KLStatusMaker` folder, exactly as a generated picture is, and the original photo on your device is not modified.

Attaching a photo to the AI picture chat (the other feature that sends a photo you already have). The picture chat lets you attach a photo of your own and ask about it:

• The photo is sent once, when you attach it — not while you type, not on every message you send afterwards, and never in the background. After that first message the conversation continues on text alone: the app keeps a short written description of what the model saw and sends that description instead of the photo.
• What is sent is the photo as you picked it, resized down before it leaves the device, and nothing else about it: no filename, no location, no camera information, no date.
• It goes to the same backend the developer operates on Google Cloud Functions, which passes it to Google Cloud Vision to be checked and then to Google's Gemini model through Google Vertex AI so it can answer you. A photo that fails the check is refused and you are not charged for it.
• The developer does not retain it. The photo is held for the length of that one request and is not written to the developer's storage, and there is no copy on the developer's servers afterwards. Google may keep it in the one case described under What Google may keep, and when below.
• The written description stays on your device, saved with that conversation. Deleting the conversation deletes it, and deleting your account deletes all of them.
• A record that the request happened — its type, outcome, credit cost and timestamps — is stored against your account, exactly as for the other AI tools. That record does not contain the photo or anything derived from it.
• A photo may show other people. The same applies here as to restyle: you are the one choosing to send it, and this app cannot tell who is in a photo, whether they agreed, or how old they are — it does not try to. Nothing in the app detects faces or identifies anyone.
• The app will not write about a person's age, health, body or attractiveness, and it treats any writing visible inside a photo as something to describe rather than as an instruction to follow.

What Google may keep, and when. Everything above describes what this app and the developer's own servers store. One thing sits outside both of those, and it is Google's rather than the developer's:

• Google runs automated safety checks over requests made to its AI services. If those checks flag a request as possibly breaking Google's Acceptable Use Policy or Prohibited Use Policy, Google may keep the prompt for that request so that someone at Google can review it. This is set out in section 4.3 of the Google Cloud Terms of Service and described on Google's abuse monitoring page.
• "The prompt" means what you sent: the text of your message, and — for the two features that send a photo — the photo itself.
• Google states that a request kept this way is held for up to 90 days, is stored in the same region or multi-region as the rest of the project, is not used to train or fine-tune any AI model, and is not encrypted with customer-managed keys.
• It is conditional: it applies to a request Google's checks flag, not to every request. Neither this app nor the developer chooses which requests are flagged; Google may contact the developer about one.
• It does not change what this app stores. The developer's servers still keep no message text and no photo, and the app still keeps your conversations on your device.

Reporting AI content. Every caption, every picture and every music track the app generates has a "Report" action next to it. If any of them is offensive or wrong, you can send it to the developer for review without leaving the app.

• Only what you explicitly report is sent. Nothing is uploaded automatically, and anything you do not report stays on your device as described above.
• A report contains the text being reported, the prompt that produced it, the reason you selected, any note you write, and your user ID. For a caption, the text being reported is the caption; for a picture it is the description the model wrote for that picture, and for a music track it is the words behind the song — its title, the tags, and, for a sung track, the lyrics the model reports having actually sung, which is not always word for word what it was asked to sing. Neither the picture nor the audio is ever sent — both stay on your device, and the words they were made from are what the review needs. The prompt is included because it is the only way to see how the output came about — the server does not otherwise keep it.
• Reports are used to review generated content and improve the app's filtering. They are not shown to other users, and no other user can see them.
• Reports are kept after you delete your account, with your user ID removed. They are records about generated content rather than about you, and a report has to remain readable for the review it exists for. What is erased is the link between the report and you. See Accessing and deleting your account data above.
• Reporting is free, does not use AI credits, and works regardless of your credit balance.

Cutout (on your device). The photo editor's Cutout tab — background blur, background replace and auto-crop — runs entirely on your device using Google's ML Kit, needs no account, and sends no image anywhere. It is named for what it does rather than called AI, precisely so that one word does not cover both this free, offline pass and the paid, signed-in tools above. Note the distinction it draws: the AI tools above need an account and send what you type to a server, and this one does neither.

Legal basis for processing

If you are in the European Economic Area or UK, the legal basis for each type of processing described in this policy is:

• Analytics — your consent, given (and withdrawable at any time) via the "Analytics" switch in the app's Settings screen.
• Crash reporting — our legitimate interest in keeping the app working correctly and fixing bugs, since this data is limited to technical crash/error diagnostics needed to operate the service. You can still turn it off at any time via the "Crash reporting" switch in Settings, even though consent isn't the legal basis for it.
• Advertising — not applicable. The app shows no ads, runs no ad SDK, and asks for no advertising consent.
• Subscriptions and AI credit purchases — performance of the contract formed when you choose to subscribe or buy a credit pack.
• Your account and the AI tools — performance of the contract you enter into when you choose to sign in and use them. You are never required to sign in to use the rest of the app, so this processing only happens if you ask for it.
• Content filtering of AI prompts, and of the images the AI tools produce or are sent — our legitimate interest in preventing misuse of a paid, third-party AI service, and in meeting the content rules the app is subject to on Google Play.
• Reports you file about AI content — our legitimate interest in reviewing what the app's AI produces and improving the filtering around it, and in meeting Google Play's requirement that apps generating content with AI let users flag it from inside the app. This only happens when you choose to send a report.

Data retention

Your videos, audio files and typed status text have no server-side retention period at all, because they are never uploaded (see "What the app does" above). Your photos are the same with two exceptions, and each is a retention statement rather than an absence: a photo you send to the AI photo restyle tool, and a photo you attach to the AI picture chat, are each held for the length of that one request, are not written to the developer's storage, and are gone from it when the request ends. The same is true of your AI caption conversations, your AI music chats, your AI photo chats, and the AI music tracks and generated pictures in the app's own libraries, all of which the app keeps on your device and the developer's servers do not store, and which are removed when you delete them or when you delete your account. What you send to Google — the text of your messages, and those two photos — is subject to one Google-side retention period, described under What Google may keep, and when in AI features above. Note that Android's own backup and device-transfer features, if you have them switched on, may copy this app's data - including these chats and the files they point at - into your own Google account, the same as for other apps on your phone; that copy is yours and is governed by Google's backup settings rather than by this app, and it is why uninstalling is not by itself a guarantee that nothing remains. Content you report is the exception: it is stored on the server, and is retained after account deletion with your user ID removed, as described under AI features.

If you use the AI features, the account data listed under "Data we collect" is kept for as long as your account exists, and is deleted as soon as you delete your account. Two kinds of record survive that deletion by design, and your account identifier is erased from both, so neither identifies you or anyone else afterwards:

• For each AI credit purchase, the fact that a particular Google Play purchase token was redeemed — for which product, for how many credits, and when — is kept so that the same purchase can never be redeemed twice.
• Any report you filed about AI content is kept so it can still be reviewed and inform the app's content filtering, as described under AI features above.

Data collected by Google's SDKs (Analytics, Crashlytics, Play Billing) is retained according to Google's own default retention periods for those products, not a KL-Status-Maker-specific policy. See Google's privacy policy for its current retention windows.

International data transfers

The Google services this app uses (Firebase Analytics, Firebase Crashlytics, Play Billing) may process your data on servers located outside your country, including in the United States. Google provides safeguards for these transfers, such as Standard Contractual Clauses and, where applicable, certification under the EU-U.S. Data Privacy Framework. See Google's privacy policy for details of the safeguards Google applies.

If you use the AI features, the same applies to the developer's own backend. Your account data and any AI content you report are stored in Google Cloud's us-central1 region in the United States, using Firebase Authentication, Cloud Firestore and Cloud Functions. Any photo you send to be restyled, or attach to the AI picture chat, is processed there too. The text you write to the AI — your prompts and chat messages — and any music generated with vocals are processed by Vertex AI through its multi-region global endpoint, which Google may serve from any region where the model is available rather than from a single named one. So account data, AI prompts, any photo you choose to restyle or to attach to the picture chat, and any AI content you report are transferred outside your country, including to the United States, even if you are elsewhere.

Analytics

KL Status Maker uses Google Firebase Analytics to understand how the app is used (for example, which screens and features are opened, and how often). Firebase Analytics may collect device identifiers, app usage/interaction data, and general device information (such as device model and operating system version). This data is processed by Google and is not linked to your name, email, or other personal information. You can review how Google handles this data through Google's own privacy policy.

Analytics collection is on by default and can be turned off (or back on) at any time from an "Analytics" switch in the app's Settings screen.

Crash Reporting

KL Status Maker uses Google Firebase Crashlytics to receive crash and error reports so problems can be diagnosed and fixed. When the app crashes or encounters certain errors, Crashlytics collects technical diagnostic information — such as a stack trace, the device model, operating system version, and app version — and an anonymous installation identifier used to group reports from the same device. This data is processed by Google and is not linked to your name, email, or other personal information. Crash reporting is on by default and can be turned off (or back on) separately from Analytics, from a "Crash reporting" switch in the app's Settings screen, since it is limited to crash/error diagnostics rather than general usage tracking.

Advertising

KL Status Maker shows no ads. There are no banner ads, no full-screen interstitial ads, and no sponsored content anywhere in the app. Nothing in the app collects or transmits your device's advertising identifier, and no ad network receives any data about you from it.

Because there are no ads, there is no ad-personalization consent to give or withdraw: the app never shows Google's User Messaging Platform consent form, and the "Ad privacy choices" option that earlier versions placed under "Privacy & Data" in Settings is gone.

Earlier versions of the app did display banner and interstitial ads served by Google AdMob. For that reason the Google AdMob library is still present inside the app package, but it is never started, makes no network request, and reads no identifier. Ads would only return in a future version of the app, and this policy would be updated before that version was published.

Subscriptions and purchases

KL Status Maker offers two optional purchases, both processed entirely through Google Play Billing: an auto-renewing support subscription (weekly, monthly, 4-month, 6-month, or yearly plans), which removes the short branded ending added to exported videos and the small watermark added to exported photos, and one-off AI credit packs for the AI features. Payment details (card numbers, billing address, etc.) are handled by Google Play and are never seen by or transmitted to KL Status Maker.

For the subscription, the app only receives a purchase confirmation (product ID and purchase token) from Google Play, which it uses on your device to turn off the branded ending and the watermark for as long as the subscription stays active. That confirmation is not sent anywhere else. You can manage or cancel your subscription at any time through Google Play's own subscription management.

For AI credit packs, the purchase token is additionally sent to the developer's backend, which verifies it with Google Play and then adds the credits to your account's balance. That is why a record of the purchase (product, credits granted, redemption time) is stored against your account, as listed under "Data we collect".

Both purchases are optional — the app is fully usable and ad-free without either, and credits are only used for the AI features. See Google's own privacy policy for how Google Play handles your payment information.

Permissions the app uses, and why

Sharing your videos

If you choose to share a split video (for example, to WhatsApp) using the app's built-in share option, that file is handed off directly to the app you selected via Android's standard share mechanism. KL Status Maker itself does not upload the file anywhere or have access to what happens after the target app receives it.

Third parties

KL Status Maker uses Google Firebase Analytics, as described in the Analytics section above, Google Firebase Crashlytics, as described in the Crash Reporting section above, Google Play Billing to process the optional subscription and AI credit packs, as described above, and Google's on-device ML Kit for the photo editor's AI options, which sends nothing off your device. It uses no advertising network — see Advertising above.

If you use the AI tools, the app additionally uses Google Firebase Authentication (sign-in), Google Cloud Firestore (your credit balance, your AI request history and any AI content you report), Google Cloud Functions (the developer's own backend), Google Vertex AI (generating the captions, the music and the pictures), Google Cloud Vision (checking a generated picture before you see it, and checking a photo you send to be restyled before it is used), Firebase App Check with the Google Play Integrity API (verifying that requests come from a genuine installation of this app rather than a copy or a script), and the Google Play Developer API (verifying credit purchases). All of these are Google services acting as processors on the developer's behalf.

The app does not use any other third-party analytics, advertising, or data-collection services.

Children's privacy

KL Status Maker is not directed at children and does not knowingly collect data from them. The AI features require signing in with a Google account, which is subject to Google's own minimum-age requirements for the country the account is in; every other feature requires no account and collects no personal information. The app shows no ads, so no advertising is directed at anyone using it, of any age. The app's restyle tool can send a photo you pick, and it neither detects faces nor identifies anyone in one — see AI photo restyle above for what that means and does not mean. If you believe a child has created an account in this app, contact us using the details below and it will be deleted.

Your rights

These rights apply to two different sets of data, and how you exercise them differs:

• Your account data, if you have signed in to use the AI features — your Google account identifier and email address, your credit balance, your AI request and purchase history, and any AI content you have reported. This is directly identifying data held by the developer, and the app gives you direct controls for the two rights most likely to matter: Settings → Account → Export covers access and portability, and Settings → Account → Delete covers erasure. For anything else, contact us using the details below.
• Pseudonymous, device-level data (such as installation identifiers) processed by Google's SDKs — Analytics, Crashlytics and Play Billing. This is processed by Google, so these rights are exercised with Google; for Analytics and Crash reporting specifically, the switches in this app's Settings screen turn the collection off directly.

Your videos, audio files and typed status text are not covered below, for a simple reason: they never leave your device, so there is no request to make of anyone. Your AI conversations and the two photos you can send — one to be restyled, one attached to the picture chat — are different. The app keeps them on your device and the developer stores no copy, so there is nothing held here to access, correct or erase; but they are sent to Google to be answered, and Google may keep one that its safety checks flag (see What Google may keep, and when above). For that copy the request is Google's to answer rather than the developer's, and Google's privacy policy explains how to make it. Content you have reported is the one thing from that set that the developer does hold, and it is covered — it appears in your export, and account deletion removes your user ID from it.

Depending on where you live, you may have the right to:

• Access the data held about you — for account data, use Settings → Account → Export.
• Rectify inaccurate data.
• Erase your data ("right to be forgotten") — for account data, use Settings → Account → Delete, or the web page at https://kl-video-splitter.web.app/delete-account. Reports you filed about AI content are the one exception: rather than being deleted they are kept with your user ID removed, for the reasons given under AI features above.
• Restrict or object to processing — for Crash reporting, whose legal basis is our legitimate interest rather than consent (see "Legal basis for processing" above), use the "Crash reporting" switch in this app's Settings screen to object.
• Data portability — receive your data in a portable format. Settings → Account → Export produces exactly that: a single JSON file you keep.
• Withdraw consent at any time, with no effect on processing already carried out — for Analytics, use the switch in this app's Settings screen. There is no advertising consent to withdraw, since the app shows no ads.
• Lodge a complaint with your local data protection supervisory authority if you believe your data has been mishandled.

To exercise any of these rights for data processed by KL Status Maker directly — which, unless you have signed in for the AI features, is nothing at all (see "Data we collect" above) — use the in-app controls described above where they exist, or contact us using the details below. For data processed by Google's SDKs, see Google's own privacy policy for how to exercise these rights with Google.

Changes to this policy

If this policy changes, the updated version will be posted at this same URL with a revised "Last updated" date.

Contact

Questions about this policy can be sent to: georgekomen91@gmail.com