Page at a glance
What you need to know before reading further.
A quick look at who this page is for, what it covers, and which official sources back it up.
Best for
What it helps you do
Core questions answered
- Which data flows are disclosed for email capture, analytics, and checkout?
- What user rights or contact details should the final policy include?
- Which legal and trust pages should sit beside privacy?
Official bodies in play
Related guides
Keep the research chain moving.
These pages cover closely related topics and are good next reads from here.
Best next steps
The most useful pages to read next based on where you are in the process.
Planning systems and printable versions
Printable guides and structured pathways that tie this topic into your wider move plan.
Related in the wider move plan
Pages from other sections that answer overlapping questions or involve the same agencies.
The short version
If you browse the site, use a free checklist form, email support, or buy a digital guide, this page explains the basic privacy rules around that activity.
It is written to reflect our current practices with live checkout, first-party analytics event tracking, and free lead-capture forms in mind. Stripe handles payment processing, lead and event records can be stored in the site database, and this page should be updated again if those provider choices change materially later.
What this means in practice
- We do not want surprise data collection doing weird side quests behind the scenes.
- If you use a free checklist or starter-pack form, we use that information to deliver the resource, understand which topics people care about, and support future updates you asked for.
- If you contact support, we use that information to answer the message you sent.
- If you buy a digital product, we use the purchase and delivery details needed to process the order and support the delivery.
- If new tools, analytics, or vendors materially change the picture, this page should be updated again.
What information may be collected
The site currently falls into four practical buckets: browsing, free forms, support contact, and commerce activity.
Browsing public pages
Like most websites, the site and its hosting environment may generate technical logs related to requests, performance, uptime, and security. That is normal site operation, not a membership system or private account area.
Free checklists and starter packs
If you request a free checklist or starter pack, the site may store the email address you submit, the resource requested, the page where the request happened, and related first-party event data needed to understand basic funnel behavior and follow-up interest.
Support emails
If you email support@sblocktechnologies.com, the information you include can be used to answer your question, investigate an issue, resolve delivery problems, or review a correction.
Checkout and delivery
Order details needed for payment, confirmation, fraud prevention, and digital fulfillment may be processed through Stripe and the site’s order and delivery systems, including database-backed records needed to verify access and support delivery follow-up.
How information may be used
The intended rule is purpose-first use.
In plain English: if you use support, we use the information to support you. If you place an order, we use it to process and fulfill that order.
Core uses
- Operating, securing, and improving the website.
- Replying to support, correction, or partnership messages.
- Processing digital-product transactions and handling delivery or access follow-up.
- Maintaining records needed for accounting, fraud prevention, compliance, or dispute handling where applicable.
What this policy does not try to hide
A few practical limits matter here.
No current member account system
Public site content can be read without creating a user account. If that changes later, the privacy explanation should change with it.
Our vendor list is reviewed periodically
This page does not pretend a final analytics, checkout, or delivery vendor list exists before those tools are actually enabled. Once they are, the policy should name them clearly.
No physical shipping promise
The current product model is digital. That means delivery and support are expected to revolve around electronic access, not physical shipment logistics.
Questions, updates, and related pages
If you want the support route or the commerce side explained more fully, start with these pages.
Best next pages
Sources and basis
What this privacy page is based on
This policy is grounded in the site’s current operating model: public content, direct-email support, live checkout, database-backed order records, and digital-product delivery through protected access pages.