Privacy Policy

1. Overview

This policy explains how LoopLog handles personal data during the private beta. LoopLog is designed to help riders record theme park activity, build a passport profile, and optionally share selected stats publicly.

This policy should be reviewed by a qualified legal adviser before a wider public launch, especially once the final business entity, contact address, support email, analytics choices, and retention schedule are confirmed.

2. Data We Collect

• Account data, such as email address and authentication ID.
• Profile data, such as username, display name, country, bio, avatar, home park, favourite ride, and passport cover.
• Ride and park data, such as ridden attractions, ride counts, dates, park visits, rankings, badges, and leaderboard stats.
• Memory data, such as optional ride notes, captions, and ride memory photos.
• Technical data needed to run the service, such as session information, security logs, and hosting diagnostics.

3. How We Use Data

• To create and secure your account.
• To save your ride logs, park visits, badges, and stats.
• To show your dashboard, profile, and public passport.
• To operate rankings, milestones, and beta product testing.
• To diagnose bugs, prevent abuse, and protect the service.
• To respond to support, privacy, or rights requests.

4. Lawful Bases

Depending on the context, we rely on the following lawful bases under UK data protection law:

• Contract, where processing is needed to provide the LoopLog account and app features you request.
• Legitimate interests, where processing is needed to improve, secure, debug, and protect the beta service.
• Consent, where you choose to upload optional content such as photos or public profile details, where consent is the appropriate basis.
• Legal obligation, where we must keep or disclose information to comply with applicable law.

5. Public Information

Public passport and leaderboard features may show selected profile and ride activity, including username, display name, avatar, country, stats, badges, favourite rides, parks visited, and recent ride activity. Do not add information to your public profile that you do not want others to see.

6. Processors and Hosting

LoopLog currently uses Supabase for authentication, database, and storage, and Vercel for web hosting and deployment. These services may process data in the UK, EEA, US, or other locations depending on their infrastructure and contractual safeguards.

LoopLog does not currently use MailerLite, advertising pixels, or third-party marketing analytics in the app.

7. Cookies and Local Storage

LoopLog uses essential authentication/session technology so you can stay signed in and use protected app features. We do not currently use non-essential advertising cookies or analytics cookies. If that changes, we will update this policy and add consent controls where required.

8. Retention

We keep account and ride data while your account is active or while needed to operate the beta. You can request deletion of your account or personal data. Some limited information may be retained where required for security, legal, dispute, or backup reasons.

9. Your Rights

Depending on your location and the lawful basis involved, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data. You may also have the right to withdraw consent where processing is based on consent.

UK users can complain to the Information Commissioner's Office if they are unhappy with how personal data is handled.

10. Contact

During private beta, privacy requests should be sent using the support or contact channel provided with your beta invitation. A dedicated public privacy contact should be added before wider launch.