REDACTDOCK
ExtensionPrivacyTermsSupport

Privacy

Your documents deserve a clear data boundary.

This policy explains what RedactDock handles, where processing occurs, what may leave your device, and the choices available to you.

Last updated September 10, 2026

1. Scope

This Privacy Policy applies to the RedactDock website, the RedactDock Chrome extension provided by RedactDock, its licensing service, and related support and account services. It does not replace the privacy policies of websites or AI services you choose to use, including ChatGPT and Claude.

2. Information we handle

Website and communications

  • Contact and demo information, such as your name, email address, phone number, company, interests, and message.
  • Newsletter email address and the consent record associated with your subscription.
  • Booking information you submit through our scheduling provider.
  • Basic technical logs used to operate, secure, and diagnose the website.
  • Website analytics when you allow analytics cookies or similar technologies.

Chrome extension and licensing service

  • Your licensed email address and a random identifier generated for that Chrome installation.
  • The six-digit confirmation code and opaque session token used to activate and maintain your session.
  • Files you deliberately select, including filenames and document contents. Documents may contain personal, financial, health, employment, tax, or other sensitive information.
  • Sanitized Markdown, detected data categories, redaction counts, extraction methods, and document fingerprints created locally during processing.
  • Extension settings, local client aliases, retention preferences, and locally stored sanitized-file history.
  • The active supported destination—currently ChatGPT or Claude—when needed to protect and complete a user-requested attachment.

RedactDock does not use the extension to read your prompts, conversation history, or AI responses. The extension operates on files you select and on the supported upload controls needed to replace those files.

3. Where document processing occurs

Document extraction, client aliasing, redaction, and final leakage checks run locally inside the Chrome extension. The original file and sanitized Markdown are not sent to RedactDock's cloud service for sanitization or storage.

The Chrome extension does not require native messaging, a companion application, or a localhost service. If local processing cannot be completed or verified, the protected-upload workflow blocks the original attachment rather than releasing it.

4. Information that may leave your device

Licensing service

Your licensed email address, random Chrome-installation identifier, confirmation code, and opaque session token are sent over HTTPS to RedactDock's licensing service. We use this information only to verify an active subscription, send the requested confirmation code, enforce the one-installation limit, maintain the session, and protect the service against abuse. The installation identifier is not derived from hardware, advertising identifiers, or browsing activity.

Your chosen AI service

When you approve or complete an attachment, the supported destination receives the newly created sanitized Markdown. Your use of that destination is governed by your agreement and privacy settings with its provider. RedactDock is not affiliated with or endorsed by OpenAI or Anthropic.

5. How we use information

  • Provide local document sanitization and protected attachment features.
  • Verify paid licenses, authenticate users, and enforce the one-installation limit.
  • Store and display sanitized files according to the user's settings.
  • Operate, secure, troubleshoot, and improve the product.
  • Respond to support requests, demo requests, and product communications.
  • Comply with law and protect users, RedactDock, and others from fraud, abuse, or security threats.

We do not sell extension user data or use document contents for personalized advertising.

6. When information is shared

We may share information only as needed with:

  • Amazon Web Services for website hosting, lead storage, confirmation-code email delivery, and licensing records.
  • Cloudflare Turnstile for website abuse and automated-submission prevention.
  • Google Analytics for website measurement when you permit analytics.
  • Calendly when you choose to schedule a meeting or demonstration.
  • Your organization's authorized administrators when you use an organization-managed deployment.
  • OpenAI or Anthropic when you direct the extension to attach sanitized Markdown to its supported service.
  • Google in connection with the Chrome Web Store and browser platform, under its own privacy terms.
  • Authorities or other parties when required by law or necessary to protect rights, safety, and security.
  • A successor in a merger, financing, acquisition, reorganization, or sale, subject to applicable notice and consent requirements.

We do not permit people to review extension user data except with the user's specific consent, for security or abuse investigation, to comply with law, or in aggregated and de-identified form for internal operations.

7. Storage and retention

The extension's sanitized-file library is stored in the browser profile. The current default retention is 30 days, with user-configurable retention and a local storage limit. Users can delete individual records or the entire local library. Signing out removes active account-session information; uninstalling the extension or clearing its storage removes extension data from that browser profile.

Website inquiries, licensing records, confirmation-code records, sessions, and security logs are retained only as long as reasonably needed for the purpose collected, contractual obligations, security, dispute resolution, and legal requirements. Retention may differ under an organization's agreement or deployment settings.

8. Your choices

  • Do not select a document if you do not want RedactDock to process it locally.
  • Delete sanitized records from the extension library or uninstall the extension.
  • Sign out to invalidate the current session, or contact support to reset the active Chrome installation.
  • Decline website analytics through the website consent control.
  • Unsubscribe from marketing messages using the link in the message.
  • Contact us to request access, correction, or deletion where applicable.

9. Security

We use administrative, technical, and organizational safeguards appropriate to the information we handle. No product can guarantee that every sensitive value will be detected or that every system will be completely secure. Review sanitized output before relying on it for legal, financial, healthcare, tax, or other high-impact work.

10. Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

11. Children

RedactDock is intended for business and professional use and is not directed to children under 13.

12. Changes and contact

We may update this policy as the product or legal requirements change. We will post the new date on this page and provide additional notice when required. Questions and privacy requests can be sent to hello@redactdock.com.

© 2026 RedactDock. All rights reserved.

hello@redactdock.comPrivacyTerms