Privacy notice

Last updated 30 September 2026. Here's what we hold, how we use it and the choices you have.

Who. Diemus and L4TiTUDE Inc. run Industrial AI Voices jointly, with Lonnie Bowling and Laurent Garrigues as administrators. Industrial AI Voices is the project and website name, not a separate company. Contact [email protected].

What we hold. Your name and email from sign-in, your profile photo and any optional profile fields, messages and files you post, and notification preferences. If you add a passkey, we store its public key and a device name, never the private key. To keep you signed in securely, each sign-in session records the IP address and browser it came from; a session ends after 30 days without use. We also keep moderation records: reports members make and a log of administrator actions.

Why. To run the community you joined (contract); provide optional profile features and email notifications (your consent, changeable at any time); and handle moderation, security logs and backups (legitimate interests). We don't sell or rent your information or use the member directory as a sales prospect list.

Where. Community data is hosted on a server in Falkenstein, Germany, with Hetzner Online GmbH. Cloudflare provides the network service in front of it. All our emails — sign-in links, notification emails, digests and community emails — are sent through Resend; sign-in and notification emails never contain message content. These providers process information needed to deliver their services; German hosting does not mean every provider processes all information exclusively in Germany. The proofreading route is described below.

Profiles and images. Your name and profile photo are visible to signed-in members. Other profile fields follow your visibility choices. Uploaded pictures are re-encoded to remove embedded metadata such as GPS location and camera details. Pictures in member spaces are visible only to signed-in members; pictures in direct messages are visible only to the conversation's participants. Deleting a message deletes its images from the live service.

Direct messages. Private between the people in the conversation. The two administrators run the server and could technically read the database; they look at a direct message only when someone in it reports it. Messages are not end-to-end encrypted. Share only information you are authorized to disclose.

Push notifications. Optional, per device. We store the browser's push subscription, including an endpoint, keys and the browser type. Notifications say who and where, never what was written, and are encrypted to your device. Turn them off under Settings → Notifications or in your browser.

Proofreading. Available by default; switch it off in Settings. Nothing is sent unless you press Proofread, and we explain the process before the first use. That action sends one draft, with @mentions and code removed, through OpenRouter (a US gateway) to Mistral (an EU company, using EU hosting) for spelling and grammar suggestions. Remaining text can still contain identifying information. We require zero data retention and exclude providers that store the content or use it for training. We don't store a separate copy of the proofreading request; any message you subsequently post is stored normally.

Community emails. Members receive occasional updates and event invitations from our address through Resend. Each has a one-click unsubscribe link. You can also switch them off or on under Settings → Notifications. Community emails go only to members. Necessary sign-in, account and security messages are separate.

Invitations. If one of us invites you, we hold your name, email and a personal note we wrote, to send the invitation and see whether you joined. We rely on our legitimate interest in inviting relevant professional contacts. If you don't join, the invitation information is deleted after six months. If you ask us not to contact you, we keep only your email address so you aren't invited again.

Research. We conduct recurring interviews and surveys under a separate notice and agreement for each study. Joining or expressing interest isn't consent to participate. Community discussion may suggest questions to investigate, but we don't use your posts, messages or attendance as research data without explaining the use and asking separately. Recordings and full transcripts stay out of community spaces. Each study explains publication, confidentiality, retention and withdrawal.

How long. Account information stays until you delete the account. Profile and sign-in data are then removed immediately from the live service; messages you've posted remain, attributed to "Former member." Encrypted backups are kept for up to twelve months and used only for disaster recovery. Sign-in session records are deleted when the session ends. Moderation records — resolved reports and the log of administrator actions — are deleted after twelve months; a report still being handled is kept until it's resolved. Research records follow the study notice. Legal retention requirements may apply to specific records.

Your choices. Export your data under Settings → Account → Download export. You can delete your account there and edit your profile at any time. Write to us to request access, correction or deletion, object to a use, or withdraw consent for future processing. We may need to verify your identity. Additional rights depend on applicable law, including the right to complain to a data-protection regulator where available.

Cookies. One session cookie keeps you signed in. If you arrive through an invitation link, another remembers the invitation until you join. No tracking cookies or analytics.

Age. You must be 16 or older to join the community. Each research study states its own eligibility requirements.

Changes. We date every revision and announce material changes to how we handle your information in #general. Questions or concerns? Email [email protected].