Loading privacy policy
Privacy Policy
Clear rules for product, workflow, and operational data.
This policy explains what QFlow Studio collects, why we use it, who may receive it, how long we keep it, and how privacy requests are handled.
We collect what the product needs
Account access, workspace activity, workflow records, learning progress, demo requests, and support context.
Provider credentials stay bounded
Provider tokens and secrets are treated as private operations data and are not placed in public review packets.
You can request access or deletion
Depending on your location and workspace role, you may ask to access, correct, export, delete, or restrict certain data.
We do not sell personal information
QFlow is not designed to sell personal information or share it for cross-context behavioral advertising.
Data we process
Data categories are tied to product surfaces.
QFlow handles different records for sign-in, workflow operations, learning, demo requests, hiring, and security operations.
CategoryExamplesPurposeRecipients
Account and access
Name, email, authentication state, sessions, workspace membership, admin role.
Create accounts, authenticate users, enforce permissions, and protect the service.
Identity, hosting, security, and support providers that help operate the service.
Workflow and run content
Briefs, circuits, generated code, versions, provider route choices, run configuration, artifacts.
Operate the workflow studio, preserve evidence, support exports, and maintain team continuity.
Workspace members you authorize, infrastructure providers, and connected quantum providers when you run jobs.
Learning and certificates
Lesson progress, attempts, badges, certificates, cohort activity, source interactions.
Track personal learning progress, support academy programs, and issue completion evidence.
Workspace or cohort administrators where applicable.
Demo, support, and communications
Demo form details, support messages, notification preferences, delivery status, contact history.
Respond to requests, route support, send requested updates, and prevent abuse.
Email, support, CRM, and operations providers used to handle the request.
Hiring data
Resume PDFs, application notes, portfolio links, role selection, review status.
Evaluate applications and manage candidate communications.
Authorized hiring reviewers and infrastructure providers that store applicant files.
Operational and security data
IP address, user agent, logs, health checks, audit events, rate-limit and abuse signals.
Maintain reliability, investigate incidents, secure accounts, and comply with legal obligations.
Security, hosting, observability, and incident-response providers.
Your choices and rights
Rights depend on your location, role, and the workspace record.
We verify requests before acting. Some records may be retained for security, legal, billing, enterprise, or abuse-prevention reasons.
Access
Ask for a copy or explanation of personal data associated with your account or request.
Correction
Ask us to correct inaccurate account, demo, hiring, or support information.
Deletion
Request deletion where retention, security, legal, or enterprise obligations do not require us to keep it.
Portability
Request export paths for account, workflow, or learning records where supported.
Restriction
Ask us to limit certain processing or object where local law gives that right.
Appeal or complaint
If a request is denied, contact privacy with context so it can be reviewed.
Retention
We keep data for the period needed to provide the service, maintain records, resolve disputes, comply with law, and support enterprise retention commitments. Workspace owners may have separate retention obligations.
International transfers
QFlow may process data using infrastructure or subprocessors in different regions. Where required, transfer safeguards or enterprise terms may apply.
Automated decisions
The product may generate suggestions, code, routing context, or analysis, but it is not intended to make legally significant automated decisions about people.
Children
QFlow is built for professional, enterprise, research, and education programs. It is not directed to children under 13.
Security
We use role boundaries, credential separation, access controls, logging, and operational safeguards to protect data. No online service can guarantee perfect security.
Changes
We may update this policy as the product, law, or operational practices change. Material updates will be posted with a new effective date.
Operating principles
Privacy is part of the workflow boundary.
Public pages, reviewer packets, certificates, and marketing routes should not expose provider secrets, private notes, billing data, or unrelated workspace records.
Review security postureContact paths
Send requests to the channel that owns the record.
Include the account email, workspace context, request type, and any deadline so the team can route the request correctly.
Security reports
security@qflow.studioResponsible disclosure, vulnerability reports, or security questionnaires.