chalk
PrivacyTerms

Privacy Policy

Effective 6 November 2026

What's changing

We are clarifying mobile guest data, sign-in cookies, participation records, recording and transcription, diagnostic logs, problem reports, and our providers and international transfer safeguards.

The data-handling disclosures below describe current practice and apply when this page is published. The update date above does not delay these factual corrections. The Archived Privacy Policy is available only as a historical record.

Chalk is a real-time collaboration platform operated by Q9 Labs ("we", "us"). This policy explains what personal data Chalk collects, why, and what your rights are. It covers the Chalk web app at chalkmeet.com, the Chalk mobile app, and the APIs behind them.

What we collect

Account data. The web dashboard offers Google and Apple sign-in through Chalk's own server. We receive your provider user ID, name, email address, and, from Google when available, profile picture URL. We keep these details in an encrypted sign-in cookie for up to 30 days and store a tenant record tied to your provider user ID and display name. Older account records, including password hashes, tenant memberships, and roles, remain stored. The mobile app does not offer accounts or sign-in; you join as a guest with a display name.

Sign-in and security data. We use guest arrival credentials, participant IDs, and web session IDs to keep access working. We process IP addresses to rate-limit abusive traffic. For tenant API keys, we retain the most recent use's IP address and timestamp for security and audit purposes. Older sign-in records can include IP addresses, browser user agents, and device names.

Spaces, Episodes, and participation. Chalk stores the Spaces you create (names, settings, admission rules), the Episodes that run in them (timing and configuration), and participant records for each Episode: participant ID, display name, role, capabilities, and join and leave times. We also process in-app actions such as reactions and read receipts to keep participants in sync.

Chat and files. Messages you send in an Episode are stored with your display name and timestamps. Photos and documents you attach are stored as private objects with their filename, type, and size. Chat attachments are scheduled for deletion seven days after the Episode ends.

Audio and video. Your microphone, camera, and screen-share streams are processed in real time to deliver them to other participants. Media travels over encrypted connections. We do not store media streams unless recording is turned on for the Episode, and the product shows when that is the case.

Recordings and transcripts. Where recording or transcription is enabled, we store the recording files, transcript text, and processing metadata as private objects. Audio retained as a source for transcription follows the Episode's configured source window, which can be up to 30 days. Temporary transcription chunks and orphan files have a 24-hour expiration rule.

Whiteboards. We store whiteboard scenes and changes, including text, drawings, and images, so participants can collaborate. Whiteboard image files are scheduled for deletion seven days after the Episode ends.

Integrations and webhooks. If your tenant connects an external integration or configures webhooks, we store the connection metadata and deliver event payloads to the endpoints your tenant chose. Webhook target URLs, signing secrets, and payloads are encrypted at rest.

Operational data. We keep audit logs of administrative actions, structured request logs, and bounded diagnostic events (request path, route, outcome, duration, journey and trace IDs). These diagnostics can be linked to participation records through identifiers in request paths and trace context. We use these to run and secure the service, and we do not use them for advertising.

Cookies

Chalk uses only functional cookies. We do not use advertising or cross-site tracking cookies.

CookiePurposeLifetime
chalk_themeRemembers your light or dark theme preference (Client-readable)1 year
__Host-chalk_session, __Host-chalk_bindingKeeps your dashboard sign-in and binds requests to your session (HttpOnly, Secure)Up to 30 days, or until sign-out
__Host-chalk_login_google, __Host-chalk_login_appleProtects the sign-in exchange (HttpOnly, Secure)10 minutes, cleared after the callback
__Host-chalk_seat_{spaceId}Keeps your dashboard Space access (HttpOnly, Secure)24 hours; access also requires your signed-in session
__Host-chalk_space_guest_{arrival_handle}Keeps your public Space arrival available in this browser (HttpOnly, Secure)Until you leave or close your browser
__Host-chalk_space_starter_{arrival_handle}Lets you end a call you started if you leave it and rejoin (HttpOnly, Secure)Until the call you started is archived, one hour after it began

Who processes your data

We use these service providers and third-party services to run Chalk:

  • Cloudflare hosts the web app, routes API and asset traffic (including assets.chalkmeet.com), receives connection metadata such as IP addresses and user agents, carries real-time audio and video and screen sharing (Realtime SFU and STUN), and stores uploaded files, whiteboards, recordings, and transcripts (R2). Cloudflare Workers AI can perform speech-to-text when enabled in the transcription configuration.
  • Amazon Web Services hosts our API and real-time application services, processes the account, participation, and collaboration data handled by those services, runs the transcription pipeline (audio processing, job scheduling, secret storage, and logs), and provides recording encryption key management.
  • PlanetScale stores account and collaboration records in PostgreSQL, including account email addresses, display names, membership and participation records, chat, and whiteboard metadata.
  • DeepInfra receives audio chunks and returns transcript text to perform speech-to-text when enabled in the transcription configuration.
  • DigitalOcean runs recording workers that process call audio, video, screen sharing, and recording metadata when recording is enabled.
  • Axiom receives API request logs and Sync diagnostic traces, including request paths, outcomes, timing, and journey and trace identifiers, to help us run and secure the service.
  • Discord receives operational alerts that may include a tenant's display name. Our private Discord channel also receives problem reports you submit through Chalk: what you type, your display name and role, and the Space name and Episode ID. If you choose to include diagnostics, the report also sends connection status, last error code, browser or user agent, and app version. We do not add your account email address, server configuration, logs or server error text. Please do not include passwords or keys in your report. URLs beginning with http://, https:// or www. are sent as non-clickable text with query strings and fragments removed. Stack traces and commit IDs you include are kept.
  • Google sign-in lets you authenticate your dashboard account. If you choose it, your browser contacts accounts.google.com and our server exchanges an authorization code with oauth2.googleapis.com and verifies Google's keys from www.googleapis.com. Google receives the sign-in request, Chalk's application identifier and callback URL, security state and nonce, and your browser's IP address and user agent. Google returns the account identity you authorize, including name, email address, and an optional profile picture. Google's own Privacy Policy governs its sign-in service.
  • Apple sign-in lets you authenticate your dashboard account. If you choose it, your browser and our server contact appleid.apple.com for sign-in, an authorization code exchange, and key verification. Apple receives the sign-in request, Chalk's application identifier and callback URL, security state and nonce, and your browser's IP address and user agent. Apple returns the account identity you authorize, including name and email address, which can be an Apple relay address. Apple's own Privacy Policy governs its sign-in service.
  • External whiteboard content. If you add or open an external embed or link in a web whiteboard, its host can receive your IP address, user agent, requested URL, and any referrer your browser sends. Excalidraw supports hosts including YouTube (Google), Vimeo, Figma, GitHub Gist, X/Twitter, Reddit, Giphy, SimplePDF, StackBlitz, Val Town, and Excalidraw's link service. Those hosts use this data to serve the content you selected under their own privacy terms. This is separate from Chalk's call-media processing; the mobile whiteboard blocks external embeds and network requests.

We do not sell personal data or share it for advertising or tracking. Apart from the providers and third-party services listed above, content you send to other participants, and integrations your tenant chooses, we disclose data only when the law requires it.

Legal bases

We process account, sign-in, and content data to perform our contract with you. We process security and operational data in our legitimate interest of keeping the service safe and reliable. Where we rely on consent (for example, a recorded Episode), you can withdraw it going forward at any time.

Recording notice

Recording and transcription depend on the Space settings and can start automatically or on request. Chalk shows participants when an Episode is being recorded. If you record, you are responsible for having the agreement of your participants under the laws that apply to you.

Retention and deletion

Account records remain stored until deleted. Space, Episode, and participant records (including participant ID, display name, role, and join and leave times) are kept while the tenant that owns the Space exists and are deleted from active systems when that tenant is purged. This includes web and mobile guests, even after they leave an Episode; the seven-day collaboration cleanup does not delete these records. Chat messages, read receipts, whiteboard scenes and changes, and their attached files are scheduled for cleanup seven days after an Episode ends. Recordings and transcripts follow the retention policy set for the Episode by its tenant. Webhook event bodies, deliveries, and attempt logs are scheduled for cleanup after 30 days. Endpoint settings and revision history remain while the endpoint is active; after deletion, cleanup is scheduled after 30 days once delivery references are removed, or when the tenant is purged. Log retention depends on the service and its configured provider settings. To request deletion of your web account or content, or your mobile guest data, email [email protected] with enough detail to identify it (for example, the Space link, display name, and approximate date). We will delete or anonymize the data in active systems within 30 days. Backup copies may remain longer; tenant-deletion archives are retained for at least 14 days. Problem reports remain in our Discord channel until we delete them; Chalk does not automatically expire problem reports. You can request deletion at [email protected].

Your rights

If you are in the EEA, the UK, or a similar jurisdiction, you have the right to access, correct, export, and delete your personal data, to object to or restrict certain processing, and to complain to a supervisory authority (in Norway, Datatilsynet). Write to us at the address below and we will respond within the legal deadline.

International transfers

Our providers operate globally, so your data can be processed outside your country. For transfers outside the EEA, Cloudflare and DigitalOcean rely on the EU-US Data Privacy Framework adequacy decision for covered transfers to their certified US entities, with EU Standard Contractual Clauses in their data processing addenda as a fallback. Amazon Web Services, PlanetScale, and Axiom use the EU Standard Contractual Clauses in their data processing addenda for transfers to countries without an EU adequacy decision. Discord relies on the EU-US Data Privacy Framework adequacy decision for covered transfers to its certified US entities and EU Standard Contractual Clauses for other applicable transfers. Google relies on the EU-US Data Privacy Framework adequacy decision for covered transfers to its certified US entities and EU Standard Contractual Clauses for other applicable transfers. Apple describes EU Standard Contractual Clauses for international transfers of EEA personal data in its Privacy Policy. External content hosts and sign-in providers also apply their own privacy terms to their services. For DeepInfra, we rely on Standard Contractual Clauses or another lawful transfer mechanism. A copy of the relevant safeguards is available on request at [email protected].

Children

Chalk is not directed at children under 16, and we do not knowingly collect their data.

Changes

If we change this policy in a way that matters, we will announce it in the product before the change takes effect. The effective date above identifies when this version takes effect. Earlier versions remain available at /privacy/previous.

Contact

Q9 Labs — [email protected]