Privacy Policy

Who this covers

This policy is written by SodaStack LLC ("SodaStack", "we") and covers sodastack.co, our Self Checkout, our contact and intake forms, and the information we hold while we build and run a website for you. It does not cover the websites we build for clients once they are live; those belong to the client and carry the client's own policy.

What we collect, and where it comes from

Everything we hold, you gave us or a service acting for you generated:

• Contact and intake forms: your name, business name, email, phone if you give it, and what you wrote in the form.
• Self Checkout: your business name, your name, your email, your web address if you have one, your domain status, the theme and plan you chose, the six brand colors you set, and the time you accepted our terms.
• Payment: handled entirely by Stripe. We receive your name, email, the last four digits of the card, the amount and the subscription status. We never see or store a full card number.
• Your website project: the logo, images, copy and business facts you supply so we can build the site, plus the credentials of the WordPress site we build for you.
• Site analytics on sodastack.co: Google Analytics records pages viewed, approximate location and device type. It does not identify you to us by name.

What we use it for

Only to do the work and run the business:

• To answer your enquiry and quote the work.
• To open, build, review and launch your project, and to bill for it.
• To send the emails the work requires: receipts, your content link, review links, renewal notices and service notices.
• To keep records the law requires of us, including tax and accounting records.
• To understand how sodastack.co is used, in aggregate.

Who else touches it

We do not sell your information, rent it, or share it for anyone else's advertising. We use these services to run ours, and each sees only what its job needs:

• Stripe, for payments, subscriptions and receipts.
• Supabase, the database and file storage behind our project dashboard, where your project, brand and content live while we work.
• Netlify, which hosts sodastack.co and receives our contact and intake form submissions.
• Google Analytics, for aggregate traffic on sodastack.co.
• Hostinger, or the host you choose, for the WordPress site we build for you.
• Email providers, to send the messages above.
• Authorities, if the law requires it and only to the extent it requires.

How long we keep it

• A Self Checkout you start but do not pay for is deleted within 14 days.
• Project information is kept for as long as we are building or running your site, plus a short period afterwards to close out the work.
• Payment and tax records are kept for seven years, as accounting rules require.
• Contact form messages are kept while the conversation is live and then removed on request or in our periodic clean-up.

Your choices and rights

Email us and we will do these within 30 days, whatever state you live in:

• Tell you what we hold about you.
• Correct anything that is wrong.
• Delete it, except records we are required to keep, such as invoices.
• Stop non-essential emails. Service notices about a paid subscription continue while it runs.
• Opt out of analytics by blocking cookies in your browser; the site works without them.

Cookies

sodastack.co sets cookies only for Google Analytics. Stripe sets its own cookies on its checkout page for fraud prevention. Our project dashboard sets a login cookie for our own team. Nothing else.

Security

Payment details never pass through our systems. Project data is stored with access limited to the people doing the work, and client website credentials are held only for as long as we need them to build and maintain the site. No system is perfectly secure; if we learn of a breach affecting your information we will tell you without undue delay.

Children

Our services are for businesses and organizations and are not directed at anyone under 18. We do not knowingly collect information from children.

Changes

When this policy changes we update the date at the top of this page. If a change affects how we use information we already hold, we will email the people it affects before it takes effect.