Privacy

C0VIBE is run by Better Digital LLC. It includes the website at c0vibe.app and the desktop app.

Questions, export requests and erasure requests go through the partnership page. Postal address and the name of the responsible person: to be added before this page leaves draft.

We collect the data listed below. Each part of the product only collects what that part needs.

• Waitlist and membership application: when you submit your card on c0vibe.app, we store your email address, chosen handle, the card fields you fill in (discipline, age, city, what you build, what you are looking for, optional X handle and project notes), a hashed IP address for abuse prevention, and your browser user agent.
• Account and sign-in: your email address, your handle and display name, and the identifiers our sign-in provider returns.
• Birth year: we ask for your birth year when you join. We keep the year only, never the full date of birth. The rules for age are in the terms.
• Profile: the fields you fill in, such as bio, avatar and profile photos. Your public profile page can be seen by anyone.
• Posts, follows and reactions: what you post, who you follow, which organisations you belong to, and the reactions you give. Follows, organisation memberships and post reactions can be read by anyone through our database. Do not put private information in them.
• Chats and direct messages: the messages you send and receive. They are stored so they can be shown to you and to the people you send them to.
• Voice and dictation audio: when you dictate, the audio is processed on your device, or sent to a speech provider if you choose a cloud mode. See AI processing below.
• Screen capture: when you use C0CAP, the captures you take are processed on your device. A capture is sent to a provider only when you use a feature that needs one.
• Camera and microphone in calls: in a C0LINK room, your camera and microphone streams go to our real-time media server so the people in the room can see and hear you. Room presence is shared with your friends through SpacetimeDB.
• Uploads: files you upload, such as avatars, profile photos and shared files, are stored in our storage. Profile photos and avatars are public on your profile.
• Payments: payments are handled by Polar. We receive the subscription record (plan, status and dates). We never receive or store card numbers.
• Error reports and telemetry: see the section on telemetry below.
• C0MAIL: your mail account settings and message content stay on your device. We do not receive them.
• Country: the country your connection comes from, taken from the request headers our hosting provider adds. Some C0LINK sessions use it to apply country rules. We do not collect precise location.

We use your data to run the service you asked for, which is the contract between you and us (or steps you ask us to take before entering that contract, such as reviewing your membership application and sending your decision email). This covers applications, sign-in, your profile, your chats, payments and calls.

Sharing anonymous data to help improve the app, including our own models, is optional and off by default. We appreciate it if you do. You can turn sharing off in Settings at any time.

We rely on our legitimate interests for security, preventing abuse, and fixing errors in the product. We weigh these against your rights.

We keep some records because the law requires it, or because a lawful request or a legal hold requires it.

Some features send content to AI providers so they can answer you or make something. What is sent depends on the feature and the model you choose.

• Chat and assistants: your messages go to the model provider you choose, through our routing service or directly.
• C0LINK AI members and the Core Agent: the text needed to answer goes to the model provider that runs the member or agent.
• Speech: cloud dictation and realtime voice send audio or text to Groq, OpenAI or Cohere, and text-to-speech to OpenAI, ElevenLabs or Fish Audio, depending on the mode.
• Images and video: prompts and reference images go to the image or video provider used for that feature.
• Web search and the browser agent: search queries go to a search provider. Pages the browser agent opens go to our browser provider.
• Your own key: if you use your own API key, your content goes from your device to that provider under its terms. It does not pass through our key.

We use service providers, called subprocessors, to run C0VIBE. Each one receives only what its feature needs. The full list, with what each one receives, why, and where it runs, is on the subprocessors page.

Sharing anonymous data to help improve the app, including our own models, is optional and off by default. We appreciate it if you do.

Community training shares dictation corrections only. Switch it on in the desktop app under Settings, Keys and privacy, Data and analytics. Single words sends dictionary words only. Corrections with context includes a short context. Personal details are filtered on your device. You approve context before sharing it. Word patterns need 10 different sources before use. Context patterns need 20.

The team can export aggregated patterns to improve the app and our own models. We do not sell or broker data. Single contributions are not published.

Core Agent community pool: this is opt-in. When you share, it sends how a workflow ran: the route shape, the kind of task, the number of steps, a duration range and the success rate. It never sends what the task was about. A group of results is published only when at least five different contributors have sent it. Raw rows are deleted after 180 days.

You can turn either option off at any time. Turning it off stops future sending. It does not remove data that was already accepted, except as described in your rights below.

Crash and error reports are always on, for every plan including Free, and you cannot turn them off. When the app hits an error, it sends a report so we can fix the fault. Before a report leaves your device, folder paths, your user name and email addresses are removed. It does not include your documents, your account ID or anything that identifies your computer. To count repeats of the same fault, it carries a random number the app made when it was installed, which is not linked to your device, your name or your account. We keep each report for 30 days after its last occurrence, and then delete it.

C0re, the Core Agent, sends one of these reports whenever a step it tries fails, even if it then finishes your request another way. The report lists the name of each failed step, its error code, how often it failed and whether the request still finished. It adds the app version, the module you were in, how you signed in (for example email or WorkOS) and which kind of AI brain ran the request. Nothing else.

Performance telemetry is on by default, on every plan, and you can turn it off in Settings under Data and analytics. It sends bucketed start-up timings, frame stalls and a broad device class, never content, text, host names, paths or hardware IDs. Dictation performance telemetry is off unless you turn it on. Full Core Agent traces, which hold more detail than these reports, are off unless you choose to send them.

Usage aggregates you choose to upload are stored as totals, not as your individual sessions.

The website sets two cookies that sign-in needs: one for your sign-in session, which lasts up to 30 days, and one that checks the sign-in response. These are essential. The website sets no analytics or advertising cookies.

The website uses browser storage for small interface choices, such as a dismissed banner, a sidebar toggle, or a draft of your card on your own device before you submit it. It sends page speed measurements to our own server. We write these to logs and do not keep them in a database.

Your account data and content are kept until you delete your account or the item. Settings → Privacy & Data lets you request immediate erasure by typing DELETE MY ACCOUNT. A legal hold in c0vibe_legal_holds prevents erasure: we show the reason and record the request for handling when the hold ends. Some records must be retained where legally required. There is no seven-day waiting period.

• Waitlist and membership applications: kept until your application is reviewed and turned into an account invite, or until you ask us through the partnership page to delete your application.
• Error reports: 30 days after the last occurrence.
• Core Agent community pool, raw rows: 180 days. Published results use only the last 90 days.
• Safety records: kept under a legal hold when an account is reported for child safety or closed. A deletion request is recorded and carried out when the hold ends.
• After a closure: we keep a keyed hash of the email address, so the same person cannot open another account.

Reports, moderation decisions and their reasons are stored so a person can review them and you can appeal. For AI features that run on our keys, we record when a model provider refuses a request for child-safety or hate reasons: the category, the feature and a fingerprint of the request. For a child-safety refusal we also keep a short excerpt for the reviewer.

An account under a child-safety report, and a closed account, is kept under a legal hold. We answer lawful requests from authorities.

Under the GDPR, the Swiss Federal Act on Data Protection (nFADP) and similar laws, you can ask us for access to your data, correction of it, erasure, a copy you can take with you, and an objection to some uses.

Export: the app can export all of your data as a machine-readable file.

Erasure: the app can erase your account and your data. You confirm with the phrase DELETE MY ACCOUNT. Accounts under a legal hold are erased when the hold ends.

California (CCPA and CPRA): you can ask what we hold, ask us to delete or correct it, and opt out of sale or sharing. We do not sell personal information, and we do not share it for cross-context behavioural advertising.

You can also complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC), or to the data protection authority where you live.

C0VIBE is for people who are 18 or older. We do not knowingly collect data from children under 13. If you believe a child has an account, write to us through the partnership page and we will act on it.

When you join a room, the birth year you give is checked against the minimum age for that room. We keep the birth year as described above.

When we change what we collect or who receives it, we update this page and the subprocessors page. The date of the last change is shown at the top of this page once the page leaves draft.

Privacy questions, export requests and erasure requests go through the partnership page.