Laster …
Freysta

Freysta Portal

Privacy Policy

How Freysta Portal handles personal data.

Last updated: 15 October 2026

Norsk · English

Privacy in short

Quick summary

The portal helps members explore jobs and communities and communicate with municipalities, local advisers and employers.

Who controls your data

Freysta AS controls its own account, platform operation and support processing. Customers control their own member dialogue and case management; Freysta processes that data on their behalf.

Contact: post@freysta.com

What data we process

We process account details, profile information you choose to add, messages, uploaded documents, and preferences used for jobs and community recommendations.

Who can see your information

Once you have completed joining a customer, your profile is visible to the customer's advisers and to the partner employers who have access to the Portal through that customer. They can see, among other things, your name, age, nationality, occupations, education and work experience. You cannot hide your profile, but you can delete it. Other members cannot see anything about you.

Employers can also see your family situation, information in your partner's profile and information about children moving with you, including their years of birth and calculated ages.

Freysta never sells personal data to third parties.

How communication works

Communication in the portal happens between Freysta members and municipalities, and between Freysta members and employers.

Users cannot send direct messages to other users outside those flows.

Your main rights

You can ask for access, correction, deletion, restriction, objection, and data portability under applicable data protection law.

How to contact Freysta

Freysta AS, Ovre Holen 24B, 5163 Laksevag, Norway

Organisation number: 929 913 477 MVA

Email: post@freysta.com

1. Data Controller

Freysta Portal is operated by Freysta AS.

Freysta AS, Ovre Holen 24B, 5163 Laksevag, Norway. Organisation number: 929 913 477 MVA. Email: post@freysta.com

Freysta AS is the controller for its own account administration, platform operation, security and support. Municipalities and customer organisations, including Lister Næringsforening, are controllers for their own dialogue with members and case management. Freysta is their processor under a data processing agreement.

Customers using the Portal:

  • Region Lister is run by Lister Næringsforening (org. no. 928 975 428), which is responsible for the dialogue between members and the local guides in Lister. Contact: post@listernaeringsforening.no.

2. Who Uses the Portal

Freysta Portal is used by Freysta members exploring jobs and communities, employers presenting businesses and job opportunities, municipalities working with settlement and integration, and Freysta administrators who operate and support the platform.

Different roles have access only to the information necessary for their interaction with the service.

Who can see your profile

Once you have completed joining a customer, your profile is visible to the customer's advisers and to the partner employers who have access to the Portal through that customer. They can see, among other things, your name, age, nationality, occupations, education and work experience. You cannot hide your profile, but you can delete it. Other members cannot see anything about you.

In Region Lister, this means the local guides, the municipalities and the companies that work with Region Lister.

Employers can also see your family situation, information in your partner's profile and information about children moving with you, including their years of birth and calculated ages.

3. Personal Data We Process

Depending on how you use the platform, we may process the following categories of data.

We store the time of your most recent successful account sign-in across portals to identify accounts that are no longer used. This is a single timestamp, not a sign-in history, and does not include an IP address or device information. Support impersonation does not update it.

Account information

  • name
  • email address
  • authentication identifiers
  • account status information

Profile information

Information you choose to provide, for example:

  • year of birth
  • education and work experience
  • language skills
  • interests and preferences
  • personal description

Communication data

When you communicate with municipalities or employers through the platform:

  • message content
  • message attachments
  • thread participation
  • read status

Case and document data

When municipalities use the Ferd module:

  • case metadata
  • tasks and notes
  • journal entries
  • uploaded documents

Notification data

To manage notifications we process:

  • notification preferences
  • notification delivery status
  • technical identifiers used to deliver messages

System and security logs

To operate and protect the service we process limited technical data such as:

  • audit logs of administrative actions
  • system error logs
  • notification delivery logs

These logs are limited to what is necessary for system operation and security.

A person may have separate profiles in contexts such as Region Lister. These include household and child information, occupations, education, village interests and preferences you choose to provide. Information is displayed according to the active context and access permissions.

Documents include CVs, attachments and profile pictures. Notification preferences and delivery information are used to send requested notifications. Email sign-in links use short-lived tokens and sessions.

Employers can keep favourites and candidate lists for their own employer and context. Personal visit baselines tell an authorised employer user which matching candidates are new since their previous visit.

You can create a profile for your partner. This requires you to confirm that your partner has consented. For children, we only store that you are moving with a child and the child's year of birth.

4. Purpose of Processing

Providing the service

To create user accounts, manage profiles and enable interaction between Freysta members and municipalities or employers.

Communication

To allow Freysta members to communicate with municipalities and employers within the platform.

Recommendations and matching

The platform may recommend job opportunities and communities or villages.

Recommendations are based on user preferences and job metadata.

These recommendations are informational only and do not involve automated decisions that produce legal or similarly significant effects.

Case management

Municipalities may use the Ferd module to manage cases, documents and tasks related to integration work.

Security and system operation

We process technical and audit data to:

  • ensure system reliability
  • investigate errors
  • prevent misuse

Support

Freysta administrators may access user accounts when necessary to assist with support requests.

Such access is logged.

Administrators may impersonate a user for necessary support. The administrator, the account being assisted and the support action are logged. Impersonation does not count as the user's normal activity or acknowledge employer visits.

6. Service Providers

Freysta uses external service providers to operate the platform.

Examples include

  • Hetzner - Servers, databases and encrypted offsite backups in Hetzner Storage Box.
  • Clerk - Authentication and identity management.
  • Google SMTP relay - Email delivery for system notifications.
  • Azure Translator / Apertium - Translation of public content. These services must not be used to translate personal profiles, private messages or uploaded documents.

These providers process personal data only on Freysta's instructions.

7. International Data Transfers

Some service providers may process data outside the European Economic Area (EEA).

When this occurs, Freysta ensures appropriate safeguards are in place, such as EU Standard Contractual Clauses or equivalent legal mechanisms.

8. Cookies and Sessions

Freysta Portal uses a secure session cookie to maintain user authentication.

The session cookie stores a signed session identifier, allows the platform to recognise logged-in users, and is not used for cross-site tracking.

Security settings include HttpOnly, SameSite protection, and secure transmission when HTTPS is used.

Company pages may contain YouTube or Vimeo videos. No player or video-provider preview is loaded before you click to play. YouTube uses youtube-nocookie.com; Vimeo uses its privacy option. After your click the provider receives technical data such as your IP address and processes it under its own privacy policy.

9. Data Retention

Personal data is retained only as long as necessary.

Examples include

  • member profiles: while needed for the membership; operator identities are deactivated and their history preserved as described below
  • notification delivery diagnostics: up to 30 days
  • ordinary technical error and access logs: up to 30 days
  • administrative audit, access changes and impersonation: 12 months; the separate context validation log follows its own rules

Where possible, data may be anonymised or deleted when no longer required.

Administrative audit logs, access changes and support impersonation records are retained for 12 months, except for the separate context validation log, which follows its own retention rules. Ordinary technical error, access and email-delivery diagnostic logs are retained for up to 30 days. These periods do not set the retention of customers' case records or journals. Records needed for a documented incident or legal obligation require a separate, justified retention decision.

Usage statistics are retained for 13 months. In the current activity report, account identifiers are retained for the same period to count distinct people across days, months and selected periods. Reports show totals to authorised users, not a public list of people. The separate legacy daily seen-user register is only a temporary counter: entries older than yesterday are removed daily after the daily total has been recorded. These registers are not used as browsing history.

When customer staff or employer users leave, their accounts are deactivated rather than erased. Portal access is blocked, while their names stay attached to their previous messages and actions. Their profile pictures, phone numbers and notification preferences are removed on deactivation.

An employer user's visit baseline and seen-candidate register are removed when that user loses access to the employer. Customers determine the retention of their dialogue and statutory case records. Backup copies expire through their separate retention cycle and are not used as active profiles.

If an account has not been used for 24 months, we send you an email saying that the profile will be deleted unless you log in within 30 days. If you do not log in, the account is deleted.

Conversations are retained when a local guide or adviser leaves. A new adviser must be given the appropriate access to the community or inbox and to the existing conversations; history is not transferred automatically just because a new account is created.

Inactive member accounts are reviewed manually. If login history is incomplete, the account is not deleted on the basis of presumed inactivity.

10. Your Rights

Under applicable data protection laws, you have the right to:

  • access your personal data
  • correct inaccurate data
  • request deletion of your data
  • restrict certain processing
  • object to processing based on legitimate interests
  • receive your data in a portable format

Requests can be sent to post@freysta.com.

11. Security

Freysta Portal implements several security measures, including:

  • role-based access control
  • database row-level security
  • audit logging of administrative actions
  • secure authentication
  • encrypted network connections

Access to personal data is restricted to what is necessary for each role.

12. Updates to This Policy

We update this policy when the service or applicable rules change. Material changes may be announced in the Portal or by email. The customer's joining document refers to this shared policy.

13. Contact

If you have questions about this Privacy Policy or how your personal data is handled, please contact Freysta AS.

Freysta AS, Ovre Holen 24B, 5163 Laksevag, Norway. Email: post@freysta.com