PRD Seek is local-first product research software for reviewing public web and App Store signals, researching keywords, and drafting product requirements. This policy describes the information the software handles, when it leaves your computer, and how this public information site is hosted.
Who operates PRD Seek and what it does
PRD Seek is local-first product research software for product researchers. It helps users collect public web and App Store signals, organize notes and evidence, calculate keyword opportunity estimates, and draft product requirements. Each user runs their own local installation. This website provides public product information and legal documentation; it has no sign-in requirement, user account, or hosted research workspace.
Information in your local workspace
The software can store product and domain names, public URLs, App Store metadata, developer names and IDs, lead descriptions, your notes and evidence, opportunity details, generated PRD drafts, source settings, keyword text, search-volume metrics, SERP counts, and calculated KGR values. You may also enter other information yourself; avoid entering passwords, payment details, or personal information that is not needed for product research. The SQLite database is stored in .local-data/ and exported PRDs are stored in exports/prd/ by default.
Google Ads API keyword data (optional)
When you run KGR analysis for a web lead, PRD Seek sends that lead’s website domain as a site seed to Google Ads Keyword Planning. It requests related keyword ideas and average monthly search volume using the configured language and geographic target. If needed, it can also send selected keyword text to request historical search-volume metrics. Google OAuth client credentials and a refresh token are read from your local .env file; the refresh token is sent to Google’s OAuth endpoint to obtain a short-lived access token. PRD Seek does not use the Google Ads API to create or manage advertising campaigns, serve ads, or build advertising audiences. Returned keyword ideas and metrics are saved in your local database. Google processes these requests under its own terms and privacy policy.
SERP and KGR calculations (optional)
To complete a KGR calculation, PRD Seek sends the selected keyword as an allintitle search query, together with the configured location and language, to DataForSEO’s Google organic SERP service. It stores the returned result count and calculated KGR value in your local database. Google Ads supplies keyword ideas and search-volume metrics; DataForSEO supplies the SERP result count. These providers receive the request data and ordinary connection metadata such as IP address. They process it under their own terms and privacy policies.
Public data-source requests
When you run a source sync, PRD Seek requests public information from Smet.cz, Top Checkouts, and Apple services. Apple requests may include the storefront country or Apple developer ID that you selected to monitor. The source provider receives the request and ordinary connection metadata such as IP address and user-agent. The software stores the results in your local workspace.
AI-assisted PRD drafting (optional)
If you configure an LLM API key and choose AI generation, PRD Seek sends the opportunity details, up to 40 related leads, and up to 40 evidence items to the model endpoint configured in your local settings (12API by default). This can include product names, descriptions, source URLs, and your notes. Without an API key or when you use the local template, draft input is not sent to an AI provider. The configured provider processes submitted content under its own terms and privacy policy.
Website hosting and request data
This public site can be viewed without signing in and does not contain analytics or advertising scripts. Its hosting, DNS, or security providers may process the visitor’s IP address, requested URL, browser and device information, and security signals to deliver the pages, prevent abuse, and troubleshoot service issues. They may use security cookies for these purposes.
Storage, retention, and deletion
The software is designed to keep workspace records and API credentials on the computer where you run it. Records remain in the local database until you remove them. To delete local workspace records and exports, stop PRD Seek and delete .local-data/ and exports/prd/. Delete .env separately to remove locally saved API credentials. You control any backups. Requests already sent to Google, DataForSEO, Apple, Smet.cz, Top Checkouts, or an AI provider are subject to that provider’s retention and deletion practices.
Security and choices
Protect the device and backups that contain your database, exports, and .env file. The software does not claim that these files are encrypted at rest. Keyword research and AI drafting are optional; you can leave those credentials unset or choose not to run those features.
Children, changes, and contact
PRD Seek is a general product research tool and is not designed to collect personal information from children. This policy may change as the software changes; the date below identifies the latest revision. For privacy questions or requests, contact the operator using the email address below.
Contact
Questions about this policy or PRD Seek? rudyxu1102@163.com.