Privacy policy

In force since October 1, 2026 · last updated: October 9, 2026

This is an English translation for convenience. The Spanish version is the official one and prevails if they differ.

In short

We show things to do that the organizers themselves publish on their public accounts and websites.
We don't ask you to create an account and we don't sell data. We measure how the site is used with PostHog (visits, clicks and screen recordings with whatever you type hidden), using an anonymous identifier; if your browser sends "Do Not Track", we don't measure you. We also see in Google Search Console which Google searches lead to the site: Google gives them to us as totals, with nothing about who searched.
On each listing and in the "Swipe" view we show the original post using Instagram's official embed code: that image is served by Instagram (Meta), we don't copy it, and Meta receives data about that visit.
If you view the site in English, listing texts are translated automatically from Spanish with artificial intelligence and may contain mistakes; each listing lets you see the original.
We don't store comments or data about the people who follow or comment on the organizers.
To invite municipalities to publish their events, we keep the name, job title and work email of people on their events, culture and communications teams, taken from their public LinkedIn profiles, from the municipalities' own websites and from Apollo.io. They are not published.
If something of yours appears and you want it corrected or removed, use the removal form (in Spanish). If you ask us to remove an image, it is hidden immediately.

1. Who is responsible

The data controller is Ismael Tagle, an individual domiciled in Santiago, Chile, who runs Salir Santiago (salirsantiago.com). For any question or to exercise your rights, write to us through the contact and removal form or the "Contact" form in the site's footer; every request goes straight to the person responsible.

2. What data we use and where it comes from

Data	Source	Purpose
About activity organizers (collectives, venues, clubs, communities): account name and username, description, links, profile picture, follower count and their posts (text, images, date and place).	Public Instagram accounts, Meetup groups, websites, culture listings and ticketing sites. Restaurants, cafés and bars come from OpenStreetMap (data © OpenStreetMap contributors, ODbL license).	Building the listings, the organizer directory and finding new activities.
Posts from public Facebook groups that announce activities: text, images, date and link of the post. We do not store who wrote it (name, profile or photo), nor comments or reactions.	Some public community Facebook groups (expats, languages, tango, hiking).	Finding activities announced there. We publish the activity with a link to the post, without data about who wrote it.
Public stories from some organizer accounts: the text of the announcement and what the poster says (what, when, where and price). We don't store story images or who viewed or replied to them.	Public Instagram accounts of organizers, checked in one-week turns (after that we keep checking only the ones that announce activities there that they don't publish in their posts).	Finding activities announced only in stories. We publish the activity, without the story image, with a link to the account's profile.
Usernames of other accounts that are tagged in or related to an organizer (username only).	The same public posts, and the public stories of accounts that share listings (event guides and media).	Internal hints to find other organizers. Not published.
About people who work in events, culture or communications at the municipalities of the Santiago Metropolitan Region (and their cultural corporations or centers): name, job title, institution, their public professional LinkedIn profile (experience, education and location; without the photo or what other people write) and their work email.	Public LinkedIn profiles of people listed as working at those institutions, collected with Apify. The work email, from the directories and contact pages that the municipalities and their corporations publish on their own websites, or from Apollo.io. If someone is not on LinkedIn but their municipality publishes their email, we only keep their name, job title, unit and that email (or the unit's email, such as its culture department's).	Contacting the municipalities so they publish their events on the site. They are not published.
What you write in the form: name, email and message.	You.	Answering your request and keeping a record of what was done.
If you use the "Contact" form (in the site's footer): your email, your name (if you give it), the subject, your message and the page you wrote from. We don't store your IP address: only an encrypted fingerprint, in memory, to stop spam.	You.	Replying to you. The message reaches us by email and we reply to the email address you gave.
If you create an account ("Sign in"): your email, your password (stored encrypted by Supabase; we never see it), how you signed in (Google or email), when you created the account and when you last used it, and the listings you save in "My plans". If you sign in with Google, Google gives us your email, your name and your picture (we don't show them). Supabase logs the IP address and browser of each sign-in in its security log.	You, and Google if you sign in with Google.	Having the same saved plans on your phone and your computer. Your plans are only used to show them to you: they don't go to analytics or to artificial intelligence, and nobody else sees them.
If you use the "Report an error" button: what you write and what you had open when you reported it (the page, the listing or organizer, the filters and the map area), along with technical data about your screen and browser (screen size, browser type, language, time zone and time). We don't store your IP address: only an encrypted fingerprint to stop spam.	You and your browser.	Finding and fixing the error.
If you rate a search ("Rate this search"): the stars, what you write (if anything), what you searched for and the listings that were being shown. We don't store your IP address: only an encrypted fingerprint, in memory, to stop abuse.	You.	Knowing whether search works and improving it.
What you search for on the site and the technical data of the visit (IP address, browser, page requested). To understand what you are looking for (for example, "something quiet to do with my dog"), the text is sent to an artificial intelligence service, with nothing that identifies you.	Your browser.	Making search work and keeping the site available and secure.
How a search worked for you: the text, the filters you had on, what the search understood, the results we showed you and which ones you opened, saved or went to see from there. It is not stored with your IP address or anything that identifies you.	Your browser.	Checking whether search finds what people look for, and improving it.
If you use "Search with AI": what you typed in the search box, the filters you had on, the searches the artificial intelligence ran and what it picked. For the daily limit on AI searches we use a random number stored in your browser and an encrypted fingerprint of your connection, which the server forgets at the end of the day and which are not stored with your search.	You and your browser.	Running the search, keeping costs in check and improving search.
How you use the site (analytics): pages and listings you open, clicks, searches, which site you came from, device type, browser, the language you view the site in, whether you got the site ordered by your preferences (see section 8), approximate country and city, and screen recordings of the visit (movements, scrolling and clicks). In recordings, everything you type in text fields is hidden and never leaves your browser. It is tied to an anonymous identifier stored in your browser, not to your name.	Your browser, with PostHog.	Understanding what works and what doesn't, fixing design problems and measuring how many people reach each listing.

We don't store comments on posts, who liked them, or the private accounts an organizer follows. That data is discarded before saving.

3. Why we can use it (legal basis)

Organizer data and their posts: legitimate interest in spreading activities that the organizers themselves publish openly to promote them. We only use what is needed to show the listing and always link to the original post. You can object at any time (see section 7).
Municipal contacts: legitimate interest in inviting public institutions to promote their activities. We only use professional data (job title, institution and work email), and in the first contact we say where we got it. You can object at any time (see section 7).
Form: your consent and the exercise of your rights.
Contact form: your consent when you send it.
Your account: your consent when you create it; you can delete it whenever you want.
Error reports: your consent when you send one.
Search ratings: your consent when you send one.
AI search: your consent, when you press the "Search with AI" button.
Understanding what you search for: legitimate interest in search understanding what you ask for, without data that identifies you.
Search log: legitimate interest in improving search, without data that identifies you.
Technical visit data: legitimate interest in the site working and being secure.
Analytics and usage recordings: legitimate interest in improving the site, with an anonymous identifier and typed text hidden. You can object by turning on "Do Not Track" in your browser or blocking PostHog with an ad blocker.

4. What we publish

For each listing we show its basic details (what, when, where, price), a summary written by us, a small image from the post (or, if it has none, from the event's page on the organizer's website or from a post on their Instagram account) credited to the organizer, and a link to the original post. On the listing and in the "Swipe" view we show the original post embedded with Instagram's official code: the image is served by Instagram from its servers and we don't copy it; if the organizer deletes it or turns off embedding, it stops showing here. Dates and places are read automatically with the help of artificial intelligence and may contain mistakes: always check the source. If you view the site in English, the texts of listings and organizers are translated automatically from Spanish, also with artificial intelligence, and may contain mistakes: each listing lets you see the original.

5. Who it is shared with (providers)

We don't sell or hand over data. We use providers that process it on our behalf:

Supabase (database, images and accounts) and Render (site server), in the United States.
Google, if you sign in with your Google account: it confirms who you are and gives us your email, your name and your picture.
Apify (collecting public posts and stories, and public professional LinkedIn profiles) and GitHub (daily automated tasks).
Apollo.io (work email of the municipal contacts), in the United States: we send it the name, institution and LinkedIn profile link of those people.
ZeroBounce (checks that the work emails of those contacts exist, before we write to them), in the United States: we only send it those email addresses.
Artificial intelligence services (via NanoGPT) to read flyers, to sort listings by topic, for search by meaning, to check that content is not adult content, to flag whether a listing is fine to attend with children, to translate the texts of listings and organizers into English, to understand what you search for (Google Gemini reads only what you typed in the search box) and for AI search (DeepSeek and, if it is slow, Google Gemini: they read what you search for and the listings to pick the ones that fit) and to rank search results (JEV, by TypeSafe: it reads what you searched for and the listings of the top results). We send them the text or image of the post, or the text you search for, without data that identifies you.
OpenStreetMap / Photon, to place addresses on the map.
PostHog (analytics and usage recordings), in the United States.
Resend (email delivery), in the United States: it emails us each message from the "Contact" form, with your email, your name and your message. That email lands in the inbox of the person responsible (Gmail, by Google). It also sends your account emails (the code and the links to confirm your email or recover your password).
Instagram (Meta), when you view an embedded post on a listing or in "Swipe": your browser connects directly to Instagram, which receives data about your visit (such as your IP address and browser) and may use its own cookies, under Instagram's privacy policy. We don't receive that data.

Several of these providers are outside Chile, mainly in the United States (DeepSeek may process what you search for with AI in China), so there is an international transfer of data. We chose them because they state security and confidentiality measures for the data they process.

6. How long we keep it

Listings and images: while they are current on the site. Once an event has passed, its page stays up marked as past, with its basic details, the link to the original post and what's coming up from the same organizer (so people arriving from a search engine don't hit a broken link); you can ask us to remove it with the removal form. The images we keep of listings that have already passed are not shown on their page and are deleted periodically; images of posts that turn out not to be a listing are deleted the same day they are reviewed.
Post data as it was collected (without the third-party data that is discarded): up to 12 months, to fix errors without having to collect it again.
Form requests: up to 2 years, as a record of what was requested and done.
Messages from the "Contact" form: up to 12 months after they are sent; sooner, if you ask.
Your account and your saved plans: as long as you keep the account. If you delete it (in the "⋯" menu, "Delete my account"), it is deleted right away along with your plans.
Municipal contacts: up to 2 years from when we collected them or from the last contact; sooner, if the person asks.
Error reports: up to 12 months from when they are sent (pending ones, until they are resolved).
Searches (including AI searches), what you opened from them and their ratings: up to 12 months, to improve search.
Server technical logs: as long as the provider keeps them, usually a few days.

7. Your rights and how to exercise them

Under Chile's personal data protection law (Law 19,628, as amended by Law 21,719), you can request access (to know what data of yours we have), rectification (to correct it), erasure (to delete it), objection (for us to stop using it), portability (to receive it in a usable format) and temporary blocking.

Use the removal form (in Spanish; you can write in English). If you ask us to remove an image, it is hidden immediately. We review other requests within 3 business days and reply to the email you provide, always within the legal deadline of 30 calendar days. If you are not satisfied, you can file a complaint with Chile's Personal Data Protection Agency.

You can delete your account and your plans yourself whenever you want: sign in and, in the "⋯" menu, tap "Delete my account".

To have us delete a message you sent through the "Contact" form (and the copy we got by email), ask in that same form, from the same email address, or in the removal form.

8. Your browser

We don't use advertising cookies. We use PostHog to measure how the site is used (see section 2): it stores an anonymous identifier in your browser (a cookie and local storage) and does not run if your browser sends "Do Not Track". Embedded Instagram posts on listings and in "Swipe" are also third-party: they are loaded by Instagram (Meta), which may use its own cookies (see section 5). The site stores your preferences in your own browser (local storage), such as light or dark theme, language (Spanish or English), the view you chose and the listings you save (if you signed in, also your session, until you sign out), and also your preferences: what kind of listings you open, save or look at for longer (their category, district, price, time of day and organizer) and which page you arrived on (for example, a list of concerts), to show you first what you are more likely to enjoy and what you already saw a little further down. Older activity counts for less. If you already gave the site permission to use your location (on the map, with "my location"), your browser also uses it to show you nearby things first; your location is not sent anywhere. That data doesn't leave your device, except the numbers of up to 20 listings you liked, which are sent on their own, with nothing that identifies you, to find similar ones; we don't store them. You can clear your preferences from the "⋯" menu with "Clear my preferences", and everything else from your browser. To find out whether ordering things this way helps, half of the site's visitors, chosen at random, get it ordered by their preferences and the other half don't, and we compare the two in our analytics. Also, to show first what people are enjoying most, we count how many times each listing is opened, saved, added to a calendar or taken to its post: only the total per listing and per day, with nothing that identifies who did it. To avoid counting the same person twice or automated programs, we use an encrypted fingerprint of your IP address, which stays only in memory and only for that day.

9. Minors and images of people

Accounts are for people 14 and older.

We don't aim to publish photos of people: we prefer flyers and posters. If an image shows a person, especially a child or teenager, and you want us to remove it, ask through the form and it is hidden immediately.

10. Security

Data is stored in services with restricted access and encrypted connections. Access keys are not on the public site and the database is not exposed directly.

11. Changes

If we change this policy, we will publish the new version on this page with its date. See also the terms of use.