Back to map

Privacy Policy

Last updated: May 3, 2026

1. Overview

Berlin Culture Map helps people discover free and affordable events in Berlin. The app includes optional account features for community posts, voting, and account management.

2. Contact

Privacy, deletion, and takedown requests can be sent to jaewon.support@gmail.com.

3. Accounts And Login

The app uses Supabase Auth with Google OAuth. If you sign in, Supabase and Google may process authentication data. The app may receive and use your account email, display name, and avatar URL from your Google/Supabase profile metadata.

4. Community Content

Signed-in users can create community posts, upload images, add source links, and vote on posts. Community post content, post location, uploaded image URLs, vote records, and account ownership metadata are stored in Supabase. Public community posts are visible to other users until they expire, are removed, or are deleted.

Uploaded images are checked for allowed file type and size. The upload pipeline strips image metadata before storage. To report unlawful, unsafe, or privacy-invasive user content, contact jaewon.support@gmail.com.

5. Location

The browser geolocation prompt is used to sort nearby events when you allow it. Coordinates sent to the events API are rounded before the request. Community event addresses may be geocoded through the app server to place a map marker.

  • Browser location permission is controlled by your browser.
  • The app does not intentionally store event-search coordinates.
  • Community post coordinates are stored because they are part of the post.
  • Event API responses use private no-store caching.

6. Hosting, Logs, And Analytics

The site is hosted on Vercel and uses Supabase for database, authentication, and storage. These providers may process technical request data such as IP address, user agent, timestamps, requested URLs, and error logs to operate and secure the service.

Vercel Web Analytics is currently disabled in the application code pending legal review and a consent/notice decision.

7. Maps And Directions

The map loads tiles from the configured tile provider. The current code uses Mapbox when a public Mapbox token is configured and falls back to OpenStreetMap tiles otherwise. Tile providers receive the tile requests needed to render the map. Address autocomplete uses Photon, and server-side fallback geocoding may use Nominatim.

Links to Google Maps and Apple Maps are ordinary external links. If you open them, those providers receive the request directly.

8. Event Data Sources

Event listings are aggregated from public APIs, open-data feeds, RSS feeds, and selected public source pages, then cached in Supabase. Public event responses expose reduced fields and short summaries; raw provider payloads remain internal. Event data may be incomplete or outdated, so users should check the original source link before relying on an event listing.

See the sources page for attribution and source-specific links.

9. Account And Data Deletion

Signed-in users can delete their account from the account page. The deletion flow removes their votes, their community posts, and user-owned community images stored in Supabase Storage before deleting the Supabase Auth account where possible. If automated deletion fails, contact jaewon.support@gmail.com for help.

This page is a product/privacy notice draft for the current implementation and should be reviewed before public launch. Contact: jaewon.support@gmail.com