Privacy Policy

We at Promdock (“Company”, “Promdock”, “we”, “our”, or “us”) respect your privacy. This Privacy Policy describes our practices regarding the information we collect from or about you when you access our websites, web applications, and browser extension (collectively, the “Services”).

This Privacy Policy does not cover third-party websites, products, or services that you may access through links or integrations.

1. Information We Collect

1.1 Information You Provide

• Account information: such as email address, username, and authentication information.
• User Content: such as prompt templates, use cases, presets, notes, folders, titles, categories, and synced content.
• Communications: when you contact us for support or other inquiries.

1.2 Information We Collect Automatically

When you use the Services, we may collect log data (IP address, timestamps), device information (browser type, OS), and cookies necessary for operation.

For the public website, we may use privacy-focused web analytics provided by Vercel to understand page views, referrers, country, device, browser, and operating system at an aggregate level. We do not use this website analytics layer to collect prompt content, account passwords, password reset tokens, or Extension activity events.

1.3 Extension Usage Analytics

When Extension usage analytics is enabled for a Promdock release, analytics is collected only while you are signed in. Signed-out or anonymous Extension use does not create, queue, or transmit analytics events.

The Extension may send a limited allowlist of feature-completion and reliability events, such as whether a prompt or Set operation completed, whether a public Market item was opened, broad count or file-size ranges, coarse latency ranges, the Extension version, language, and online state. These events are used only to understand feature adoption, diagnose reliability, and improve Promdock.

These allowlisted events do not include Prompt or Set text, titles, notes, search terms, selected text, page URLs or domains, browsing history, images, files, file names, email addresses, raw account identifiers, authentication tokens, OTPs, passwords, exact error messages, stack traces, IP addresses, User-Agent values, or precise location. This event pipeline does not use autocapture, heatmaps, advertising profiles, or remotely hosted analytics code. Optional interaction replay is separate and described below.

Events are sent to Promdock's first-party Production endpoint. The server verifies the signed-in session, replaces the account identifier with an environment-specific HMAC pseudonym, disables GeoIP enrichment and person profiles, and then forwards the validated event to a separate PostHog Cloud EU project. The pseudonym is not the user's raw account ID and is not reversible without Promdock's server-side secret.

We retain Extension analytics only for as long as reasonably necessary to review product usage and reliability, maintain security, and meet legal obligations. You may contact us to request deletion; where applicable, we can derive the same pseudonym on the server and locate the corresponding analytics records without disclosing your raw account ID to PostHog.

1.4 Extension Interaction Replay

In releases with interaction replay enabled, replay is on by default while you are signed in unless you have saved an off preference for that account on that device. You can turn it off in Settings → Data & Sync → Interaction replay. It sends a visual reconstruction of clicks, scrolling, visible content and interface changes inside the Promdock popup and side panel to PostHog Cloud EU. The Promdock team may view those replays to understand product usage, diagnose usability problems and improve the product. We do not record other websites or browser tabs, your desktop, microphone audio or camera video.

Content visible inside the signed-in Promdock interface—including Prompt and Note text, titles, searches, account details, images and media—may appear in a replay. Passwords, verification codes, authentication forms, authentication tokens, console logs, and network request or response bodies are excluded. Credential-bearing URL components are removed before transmission. Replays use a random identifier rather than your email or raw account ID; no PostHog person profile is created.

This optional replay stream is sent directly from the Extension to PostHog EU, separately from the first-party event pipeline above. PostHog receives the network connection information needed to accept the request; the project's “Discard client IP data” setting is enabled. Replay libraries are bundled with the Extension rather than downloaded as executable code at runtime.

Your choice applies only to the current account and device. Turning it off stops future recording without affecting Promdock's other features. Signing out stops recording; another account does not inherit your choice. Previously uploaded recordings are not automatically deleted by turning the setting off. Recordings are retained according to the project's configured PostHog retention period and may be deleted sooner when no longer needed. Contact us for the current retention period or a deletion request; we may ask you to provide the random replay reference stored on the device so we can locate the recordings without sending your account ID to PostHog.

2. How We Use Information

We may use Personal Information to:

• Provide, administer, and maintain the Services (including account-based library sync).
• Enable core product features like saving prompts and publishing to the Market.
• Communicate with you regarding updates or support.
• Prevent fraud and enforce our Terms.
• Measure allowlisted Extension feature adoption and reliability while you are signed in.

3. Cloud Backup and Sync

Promdock provides account-based cloud backup/sync so you can access your library across devices. This means your saved prompt templates, use cases, presets, notes, folders, and related User Content may be uploaded to and stored on our servers. If you publish a prompt to the Market, it becomes publicly accessible.

4. Sharing and Disclosure

4.1 Service Providers

We may share information with vendors who process information on our behalf (e.g., cloud infrastructure, email providers, payment processors).

For Extension usage analytics, PostHog Cloud EU processes validated, pseudonymous, personless events on our behalf. We do not provide PostHog with Prompt content, browsing content, raw account IDs, email addresses, IP addresses, User-Agent values, or advertising identifiers through this analytics pipeline.

4.2 Legal Requirements

We may disclose information if we believe disclosure is necessary to comply with applicable law, legal process, or to protect the rights and safety of Promdock and its users.

5. Data Retention

We retain Personal Information for as long as necessary to provide the Services and for legitimate business purposes. If you delete content, we may retain certain information as required by law.

6. Security

We use commercially reasonable safeguards designed to protect information. However, no method of transmission or storage is 100% secure.

7. Children

The Services are not directed to children under 13, and we do not knowingly collect Personal Information from children under 13.

8. Your Rights

Depending on where you live, you may have rights to access, correct, delete, or object to certain processing of your Personal Information. Contact us to make a request.

Promdock's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell Extension user data or use it for personalized, retargeted, or interest-based advertising.

9. Contact

For questions or requests regarding privacy, contact: privacy email