Cortex Cola Privacy Notice
Effective date: November 1, 2026.
Cortex Cola is operated by FLock Technology Holdings (“we”, “us”). It is the iPhone and iPad companion to the Cortex desktop agent. Tasks run on your paired computer. This notice explains how the app and remote connection service handle information and supplements the FLock Privacy Policy.
Information on your devices
Cola stores pairing credentials and its private pairing key in the iOS Keychain. Drafts, pending messages, selected attachments, recent synced conversation content, result listings and reference titles are stored locally to support recovery after disconnection. Files shared into Cola are staged locally before you choose to send them.
Downloaded results and image thumbnails remain on your device for reuse and offline viewing. The result cache and local state directory are excluded from iCloud backup. This does not describe all other app files, exported copies or your computer’s backup settings. Removing a pairing does not erase downloads or copies saved to Photos, Files or other apps. Deleting Cola removes its app-container data; Keychain items may remain.
Messages, attachments and your computer
When you send a request, Cola sends your message, chosen attachments and relevant references to the paired computer. The computer returns task progress, replies, results and supported schedule information. It may store those records and use the models, tools and connected services configured there to carry out your request.
Remote message and attachment payloads are encrypted between the phone and computer using HPKE, with Apple’s CryptoKit on iOS. The relay routes ciphertext without the endpoint private keys needed to decrypt it. This protection does not prevent the paired computer or a service it calls from reading content needed to process the request, and it does not make connection metadata anonymous.
AI services and sharing consent
Your computer selects the AI providers and gateways. Message text, images, audio, files, relevant conversation context and tool results may be sent to them. Gateways may forward requests to upstream providers. Their retention, training and processing locations depend on their own terms and your account settings. Cola does not automatically route all requests to FLock’s inference platform.
Current test versions show the configured AI recipient hosts and ask for permission before new sends, attachment uploads, supplements and schedule creation or enabling. You may decline and keep your draft. Consent is saved for the paired computer, conversation and recipient configuration. A configuration change requires confirmation again. The listed AI hosts are not a complete list of every website, tool or connector a task might use. Review those services before sharing sensitive information.
You can withdraw permission for future phone sends in Privacy & Data Sharing. Withdrawal cannot recall information already sent and does not automatically stop accepted work or existing schedules. Stop or pause those separately. Newly authorized mobile schedules block new AI requests when the recipient configuration changes until reauthorized; older schedules are not retroactively treated as newly consented.
Relay and notification metadata
The relay stores computer and device identifiers, credential hashes, pairing records and a limited list of revoked-device identifiers. If notifications are enabled, it also stores an Apple push token linked to the pairing. These records support authentication, routing, revocation, reconnection and reminders; they do not contain chat or attachment bodies.
Apple Push Notification service delivers generic task-status messages and identifiers used to open the relevant result. The push payload does not include chat text, attachment names or approval arguments. Apple processes delivery under its own terms.
Hosting, logs and retention
The relay service and its persistent volume are currently hosted by Railway in Singapore. Hosting operations and subprocessors may process information elsewhere, including the United States. Choosing the Singapore region does not mean all platform data stays there. Apple and the AI or connected services selected on your computer may also process information in other countries.
Railway logs network metadata such as IP address, client information, request path, status, timing and duration. The current hosting plan exposes seven days of log history. That visibility window is not a guarantee that logs or internal copies are permanently erased after seven days. No customer-managed volume backups are currently configured for this relay; this does not establish the absence of provider-managed internal copies. Railway’s privacy policy describes its own handling of platform data.
Pairing metadata has no automatic expiry-based deletion period in the current service. Once the computer synchronizes a revocation, active device authorization and its push registration are removed. Up to the most recent 32 revoked-device identifiers per computer may remain for revocation checks; older entries are displaced by count, not by age. Computer records may also remain. Revocation is not complete erasure of every server record.
Local data remains until removed through applicable device or storage controls. Copies on your computer, exported files and information held by AI or connected services have separate retention and deletion controls. Information may also need to be retained for security, legal obligations or other purposes permitted by applicable law.
System permissions
- Camera: reads a pairing QR code when you open the scanner; camera frames are not uploaded to the relay by this path.
- Photos and Files: system pickers select attachments. Saving an image to Photos requests add-only permission.
- Microphone: records audio or dictation you start. Dictated text goes into the draft for review before sending.
- Speech recognition: uses on-device recognition when supported; otherwise Apple’s speech service may process the audio.
- Notifications: optional task reminders, controlled in Cola and iOS Settings.
- Local network: connects directly to a compatible computer on your network.
Privacy requests and contact
Our existing legal team handles privacy requests. For questions or requests to access, correct or delete information held by the service, email legal@flock.io with “Cortex Cola privacy request” in the subject. Describe the request and affected pairing. Do not email API keys, pairing invitations, connection tokens, private keys or chat files. Additional information may be needed to locate the relevant records and verify authority over the pairing. An email address alone may not identify a device because Cola does not use a separate username/password account.
Requests involving data held by your computer or chosen AI services may require action there as well. Removal from the active relay store does not by itself prove erasure of hosting logs or provider-managed copies. Applicable rights, verification and exceptions depend on the relevant law. The general FLock policy provides additional information about privacy rights and contacting the operator.
This website and changes
Visiting these pages is separate from using the mobile app. The FLock website uses hosting logs and Google Analytics; website data and support correspondence are covered by the general FLock Privacy Policy. No transmission or storage method is completely secure. Material updates to this notice will show a revised effective date here.
For product help, visit Cortex Cola Support.