Skip to content
Legal

Privacy Policy

How So It Sticks handles information submitted through this website and during website projects and continuity services.

Effective: October 13, 2026
Plain-language summary. SIS collects information people choose to submit so we can answer inquiries, return Website Check results, start and manage projects, receive website review feedback and final-acceptance requests, process payments and provide ongoing service. The current site uses Netlify Forms for its website forms and Stripe-hosted checkout for payments. Do not submit passwords, full card numbers or private customer records through ordinary SIS forms.

1. Scope

This Privacy Policy applies to information SIS receives through soitsticks.com, website assessments, project briefs, the project Start form, the Launch form, the project-review and project-acceptance forms, referral submissions, file uploads, shared-folder links, payments, project communications and related SIS services.

It does not control how an outside website, payment provider, storage provider or other third-party service handles information under its own terms and privacy policy.

2. Forms currently used on the website

The site currently includes these Netlify Forms:

  • website-assessment — receives the email address of a visitor who asks for a Website Check action plan, together with the visitor's answers, the outcome the check identified (get found, earn trust or close business) and the suggested priorities.
  • website-inquiry — the homepage Project Brief. Receives name, email, business name, current website, the build or service the visitor is considering and what the website should help customers do.
  • project-start — the private Start form at /onboarding. Receives project intake information including client/business identity, Project ID, industry, business information, customer types and desired outcomes, reference website links and notes, tools the site should work with, an optional video link, logistics, small file uploads and shared-folder links.
  • launch-handoff — the private Launch form at /launch. Receives client/business identity, Project ID, the domain, registrar and DNS manager, how the client will give SIS access, tools to connect, an optional mailing-list link and notes. It does not accept passwords.
  • project-review — receives consolidated revision feedback including client/business identity, Project ID, version and review round, requested changes, corrections, design/image feedback, launch blockers, optional files and shared-folder links.
  • project-acceptance — receives a final-acceptance request: Project ID, final version identifier, preview URL, scope reference, approver name and email, the acceptance acknowledgement and a client-side timestamp. SIS confirms each request directly with the named approver before requesting final payment.
  • referral-submission — receives the referrer's name and email, the referred business and contact details and a note about the introduction.
  • agreement-signature — after server-side package validation, receives the Project ID, business/client identity, MSA and SOW version identifiers, agreement-package fingerprint, encrypted agreement token, signer name/title/email, electronic-consent acknowledgements, authority-to-bind acknowledgement, typed electronic signature, client-side timestamp, server-side validation timestamp and verification status.

Netlify processes these website form submissions as the form service used by the current site.

3. Information we collect

Depending on how you interact with SIS, we may receive:

  • name, email address, phone number and business name;
  • website/domain information;
  • assessment answers and calculated assessment results;
  • project package, Project ID, business description, customer information, primary actions, offers and project goals;
  • company story, credentials, authorized testimonials/reviews and other source material you choose to provide;
  • current-site or Version 1 feedback;
  • integration/vendor information and project deadlines;
  • files uploaded through project forms;
  • links to folders or files you share through services such as Google Drive, Dropbox, OneDrive, iCloud or another provider;
  • project approvals, review comments, support requests and service history;
  • electronic agreement records, including agreement versions, package fingerprint, encrypted package token, signer identity/role, electronic-consent acknowledgements and typed signature;
  • payment status, amount, purchased service and billing/contact information made available to SIS by Stripe or another disclosed payment provider;
  • referral-program information where applicable;
  • technical information that hosting, security or third-party service providers may receive automatically as part of operating their services.

4. How we use information

  • respond to assessments and inquiries;
  • determine project fit and prepare scopes, SOWs, proposals and invoices;
  • create and manage a client project under its Project ID;
  • prepare, present, record and retain electronic client agreement packages and signature records;
  • review source material and build agreed website deliverables;
  • reconcile Version 1 feedback and revisions;
  • verify project facts, assets, integrations and launch requirements;
  • process project installments, invoices and recurring payments through Stripe or another disclosed provider;
  • provide continuity, maintenance and support services;
  • administer the Referral Partner Program;
  • operate, secure, troubleshoot and improve SIS services;
  • maintain reasonable business, accounting and contractual records;
  • comply with applicable legal obligations and protect against misuse or fraud.

5. Project IDs and internal project records

SIS uses a Project ID as the primary operational key for a client project. Forms also collect business_name and client_email so submissions can be reconciled to the correct project.

Netlify form submissions are capture records; SIS may maintain a separate internal project record and project folder that references or contains relevant submitted information and authorized project materials.

For the electronic agreement workflow, SIS uses an encrypted agreement-package token and a SHA-256 package fingerprint to associate the signature record with the identified Project ID, SOW version and MSA version. The agreement page is designed to let the signer download or print the agreement before signing.

The project-start and project-review forms may accept small file uploads. For larger asset libraries, SIS may ask the client to share a folder or file link from a third-party storage provider.

Clients should provide only material SIS needs for the project and should avoid sending passwords, full payment-card information, private customer records, government identification numbers, health information, tax records or other unnecessary sensitive data through ordinary SIS forms or shared folders.

Third-party storage providers control their own accounts, access rules and privacy practices.

7. Payments and Stripe

SIS uses Stripe-hosted payment services for approved project installments and may use Stripe for invoices or recurring service payments.

Stripe may collect payment, transaction, device and identifying information under its own privacy practices. SIS generally does not receive or store a full payment-card number through the SIS website.

Stripe's privacy policy is available at stripe.com/privacy.

8. Analytics, interaction events and cookies

At the effective date of this policy, the SIS site code reviewed for this policy does not have a general network analytics provider wired into it.

The site includes a browser-side interaction event layer that can identify events such as an email-link click, Stripe-checkout click, external-link click, project-brief click, build preselection, completed Website Check outcome, project-brief submission or form-submission attempt. That current event layer does not itself send a network request, set cookies, use browser storage, include query strings or include form values.

If SIS later connects an analytics provider or changes the site's cookie/storage behavior, this Privacy Policy should be updated to describe the actual provider and data practices.

Third-party pages or services you choose to open, including Stripe or a shared-folder provider, may use their own cookies or tracking technologies under their own policies.

9. Service providers and disclosures

SIS may disclose information to service providers and contractors only as reasonably needed to operate the website, process forms/payments, deliver client work, host/deploy sites, provide technical support or operate the business.

The current website implementation verifies Netlify as the website form/hosting platform and Stripe as a payment provider. Other project-specific providers may be used when a client supplies or approves them.

SIS may also disclose information when reasonably necessary to comply with law, respond to lawful requests, enforce agreements, protect rights or security, prevent fraud or complete a business transfer.

10. Data retention

SIS does not state a single fixed retention period for every record type because project, payment, accounting, contractual and operational records may have different requirements.

Information is retained only as reasonably necessary for the purpose for which it was collected, to provide services, maintain appropriate business records, resolve disputes, enforce agreements and satisfy applicable legal obligations.

SIS should not retain credentials merely because a project is archived.

11. Security

SIS uses reasonable administrative and technical practices appropriate to the information and services involved, but no online service, transmission method or storage system can be guaranteed completely secure.

Clients should use provider-supported collaborator, delegated-user, OAuth, API-key or similar controlled-access methods where available rather than sending passwords through ordinary forms.

12. Client responsibility for submitted material

Clients are responsible for providing only information and materials they are authorized to share. This includes photographs, logos, testimonials, customer information, documents and data from third-party systems.

SIS websites and projects may link to or integrate with outside systems. Their own terms and privacy policies govern their handling of information.

A client project may also introduce additional privacy, cookie, consent, regulatory or data-processing requirements. The client is responsible for identifying legal requirements specific to its business, and SIS implements agreed technical controls within the approved scope.

14. Children

SIS services are directed to businesses and adults. The website is not designed to solicit personal information from children under 13.

15. Your requests

You may ask SIS to correct information you previously submitted, ask questions about how information is handled, or request deletion where legally and operationally appropriate. SIS may need to verify identity before acting on a request.

16. Changes to this Policy

SIS may update this Privacy Policy when the website, forms, vendors, project workflow or legal obligations change. The effective date above identifies the current version.

17. Contact

Privacy questions or requests may be sent to brian@soitsticks.com.

Operating rule. SIS should update this policy when actual tools or data flows change. Do not add a processor, analytics service, cookie practice, storage claim or retention promise here unless the practice has been verified.