This Cookie Policy explains cookies and similar browser technologies in relation to the Fendrick Launch website. It separates the behavior of the custom website sections from possible hosting, theme and application features. Cookie behavior can depend on the configuration actually deployed on the site.
1. What cookies and similar technologies do
A cookie is a small value stored by a browser for a website. It can help maintain a session, remember a choice or associate later requests with an earlier visit. Cookies can be set by the visited site or by a third-party resource. Some last for a browser session, while others remain until their expiry or removal.
Local storage and session storage are separate browser mechanisms that can retain information on a device. Pixels, resource requests and similar technologies may also disclose connection information even without storing a cookie. Their purpose and effect depend on how the particular technology is implemented.
2. The custom Fendrick sections
The supplied custom sections do not write analytics cookies, advertising cookies, local storage or session storage. The navigation, animations, expandable questions and project modal use browser functionality and temporary page state. That state is not used as a persistent visitor profile.
The project form validates its fields locally and displays an on-screen confirmation. It does not save the completed fields in browser storage or transmit them as an enquiry. Closing or refreshing the page ends that temporary interaction. The local confirmation does not create an account or a delivered support ticket.
3. Hosting platform, themes and applications
Shopify, the deployed theme and independently installed applications may use cookies or other technologies for security, session management, preferences and other functions. The existence, name and duration of those technologies depend on the actual store configuration and provider behavior.
This policy does not claim that a particular optional tracking application is installed. Nor does it give blanket consent for tools that might be added later. Before enabling new optional tools, their purpose, data collection and applicable consent requirements should be reviewed and the disclosure updated as needed.
4. Essential functionality
Some technologies may be necessary to serve pages, protect the site, maintain a required session or remember a privacy choice. Where applicable law allows an essential-function exception, it is limited to technologies that actually meet that requirement, rather than everything a provider chooses to install.
Blocking essential technologies can affect the underlying hosting platform or other site functions. The custom text, navigation and locally validated form do not require an advertising or analytics cookie. A provider’s technical label does not determine whether a technology is legally essential in every jurisdiction.
5. Preferences and optional functionality
A deployed theme or application may remember a language, display choice or other user-selected setting. Such technologies should have a defined purpose and retention period. Their treatment under applicable law depends on what they do and whether they are necessary for the requested function.
The custom sections do not currently add a persistent theme, language or display preference. Any optional feature that later stores such a choice must be assessed on its actual behavior. This policy should be revised when a materially new storage practice is introduced.
6. Analytics and advertising
No analytics service or advertising pixel is installed by the custom sections themselves. If optional analytics, conversion tracking or advertising tools are added elsewhere in the site, they may collect information about visits, interactions or referrals. Those activities require appropriate disclosures and controls.
Where consent is legally required, optional tracking should remain inactive until the relevant consent is obtained. A visitor must be able to change an applicable choice. Loading a resource, opening the enquiry modal or completing the local form is not treated by these custom sections as consent to advertising tracking.
7. External fonts and image delivery
The website loads the specified typefaces through Google Fonts and displays images through Shopify-hosted resources. Requests to those providers can expose an IP address, requested resource and ordinary browser connection information. The custom implementation does not use those requests to create an advertising profile.
A resource request is not always a cookie, but it can still involve personal information depending on applicable law. Provider behavior is governed by its own systems and notices. The Privacy Policy explains this distinction in the context of the information handled by the site.
8. Managing browser settings
Most browsers let you view, delete or restrict cookies and stored site data. The options may include blocking third-party cookies, clearing data when the browser closes and setting permissions for an individual site. Use your browser’s current settings or help information for the specific steps.
Deleting cookies or site data may also delete preferences and require a hosting or third-party service to recreate a session. Private browsing changes how some information is retained, but it does not make all network requests anonymous or prevent infrastructure providers from receiving connection information.
9. Privacy signals and consent controls
Some jurisdictions or platforms recognize specific browser privacy signals or opt-out mechanisms. Any implemented preference mechanism should be assessed against the actual activity, provider capabilities and applicable law. This policy does not promise that an unsupported signal automatically controls every third-party tool.
If you have a question about optional tracking on the deployed site, contact us with the page, approximate time and browser details. Do not include unrelated identifiers or private account information. We can review the reported behavior and clarify which part of the deployment is involved.
10. Changes and contact
Changes to the theme, applications, embedded resources or provider behavior can change the site’s storage and tracking practices. This policy should reflect the current deployment. The updated date identifies this version; it is not a representation that every possible application has been audited.
Questions about this policy can be directed to the contact details below. Please identify the technology or behavior you are asking about so the response can address the actual issue rather than a hypothetical feature.
Contact Fendrick Launch
EMAIL: projects@fendricklaunch.com
ADDRESS: 40 Northtown Drive, Jackson, MS 39211, United States
PHONE: +1 601 201 9811