Privacy Policy
Short version: Clause5 uses data to operate welding tools, protect the service, send requested messages, maintain compliance evidence, and improve product reliability. We do not sell personal data.
This policy covers account and contact data, welder-linked PII, vision uploads, analytics and session telemetry, first-party /api/events telemetry, lawful basis, retention period, access, correct, erase, and port rights, anonymization limits, Privacy choices, processor categories, and change procedure.
1. Data categories
- account and contact data, including email address, organization details, waitlist details, invitation state, billing state, and support messages.
- welder-linked PII, including welder name, stamp ID, email, phone, certification number, qualification details, expiry or scope, and linkable pseudonymous references when a welding workflow needs them.
- vision uploads, including Uploaded drawings, images, and related review context submitted for analysis.
- Product inputs and outputs, including Flux questions, calculator context, project metadata, WPS or WPQ workflow state, and generated compliance-support output.
- analytics and session telemetry, including page path, rough interaction events, browser metadata, opt-out state, first-party /api/events telemetry, and session usability analytics that may replay clicks, scrolls, and page interactions.
- Security and operations data, including abuse-prevention signals, rate-limit records, error logs, and consent-safe debug records.
2. Lawful basis
We process data to provide requested services, take pre-contract steps, perform contracts with customers, meet legal or compliance obligations, protect the service, and improve product reliability where analytics opt-out controls or a legitimate operational basis applies.
3. Welder consent and employer attestation
welder-linked PII requires a consent decision before it is used in qualification workflows. Direct welder consent is preferred where a deliverable welder contact exists. Employer attestation is provisional, reason-coded, time-limited, and not treated as permanent direct welder consent.
4. Analytics, cookies, and first-party events
Analytics is on by default so we can understand page usability, session quality, product funnels, and traffic sources. Turning analytics off does not block calculators, Flux, SaveGate, share links, authentication, or app pages. First-party /api/events telemetry, session usability tools, and marketing/product analytics stop after you opt out, except for essential security or operational telemetry with no marketing payload.
5. Retention period
Contact and account records are kept while the relationship or requested communication remains active. Consent records, non-PII compliance trace evidence, and security logs may be kept longer where needed to prove workflow integrity, prevent abuse, or preserve lawful compliance history. Raw uploads, prompts, and telemetry are retained only as long as needed for product, security, support, or legal purposes.
6. Your rights
You can ask to access, correct, erase, and port your personal data. You can also object, restrict processing, withdraw consent, or ask for a copy of consent evidence. Email privacy requests to flux@clause5.io.
7. Deletion and anonymization limits
When consent is withdrawn, Clause5 redacts or anonymizes PII that is no longer lawful to retain, severs or rotates linkable references where possible, and preserves non-PII qualification and compliance audit history. Some audit evidence cannot be deleted without breaking compliance trace integrity, but it must not contain raw welder PII.
8. Processor categories
We use category-based service providers: edge infrastructure provider, database provider, email delivery provider, payment processor, AI processing provider, security provider, and analytics or consent-management provider. Exact processor details are maintained in an internal registry with owner, update cadence, and change procedure.
9. Updates
This policy is reviewed when processors, data categories, purposes, retention periods, or consent mechanics change. The current change procedure updates the internal processor registry, shared policy metadata, public policy copy, and automated privacy tests before deployment.
10. Contact
Privacy questions, deletion requests, and DPO-style requests can be sent to flux@clause5.io. Security reports can be sent to security@clause5.io.