# CoCrypt ## One file. Every key matters. Lock a file with a shared decision. CoCrypt splits its encryption key among your chosen participants and collects their approvals through nearby Bluetooth connections. ### Every key piece counts AES-256-GCM protects the file. Its key is split into N pieces with XOR; all pieces are required to reconstruct it. Each piece is encrypted for its participant using EC P-256 and ECIES. ### Nearby, device to device Exchange public keys and collect approvals over Bluetooth Low Energy. Encryption and approval need no internet connection or cloud relay. ### Approve with biometrics Participants authenticate with face or fingerprint recognition on their own device before sending an approval. CoCrypt receives the authentication result, not biometric templates. ### A fresh challenge Unlock requests use a fresh, time-stamped challenge. The app verifies the participant’s ECDSA signature before accepting the returned key piece. ### Your key, your recovery Create a 12-word recovery phrase during setup. It can restore the same key on another device. Keep it private: anyone with those words can recreate your key. ### One portable .cvl file Documents, images, videos and archives can be encrypted into a .cvl container. Save or share the encrypted file using the system share sheet. Device memory and storage limit file size. ## User guide Start with your recovery phrase, then agree who will participate. Keep a copy of the encrypted .cvl file and protect each participant’s 12 words separately. Beyondend cannot recover lost keys; a missing key without its recovery phrase can leave the file inaccessible. ### 1. Prepare your key Choose Create New Key, securely record the 12 words, and finish setup. To recover an existing key, choose Restore and enter the original phrase. ### 2. Choose the participants The owner opens Lock My File. Each participant chooses Send Participant Key, authenticates and brings their phone nearby. The owner collects each public key and reviews the list before continuing. ### 3. Lock and save Select the source file. CoCrypt creates its encrypted .cvl container. Use Save to keep or share it before choosing Clean and Close, which deletes the generated output from the app. ### 4. Collect approvals and unlock Open the .cvl file and request approval from each remaining participant. They choose Approve, authenticate and bring their device nearby. Approvals are collected sequentially. Once every required piece is available, unlock and save the decrypted file. ### Owner and participant roles The owner’s own key is included by default and can be removed before encryption. If its matching key is on the unlocking device, that piece is recovered locally. Collective control depends on the participant list you select. ### After unlocking The decrypted output is an ordinary file. CoCrypt does not control copies saved or shared outside the app. Leaving with Back does not delete the generated output; use Clean and Close after saving what you need. ### Every key piece counts AES-256-GCM protects the file. Its key is split into N pieces with XOR; all pieces are required to reconstruct it. Each piece is encrypted for its participant using EC P-256 and ECIES. ### Nearby, device to device Exchange public keys and collect approvals over Bluetooth Low Energy. Encryption and approval need no internet connection or cloud relay. ### Approve with biometrics Participants authenticate with face or fingerprint recognition on their own device before sending an approval. CoCrypt receives the authentication result, not biometric templates. ### A fresh challenge Unlock requests use a fresh, time-stamped challenge. The app verifies the participant’s ECDSA signature before accepting the returned key piece. ### Your key, your recovery Create a 12-word recovery phrase during setup. It can restore the same key on another device. Keep it private: anyone with those words can recreate your key. ### One portable .cvl file Documents, images, videos and archives can be encrypted into a .cvl container. Save or share the encrypted file using the system share sheet. Device memory and storage limit file size. ## Support & FAQ team@beyondend.dev ### The other phone does not appear Turn on Bluetooth, allow the requested permissions and keep both phones close with CoCrypt open. For key registration, one phone sends while the owner receives. For unlocking, the owner requests approval while the participant chooses Approve. ### Biometric authentication fails Set up a supported fingerprint or face method in the device settings. CoCrypt requests biometric-only authentication. Check permission and enrollment, then try again. ### I replaced or lost my phone Use Restore with your original 12-word phrase to derive the same key. A new phrase creates a different key and cannot replace a key required by an existing .cvl file. Beyondend has no recovery copy. ### Does everyone need to stay together? The app collects nearby approvals one at a time and keeps accepted pieces during the current flow. It does not continuously verify that all participants remain nearby after approving. ### Can the owner open a file alone? Only if all required pieces can be recovered with keys on that device. The owner’s matching piece is handled locally. Select other participants when you want shared control. ### Where are my files? Generated outputs are saved in the app’s Documents directory and can be exported through the system share sheet. On iOS, file sharing is enabled for access through Files. Clean and Close removes the generated output; Back does not. ### What should I send support? Describe the step, device model, OS version and visible error. Never email recovery words, private keys or confidential files. Contact team@beyondend.dev. ## Get CoCrypt Collective file encryption for iPhone, iPad and Android. Free on the App Store and Google Play. ### iPhone & iPad Requires iOS 16 or iPadOS 16 or later. Nearby key exchange and biometric approval require compatible hardware and permissions. [Download on the App Store](https://apps.apple.com/gb/app/cocrypt/id6759932131) ### Android Available on Google Play. Bluetooth Low Energy and enrolled biometrics are required for nearby participant approval. Check Google Play for device compatibility. [Get it on Google Play](https://play.google.com/store/apps/details?id=com.beyondend.covault&pcampaignid=web_share) ## Privacy Policy The short version: the CoCrypt app does not send your personal data to Beyondend Dev. There are no accounts, analytics or tracking. Files and keys are processed on your device. Last updated: May 28, 2026 ### 1. Who We Are CoCrypt is an application developed by Beyondend Dev, a company registered in Turkey at Zühtüpaşa, Rıfat Bey Sk. No:2 kat:3, 34724 Kadıköy/İstanbul. You can reach us at team@beyondend.dev . ### 2. What CoCrypt Is CoCrypt is a multi-party file encryption application. It allows a file owner to encrypt any file so that all designated participants must physically approve — via Bluetooth proximity and biometric authentication — before the file can be decrypted. There is no server, no cloud storage, and no user account system. All operations are local or peer-to-peer. ### 3. Local Key Storage During participant setup, CoCrypt creates an EC P-256 key pair on your device. The private key is protected on the device using the operating system’s secure storage mechanisms; it is not sent to Beyondend Dev or a remote server. Beyondend cannot read, retrieve or recover your key. ### 4. No Data Transmitted to Us CoCrypt does not transmit any data to Beyondend Dev or to any third-party server. All key exchanges happen peer-to-peer over Bluetooth Low Energy — physically between users' devices, with no internet connection involved. Encrypted files ( .cvl ) are created and stored on your device and travel through whatever channel you choose (email, AirDrop, etc.). We receive nothing. ### 5. No Personal Data Collected We do not collect any of the following: Names, email addresses, or contact information Device identifiers or hardware fingerprints Usage data, analytics, or crash telemetry Location data The content of any file you encrypt or decrypt Your cryptographic keys or any derived material ### 6. No Third-Party Services CoCrypt uses no third-party analytics SDKs, advertising networks, crash-reporting services or tracking tools. It uses operating-system interfaces for Bluetooth, biometric authentication and secure storage, as well as file selection and sharing. ### 7. No Accounts Required CoCrypt requires no account creation and no registration with Beyondend Dev. There is no login, no signup, and no user profile — which means there is no personal data associated with you in any system we control. ### 8. Biometric Data CoCrypt uses the device’s fingerprint or face authentication to authorise unlock operations. The operating system processes biometric data. CoCrypt never accesses raw biometric data; it receives only a success or failure result. ### 9. Data Loss Warning Because your private key exists only on your device and we have no copy of it, losing your device or uninstalling the app without backup means losing your ability to participate in future unlock sessions. We strongly recommend keeping your device secure. We cannot recover lost keys under any circumstances. ### 10. Children's Privacy Since we collect no data from anyone, there are no special concerns regarding children's privacy. No data is collected from users of any age. ### 11. Changes to This Policy If we ever change our data practices, we will update this Privacy Policy accordingly and notify users through the app or our website. The date at the top of this page indicates when the policy was last revised. ### 12. Contact If you have any questions about this Privacy Policy, you can contact us at: Beyondend Dev Zühtüpaşa, Rıfat Bey Sk. No:2 kat:3 34724 Kadıköy/İstanbul, Turkey team@beyondend.dev [team@beyondend.dev](mailto:team@beyondend.dev) ### Technical clarification · September 6, 2026 The legal source is dated May 28, 2026. Technical wording has been aligned with the current app: private keys are loaded by the app from secure storage, rather than being permanently confined to a hardware enclave. The 12-word recovery phrase can recreate the same key. Approvals are collected sequentially; a matching key on the unlocking device is handled locally. See the user guide for the full flow. ### Website and support This website stores an explicit EN/TR language preference in your browser under cocrypt.web.language. It does not query your location and contains no accounts, payments or analytics. Hosting may process standard request logs to deliver and secure the site. If you email support, we receive the email address and message you choose to send to answer your request. Never send recovery phrases or private keys. ## Terms of Use By downloading or using CoCrypt, you agree to these terms. CoCrypt is a local, peer-to-peer application. It collects no personal data, requires no account, and transmits nothing to our servers — because we have no servers involved in its operation. Last updated: May 28, 2026 ### 1. Agreement These Terms of Use constitute a legally binding agreement between you and Beyondend Dev ("we," "us," or "our"), a company registered in Turkey at Zühtüpaşa, Rıfat Bey Sk. No:2 kat:3, 34724 Kadıköy/İstanbul, regarding your use of the CoCrypt application ("the App"). By using the App, you agree to be bound by these Terms. If you do not agree, please do not use the App. ### 2. The App CoCrypt is a multi-party file encryption application. The owner encrypts a file into a .cvl container using AES-256-GCM, splits the key among designated participants using XOR, and encrypts each piece with the participant’s EC P-256 public key via ECIES. During unlocking, participant approvals are obtained over Bluetooth Low Energy with biometric authentication on the participant’s device. Operations run locally and over direct Bluetooth connections. Beyondend Dev has no access to your keys, files or communications. ### 3. No Account Required CoCrypt requires no registration, account or login with Beyondend Dev. You use the App without identifying yourself to us. We do not collect, store or process personal data through the App. Your cryptographic private key is generated on your device and protected by the operating system’s secure storage mechanisms; it is inaccessible to us. ### 4. Intellectual Property The App, its design, code, name, and associated materials are the intellectual property of Beyondend Dev, protected under applicable copyright and trademark law. You may not copy, modify, distribute, reverse-engineer, or create derivative works from the App without our express written permission. ### 5. Licence Grant We grant you a limited, non-exclusive, non-transferable, revocable licence to install and use the App on your personal device(s) for personal, non-commercial purposes, in accordance with these Terms. ### 6. Acceptable Use You agree to use the App only for lawful purposes. You must not use the App to store, manage, or facilitate any illegal activity. You are solely responsible for the content you store within the App. ### 7. No Warranties The App is provided "as is" without warranty of any kind, express or implied. We make no guarantees regarding the App's availability, reliability, accuracy, or fitness for any particular purpose. Use of the App is at your own risk. ### 8. Limitation of Liability To the fullest extent permitted by law, Beyondend Dev shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of, or inability to use, the App — including any loss of data stored within the App. You are solely responsible for maintaining backups of your data. ### 9. App Store Terms If you download the App through Apple App Store or Google Play, your use is also governed by the terms of the respective distributor. Beyondend Dev, not the App Store or Google Play, is solely responsible for the App and its content. ### 10. Modifications We reserve the right to update or modify these Terms at any time. The updated Terms will be posted within the App or on our website. Continued use of the App after changes constitutes acceptance of the updated Terms. ### 11. Governing Law These Terms shall be governed by and construed in accordance with the laws of Turkey. Any disputes arising from these Terms shall be subject to the exclusive jurisdiction of the courts of Turkey. ### 12. Contact If you have any questions about these Terms, please contact us: Beyondend Dev Zühtüpaşa, Rıfat Bey Sk. No:2 kat:3 34724 Kadıköy/İstanbul, Turkey team@beyondend.dev [team@beyondend.dev](mailto:team@beyondend.dev) ### Technical clarification · September 6, 2026 The legal source is dated May 28, 2026. Technical wording has been aligned with the current app: private keys are loaded by the app from secure storage, rather than being permanently confined to a hardware enclave. The 12-word recovery phrase can recreate the same key. Approvals are collected sequentially; a matching key on the unlocking device is handled locally. See the user guide for the full flow.