Your team retreat details are handled with care
NextRetreat protects attendee and trip information through encryption, restricted access, secure infrastructure and deliberate data-sharing practices.
Attendee profileAttendee nameE-mailPhone numberTrusted by companies like
A private link for every attendee
Each attendee receives a unique link to their attendance page. The link contains a private, non-guessable token selected from 10¹⁸ possible combinations. Rate limiting and cloud-level threat detection provide additional protection against automated attempts to discover valid links.

Accommodation provider
Receives attendees’ full names. Passport information is normally collected directly by the provider at check-in.
Airport-transfer provider
Receives attendee names, arrival times and flight numbers for tracking purposes.
Other booked provider
Receives only the information required to deliver the specific service.
Security built into every stage of planning
From the first attendance form to post-retreat deletion, we use technical controls and careful internal processes to protect the information entrusted to us.
Encrypted in transit and at rest
Data sent to and from the NextRetreat App is protected with HTTPS. Stored customer data is encrypted using AES-256.
Restricted access
Customer information is available only to authorized NextRetreat team members who need it to deliver the service.
Private attendee links
Each attendee receives a unique private link protected by a non-guessable token, rate limiting and infrastructure-level threat protection.
A clear deletion process
Trip data can be removed from the platform after a retreat. Deleted data is automatically erased from database backups within seven days.
Access is limited to the people delivering your retreat
Only authorized NextRetreat team members can access customer information, and only when they need it to perform their role.
Some attendee information must be shared with essential partners so they can deliver the booked service. We share only the fields each partner needs.

Layers of protection around your data
Technical controls and infrastructure safeguards work together to protect your retreat information.
Encryption
All traffic is protected with TLS via HTTPS. Stored data is encrypted at rest using AES-256.
Isolated cloud infrastructure
Runs in an isolated AWS network, accessible only through defined endpoints.
App protection
Protected by AWS WAF and AWS Shield with malicious-IP blocking and threat detection.
We ask for what the retreat requires
Attendees typically provide their name, email, travel details and the personal preferences requested by the organizer.
We do not collect or share passport data unless specifically requested by the client. Hotels typically collect it directly at check-in.
Typical attendee information
Name
Email
Travel details
Personal preferences requested by organizer
Information we avoid collecting by default
Passport details
Home address
A defined end to the data lifecycle
After the retreat, the organizer can request deletion of the trip and its attendee data.
Request deletion
The organizer deletes the trip in the App or asks NextRetreat to do so on their behalf.
Data is removed
Trip and attendee info is removed from the platform. Confirmed in-app and by email.
Backups expire
Backups are automatically and permanently erased within seven days of deletion.
Your questions about data security, answered
Is our data encrypted?
Who at NextRetreat can access our information?
Do you share attendee information with third parties?
Do attendees need to provide passport information?
How do the private attendee links work?
What happens when I request data deletion?
Where is the app hosted?
Can NextRetreat sign an NDA?
Your next team retreat starts with a conversation
Tell us about your team, dates and goals. We’ll help you turn them into a clear plan.