Let’s talk

Data, access, and control.

Before a system is built, four things need to be clear for your organization. This page explains them simply.

Four questions we ask at the start

  1. What data is used?
  2. Who may access it?
  3. Where does the system run?
  4. Who carries the management forward?
Infographic of where your data goes: your servers, a private cloud, or outside services only with written permission
Infographic of where your data goes: your servers, a private cloud, or outside services only with written permission
Text summary of the infographic

Your documents and data only go where you choose. First, you choose which documents may be used. Option A: the system runs on servers your organization owns, and access stays with the people you appoint. Option B: the system runs in a private cloud you select, again with access held by the people you appoint. Option C: outside services are used only with your written permission; without it, no outside service is connected. Location and access are agreed before we build and written down for each project.

Four areas of control

Data

Production data, backups, and activity logs stay in the location you decide: your own server or a private cloud. The location is written into the scope document.

Access

Accounts, keys, and activity logs are in your organization’s name. We work with the access you give us; it is logged and can be revoked at any time. You appoint one person responsible for access.

Technology

Systems use open standards. Code, data structures, and documentation are handed over, and data can be exported in common formats, so the system is portable by design and can be moved or continued by others without depending on a single vendor, including us.

Operations

Day-to-day management is set out per project: who maintains the system, who decides on changes, and how handover happens. For AI assistants, if an outside component is needed, we name it at the start along with the alternatives.

Who holds what?

How roles are divided between your organization and us is set out per project.

Infographic of who holds what: your organization and sixseven.camp for accounts and access, data, code and documentation, and day-to-day operations
Infographic of who holds what: your organization and sixseven.camp for accounts and access, data, code and documentation, and day-to-day operations
Text summary of the infographic

This table compares the roles of your organization and sixseven.camp, whose access can be revoked. Accounts and access: accounts are in your organization’s name and you appoint who is responsible for access; we work with the access you grant, which is logged and revocable. Data: stored where you decide; we use it within the agreed scope. Code and documentation: code, data structure, and documentation are handed over to you; we prepare them and hand them over. Day-to-day operations: you decide on changes; we maintain the system only under an agreement. Everything is set out for each project.

The two contexts we see most often

For ministries and agencies

The focus is a system your institution can manage and stand behind: data classification, placement according to your agency’s rules, documentation and handover, and the ability to carry management forward without depending on a single vendor. This approach is in line with efforts to strengthen national digital self-reliance.

For companies

The focus is keeping business documents and customer data confidential: who may ask the AI what, which outside services may connect, the freedom to switch providers, and no documents sent outside without written permission.

Limits

  • There is no guarantee of zero risk.
  • We do not issue certifications or compliance statements on behalf of clients.
  • We design systems so your organization can meet the data protection obligations that apply to you. The specific arrangements, such as location, encryption, retention, and access rights, are written down per project.

The approach on this page applies to the systems we build for clients. The public sixseven.camp website uses third-party hosting, and its privacy policy is described separately in the Privacy policy.

Ask about your needs

Start with a short question or a rough idea of the work you want to improve. No technical specification needed.

Email: info@sixseven.camp