Privacy Policy

Effective November 19, 2026 · Arklytech LLC

This Privacy Policy explains what information Arklytech LLC ("we", "us") collects when you use Arklytech: the Arklytech mobile app, the web app at app.arklytech.ai and the cloud service behind them at api.arklytech.ai (together, the "Service"). It also explains how we use that information and the choices you have. The iPhone app is on the App Store and the Android app is on Google Play.

In short: we collect what we need to run your account and your Device Manager data, and nothing more. There are no ads, no tracking across other apps or websites, no analytics SDKs, and we do not sell or share your information for advertising. You can delete your account in the app at any time, or ask us by email.

1. What Arklytech is

Arklytech is a professional tool for access-control technicians. It configures Mercury access-control panels through Arklytech Edge, a Bluetooth device, and keeps your organization's sites, buildings and devices in Device Manager, in the cloud, so a configuration can be prepared once and pushed to a panel later. Support, its assistant, answers questions about the hardware of the devices listed in Resources from their manufacturers' official documentation. The Service is meant for business use by people who are 18 or older.

2. Information we collect

Account information

  • Email address, name and organization name, which you give us when you create an account.
  • Profile photo, if you choose to upload one. It is optional and is used only to show your account in the app and the web app. You pick the picture yourself, and only that picture is sent. Our server keeps a small square copy of it (at most 512 pixels wide) and nothing else from the file: the location, camera and date details a photo can carry are removed before it is stored. You can replace or remove it in the app at any time; a replaced or removed photo is deleted from file storage, and your photo is deleted when you delete your account.
  • Password, if you set one. We store only a one-way hash (bcrypt), never the password itself.
  • Two-factor authentication. When you turn on two-factor authentication (or your organization requires it), we store the authenticator secret in encrypted form and your recovery codes as one-way hashes. When you turn it off, both are deleted.
  • Google or Apple sign-in. If you choose "Continue with Google" or "Sign in with Apple", we receive from that provider your account identifier, your email address (with Apple this may be a private relay address) and, the first time, your name. From Google we request only the basic profile scopes (openid, email, profile). For Apple we also keep an encrypted token that lets us revoke Arklytech's access to your Apple ID when you delete your account. We never receive your Google or Apple password.
  • Sessions: for each signed-in device we keep the device name, platform, app version and when it signed in and was last used, so you can see your sessions and sign them out.

Your organization

Each account belongs to an organization, and we store your role in it (manager or technician) and, for a technician, the sites you can access. When you create an account you also create its organization, and you are its manager. A manager can invite others by email: for each invitation we store the email address, the role and site access it offers, who sent it, and when it was sent, accepted or cancelled.

Device Manager data

The content you enter or import: sites, buildings and devices, with their names, MAC addresses, IP addresses, network settings, panel configurations and descriptions, panel user names and panel passwords, and records of the Arklytech Edge devices your organization uses (hardware address, Bluetooth name, firmware version, battery level, network address, last seen and last user). Panel passwords and 802.1X passwords are encrypted on our servers with per-organization keys.

Purchases

When an organization subscribes to Arklytech Pro or you order an Arklytech Edge, you pay on the checkout of Whop, our payment processor. Whop collects your payment details, name, email address, billing address and, for an Edge, the shipping address, and processes the payment under its own privacy policy. We never receive your full card number.

  • What we receive and keep: the reference numbers of the subscription and each payment, the plan, its status, renewal and end dates, the amounts paid and refunded, the email address used at checkout, and for an Edge order its quantity and whether it has shipped.
  • Shipping address: it stays with Whop. We see it in Whop's dashboard to send your Edge, and we do not copy it to our servers. We keep only its country, to check that the order ships to the United States.
  • Free trial: to give each email address one trial, we keep a one-way hash of the email address that used it, and when. It is kept after the account is deleted, and it does not reveal the address.

Knowledge Base favorites

If you mark Knowledge Base models as favorites, we store which models you marked and when, linked to your account, so your favorites follow you to each phone.

Support conversations

If you use Support, we store the questions you type, the answers Support writes, the device and topic you picked, the conversation's title and dates, and how you rated a conversation when you end it. Before your first question, Support asks for your consent to send your questions to OpenAI (see section 5); we store that consent, its version and the date, and you can withdraw it in Settings at any time. Please do not type personal information into Support. For each answer we also record which documentation it was written from, how many words (tokens) the request used and what it cost, to keep the cost in check and to check the quality of the answers. We do not use your conversations for advertising, and we do not use them to train AI models.

The web app

The web app at app.arklytech.ai keeps you signed in with one cookie that holds your session. It is needed to sign in, the page's scripts cannot read it, and it ends when you close the browser, after 30 minutes without use, or 12 hours after you signed in. It is used for nothing else. Google's sign-in script also stores a cookie named g_state on app.arklytech.ai to remember the state of its sign-in prompt; it holds no account data. The web app keeps your theme and language choice in your browser's local storage, so they stay as you set them; it keeps nothing else there. It keeps no copy of your Device Manager data in your browser: it reads it from our servers each time you open it. It loads no analytics and no fonts from other sites. Its one outside script is Google's sign-in script from accounts.google.com, which draws the "Continue with Google" button; what Google collects through it is covered by Google's own privacy policy.

Activity and security records

  • Push results: which devices were pushed, the result, when, by whom and through which Edge. Status checks (Ping again and the status report) are stored the same way: which devices answered, when, by whom and through which Edge.
  • An audit log of important actions, such as creating, editing, moving or deleting records, imports and exports, pushes, sign-ins and failed sign-ins, and changes to passwords, two-factor authentication and sign-in methods. Each entry records the user and the time, and can record the IP address, the app version and the Edge used. Passwords and other secrets are never written to the audit log.
  • Web server logs with the IP address, the time, the address requested (for our API and the web app, the path only, without what you search for), the status and the app's or browser's user agent. Our API also logs the type, route, status and timing of each request, without the IP address. We do not log request bodies, passwords or tokens.

Crash reports and diagnostics

The app does not include a crash reporting or analytics SDK and does not send crash reports or diagnostics to us. If we add crash reporting to improve stability, it will be set up to exclude email addresses, names, IP and MAC addresses, panel data and passwords, and we will update this policy before it ships.

What stays on your phone

  • Your session token, in the phone's secure storage, and an encrypted database with the push jobs and results waiting to upload and the Edge devices this phone has used. Both are erased when you sign out. Device Manager is read live from our servers and is not stored on the phone; the panel passwords a push needs are fetched just before the job and kept in memory only while it runs.
  • Bluetooth is used to connect to your Arklytech Edge.
  • Location permission is requested on Android because the phone needs it to scan for the Edge over Bluetooth. Arklytech does not read, store or send your location.
  • Wi-Fi and, on iPhone, local network access are used to open a device's own web page through the Edge, a Mercury panel or a Direct Connect model: the phone joins the Edge's Wi-Fi, and the Edge reaches the device over Ethernet.
  • Network Access: the Wi-Fi network name and password you type for it are sent only to your Edge, over the encrypted Bluetooth link, so it can join that network. The password field is cleared once it is sent, and neither is sent to or stored on our servers.
  • App lock, if you turn it on, uses your phone's own biometrics or passcode. We never receive biometric data.
  • Support keeps nothing on the phone or in the browser: your conversations are read from our servers while you use them and are cleared from memory when you sign out.
  • Camera access is asked for only when you take a profile photo or scan a label (a device’s QR label or a MAC address label). Label pictures are read on your device and are never sent or stored; only the label’s code or the MAC address you choose is sent. Photos access is used only for a profile photo or a label picture you pick, and only the profile picture you crop is sent.

3. How we use information

  • To provide the Service: your account, sign-in, keeping your Device Manager data in the cloud, pushes and their results.
  • To keep accounts secure: two-factor authentication, checking new passwords against known leaked passwords, pausing sign-in after repeated failed attempts, sign-in alerts, the audit log and investigating misuse.
  • To send service emails, such as verification and password reset codes, security alerts and account notices. We do not send marketing email.
  • To answer the questions you ask in Support, and to measure Support's cost and the quality of its answers.
  • To answer your support requests and to meet legal obligations.
  • To bill a plan, refund a payment, send an Edge order, and keep the records that tax and accounting law requires.

Where the law asks for a legal basis (for example in the EU or UK), we rely on performing our contract with you or your organization, our legitimate interest in keeping the Service secure and working, and compliance with legal obligations.

4. What we do not do

  • No advertising and no advertising identifiers.
  • No tracking of you across other companies' apps or websites.
  • No analytics SDKs.
  • No selling of personal information, and no sharing of it for cross-context behavioral advertising.

5. Who we share information with

  • Your organization. Device Manager data belongs to your organization, and only its members can see it. Every member also sees the other members' names, email addresses, photos, roles and when they last signed in.
  • Service providers that process data for us only on our instructions: DigitalOcean (our server, database, file storage in DigitalOcean Spaces and encrypted backups, in New York, USA) and Resend (delivery of service emails).
  • Whop (whop.com), our payment processor, when you subscribe or order an Edge: it handles the checkout, payments, receipts and refunds, and keeps your payment details and addresses under its own privacy policy.
  • Google and Apple, only when you choose to sign in with them. Their handling of your data is covered by their own privacy policies.
  • The Apple App Store, which distributes the iPhone app. Apple's handling of your data when you download or update the app is covered by its own privacy policy.
  • Google Play, which distributes the Android app. Google's handling of your data when you download or update the app is covered by its own privacy policy.
  • OpenAI, which writes Support's answers. When you ask Support a question, the text of your question, the earlier messages of that conversation and passages of the manufacturers' documentation are sent to OpenAI's API, without your name or email address. Under OpenAI's API terms, data sent to its API is not used to train or improve its models, and OpenAI keeps it for up to 30 days to detect abuse, unless the law requires longer, and then deletes it. Support is used only if you agree to this first.
  • Pwned Passwords (Have I Been Pwned), to check that a new password is not a known leaked password. It receives only the first 5 characters of a one-way hash of the password, never the password itself or your email address.
  • Legal reasons: when required by law or to protect the rights, safety and security of our users, the public or Arklytech LLC.
  • Business transfers: if Arklytech LLC is involved in a merger, acquisition or sale of assets, information may transfer under this policy.

6. Security

All traffic between the app and our servers is encrypted with TLS. Every account can turn on two-factor authentication, and an organization can require it for its members. Panel passwords, authenticator secrets and provider tokens are encrypted on the server; passwords and recovery codes are stored as one-way hashes; the backups kept in DigitalOcean Spaces are encrypted. The app's database on the phone is encrypted. No system is perfectly secure, so please keep your password, authenticator and recovery codes safe.

7. Where data is stored

Our server, file storage and backups are in the United States (DigitalOcean, New York). OpenAI processes the Support questions it receives in the United States. If you use the Service from outside the United States, your information is transferred to and processed in the United States.

8. How long we keep information

  • Account and Device Manager data: for as long as your account and your organization's account are active.
  • A deleted device, panel user or building is kept as a deleted copy for 30 days and then erased. A deleted site keeps only its name.
  • Push results and audit log entries are kept as a record of what was done and are not edited. They are kept for as long as your organization's account is active, and are erased with the organization when it is closed and purged (see below). Sign-in records outside an organization (sign-ins and failed attempts) are kept for security with no fixed end date, linked only to an internal user number, not to your name or email.
  • A closed organization is erased for good by an automatic job that runs every hour, once 30 days have passed since it closed: its Device Manager data, members, sessions, keys, imports and exports (with their files), Edge records, change history, push results, status checks and audit log. What remains is a renamed record that the organization existed and was closed, and one log entry noting that it was erased.
  • Support conversations are kept until you delete them, and are deleted automatically 180 days after their last message. Deleting a conversation deletes its messages. The record of what each request cost is kept, without the question or the answer, so the daily cost limit stays right.
  • When you delete your account, your sign-in methods, authenticator secret, recovery codes, emailed codes, Knowledge Base favorites, profile photo, Support conversations and Support consent are deleted at once, every session is signed out and deleted, and your name and email address are removed from your user record.
  • The contents of an uploaded CSV file that is not imported are cleared after 24 hours. CSV exports and import error reports are deleted from file storage 24 hours after they are made.
  • Encrypted backups are made every hour. Hourly copies are kept for 48 hours and one copy a day for 30 days. We also keep a backup from before each update of our server: the last 20 in encrypted storage and the last 5 on the server itself. Deleted data leaves the backups as these copies are replaced.
  • Purchase records (plans, payments, refunds and Edge orders) are kept for as long as tax and accounting law requires, also after an account is deleted.
  • Web server logs are kept for 14 days. Our API's own logs are limited in size and overwritten as new ones are written.

9. Deleting your account

In the app: tap your photo or initials at the top right to open Settings, then Privacy & data › Delete account, confirm with your password (or a fresh Google or Apple sign-in) and, if two-factor authentication is on, your authenticator code.

By email: write to contact@arklytech.ai from the email address of your account. We may ask you to confirm the request, and we complete it within 30 days.

If your organization has a paid plan, deleting your account cancels it first; see Refunds.

Deleting your account also closes your organization, and no one can open its Device Manager data again. Its records are erased for good 30 days after it closes; email us to have it done sooner. Full details are on the account deletion page.

10. Your rights and choices

Depending on where you live, you may have the right to access, correct, export or delete your personal information, to object to or restrict some processing, and to complain to a data protection authority. You can update your name in the app, ask us for a copy of your data, and delete your account at any time. For any other request, email contact@arklytech.ai. We will not treat you differently for exercising your rights.

California residents: in the past 12 months we have collected the categories described in section 2 (identifiers such as name, email and IP address; account and security records; your profile photo, if you upload one; the questions you ask in Support, if you use it; commercial information, such as the plan you bought and your payments; and the business data you enter) for the purposes in section 3. We do not sell or share personal information as those terms are defined in the CCPA, and we do not use sensitive personal information to infer characteristics about you.

11. Children

Arklytech is a professional tool for business users who are 18 or older, and it is not directed to children. We do not knowingly collect information from anyone under 18. If you believe someone under 18 has given us information, contact us and we will delete it.

12. Changes to this policy

We may update this policy. We will post the new version here with a new effective date, and for significant changes we will let you know in the app or by email before they take effect.

13. Contact

Arklytech LLC
Email: contact@arklytech.ai