Security

Security overview

This page describes the operational security principles Btor Oy applies around Arinda and how to contact us about security-related questions.

Approach

Operational security, stated plainly

We do not treat security as a marketing slogan. For Arinda, the most important public signals are clear administration, controlled access, visible support paths, and defined processes for privacy-related requests.

This page explains our security operating model at a practical level. It helps buyers and partners evaluate our approach while keeping sensitive implementation details out of public documentation.

If you need more detail for an evaluation process, contact us directly.

Operational controls

What security looks like in the product context

The relevant control areas for Arinda include administration, member access handling, operational visibility, and documented response paths.

Administrative control

  • Key operational settings are managed through the admin portal.
  • Membership configuration, benefit rules, and access-related settings are centrally controlled.
  • Operational changes can be aligned with the venue's membership structure.

Access-related features

  • QR-based visit registration and mobile key access are managed as explicit product features.
  • Access behavior can be linked to membership status and configuration.
  • This helps venues keep member-facing access rules tied to defined administration.

Request and response paths

  • Privacy and deletion contact paths are publicly available on the site.
  • General security questions can be sent directly to Btor Oy.
  • Additional evaluation questions can be handled through direct contact during sales or customer discussions.