Apps Client Pricing Log in Early access
Apps Client Pricing Log in Early access

Privacy policy

Nordkastell gives each customer a server of their own. Your workspace data lives on that server, and we only hold what we need to sell you the service and keep it running.

Last updated
4 October 2026
Operated by
H5 Förnyelsebyrå AB, organisation number 556970-4371, VAT number SE556970437101, Skaraborgsvägen 3A, 503 35 Borås, Sweden

Contents

  1. In short
  2. Who is responsible
  3. What we collect and why
  4. Data in your workspace
  5. The Snacka apps
  6. Google Calendar in Alma
  7. Other companies involved
  8. How long we keep data
  9. Your rights
  10. Changes and contact

In short

  • Your workspace content is stored on your organisation's own server in the EU/EEA, today in Sweden, not in a shared Nordkastell database.
  • We hold your customer account and figures about your server's health, not your content.
  • We do not sell personal data, use it for advertising or use it to train AI models.

Who is responsible

Nordkastell is operated by H5 Förnyelsebyrå AB, organisation number 556970-4371, VAT number SE556970437101, Skaraborgsvägen 3A, 503 35 Borås, Sweden. We are the controller for this website, early-access requests, customer accounts and billing, the platform we run servers from, the Snacka apps' update checks, and security reports and requests under your rights.

For everything inside a workspace, the organisation that runs it is the controller and we are its processor, under our data processing agreement. If you use Nordkastell through your employer or school, they decide what happens to your data there, and questions about it go to them first.

What we collect and why

  • Customer accounts: name, email address, role, organisation and acceptance of the terms, and the sessions you sign in with, including IP address and browser. We use them to provide the service your organisation signed up for and to keep accounts secure, based on our agreement with your organisation and our legitimate interest (Art. 6(1)(b) and (f) GDPR).
  • Server health: figures such as CPU, memory and disk use, and a log of what we have done on each server, to run and repair the service (Art. 6(1)(f)).
  • Billing, once it starts: plans, invoices and payment status, to charge for the service and because the Swedish Bookkeeping Act requires us to keep accounting records (Art. 6(1)(b) and (c)).
  • Early-access requests: what you fill in on the form, and our notes and the invitation we send, to answer you and set up your workspace (Art. 6(1)(b) and (f)). Name, email, phone and company are needed to reply; the rest is optional.
  • Security reports and rights requests: what you send us and our reply, to handle the matter and show that we did (Art. 6(1)(c) and (f)).

This website

nordkastell.se sets no cookies and uses no third-party trackers. If you pick a light or dark theme, your browser remembers it. The customer dashboard sets a cookie to keep you signed in.

We count visits on our own server: the page, where you came from, your country, browser and device type, and how long the page was open. Your IP address is used briefly to look up your country and to make a daily code for counting unique visitors, and is not stored. If your browser sends Do Not Track or Global Privacy Control, nothing is recorded. The legal basis is our legitimate interest in knowing how the site is used (Art. 6(1)(f)), and you can object at any time.

No law requires you to give us any of this, but without the account details we cannot provide the service. We make no decisions about you based solely on automated processing.

Data in your workspace

Everything your team puts into the apps is stored on your workspace's server and is not copied into any central Nordkastell system. Our staff can reach the server to install updates and fix problems, and may see personal data in its logs while doing so. The logs are deleted after about 30 days.

Email from the workspace, such as invitations and sign-in links, is sent through our platform and Loopia without being stored on the way.

AI features

The AI app is optional. Once a workspace connects an AI account, what the AI works on is sent to Anthropic or OpenAI in the USA:

  • questions to Reda, and the content Reda reads to answer them, such as messages, hours or calendar events the person asking can see;
  • exam answers in Tempa, when the teacher uses automatic grading;
  • email handled by an email assistant.

With a workspace AI key, the organisation's agreement with the provider governs that data. With a member's own Claude or ChatGPT account, that person's agreement applies, and depending on their settings the provider may use it for training. In Tempa, the teacher can change any grade the AI proposes and chooses when students see them.

The Snacka apps

Snacka, our chat and video call app, also comes as a phone app and a desktop app. H5 Förnyelsebyrå AB provides them; in the App Store the seller is currently shown as Hafajy Group AB. The apps connect to your workspace's server like the web version, so everything above applies to them too.

  • Permissions: the camera and microphone for calls and photos, and notifications. You choose which photos and files to send; the app does not read your library on its own, and it does not ask for your location or contacts.
  • On your device: your sign-in, the workspace's address, your settings and a cache of recent content so the app opens quickly. Signing out deletes the cache and any unsent messages.
  • Notifications to a phone go through Apple or Google and our platform, which passes them on without storing them. A message notification contains what you see on the lock screen, including the message text.
  • Calls go through your workspace's server, encrypted in transit. They are not end-to-end encrypted, and they are not recorded.
  • Link previews are fetched by your workspace's server, and the preview picture loads from the linked site. A YouTube or Vimeo video loads from them only when you press play.
  • Updates: the phone app checks with Expo (USA) for updates, which sees the phone's IP address, the app version, an installation ID and any crash message. The desktop app checks our platform and downloads from GitHub. We are the controller for these checks, based on our legitimate interest in delivering fixes (Art. 6(1)(f)).

The apps contain no analytics, advertising or tracking tools.

Google Calendar in Alma

A member can choose to connect their Google account to Alma, our team calendar, so their calendar shows next to their colleagues' and they can create and change events from Alma. Nothing happens until they approve it on Google's consent screen.

Alma asks for the account's email address and read and write access to its calendars, and touches nothing else on the account. For the calendars the member picks, Alma stores a copy of the events from 90 days back to a year ahead, with their titles, times, places, descriptions and guests. It writes to Google only when the member creates, changes or answers an event in Alma. Everything, including Google's tokens, is kept on the workspace's own server, and the tokens are encrypted there.

Colleagues see the titles and times of events in calendars the member shares with the team. Descriptions, places and guests are shown only to the member.

Disconnecting Google in Alma revokes Alma's access and deletes its copy straight away. When a member is removed from the workspace, Alma does the same shortly after. If access is withdrawn at myaccount.google.com/permissions, Alma deletes the tokens and, unless the member reconnects within 30 days, the copy of the events. Copies in the server's backups disappear as the backups are replaced, within two months at most.

Google API Services Limited Use

Nordkastell's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only for the calendar features in Alma that the member connected it for. We do not sell it, use it for advertising, or use it to develop, improve or train generalised AI or ML models. It is not shared with anyone except as needed for those features, for security, or where the law requires it. No one at Nordkastell reads it unless the member asks us to, or security or the law requires it.

Other companies involved

These sub-processors help us run the platform and every workspace:

  • Hostup (Sweden) hosts the servers and makes their backup images.
  • deSEC (Germany) runs the DNS for workspace addresses.
  • Let's Encrypt (USA) issues the certificates for workspace addresses, which appear in public certificate logs.
  • Loopia (Sweden) sends email from our platform and workspaces, and hosts our own mailboxes.
  • GitHub (USA) hosts the app software servers download, and the desktop app's downloads.
  • Apple and Google (USA / EU) deliver notifications to phones with the Snacka app.

These receive data only when your organisation or a member chooses to use the feature behind them, under that organisation's or member's own agreement with them:

  • Anthropic or OpenAI (USA): when the workspace connects an AI account, as described under AI features.
  • Calendar and mail providers, such as Google or iCloud: when a member connects their calendar to Alma or their mailbox to Korgen or the AI app.
  • Google or GitHub: when someone signs in to their customer account with them, or the workspace connects a GitHub repository.
  • Slack: while an import from Slack that you started is running.
  • Browser push services: when someone allows notifications in Snacka's web version. The content is encrypted so the service cannot read it.
  • YouTube and Vimeo: when someone presses play on a video link in Snacka.

Expo (USA) handles the phone app's update checks, for which we are the controller. Transfers to the USA rely on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses. Once billing starts, we will name our payment provider here first.

How long we keep data

  • Workspace data is kept for as long as the organisation keeps it, and deleted 30 days after the agreement ends.
  • Backups of each server are replaced as they age, so deleted data can remain in them for at most two months.
  • Logs on the servers are deleted after about 30 days.
  • Customer accounts are deleted within 30 days after the agreement ends. Bookkeeping records are kept for seven years, as the law requires.
  • Sign-in sessions are deleted 30 days after they expire.
  • Website statistics are deleted after 13 months.
  • Early-access requests are deleted 12 months after our last contact, or sooner if you ask.
  • Security reports and rights requests are kept for at most 3 years after they are closed.

Your rights

You have the right to access, correct and have deleted your personal data, to restrict or object to its processing, to data portability, and to withdraw any consent you have given. We answer within one month. You can also complain to Integritetsskyddsmyndigheten (IMY, imy.se), or to the authority where you live or work.

For data inside a workspace, ask the organisation that runs it. If your request reaches us, we pass it on within five working days. How someone who uses Snacka has their account deleted is described under deleting your account.

Changes and contact

We update this page when the product changes, and the date at the top shows when. We email customers before a change that materially affects how we handle their data. The policy is published in Swedish and English, and the Swedish version prevails if they differ.

Questions about personal data: privacy@nordkastell.se. Security vulnerabilities: security@nordkastell.se, as our security page describes. By post: H5 Förnyelsebyrå AB, Box 8000, 501 18 Borås, Sweden.

© 2026 H5 Förnyelsebyrå AB. All rights reserved.

Skaraborgsvägen 3A, 503 35 Borås, Sweden

Legal

  • Privacy policy
  • Terms of service
  • Data processing agreement
  • Delete account

Help

  • Get started
  • Support
  • Security

Language

  • English
  • Svenska