Privacy policy

This policy explains what personal data we process when you visit aneddo.com or join the Aneddo waitlist, why, and what rights you have. It is written under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR) and the Italian Privacy Code (Legislative Decree 196/2003). Part B covers the Aneddo app (beta): how it uses your location, the microphone and the little data that reaches us.

1. Who is responsible for your data

We have not appointed a Data Protection Officer because the law does not require one for our activity. For anything about your data, write to ciao@aneddo.com.

2. What data we collect

When you join the waitlist

Pressing "Get the pass" does not buy anything. It only records that you are interested in the pass, so we can tell you when it is available.

When you browse the site

Like any website, our hosting provider receives technical data needed to deliver pages and protect the site: IP address, browser and device type, requested page, date and time. We do not use advertising or profiling cookies and we do not load third-party trackers. See the cookie policy.

The voice demo on the home page plays a pre-recorded audio file from our own site. It does not use your microphone.

When you write to us

Your email address, name if you give it, and whatever you choose to write.

We do not collect your location on this website. Please do not send us special categories of data (health, religion and so on).

3. Why we use it and on what legal basis

Giving us your email is optional, but without it we cannot put you on the waitlist. We will not send you marketing about anything other than Aneddo, we do not sell or rent your data and we do not make decisions about you based solely on automated processing.

4. Who processes it for us

Your data is handled only by us and by providers that process it on our behalf under a data processing agreement (art. 28 GDPR):

The full, current list of processors is available on request. We may disclose data to public authorities when the law requires it.

5. Transfers outside the EU

Cloudflare may process data in the United States and in other countries where it operates. Cloudflare, Inc. is certified under the EU-US Data Privacy Framework, which the European Commission has recognised as providing adequate protection (art. 45 GDPR), and its data processing agreement also includes the Commission's Standard Contractual Clauses (art. 46 GDPR). You can ask us for a copy of the relevant safeguards.

6. How long we keep it

7. Your rights

At any time and free of charge you can ask us to:

You can withdraw your consent at any time, for example with the unsubscribe link in every email or by writing to us. This does not affect what we did before you withdrew it.

Write to ciao@aneddo.com or protek.talevi@pec.it. We reply within one month. If you think we are handling your data unlawfully, you can complain to the Italian supervisory authority, the Garante per la protezione dei dati personali, or to the authority of the EU country where you live or work.

8. Age

The waitlist and the beta are for people aged 18 or over. If you are under 18, please do not sign up. If we learn that we have a minor's data, we delete it.

9. Security

The site is served only over HTTPS. The waitlist is stored in a database that only we can access, protected by strong authentication. No system is perfectly secure, so if a breach ever affects your data we will tell you and the Garante as the law requires.

10. Changes

We will update this page if what we do with data changes, and change the date at the top. If a change is significant we will tell waitlist members by email before it applies.

This part covers the Aneddo app for iPhone and Apple Watch during the beta. The controller is the one named in section 1. Sections 7 (rights), 9 (security) and 10 (changes) also apply.

B1. Your coordinates and route stay on your phone

B2. Account

On first launch the app creates an anonymous account (Google's Firebase Authentication), with no name, email or phone number. It makes the app work and manages your pass. We also use Firebase App Check to verify that requests really come from the app. Legal basis: performing the service (Art. 6(1)(b)) and our legitimate interest in security (Art. 6(1)(f)).

B3. Talking to the guide (microphone)

Legal basis: performing the service (Art. 6(1)(b)).

B4. Anonymous statistics (only if you say yes)

At the start we ask whether you want to share anonymous statistics: the choice is not pre-selected and you can change it any time in the app's settings. If you say yes we send usage events (screens opened, stories played and how far, walk length, GPS quality and battery use in ranges, ratings) and, when the guide can't answer, the text of the question with obvious personal details removed: it helps us improve the content, only the people who edit content can see it, and we delete it after 12 months. Events are tied to a random installation ID you can reset. No advertising identifiers, no tracking across apps or websites, never coordinates or routes, and we don't store your IP address. We keep them for 13 months. Legal basis: consent (Art. 6(1)(a)), which you can withdraw at any time.

Whatever you choose here, we always count your minutes of conversation with the guide and your purchases, linked to your anonymous account: they make the pass and its limits work (see B3), not statistics. Legal basis: performance of the service (Art. 6(1)(b)).

B5. Crash reports

If the app crashes, or hits an error it can handle, we send a technical report to Firebase Crashlytics (Google): phone model, iOS version and where in the code the error happened. The report does not include your location. It is on by default and you can turn it off in settings. Legal basis: our legitimate interest in an app that works (Art. 6(1)(f)).

B6. Feedback, support and purchases

B7. App providers

Besides Cloudflare (network and city-pack delivery): Google (Firebase Authentication, App Check, Crashlytics, Gemini API, Places API), Railway (app server and database, in the EU), Apple (on-device speech recognition, Apple Maps, purchases), Wikimedia (Wikipedia, Wikidata), Resend (service emails, in the EU) and, once passes exist, RevenueCat and Stripe. When data leaves the EU the transfer is covered by the EU-US Data Privacy Framework or the Standard Contractual Clauses.

B8. Retention, deletion and age