PRIVACY
Privacy notice
Updated November 17, 2026.
Vibedoro is a Mac app for organizing your day, focusing, and reviewing your progress. This notice explains how the app, this website and support handle information.
Vibedoro is developed and operated by Shuhao Yao. For privacy questions or requests, email dexter.yao23@gmail.com.
Your focus data
Vibedoro stores your goals, daily tasks, focus history, settings, project links and message-count records on your Mac. Manual planning, focus and Review work without a Vibedoro account. Your archive stays on your Mac. Restoring an App Store purchase does not restore or synchronize your local history.
When you choose Export data in Settings, Vibedoro writes one timestamped JSON file, vibedoro-export-YYYYMMDD-HHMM.json, to a folder you select, so you or your own agents can read them. Vibedoro keeps a bookmark to that folder to write later exports, does not read other files in it and does not send the export anywhere.
Optional AI planning
Before you send your first AI planning request in a session, Vibedoro asks for permission to share planning information with its cloud service and OpenAI. A request includes what you type, the date and time zone you’re planning for, and the tasks, time blocks, occupied times and intended outcomes used for that day. It may also include applicable goal names, a clarification you answered or up to four recent messages about the same draft. The request excludes your full archive, focus history, Review notes, agent transcripts, project paths, sign-in credentials and purchase details. You decide whether to save the suggested plan on your Mac.
The planning service runs on Google Cloud. It makes an encrypted suggestion available for up to 15 minutes after submission so your Mac can retrieve it after a connection problem. A delivery confirmation clears the live copy. Expired suggestions become unavailable for retrieval and are eligible for background removal. Firestore keeps one hour of version history separately from the retrieval window.
Vibedoro asks OpenAI to generate a suggestion without storing a reusable API response object. Under OpenAI’s default controls, its abuse-monitoring logs may contain prompts and responses for up to 30 days. OpenAI can keep them longer where legally required or needed to prevent harm. OpenAI may also use temporary prompt caching. For details, including its API training policy, see OpenAI’s API data controls.
We keep technical information for troubleshooting, usage accounting and service security. This can include a random request reference, processing stages, error types, latency and model usage. LangSmith receives these trace details without plan or chat text. Standard traces have a 14-day retention tier. Google Cloud request logs may include the source IP address, request path and status. Ordinary Cloud Logging records are kept for 30 days and required Google Cloud audit logs are kept for 400 days.
Signing in for AI planning
Apple or Google verifies the sign-in you choose. We receive a provider account reference and verified profile details, such as a name or email when available. We use them to maintain your account, session and cloud planning access. Your Mac stores its Vibedoro session credential in the system Keychain. Apple and Google have separate Vibedoro sign-in records. With Google sign-in, Google’s SDK may process account data, such as your name, email or phone number, account or device identifiers, approximate location and usage information for its sign-in, security and SDK analytics purposes. See Google’s sign-in disclosure.
Local agent information
You can use focus without connecting any agent. Codex is the native supported agent. When you choose Connect in Settings, a macOS folder picker asks you to select its expected source folder. Vibedoro stores a local, read-only folder bookmark. It does not modify Codex records, send agent messages or approve requests.
Claude Code is also optional. Vibedoro detects supported terminal and desktop installations using limited application and executable metadata, without reading credentials or transcripts. Detection does not grant access. When you choose Connect Claude Code, a separate macOS picker asks you to select the actual ~/.claude folder. A read-write app-scoped bookmark permits merging and removing only Vibedoro’s bundled hooks in settings.json, preserving unrelated configuration, and the publisher’s limited session reads. Installation, repair and removal require your explicit action. Vibedoro does not download code or install a background service.
Claude invokes this bundled publisher through its hooks. The publisher reads only the named session transcript within the authorized folder, identifies user-authored messages locally and retains message identifiers, reading progress, project references and cumulative counts, rather than message bodies or credentials. It writes a sanitized local export inside Vibedoro’s container; the resident app reads that export instead of scanning native Claude transcripts. An existing external publisher is not silently taken over. The current bundled publisher supplies message counts; it does not infer sessions, waiting states or quota.
Other coding agents and personal assistants can use the optional copyable connection prompt in Settings. Your own agent can publish a sanitized JSON file in ~/.vibedoro/agents; after you choose Connect Agent exports and select that folder, Vibedoro reads it through a separate read-only grant. Copying the prompt does not run code, grant folder access, install a skill or provide a login credential. The agent should explain any additional tool, background refresher or permission it needs before you enable it. That agent’s own authentication and data handling remain under its applicable terms.
Exports may contain the agent’s display name, supported capabilities, session identifiers, activity, waiting-session titles and native links, quota windows and aggregate user-message counts grouped by project and conversation. They must not contain passwords, login tokens, account identifiers or message bodies. Agent connections do not read agent credentials or Keychain records and do not send agent quota requests. Reliable quota evidence may be unavailable, in which case no quota is shown.
For native Codex message counts, an embedded helper reads message text locally to determine what counts as a user-authored message. Its ledger retains counts, reading progress, deduplication information and project references, rather than message text. Integration counts are stored separately as cumulative conversation revisions. Newer revisions replace that conversation, while missing conversations stay saved. Completeness evidence is bounded and specific to each source. Some records include local folder paths or identifiers associated with projects and conversations. The native helper can inspect directory metadata to identify a project; reading Git file contents is limited to granted source folders. Integration project paths do not cause additional folder grants or repository reads.
Removing an original transcript or an integration export does not remove counts already retained by Vibedoro. Repeated scans do not add the same integration counts again. Missing, expired or incomplete evidence remains unknown rather than idle or zero. Existing historical Claude message records remain readable.
App Store purchases
Subscriptions are handled by Apple through the App Store. Vibedoro uses verified StoreKit transaction and renewal information to determine subscription access. It processes product and transaction identifiers, environment, expiration, grace and revocation information in memory. It does not save a separate local license or order database, raw signed transactions or purchase identifiers in its local state files or diagnostic logs. Restoring purchases explicitly asks Apple to synchronize purchase information; it does not upload local focus history. Payment card and bank details entered with Apple are not provided to Vibedoro. Apple processes purchases under its applicable privacy policy and Media Services terms.
Local subscription access is verified with StoreKit. Apple handles the payment. The developer may receive Apple’s sales and financial reports; those reports do not contain your Vibedoro goals or transcript text.
When you enable AI planning, our cloud service verifies eligible App Store transactions with Apple. It records subscription ownership and status and the usage needed to count delivered AI rounds. We keep these records to verify access and prevent duplicate claims. Apple handles billing and does not send us card or bank information.
Diagnostics and sound
To hide the island during fullscreen viewing, Vibedoro reads macOS presentation flags and on-screen window geometry locally. It does not read window titles or webpage content, capture images, retain this temporary information or send it anywhere. This feature does not request Screen Recording or Accessibility permission.
Vibedoro writes local diagnostic events containing technical reason codes and timing information. Its diagnostic logs do not contain goal names, task text, conversation titles, project paths or login tokens, and are not automatically uploaded. Each app and helper log stream rotates by size, keeping the current file and two older generations. macOS also manages its own system diagnostic records.
Soundscapes are included with the app and play locally. Listening does not download audio or record sound from your microphone.
This website
This website provides product information, demonstrations and help. It has no checkout, user accounts or app-data synchronization. It does not use advertising pixels. Fonts are served from the site. Animated interactions are processed in your browser without being saved as a user activity record.
Optional website analytics
If you choose “Allow analytics”, this website loads Google Analytics to understand page visits, referral sources and general usage. Google receives technical information such as your IP address, browser and device information, page address and cookie identifiers. We omit URL query parameters and fragments from the page addresses we send, and send only the origin of a referring site. We disable Google Signals, advertising personalization and enhanced measurement. We do not send the app’s goals, tasks, focus history or Agent data to Analytics.
Before you allow analytics, or if you decline, we do not load the Google tag or send analytics requests. Your choice is stored in this browser for up to 180 days. You can reopen “Analytics preferences” in the footer and decline at any time; this stops future collection and removes this site’s Analytics cookies. It does not erase data already received by Google. User-level and event-level data retention is set to two months without resetting on new activity; aggregated reports may persist longer. Google may process data outside your country. See Google’s privacy policy and its Analytics data practices.
The current hosting provider, Vercel, receives request information such as your IP address, requested URL, browser information and request time to deliver and protect the site. Vercel may process information outside your country. Its privacy notice explains its practices. Vercel determines retention for its delivery and security records. We do not keep a separate website visitor log or export these records to another service.
Support messages
If you contact support, the recipient receives your email address, message and any attachments you choose to send. These are used to respond to your request. Please leave out passwords, login tokens, full transcripts and private project details. Support does not automatically receive the app’s local records.
The contact mailbox uses Gmail, provided by Google, which processes mail under its applicable privacy policy; processing may occur outside your country.
Your choices
You can decline cloud planning and continue planning manually. Signing out ends the Vibedoro session on this Mac. To delete the AI planning account, choose Settings → Subscription & Account → AI planning account → Delete Account and verify the same sign-in method. This ends access, revokes active sessions and starts removal of linked account and usage records. We can retain a detached purchase reference to prevent reuse of that purchase. Provider records and audit logs follow the retention terms described above. Your plan and focus archive stay on this Mac. Manage Apple subscription renewal separately in the App Store.
You decide whether to connect Codex, Claude Code or the Agent exports folder. Main and Settings rescan connected sources about every 20 seconds, Settings offers a manual refresh, and Review normally refreshes message counts every five minutes. Deep focus hides agent information and pauses all new agent reads by Vibedoro, including manual refresh; a bounded read already in progress may finish. It does not silence other apps or pause agents. Quitting Vibedoro stops its readers and native Codex helper. Claude’s independently invoked publisher can still run while Vibedoro is closed or in Deep focus.
For a managed Claude connection, choose Remove in Settings → Agents. Vibedoro removes only its recorded hooks and live export and disables that managed grant; it preserves unrelated Claude settings, native transcripts and retained message counts. Repair or reconnect explicitly to resume the managed connection. For a generic integration, remove its own updater configuration and export file; a complete rescan removes it from live monitoring. Codex and generic export connections have no bookmark-removal button. Disconnecting does not erase saved history, and the app does not automatically delete it.
Local focus history and message summaries do not expire automatically. Deleting the app itself does not necessarily delete its local data. We do not have a server copy of your local history to retrieve or erase. Information you choose to send to support is separate from the records on your Mac. Depending on applicable law, you may have rights concerning access, correction, deletion and other handling of information received through AI planning, the website or support, and a right to complain to your data protection authority.
