PaperDockPaperDock

Last updated: July 22, 2026

Privacy Policy

This policy explains how PaperDock handles information when you use the web app, collaboration features, LaTeX compilation, invitations, and connected services.

Information We Collect

We receive your email address, name, profile image, authentication provider identifier, and basic account metadata when you sign in with Google or GitHub. We store the projects, files, revisions, comments, replies, chat messages, invitations, and settings you create or share through PaperDock.

We also process technical records needed to operate the service, such as session data, access-control records, compile status and logs, storage usage, rate-limit counters, security events, and sanitized error diagnostics. We do not use project content for advertising.

We use Google Tag Manager to manage Google Analytics 4. We send analytics events only from non-sensitive web app routes to understand generalized page visits and product milestones such as account access, project creation, compilation, invitations, and interest in MCP setup. Analytics events do not include email addresses, account or project identifiers, project names, file paths, document content, collaboration content, invitation tokens, OAuth parameters, MCP credentials, compile logs, or raw error messages.

How We Use Information

We use this information to authenticate users, enforce project permissions and quotas, synchronize collaborative edits, deliver invitations, compile LaTeX projects, provide file history, prevent abuse, diagnose failures, and improve reliability. We do not sell personal information.

Collaboration and Sharing

Project managers can invite other people as editors or viewers. Project members can see project content and collaboration activity according to their role. Removing a member ends future access, but content they previously contributed may remain in project history and collaboration records.

AI Agents and MCP Connections

If you connect an external AI agent through PaperDock's MCP interface, that agent can access only the projects and actions allowed by your current PaperDock membership and role. PaperDock records agent-created collaboration content as such. The external agent provider processes information under its own terms and privacy policy; review its settings before granting access.

Reference Integrations and Invitations

When you connect Zotero or Mendeley, PaperDock stores the authorization data needed to access the selected service and import bibliography information. Invitation emails are delivered through an email provider and include the recipient address, project name, role, and a time-limited acceptance link. You can disconnect an integration or revoke a pending invitation from the product.

Service Providers

PaperDock relies on service providers for authentication, database and file storage, hosting and network delivery, transactional email, and privacy-limited product analytics. These providers process information only as needed to supply their services and under their own contractual and privacy obligations.

Cookies and Sessions

PaperDock uses essential cookies and similar session storage to keep you signed in, complete OAuth flows, protect invitation acceptance, and preserve necessary product state. Google Analytics may use cookies or similar storage to distinguish visits and measure product usage where enabled. We do not use advertising cookies or send project content to analytics.

Retention and Deletion

Current project files remain while the project exists. During the Public Beta, visible document history is generally retained for up to 30 days, operational revisions for up to 7 days, and compile artifacts for up to 7 days. Successful compile logs are generally retained for 24 hours, failed or canceled logs for 72 hours, and terminal compile job metadata for up to 30 days. The latest successful PDF and SyncTeX result may remain until a newer result is available or the project is deleted.

Deletion from the database and deletion from object storage may complete asynchronously. We keep durable deletion records so failed storage cleanup can be retried. Backups and security records may remain for a limited period where reasonably necessary for recovery, fraud prevention, or legal obligations.

Your Choices

You can download project content, remove collaborators, revoke invitations, disconnect integrations, and delete projects through the product where those controls are available. Contact us to request access to or deletion of account information that cannot be managed directly in the app.

Security

We use access controls, private project authorization, encrypted connections, isolated compilation, rate limits, and operational monitoring to protect the service. No system is completely secure, so keep your account and connected-agent access secure and avoid uploading information you do not need PaperDock to process.

Changes to This Policy

We may update this policy as the Public Beta evolves. We will update the date above and provide additional notice when a change materially affects how we handle information.

Contact

For privacy questions or data requests, contact support@paperdock.dev.