Privacy and data handling
Privacy Policy
Last updated: June 18, 2026. This policy explains how DataCrawlPro handles client communication, website scraping and audit requests, uploaded files, cookies, payments, authentication, and responsible data service work.
This policy is written in plain language for a solo freelance service. It is self-reviewed by DataCrawlPro for transparency and risk reduction, but it is not legal advice. Sensitive, regulated, high-volume, cross-border, or personal-data projects may be declined unless the client can provide clear authorization and any needed legal basis.
Who operates DataCrawlPro
- DataCrawlPro is a full-time freelance service brand operated directly by Prashant Patil. It is not a registered company, large agency, big team, or hidden outsourcing team.
- Workflows may use AI-assisted tools for drafting, checks, summaries, and speed, but client-facing delivery is manually reviewed.
- For privacy questions, data requests, or project-specific compliance concerns, contact contact@datacrawlpro.com.
Information we collect
- Contact and request details such as name, email address, company name, website URL, target URLs, output format, budget range, deadline, and preferred contact method.
- Chat messages, quote notes, project instructions, uploaded files, sample files, deliverables, audit reports, payment status, and private request tokens.
- Technical and security data such as IP-derived rate-limit signals, form anti-abuse metadata, authentication state, device/browser information, and server logs.
- Google account identity data when you choose Firebase Authentication for dashboard access, usually email address, name, and account identifier.
How we use information
- To review scraping, extraction, Python script, AI automation, and website scraping risk audit requests.
- To confirm scope, feasibility, authorization, pricing, deadlines, payment state, project status, files, and delivery.
- To protect the service from spam, abuse, repeated submissions, unauthorized access, payment fraud, and unsafe requests.
- To improve site performance, conversion paths, and service quality when optional analytics are configured and permitted.
Lawful and responsible data work
- DataCrawlPro works with public data, client-owned data, or data the client is authorized to provide or request.
- Projects are reviewed for applicable legal, contractual, privacy, and technical restrictions before acceptance.
- Requests involving personal data, regulated data, children, health, financial records, account credentials, or sensitive categories may require extra review, written authorization, or refusal.
- DataCrawlPro does not promise universal compliance with every country law. Each project must be assessed against the jurisdictions, data source terms, data type, and intended use.
Payments and providers
- DataCrawlPro does not store payment card details. Website checkout is paused; payment is currently handled through Upwork contracts or direct communication after scope confirmation.
- Work is treated as paid only after Upwork or direct payment confirmation is reviewed.
- Upwork may be used when a client prefers marketplace contracts, milestones, escrow-style payment protection, or platform-managed records.
- Service providers may process limited data needed for hosting, storage, authentication, payment, analytics, email, security, and project delivery.
Cookies and similar storage
- Essential storage may be used for security, request tracking, dashboard login, private workspace access, form protection, and remembering cookie preferences.
- Optional analytics, advertising, or behavior-measurement tools such as GA4, Google Ads, Microsoft Clarity, or similar integrations run only when configured and accepted where consent is required.
- You can choose essential-only cookies or accept all cookies from the banner. You can reopen cookie settings from the footer.
- Some third-party providers may set their own cookies or similar technologies when their services are used.
Security and retention
- Backend protected routes verify Firebase ID tokens, admin routes are protected, and request workspaces use request-scoped access tokens.
- Uploaded files and deliverables should be stored with access controls. Production deployments should use controlled storage such as Firebase Storage or S3-compatible storage.
- Information is kept only as long as reasonably needed for project delivery, legal records, payment records, fraud prevention, support, and business operations.
- No internet service can guarantee perfect security. If a security issue is suspected, contact DataCrawlPro quickly at contact@datacrawlpro.com.
Your choices and rights
- You may request access, correction, deletion, or a copy of personal information associated with your request, subject to identity verification and lawful retention needs.
- You may ask DataCrawlPro to delete uploaded files or project materials when they are no longer required, unless retention is needed for payment, dispute, legal, or security reasons.
- You can avoid optional dashboard login by using the private request token, but anyone with that token can access the request workspace.
- If your project involves EU, UK, US, Middle East, India, or other regional data protection obligations, DataCrawlPro may ask for additional written instructions before work starts.
Contact
Email contact@datacrawlpro.com for privacy requests, cookie questions, data deletion, or service-specific compliance questions. You can also review the Terms and Ethical Usage, Return and Refund Policy, and Shipping and Digital Delivery Policy.