Privacy and data boundaries for Payback Map.

We use Vercel Analytics and a small Payback Map event wrapper to understand page visits and limited buyer-path events such as resource clicks, start-path clicks, intake-result states, handoff availability, calculator inputs by field name, checklist counts, and support-form attempts. These events are designed to avoid raw form text, email addresses, phone numbers, private customer data, passwords, secrets, or payment details.

If you use the AI intake, the page may send the fields you provide to an AI service for a readiness assessment. You should only provide safe, redacted workflow notes: business type, workflow type, rough volume, current tools, pain points, and human-review boundaries. Do not submit passwords, API keys, billing data, private customer lists, regulated records, or sensitive customer details.

Raw intake notes are not sent for human review unless you choose the optional review request, provide an email, and check the consent box on the intake page. If you submit a support form, review request, or separately approved scheduling request, we may receive your name, email, company, topic, message, requested timing, and the page where the request started. These details are used to respond, confirm scope, and support the Payback Map process. A support note or scheduling request is not the same as a booked call.

No payment is collected by the static public page. When a separately approved payment path is used after scope confirmation, payment details are handled by the approved payment provider. Payback Map does not store full card numbers or banking credentials.

We use submitted information to answer questions, evaluate whether a workflow is ready for a Payback Map audit, confirm scope, deliver the audit, improve site clarity, and maintain safety boundaries. Payment, scheduling, implementation, live customer sends, system access, CRM changes, automations, and customer-visible AI messages remain separate manual or gated steps.

We may use analytics, hosting, email delivery, approved payment, scheduling, AI model, and messaging/workflow providers to operate the site and deliver the service. Public pages should not expose passwords, API keys, billing credentials, or private customer records.

We keep support, scheduling, and audit-related information only as long as reasonably needed for service delivery, records, dispute prevention, security, and business operations.

The safest choice is to use redacted examples only. If you accidentally submit sensitive information, contact support and ask for deletion or correction. Do not repeat the sensitive details in the request.

Use Payback Map Support and choose the privacy access, correction, or deletion topic. Include only safe locating context: the email address you used, company name if relevant, the page or form you used, the approximate date, and whether you are asking for access, correction, deletion, or review of accidental sensitive data. A sent support request is a receipt for manual review and does not mean the requested action has already been completed.

Use Payback Map Support for privacy questions, access/deletion requests, or data-safety concerns.