Privacy & data handling
Your information in ThinkOS
This policy covers ThinkOS for iOS and Android and ThinkOS / Project Portal workspaces. THINKVERSE AI COMPANY LIMITED operates the app. Your organization's workspace administrator manages accounts, permissions and shared organizational records.
Information we process
| Information | Purpose and recipients |
|---|---|
| Username, email, display name and sign-in details | Authentication, access control and identifying authors of shared work. Native session credentials are stored using the device Keychain or Keystore until you sign out or delete the account. Optional Face ID or fingerprint protection controls access to the saved session. Web passkeys store a public credential on the workspace server; ThinkOS never receives your biometric template or private passkey. Device authentication may use a device PIN when the platform permits it. |
| Business contact and financial records entered in authorized tools | Some workspaces enable client and finance tools. These can store contact names, phone numbers, addresses, invoice and expense details, tax identifiers and bank details entered for organizational work. Access follows workspace permissions. ThinkOS does not charge for the app or collect card details for app purchases. |
| AI instructions, conversations and selected attachments | Sent to your workspace server and the AI provider used for the task, such as OpenAI or Anthropic. Coding agents may read project files needed for your instructions and authorized work. Conversation and native agent histories are stored on the workspace server. |
| Projects, tasks, issues, comments, documents and selected images | Stored on the workspace server and shared with authorized project participants. The app uses system file pickers; it does not request blanket access to your photo library or device storage. |
| Voice recordings you choose to make | Device mode is the default and transcribes on the device without uploading audio or silently falling back to a cloud service. In explicitly selected API mode, recordings are sent through ThinkOS to OpenAI GPT-Transcribe (model gpt-transcribe) for transcription. Recordings are limited to one minute. You review the transcript and choose whether to send it as an AI instruction. Dictation does not record in the background; explicitly started or answered AI calls can continue while the screen is locked. |
| Push token, installation ID, account and workspace identifiers | Deliver optional notifications through Google Firebase Cloud Messaging on Android or Apple Push Notification service on iOS. Agentic Coding notifications show the project name, a status and queue progress (for example, 2 of 3 queued tasks); project comment notifications use generic text. Notifications also carry navigation identifiers and never include conversation text or file contents. Your device notification settings control whether this text appears on the lock screen. |
| Optional AI voice calls | After you start or answer a call, Thai speech is transcribed on your device and the text is sent automatically to OpenAI gpt-6-luna through ThinkOS. In cloud voice mode, only the generated reply text goes to gpt-4o-mini-tts for AI-generated speech streamed into temporary memory. In device voice mode, the selected installed Thai system voice reads the reply on the phone; reply text is not sent to a speech provider. Microphone audio is not uploaded. Calls may continue while locked and are limited to 20 minutes. You can mute or end the call and separately disable incoming calls. Calls cannot read project files or run Coding tasks. ThinkOS keeps bounded temporary text in memory, not its database. Scheduled-call times, delivery status, usage counts and revocable device registrations are stored separately. Generic call invitations travel through APNs VoIP or FCM without conversation text. A call-only credential protected by Keychain/Keystore allows answering while locked; it cannot unlock the app or access other workspace APIs. Provider retention follows the provider account and service terms. |
| Appointment details you enter or select | Passed to the device calendar confirmation interface. The app does not read existing events or upload your calendar to ThinkOS. iOS 17+ uses write-only calendar access. iOS 16 requires the older read/write permission even though ThinkOS does not read existing events. Android uses the system insertion interface without requesting calendar read/write permissions. Your calendar provider may sync saved events according to device settings. |
| Network requests, technical logs and app update information | Used by the workspace server, network infrastructure and Expo update service to connect, deliver compatible updates, diagnose errors and protect the service. |
| Selected text for read-aloud | Device TTS uses installed system voices without uploading text. When you select API TTS and press Read, the selected text (up to 3,500 characters) goes through ThinkOS to OpenAI gpt-4o-mini-tts for an AI-generated voice. Temporary playback audio is removed after playback or cancellation. No public download link is created. Downloading device language or voice packs initially requires internet access. |
Your choices
Voice, notifications and adding calendar events are optional. You can type instead of recording, check work in the app instead of receiving push, and decline device permissions. Change permissions in device Settings. The mobile app does not include advertising SDKs or Firebase Analytics, Firestore or Firebase Authentication. Additional organization-connected tools have their own settings and provider policies.
Storage and retention
Account and workspace records are kept while required for the active service and the organization's shared work. The app offers account deletion in Settings after password confirmation. This immediately removes the account profile, password, sessions, passkeys and push registrations. A temporary erasure case records the account identifier and request receipt while an administrator reviews personal information in submitted content and related copies. This identity mapping is removed when that case is completed. A one-way identifier digest is retained to prevent an unintentionally restored or reseeded account. For requests made without the app, we verify account ownership first. We explain the scope and handling timeline for remaining records. Shared organizational records, legal obligations or disputes may require restricted retention of some information; we explain the reason where applicable.
Connection logs are kept as needed for security and troubleshooting. Backup copies expire through the workspace's configured backup rotation rather than immediately on sign-out. Previously completed deletion requests must be reapplied if a backup is restored.
Signing out removes the local session, not server records. Native form drafts are cleared on sign-out. The shared web workspace keeps account-scoped drafts and display preferences between visits; remove those drafts or clear the workspace's website data when using a shared device. Temporary voice recordings and temporary upload/share copies are cleaned up during normal processing. Interrupted processes can leave cached files until cleanup. Files you save or share to another app are outside ThinkOS's control.
Deletion of a local ThinkOS copy does not mean a third party deletes its copy at the same time. OpenAI, Anthropic, Expo, Google and Apple process data under the services, account settings and terms used by your workspace. Processing may occur outside your country. Do not send information you are not authorized to share.
Access, correction and deletion
Contact your administrator or wisarut@thinkverse-ai.com to request access, correction or deletion. See account and data deletion for the request process. Do not include passwords or one-time codes. We may update this policy when the service changes and show the effective date on this page.