Privacy Policy

QuickNoteLM Privacy Policy

QuickNoteLM is built to capture notes, links, files, screenshots, voice memos, and workspace knowledge. This policy explains the product privacy model we are building toward during the pre-launch period. It should be reviewed by counsel before broad commercial launch.

What we collect

We may collect account details, waitlist emails, workspace membership data, billing and support metadata, device and usage metadata, and the content you choose to save in QuickNoteLM.

Saved content can include raw notes, original uploaded files, extracted text, OCR, transcripts, summaries, tags, entities, search chunks, embeddings, and AI outputs. We treat source content and derived content as confidential customer content.

How we use content

We store raw notes and original files because they are the source of truth for search, export, sharing, recovery, and reprocessing. AI summaries and embeddings do not replace the original content.

We use customer content only to provide the service features selected for your workspace, such as capture, sync, extraction, organization, search, sharing, export, and support.

Personal and company workspaces

Personal workspaces and company workspaces must stay separate. Company administrators should not have a technical path to personal workspace content unless you explicitly move or share that content.

Company workspace content may be governed by organization policies. Ordinary administrators should manage members, billing, settings, and policy without automatically receiving blanket access to every note.

AI processing

Organization AI features should require an explicit organization decision. External AI should remain off until enabled by an authorized owner.

When AI is enabled, QuickNoteLM should permission-check content before retrieval, send the smallest useful context, and avoid sending whole workspaces or original files when selected text is enough. Customer content must not be used to train shared models unless an organization separately opts into a clearly defined program.

Telemetry and logs

Raw note text, prompts, model responses, attachment bodies, OCR text, and embeddings should not appear in analytics, logs, traces, error monitoring, session replay, support tickets, or alert payloads. Operational telemetry should use metadata such as IDs, timings, sizes, error codes, and policy versions.

Sharing, export, and deletion

Public sharing should be opt-in, revocable, and clearly labeled. Personal users should be able to export their personal workspace. Company exports should be restricted to elevated organization roles and audited.

Permanent deletion should remove active access immediately and propagate to source content, extracted text, summaries, embeddings, search indexes, caches, share links, temporary files, AI state, and backups on a documented schedule.

Security and support access

QuickNoteLM should use encryption in transit, encryption at rest, tenant-scoped authorization, restricted internal access, and audited support workflows. We do not claim end-to-end encryption for server-side search and AI features.

QuickNoteLM personnel should have no standing production-content access. Support access should be case-bound, time-limited, approved, and audited.

Contact

For privacy questions, contact support@quicknotelm.com.