RegOpsPro™

Privacy Policy

Data Controller during controlled beta: Nicholas Hughes.

This policy explains the information processed when you use RegOpsPro, including public tools, the signed-in Professional organisation workspace and Ask RegOps.

Last updated: 7 October 2026.

Information you provide

RegOpsPro may process account and profile information, organisation membership details, workspace content, evidence references, files you choose to upload, information submitted to AI-assisted features, and information you send by email. Only submit confidential, personal, patient, product, batch, supplier, customer, inspection or authority-sensitive information where your organisation has authorised that use.

Public tools and local browser storage

Some tools store drafts, progress and settings locally in your browser. Information held only in local browser storage is not sent to RegOpsPro merely because it is saved locally. Clearing browser storage, changing browser or changing device may remove locally stored content.

Signed-in Professional workspace

When you use the signed-in Professional workspace, selected information is stored server-side so it can persist between sessions and devices. This can include account/profile information, organisation membership, saved workspace content, working assessments, findings and actions, evidence references, QMS handoff references, version history and workspace activity. RegOpsPro is a working oversight environment; this information is not presented as the approved master or controlled record in your organisation’s authorised QMS.

Ask RegOps and organisation documents

Ask RegOps may use regulatory source material and, where enabled, organisation-provided working/reference documents to answer grounded questions. Uploaded organisation documents may be stored with document metadata and may be processed into extracted text or retrieval data so relevant passages can be found. Organisation-linked content is intended to remain scoped to the appropriate organisation workspace. The approved master remains in the organisation’s authorised QMS or document system.

AI-assisted processing

When you use an AI-assisted feature, the information you submit and relevant retrieved context may be sent to configured processing services to generate a response. AI output is support material and should be reviewed before use. RegOpsPro analytics are designed not to record the content of workspace forms, Ask RegOps questions or generated answers.

Data-protection roles

For website administration, account management, direct enquiries and service-security activity, RegOpsPro may determine why and how personal information is processed and therefore act as controller for that processing. For organisation workspace content entered by a customer organisation, the intended B2B model is generally that the organisation determines the purpose of the working content and RegOpsPro provides the processing service. During the controlled beta, Nicholas Hughes is the Data Controller for RegOpsPro. The precise controller/processor allocation and contracting entity for wider commercial use will be confirmed in the applicable customer agreement or data-processing terms.

Why information is processed

Information is processed to provide and secure the service, authenticate users, maintain organisation workspaces, persist saved work, answer grounded questions, support requested functionality, respond to enquiries, diagnose failures and understand service usage. Where data-protection law requires a lawful basis, the applicable basis will depend on the context and may include providing the requested service, legitimate interests in operating and securing the platform, legal obligations, or consent where required.

Access and organisation separation

Signed-in workspace information is access-controlled by user identity and organisation membership. RegOpsPro uses organisation-scoped application and database controls to separate organisation workspace information. Users remain responsible for controlling who is authorised to use their organisation workspace and for reporting suspected unauthorised access.

Service providers

RegOpsPro uses service providers for functions such as hosting, authentication, database/storage, email delivery, security, analytics and AI processing. Those providers may process information only as needed to deliver the relevant service and are subject to their own security and data-processing arrangements.

Analytics and technical data

RegOpsPro records limited technical and usage events such as page views, model and tool use, output actions and technical failures using an anonymous or pseudonymous session identifier. Analytics are designed not to record tool form entries, regulatory prompts, generated outputs, company, product or batch details, or email addresses. Browser Do Not Track settings are respected where implemented by the analytics layer. Hosting and security services may process technical request data such as browser, device, IP address and request information.

Cookies and sessions

RegOpsPro does not use advertising or cross-site tracking cookies. Essential authentication mechanisms are used to sign users in, maintain secure sessions and protect account access. These are necessary for the signed-in service to operate.

Retention and deletion

During beta, active account and organisation workspace information is retained to provide continuity unless deleted through available controls or on verified request, subject to limited security, operational and backup retention. A category-specific commercial retention schedule is being formalised before wider paid launch. Where removal controls are available, they remove the relevant active workspace copy; some information may remain temporarily in backups, logs or records retained for security, legal or operational reasons.

Your privacy requests

You can ask about personal information associated with your RegOpsPro account, or request access, correction or deletion where applicable, by contacting feedback@regopspro.com. Requests are handled subject to applicable law, identity verification and legitimate retention requirements. Where UK data-protection law applies, you also have the right to raise concerns with the Information Commissioner's Office.

Beta access requests

If you request Professional beta access through the website, RegOpsPro processes the name, email address, professional role, optional organisation name and high-level intended-use information you submit. The request is used only to review controlled-beta suitability and respond about access. Submitting the form does not create an account or grant access automatically. Do not include patient information, special-category personal data, confidential quality records or commercially sensitive detail in the request.

Email enquiries

If you email RegOpsPro, the message and contact details are used to respond and manage the enquiry. General feedback, account and privacy enquiries go to feedback@regopspro.com; consulting enquiries go to consulting@regopspro.com. Do not send confidential controlled records in an initial enquiry.

Related information

See Trust & Security, Subprocessors, Data protection & retention, the Terms & Conditions, Disclaimer and AI Use Boundary.