1. Who we are
LK Go, LK Up, LK On and this website are operated under the LineKeeper product name (the "we", "us" or "operator" in this policy). You can reach us any time through the contact form on this website.
2. LK Go and LK On are local-only by design
LK Go connects your phone directly to your PLC over your own local network — Allen-Bradley controllers over EtherNet/IP, Siemens S7 controllers over S7comm, and Modbus TCP devices — using the same protocols an HMI uses. There is no LineKeeper cloud, no account to create, and no server between your phone and the PLC.
Everything you configure — controller IP addresses, tag lists and values, dashboard and operator-panel layouts, and machine profiles — is stored only on your device. We never receive it, and we cannot see it.
LK On works the same way: it talks to the PLC on your plant network and stores its tag history, dashboards, panels, alarm rules and audit log on its own storage. Nothing is uploaded to us. Internet is used only for the optional alarm messages you configure (Telegram or WhatsApp, sent from the device to the chat you chose), software updates, and the optional remote access you can switch on or off yourself.
2a. LK Up: your plant's server and its apps
LK Up is maintenance software you run yourself. The LineKeeper Up Server app for Mac (downloaded from our site or the Mac App Store), the server programs for Windows and Linux, the web app they serve and the LK Up apps for iPhone and Android keep your plant's records — work orders, assets, parts, people (names, emails and roles), photos, documents and settings — on your server. A phone keeps its own copy and a queue of unsent changes, encrypted with a key per person, until it can reach the server. We never receive any of it and we cannot see it. There is no LineKeeper account and no LineKeeper cloud in this release, and the software contains no analytics, advertising or tracking.
What the software connects to: the other phones and computers on your network and, only if you set them up in Settings → Notifications, your own Telegram bot and your own mail server, to send the notices you chose. Those services are yours and have their own policies. The Updates tab of the Mac app downloaded from our site links to the release page on GitHub; it opens in your browser only when you click it.
On a Mac, the app registers the server as a background item that starts when you log in, only after you allow it; you can remove it at any time in System Settings → General → Login Items. If you choose a backup folder, copies of your data are written only there. The phone apps ask for the camera (to scan QR codes and take photos for requests and work orders), the photo library (to attach or save photos) and local-network access (to reach your server); photos stay with their record on your server.
You control this data directly. To delete it, delete the data folder of your server (or the Mac app and its container) and, on a phone, sign out or uninstall the app. If we ever offer a hosted copy, this policy will say what it stores before it exists.
3. What the app does not collect
- No account, name, email or password (the app needs none).
- No controller data, tag names or tag values.
- No location data.
- No advertising identifiers, and no data sold or shared with advertisers.
4. Local network access
To reach your PLC, the app on iOS asks for permission to access devices on your local network; on Android (closed beta) no separate permission prompt exists, and the app simply opens connections on the local network. In both cases this access is used solely to connect to the controller IP addresses you enter or scan for. No network scan results leave your device.
5. Diagnostics through Apple and Google
If you opt in to sharing analytics with app developers in your iOS settings (Settings → Privacy & Security → Analytics & Improvements), Apple may provide us with aggregated, anonymised crash and usage statistics through App Store Connect and TestFlight. This data is collected and controlled by Apple, cannot be tied to you by us, and helps us fix crashes. You can turn it off at any time in iOS settings. TestFlight beta usage is additionally governed by Apple's Privacy Policy. The same applies to the LK Up apps for iPhone and Mac.
On Android (closed beta installed through Google Play), Google may likewise provide us with aggregated, anonymised crash reports and vitals through the Play Console if crash reporting is enabled on your device. This data is collected and controlled by Google, cannot be tied to you by us, and is governed by Google's Privacy Policy.
6. The website, contact forms and reservations
When you submit the contact form, the Android beta form, the LK Up early-access form or the device reservation form, we collect the details you type — typically your name, an email address or phone number, how urgent it is (or, on the LK Up form, what you track maintenance in today), and your message. With it the browser sends the page you were on and, if present, first-touch attribution it remembered from your first visit (UTM campaign parameters, the referring site, the landing page and the time of that visit; stored in your browser's local storage under lk_attrib, no cookie). We use all of this only to reply to you, to route line-down messages first, and to know which pages bring questions. We do not sell it or use it for unrelated marketing.
Where it goes: each submission is delivered to the developer as a message in Telegram (processed by Telegram's servers on the way) and, when configured, appended as a row to a private spreadsheet. If you left an email address, an automatic acknowledgement is sent through Resend, our transactional email provider. A device reservation additionally creates a draft order as described in Section 6b.
The website is hosted on Vercel, which processes standard server logs and privacy-friendly, cookie-less analytics (aggregate page views) on our behalf. We also keep our own first-party counters of page views and anonymous interaction events (for example, which sections of a page visitors reach). These counters contain no personal data and use no cookies.
6a. Cookies and Google Analytics
We use Google Analytics 4 to understand how visitors use this website — which pages are viewed, roughly where visitors come from, and what device and browser they use. For this, Google Analytics stores first-party cookies (names starting with _ga) in your browser to tell returning browsers apart. We use this data for aggregate statistics only — we do not use it for advertising, remarketing or cross-site tracking, and we do not sell it.
If you visit from the EU/EEA, the United Kingdom or Switzerland, we ask for your consent with a banner before any Google Analytics cookies are set, and the site does not load Google Analytics unless you accept. You can change your decision at any time via the Cookie preferences link in the footer.
These cookies are optional for using the site: everything works if you block them in your browser settings, or you can install Google's Analytics opt-out browser add-on. How Google processes this data is described in Google's Privacy Policy. Beyond Google Analytics, the website sets no advertising or cross-site tracking cookies.
6b. Device preorders and payments
Paying by card. Card payments run on Stripe Checkout. Stripe collects your card details, name, email address, phone number and shipping and billing address on its own pages; we never see or store your card number. Stripe processes this data under Stripe's Privacy Policy and may use it for fraud prevention. After payment, Stripe passes us your name, email, phone number and shipping address so we can build and ship the unit.
What we store. For every order — card or invoice — we keep an order record: your name, email, phone number, shipping address, the size and price, the order status, Stripe's payment reference, the tracking number once it ships, and any notes you gave us (for example a PO number or the machines it is for). It is stored in a private hosted database (Upstash Redis, provisioned through Vercel) that only the developer can read, and it is used to fulfil the order, send you the emails below, handle refunds and returns, and meet accounting obligations. A new order also notifies the developer by Telegram with your name, email and shipping address.
Emails we send about an order. An order confirmation, a tracking email when the unit ships, and — if you reserved a unit before ordering opened — the one announcement we promised. They are sent through Resend. There is no marketing list: nothing else follows.
Refunds go back to the original payment method through Stripe (or by bank transfer for invoiced orders); the order record is kept with its refunded status.
6c. Your browser: local storage and the country check
Besides the analytics cookies in Section 6a, the site keeps a few values in your browser's local storage, all first-party and readable only by this site: lk_consent (your cookie choice), lk_geo (a two-letter country code, see below), lk_attrib (first-touch attribution, Section 6) and a session flag so the logo animation plays once. Clearing site data removes them. To decide whether to show the consent banner, the page asks our server for your country; the server echoes the country that Vercel's edge already derived from the request and stores nothing. Our own first-party counters (page views, sections reached, button clicks) are daily totals with no visitor identifier and are deleted after 90 days.
7. How long we keep things
App data lives on your device until you delete it or uninstall the app — see Data & Account Deletion; data on the LineKeeper device stays on the device and is yours to wipe; LK Up data stays on your own server until you delete it, and on a phone until you sign out or uninstall the app, and we hold none of it. Contact and beta submissions are kept only as long as needed to answer you or to send the one notification, after which you may ask us to delete them. Order records are kept for as long as the ship window, the return period and any warranty run, and afterwards for as long as accounting and tax law require; Stripe keeps its own payment records under its policy.
8. Your rights
You can ask us what website or order data we hold about you, and ask us to correct or delete it, through the contact form or by replying to any order email. We delete on request, except the parts of an order record we must keep for accounting or tax law. Because the app and the device store nothing on our side, you control that data directly at all times.
9. Children
LineKeeper is a professional industrial-automation tool. It is not directed at children and we do not knowingly collect data from anyone under 16.
10. Changes to this policy
If we change this policy we will update the date above and, for material changes, note it on this page. Continuing to use the app or website after a change means you accept the updated policy.
11. Contact
Questions about privacy? Reach us through the contact form and we will respond by email.