Who this policy covers
Jamie Lynn Services operates a connected group of business-system, software, professional-product, documentation, audit, and operational-support pages. This policy covers the Jamie Lynn Services web presence and the Dominator, FrankieFam, Free Frankie, Products & Services, and Partner Sales surfaces that link here. Customer accounts and customer environments may have additional contractual privacy, security, or data-processing terms.
Information you choose to provide
Inquiry and contact forms may receive your name, work email, organization, selected interest, contact type, workflow description, message, requested service, and consent acknowledgements. Do not submit medical, injury, employee, payroll, payment-card, authentication, security, emergency, or other sensitive customer information through a general website form or ordinary email.
When a customer creates an account or enters a service relationship, the service may receive account identifiers, authorized contacts, billing and contract information, configuration choices, support communications, customer-provided operational records, and other information needed to provide the contracted service. Customers are responsible for providing lawful instructions and notices for information they place into a customer environment.
FrankieFam and operational data
FrankieFam is software in development and is configured around the customer operation. Depending on the contracted configuration, the system may involve workflow, customer, lead, vendor, employee, training, equipment, maintenance, inventory, route, GPS/location, scan, payment, consent, voice, accounting, or other operational information. A page description does not mean a feature is live for every customer. The customer agreement should identify the actual fields, systems, integrations, roles, retention, security controls, and permitted purposes.
Sources and purposes
- Information you submit: respond to requests, scope work, communicate about an engagement, provide support, and document consent.
- Customer-provided information: provide the contracted software, documentation, audit, implementation, or support service under customer instructions.
- Public or authorized professional information: perform Dominator authority-infrastructure work, correction, publishing, and related customer-approved services.
- Technical and consent information: operate, secure, troubleshoot, measure, and protect the website and consent choices.
- Optional analytics and behavior: improve the site and services only after analytics consent, subject to the distinctions below.
- Contract, legal, security, and dispute purposes: establish, perform, protect, and document the business relationship.
Account sign-in
Established customers may choose Google, Microsoft, or Amazon sign-in from the Jamie Lynn Services public site. Those providers authenticate the person on their own controlled sign-in surfaces. Jamie Lynn Services receives the account response needed to associate an approved account with its customer record after the server-side authentication and provisioning service is connected. Provider cookies and provider privacy practices remain governed by the selected provider.
Analytics, cookies, and tokenized behavior
Optional analytics are not loaded until a visitor selects Accept Analytics. The current tools are Google Tag Manager, Microsoft Clarity, Contentsquare, Ahrefs Analytics, and Jamie Lynn Services’ own consent-aware behavior event bridge. Necessary website features should remain available after Reject Non-Essential. The Cookies page lists the current first-party storage keys and conditional third-party technologies by name and purpose.
With analytics consent, the site may maintain tokenized behavior such as page views, return visits, section views, product-interest clicks, form-start events, form-submission events, and broad service/product tags. The site should not place names, emails, free-text messages, workflow descriptions, or sensitive values into analytics event data.
Customer-account behavior may be linked to a customer only when the person has created or is using an authorized customer account and has provided the required account-linked behavior consent. Without both conditions, behavior remains tokenized or is not persisted to the customer behavior store. The browser does not write directly to SQL; any customer behavior database must be protected behind an approved server-side endpoint, access policy, retention schedule, and audit trail.
Where permitted by applicable law, Jamie Lynn Services may maintain anonymized or aggregated behavior that cannot reasonably be used to identify a person or customer. Consent, opt-out, regional law, customer instructions, and the final vendor configurations control.
Vendors and sharing
Information may be processed by hosting, form-delivery, security, analytics, communications, payment, software, integration, and professional-service providers necessary for the stated purpose. The current analytics configuration identifies Google Tag Manager, Microsoft Clarity, Contentsquare, and Ahrefs Analytics. The final policy should include verified vendor names, roles, subprocessors, regions, retention practices, transfer mechanisms, and links to vendor notices.
Personal information is not sold. Information may be disclosed when needed to provide a requested or contracted service, follow customer instructions, comply with law, protect rights and safety, prevent abuse, investigate security events, or support a business transaction, subject to the final legal and contractual framework.
Customer responsibility and restricted data
Customers must not place sensitive information into public inquiry forms or unapproved channels. Before onboarding, Jamie Lynn Services and the customer should classify data, define controller/processor roles, approve integrations and tools, identify permitted users, set retention and deletion instructions, and select a secure transfer method. Customer contracts may impose stricter rules than this public policy.
Retention, security, and deletion
Information should be retained only as long as necessary for the stated purpose, the customer agreement, lawful records obligations, security, dispute resolution, and account administration. Final retention periods and deletion procedures must be documented by system and data category. Reasonable administrative, technical, and organizational safeguards should be used, but no website or transmission method can promise absolute security.
Email and communications
Requesting a response or consenting to service follow-up is different from subscribing to marketing. Marketing lists require a separate, recorded consent where required, a clear purpose, and an unsubscribe or preference mechanism. Customer service, account, security, privacy, and engagement communications may be sent as needed for the requested or contracted relationship, subject to applicable law and the final agreement.
Your choices and requests
You may change optional analytics preference through Cookie Settings, reject non-essential analytics, or ask about information submitted through the site. Privacy requests should be routed through the working contact channel and may require reasonable verification. If a customer account or customer environment is involved, the customer’s authorized privacy/security contact and the applicable agreement may control the request process.
Children and external sites
This business site is not directed to children, and general forms are not intended to collect children’s information. External sites and product providers have their own practices; a link does not transfer this policy to an external website.
Changes and contact
Material changes should be posted here with a revised effective date. Use the Contact page for privacy questions when its handler is available, or written correspondence may be sent to Jamie Lynn Services, 2318 3rd Ave, Watervliet, New York 12189. This page is the single global privacy and cookie policy; the Cookies page is a settings/technology explainer, not a separate policy.