Privacy Policy

Ignitabull Services Inc. operates ignitabull.com and beta.ignitabull.com. This policy covers information submitted through these public websites, inquiry follow-up, and website analytics.

Information we collect

• Introductory-call requests: Your name, email address, optional Amazon or store link, submitted request, submission identifier, receipt timestamp, source URL, campaign attribution and review-routing information. Previously submitted full applications may include the business answers provided at that time.
• Agency waitlist requests: Contact details, brand or company, optional store or product link, service interest, context, source page and consent choices supplied through the relevant form.
• Blueprint intake: Business and product information, marketplace, decision context, objectives, constraints, economics, execution ownership and evidence links you choose to submit.
• Technical records: Request identifiers, submission status, error and audit records used to operate the forms and investigate failures, along with optional analytics described below.

Do not include passwords, API keys, access tokens, payment-card details or Amazon secrets in public forms.

How we use information

• Review inquiries, assess consulting fit and arrange a follow-up.
• Record the information and consent choices you supplied in Twenty CRM.
• Reconcile retries, investigate failures, protect the forms from misuse and maintain recovery records.
• Measure website use where you permit optional analytics.
• Respond to privacy requests and meet applicable legal obligations.

Joining an agency waitlist does not create an engagement, reserve capacity or authorize Amazon access. On the main-site forms, the optional marketing checkbox is off by default. A checked box records your preference; it does not automatically subscribe you to a mailing platform. The separate beta waitlist requires consent specifically for agency availability updates. That consent does not cover a general newsletter.

We do not sell personal information submitted through these forms.

Public form processing

Introductory-call requests and existing beta applications

Cloudflare Pages Functions handle introductory-call requests submitted at beta.ignitabull.com/apply. They validate the request fields, then record the request as a separate inquiry source record in Twenty. That record includes your name, email address, optional Amazon or store link, the original request payload, a submission identifier, the receipt timestamp, source URL, campaign attribution and review-routing information. Previously submitted full applications retain the answers originally provided. We confirm receipt only after reading back the saved record and checking that it matches the submitted request or application.

A repeat submission with the same identifier and unchanged answers can reconcile to that same source record. Changed answers are not treated as a successful duplicate. A call request or application does not subscribe the requester to marketing, create app access or automatically create a person, company or sales deal. A source record may be linked to an existing contact and its existing company when a single matching contact is found; existing suppression status is preserved. A confirmed receipt acknowledges the request; it does not book a call or start a consulting agreement. This beta route does not send an automatic receipt email.

To support safe retries, the beta form uses browser session storage for a pending submission identifier, a form-kind marker, an answer fingerprint and the original attribution/session context. It also stores an optional analytics choice, confirmed-receipt timing and optional analytics deduplication metadata. Raw request details or application answers are not saved in this browser retry record; they remain on the open page, so closing or reloading the page can require re-entering them. We do not promise that browser storage will be available.

Optional first-party funnel analytics measures selected page and request steps only when allowed. Those measurements do not include the submitted request details or application answers. Declining optional analytics does not prevent a call request. Campaign attribution accompanying the service inquiry is separate from optional analytics permission and does not constitute marketing consent.

After you allow optional analytics, Google Analytics may measure page visits and consulting-link clicks on the main Ignitabull website, and selected call-request steps and confirmed non-test requests on the beta call-request page. Google tags stay unloaded before permission. We do not send submitted names, email addresses, store links, form answers, submission identifiers or raw page-query strings in these events. Advertising storage, advertising user data and ad personalization remain denied. You can withdraw permission through Analytics preferences on the main site or Decline optional analytics on the beta page; the page then reloads to stop loaded Google tags. Optional analytics permission applies separately on each site. Request attribution and service-inquiry handling remain separate from optional analytics and marketing consent.

Separately maintained legacy forms

For the agency waitlist and Blueprint intake forms, Cloudflare Pages Functions handle requests. After route-specific origin, size, and field validation, inquiry source records are written to Ignitabull's access-controlled Twenty CRM. The CRM record stores supported contact details, source, request context, status, routing, qualification, next action, and a submission identifier used to prevent accidental duplicates.

For the main-site routes, Cloudflare D1 may retain a technical secondary or recovery copy for audit and reliability purposes. D1 does not replace the Twenty CRM as the operating sales system for these forms. The agency waitlist form reports success only when the Twenty CRM confirms the record. Blueprint intake may return a recovery state if D1 accepted the submission but Twenty was temporarily unavailable, so the intake can be reconciled instead of silently lost. These forms currently send no automatic receipt email. The beta call-request, application and waitlist routes use Twenty for inquiry storage and do not use D1.

Service providers and disclosure

Twenty stores inquiry records and supports their review and follow-up. Cloudflare hosts the public websites, processes form requests and supports first-party analytics, rate limiting and technical audit or recovery storage. Google Analytics is used only after optional analytics permission, as described above. Form submissions do not automatically enroll contacts in an email marketing service.

We may also disclose information when required by law or necessary to protect rights and security. Providers may process information outside your country of residence.

Security

Public forms use HTTPS. Server credentials stay outside browser code. Form handlers validate requests and limit the information returned in responses. No system can guarantee absolute security; avoid submitting unnecessary sensitive information.

Retention and privacy requests

Inquiry and recovery records may be retained for follow-up, troubleshooting and applicable legal obligations. We do not promise automatic deletion after a fixed interval.

You may request access, correction or deletion through the contact address below. We will assess the request, verify identity where needed and respond in accordance with applicable law. Some records may need to be retained for legal obligations or claims. This process is handled by a person; the public forms do not provide an automated deletion service.

Your choices

• Provide only information needed for your inquiry.
• Leave optional marketing consent unchecked, or contact us to withdraw a previously recorded preference.
• Decline or withdraw optional analytics using the controls described above.
• Contact us to request access, correction or deletion of your information.

Children

These business websites are not directed to children, and we do not knowingly collect children's personal information through them.

Policy changes

We may update this policy when the product, providers, or legal requirements change. We will post the revised date here and provide additional notice when a material change requires it.

Contact

For privacy questions or requests, email jeremy@ignitabull.com. Identify the organization and request type, but do not send passwords, API keys, access tokens, or Amazon secrets.

Last updated: October 20, 2026

Back to Ignitabull