Privacy notice draft

JotWeave is a private notes, chat, and assistant workspace. It is not end-to-end encrypted: the service and selected providers can read content needed for the features a user invokes.

What the product stores

• Account data: email, display name, authentication, membership, and security records handled through Supabase-backed account flows.
• User content: notes, tasks, messages, meetings, files, and related workspace records created or uploaded by a user.
• Usage and service data: quota, billing-entitlement, audit, and security records needed to operate and safeguard supported workflows.
• Connected-service data: tokens and requested content for a service a user explicitly connects. Availability and permissions depend on the specific connector and deployed configuration.

Google user data

Google connection begins with identity only. Calendar, Gmail, Meet, and Google Chat are separate optional upgrades. JotWeave does not request Gmail or Google Chat message access during the initial connection. A user must choose each capability before its scopes are requested, and Google Chat message reading remains disabled unless the deployed test-user gate and Google approval allow it.

If a user enables a Google Chat conversation, JotWeave mirrors its messages into the same private conversation system used by native chat. The conversation stays personal unless the user explicitly moves it into a workspace through existing workspace permissions. Chat attachments are represented by metadata first; uploaded files are downloaded only when the user opens them and are retained in JotWeave storage only after the user chooses “Save to JotWeave.” Google Drive-backed Meet and Chat files remain links unless a separately approved Drive capability is added.

Disconnecting Google cancels future synchronization, marks Meet sources disconnected, and removes mirrored raw Google Chat messages and JotWeave attachment caches. Notes, tasks, summaries, decisions, and other JotWeave records a user explicitly created are retained with disconnected-source provenance so the user does not lose their own work.

Any production use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including Limited Use requirements. Owner confirmation remains required for the final advertising, sale, model-training, transfer, and exception language.

AI processing

Supported cleanup, organization, transcription, summary, and search workflows can send relevant content to a configured, provider-abstracted AI service. Provider availability, retention, account settings, and model-training terms can differ. JotWeave does not publish a universal no-training or zero-retention promise without current contract and setting proof.

Access and storage boundaries

Repository schema uses row-level security and membership checks for covered data. Newer V2 schemas and cross-object paths still require migrated, authenticated runtime verification. JotWeave does not make a universal encryption-at-rest claim for every database, object, backup, token, queue, log, and provider path.

Deletion and retention

Supported app surfaces include deletion paths for content and connected-service tokens. Account deletion can be requested through the feedback form. The final policy still needs confirmed timing for account data, backups, derived indexes, audit records, and provider-held data.

Business policy confirmation

Sale, advertising use, subprocessors, legal disclosures, cross-border processing, and company-wide handling are business and legal commitments that application source code cannot prove. The owner must confirm those commitments and publish the approved wording before this route can be indexed as the production privacy policy.

Questions

Send questions or policy requests through the feedback form.