RegOpsPro™
Controlled beta corporate review pack

Beta Security & Data Protection Pack

This page is intended for participants, Legal, Privacy, Data Protection and Information Security reviewers considering controlled-beta use of RegOpsPro Professional. It summarises the current implemented controls, data boundaries, accepted beta limitations and the points that remain subject to later commercial assurance.

Controlled-beta position. RegOpsPro Professional is an invitation-controlled working operational layer. It is not the customer's authorised QMS, system of record, CAPA system, EDMS or electronic-signature platform. Formal controlled approvals, statutory records and QMS closure remain in the organisation's authorised systems.

Beta operator / controller

During the controlled beta, the Data Controller for RegOpsPro's own website, account administration, security and direct beta administration is Nicholas Hughes. For organisation workspace content, the intended B2B model is that the participating organisation determines the purpose of its content and RegOpsPro provides the processing service, subject to the applicable beta/DPA terms.

Production environment

Professional uses a dedicated Production Supabase project hosted in the EU (Ireland region). Preview/Test and Production are separated. Organisation work is scoped by authenticated membership, row-level database controls and server-side checks.

Access controls

Professional is invitation-controlled during beta. Authentication uses secure session cookies, HTTPS, organisation membership and role checks. Cross-organisation read and mutation tests have been executed directly in Production and passed.

AI boundary

AI-assisted functions support retrieval, drafting, comparison and decision support. They do not make autonomous quality or regulatory approvals. Users must review outputs and should only submit organisation information where their organisation has authorised that use.

What data may be processed?

CategoryBeta position
Account/profile dataName/email, professional role, authentication and membership metadata needed to operate the account.
Organisation working contentSaved Work, working assessments, outputs, evidence references, findings, actions, decisions, review context and QMS handoff references voluntarily entered by authorised users.
Organisation documentsWhere a document-processing feature is used, uploaded material is treated as a working/reference copy. The approved master remains in the organisation's authorised system.
AI-assisted contextPrompt/context is processed only where the user invokes an AI-assisted feature. The AI boundary remains human-reviewed and source-grounded where designed.
Service/security metadataTechnical metadata required to operate, secure and troubleshoot the service.
Do not use the beta for: patient-identifiable data; special-category personal data; individual adverse-event or complaint case data; unnecessary personal data; passwords/secrets; highly sensitive commercial information; formal controlled QMS records; or other information your organisation has not authorised for use in an external beta service.

Current security controls

Tenant separation

  • Organisation-scoped data model.
  • Row-level security.
  • Server-side membership/role checks.
  • Direct cross-organisation negative testing passed.

Application / transport

  • HTTPS and HSTS.
  • HttpOnly secure session cookies.
  • nosniff, frame protection, referrer and permissions policies.
  • CSP currently operated in Report-Only mode pending later enforcement.

Environment / secrets

  • Dedicated Professional Production database.
  • Preview/Test separation.
  • Server-side deployment secrets rather than client-side exposure.
  • JWT verification on Production Edge Functions.

Analytics boundary

Analytics are designed to exclude workspace form content, prompts, generated responses, notes, company, product, batch, email and name fields. Hosting/security services may still process technical request metadata needed to operate the service.

Subprocessors

ProviderPurpose
SupabaseAuthentication, Production database and selected server-side/Edge Function services.
VercelApplication hosting and request delivery.
ResendTransactional email, including beta access/invitation-related messages.
OpenAIAI processing where a user invokes an AI-assisted feature.

Detailed contractual role/location/transfer safeguards depend on the configured service and applicable provider terms and are part of the later commercial legal-assurance work.

Retention, deletion and end of beta

RegOpsPro applies a data-minimisation principle. Beta retention periods are not yet the final commercial schedule. Active workspace information is retained while the beta/service requires it; security, support and backup information may have separate operational retention. Verified deletion/access requests can be raised at feedback@regopspro.com. Final category-specific retention periods will be fixed before wider paid launch.

Incident and security response

Suspected security or privacy incidents are to be triaged, contained, investigated and documented. RegOpsPro will assess affected data, organisations and legal notification obligations and communicate with affected beta participants where required. During beta, incidents should be reported to feedback@regopspro.com.

Known beta limitations

  • RegOpsPro does not currently claim ISO 27001 or SOC 2 certification.
  • Supabase leaked-password protection is not available on the current Free plan; this is a documented controlled-beta risk. It must be revisited before wider paid/commercial launch.
  • MFA is recommended during controlled beta and is intended to become mandatory before wider paid/commercial access unless equivalent protection is formally risk-accepted.
  • CSP is currently Report-Only rather than blocking.
  • Independent penetration testing and the final commercial legal/DPA/retention/transfer package remain pre-paid-launch assurance items.
  • The current beta should not be treated as a validated regulated system or authorised QMS.

Corporate review position

If your organisation requires Legal, Privacy, Data Protection, Procurement or Information Security review before using external software with company information, complete that review before entering organisational data. A beta participant may explore the platform using non-sensitive test/example information while that review is pending, subject to their organisation's policies.

Documents available for review

A beta DPA template and additional security-control detail can be provided on request. These materials remain subject to legal/commercial review before wider paid use.