Your workspace.
Your data choices.
AIOS connects your workspace to AI providers. This policy explains what is collected, where it goes, and how you control sharing.
Effective 9 September 2026 · AI sharing disclosure version 1
1. Who is responsible
AIOS Workspace is provided by Yekar GmbH, Wachtelring 3, 04827 Machern, Germany. Managing director: Arthur Kloss. Contact arthur@yekar-ai.com for privacy questions, deletion requests, or assistance withdrawing permission.
When your employer or another organisation operates your workspace, it determines the purposes of its business data processing and the connected services. Yekar provides the app and, where agreed, hosting and support. Contact your workspace administrator as well as Yekar about organisation-controlled data.
2. What we collect and how
- Account and workspace details: your name, email address, user ID, role, workspace membership and authentication information, supplied when an account is created, an invitation is accepted, or you sign in. These enable authentication and access control.
- Content you provide: messages, conversation history, task instructions, selected photos, videos, files, and voice recordings. We receive these when you use the corresponding features and store submitted content in your workspace to provide conversation history and complete your work.
- Agent context: relevant workspace files, memory, instructions, and content obtained from services connected by your organisation. Agents retrieve this information while carrying out tasks; it can include personal information about you or other people.
- Operational data: request and connection information, including IP addresses, timestamps, errors and service logs, used to operate, secure and troubleshoot the service. Apple push notification tokens are used to deliver notifications if you enable them. Diagnostic reports can be shared with support when you choose to share them.
- On-device data: authentication details in Keychain, drafts, cached media, preferences and your AI-sharing choice. Voice recordings awaiting delivery remain on the device until delivered or removed.
3. AI providers and the data they receive
OpenAI — GPT and Codex
When an OpenAI-powered agent processes a task, OpenAI receives the messages and relevant conversation history, instructions, attachments and workspace or connected-service content included in that task. This is used to produce responses and perform requested work. See OpenAI’s privacy policy.
Anthropic — Claude
When a Claude-powered agent processes a task, Anthropic receives the messages and relevant conversation history, instructions, attachments and workspace or connected-service content included in that task. This is used to produce responses and perform requested work. The recipient depends on the selected agent engine; delegated work can use either provider. See Anthropic’s privacy policy.
Voice transcription — OpenAI
Voice transcription sends recorded audio to OpenAI to turn speech into text. Realtime transcription streams audio while the feature runs, before a chat message is sent. Recorded-file transcription is sent through the workspace server; where configured, a local transcription fallback may be used. Transcribed text sent to an agent is processed as message content.
Running AIOS on your own server does not mean all AI processing happens there. The providers above process the content sent to them on their infrastructure, which may be outside your country, including in the United States.
4. Your permission and controls
The iOS app version containing AI sharing disclosure version 1 asks for explicit permission before enabling AI sharing. Older builds may not include these controls; update before using AI features. Choosing Not now leaves AI processing off and allows browsing. Microphone or photo access permission is separate from permission to share content with AI providers.
Open Settings → Privacy & AI to allow or withdraw AI processing. The choice applies to the signed-in account and workspace on that device. Withdrawal blocks new AI requests and voice uploads from that device. It does not recall data already sent, stop server work already started, remove messages already queued on the server, or change another device’s permission. Stop active runs and remove queued messages in the app, or contact your administrator for help. Permission must be given again when the sharing disclosure changes.
Only include other people’s information when you are authorised to use it for the task. An organisation’s connected services and independent automations are managed by its administrator.
5. Other recipients and protection
Your workspace operator and authorised members can access content according to workspace permissions. Hosting and infrastructure providers process data to run the service. Apple processes device notification tokens and notification payloads to deliver push notifications. Services connected to your workspace receive the information needed when an agent uses those services for a task; your administrator manages these integrations and their access.
Third parties processing personal data on our behalf must provide the same or equal protection described in this policy, including confidentiality, appropriate security, limited use and applicable deletion obligations. This is a requirement for our processing arrangements, not a claim that every independently configured workspace or provider account has been verified. Your workspace operator must ensure applicable processing agreements and lawful international-transfer safeguards cover the services it enables. Contact us to confirm the arrangements for your workspace before sharing personal data.
Provider retention and model-improvement rules depend on the service, plan, settings and agreement used by your workspace. This policy does not promise zero retention or a universal exclusion from model training. Your administrator and Yekar can explain which arrangements apply before you share content.
6. Retention and deletion
Workspace messages, attachments and agent context are retained to provide history and ongoing work until deleted under your organisation’s retention arrangements. Operational records are retained as needed for security, troubleshooting and applicable legal obligations. Copies may remain in backups until those backups expire. AI providers apply their own applicable retention rules; withdrawing permission does not automatically delete data already received by them.
Request access, correction or deletion through your workspace administrator or arthur@yekar-ai.com. We will identify the relevant workspace and explain any legal retention requirements or third-party steps. Logging out or uninstalling the app does not delete server-side workspace content.
7. Your rights and legal bases
Depending on applicable law, you may have rights of access, correction, deletion, restriction, portability and objection, and may withdraw consent for future processing. You may complain to your local data protection authority; Yekar’s regional authority is the Saxon Data Protection and Transparency Commissioner.
Where the GDPR applies, processing is based on consent where requested, performance of a contract for the service, legitimate interests in security and reliable operation, and compliance with legal obligations where applicable.
8. Policy changes
We update this page when our practices change. Material changes to the AI-sharing disclosure require a new permission decision in the iOS app.