GitHub
Used for source code, version control and static project files. GitHub is not intended to store participant production data.
Data & Privacy
Clear data storage. GDPR from the start.
Camp-Planner is still under development, but data protection must be part of the product from day one. This page explains the current setup and the principles we are building around.
Current technical setup
Where data is stored today.
At the current development stage, Camp-Planner uses a small number of trusted services to build, host and operate the website and application.
Vercel
Used for website and frontend deployment. Vercel serves the website and application frontend.
Supabase
Used for backend services such as database, authentication and application data as the product develops.
One.com
Used for domain registration, DNS and domain-related services.
GDPR approach
Our GDPR principles.
Data minimisation
We only aim to collect the personal data needed to plan, run and support an event.
Purpose limitation
Personal data is used for event administration, communication, check-in, participant management, support and product operation.
Access control
Customer and event data should only be available to authorised users based on role and organisation.
Deletion and retention
Event data should be deleted or anonymised when it is no longer needed, subject to legal and operational requirements.
Processor agreements
Where suppliers process personal data on behalf of Camp-Planner or its customers, relevant data processing agreements must be in place.
Transparency
Customers and participants should be able to understand where data is stored and who processes it.
Typical data categories
What kind of data Camp-Planner may process.
The final product may process organiser details, instructor details, participant information, event registration data, schedule data, accommodation preferences, check-in status and communication history. Payment data should be handled by dedicated payment providers and not stored directly by Camp-Planner unless required for accounting records.
Responsibilities
Controller, processor and customer responsibility.
For the marketing website and Camp-Planner’s own communication, TK Virksomhedsservice / Camp-Planner is responsible for the personal data it collects.
For customer events, the customer or organisation may be the data controller for participant data, while Camp-Planner may act as a data processor depending on the final contractual setup.
Important note
This page will evolve before launch.
Before commercial launch, Camp-Planner should maintain a formal privacy policy, cookie policy, data processing agreement, subprocessors list, retention policy and security overview.
Camp-Planner
Questions about data or GDPR?
Contact us if you need information about data storage, security or compliance before joining the pilot programme.