Privacy
This policy explains what Aparok collects, how it is used, and what product data is stored when teams use audits, prompt monitoring, and assistant traffic analytics.
Last updated: October 28, 2026
Aparok stores workspace details, domains, crawl results, report data, prompt watchlists, prompt-run observations, and assistant-attributed traffic events sent by the installed snippet.
Snippet events can include URL, referrer, session identifier, conversion metadata, and rendered page metadata such as title, canonical URL, headings, and text length.
Product data is used to generate audits, reports, executive summaries, prompt visibility analysis, and AI traffic insights. We also use configuration and access data to secure accounts and enforce workspace boundaries.
When prompt monitoring is enabled, Aparok sends configured prompts and grounded report context to third-party model providers such as OpenAI, Perplexity, or Google Gemini. Do not include secrets, credentials, or regulated data in prompts unless your own compliance review allows it.
Connected assistant providers, including OpenAI for ChatGPT and Anthropic for Claude, also process tool requests and responses when you enable Aparok in their products.
When you connect Aparok to an MCP-compatible assistant such as ChatGPT or Claude, the assistant can request Aparok data and actions that you authorize. Aparok stores OAuth client and grant records, token hashes, approved scopes, and expiration or revocation information needed to operate and secure the connection. Aparok does not store your ChatGPT or Claude password.
Connector responses can include workspace metrics, prompt observations, crawl findings, recommendations, traffic analytics, report data, and prospect-fit evidence. The connected assistant processes those responses under its own terms and privacy policy.
Aparok records operational information about connector use, including the tool name, success or failure, duration, authentication type, and limited numeric or boolean request attributes. Analytics events use a pseudonymous hashed identifier. Aparok does not send workspace IDs, prospect domains, prompt text, credentials, authorization tokens, or full tool responses to Google Analytics through this MCP event tracking.
When you upload a list, Aparok reads it in your browser. Contact names, email addresses, and phone numbers never leave your browser. Only company domains, company names, and job titles are sent to Aparok, plus record IDs (such as CRM or Apollo IDs) if you choose to keep them. We also read your own company website once to learn what you sell.
For each company, Aparok reads its public website and uses a third-party AI model (Google Gemini) to produce the fit decision, evidence, and suggested opener. We don’t use your uploads to contact anyone, and we don’t sell or share them for marketing.
For uploaded lists, you decide what to upload and why, and Aparok processes it only to produce your results. Don’t upload health information or other sensitive personal data.
Running Prospect Fit without an account sets a random visitor cookie so we can show your free companies and your last run. To limit abuse, we store a one-way hash of that cookie and of your IP address, not the raw values.
If you buy a bundle, we store your email address, the bundle, the amount, and the payment reference. PayPal or Razorpay process the payment itself; Aparok never sees your card or bank details.
Strictly necessary cookies keep you signed in, remember your logged-out runs, and store your cookie choice. With your consent, we also use Google Analytics and Google Ads (including conversion measurement), Microsoft Clarity, the LinkedIn Insight Tag, the Apollo website tracker, and the OpenAI ads pixel to understand usage and measure our marketing.
Visitors in the EEA, UK, and Switzerland are asked first, and these tools stay off until they accept. You can change your choice anytime with “Cookie settings” in the site footer. If you reject them, our server-side analytics events aren’t linked to your browser.
Logged-out Prospect Fit runs that aren’t paid for are deleted automatically after 30 days. Paid runs that aren’t saved to an account have their uploaded list and results deleted 180 days after purchase; we keep the payment record for accounting. You can delete a run yourself anytime from its results page. Runs saved to an account stay until you delete them.
You can delete your whole account from Profile → Account. That removes your login and, unless you share a team with others, all of its workspaces and data, and cancels any subscription. Payment records are kept as required for accounting.
Workspaces can delete domains, reports, and prompt sets from the product. Operational logs, backups, analytics records, and provider-side processing may have separate retention windows.
You can disconnect Aparok in the connected assistant and revoke an Aparok OAuth grant.
We use these providers to run Aparok: Supabase (database), Google Cloud (hosting and task processing), Google Gemini, OpenAI, Anthropic, and Perplexity (AI models), PayPal and Razorpay (payments), and the analytics and advertising tools listed under Cookies and tracking. Your data may be processed outside your country by these providers under their own data protection terms.
Depending on where you live (for example under the GDPR, UK GDPR, or India’s Digital Personal Data Protection Act), you can ask to access, correct, export, or delete your personal data, object to or restrict its use, and withdraw consent. Email info@aparok.com and we’ll respond within 30 days. You can also complain to your local data protection authority.
Businesses that need a data processing agreement for Prospect Fit uploads can request one at the same address.
For privacy questions or requests, email us at info@aparok.com.