Effective date: July 18, 2026
Frankly Dog Training uses personal information to answer inquiries, evaluate whether its services may fit a dog owner's needs, operate the website, protect its systems, and understand marketing performance. This policy explains the current website and aggression application flow.
When you use the aggression application, we collect the answers you choose about your dog's behavior and bite history, your name, email address, callback phone number, and your answer about budget readiness. The landing page also creates an event identifier and may pass Meta browser identifiers named _fbp and _fbc into Typeform as hidden fields.
The website and its service providers may also process normal technical information needed to deliver, secure, and measure the site, such as page and event activity, browser or device information, cookies or similar identifiers, and network-derived information.
We use the information to:
Submitting an application does not guarantee acceptance, availability, results, or a training relationship.
_fbp and _fbc values are sent as browser identifiers when available.generate_lead event only after the one-time qualified-submission proof succeeds. The explicit conversion call does not contain the Typeform answers.Hashing is not anonymization. A deterministic hash can still be used to match records and should be treated as personal or pseudonymous data where applicable.
Frank can access the qualified intake summary needed for the callback. Vlad receives a monitoring copy and administers the connected business systems. Authorized administrators at the providers above may process information as needed to operate their services. We do not address, copy, or set reply-to on the internal alert to the applicant.
We keep intake and lead records only while they are reasonably needed to respond to the inquiry, administer a potential or existing client relationship, measure marketing performance, handle disputes, or meet legal obligations. When a record is no longer needed for those purposes, we delete it or de-identify it where reasonably practicable.
The short-lived Cloudflare submission-gate record expires after ten minutes and is deleted by the gate. That technical record contains event/proof state, not the visible intake summary. Other copies may remain in Typeform, internal email, Meta, GA4, Resend, or provider logs until they are deleted or de-identified under this rule, account settings, and provider or legal obligations. Removing one copy does not automatically remove every provider-held copy.
Use the contact page and clearly state that the message is a privacy request. You may ask to access, correct, or delete personal information associated with you, subject to applicable exceptions.
We will use reasonable steps to verify that a requester is entitled to the record before disclosing, correcting, or deleting it. A request may require action across more than one provider; removing one copy does not automatically remove every provider-held copy.
We use scoped access, signed webhooks, encrypted Worker secrets, one-time conversion authorization, and provider controls to reduce unauthorized access or misuse. No system can be guaranteed perfectly secure. If we discover an incident involving personal information, we will investigate, contain it, preserve necessary evidence, and provide any notice required after the facts and applicable obligations are assessed.
We may update this policy when the website, application flow, providers, or business practices change. The effective date above identifies the current published version.