Understand where
your data goes.

This notice covers the vibeokie test apps, desktop agent, and account service. The product is still in testing. Retention schedules, deletion procedures, and service provider details will be completed before public release.

Account and device information

We process the account details, permissions, sessions, and device connection records needed to verify your identity and manage access. If you choose Google sign-in, the current requested scopes are openid, email, and profile. They do not grant access to Gmail or Google Drive content.

Tasks, approvals, and project content

The vibeokie server processes and stores task instructions, saved templates, task events, execution summaries, and approval details. This supports task routing, cross-device access, status updates, and history. The server can read this content.

Project files and Codex sign-in credentials stay on your computer. However, task instructions, commands, execution output, and approval details may include code snippets, file paths, or other project content that reaches the server. Keeping project files on your computer does not mean all project-related information stays local.

Dictation

The apps use system dictation to enter task text. How audio is processed depends on Apple’s services, your device, and your settings. Review the recognized text before sending it. Once sent, the text is handled as task content.

Local storage and connections

The iPhone app stores its credentials in the system keychain and may keep drafts and records of unconfirmed operations locally. Remote service connections use HTTPS. Disconnecting or revoking a device blocks future access; it does not automatically delete task history.

Other services

Codex sign-in and execution involve OpenAI services. System dictation involves Apple services. Optional Google sign-in involves Google’s identity service. Those services also have their own terms and privacy notices. Do not submit passwords, verification codes, or secret keys in tasks or support tickets.

Retention and deletion requests

The test version does not currently offer a complete self-service deletion workflow or a uniform automatic deletion schedule. To request access, correction, or deletion of account-related data, contact support through your account and describe the scope of your request. Do not include sensitive credentials. Support will verify the account and respond about the data that can be handled.

Support information

Issue descriptions, device models, app versions, and error messages submitted in support tickets are used to investigate the issue. Remove private information from screenshots and logs before sharing them.

Contact

Submit a data request through your account ↗

Before public release, this notice will be updated with the operator’s identity, a contact route for people without an account, a complete service provider list, and specific retention arrangements.