LowCodeStacks™
Sign in

Privacy · Effective November 13, 2026

Privacy notice, in plain words.

What LowCodeStacks collects, why, who processes it, and how to see, correct or delete your information. No ads, no analytics, no tracking cookies.

This notice explains what personal information LowCodeStacks collects, why, and what you can do about it. It applies to lowcodestacks.com.

LowCodeStacks is run independently by its owner, who is responsible for the personal information described here. For anything about your privacy, email contact@lowcodestacks.com.

The short version

  • You can read every guide without an account. We don't run ads, analytics or tracking cookies.
  • If you sign in, we store your email address and what's needed to keep you signed in.
  • We never sell your information.
  • You can ask to see, correct or delete it at any time.

When you browse

No tracking. The site has no advertising, no analytics service, no tracking pixels and no third-party scripts. Our fonts are served from our own site, so your browser doesn't contact a font service.

Server logs. To keep the site working and secure, our application records each request: the page or address requested, the result, and how long it took. It doesn't record your IP address or email address. When you search the site, the words you type are recorded too, so we can see what people look for.

Our hosting provider may also keep standard request logs, which can include IP addresses and browser details, as part of running the service.

Power BI visuals. Our Power BI visuals send no data anywhere, to us or anyone else; the live demos on this site run in your browser on made-up data and send nothing.

When you sign in

You can sign in with a password, with a link sent to your email, or with your Google account. When you sign in, we store:

  • Your email address, and when you confirmed it.
  • If you use Google: Google tells us your email address, your name and your Google account's ID, which we store so we know it's you next time. We don't store your profile photo or any access to your Google account, and we never act in your Google account. Google's own privacy policy covers what Google does when you use it to sign in.
  • If you choose a password: only a scrambled form of it (a salted hash), never the password itself. When you choose one, our server checks it against Have I Been Pwned's list of passwords exposed in data breaches. Only the first 5 characters of a hash of your password are sent, so the service never learns your password or your email address.
  • Failed sign-in attempts: to stop people guessing passwords, we count recent failed attempts for each email address and each network (IP) address. Both are stored only as hashes, and each count is deleted a day after it was last used.
  • Your sign-in sessions: when each started and when it expires (after 30 days). You can see and end them on your account page. Sign-in links expire after 24 hours. Links to confirm your email or set a password expire after 1 hour, and are deleted a day after that.
  • Your choices: whether you accepted the Terms, and whether you agreed to receive optional emails, each with the date.
  • A record of emails we sent you: the type of email and whether it was sent. Not the address or the content. For the weekly email, also whether it was delivered and which of its links you clicked.
  • Deletion requests, if you make one, and what happened to them.
  • Downloads of Power BI visuals: we count how many times each version is downloaded each day, in total. We don't record who downloaded it. To stop downloads in bulk, we count recent downloads for each account; the count is stored only as a hash and deleted a day after it was last used.

Emails

We send email when you ask for it: a sign-in link, a link to confirm your email or set a password, or confirmation of a request you made.

The weekly email is off until you say yes: on the welcome page when you make an account, when we ask you once on the site, at the end of a guide, or in your privacy settings. If you do, we email you once a week, on Tuesdays, with links to what we published that week. Every weekly email says who it's from, gives our postal address, and has an unsubscribe link, and your mail app's own Unsubscribe button works too. Unsubscribing takes effect straight away.

To see which links are useful, each link in the weekly email goes through our site first: we count the click against your copy of that email, then take you to the page. We don't track whether you open it; there is no tracking image. Resend, which delivers it, tells us whether it was delivered, bounced or was marked as spam. If your address bounces for good, or you mark the email as spam, we stop sending you the weekly email.

Feedback on guides

You don't need an account to tell us whether a guide helped.

  • "Did this fix it?" We store only your answer, which guide it was about, and when. Nothing about you.
  • "Something here changed?", and "Report a problem" on a component. We store your note, which guide or component it was about, and when. Please don't put personal details in a note: we can't reply to it, and we delete each note once we've checked it.
  • Limits: to stop votes and notes being sent in bulk, we count recent ones for each network (IP) address. Addresses are stored only as hashes, and each count is deleted a day after it was last used.

Comments and your profile

If you're signed in, we give you a display name and an avatar at random, which you can change on your profile page. When you comment, we store the comment, the guide or component it's on, the comment it replies to if it's a reply, when you posted it, and your account. Your comment is public, shown with your display name and avatar, never your email address.

  • You can delete your comments at any time; they're gone straight away. If others have replied to one, an empty placeholder stays so their replies keep their place, without your text or your name.
  • If we remove a comment that breaks the Terms, we keep it, hidden, so a mistake can be undone. It's deleted with your account.
  • Anyone can report a comment. We keep only that it was reported and when, nothing about who reported it. To limit abuse we keep a scrambled (hashed) counter for each address for a day.

Replies, mentions and notifications. On a component's page you can reply to a comment, and mention someone in the conversation, or the LowCodeStacks team, by typing @ and their name. When someone replies to you or mentions you, we store a notification: who it's for, which comment it's about, and whether you've seen it. Only you see your notifications, under the bell at the top of the site.

Emails about replies and mentions are off until you turn them on, on your notifications page. If you do, we email you when someone replies to you or mentions you. The email says who and where, never what they wrote; we send at most 20 a day, and each has a link to turn them off. Like every email we send, we keep a record of it: what kind it was, when, and whether it was delivered.

Ratings and "Worked in my app". If you're signed in, you can rate a component from 1 to 5 stars, and you can say it worked in your app. They're separate: you can do either without the other. With "Worked in my app" you can add the Power Apps Studio version you used, if you want to. We store your rating, that it worked, the version if you gave one, the component and your account. Others see only the totals: the average rating and how many people it worked for, never who. You can change your rating, or take back "Worked in my app", at any time, and both are deleted with your account.

Learn progress

If you're signed in and mark a lesson as done, we store which lessons you've finished and when. If you finish a practice mission, we also store your best score, how many times you've finished it, and when you first got everything right. Only you see it. You can clear it on your profile page, and it's deleted with your account.

Cookies

We use only the cookies the site needs:

  • Sign-in cookies keep you signed in and protect sign-in forms. They are set only when you use the sign-in page or are signed in, and the session cookie lasts up to 30 days.
  • lcs-theme remembers light or dark mode, and is set only if you choose one. It lasts a year.

There are no advertising, analytics or tracking cookies.

Stored in your browser

  • lcs-updates-last-visit remembers when you last opened the Updates page, so the Updates badge can count what's new since then. It's kept in your browser's local storage only and is never sent to us. Clearing your browser's site data removes it.
  • lcs-extension-prompt-dismissed remembers that you dismissed the card suggesting our browser extension on the component pages, so it doesn't show again. It's kept in your browser's local storage only and is never sent to us. Clearing your browser's site data removes it.
  • pg-demo-theme remembers the light or dark choice you make in the Pulse Gantt live demo, if you make one and opened the demo on its own page. It's kept in your browser's local storage only and is never sent to us. Clearing your browser's site data removes it.

Why we use your information

  • To sign you in and keep your account secure.
  • To send the emails you ask for.
  • To keep the site running, fix problems and protect it from abuse.
  • To understand which topics people look for, from search terms that aren't linked to you.

We don't use your information for anything else without asking you first.

Who processes it for us

We use a few service providers to run the site. They process information only to provide their service to us:

  • Netlify hosts the website.
  • Supabase hosts the database that stores account information.
  • Resend delivers the emails you ask for.
  • Google confirms who you are, if you choose to sign in with Google.
  • Have I Been Pwned checks new passwords against passwords exposed in data breaches. It receives only the first 5 characters of a hash, never your password or anything that identifies you.

These providers may store or process information outside Canada, including in the United States. While it's there, it can be accessed by courts, law enforcement and national security authorities of that country under its laws.

We don't sell, rent or trade personal information. We would disclose it only if required by law.

How long we keep it

  • Account information is kept while your account exists.
  • Sign-in sessions expire after 30 days, sign-in links after 24 hours, and password links after 1 hour.
  • Counts of failed sign-in attempts, votes, notes and Power BI visual downloads per account are deleted a day after they were last used. Download totals per version say nothing about who downloaded.
  • Notes sent with "Something here changed?" are deleted once we've checked them. Vote answers are kept with the guide; they say nothing about who voted.
  • Learn progress is kept until you clear it, or until your account is deleted.
  • Ratings and "Worked in my app" are kept until you change them or take them back, or until your account is deleted.
  • Comments are kept until you delete them, or until your account is deleted. That includes comments we've removed and kept hidden.
  • Notifications are kept until the comment they're about is deleted, or until your account is deleted.
  • Records of your choices and of deletion requests are kept as proof of what you asked for, even after the rest of your account information is removed.
  • Logs are kept only as long as needed to run and protect the site.

Your choices and rights

You can ask to see the personal information we hold about you, to correct it, or to delete your account. Email contact@lowcodestacks.com from the address on your account, or use the deletion request on your account page. We'll reply within 30 days. If we need longer, we'll tell you why within those 30 days.

You can withdraw consent to optional emails at any time on your account page.

If you're not satisfied with how we handle a privacy concern, please tell us first. You can also complain to the Office of the Privacy Commissioner of Canada.

How we protect it

The site is served only over HTTPS. Sign-in links are single-use and expire. Passwords are stored only as salted hashes. After 5 wrong passwords in 15 minutes, sign-in with a password is paused for 15 minutes, and choosing a new password signs you out on every other device. Account pages are visible only to you, and administrative actions are limited to the site's operator.

Children

LowCodeStacks is written for people who build business software, and isn't directed at children.

Changes to this notice

When this notice changes, we'll update it here and change its effective date. If a change affects how we use information you've already given us, we'll ask you first.

This notice took effect on November 13, 2026.