Your school plays a central role in protecting customer data. What you ask customers, which staff can see their information and what you keep after an activity all affect their privacy.
Give your team only the access they need, collect information for a clear purpose and regularly remove details that are no longer needed. This guide explains what your school can do in its day-to-day use of Viking.
In short
- Give staff the lowest level of access they need.
- Collect only information needed for a clear, lawful purpose.
- Regularly remove personal details and messages you no longer need.
- Choose whether to delete old bookings or keep them with fewer personal details.
- Protect accounts, devices and downloaded exports.
Your school decides what to collect and keep
Your school is responsible for ensuring that its use of customer data complies with applicable privacy laws, including the GDPR where applicable. This includes having a valid reason to collect and use the information, explaining that use to customers and setting appropriate retention periods.
A field being available in Viking does not mean that collecting or retaining that information is necessary or legally permitted. Review the standard fields, custom questions and additional-message fields in your booking forms. Ask staff to keep customer notes relevant to the activity.
Give staff as little access as their work allows
Give each team member only the access needed for their work. Use Instructor or Head Instructor where those roles are sufficient.
Planners can view customer records and messages, so only assign this role to staff who need that information for planning and booking management.
School Manager and System Manager have broader management permissions. System Managers can also make report exports. Keep these roles limited to as few people as possible and use a lower-access role for everyday work whenever possible.
Regularly check that:
- Each employee still needs access.
- Their role matches their current responsibilities.
- Their account uses the correct email address.
- Staff roles are removed promptly when someone leaves.
Automatic account restrictions are an additional safeguard. Do not wait for an account to become inactive before removing access that is no longer needed.
Collect only information you need
Each question in your booking form should serve a clear purpose. For example, weight may be needed to select suitable equipment for one activity, while another activity does not need it.
Use the booking-form settings to make standard fields required, optional or hidden, as appropriate. Review custom questions too, including whether you need an answer for each participant or only once per booking.
Take particular care with health information entered through custom questions or customer messages. Only collect it where necessary and legally permitted, and remove it when it is no longer needed.
To remove medical information, simply delete the message containing it from the booking, the customer record, or both, depending on where it is stored. You can keep the booking itself.
Read more about booking-form fields.
Remove information you no longer need
Set retention periods for different types of information and review them regularly, for example at the end of each season. Customer details, health information, financial administration and signed waivers may need different retention periods.
You can delete bookings or remove personal details while keeping the booking. Choose the approach that fits the information your school still needs.
- Delete the booking if you no longer need it or its associated reports. Deleting a booking also removes its associated reporting.
- Keep the booking and clear or replace personal details if you still need the reporting. You can manually remove customer messages and change names, email addresses, phone numbers, dates of birth and weight. Use neutral placeholders where needed, never another person’s contact details.
Before making changes, check for outstanding activities, payments, legal retention requirements or a specific dispute. Knowing the figures does not by itself mean that underlying records can be deleted; make sure any records you must retain are preserved.
Changes to personal details are reflected in subsequent exports. Previously downloaded exports remain unchanged and must be reviewed separately.
Protect accounts and unattended devices
Use strong, unique passwords and keep passwords and authentication codes private. Do not share System Manager credentials or approve an authentication request you did not initiate.
Lock devices when stepping away and log out after using a device that others can access. Where a device stays available for daily planning, use a role with only the permissions needed for that work.
Keep downloaded exports secure
Once an export leaves Viking, your school must also protect the downloaded copy. Download only what you need, store it securely and share it only with authorised people.
Review copies in downloads folders, shared devices, email attachments and shared storage. Remove them when they are no longer needed rather than keeping an indefinite archive of customer lists.
Report suspected unauthorised access promptly
If you suspect that someone has accessed customer information without permission, contact Viking support promptly. Explain what happened, when it happened and which account or part of the system may be involved.
Include enough information to investigate, but do not send passwords, authentication codes, full customer exports or unnecessary health information.