Privacy Policy
Last updated: July 17, 2026
1. Who we are and what this policy covers
This Privacy Policy explains how MarkDocket, Inc. (“we,” “us,” or “our”) collects, uses, and protects personal information when you use the MarkDocket web and mobile applications and related services available at markdocket.com and through associated subdomains, email, and APIs, including the MarkDocket Desktop application (the “Service”). MarkDocket is operated by MarkDocket, Inc., a Delaware corporation and a subsidiary of Q6 Technology Holdings, Inc.. This policy applies to all visitors and users of the Service. It is incorporated into and governed by our Terms of Service.
The Service is an intellectual property operations workspace. It helps you search, track, and monitor public trademark and patent records, manage deadlines, and generate summaries and analytical documents, some of which are produced by automated, AI-assisted tools. This policy describes the personal and usage information involved in providing those features.
2. Information we collect
We collect the following categories of information:
- Account information. The name, email address, and organization details you provide when you register, sign in, or update your profile, plus authentication identifiers from our sign-in provider.
- Payment and billing information. Billing contact details and transaction metadata processed by our payment processor. We do not store full card numbers on our servers.
- User Content and queries. The records, identifiers, serial numbers, marks, documents, notes, portfolios, searches, and other content and instructions you submit, store, or ask the Service to process.
- Usage information. How you use the Service, including features used, reports generated, usage metering for billing, and settings.
- Communications. The content of support, legal, or other requests you send us, and records of our responses.
- Technical information. Device, browser, IP address, and similar data collected in server logs and through cookies and similar technologies as described below.
- Desktop application data. If you use the MarkDocket Desktop application, the additional information described in Section 2a below, including filing progress events, action logs, and screenshots of USPTO pages captured during a filing.
- Mobile application data. If you use the MarkDocket mobile application, the additional information described in Section 2b below, including app usage, diagnostics, notification tokens, and content you choose to upload.
2a. MarkDocket Desktop application
MarkDocket Desktop is an optional companion application for macOS that pairs with your MarkDocket account and assists with filings you initiate on the Service by filling USPTO Trademark Center forms in a browser on your own computer. This section describes the information involved when you use it.
Stored only on your computer. The desktop application stores a device token that pairs it with your account and the email address of the paired account. If you enable optional automated USPTO sign-in, it also stores your USPTO username and password and a security-key (WebAuthn) private key. All of these are encrypted using your operating system’s keychain. Your USPTO password and security-key private key never leave your computer and are never transmitted to our servers.
Transmitted to MarkDocket. During a filing, the desktop application sends our servers job progress events, action logs, serial and confirmation numbers, and screenshots of the USPTO pages it is working on. Because these screenshots show USPTO pages, they can include information visible on those pages, such as the applicant’s name and address and the masked payment-method label USPTO displays (for example, “Card ending 1234”). We use this information to show you filing progress, provide support, and troubleshoot filings.
Desktop usage analytics. The desktop application sends usage events to our analytics provider, PostHog (hosted in the United States), associated with a per-install device identifier and the email address of the paired account. You can turn this off using the “Send usage data” toggle in the application’s menu-bar settings.
What we never collect. We never receive your USPTO password or security-key private key. The desktop application reads only the visible display labels of stored USPTO payment methods; it never reads or transmits card numbers, CVV codes, or bank credentials, other than a masked label to the extent one appears in a USPTO page screenshot as described above. USPTO fees are paid by you directly to USPTO.
Update checks. The desktop application periodically contacts a public GitHub repository to check for and download application updates. GitHub receives the standard technical information associated with that request (such as your IP address).
Erasing local data. Disconnecting the computer from your account, or removing USPTO sign-in enrollment, wipes the corresponding locally stored data, including any stored USPTO credentials and security-key private key. If you enrolled a security key, you should also remove it from your USPTO account settings.
2b. MarkDocket mobile application
The MarkDocket mobile application for iOS signs in to your existing MarkDocket account and provides access to agent conversations, work products, deadlines, notifications, billing status, and account settings.
Analytics and diagnostics. The mobile application sends app lifecycle events, screen views, selected product interactions, app and device metadata, and crash or exception diagnostics to PostHog (hosted in the United States). After sign-in, this information is associated with your account identifier, name, and email address so we can understand cross-platform use, improve the Service, and troubleshoot errors. We disable IP-derived location, advertising tracking, cross-app tracking, and mobile session replay.
Content and device permissions. Messages, files, and photos you choose to send are transmitted to our servers to provide the requested agent, Vault, and work-product features. Camera and photo-library access are requested only when you choose the corresponding attachment action.
Notifications. If you grant notification permission, the application registers an Expo push token with our servers. Expo and Apple Push Notification service process that token to deliver account and docket notifications. The application asks our servers to unregister this device when you sign out.
Stored on your device. The application stores an encrypted authentication session, the last agent-conversation identifier, app preferences, and analytics state. Signing out clears account session data; deleting the application removes its remaining local data.
3. How we use information
We use the information we collect to:
- provide, operate, secure, and maintain the Service and your account;
- generate the Output you request, including AI-assisted summaries, key points, clearance and due-diligence reports, estimates, and other analysis;
- process payments, calculate and display usage, and issue receipts;
- communicate with you about your account, billing, support, and updates;
- monitor for fraud, abuse, security issues, and compliance with our Terms and applicable law;
- analyze and improve the Service, fix bugs, and develop new features; and
- carry out other purposes described at the point of collection or as otherwise permitted by law.
4. AI processing of your content
Some features use automated, AI-assisted tools to analyze records and User Content and produce Output such as case summaries, key points, and report drafts. We use sub-processors to provide these capabilities. When we process your User Content for these features, we do so to deliver the feature to you. We do not sell your User Content, and we do not knowingly allow third-party generative model providers to use your confidential User Content to train their general-purpose models; we configure and contract with our AI providers to limit training on your data where the provider offers that control.
AI Output may be inaccurate or incomplete and is not legal advice. See our Terms of Service for important disclaimers about AI-generated Output.
5. What we do not do
We do not sell your personal information to third parties. With your consent, we use analytics and marketing cookies for Google Ads measurement (conversion tracking) and remarketing, as described in our Cookies Policy; you can reject non-essential cookies or withdraw consent through your browser settings. We do not share your personal information for third-party marketing without your consent, except as described in this policy. We do not collect more information than is reasonably necessary to provide and improve the Service.
6. How we share information
We share information only as described in this policy, as needed to operate the Service, or as required by law. Categories of recipients include:
- Service providers and sub-processors. Vendors that help us run the Service, such as hosting, authentication, payment processing, email delivery, analytics, and AI providers. They process information on our behalf under appropriate contractual obligations.
- Public and third-party data sources. When you search or track a record, we may query external sources such as the USPTO. The identifiers you submit may be sent to those sources to retrieve the record.
- Legal and safety. We may disclose information when we believe it is required by law, legal process, or to protect the rights, safety, or property of our users, ourselves, or the public.
- Business transfers. In connection with a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred to the successor entity subject to this or a comparable policy.
7. Cookies and similar technologies
We use cookies and similar technologies to operate the Service, keep you signed in, remember preferences, and understand usage. Our authentication session cookie is first-party to the Service. Analytics and marketing cookies load only after you consent using the cookie banner; with your consent, marketing cookies enable Google Ads measurement (conversion tracking) and remarketing via gtag.js and Google’s Consent Mode v2. You can accept all cookies or reject non-essential cookies, and rejecting non-essential cookies does not affect core functionality. You can also control cookies through your browser settings; disabling strictly necessary cookies may affect some features. See our Cookies Policy for details.
7a. Consent records
When you accept or reject cookies using our banner, we record your choice in an append-only audit log. The lawful basis for this processing is your consent. Each record includes the date and time, your IP address, your browser/user-agent string, an anonymous randomly generated browser identifier stored on your device, the version of our Cookies Policy you were shown, and — if you are signed in — your MarkDocket account identifier. Each Accept and Reject creates a new record; we do not overwrite prior choices.
We use consent records to honor your preferences, to demonstrate consent for legal and compliance purposes, and to enable analytics and advertising features you have consented to. We retain consent records for the life of your account plus a reasonable period thereafter for audit and compliance. To request access to, correction of, or deletion of your consent records, contact us as described below.
8. Data retention
We keep personal information for as long as your account is active or as needed to provide the Service, and afterward for as long as reasonably necessary to comply with legal obligations, resolve disputes, enforce our agreements, and maintain records for billing, security, and audit purposes. You can request deletion of your account and personal information as described below, subject to legal retention requirements.
9. Security
We use reasonable administrative, technical, and physical safeguards designed to protect personal information. However, no system or transmission is completely secure, and we cannot guarantee absolute security. You are responsible for protecting your account credentials. If a security incident affects you, we will notify you as required by applicable law. See our Security overview for more information.
10. Your privacy rights and choices
Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal information, to restrict or object to certain processing, to withdraw consent, and to opt out of marketing. You can manage some of these directly in the Service. For all other requests, contact us at hello@markdocket.com and we will respond in accordance with applicable law.
California residents. Under the California Consumer Privacy Act, as amended by the CPRA, California residents may request to know, access, delete, correct, and opt out of the “sale” or “sharing” of their personal information. We do not sell personal information. With your consent, we share information for cross-context behavioral advertising through Google Ads measurement and remarketing, as described in our Cookies Policy; you can opt out by rejecting non-essential cookies or through your browser settings. To exercise these rights, contact us at hello@markdocket.com.
Residents of the EU, UK, and other regions with data protection laws. You may have rights under the GDPR or similar laws, including rights to access, rectification, erasure, restriction, portability, and to lodge a complaint with your local supervisory authority. Where we rely on your consent, you may withdraw it at any time without affecting the lawfulness of prior processing. For requests, contact us at hello@markdocket.com.
11. International transfers
The Service is hosted and operated from the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States, which may have data protection laws different from your jurisdiction. By using the Service, you consent to that transfer. We take reasonable steps to ensure an appropriate level of protection for such transfers, including through standard contractual clauses or other lawful transfer mechanisms where required.
12. Children
The Service is not directed to children, and we do not knowingly collect personal information from children under the age of 16 (or the higher minimum age required by applicable law). If you believe we have collected information from a child in violation of this policy, contact us at hello@markdocket.com and we will delete it.
13. Third-party links
The Service may link to or interact with third-party websites and providers that have their own privacy practices. We are not responsible for the privacy practices or content of those third parties. We encourage you to review their policies before providing them any information.
14. Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date above and, for material changes, provide reasonable notice (such as an in-app or email notice). Your continued use of the Service after the effective date constitutes acceptance of the updated policy.
15. Contact
MarkDocket is operated by MarkDocket, Inc.. If you have any questions, concerns, or requests regarding this Privacy Policy or your personal information, contact us at hello@markdocket.com or by mail at: MarkDocket, Inc., 2261 Market Street, Suite 22871, San Francisco, CA 94114.