What is collected
Contact details, project context, current tool stack, website activity, checklist requests, search or AI visibility context, and service-related notes needed to respond or deliver work.
Privacy and service terms
Privacy, data handling, and service terms for eArif.com.
This page explains how eArif.com handles inquiries, lead magnets, analytics, search and AI discovery, marketing messages, service delivery data, project access, and working terms for audits, implementation, repairs, and support.
Plain Summary
Only send information needed to understand the project.
What not to send first
Do not send passwords, API keys, payment card numbers, private customer exports, or sensitive client data through a public form or first email.
How it is used
Information is used to reply, qualify fit, scope an audit or service, deliver agreed work, improve the website, review search visibility, and measure campaign performance.
How to ask
Email arif@earif.com if you need to update, remove, or ask about information you shared.
Privacy Source Context
Use Privacy before a source signal becomes access, data, proof, or service-start permission.
A Privacy visit from Google, Bing, ChatGPT, Perplexity, Claude, Gemini, Copilot, LinkedIn, X, YouTube, TikTok, Reddit, Facebook groups, Upwork, referrals, saved links, About, Services, Systems Audit, Proof, Learning Cave, AI Search Profile, Contact, lead magnets, checklists, forms, or browser-agent visits is safe-access context only. It does not prove consent, private-data permission, access readiness, service fit, buyer fit, project qualification, proof permission, form-submit proof, tracking proof, ranking, AI citation, or approval to use private screenshots, credentials, exports, customer records, payment data, API keys, OAuth tokens, webhook secrets, analytics screenshots, ad account screenshots, or AI prompts with private data.
Source signal names the privacy decision
Search, AI search, profile, social, referral, checklist, form, and saved-link visits only explain why someone is checking access rules.
Public context comes before access
Business model, current tools, expected path, visible symptom, owner, timing, and decision needed come before credentials or admin access.
Private data stays redacted
Customer records, payment details, exports, screenshots, API keys, OAuth tokens, webhook secrets, and private URLs need redaction or secure sharing rules.
Proof and claims need permission
Marketplace facts, screenshots, review themes, client examples, AI answers, and case-study notes need Proof and permission boundaries before reuse.
Live system risk routes to Systems Audit
When the privacy question affects live leads, buyers, members, orders, reports, ads, CRM data, or automations, start with Systems Audit.
Safe context routes to Contact or no-fit
After source, redaction, access scope, proof permission, and live-risk state are clear, the next step is Contact, Services, monthly support, or no-fit.
Route by privacy-source evidence: use Privacy for access and data boundaries, Contact for safe first-message context, Systems Audit for live-system risk, Services for clear scope, Proof for permission-based claim reuse, Learning Cave for public education, AI Search Profile for answer correction, Monthly CRM automation support for recurring access governance, or no-fit when the source asks for unsafe access, private data, or unsupported proof.
Safe Access Decision Guide
Share context first, then decide whether access is actually needed.
Use this map before sending credentials, exports, private customer records, payment details, CRM screenshots, analytics screenshots, ad account screenshots, API keys, OAuth access, webhook secrets, or AI prompts with private data.
First-message evidence
Send the business model, current tools, expected customer path, visible problem, affected handoff, timing, owner, and decision needed before any private access is requested.
Redaction evidence
Replace customer names, emails, order IDs, payment values, phone numbers, addresses, API keys, screenshots with personal data, and private dashboard URLs with safe labels or redacted examples.
Access timing evidence
Share access only after the scope, risk, owner, testing path, permission level, and revoke plan are clear enough to protect live customers and live reporting.
Role-limited access evidence
Use temporary, role-limited access for Shopify, GoHighLevel, Keap, WordPress, LearnDash, Memberium, GA4, Looker Studio, ad platforms, email tools, and integration tools when access is required.
AI and analytics boundary evidence
Keep sensitive data out of AI-assisted work unless the task, allowed fields, review owner, privacy boundary, and redacted context are already agreed.
Proof permission evidence
Use public proof, anonymized notes, permission-based screenshots, marketplace-visible facts, or category-level examples instead of publishing private client systems or unsupported outcome claims.
Safe privacy intake should include only public business context, current tools, expected path, visible symptom, affected data type, access already available, access not yet shared, redaction requirement, permission owner, testing expectation, revoke plan, business risk, deadline, proof boundary, and redacted example.
Route by evidence: use Privacy for access and data boundaries, Contact for first-message context, Systems Audit when the risk crosses tools, Proof when a claim needs permission-safe evidence, AI lead response prototype when private-data boundaries affect AI workflow design, Shopify GA4 tracking audit when consent or tracking evidence is unclear, Monthly CRM automation support when access governance needs recurring ownership, or Services when a narrow route is already clear.
Privacy Policy
How eArif.com handles website and project information.
Information you provide
You may provide your name, email address, company or website, project type, current stack, problem description, timing, and files or links that help explain the work.
Website, analytics, search, and advertising data
The site may use Shopify analytics, GA4, Google Search Console, Bing Webmaster Tools, advertising pixels, UTM parameters, and similar measurement tools to understand traffic, crawl/indexing signals, CTA clicks, form submissions, and campaign performance.
Email and lead magnet data
If you request a checklist, subscribe, reply to outreach, or submit a form, your email and request context may be used to send the requested resource, follow up, and route future messages by topic.
Service delivery data
For paid work, eArif may receive temporary access, screenshots, test records, workflow notes, CRM fields, dashboard context, or other system details needed to audit, repair, build, test, and document the agreed scope.
Third-party tools and service providers
Information may be processed through tools used for website hosting, Shopify, email, CRM, analytics, search visibility, ads, scheduling, payments, documents, project delivery, automation, and AI-assisted workflow support.
AI-assisted work and AI search
AI tools may be used to help summarize notes, draft documentation, review code or workflows, and prepare internal implementation material. Public pages may also be reviewed for AI-search visibility. Sensitive client data should be minimized before being shared with any AI tool.
Security and access
Project access should be temporary, role-limited, and revoked after the work is complete. Passwords should be shared through secure access methods, not public forms or plain-text messages.
Retention and removal
Information is kept only as long as needed for inquiry handling, service delivery, records, security, dispute handling, legal obligations, or legitimate business needs. You can ask about update or removal options by email.
Marketing choices
Marketing emails should include an unsubscribe path where required. You can also ask by email to stop non-transactional marketing messages.
Children's data
eArif.com is a business service website and is not intended for children.
Policy updates
This page may be updated as the website, tools, services, analytics setup, or marketing systems change.
Contact
Questions about privacy, project data, or marketing messages can be sent to arif@earif.com.
Service Terms
Working rules for audits, implementation, repairs, and ongoing support.
Scope comes first
Work starts from an agreed scope, audit, proposal, task list, or support backlog. Extra requests may require a separate estimate or priority decision.
Client access and approvals
The client is responsible for providing accurate context, required access, test examples, approvals, platform accounts, and third-party billing where needed.
No unsupported outcome guarantees
Technical work can improve systems, tracking, workflows, and visibility, but it does not guarantee sales, rankings, ad performance, platform approval, or third-party results.
Third-party platforms
Shopify, GoHighLevel, Keap, WordPress, payment tools, ad platforms, analytics tools, AI tools, and integrations may change features, policies, limits, pricing, or behavior outside eArif's control.
Testing and launch responsibility
Important customer paths should be tested before launch. Client teams should review live behavior, revoke unused access, and monitor the system after changes are published.
Payments, refunds, and cancellations
Payment terms, milestones, cancellation windows, refunds, and ongoing-support capacity should be agreed in writing before work begins. Custom service work is generally scoped around time, deliverables, and access already used.
Confidentiality and proof
Private client systems, credentials, customer data, and business details should not be published as proof without approval. Public proof should be anonymized or permission-based.
Support boundaries
Monthly support is not unlimited emergency coverage unless that is explicitly included. Urgent work, after-hours support, and high-risk live changes need clear agreement.
Safer Project Handoff
Use secure access and minimum necessary data.
Privacy and service terms FAQ
Clear answers before you send project context.
What should I include in a first message?
Send the tool stack, expected customer path, what is not working, timing, and the decision you need. Do not send passwords, API keys, payment details, private exports, or customer records in a public form.
When should I share system access?
Share access only after scope is clear. Use temporary, role-limited access where possible, and revoke unused access after the work is complete.
How is marketing email handled?
Marketing messages should use accurate sender identity, unsubscribe handling where required, suppression for opt-outs and wrong-fit contacts, and only the context needed to route the message.
Does the site use analytics and ad pixels?
The site may use analytics, search tools, ad pixels, UTMs, and Shopify privacy settings to understand page visits, crawl/indexing signals, CTA clicks, forms, and campaign performance. Cookie and consent settings should match the live Shopify setup.
Can AI tools be used during service delivery?
AI tools may help summarize notes, draft documentation, review workflows, or prepare implementation material. Sensitive data should be minimized before it is shared with any AI-assisted workflow.
Does eArif guarantee business outcomes?
No. Technical work can improve systems, tracking, workflows, documentation, and visibility, but it does not guarantee sales, rankings, ad results, platform approval, or third-party behavior.