Privacy

Locol Privacy Policy

Last updated: 2026-09-04

This policy explains how Locol handles information in the Locol iOS app, the Locol website at locolapp.xyz, the waitlist, and support.

Who is responsible

Locol is operated by Wesley Koot, a natural person and sole owner.

What Locol does

Locol helps people browse public event information, save events privately, and make personal plans. You can browse as a guest. Signed-in features use an account. Optional features include Google Calendar availability, timing and directions, and sharing a private plan with invited people.

Information we receive

We collect information from you, your device, integrations you choose, and public or technical sources:

• Account and rights requests: account email, profile or account identifier, sign-in provider information, and the details needed to answer an access, export, correction, objection, or deletion request.
• Discovery and location: chosen or current latitude and longitude when you use location-based discovery, search radius, market or city, timezone, and search, event, or place identifiers and display data. Location access is optional; you can browse without granting location access.
• Saved content: saved event identifiers and the event display data needed to show your saved items.
• Plans and invitations: plan title, notes, event and place snapshots, place and time information, invitation-response identifiers, answers, attendance and reactions, and shared invite event details. Plans and intents are private to the people the plan owner invites.
• Google Calendar: a Google authorization code during connection, encrypted OAuth credentials and tokens, selected calendar identifiers, and the plan fields needed to check availability or write only the Locol plan you choose. Locol does not store your calendar contents.
• Live Activities and notifications: Live Activity identifiers, push token, route coordinates, travel mode, and timing when you request a relevant timing or Live Activity feature.
• Optional product analytics: when you give the required consent, product interaction records can include an event, timestamp, idempotency key, market, surface, app version, a signed-in account identifier or a random guest installation identifier and hash, and relevant invite or plan identifiers. Locol has no advertising SDK, ATT-based advertising tracking, crash reporter, or resale of personal data.
• Waitlist: the email address, city, business flag, and referral information you submit on the website. We retain it for 12 months after the last contact, or until the account is created.
• Website and security data: Cloudflare may process standard technical request data and bot-protection data when you use the website or its Turnstile protection.

Locol does not use product analytics to collect calendar contents, contacts, precise location, messages, or plan links. The optional analytics described above is first-party and consent-gated.

Why we use information and our legal bases

If a signed-in feature requires account data, we explain that requirement at the point of use. Withdrawing optional analytics or waitlist consent does not affect unrelated features. Withdrawal does not make earlier lawful processing unlawful. You can object to processing based on legitimate interests; we will stop unless we have a compelling lawful reason or need the information for legal claims.

Recipients, processors, and third-party services

Depending on the service, providers may act as processors on Locol's instructions or as independent controllers under their own terms. We use or interoperate with the following services for the purposes above:

• Supabase, hosted in eu-central-1 (Frankfurt), for authentication, database, Functions, and Storage.
• Cloudflare for Pages, Functions, D1, Turnstile, network security, and delivery of the website.
• Apple for iOS distribution, Sign in with Apple, APNs and ActivityKit, and Apple Maps/MapKit where used.
• Google for Google Sign-In, optional Google Calendar, and the Google Workspace support email.

For Google Calendar and other Google Workspace scopes, the following statement applies exactly:

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

See the Google User Data Policy.

International transfers

Supabase stores the primary Locol backend data in Frankfurt. Other providers may process information in countries outside the European Economic Area as part of their global infrastructure or support. Where a transfer is required, Locol will use a lawful transfer mechanism and appropriate contractual, technical, or organizational safeguards, such as an adequacy decision or approved standard contractual clauses where applicable. Contact us for the current provider-specific transfer information.

How long we keep information

• Account and plan content is kept while the account is active and then purged, subject to legal duties, disputes, and necessary recovery records.
• Guest product interaction records are kept for 35 days.
• Signed-in product interaction records are kept for 90 days.
• An account deletion request has a 30-day recovery period. Your account remains active and you can sign in during that window; to cancel before the deadline, contact [email protected].
• A private data-export object is available for at most 24 hours; a signed export URL expires after 5 minutes.
• A completed-deletion tombstone without personal data is retained for 730 days to prevent accidental re-creation and support auditability.
• Address-free completion-notification evidence is retained for 90 days.
• Google Calendar tokens are retained until you disconnect Calendar or your account is purged, with bounded revocation handling.
• Waitlist records use the following owner-confirmed period: 12 months after the last contact, or until the account is created.

If an in-app export or deletion operation is unavailable, contact [email protected].

Your choices and rights

Depending on where you live, you can ask us to access, correct, export, or delete your information, restrict or object to processing, and withdraw consent. You may also complain to the supervisory authority in the EU/EEA country where you live, work, or believe an infringement occurred. Autoriteit Persoonsgegevens (NL)

To make a request, email [email protected] and include enough information for us to find the relevant account or record. Do not send passwords, OAuth tokens, or other secrets. We may need to verify identity before fulfilling a request. We aim to acknowledge support requests within 2 business days and resolve rights requests within 30 calendar days, or tell you within that period why a lawful extension is needed.

For the current in-app controls:

• Export: Account → Privacy & data → Your data → Download your data. This prepares JSON; Share data export can save or share it. You must be signed in. See Data export.
• Delete: Account → Account & sign-in → Delete account. You can download your data first, type DELETE, and tap Request account deletion. The recovery window is 30 days; your account remains active and you can sign in during that window. To cancel before the deadline, contact [email protected]. See Account deletion.
• Google Calendar: disconnect it in Account. Locol will revoke credentials within bounded operational limits and purge them with the account where applicable.
• Optional analytics and waitlist communications: withdraw consent in the relevant control or contact us.

Children and automated decisions

Locol is a general-audience personal planning service. We do not knowingly request information from children in violation of applicable law. If you believe a child has provided personal information, contact [email protected].

Locol uses deterministic rules and ordinary service operations to show event information, availability, and planning features. We do not make decisions about people based solely on automated processing that produce legal or similarly significant effects.

Public events and the Digital Services Act

Event details come from public sources. Locol does not currently provide a public user-generated-content feed or organizer-submission channel. Private plans and intents can be shared with invited people. Reports about allegedly unlawful information or service issues can be sent to [email protected]. DSA points of contact: [email protected], [email protected], and [email protected]. EU languages accepted for DSA communications: English and Dutch.

Security

We use access controls, encrypted transport, protected token storage, bounded retention, and operational safeguards appropriate to the information and feature. No online service can guarantee absolute security. Tell us promptly about suspected account compromise or a security issue at [email protected].

Changes and contact

We may update this policy when the service, providers, or legal requirements change. We will update the date above and provide additional notice where required. Questions, rights requests, and support are handled at [email protected].