> For the complete documentation index, see [llms.txt](https://optilock.gitbook.io/optilock-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://optilock.gitbook.io/optilock-docs/privacy-policy.md). # OptiLock Privacy Policy **Effective date:** August 17, 2026 ยท **Last updated:** August 17, 2026 OptiLock is a mobile access-control application that lets an enrolled device request that a connected door be opened. This Privacy Policy explains how information is handled by the OptiLock mobile application (the **App**) and the OptiLock server selected during enrollment (the **Server**). ## 1. Who is responsible for your information OptiLock is designed to connect to a self-hosted Server. The organization that provides your enrollment QR code and operates that Server (the **Server Operator**) determines why and how Server-side information is processed. Contact the Server Operator for questions about its identity, legal basis for processing, retention periods, or handling of privacy requests. ## 2. Information handled by OptiLock ### Information stored on your device The App stores: * a randomly generated device identifier; * a non-exportable private signing key in Android Keystore, StrongBox when available, or Apple Secure Enclave/Keychain; * the corresponding public key; * the enrolled Server address and public certificate-authority certificate; * connection preferences, including request timeout and diagnostic-display settings; and * whether enrollment and setup are complete. Protected settings are encrypted on Android and stored as device-only Keychain items on iOS. App backup is disabled on Android. The private signing key is not uploaded or exported by the App. ### Information sent to the Server During enrollment and normal use, the App may send the Server: * the random device identifier; * the device public key; * whether the signing key is hardware-backed; * one-time challenge identifiers and cryptographic signatures; * door-unlock requests; and * ordinary network metadata sent with an internet request, such as IP address and user-agent information. The Server may record timestamps, request identifiers, device and challenge identifiers, request outcomes, HTTP status codes, direct peer IP addresses, user-agent information, and limited technical details in security audit logs. Door-controller response bodies and controller authorization tokens are not intentionally stored in those audit logs. ### Camera access The App requests camera permission only to scan an enrollment QR code. Camera frames are processed for QR recognition and are not intentionally saved, uploaded, or used for advertising or analytics. ### Biometrics and device credentials The App asks Android or iOS to authenticate you before enrollment, protected settings access, and door-unlock requests. Authentication is performed by the operating system. The App receives only the success, failure, or cancellation result and does not receive or store your fingerprint, face data, device PIN, or passcode. ## 3. How information is used Information is processed only as needed to: * enroll and identify an authorized device; * authenticate signed door-unlock requests; * operate the connected door controller; * protect connection settings and private keys; * prevent replay, unauthorized access, and abuse; * diagnose failures and display request identifiers when technical details are enabled; and * maintain security and operational audit records. The App does not contain advertising SDKs or analytics SDKs. The App provider does not sell personal information or use it for cross-app tracking. ## 4. Sharing and disclosure The App sends information only to the Server configured through enrollment. The Server Operator may use infrastructure providers, hosting providers, administrators, or a connected physical-access controller to operate its installation. Their handling of information is governed by the Server Operator's policies and agreements. Information may also be disclosed when required by applicable law, to respond to a valid legal request, or to protect users, systems, and physical premises from harm or unauthorized access. ## 5. Retention * On Android, local App settings and keys are normally removed when App data is cleared or the App is uninstalled. On iOS, device-only Keychain items may remain after the App is uninstalled and are removed when the operating system or device erasure removes them. * An enrollment token is held by the App only while enrollment is in progress. The Server stores only a hash of the token; the token expires and is limited to one successful enrollment. * Device records and audit logs remain on the self-hosted Server according to the Server Operator's retention policy and administrative actions. {% hint style="info" %} The reference OptiLock Server does **not** automatically delete audit logs. Each Server Operator is responsible for defining and enforcing an appropriate retention schedule, securing backups, and responding to deletion requests where legally required. {% endhint %} ## 6. Security OptiLock uses platform secure storage, non-exportable cryptographic keys, short-lived one-time challenges, system authentication, and certificate-validated HTTPS when configured for production. No system can guarantee absolute security. The Server Operator is responsible for securely configuring TLS, restricting access to its database and controller, protecting backups, and keeping software up to date. {% hint style="warning" %} Plain HTTP can be enabled for isolated development networks. It does not provide transport encryption or server authentication and should not be used for production or over untrusted networks. {% endhint %} ## 7. Your choices and rights You may deny or revoke camera permission in system settings, but QR enrollment will not work without it. On Android, you may remove locally stored App information by clearing App data or uninstalling the App. On iOS, uninstalling the App may not remove device-only Keychain items. Removing local data does not automatically delete Server records. Depending on your location, you may have rights to access, correct, delete, restrict, or obtain a copy of personal information, or to object to certain processing. Contact the Server Operator for requests involving enrollment, access, or audit records. Contact the App provider using the details above for questions about the App itself. Disabling or deleting an enrolled device may require action by an administrator and may end your ability to open the connected door. ## 8. International transfers The location in which information is processed depends on where the Server Operator hosts its Server and supporting infrastructure. Ask the Server Operator about applicable international transfers and safeguards. ## 9. Children's privacy OptiLock is intended for managed physical-access use and is not directed to children. The App provider and Server Operator should not knowingly enroll a child unless they have an appropriate lawful basis and any consent required by applicable law. ## 10. Changes to this policy This policy may be updated when OptiLock's features or legal obligations change. Material changes should be communicated through the App's distribution channel or by the organization operating the Server. The effective date at the top identifies the current version. ## 11. Contact For Server-side privacy questions or requests, contact the organization that issued your enrollment QR code. For App-related privacy questions, contact: * **App provider:** OOO IT-INTEGRACIYA * **Privacy contact:** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://optilock.gitbook.io/optilock-docs/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.