Contact & support

Ask for help, share feedback, or start the right conversation without guesswork.

Whether it is login trouble, field workflow feedback, pricing questions, or a partnership idea, this page should get the message into the right hands quickly. The public side stays focused on the app, the workflow, and the AI-guided field intelligence behind it.

Use this page for

  • Support requests that block people from using the app, website, or account-linked workflow.
  • Business, pricing, or partnership enquiries that need a clear commercial reply.
  • Useful detector, ground, and workflow feedback that helps the AI-guided field intelligence get smarter.
The form below is the tracked path. The email cards stay here as a practical fallback if you ever need to bypass the form and go straight to inbox.

Tracked contact form

This is the cleanest path because it lets the website keep the enquiry and follow-up together instead of losing context in someone's inbox.

If the tracked path is unavailable, use the email backups on the right.

Why this matters

PFA is not just map layers and saved finds. It is meant to become a practical assistant around settings, ground choice, field follow-up, and the AI-guided field intelligence that helps people stop walking over gold without knowing why.

Business email

spyingeye007@gmail.com

Use this for pricing, partnerships, sponsorships, or anything commercial that should go straight to the main business contact.

Email business directly

Support email

spyingeye007@gmail.com

Use this for login trouble, app and website workflow issues, account-linked problems, or anything blocking normal use.

Email support directly

Privacy email

spyingeye007@gmail.com

Use this for privacy questions, data handling concerns, or anything related to personal information on the platform.

Email privacy directly

Legal email

spyingeye007@gmail.com

Use this for terms questions, formal notices, or anything that should go to the legal contact.

Email legal directly

Fastest way to get a useful reply

  • Say whether the issue is on Android, iPhone, or the website.
  • Mention the detector, ground type, or workflow involved if it matters.
  • Include the exact page or screen name.
  • Add a screenshot if the issue is visual or layout-related.