Last updated: November 5, 2026
Corked Labs, LLC (“we,” “us,” or “our”) operates the Corkulous website, apps, CLI, and related Credits service. This policy explains the information involved in those services and your choices. Corked Labs is responsible for the personal information we collect to operate them. Contact us about privacy at [email protected] or through our contact page, selecting Support and describing your privacy request.
We do not sell personal information or share it for targeted advertising. This policy explains processing; using the Service is not blanket consent to processing that requires separate permission.
Boards on your devices and storage services
Corkulous stores boards on your device and, when you choose them, in your iCloud or Dropbox storage. We do not automatically upload your whole board library to the Credits service. Device backups, folders shared with other people, and the settings of your chosen storage provider affect where copies exist and who can access them.
AI features, exports, sharing, support submissions, and connected assistants can send board content outside that storage. For example, asking the Agent about a board may send its text and other relevant context as part of the request. Local storage does not make an AI request or a shared export local-only.
Apple handles your Apple account and optional iCloud storage under its own policies.
Optional Dropbox storage
Linking a Dropbox account is optional. When you link it, Corkulous uses authorization tokens to access the account and file operations you authorize; Corked Labs does not receive your Dropbox password. The app reads account information, such as your display name and available storage, and file metadata to show the connection and synchronize your boards.
Boards you choose to keep in Dropbox-backed collections are uploaded to and stored by Dropbox. Changes to those boards can synchronize automatically. The uploaded board files can include board text, notes, images, PDFs, and imported or recorded audio and video, along with backups kept in those collections. Linking Dropbox does not by itself upload every board stored elsewhere on your device.
Dropbox processes the linked-account identifiers, uploaded files, file metadata, and information about API requests involved in this connection. Dropbox’s SDK documentation describes collection of user IDs, product-interaction information, and diagnostic API-call logs. It lists app functionality and analytics uses for user IDs, app functionality, analytics and product personalization for product interactions, and app functionality for diagnostic logs and uploaded content. This processing is associated with your Dropbox account; it is separate from the Credits service’s handling of AI requests.
Dropbox’s handling of this information, including retention, file versions, backups, sharing, and account controls, follows its Privacy Policy and the terms and settings of your Dropbox account. You can disconnect Dropbox in Corkulous or revoke the app’s access through Dropbox. Disconnecting the integration or deleting a Credits account does not delete files, versions, or backups already held in Dropbox; use Dropbox’s own controls to manage those copies.
Website visits, security, and support
- Hosting and traffic: Cloudflare hosts and protects the website and may process request information such as IP address, browser details, timestamps, and requested URLs. Traffic reports available to us are aggregated. We do not add advertising trackers.
- Fonts: Pages load DM Sans and Fraunces from Google Fonts. Your browser sends Google the font request and associated information such as your IP address, browser details, and referring page. See Google Fonts privacy information.
- Browser preferences: The website saves your light/dark theme choice in browser local storage. You can remove it through your browser’s site-data controls.
- Contact-form protection: Cloudflare Turnstile processes browser and request signals to distinguish legitimate submissions from abuse. Our verification sends the challenge token and connecting IP address to Cloudflare. Cloudflare security features may use cookies or similar storage depending on configuration. See the Turnstile Privacy Addendum.
- Support messages: The contact form sends your name, email, request category, message, optional referral information, and submission time to our GitHub-based support workflow. Information you choose to email or send for troubleshooting is also used to respond and investigate. Please omit passwords, API keys, and unnecessary sensitive board content.
- Tutorial videos and outside links: Documentation links to third-party services. Following a video link takes you to YouTube, which processes your visit under Google’s privacy policy. Your use of linked services is governed by their policies.
Credits accounts, purchases, and service records
An AI Credits account uses your email address and email magic links. We process account and session identifiers, sign-in and delivery events, wallet balances and ledger entries, and records needed to verify App Store purchases and entitlements. Postmark delivers transactional sign-in messages and reports delivery status. Apple handles payment information; we receive purchase verification data such as transaction and product identifiers, purchase environment, and verification results, not your full payment-card details.
Requests may also produce technical records: request identifiers, timestamps, status and error codes, app and feature identifiers, provider/model choices, usage and pricing information, cancellation and settlement records, IP addresses, user agents, and device or network hashes used for security and abuse prevention. Hashing an identifier does not necessarily make it anonymous.
Some subscription or purchase verification records can be created before Credits sign-in so the app can register an entitlement and later link it to the appropriate account. Signing out ends the current session; it does not erase the wallet or those records.
AI requests and third-party processing
Before using AI: The feature can send your prompt, included board or conversation content, selected attachments, and tool requests to external providers. Providers may retain inputs, generated outputs, and technical records under the policies, API terms, and agreements that apply to the service. Read the provider privacy and data-use links below before sharing information you consider private or confidential.
What may be shared
The data sent depends on the feature, selected context, attachments, enabled tools, and provider route:
| Feature | Data the services involved may receive |
|---|---|
| Board generation, Agent conversations, and summaries | Your prompt, board text or other board context included in the request, conversation history included in the request, and attached files or extracted content. |
| Image, audio, music, and video generation | Generation instructions, narration text or lyrics, any reference media supplied to the feature, and generated output. |
| Web research and page retrieval | Search queries, URLs, and relevant context passed to a search/retrieval tool. A query can contain information from your prompt or board. Retrieved material can then be sent to the model answering your request. |
| Connected assistants | Board contents and metadata returned through tools, which the assistant may send to its own providers and keep in its conversation history. |
Providers can also receive API-account identifiers, request and usage information, and network details associated with the connection. A request through the Credits gateway and a direct request from your device expose different connection information. A workflow can use more than one provider, such as a text model, a media generator, and a search service. Your entire library is not sent to every listed provider simply because you use Corkulous.
Credits mode
Your request passes through our gateway to the providers and tools needed to perform it. It can include your prompt, relevant board content or conversation context, selected attachments, media-generation instructions, and search queries or URLs. Generated output returns through the service for delivery to the app and credit settlement.
Routes depend on the feature, tier, and current service configuration. They may involve OpenAI, Anthropic, Google, xAI, ElevenLabs, and search or retrieval services used by the feature. Enabling web tools can send queries or URLs to additional providers or destination websites. Third-party services may receive request and network information and apply their own policies.
Asynchronous board generation temporarily stores request data and results so the app can poll, recover from connection interruptions, and import the result. Selected attachments and generated media may also be held temporarily in private object storage for processing or delivery. These copies are not a permanent board backup. See Retention below.
We process limited request metadata to authenticate requests, prevent abuse, diagnose failures, and settle credits. Before board, image, narration, and music requests run, the prompt or narration text is sent to OpenAI’s moderation service, even when another provider handles the request. Safety checks can retain decisions, category signals, prompt hashes, character counts, and request identifiers. The production service disables the optional capture of raw provider-failure output as diagnostic artifacts; temporary job data needed to complete and deliver a request is separate from those diagnostics. Test environments can have additional diagnostic capture enabled.
Provider Mode and the CLI
Provider Mode (on Mac and on iPhone and iPad running iOS or iPadOS 26 or later) and CLI AI generation (on Mac) use your own provider accounts. AI requests go from the device to the selected providers and enabled tools, rather than through the Credits gateway. The providers’ account terms, retention settings, and charges apply. Web searches, fetched pages, and remote media can contact additional services.
The main app stores its Provider Mode keys in the device Keychain. The CLI and its settings/menu bar helper use separate configuration: keys you save there are stored in the local ~/Library/Group Containers/group.com.corkedlabs.corkulous/CLI/config.json file (earlier versions used ~/.config/corkulous/config.json), or read from environment variables. That file is not Keychain storage or an encrypted vault. Protect it from other users, source-control commits, shared backups, and diagnostic uploads. API keys are sent to the provider or tool they authenticate, not to our Credits service by the ordinary Provider Mode flow.
Connected assistants, MCP, Shortcuts, and exports
When you connect an assistant to Corkulous through MCP, it can list and read accessible boards, export content, and create boards using the exposed tools. The MCP connection runs locally, but the assistant can send the content it reads to its own cloud/model provider and keep it in chat history or logs. A local MCP connection is not a promise that board content stays on your Mac.
A Corkulous board passcode is an in-app access control, not file encryption; it does not prevent a connected tool with file access from reading the underlying board. Review the assistant’s permissions and data controls. Disconnecting Corkulous stops that configuration from providing future access; it does not erase copies already held by an assistant, provider, recipient, or backup. Shortcuts and exported files can likewise disclose content to the other apps and destinations you choose.
Provider policies
A provider may keep data after your request finishes. Retention, deletion, safety review, human access, model-training or improvement use, and zero-retention eligibility depend on its product, API feature, account settings, and applicable agreement. A “not used for training” statement does not mean “not stored.” We do not promise zero retention across all providers or features.
Review the current documents below for the providers involved in your feature. API/business terms can differ from consumer-chat policies. In Credits mode, requests use Corked Labs’ provider accounts and agreements; settings in your personal ChatGPT, Claude, or other consumer account do not necessarily apply. In Provider Mode and the CLI, review the settings and terms of the account associated with your own API key, including any differences between paid and free services.
| Provider | Use in Corkulous, when selected or routed | Privacy and API data information |
|---|---|---|
| OpenAI | AI text, media, supported web tools, and automated safety checks | Privacy policy · API data controls and retention |
| Anthropic | AI text and supported web tools | Privacy policy · Commercial/API retention |
| AI text, media, and supported web tools | Privacy policy · Gemini API data-use terms | |
| xAI (SpaceXSI) | AI text, media, and supported web tools | Privacy policy · API security and retention |
| ElevenLabs | Narration and music | Privacy policy · Data-use settings · API zero-retention eligibility |
| Brave | Optional web/image search | Search API privacy policy |
| Firecrawl | Optional search and page retrieval | Privacy policy |
| Perplexity | Optional research/search answers | Privacy policy |
For connected assistants, also review the assistant service’s policies and account controls: Anthropic for Claude Desktop/Claude Code, OpenAI for Codex, and Cursor. Their handling of a chat or coding session can differ from Corkulous’s direct API calls. Other assistants, tools you configure, and websites reached through HTTP Fetch have their own policies.
Deleting a board, disconnecting a provider, or deleting your Corkulous Credits account does not automatically erase copies already held by a provider or assistant. Those copies follow the applicable retention and deletion arrangements. Contact us about data sent through Credits mode; for your own provider or assistant account, also use that service’s privacy controls and request process. We remain responsible for our handling of personal information and applicable obligations described in this policy.
Why we use information
We use information to provide requested features; authenticate users; maintain balances and histories; verify purchases; respond to support; detect abuse and security problems; diagnose failures; and meet legal obligations. We do not use your boards or prompts to build our own general-purpose AI model or to target advertising.
Where the EEA or UK data-protection framework applies, the relevant bases are performing our agreement with you for requested services; legitimate interests in securing, maintaining, and supporting the Service; and applicable legal obligations for required records. Where a feature requires consent, we request it separately and you can withdraw it. Information necessary for sign-in, payment verification, or a requested AI operation is needed to provide that operation; you can use available offline features without creating a Credits account.
Automated safety and abuse checks may reject requests or restrict service access. Contact us if you believe a restriction is mistaken so we can review it.
Retention and account deletion
We keep information for the purpose for which it is needed, taking into account service delivery, unresolved support requests, security investigations, refunds and purchase reconciliation, and legal recordkeeping requirements.
- Boards and exports: Copies on your devices, in your chosen cloud storage, and with recipients follow those locations’ backup and deletion settings. Credits account deletion does not delete them.
- Temporary AI data: Board jobs have a processing timeout and a separate result-import window. The current default result window is 30 minutes after completion, with earlier removal possible after successful import. Attachments and generated media have feature-specific expiry and cleanup paths. Expiry makes data eligible for cleanup; it is not a promise of immediate erasure from every copy or third-party system. Temporary service storage is not long-term account content.
- Account and wallet records: We retain data needed to provide the account while it remains active. In AI Settings, open the Credits sheet, choose Delete Account, and type
DELETEto request permanent deletion of Corkulous-scoped account data, including the wallet balance and associated temporary objects. Contact us if the control is unavailable. - Retained records: Deletion is subject to limited legal, accounting, refund-reconciliation, fraud-prevention, and security needs. For example, transaction and welcome-award eligibility records may remain to prevent replayed purchases or repeat awards. We limit retained data to those purposes. Signing in again does not restore a deleted wallet or make a previously used welcome offer new.
- Support and technical records: Retention depends on resolving the request, diagnosing the problem, protecting the service, and any continuing legal need. You may ask us to delete support information that is no longer needed. Providers may retain their own records under their policies.
Deletion applies to Corkulous’s Credits account. An account for another Corked Labs app is separate. Deletion does not cancel Apple subscriptions or issue refunds; use Apple’s subscription and refund controls separately.
Service providers and international processing
Our providers include Cloudflare for hosting, security, database and temporary object storage; GitHub for support tracking; Postmark for transactional email; Apple for purchases and optional iCloud storage; Dropbox for optional linked-account file storage and synchronization; and the AI, search, and assistant services described above.
We and these providers may process information in the United States and other countries where their systems operate. Protections can differ from those in your country. Where transfer rules apply, the transfer must have an applicable legal basis and safeguards. Contact us for information about the arrangements applicable to your data; this policy does not claim that every provider or route has the same certification or data location.
We may also disclose information when required by law, to address fraud or threats to safety, or to establish or defend legal claims. If the Service is transferred to a new operator, relevant information may transfer subject to applicable notice, privacy, and legal requirements.
Your choices and rights
You can choose your storage location, control device permissions, disconnect assistants and cloud integrations, avoid sending particular content to AI, sign out, and request account deletion. Removing an integration does not itself delete copies held elsewhere.
Depending on your location and applicable law, you may request access, correction, deletion, a portable copy, or restriction of processing. You may object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. You may also complain to your local data-protection authority; UK residents can contact the ICO.
Email [email protected] or use our contact page for a privacy request. We may need proportionate information to verify your identity and clarify the request. We will respond within the period required by applicable law and explain any lawful limitation. We do not penalize you for exercising applicable privacy rights.
Security and children
We use HTTPS for connections to our website and Credits service and access controls for service records. No system, device, or transfer is completely secure. Protect your devices, email account, API keys, backups, and sharing permissions.
The Service is not directed to children under 13, and we do not knowingly collect their personal information. A parent or guardian who believes a child has supplied information to us should contact us so we can investigate and take appropriate action. AI providers may set higher minimum ages. Schools and organizations must assess their own permissions and obligations before sending student or third-party data to an online feature.
Changes
We will date updates to this policy and provide additional notice or obtain consent when applicable law requires it. A new policy does not by itself authorize a materially different use of information for which separate permission is required.
