Skip to main content

Security report for flowby.io

Roawr AB · Technology · Sweden

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

0–100, higher is better. How it is calculated

Flowby is a Swedish technology company founded in 2021 that offers a SaaS digital queue management solution enabling customers to join queues via their phones and receive notifications when it's their turn. The service targets businesses looking to enhance customer experience and increase sales without requiring physical hardware or installations. The website is built on a modern React and Gatsby framework with Chakra UI for styling, demonstrating good technical maturity and performance. Security posture is solid with HTTPS enforced and domain transfer protection, though DNSSEC is not enabled and security headers are not explicitly visible. Privacy compliance is limited due to the absence of a privacy policy and terms of service, though a cookie consent mechanism is implemented. Overall, the site is professional and trustworthy with room for improvement in privacy and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching flowby.io

This scan found 24 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
77
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
68
Average
68

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention flowby.io, from OffSeq Breach.

No leaked records found

Breach holds no records for flowby.io right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Flowby operates in the niche market of digital queue management, leveraging a SaaS business model. Its competitive advantage lies in ease of use, requiring no hardware installation and providing real-time queue tracking and notifications. The company serves businesses aiming to improve customer flow and sales, primarily in Sweden. The domain registration aligns with the company information, enhancing credibility. The website features client logos indicating partnerships or customers, suggesting some market traction. The absence of detailed business documents like privacy policies or terms may limit trust for some users. Analytics usage is minimal and privacy-conscious, using Plausible Analytics. The company appears small but focused on technology innovation in customer queue management.

Security posture

The website enforces HTTPS and has domain transfer protection, which are positive security indicators. However, DNSSEC is not enabled, which could expose the domain to DNS spoofing risks. Security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options are not explicitly detected, representing an area for improvement. No security or incident response policies are published, and no vulnerability disclosure or security.txt files are found. The cookie consent mechanism is implemented via Klaro, supporting GDPR compliance to some extent. Overall, the security posture is moderate but could be enhanced by adopting additional security headers, enabling DNSSEC, and publishing security policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and terms of service to enhance legal compliance and user trust.
  3. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Create and publish a security policy and incident response contact information to improve transparency and readiness.
  5. Consider adding a vulnerability disclosure policy and security.txt file to encourage responsible reporting and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Roawr AB
Description
Flowby provides a digital queuing system allowing customers to queue using their phone and get notified when it's their turn, eliminating the need for physical queue numbers or hardware installation.
Key services
Digital queue number issuance via QR code, Real-time queue position tracking, Customer notification when it's their turn
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, Chakra UI, Klaro (cookie consent), Plausible Analytics
Frameworks
React, Gatsby
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent banner implemented

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Plausible Analytics
Marketing tools
Plausible Analytics
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website uses modern React/Gatsby stack with Chakra UI for styling
  2. Cookie consent implemented via Klaro
  3. No visible privacy policy or terms of service pages found in HTML content
  4. Contact phone number clearly displayed with country code +46 (Sweden)
  5. No email addresses or social media links explicitly found in provided content
  6. No forms detected in the truncated HTML content
  7. External links primarily to admin portal and analytics provider plausible.io
  8. No security.txt or vulnerability disclosure information found
  9. No explicit security or incident response policies found
Technical notes

Notes

The website is built using modern web technologies including React, Gatsby, and Chakra UI, indicating a contemporary and maintainable codebase. It uses Plausible Analytics for privacy-focused tracking and Klaro for cookie consent management. Hosting appears to be managed via Gandi SAS, as indicated by the domain's nameservers. The site is fast and mobile-optimized with good SEO practices including meta tags and Open Graph data. No CMS is detected, suggesting a custom static or server-side rendered React site. The absence of DNSSEC and some security headers are technical gaps. Overall, the technical infrastructure is solid with opportunities for security enhancements and improved privacy documentation.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with flowby.io. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review flowby.io.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.