legal
privacy policy.
the short version.
- let's is made by LOCALLY TRAVEL S.R.L., a company based in Rome. We decide how your data is used, and we answer for it.
- We collect what the app needs to work: your email, your first name, a profile photo and a short bio, the events you go to, what you write in event chats, your answers to the questionnaire after an event, your circle and the people you block. Your photo and bio are seen by signed-in members, so people can recognise each other. Your gender, if you give it, is never shown to anyone.
- Your phone number is optional. We use it only to send you the invitation to the WhatsApp community group, and other members never see it.
- No advertising, no tracking across other apps or websites, and we never sell your data.
- Chat messages are deleted 30 days after the chat closes. Reports are deleted 12 months after they are closed. Your account data stays until you delete the account.
- You can delete your account from the app at any time, and it happens straight away. Without the app, ask from the deletion page. If your account is suspended and you can't sign in, ask for deletion there too.
- This website uses no cookies and no analytics.
- If you join the launch list, we use your email only to write to you about the launch of let's in Rome, and you can leave the list at any time.
- Questions: office@travelocally.com.
who we are.
LOCALLY TRAVEL S.R.L., Via Ostriana 12, 00199 Roma (RM), Italy, VAT number (P.IVA) IT18198841001, is the data controller for let's, both the app and this website. Contact: office@travelocally.com.
what we collect, and why.
- Email and password. To create your account and keep it secure, through Firebase Authentication. We never see your password. We also use your email to check that it's yours and to reset your password when you ask.
- First name. Shown to people going to the same events as you, in the chats you share with them, and to your circle. We do not collect or show a surname. Your profile is seen only by signed-in members of let's.
- Profile photo. A clear, accurate photo featuring your face, required when you complete your profile. You pick it from your photo library; the app resizes it to a 512-pixel JPEG and we keep it in our storage in the European Union. Every signed-in member can see it wherever you appear: who's-going lists, event chats, circles and your profile. It's there so people can recognise each other and get a sense of who they are going to meet.
- Short bio. Required, from 30 to 90 characters, written by you. It's seen in the same places as your photo, for the same reason: understanding who someone is before meeting them.
- Phone number, if you give it. Optional. At sign-up the app asks for it, in international format, to send you the invitation to the WhatsApp community group. We keep it apart from your profile: other members never see it, and only the administrator of the editorial team can read it. We use it only to send that one invitation. You can remove it from Settings at any time. Joining the WhatsApp group is up to you and happens outside the app, under WhatsApp's (Meta) own terms and privacy policy.
- Gender. One of four answers, including “prefer not to say”. It is never shown: not on your profile, not in any list, and not to the moderation team. We only use it to count, for example how many women and how many men go to events each month, so we can check that events stay safe and balanced. Those counts never identify anyone.
- Language. To show the app, the editions and the notifications in Italian or English.
- Your agenda. The events you are going to and have been to. Needed for the limit of 3 spots in any 14 days, the event chats and your circle.
- Messages in event chats. What you write in the chat of an event you're going to. Only the people going to that event can read it.
- Your circle. Your connections and connection requests. A connection starts after an event you both went to, or from a personal invite that was accepted. A connection sees which events you have been to and are going to.
- People you block. We keep the list so the app can apply your blocks: a blocked person no longer appears in your who's-going lists, their messages in chats you share are hidden from you (you see “message from someone you blocked”), and any connection between you ends. You can see and unblock them from Settings, under “blocked people”. Blocking hides them from you, not you from them: if you're both going to the same event, they can still see you among the people going and read your messages in its chat. To keep your distance from someone, you can also give up your spot, leave the chat or report them: at times, reporting them and choosing another of our events may be the best option. Blocking alone does not notify us. When you block someone, the app asks whether you also want to report them; you can say no and the block still happens.
- Answers to the questionnaire after an event. If you held a spot, the event chat offers you a short questionnaire from when the event ends and for 7 days: were you there (yes or no), how was it (1 to 4), would you do it again (yes, maybe or no), and a note if you want. One answer per event, and it can't be changed. Only you and the editorial team see it, never other members or the organisers. We use it to choose better events.
- Personal invites. If you use “invite someone to let's”, we create a personal link: a random code that contains no data about you. We keep who created the link, when, when it expires (after 7 days) and, if it's used, who used it and when. We use this only to create the connection between you and the person who opens the link and accepts. Before deciding, in the app, that person sees your photo, first name and bio, the same as on your profile. The website page that opens the link doesn't show who sent it. We don't use outside services to track links, and we don't collect device data. Link data is deleted at most 14 days after it's created, and straight away if you delete your account. The connection that results stays until either of you removes it, like any connection, and records that it started from an invite.
- Inviting a connection to an event. Before an event starts, you can invite someone in your circle to come along. We keep a record of who sent the invite, to whom, and for which event. We use it to send the person a notification and to show the event at the top of their Home, with “X invites you”. An invite carries no message, only the event. You can invite each person once per event, and not at all if they have blocked you or are already going.
- Reports. When someone reports a message, we keep a copy of its text, the reasons chosen (offensive, harassment, spam) and any note you add, who reported it and who wrote it. When someone reports a person, we keep a copy of their first name, bio and profile photo as they were at that moment, the reasons chosen (offensive, harassment, spam, profile picture doesn't match) and any note you add, who reported them and the person reported. The moderation team uses them to review the report. We may write to you at your account email to learn more.
- Answers when you leave a connection. When you remove someone from your circle, the app asks why, with three set answers. The answer is never shown or notified to the other person, and the moderation team never sees who gave it: it only sees how many different people answered “they made me uncomfortable” about the same person (see automated decisions).
- Age and terms. That you confirmed you are 18 or over, and the date and version of the terms you accepted.
- Account status. Whether the moderation team has suspended your account. This can follow reports, answers of “they made me uncomfortable” given by people leaving a connection with you, or a profile photo that doesn't follow our rules.
- Your phone, for notifications. A notification token, a random identifier for this installation of the app, the kind of phone (iPhone or Android) and its language. Used only for the notifications let's sends: the chat of an event you're going to has opened (5 days before the event); someone asked to connect; someone accepted your request; an event you hold a spot for was cancelled, or changed time or place; a connection invited you to an event; a reminder the day before your event.
- Your notification choices. Two notifications are optional and arrive only if you say yes: the daily edition at 8:00 (once a day, when the Home updates) and special events chosen by the editorial team (at most 3 a month). We keep these two choices with your account, as the preferences “edition” and “roundup”. You can switch either off at any time from Settings. We never send notifications only to bring you back to the app.
- Crash reports. When the app crashes, a technical report through Sentry, without your name, your email or your messages.
The app asks for access to your photo library only to let you pick your profile photo. It does not ask for your location, your contacts, your camera or your microphone.
legal basis.
We process your data:
- to perform our contract with you: running the app, your profile with its photo and bio, the events, the chats, your circle and invitations (Article 6(1)(b) GDPR);
- on the basis of your consent: your phone number, for the invitation to the WhatsApp community group, and the two optional notifications, the daily edition and special events. You can withdraw it at any time by removing the number or switching the notifications off from Settings (Article 6(1)(a) GDPR);
- to comply with legal obligations, for example when you exercise your rights (Article 6(1)(c) GDPR);
- on the basis of our legitimate interest in keeping the community safe and the service working: moderation, reports, discomfort signals, suspensions, crash reports and protecting the website forms from abuse; and in choosing better events, through the questionnaire after an event (Article 6(1)(f) GDPR).
Where the law requires your consent, we ask for it.
who processes your data on our behalf.
We use the following providers as data processors:
- Google Firebase / Google Cloud: Firebase Authentication for your login; the Firestore database (Europe, multi-region eur3); cloud functions and storage of event photos and profile photos (europe-west1, Belgium); Firebase Hosting, which serves this website.
- Expo: sends push notifications on our behalf; it receives your notification token and the text of the notification. Expo's infrastructure is in the United States.
- Apple and Google: deliver push notifications to your phone through their own notification services.
- Sentry: receives crash reports, without your name, your email or your messages.
- Our email provider: handles the messages you send to office@travelocally.com and our replies.
Inside the company, only the people on the editorial team who need your data can see it, each according to their role (see security).
We do not run advertising, we do not sell your data, and we do not track you across other apps or websites.
international transfers.
Our database, our cloud functions and the storage of event photos and profile photos are in the European Union. Sending push notifications through Expo involves a transfer of the notification token and text to the United States.
If you give your phone number, the administrator of the editorial team uses it on WhatsApp, a service of Meta, to send you the invitation to the community group. Once you join the group, WhatsApp handles your data under its own terms and privacy policy, not ours.
how long we keep your data.
| what | how long |
|---|---|
| Your account: profile, first name, profile photo, bio, gender, language, agenda, circle, blocks, notification choices | Until you delete the account. |
| Phone number | Until you remove it from Settings or delete the account. |
| Answers to the questionnaire after an event | Until you delete the account. |
| Invitations | Until you delete the account. |
| Personal invite links | At most 14 days after they are created, then deleted. |
| Notification tokens | Until you sign out, delete the account, or the phone stops accepting notifications. |
| Messages in event chats | 30 days after the chat closes, then deleted. |
| Reports and discomfort signals | 12 months after they are closed, then deleted. |
| Answers given when leaving a connection | 12 months after they are given, then deleted. |
| Requests sent through the forms on this website | 12 months from when they are sent, whatever their outcome, then deleted. |
| Anti-abuse counters of the forms (IP fingerprint) | At most 1 day. |
| Launch list (email, language, phone type, where you came from, consent) | Until you leave the list, and at most 12 months from your last sign-up, then deleted. |
| Crash reports | Per Sentry's standard retention, without your name, your email or your messages. |
Reports and discomfort signals that are still open are kept until the moderation team closes them.
If your account is suspended and you can't sign in, you can ask for deletion at the deletion page.
deleting your account.
From the app. Profile → Settings → delete account. The deletion is immediate.
Without the app. Use the form on the deletion page. If your account is suspended and you can't sign in, ask for deletion there too. Anyone can type an email address, so we first write to that address to check that the request really comes from you. Once you reply, we delete the account within 30 days.
Either way, these are removed straight away:
- your profile: first name, profile photo, bio, gender, language, age confirmation, terms acceptance and notification choices;
- your phone number;
- your answers to the questionnaires after events;
- the invitations you sent and received, and the personal invite links you created or used;
- your circle: connections and connection requests;
- your agenda, and your place in the who's-going lists of every event, past ones included;
- your spots in future events, which become free for others;
- the people you blocked;
- the notification tokens of your phones;
- your login: email and password.
These stay for a while, then are deleted:
- messages you wrote stay in the chats, shown as sent by “someone who left”, until the chat is deleted, 30 days after it closes;
- reports and discomfort signals that you made or that concern you stay for 12 months after they are closed, and answers you gave when leaving a connection for 12 months after you gave them;
- if you asked from the website, the deletion request itself stays for 12 months.
Deleting the app from your phone does not delete your account.
data on your phone.
The app keeps a few things in its own storage on your phone:
- your login session, so you stay signed in from one launch to the next;
- the language you picked;
- a random identifier for this installation, which links your phone to its notification token, and whether the app has already asked you to allow notifications;
- the connection requests you put aside with “not now”, which stay only on this phone and never reach us;
- copies of event photos, so they load faster.
None of this is used for advertising or tracking. Signing out ends the session and stops notifications on that phone. Deleting the app removes all of it.
this website.
This website uses no cookies, no analytics and no advertising, and loads no fonts or scripts from other companies: the fonts are served by the site itself.
The site is hosted on Firebase Hosting (Google). Like any web server, it processes your IP address to deliver the pages to you.
The two forms, on the contact page and on the deletion page, collect:
- your email address;
- your name, if you give it;
- your message (required for contact, optional for deletion);
- the topic you pick (contact form only);
- the language of the page you used.
To stop abuse, we limit how many requests can be sent from the same connection in an hour. For this we keep a fingerprint of your IP address, never the address itself. The fingerprint is a keyed hash: under the GDPR it is pseudonymised data, not anonymous data, and we treat it as personal data. The hourly counter it feeds is deleted within a day. The fingerprint is also stored with your request and is deleted with it. A keyed fingerprint of your email address feeds an hourly counter too, and it is deleted within a day.
Form requests are kept 12 months from when they are sent, whatever their outcome, then deleted. Only the people on the editorial team who handle requests can read them.
We use what you send only to reply to you and to handle your request. The legal basis is taking the steps you ask of us, before or under a contract, and our legitimate interest in answering the people who write to us; for a deletion request, also our legal obligation to act on your rights.
the launch list.
On the launch list page you can leave your email so we can write to you the day let's opens in Rome. We collect:
- your email address;
- the type of phone you have (iPhone or Android), if you tell us;
- the language of the page you used;
- how you reached the page: the campaign tags in the link you followed (for example “utm_source=instagram”) and the website that sent you, as a domain name only (for example instagram.com), never the full address;
- that you ticked the consent box, when, and which version of the text you agreed to.
We use your email only to write to you about the launch of let's in Rome. We don't share it, sell it or use it for anything else. The legal basis is your consent (Article 6(1)(a) GDPR), which you give by ticking the box. You can withdraw it at any time: use the unsubscribe link in any email we send, write to office@travelocally.com or use the contact form, and we remove you from the list. Signing up again with the same email doesn't create a second entry: it updates the one we have.
To stop abuse, we limit how many sign-ups can come from the same connection in an hour, with a fingerprint of your IP address as for the forms above. The fingerprint is not stored with your sign-up, and its hourly counter is deleted within a day.
We keep your sign-up until you leave the list, and at most 12 months from your last sign-up, then we delete it. Only the people on the team who run the launch can read the list.
security.
- Data travels encrypted (HTTPS/TLS) between the app, this website and our servers.
- Passwords are handled by Firebase Authentication: we never see them and never store them.
- Firestore security rules decide who can read and write each piece of data. For example: only the people going to an event can read its chat; only your connections can see your agenda; only the administrator of the editorial team can read your phone number; only you and the editorial team can see your answers to the questionnaire; only the moderation team can read reports; no one, the moderation team included, can see who gave an answer when leaving a connection.
- Access for the editorial team is limited by role: editors manage events, the moderation team handles reports and requests. Roles are assigned by the company, never from the app.
- You need to confirm your email before you can take spots, write in chats or connect.
No system is perfectly secure. If a breach puts your data at risk, we will notify the Garante and, where the law requires it, you.
automated decisions.
let's makes no decisions about you based solely on automated processing that have legal or similarly significant effects.
The only automatic step is this: when three different people answer “they made me uncomfortable” about the same person, the case goes to the moderation queue. The system does nothing else on its own. A person on the moderation team reviews the case and decides whether to act, up to suspending the account. The moderation team sees how many people answered, never who.
minors.
let's is only for people aged 18 or over, because it's about meeting people you don't know, in person. Everyone confirms their age when signing up. If we find out that an account belongs to someone under 18, we delete it. If you think a minor is using let's, write to office@travelocally.com.
your rights.
Under the GDPR, you have the right to access your data, to have it corrected or erased, to restrict or object to certain processing, and to receive a copy of it in a portable format. Where we rely on your consent, you can withdraw it at any time. To exercise any of these rights, write to office@travelocally.com or use the contact form. We reply within one month.
You also have the right to lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali.
changes to this policy.
We may update this policy from time to time. The date it came into force is shown at the top of this page. When a change matters, the app asks you to accept the new version.
contact.
The data controller is:
LOCALLY TRAVEL S.R.L., Via Ostriana 12, 00199 Roma (RM), Italy. VAT number (P.IVA) IT18198841001. Email: office@travelocally.com.You can also write to us through the contact form.
If you think we have not respected your rights, you can complain to the Garante per la protezione dei dati personali, the Italian data protection authority: www.garanteprivacy.it.