Skip to content
Menu

Trust throughout our work together.

When a solution becomes part of your working day, you should know how your information is handled, who looks after operations and where to get help.

At Apalos, privacy, security and operations are part of development itself. Our model is built on established principles: privacy by design, access according to need, clear responsibilities and systematic maintenance. We turn those principles into practical choices in the solution and the routines around it.

Privacy starts before we build.

We start by understanding what information you need, what it will be used for and who should have access. We also clarify how information should be stored, deleted and retrieved when needed.

This provides the basis for access control, traceability and privacy functions that fit your needs. We help document the processing and set up functions that support access requests, consent and deletion where relevant.

You know your organisation and the purpose of the processing. We contribute technical expertise, practical tools and help with making the ongoing work part of your everyday routines.

A shared foundation that keeps developing.

Our solutions build on shared functions that we use and maintain ourselves. Sign-in, permissions, data storage and traceability therefore have a carefully considered place in each delivery.

We choose established technologies and favour solutions that are understandable, robust and maintainable over time. Revenue from all our customers goes back into developing and running the foundation. Improvements can then benefit every solution, while the solution is adapted to you.

It also gives us room to offer bespoke software at a competitive price.

Professional operations are part of the offer.

A solution needs care throughout its lifetime. With an operations agreement from Apalos, you have someone who knows the solution and takes care of the agreed operational work.

Periodic software updates are included, also for bespoke solutions. We look after monitoring, backups and maintenance within the agreement. We also practise restoring data, so the backups form part of practical recovery preparations.

You should know who to contact, how to get help and what the monthly fee covers. New features and other further development are agreed with you as your needs change.

Read about operations and support

Clear responsibilities and openness about data.

You should be able to understand where information is processed, which suppliers are involved and what their services are used for. We prioritise Norwegian and European infrastructure and make those dependencies visible.

Before delivery, we agree who is responsible for what and which requirements the solution must meet. Documentation, agreements and the technical setup should describe the same reality. When needs or circumstances change, our ongoing work must change with them.

We use experience to improve.

If something does not work as it should, we follow up both the incident and its cause. We document what we have learnt and assess what needs to change in the solution or our routines.

In this way, experience from development, testing and operations informs the work ahead. It is this continuing care that we want you to be able to trust.

More about data processing and transparency.

Suppliers and data storage

The data in your solution — what you work with every day — is stored on hardware we run ourselves in the Nordic region. The same applies to your enquiries and our notes about you: they are in our own systems, not in an American cloud service.

We prefer European suppliers. Some services use American infrastructure. That is why we describe both who the supplier is and what the service does.

The overview below describes suppliers and data processing as reviewed on 26 August 2026:

Hetzner — Finland

Copies of backups, and the server that counts visits to this website.

Scaleway — France

Sending email.

Domeneshop — Norway

Domain and email. All email to @apalos.no is delivered to mailboxes at Domeneshop.

PowerOffice — Norway, using American infrastructure

Our accounting system, for customer records, orders and invoices. This includes company names, organisation numbers and purchase information. PowerOffice is a Norwegian company that uses Microsoft Azure.

The list is short because we run most things ourselves — sign-in, CRM, forms, statistics and monitoring run on our own machines.

Privacy on this website

Visits are counted with Umami, which we host ourselves in Helsinki. The statistics use no tracking cookies. The order form sets one technical cookie to protect submissions against misuse. It lasts for the browser session.

If you choose a language, we remember your choice in a language cookie for up to one year.

We count page views, where visits came from, whether buttons are used and how far people read the two long pages. Everything is counted in aggregate, never per person: your IP address is not stored, and the only identifier is a hash that changes every night. This means we cannot tell that you were here yesterday. We have decided that the figures will be deleted after fourteen months.

You are welcome to check this in your browser's developer tools.

Use of artificial intelligence

We use AI tools for tasks such as coding, drafting and reviewing our work. The models come from American providers. Responsibility for what we deliver remains with us.

Customer data does not go there. The tools are used on code, plans and our own documents — not on the content of your solution. If a customer wants AI as part of their product in future, that requires a separate agreement specifying where the model runs.

Documentation and certification

Apalos has no ISO 27001 or SOC 2 certification. Our work is based on the routines above and documentation from our own operations.

If you have requirements for data storage, documentation or ongoing support, we go through them together before agreeing a delivery.

Let us go through your requirements.

Tell us what the solution will be used for and what you need from privacy, security and operations. Together, we can agree how delivery and ongoing support should be arranged.