What we collect, what we store, and how to reach us.

What we collect

• Audit request form — name, business name, email, phone (optional), country, business type, the answers you give to the audit questions, and any free-text you write.
• Booking / request flow — name, email, optional phone, the type of inquiry, and any message you add.
• Public chat assistant (anonymous) — the text you type into the chat. Anonymous chat is not associated with a customer account and is not retained beyond your browser session.
• Customer account (optional) — when you create an IronWake account at /signup we collect your email, password (hashed by Supabase Auth, never stored in plain text on our side), and display name. We store your Supabase user id.
• Authenticated chat history — if you are signed in and chat through Ask IronWake, we persist your conversation in Supabase so it appears in /account. Each row is tied to your user id via row-level security; you can only see your own history.
• Linked audit/booking history — if you submit an audit or booking while signed in, the row is tagged with your user id so it appears in /account without re-entering your email.
• Server logs — request path, status code, IP, and user agent. Kept by Netlify for a short rolling window for security and abuse response.

We do not run third-party advertising trackers. We do not sell or rent your data.

Where it is stored

• Audit, booking, customer profile, and chat-handoff records are stored in our Supabase Postgres (Frankfurt region). Only IronWake operators can read them.
• Customer accounts are managed by Supabase Auth — passwords are hashed, never visible to IronWake. Row-level security restricts each customer to their own profile, chat history, and linked inquiries.
• Anonymous chat messages are not persisted; they live only inside your browser session and the rate-limiter window.
• Authenticated chat history is stored in the same Supabase database (tables chat_sessions and chat_messages) and scoped to your account.
• Emails sent to ironwake.dev@gmail.com are stored in Google's Gmail on the ironwakee account.
• Static site assets are served by Netlify from their global CDN. Netlify retains short-lived access logs for the deployed site.

What we do with it

• Run an automated triage over audit and booking submissions so the operator can see priority and next action.
• Reply to you. The current reply path is the operator's email; transactional SMS or WhatsApp notifications are not currently wired up.
• Improve the chat assistant's quality. Failures and crash traces are logged without your personal data.
• Allow you to review and continue your previous Ask IronWake conversations, and to keep your audit/booking history in one place.

Retention

• Audit and booking records are kept while the inquiry is active and for up to 24 months afterwards, then deleted.
• Customer accounts remain until you delete them. You can request deletion at any time by writing to the address below.
• Authenticated chat history is kept with your account and is deleted with the account.
• Anonymous chat sessions are not retained beyond the browser session.
• Server logs are kept by Netlify on their standard rolling window for the deployed site.

Your rights and how to reach us

You can ask for a copy of your record, ask for it to be corrected, or ask for it to be deleted. Write to ironwake.dev@gmail.com and include the email you submitted so we can find the row.

If you created an IronWake account, you can also use the in-product controls in /account to update your display name or sign out. Password changes are handled by Supabase Auth.

This page is operated by the same person who runs the demonstrations on this site. There is no separate legal entity registered behind it yet — that will be added before the first paying client is onboarded.