Privacy Notice

1. Who is responsible

Puzinski LLC determines how its own business inquiries are handled. Where Puzinski later handles personal data for a client under instructions, the client engagement and an appropriate data-processing agreement must identify the parties’ roles and duties.

2. Information provided through the website

A quick inquiry collects name, email, selected service, and a description of the goal; business name, a public link, and timing/budget context are optional. A focused review request collects its subject and goal. The detailed project brief can include name, business email, optional phone, role and decision authority; business name, niche, model, locations, customers and goals; selected services/programs; current tools, processes, approximate volumes and aggregate results; budgets, timing, access readiness, public references, and free-text context. Some core fields are required to assess the inquiry; supporting scope fields are optional.

A privacy request can include a reply email, request type, and limited supporting information. Please do not submit passwords, payment-card details, identity documents, patient/customer records, private contact lists, or confidential project files. If sensitive material becomes necessary for contracted work, an appropriate process must be agreed first.

3. Technical information and browser storage

Netlify hosts this website and provides server-side Web Analytics based on requests to its infrastructure. Analytics reports include pageviews, unique visitors derived from IP addresses, approximate locations, referring sources, missing resources, and bandwidth. The current plan provides reports for up to 30 days. This reporting uses hosting request data rather than a visitor analytics script installed by this application. Netlify also processes security and operational logs under its terms.

Inquiry forms can include the current public page path, a limited referring-page path or referring hostname, and allowlisted campaign source/medium/campaign labels carried through site links. Full referring URLs and query strings are not collected in these form fields, and form answers are not stored as browser drafts. This limitation concerns our inquiry fields, not Netlify’s infrastructure request processing. After an explicit Allow analytics choice, Google Analytics receives page views and allowlisted events for inquiry selection, form starts, steps, errors, and successful inquiry submissions. A successful submission is recorded as a lead event, not a sale or a qualified opportunity. Fields supplied by our application are limited to the public page path, form type, permitted service identifier, and step number. Where present, recognized campaign source/medium labels from a fixed list may be used for attribution; arbitrary campaign names and other query values are not sent to Google Analytics. Form answers, names, email addresses, project messages, URL query strings, and URL fragments are not included in the events we send. Referring URLs are reduced to their origin. Google still processes network information, analytics identifiers, and device/browser context to provide its service. The property uses a two-month user/event data-retention setting with reset on new activity off; standard aggregated reports are subject to Google’s separate reporting behavior. This application stores a motion preference under the sessionStorage key puzinski-effects. Fonts and visual assets are served with the site. See the Cookies & Storage Notice. The Google Analytics tag is loaded only on the production domain after analytics consent. The application uses basic consent behavior: declining does not load the Google tag or send cookieless analytics pings. Advertising consent remains denied; Google signals and advertising personalization are disabled in the tag configuration. Enhanced measurement is disabled for the web stream; the application sends the limited events described here. No Google Tag Manager container, Meta/TikTok advertising pixels, session replay, or third-party chat widget is installed. The Google tag script is delivered from a googletagmanager.com URL; that hostname does not mean a Tag Manager container is installed.

4. How information is used

Information is used to evaluate fit, understand requirements, communicate about the inquiry, prepare or negotiate a proposal, operate and protect the website, manage legitimate business records, respond to requests, and meet applicable legal obligations. Inquiry submission does not subscribe you to a marketing list.

If a later marketing subscription is offered, its choice and unsubscribe process must be separate from a project inquiry. We do not promise to use information for a different incompatible purpose without the disclosures or permissions required by applicable law.

5. Providers and disclosure

This website uses Netlify for hosting and Netlify Forms to receive and store submissions. Submission notifications are sent to our designated business inbox through Microsoft 365, provided by GoDaddy. A Google Gmail inbox may retain earlier inquiry notifications from the initial setup; new notifications are directed to the business inbox. Telegram also receives notifications in a designated private business-owner chat, sent by a server-side bot. Notifications include the submitted form answers and the limited source/campaign context described above; longer briefs are delivered as a text attachment. This applies to project inquiries, review requests, and privacy requests. These copies are used to review and respond to submissions. Telegram processes them under its own terms and privacy practices. These providers process information needed to host the website, handle submissions, or deliver notifications. Google provides the optional Analytics service after consent, under its own service and privacy terms. Read Google’s Privacy Policy and how Google uses information from sites using its services. Optional receipt and CRM integrations remain disabled; Resend and a separate CRM do not receive inquiry data through those integrations. Before enabling additional providers, this notice must be updated to describe the actual data flows. Privacy requests are excluded from sales/CRM delivery. Access is limited to people and providers who need it for the stated business purposes.

Information may also be disclosed when required by law, to protect lawful rights or security, with your direction, or in a business transaction subject to applicable protections. Current website inquiry data is not sold or shared for cross-context behavioral advertising. Adding advertising or analytics tools requires a fresh review of the actual data flows, disclosures, and choices.

6. Client projects and AI

The public site’s interactive examples and problem finder are illustrations and rule-based interfaces. The current application does not send inquiry answers to a model API. Infrastructure providers may operate their own security and anti-abuse processes under their terms.

Client projects may involve CRM, messaging, cloud, development, or AI services selected for the engagement. Before personal or restricted client data is introduced, the agreement must identify authorized purposes, vendors, access, instructions, retention, and any required additional terms. This website notice is not a blanket authorization to process a client’s customer data or use it to train models.

7. Retention and safeguards

Inquiry and business records should be retained only for the purposes described, including an active discussion, a resulting engagement, legal recordkeeping, or a dispute. The relevant period depends on the type of record and applicable obligations; this draft does not assert that an automated deletion schedule already exists.

Appropriate administrative, technical, and organizational safeguards must reflect the data and processing involved. No website transmission or storage method is guaranteed secure. This notice is not a claim of a security certification, audit, HIPAA compliance, or a specific vendor retention configuration.

8. Requests and choices

Depending on applicable law, you may have rights to access, correct, delete, obtain a copy of, restrict, or object to certain processing, withdraw consent where processing depends on it, or complain to a regulator. These rights may have lawful exceptions. We may need to verify identity or an authorized agent’s authority using information proportionate to the request.

Use the privacy-request form below, email info@puzinski.com, or the business mailing address. You do not need to complete the business questionnaire or accept a service agreement to make a privacy request. We will assess requests under the applicable law; submission does not itself establish identity or require disclosure of someone else’s data.

9. Visitors in other places, children, and browser signals

The agency is based in New York and providers may process information in the United States or other locations. If a particular engagement triggers additional international transfer or data-protection requirements, the appropriate arrangements must be assessed and agreed. This draft does not claim that every worldwide privacy regime applies or that a transfer mechanism is already in place.

The site is intended for adult business representatives, not children. Contact us if you believe a child submitted information. Current application code does not implement cross-site advertising tracking; there is no advertising-sale/share feature to turn off. The application keeps optional Google Analytics off when it detects Global Privacy Control. Analytics is also off until an explicit choice to allow it. Analytics settings in the footer let visitors decline or withdraw consent; withdrawal disables further application analytics events and clears accessible Google Analytics cookies on this domain. These browser choices do not erase Netlify infrastructure logs or previously collected provider records. A Do Not Track signal does not separately alter the server-side hosting reports.

10. Updates

The final notice must carry its actual effective date and reflect the production setup. Material changes will be disclosed as applicable law requires. An updated notice does not retroactively authorize an incompatible use of previously collected data.