Trust

Security & privacy

Security and privacy are built into how Revunor handles your data. Your account is isolated from other users, sensitive operations are handled server-side, and billing data is kept separate through controlled payment-provider connections. We take a deliberate, transparent approach to protecting the information you trust us with.

Protection built into Revunor

These protections are part of the way Revunor works today — not promises for a future release.

Browser-based analysis

Your free scans run in your browser, keeping the initial analysis experience local rather than requiring your business data to be permanently stored on our servers.

Your data stays separated

Revunor isolates account data at the individual-user level, helping prevent one customer's information from being exposed to another account.

Privacy-conscious by design

We collect and retain only what the product needs to operate, with account deletion and data-export controls built into the platform.

  • Account isolation

    Your account data is separated from other users.

  • Controlled billing access

    Stripe customer relationships are linked to the correct Revunor account and environment.

  • Account deletion

    Account and linked billing records can be deleted through the normal account controls.

  • Data export

    Users can request an export of their account data.

Where we're going next

Revunor is being built with security and privacy in mind from the beginning. As the platform expands, we're continuing to strengthen the controls needed for larger teams and more complex business-data workflows.

  • Organisation membership and role-based accessPlanned
  • Persistent storage and tenant isolation for uploaded business datasetsPlanned
  • Business-data integrations such as HubSpot and XeroPlanned
  • Multi-factor authenticationPlanned

Revunor is built with security and privacy in mind from the ground up. We use account-level data isolation, controlled server-side access, protected billing flows, account deletion and data export controls.

We describe the protections that are actually implemented rather than using compliance or security labels that require independent certification or validation.

How every figure is calculated

One formula, applied per finding, with no model in the loop:

affected records × average value × recovery assumption = estimated annual opportunity

Detection rules

  • Lead leakage — a lead older than 14 days with no activity recorded after creation.
  • Customer leakage — a customer with no recorded activity for 90 days or more.
  • Sales leakage — a quotation open for 30 days or more with no closing status.
  • Payment leakage — a payment marked failed, declined or past due.
  • Conversion leakage — an enquiry-to-quotation rate below 50%, measured against that generic reference point rather than a sector benchmark.

Recovery assumptions

  • lead leakage35%
  • customer leakage40%
  • quote leakage30%
  • payment leakage66%
  • conversion leakage25%

These are fixed, stated assumptions — not measurements of your business. Average values come from your own data whenever your file supplies them; where it does not, a documented fallback of €800 per customer per year is used and flagged in the finding.

Confidence levels

Confidence is derived from sample size and field completeness only. High requires at least 20 affected records with 80% of required fields populated; medium requires 8 records and 50%; anything smaller is reported as low and treated as directional.

Third parties involved today

  • Web hosting, authentication and database infrastructure for accounts and subscriptions.
  • Stripe for secure checkout, subscription management and billing history.
  • Revunor hosts its website fonts directly rather than relying on Google Fonts.
  • The browser-only free scan does not send your rows to Stripe, a model provider, a data warehouse or a CRM.

Still want to see it work?

Run the demo dataset — it is entirely synthetic, so nothing of yours is involved.

Start your free leak scan