Last updated: October 17, 2026
This policy covers the mobile app Knock (package identifier
com.lcsoftwaresolutions.knock) on iOS and Android, published by
Naeim Salib ("we", "us"). Contact:
Accounts@lcsoftwaresolutions.com.
Knock asks for your birth month and year once, the first time it opens, so it can set up the right version for you. It keeps only the result (under 13, 13 to 17, or 18 and over) on your device, and it does not save, log or send the month or year you choose. Players under 13 get a protected version: no ads, no real-money purchases, no leaderboard, no sign-in, no feedback form. Knock does not start those online features for this age group. Third-party software may perform load-time activity before the age answer, as described under “Advertising”. Players 13 to 17 see no ads either. Ads are shown only to players who say they are 18 or over. See “Children’s privacy” and “Advertising” below. The rest of this short version describes the game for players 13 and older.
Knock is a puzzle game that plays offline, with two online features: a daily and all-time score list, and an optional account that saves your progress (below). For players 13 and older, taking part in the score list is automatic. The first time you open the app with a connection, our server creates an anonymous player profile for this installation, and every time after that the app tells the server you were present that day. Unless you sign in, your game progress, coins and purchases stay on your device. What reaches our server is a randomly generated player number, a public display name (random at first, yours if you change it), an avatar number, your scores and the points from your plays, and the dates involved. Taking part needs no account, password or sign-in, and we do not ask who you are. Settings → About & Legal → "Privacy & Data" → "Delete online data" erases that profile from our server. Afterwards the app does not create a new one unless you turn the leaderboard back on yourself.
Signing in is optional, and it is for one thing: saving your progress to an account so it comes back after a reinstall or on another device. If you choose the account button on the Home screen → Continue with Google / Sign in with Apple, the app uploads your game save (level, unfinished board, coins, helpers, awards, streak, your Ranks name and buddy) to our server under that account, and keeps it up to date while you play. We receive from Google or Apple only an account identifier (a random string Firebase Authentication assigns); we do not store your email address, name or photo. See “Optional account and cloud save” below. If you never sign in, nothing in this paragraph applies and your progress stays only on your device.
For players 18 and over, Knock shows ads supplied by Google AdMob. There is a banner on the Tasks and Awards screens, an occasional full-screen ad between puzzles, and an optional video you can choose to watch for one extra undo or hint. Google’s advertising software in the app collects data from your device itself, which may include an advertising identifier, to deliver and measure those ads. That data goes to Google, not to us, and is not joined to your player profile. Where the law requires it you are asked first, and on iPhone and iPad the system asks whether Knock may track you. See “Advertising” below. Nothing in the game is locked behind an ad.
On iOS, optional in-app purchases are handled by Apple. Purchases on Android, in versions of the app that offer them, are handled by Google Play. Knock never receives your payment details. It keeps a record of delivered purchases on your device; if you sign in, that record is also part of your cloud save.
For players 13 and older, taking part starts automatically after the age question is answered. No separate leaderboard sign-up is needed. The first time an eligible player opens the game with a working connection, our server creates an anonymous player profile: it generates a random player number and a random display name and sends them back. Each time you open the game after that (a cold start, or bringing it back to the foreground, at most once a minute) the app tells our server you were present for that day, and sends your scores and play records as you earn them. No name, email address, account or identifier belonging to your device is involved. If you would rather not be on the list, Settings → About & Legal → "Privacy & Data" → "Delete online data" erases the profile, and the game carries on exactly as before.
| What | What it is | Why we have it |
|---|---|---|
| Player number | A random identifier (a UUID) generated by our server. It is not derived from your device, your hardware, your phone number, or anything about you. It is kept on your device and sent with each request. | It is the only thing that connects your scores to each other, so your standing persists between sessions and so you can delete your own data. |
| Display name | 3–12 letters and digits. Our server picks a random one for you; you may change it. Spaces, punctuation and other characters are not accepted. | So the score list can show something other than a number. It is public to anyone who views the list. |
| Avatar number | A whole number from 0 to 11. The picture itself is drawn by the app on your device; the server only stores the number. | So your row on the list looks like yours. Also public. |
| Profile frame | The name of one of a few decorative frames you can pick for your row. | So your row on the list looks like yours. Also public. |
| Daily score and its date | Your best score for one calendar day, together with that day. The date is the calendar day where you are, not ours. | To rank today's list. Only your best score for a day is kept — a later, worse run never replaces a better one. |
| Play records | One record per scored play: your player number, your local calendar day, the mode it came from (a challenge, the daily board, or main mode), an identifier for the board, level number or date, and the time we received it. The points from each play are added to one running total for that day. | To work out today’s points total, and to make sure the same play is never counted twice if the app has to resend it. |
| Daily participation | Your player number, a date, and the time that row was first written. The date is our server's own date, in UTC; your device does not send one. It records that the app reached us on that date. There is one row per day at most, however many times you open the app. | So we can tell how many people took part in a given day, and in what order they arrived. |
| Lifetime total | A single running total of points you have scored. | To rank the all-time list. |
| Rate-limiting counters | A timestamp and a small counter, stored on your own player record. | To stop one device from flooding the service. They are deleted with the rest of your record. |
That table is exhaustive for the score list. Three other things also reach a server of ours or a service we use: a launch check (next paragraph), the in-app feedback form (described in its own section), and Google’s advertising software (described under “Advertising”).
Launch check. For players 13 and older, after the age question is answered, each launch makes one request to our server asking whether a newer version of the app is required. The request carries no player number or any other data about you; like every internet request it reveals your IP address to the server’s hosting provider. The app makes this request whether or not you are on the score list, including after you have deleted your online data.
The two dates in that table are deliberately different, and it is worth saying which is which. Your score and your play records are stamped with the calendar day where you are, because "today's board" means the day on your own wall. Your participation is stamped with our server's date, in UTC, and your device does not send a date for it at all. That difference is on purpose: a score is something you earned, so your own clock is the right one to trust; participation is recorded with no action from you, so it must not rest on a device clock nobody checked.
This is the one place Knock asks you to type anything about yourself, and it only happens if you choose to use it. Settings → Help & Support → Send feedback opens a form with three fields. Nothing is sent unless you fill it in and press Send.
| What | What it is | Why we have it |
|---|---|---|
| Your name | Up to 40 characters, whatever you type. It does not have to be your real name. | So a reply can address you. |
| Reply email | The address you type, up to 254 characters. We do not verify it and we do not check it against anything. | So we can answer you. It is the only reason we ask. |
| Your message | Up to 2,000 characters of free text. | It is the feedback. |
Your message is sent over HTTPS to our server, which forwards it as an email to Accounts@lcsoftwaresolutions.com. The message itself is not stored in our database. Our server’s log notes only that a message arrived and how long each field was, never what it said. We do not add your player number, your scores, your device details or any diagnostics to it — the three fields above are the entire contents. If the message cannot be delivered the app tells you so. If the form reports a delivery failure, please write to Accounts@lcsoftwaresolutions.com instead. Your address is used to reply to you and for nothing else: it is never added to a mailing list, never used for marketing, and never shared.
We keep feedback email for as long as it takes to deal with it, and you can ask us to delete it sooner at the same address.
Because this is a message you send us rather than a record attached to your player profile, "Delete online data" does not remove it. To have an email deleted, reply to it or write to Accounts@lcsoftwaresolutions.com and ask.
Outside the age question, optional sign-in and feedback form described in this policy, Knock does not ask for your name, email address, phone number, date of birth, location, contacts, photos, calendar, microphone, camera, or health data, and the app requests none of those permissions. The only permissions Knock itself ever asks your phone for are the iOS tracking permission (so Google’s ads can be personalised, see “Advertising”) and, only if you turn on reminders, the permission to show notifications. Nothing you type into the feedback form is attached to your player profile or your scores.
Knock’s own code does not read or store any hardware or advertising identifier. Neither Apple’s IDFA or identifierForVendor, Android’s Advertising ID, the IMEI, MAC address nor serial number is written to our database or attached to your player profile or your scores. We do not build a device fingerprint. Knock itself holds no password for you: if you sign in, Google or Apple authenticate you and hand the app a short-lived token, which the app sends only to our save service to prove who is asking and never stores in your save, our database or any log.
Our advertising provider is a separate matter, and it is described in “Advertising” below. Google’s advertising software runs inside the app and collects data from your device itself, subject to the choices described there and to your device settings. That data goes to Google, not to us. Saying “Knock’s own code reads no advertising identifier” without this paragraph beside it would be true of our code and misleading about your phone.
We do not store your IP address. As with any internet service, your device's IP address is necessarily visible to our hosting provider, Cloudflare, in order to deliver the request. Our server uses it at Cloudflare’s network edge, through Cloudflare’s rate-limiting feature, to limit how many new players, and how many feedback messages, one connection can create in a minute. Our code does not write the address to our database. Cloudflare may keep routine operational logs under its own terms (see “How long we keep it”).
Everything that makes up your progress is stored locally, using your browser/WebView's standard local storage, and — unless you sign in, see the next section — is not uploaded:
If you uninstall the app, this local data is deleted with it. On Android, the operating system's own backup feature may include app-local data in your general phone backup — standard Android behaviour under your control in system settings, not something Knock initiates.
Uninstalling does not delete your profile from our server, because that lives on the server. Use "Delete online data" first — see below.
Added October 3, 2026. Nothing here happens unless you sign in. The account button on the Home screen opens a small sign-in panel offering Continue with Google and Sign in with Apple, through Firebase Authentication (a Google service). If you do:
Knock is built to work with no connection at all. Every board, every point and every setting works identically in airplane mode; the score list simply says it is offline. Nothing in the game waits on the network, and nothing about the game changes when it is missing.
If you finish a board while offline, the score and play record are held on your device and sent the next time the app runs with a working connection — which may be days later. A score sent late still carries the date you actually earned it, so it is ranked against the correct day rather than the day it happened to arrive. The same applies to a name change or a deletion request made while offline.
Participation is the one thing that is not backdated. If the app could not reach us when you opened it, the record that you were present is sent when it next can, and it lands on the day it reaches us rather than the day you played. We have no way to check a claim about a past day, so we do not make one.
The score service runs on Cloudflare (Cloudflare, Inc.), which provides the computing and database infrastructure as our processor and does not use the data for its own purposes. The database is located in North America. Cloudflare also handles the network connection itself, which necessarily includes your IP address as described above.
Google (Google Ireland Limited / Google LLC) supplies the advertisements and the consent form described under “Advertising” below. Google does not receive your player number, your display name or your scores from us, and it is not a processor of the score-list data described in this section — it is an independent controller of the separate advertising data its own software collects on your device. The two are not joined by us.
Apple (on iOS) and Google Play (on Android, where purchases are offered) handle payment for in-app purchases under their own terms. We do not receive your payment details or the store’s receipts. If you sign in, your cloud save includes the record of purchases already delivered, described under “In-app purchases” below.
Google also provides Firebase Authentication, which handles sign-in if you choose to sign in, as our service provider. It does not receive your scores or your game save.
No other third party receives any of it. We do not sell your personal information, and we do not share your score-list data for advertising or marketing. Knock’s own server does not combine your data with data from other apps or websites. Google’s advertising software, however, can use an advertising identifier, where you have permitted it, to personalise and measure ads across apps — which is why the iOS tracking permission exists, and why that is described in its own section, with the controls for switching it off.
Your player profile, scores, play records and participation dates are kept for as long as you leave them there, so that your all-time standing continues to mean something — there is no automatic expiry. You can remove all of it at any moment, and when you do the rows are deleted from our database rather than being archived or flagged.
Two things outside our own tables are worth being plain about. Cloudflare’s database service keeps automatic point-in-time recovery data, for up to 7 days on its free plan and up to 30 days on its paid plan, so a deleted row can persist in that recovery data until it ages out; we do not use it to restore deleted profiles. And routine operational logs produced by our hosting provider — the ordinary record of requests reaching the service, used for debugging and abuse prevention — are not used to build any profile of you. Feedback email is covered in its own section.
In the app: Settings → About & Legal → "Privacy & Data" → "Delete online data". It asks you to confirm, and tells you plainly that your leaderboard profile is deleted from the server while your levels, coins, items and purchases stay on your device. This erases your player record and everything attached to it: your player number, display name and avatar, daily scores, play records and points totals, lifetime total, and the record of which days you were present.
The local half takes effect immediately: your device stops uploading at once, and any scores still waiting to be sent are discarded rather than sent. If you are offline when you ask, the deletion is kept as pending — the app says so rather than claiming it is done — and it is sent as soon as a connection is available. We do not report the deletion as complete until the server confirms it.
Afterwards the app does not put you back. Once a deletion is confirmed, opening the game creates no new profile, sends no leaderboard data and enrols you in nothing. The only request it still makes is the anonymous launch check described above. A separate control — "Turn the leaderboard back on", in the same Privacy & Data panel — is the only way back, and it starts a brand-new profile with a new player number, unrelated to the old one. It restores nothing: what was deleted is gone. Your local game progress, coins, purchases and settings are not affected; to clear those, use Settings → "Reset progress", or uninstall the app.
The same panel has "Request deletion on the web", which opens https://privacy.lcsoftwaresolutions.com/knock/delete-data. That page sets out the same deletion and the ways to ask for it, including for somebody who has already uninstalled the app and can no longer reach the in-app control. If you uninstall before asking, the profile stays on the server, because only the app knows your player number — and, if you signed in, your cloud save, which brings it back when you reinstall and sign in. A display name, avatar and scores are public, so they cannot show that a profile is yours, and we do not delete a guest profile based only on its public name, avatar or scores. Account deletion by email is not offered. To delete a signed-in account, use the in-app steps described above. The deletion page explains this, and how a name that breaks the name rules is reported instead. We hold no email address or other contact detail for a player.
Your display name appears on a public list. Please do not put anything in it you would not want shown to strangers — a real name, a contact detail, or anything offensive. Names are limited to 3–12 letters and digits, and names matching a blocklist are rejected when you try to set them. These limits do not prevent a real name or a phone number written as digits, so please do not include personal or contact information.
If you see a name that should not be there, use "Report a name" on the Leaderboard screen, or write to Accounts@lcsoftwaresolutions.com. We review every report. A name that breaks these rules is replaced with a neutral one.
Where available, Settings offers a separate Share level progress switch, off by default and unavailable to children under 13. With your opt-in, Knock sends level starts, resumes, finishes, explicit restarts/give-ups, helper use, rewarded-ad presentations and earned assist rewards. Records contain a random installation identifier, separate random attempt identifiers, puzzle version, mode, level, app build, event time and solve duration. They do not contain your name, account identifier, email, age, saved board, purchase details or ad value. They help us understand progression; they do not change your puzzle difficulty.
Measurement uses a separate Cloudflare service. The installation credential is hashed with a server secret before storage. Raw events are removed after 90 days by daily cleanup (allowing up to one further day for that cleanup). Turning the switch off clears unsent events and requests deletion of that installation’s shared events when a connection is available. A non-reversible revocation digest is kept to discard delayed uploads. Delete online data/account deletion on this device also turns this measurement off and requests its deletion. Uninstalling before requesting deletion removes the device’s deletion credential; already shared events then expire under the retention policy.
Cloudflare's database service keeps automatic point-in-time recovery data, for up to 7 days on its free plan and up to 30 days on its paid plan, so an event deleted by you or by cleanup can persist in that recovery data until it ages out; we do not use it to restore deleted measurements. The measurement service stores no IP address, but a request necessarily reaches Cloudflare, which sees the sender's IP address to deliver it and to apply a rate limit, and keeps routine infrastructure records. The service keeps no log of requests of its own.
Measurement is available only in app builds that include this switch and a configured measurement service. Builds without them send no level progress.
Knock includes an optional, on-device diagnostics tool (Settings → Help & Support → Send diagnostics). It is entirely opt-in and manual:
Knock shows advertisements supplied by Google AdMob. The Google Mobile Ads SDK and Google’s User Messaging Platform (the consent form) are included in the app, and they are the only advertising components in it. Three AdMob ad formats may appear — banner, interstitial and rewarded — and each is described below in the place it is shown.
One thing the age question cannot prevent: on iPhone and iPad, software from Google that is built into the app may, when the app opens and before you answer, create a small settings file on the device and check whether the device can reach Google. A network reachability check can reveal the device’s IP address to network services. Knock does not request ads or start its consent or tracking flows for anyone under 18. On Android, linked platform and third-party components can also perform startup work before the age answer. These load-time activities are separate from the age-gated features.
Watching an ad can never change your score or your leaderboard position. Undos and hints do not affect the score a board pays, so nothing you can get from an advertisement moves you up the list.
When an ad is requested, Google receives information from your device in order to select, deliver, measure and report on that ad. According to Google’s own disclosures, that can include an advertising identifier (Apple’s IDFA or Android’s Advertising ID) and other device identifiers, your IP address and the approximate location derived from it, how you interact with ads and the app (for example launches, taps and video views), and diagnostic information such as launch time and crashes. Google may use this to limit how often you see the same ad, to measure whether an ad led to an install, to prevent fraud, and — where you have permitted it — to show you personalised ads.
Google is an independent controller of the data it collects this way. We do not receive it, we cannot see it, and we do not join it to your player number, your display name or your scores. What Google does with it is governed by Google’s own privacy policy, at policies.google.com/privacy, and by policies.google.com/technologies/partner-sites, which describes how data is used when you use a partner’s app.
Knock itself asks for the iOS tracking permission, and shows Google’s consent form where required. It sees only whether an ad may be requested, not the details of your answer.
On Android, Google Play Billing may send diagnostic events to Google, including the app package and version, billing-library version, device model and operating-system build information, language and country settings, network type, and billing errors. Events may be queued on the device and sent later. This diagnostic traffic is separate from the purchase records in your optional cloud save.
Knock offers optional in-app purchases: packs of coins, the removal of forced ads, and bundles. Coins are an in-game currency with no cash value, and they can also be earned by playing. On iOS every purchase is handled by Apple through StoreKit. On Android, where the version of the app you have offers purchases, they are handled by Google Play. Knock never sees or stores your payment details, and it never keeps the store’s receipts. So that the same purchase is not delivered again, Knock records on your device the store’s transaction number, the product and the time of each purchase it has delivered. Restore Purchases asks the store, not this record, what you own. If you sign in, this record is part of your cloud save on our server (see “Optional account and cloud save”), together with a list of those transaction numbers (a long one, such as Google Play's, is kept as a one-way digest) kept so a delivered purchase is not delivered again on another device; deleting the account deletes both. Purchase information is never sent to the score service.
If you turn on reminders in Settings, Knock asks your phone for permission to show notifications and then schedules at most one a day, at around 7 PM, when you have not yet completed that day's Calendar. These are local notifications: your phone creates and delivers them, no information about them is sent to us or to anyone else, and turning the setting off in Knock cancels any that are waiting.
Everything sent to the score service travels over HTTPS. Your player number is the only credential the service has, it is stored on your own device, and it is never shown on the score list — the list carries display names and avatars only.
We should be straightforward about the limits: because scores are calculated by the game on your device, we cannot fully prove a submitted score was genuinely earned. The service refuses impossible scores, keeps only one best score per player per day, and limits how fast requests can arrive, but a determined person could still post a score they did not earn. This affects the accuracy of a leaderboard, not the safety of your data.
The linked Firebase Crashlytics SDK has automatic collection disabled. This launch configuration does not send automatic crash reports.
Knock is made for children, teens and adults. It is not an app for babies, toddlers or pre-school children, and it is not listed in Apple's Kids Category. This is how Knock treats players of different ages.
How Knock knows. The first time Knock opens, it asks for a birth month and year. It works out an age group from the answer, taking the youngest age that fits, and keeps only the group on your device: under 13, 13 to 17, or 18 and over. The month and year are not stored, written to any log or sent anywhere. The group is not part of your game save or your cloud save, and it cannot be changed from inside the app; deleting the app and installing it again asks again.
Under 13. Knock runs in a protected mode:
Reminder notifications, if the player turns them on, are scheduled on the device and send nothing.
13 to 17. The leaderboard, optional sign-in and cloud save, in-app purchases and the feedback form are available. There are no ads and no rewarded videos, as described under “Advertising”. Purchases are made through Apple or Google, and their family controls (such as Ask to Buy) apply.
18 and over. Everything in this policy applies as written.
Parents and guardians. If you believe information about a child reached us (for example from a copy of Knock used before this age screen existed), write to Accounts@lcsoftwaresolutions.com and we will delete it; the in-app Delete online data control is also available in every mode.
No account or email address is needed to play (the app asks for a birth month and year once, as described above); signing in is optional and exists only to save progress. There is no chat or messaging between players: the only text a player can show to others is the display name, and the only free text a player can type to us is the optional feedback form, which goes privately to us. A player aged 13 or over is put on the leaderboard by opening the game rather than by choosing to, which is why this policy says so plainly and why the deletion control is in Settings from the first launch. If you believe a child has set a display name you would like removed, write to Accounts@lcsoftwaresolutions.com or use "Report a name": a name that is a real name or a contact detail breaks the name rules, and we replace it with a neutral one. Deleting the profile itself is done in the app, as described above, because only the app holds its player number.
Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal information, or to object to its processing. In Knock's case deletion is built into the app: uploading stops the moment you ask, and the server-side erasure completes immediately if you are online or as soon as you reconnect if you are not — we do not report it as done until the server confirms it. Correction of the only editable field — your display name — is likewise a setting you control. For anything else, write to Accounts@lcsoftwaresolutions.com.
What this policy no longer says, and why. Until August 30, 2026 this paragraph said we relied on your consent, given by tapping "Join Leaderboard". There is no such tap in the app any more, so that description is withdrawn rather than reworded — we are not going to call something consent that you were never asked for. What we do instead is set out the processing plainly: what is sent, when it is sent, what it is for, and who runs the service, all of it above. Ending it is a single control: Settings → About & Legal → "Privacy & Data" → "Delete online data" stops uploading immediately and deletes the profile from the server, with no reason required and nothing asked in return. It never touches your local game progress, and afterwards no leaderboard data is sent again unless you turn the leaderboard back on. (If you have also signed in, your cloud save keeps syncing until you sign out or delete that account.)
The October 15, 2026 revision clarifies Google Play Billing diagnostics, the production service used by test builds, the current limits of email deletion, and the fallback when feedback delivery fails. The dated notes below describe earlier revisions; the current deletion instructions are on the deletion page.
We may update this policy as the app changes. We will update the "Last updated" date above, and material changes will also be reflected in the app's Data Safety (Google Play) and Privacy Nutrition Label (App Store) disclosures.
The revision dated September 8, 2026 added the “Advertising” section, when Google AdMob was integrated. The revision dated October 1, 2026 added the in-app purchases and reminder notifications sections. The revision dated October 2, 2026 corrected the policy to match the app: it adds the per-play records and the launch check to what we collect, describes the feedback form and the Google advertising and consent software more exactly, states that the app asks for the iOS tracking permission itself, removes the earlier statements that Knock has no in-app purchases and no in-game currency, that nothing at all is sent after a deletion, and that there is no free text anywhere in the app, and corrects the path to the deletion control. The revision dated October 3, 2026 adds the optional account and cloud save (Firebase Authentication, the save service, what is and is not stored, the status line, restoring, and the separate “Delete account & cloud save” control), and reworded the statements that there is no account or sign-in to say that taking part in the leaderboard needs none. The revision dated October 4, 2026 removes the routine save status line (the app no longer shows one), states that keeping one of two conflicting saves discards the other entirely, that progress not yet uploaded is lost if the app is uninstalled, that out-of-date versions may be asked to update before they can save, and describes the deletion steps (confirmation with Apple or Google, revocation of Sign in with Apple, and how a partly finished deletion is reported and finished). The revision dated October 5, 2026 says where to remove Knock from an Apple account on Android (account.apple.com) and that a deletion whose outcome could not be confirmed is finished the same way, with the same button. It also says Knock has two online features (the score list and the optional account), that a cloud save records the transaction number, product and time of each purchase already delivered to it, and it separates leaderboard deletion from account deletion on the deletion page. An emailed request cannot delete or change a leaderboard profile, because nothing but the app’s player number (restored with a cloud save) shows that a profile is yours; a name that breaks the name rules is handled as a moderation report. Statements about what is sent after a leaderboard deletion are limited to leaderboard data. The in-app purchases passages no longer say purchase information stays on the device: for a signed-in player the record of delivered purchases is part of the cloud save, receipts are never kept, and Restore Purchases asks the store. The revision dated October 8, 2026 adds the public profile frame, the installation number and app version stored with a cloud save, the details Firebase Authentication holds, Firebase as a service provider, how long the account deletion record is kept, and says plainly that an email alone deletes neither an account nor a leaderboard profile: we cannot yet confirm by email that an account is yours, so an emailed request is answered with the in-app steps. It also says that the in-app feedback form is not yet connected to an email service. It also says that Delete account & cloud save deletes the leaderboard profile saved with the account. It also lists the app version and the record of ad steps that the optional diagnostics report contains. The revision dated October 13, 2026 adds the age screen, the protected mode for players under 13 and the rules for players 13 to 17, and rewrites the children’s privacy and advertising passages to match.
Questions about this policy or Knock's privacy practices can be sent to Accounts@lcsoftwaresolutions.com. A support page is at https://privacy.lcsoftwaresolutions.com/knock/support.