Privacy Policy

1. Scope

This policy applies to the public website at riskrover.io, the authenticated RiskRover application at app.riskrover.io, public tools and resources, website forms, RiskRover Clinics and related online services.

The customer organisation remains responsible for deciding what project information its users enter into RiskRover and for ensuring that it has a lawful basis for that information.

2. Information we process

The information depends on how RiskRover is used. It may include:

• Account information such as name, email address, organisation, role, authentication settings and profile preferences.
• Application and project data that customers and users choose to store, including plans, stakeholders, discussions, execution information and integration settings.
• Customer, subscription and billing details. Stripe handles payment-card processing; RiskRover stores the customer and subscription references needed to administer access.
• Information entered in contact, resource, free-tool, Clinic-interest and Clinic-registration forms, together with the purpose and version of any consent provided.
• Public website measurement data from eligible marketing pages, including page URL and title, referrer, browser and device details, approximate location, session statistics and Google Analytics cookie identifiers.
• Technical and security information in server logs and error events, which may include request metadata, IP address, browser or device information and identifiers needed to investigate an incident.

3. Why we use information

Scroll sideways to read all columns. The first column stays visible.

4. Forms, resources and Clinics

Submitting a contact, product-question, resource or free-tool form does not by itself subscribe a person to general marketing. An optional, unchecked marketing field is shown where marketing permission can be requested. RiskRover records the choice, time, source form and wording version.

A Clinic-interest form records the selected topic and a separate request to be contacted when a relevant Clinic is scheduled. It may be used for that relevant notification or follow-up only; it is not general marketing consent.

Website submissions are stored locally in encrypted database fields. Submitting a request does not add that person to a marketing list. Any future marketing-list or automation activity requires explicit marketing consent and remains subject to suppression and withdrawal controls.

5. Service emails and marketing

RiskRover sends service messages needed for the requested service, such as account verification, invitations, password resets, security notices, billing information, support replies, requested resource delivery, discussion notifications and a requested Clinic notification. These are not newsletter marketing.

Product news and marketing emails are optional and are sent only when the relevant consent has been given. Consent can be withdrawn at any time by using the unsubscribe method in the message or by contacting privacy@riskrover.io. Withdrawal does not affect processing that was lawful before it was withdrawn.

Service messages are sent through mail infrastructure contracted by Be-Sure. Current provider, processing and transfer details are available from privacy@riskrover.io and, where applicable, under the customer's data processing agreement.

6. Website and application analytics

With your permission, RiskRover uses Google Analytics 4 (measurement ID G-R81Q74E58B) on public marketing content pages to measure page views, sessions, approximate location and browser or device information. The standard tag also sends page metadata such as the page URL, title and referrer. Google states that it uses the IP address at collection time to derive approximate location and does not log or store the raw IP address in Google Analytics.

The Google Analytics tag is not loaded in the authenticated application, Test Case Calculator, Checkout, Checkout status or completion, or thank-you flows. RiskRover does not define custom analytics events or intentionally send form values, calculator inputs, checkout identifiers or customer project data to Google Analytics. Google Analytics may collect enhanced-measurement events when that provider-side property setting is enabled.

Google Analytics remains unloaded until you choose Allow analytics. Decline analytics keeps it off. Use Privacy choices in the footer to change or withdraw your choice at any time. Withdrawal disables measurement and clears the website’s Analytics cookies. Your choice is remembered on this browser for 180 days when storage is available. Advertising pixels and session replay are not installed.

Google Analytics data collection Google Privacy Policy Google Analytics opt-out add-on

7. Cookies and browser storage

RiskRover uses first-party cookies and browser storage for sessions, security, language, interface preferences and the public Test Case Calculator. After you allow analytics, Google Analytics sets first-party _ga and _ga_R81Q74E58B cookies on eligible public marketing content pages to distinguish visitors and persist session state.

YouTube and Vimeo players are not loaded automatically. A provider connection is made only after the visitor selects Load video on the relevant page. That provider may then process technical request data or use its own cookies or storage under its own policy.

Read the Cookie Policy

8. Technical and error logging

RiskRover keeps technical logs to operate the service, troubleshoot errors, investigate reliability or security issues and prevent abuse. Technical logs are retained for a maximum of 6 months and are not used to build behavioural or marketing profiles of application users.

Sentry may receive server-side exception and performance events when it is enabled. Default personal-data collection is disabled in configuration, although an error event can still contain limited request or account context needed to investigate the issue.

9. Service providers and customer integrations

The providers used depend on the feature and deployment configuration:

• Combell hosts RiskRover's primary application infrastructure and application data in Belgium.
• Stripe processes subscriptions and payments. RiskRover exchanges customer and subscription data needed to administer billing and does not store full payment-card details.
• Billit receives customer identity, address, tax treatment and statutory invoice data originating in Stripe so it can support invoice administration and deliver structured or electronic invoices, including Peppol or another supported format.
• Sentry may process technical exception and performance information when operational monitoring is enabled.
• Google Analytics receives standard public-page measurement data and first-party analytics identifiers on eligible marketing content pages.
• YouTube or Vimeo receives a request only when a visitor explicitly loads an externally hosted video.
• Customer-selected integrations such as Azure DevOps, Jira/Xray, Jira/Zephyr Scale, TestRail or Qase receive credentials and the project information selected for the requested import or synchronisation.
• When a customer uses RiskRover MCP, its chosen AI client and provider may receive selected RiskRover project data and workspace excerpts under that client's permissions, terms and data controls. The local MCP server does not send repository content to RiskRover.

10. Location and international transfers

RiskRover's primary application infrastructure and application data are hosted with Combell in Belgium. This does not mean that every provider processes all data only in Belgium.

Payment, invoicing, analytics, monitoring, external-media and customer-selected integration providers may process information in other countries. Be-Sure assesses the required contractual and legal safeguards for the providers it activates. Current provider locations and safeguards are available from privacy@riskrover.io and, where applicable, under the customer's data processing agreement.

11. Retention and deletion

Application and project data remains available while the relevant customer account or workspace is active. When a customer asks Be-Sure to close the relevant account or workspace, associated data is removed from active systems without undue delay, subject to access checks and legal exceptions.

Technical logs are retained for no more than 6 months. Contact and resource requests are retained only while reasonably needed to handle and document the request. Clinic-interest information is retained only while reasonably needed for the Clinic topic requested. Marketing contact data is kept while needed for the consented purpose and is suppressed or removed when consent is withdrawn, subject to minimal suppression evidence needed to honour the choice. Google Analytics cookie lifetimes are listed in the Cookie Policy; event and user-level retention follows the configured Google Analytics property settings.

Certain invoice, payment and accounting records may be retained for the period required by applicable Belgian accounting and tax law, even after an account is closed. For the current backup retention and deletion schedule, contact privacy@riskrover.io.

12. Be-Sure as controller and processor

Be-Sure acts as controller for information used for its own account administration, billing, security, website, forms and customer communication.

For personal data that a customer chooses to store in RiskRover project content, Be-Sure may act as processor on behalf of that customer. The customer remains responsible for its instructions and lawful use of that project data.

13. Calculations, AI and automated decisions

RiskRover uses deterministic calculations to support product-risk analysis, strategy, estimation and planning. Users and Test Managers retain judgement and make the decisions. RiskRover does not make legally significant automated decisions about individuals.

Be-Sure and RiskRover do not train their own AI models on customer data. When a customer uses RiskRover MCP, the local MCP server returns selected RiskRover project data to the customer's chosen AI client. The MCP server does not read repository files or run commands, and repository content is not sent to RiskRover. The AI client may send RiskRover data and workspace excerpts to the customer-selected AI provider under that provider's terms, permissions and data controls.

14. Security

We use technical and organisational measures designed to protect the information processed through RiskRover. Verified examples include HTTPS requirements for production, password hashing, CSRF and session protections, optional two-factor authentication, role-based access controls, encrypted integration credentials and encrypted public-form fields, bounded API access and operational monitoring. No internet service can guarantee absolute security.

15. Your rights

Depending on the circumstances and applicable law, a person may have rights to access, correct or delete personal data, restrict or object to processing, receive portable data and withdraw consent. A request can be sent to privacy@riskrover.io. We may need to verify the requester's identity and authority before acting.

A person may also lodge a complaint with the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorite de protection des donnees) or another competent supervisory authority.

Contact RiskRover privacy Belgian Data Protection Authority: actions and complaints

16. Changes to this policy

We may update this policy when RiskRover, its providers or legal requirements change. The current version and update date are published on this page. Material changes that affect an active service may also be communicated through an appropriate service channel.