Privacy
Bluewizarding should reduce what people have to track, not make their data harder to understand. This policy states what may be collected, how it is used, and what stays private.
This policy covers Bluewizarding products, consulting, research, supplier routing, practical AI systems, account features, and support requests.
Some clauses apply only when the related feature is active. Public supplier pages use reviewed, derived fields rather than raw private-source material.
When an account exists, Bluewizarding may collect name, email address, profile image, sign-in method, account preferences, and saved work. OAuth sign-in can provide basic profile details, but Bluewizarding does not receive the user's OAuth password.
The client portal is the account entry point. Account data, saved work, billing records, and deletion controls belong behind that boundary.
If credit packs, consulting retainers, routed handoffs, or other paid services are enabled, payment processing should happen through the approved payment provider. Bluewizarding should not store full card numbers, CVV values, or complete card details on its own servers.
Transaction IDs, payment amount, last-four card references, invoices, receipts, and accounting records may be retained where needed for billing, support, tax, and dispute handling.
The site may collect intake answers, consulting notes, research requests, simulation notes, routing clicks, deliverables generated, technical logs, theme preference, consent records, and support messages.
For supplier routing, the system may store normalized supplier categories, fit signals, review states, and buyer problem context. Raw source workbooks, contacts, commission terms, private notes, and supplier collateral do not belong in public pages or git.
Data may be used to recommend suppliers, shape research, draft practical next steps, save a user's context, respond to support, maintain security, remember interface preferences, and reconcile routed supplier handoffs when that mechanism is approved.
Bluewizarding does not sell personal information. User data is not used to train AI models unless a separate written agreement says otherwise.
Bluewizarding may use service providers for authentication, payment processing, transactional email, hosting, CDN, bot protection, web analytics, backend storage, session management, rate limiting, error monitoring, and model generation.
Provider categories may include a payment processor, OAuth providers, email delivery, hosting/CDN, database/storage services, error monitoring, and the configured AI model provider used for generation or question refinement.
Strictly necessary cookies may keep users signed in, remember theme or consent preference, protect forms, and support rate limits. Analytics stays privacy-minded and never becomes an advertising pixel or cross-site tracking.
First-party behavior analytics, when enabled, record anonymous interaction patterns (where people click, how far they scroll, and where a form is left unfinished) to improve these pages. This is off by default and runs only after an explicit consent choice. It never records keystrokes, form field values, or a video of a session, and it honors Do Not Track and Global Privacy Control browser signals. All of it stays first-party on Bluewizarding infrastructure and is never sold or shared for advertising.
To opt out, decline the analytics consent notice, clear the consent preference, or send a Do Not Track or Global Privacy Control signal from the browser. If analytics, bot protection, or consent tooling changes, this policy is updated so users can understand the active data flow.
Account information and deliverables may be retained while an account is active. Payment and accounting records may be retained where law, tax, fraud, or dispute obligations require it.
Use the public contact page with the address or account you used to ask for access, correction, export, deletion, or non-essential communication changes.
Bluewizarding should use HTTPS in transit, access controls, scoped credentials, reviewed admin flows, and appropriate storage protections. No method is perfect, so sensitive source material stays private by design rather than relying on public-page discipline alone.
The review workflow stores private-source flags instead of private values wherever possible.
Bluewizarding is a business tool for professionals and is not intended for children under 13. If a child has provided personal information, contact Bluewizarding so it can be removed.
Users may have privacy rights depending on location, including access, correction, deletion, export, and opt-out rights. Bluewizarding's stated posture is not to sell personal information.
A supplier handoff may share the information needed to connect the buyer with the supplier. Commercial relationship disclosure must be shown wherever paid routing is active.
Public supplier claims use reviewed public profile language. Private contacts, commission terms, and collateral stay internal unless explicit rights and disclosure rules allow use.
This policy may be updated when material data flows change. A material update may also require account notice, email notice, or a visible platform notice depending on the change.
For privacy questions, corrections, deletion requests, or supplier-data concerns, use the public contact page.
Use the public business contact for privacy, correction, deletion, and account questions.
Open the contact page