Privacy, terms, and policies in plain language

How to use this information

Start here for orientation:

What this document covers — the same ground as a serious privacy notice plus terms for this public marketing surface, how third-party tools fit, what ships in the browser, how updates are recorded, and a shortcut lane for inboxes and external pointers.
Who should read it — anyone who loads pages here, including people who only browse and people who use Contact or Get Started for a real introduction.
How the sections below fit together — seven top-level lanes (operator, privacy, terms, third parties, stack, changes, quick reference) you can read in any order. Use the table of contents to jump; footnote ² explains how to open it on small screens versus larger ones.

What this is

This information tells you what happens when you use this site. No padding, no mystique.

It covers:

How your data is handled
What happens when you browse or interact
What rights and controls you have
How third-party tools fit in

Statute and regulators still govern if there is a conflict.

We wrote this in plain language on purpose, but that is a clarity choice, not a downgrade.

This is the same class of document as the privacy notices and terms you would expect on a site that ships real work, with the same intent. Use the references when you want to drill in.¹

Who should read this

Anyone who visits this site.

Even if you never fill out a form:

Browsing still creates technical logs
Third-party tools may run (if enabled)

How it's organized

There is a table of contents for this document so you can jump without rereading from the top.

Each top-level section below is a lane you can move between directly:

Who runs this site
Privacy
Terms of use
Third-party sites and tools
Open source, stack, and transparency
Changes and version
Quick reference

Reference the table of contents for more detail about what sits inside each lane.^2:1

Who runs this site

Luckgrid operates this surface as controller. That covers who to email for rights and legal questions, how light-touch identity checks work, and how the contact form sits next to formal channels.

Operator

Luckgrid, Inc. operates this site.

Luckgrid decides why and how data is used. Vendors (hosting, analytics, and so on) only process it under contract and for the job they are hired to do.

Contact and requests

To:

Access your data
Correct it
Delete it
Ask privacy or legal questions about this document

Email admin@luckgrid.net.

Whether you use Contact (footer on every page) or Get Started (homepage hero), you get the same contact form with one submission path. It is meant for real introductions and real business context. It is the wrong place to prove identity for a privacy request or to unload sensitive material. For that, use admin@luckgrid.net so the thread can be handled with care.

Why identity checks happen

Some requests require verifying who you are.

This prevents:

Impersonation
Accidental data disclosure

Verification is kept minimal and proportional.

Privacy

Collection, retention, cookies, analytics, AI vendors, security posture, and the rights language in one lane so you do not have to hunt across marketing copy for the same facts.

Some regions require consent before tracking runs. Luckgrid is planning a first-party layer here. It would add granular choices for what runs, documented defaults, and logging that can stand up to a serious review. A public roadmap for that work may ship later. Until it is live, your practical controls are still the browser and platform settings already on your device. For timing, scope, or procurement questions, email admin@luckgrid.net.³

When it ships, the plan is to:

Let you choose what runs
Provide granular control

Until then:

Use browser controls.⁴

What this site is (and may become)

Right now, this is a marketing and content site with pages, posts, and the Contact / Get Started path described here.

It may grow later (forms, accounts, payments, integrations). When it does, this document is expected to move with it.

If it does:

This document is updated when those changes happen, not after the fact.

Future-facing tools (conditional)

Some tools mentioned here may not always be active:

Cookie/consent systems — banners, preference centers, or similar wiring so people can see and flip non-essential cookies or tags before they run, where the law expects that upfront choice.
Analytics — traffic, paths, and content performance so Luckgrid can see what is working instead of guessing. May be first-party only or go through a vendor, depending on how the site is wired at the time.
Advertising pixels — small tags or requests that tie visits to campaigns, support remarketing, or tune delivery when paid ads are actually on.
Email systems — outbound and inbound mail for marketing, lifecycle, or transactional messages (confirmations, follow-ups, and the like), usually through a provider that brings its own deliverability and suppression rules.
Payment processors — checkout, invoicing, or subscriptions if paid products or deposits show up later. Card and bank data stay with the processor and its compliance stack, not in a contact form.
Hosted AI and model APIs - when used, only inside Luckgrid's internal delivery workflows, not as silent tracking on every page load. See AI providers and models for how client context is handled and how vendor terms apply.

If they're not live, they don't run.

What you send on purpose

Contact or Get Started

Contact (site footer on every page) and Get Started (homepage hero only) both open the same contact form. There is only one submission path.

The form collects:

Email (required) — so we can reply and correlate your message.
Name (optional, recommended) — helps us address you properly and reduces the chance your message reads like anonymous spam or cold prospecting noise.
Brief message (optional, recommended) — context for what you are looking for; a blank or generic submission is more likely to be deprioritized.

Used to:

Respond
Follow up
Operate the business around that interaction

What not to send

Do not put any of the following in this form (the one behind Contact or Get Started). Regulated and high-risk material belongs in purpose-built, secured channels, not a generic inquiry field.⁵

Health data — Diagnoses, treatment details, insurance member numbers, and similar information belong under HIPAA-aligned or other clinical pathways, not here.
Government ID numbers — Passport, national ID, tax identifier, driver's license number, or similar. Identity and government services use verification flows built for that risk, not a general-purpose contact box.
Financial account details — Payment card numbers, CVV, full bank account numbers, wire instructions, or other credentials that move money. Card and bank data stay with payment processors and PCI-scoped systems, not pasted into this form.
Passwords or credentials — For any service (including Luckgrid accounts, if they exist). Secrets go through the product's real sign-in, reset, or support flows, not arbitrary text fields.

If it would feel wrong to paste it into a normal email to someone you do not know, it does not belong in this form.

What gets recorded automatically

When you visit, your browser sends:

IP address
Browser and device info
Time of request
Pages visited and referrer
Errors and diagnostics

That is how the web works at baseline. The goal here is still to collect only what the site needs to run.

Where it lives

This data is stored in:

Server logs
Hosting systems
CDN/DNS infrastructure

It's required to run and secure the site.

Cookies, pixels, and storage

What these are

Cookies — small files the site (or embedded third-party tools) may store in the browser to remember sessions, preferences, or measurement identifiers; you can clear or block them in browser settings.^4:1
Pixels/tags — tiny images, scripts, or one-pixel requests that report an event such as a page view, signup, or purchase to an analytics or advertising platform.
Local/session storage — browser APIs related to cookies that can hold short-lived or larger blobs of text on your device; used sparingly for state, experiments, or tool-specific data instead of round-tripping everything to a server.

They support:

Functionality
Measurement
Advertising (if enabled)

Analytics and advertising (when enabled)

Analytics may measure:

Traffic
Usage patterns
Content performance

Advertising tools may:

Track conversions
Build audiences
Optimize campaigns

They operate under:

Their own policies
Your platform-level settings

AI providers and models

Luckgrid may use hosted AI platforms and models (LLMs and related APIs) on internal delivery work such as research, drafting, code help, analysis, and the other unglamorous tasks behind shipped work. That is separate from dropping an AI widget on every page view. Reading this site does not require your browser to load a proprietary model to render static content.

Client and identifying context

Before anything that could tie to a specific client, account, or identifiable person becomes context for an AI tool (prompts, retrieval, attachments, or automated chains), Luckgrid abstracts, generalizes, aggregates, or strips identifying detail so the model sees patterns, structure, and minimized information, not raw names, credentials, production secrets, or full dossiers. If you would not paste it into a vendor console by hand, it does not go into an automated pipeline either. If it cannot be responsibly abstracted, it does not go in.

How AI is used in practice

AI is a tool, not a substitute for ownership. Practitioners who are accountable for the outcome (engineers, designers, architects, and other specialists) use it for speed and exploration, then edit, review, and check output against requirements, risk, and facts. Where code or infrastructure is involved, changes still go through real testing (and peer review when it matters) before production or client-facing delivery. Models can be wrong, biased, or overconfident. People stay responsible for what Luckgrid publishes and ships.

Vendor terms

Each provider carries its own privacy policy, retention rules, and (where applicable) training or logging terms. Read those sources directly when you need vendor-level detail. Luckgrid cannot restate them here.⁶

Why data is used

Data is used to:

Run and secure the site
Respond to messages
Improve the experience
Support marketing (where allowed)
Meet legal obligations

Principle:

Collect what's needed. Don't keep it longer than necessary.

Who receives data

Service providers

Vendors (hosting, email, analytics, and, where used, hosted AI and model services) may process data only to deliver what Luckgrid contracted them for, under those contracts, and without a free hand to repurpose it for unrelated product work.

For AI-specific handling and how client context is minimized before model use, see AI providers and models above.

Professional advisors

Lawyers, accountants, and auditors may see data when the work truly requires it, under confidentiality.

Legal and business events

Data may be disclosed:

When required by law
To protect safety or systems
During mergers or acquisitions

Data from the contact form (Contact or Get Started) is not sold or rented.

If this ever changes:

It will be stated clearly
Opt-outs will be provided where required

Legal bases (where required)

Depending on region, processing may rely on:

Consent
Legitimate interests
Contract
Legal obligation

Consent is explicit when required
You can withdraw it

Withdrawal stops future processing tied to consent.

Your rights

Depending on where you live, you may:

Access your data
Correct it
Delete it
Restrict or object
Request portability
Opt out of certain uses

How to exercise rights

Email admin@luckgrid.net with enough detail to find the right records. Sensitive requests may include a short verification step to prevent mistakes and abuse.

You may also:

Appeal decisions
Contact regulators

Email communications

Luckgrid keeps marketing mail honest. That includes one-click unsubscribe where the law expects it. Transactional mail (receipts, security notices, submission acknowledgments) may still arrive because it is tied to an action you took or a relationship Luckgrid must honor.

Browser and platform controls

You can manage tracking via:

Browser settings^4:2
Ad platform settings⁷
Industry opt-out tools⁸

International visitors

Data may be processed outside your country because vendors and infrastructure do not all sit in one jurisdiction.

Where the law expects it, Luckgrid relies on appropriate safeguards (contractual and technical) instead of treating borders as an afterthought.

Children

This site is not directed at children requiring parental consent.

Parents and guardians. If you believe a child who needs parental consent in your region submitted personal information here, email admin@luckgrid.net. Luckgrid will work with you on deletion or other sensible next steps under applicable law.

Data retention

Data is kept based on purpose:

Messages — for communication, follow-up, and a proportionate business record
Logs — for security, abuse response, and troubleshooting
Analytics — according to each vendor's settings and our configuration

Then deleted or anonymized when no longer needed for those purposes.

Retention is not a default hoard policy. Operations, law, and security set the floor; minimization sets the aim. For how long that tends to mean in practice, regulators publish useful framing (for example storage limitation under the GDPR).⁹

Security

Safeguards are meant to sit above a brochure-site baseline. That means defense in depth, least privilege on services, modern transport encryption for data in motion, patching and dependency hygiene, and a hard line between the public marketing surface and anything that stores submissions. No stack is bulletproof; the choices here are informed by years of shipping and running production systems, not weekend experiments.

You should still treat the public web as a shared street. Use unique passwords, current devices, and a quick flag if something looks off.¹⁰

Terms of use

Rules for the free public marketing site run from acceptable use through liability caps. They cover intellectual property, what you grant when you submit a message, disclaimers on content, and how liability is capped when there is no separate paid contract.

The agreement

By using this site, you agree to these terms.

If you disagree, stop using it.

Separate agreements apply to paid services.

Acceptable use

You may (ordinary, lawful use), for example:

Read, search, quote reasonable excerpts, and link to public pages
Use feeds and accessibility tools in line with their normal purpose
Use Contact or Get Started for genuine business or partnership inquiries. Both open the same contact form.
Inspect the public site in a browser (including developer tools) for your own understanding

Do not:

Disrupt the site or other users (including denial-of-service style behavior)
Attempt unauthorized access, credential stuffing, or bypassing technical limits
Upload or transmit malware, unlawful material, or content intended to harass or defraud
Misrepresent who you are in a way that could harm others or Luckgrid
Break the law or ask Luckgrid to break the law

Access may be restricted to protect the site.

Intellectual property

Luckgrid-owned material on this site is owned or licensed by Luckgrid.

Articles and long-form content may include third-party material for reference, attribution, illustration (including labeled placeholders), or royalty-free / commercially licensed stock, in line with each source's terms and labeled in context when that is practical. Rights stay with the owners. Do not treat the page as a blanket license to reuse that material beyond what law or the upstream license already gives you.

Do not reuse Luckgrid material beyond what law allows without permission.

Your submissions

You keep ownership of your content.

You grant Luckgrid a license to:

Use it to operate the site
Respond to you

Disclaimers

The site is provided:

"As is"
"As available"

About insights, use cases, and marketing content:

Posts, whitepapers, annotated breakdowns, and similar material are grounded in real product, engineering, and field work. They exist to sharpen decisions and shorten learning curves, not to replace regulated, fact-specific professional advice (legal, tax, securities, medical, or other licensed counsel) unless Luckgrid signs a separate written agreement that says otherwise.

Reading this site does not create an attorney-client, doctor-patient, or other fiduciary relationship.

Limitation of liability

To the extent allowed by law.

Luckgrid is not liable for:

Indirect or consequential damages
Lost profits, revenue, or data
Decisions you make based on general educational content on this site (see disclaimers above)

Direct damages tied only to use of this free public marketing site (not a separate paid engagement) are capped at the greater of $100 USD and what you actually paid Luckgrid for the specific service behind the claim, if anything was paid.

Third-party sites and tools

Vendors run on their own terms and incident playbooks. This lane states the separation rule and points you to their policies when you need vendor-level detail.

The rule of separation

Third parties are not Luckgrid. Their incentives, retention, and incident response are their own.

They operate under:

Their own terms
Their own privacy policies

Common categories

Analytics
Advertising
Email
AI and large language model platforms (see AI providers and models under Privacy)
Payments (if added)

Important

For full details, read each vendor's own policies. Luckgrid does not control their wording or their incident response.

Open source, stack, and transparency

What ships in the browser, which open parts of the stack are named here, and how to ask for repository access or a deeper technical review if procurement needs it.

How this site is built

This marketing site ships as static HTML and CSS, built with open-source tooling and boring web standards, hosted where it can sit close to readers. There is no heavy client-side app shell required just to read a page.

Overview:

Lume — static site generation. Content and templates compile to plain HTML for fast, cache-friendly delivery.
Deno — single runtime for building the site, running checks, and serving the lightweight backend behind the contact form (Contact or Get Started).
Styles — CSS is authored in-house and compiled with Lightning CSS for efficient output.
Datastar — small, standards-friendly layer for interactive pieces (including the contact form opened from Contact or Get Started) without turning the marketing surface into a heavy client application.
Media — fonts and images are prepared at build time so pages stay lean and predictable in production.
PostgreSQL + Resend — database and transactional email for storing and acknowledging submissions from the contact form (Contact or Get Started).
Coolify / Coolify Cloud — deployment and operations across HTTPS, databases, secrets, and production hosting wired as managed infrastructure.
GitHub — source hosting and collaboration for Luckgrid work, alongside the broader open-source ecosystem this stack builds on.

Source and verifiability

What ships is ordinary web content as HTML, CSS, assets, and network calls you can inspect in any browser without asking permission first.

For repository access, a written architecture overview, or procurement and security review, email admin@luckgrid.net.

Why that matters

You can inspect everything in the browser:

View source
Use DevTools
Monitor network requests

Transparency means the behavior is checkable, not just claimed in copy.

Changes and version

How revisions tie to product changes on the site, and where to read the recorded last-updated date.

When this document updates

This document tracks the same commitment as What this site is (and may become). When practice changes, a new tool ships, the law moves, or an error is caught, this text is revised and the Last updated line below moves with it. Quiet drift is not the goal.

Last updated

April 23, 2026

Quick reference

This section gathers the right inbox, tracking controls, and footnote pointers in one place so you can skim without rereading full sections.

Contact

Privacy, data rights, legal questions about this document — admin@luckgrid.net
Marketing inquiries — use Contact (footer on every page) or Get Started (homepage hero). Same form, same path.

Cookies and tracking

Use browser controls^4:3
Consent tooling is in planning; see the Consent subsection under Privacy (footnote ^3:1), or email admin@luckgrid.net.

External resources

Start with:

Ad settings^7:1
Opt-out tools^8:1
Regulator guides¹¹

Final note

A single closing frame on where to start if you want practical control, and how Luckgrid thinks about keeping this document readable over time.

If you want control:

Start with your browser
Then platform settings
Then deeper resources

Luckgrid intends to keep this document clear, honest, and boring in the good way, predictable enough to trust and specific enough to use.