Privacy

Who handles the data

The data controller is the owner of the site, whose details (business name, VAT number, tax code and REA number) are in the image below. For any question about privacy write to info@fribbynetwork.net.

This site

The pages contain no analytics tools, no tracking cookies and no third-party resources. Your theme choice stays in your browser and is sent to nobody; the language lives in the address. The cookies, technical ones only, are explained on the Cookies page.

Like every website, the web server logs the requests it receives: IP address, date and time, page requested, referring page, browser type and result. They are used for security and to troubleshoot problems. Access logs are deleted after 90 days, error logs after 30 and the log of suspicious requests, which the server uses to stop attacks, after 14.

From the logs we only work out totals: how many visits, from which countries, on which devices, where they come from and which pages are viewed most. The country is worked out from the IP address with a database stored on our server (GeoLite2). Nothing in the counts can be traced back to a person.

The site is part of Fribbynetwork, a network of sites that defends itself from attacks with IPselfie, a service of ours: addresses that attack one of the sites stay there for up to 90 days after the last event, and those who keep trying can be blocked. Ordinary visitors never end up on that list.

Legal basis for logs and protection: legitimate interest in the security of the site (GDPR art. 6.1.f).

The Fribbynetwork account

The account is optional: it is only needed to use our trip server. It is the same for every site of the network and it is managed by the Fribbynetwork portal, which keeps:

• your email address, which is also the name you sign in with;
• your display name and language;
• your confirmation of being old enough to use online services (14 in Italy);
• your password, stored so that nobody can read it, not even us;
• two-step verification, if you turn it on;
• sign-ins, with date, time and IP address, for 90 days; date and IP address of the registration as long as the account exists.

All the details, with retention times, are in the portal's privacy notice (account.fribbynetwork.net/privacy).

Legal basis: the service you ask for by registering (art. 6.1.b); for sign-ins our legitimate interest in account security (art. 6.1.f).

What this site receives

When you sign in, this site receives from the portal and keeps: the account code (an identifier that says nothing about you), the name you chose, your language, the rights that come from your subscriptions, your choice about the thank-you notes in place of ads, the date of your first sign-in and of your last one.

It also receives your email, inside the identity token the portal hands over at sign-in: it does not store it separately, but the token stays in our database with the session, because it lets you sign out of every site at once. It is deleted with the session: when you sign out, when you sign out of another site of the network or after 30 days.

Every hour the site asks the portal whether the account still exists and which rights it has: this way the end of a subscription also applies to phones that send trips without signing in to the site. When you delete your profile on the portal, within an hour we delete the account, devices, key and trips here too.

Legal basis: the service you ask for by signing in (art. 6.1.b).

Subscriptions and payments

Subscriptions (No ads across the network, iamhere.it PRO, Network Pass) are bought and managed on the portal. The portal keeps what you bought, when it starts and when it ends, the country you live in and, if you ask for an invoice, the invoice details. Payments are handled by Stripe: card details never reach us. Payments and invoices are kept for 10 years, as the law requires.

This site sees none of this: it only receives the right your subscription gives you (for example “no ads” or “iamhere.it PRO”), which sets limits, how long trips are kept and ads.

Legal basis: the contract (art. 6.1.b) and legal obligations (art. 6.1.c).

Our trip server

If you use it, the app encrypts the points on the phone before sending them (end-to-end encryption): only unreadable data reaches the server. The key is on your phone and we do not have it: we only keep a fingerprint that tells whether a recovery code is right, without being able to rebuild it. That is why, if you lose the key, not even we can recover the trips.

What the server sees anyway: when a trip arrives and how big it is, from which device, the start time and the IP address the data comes from, which ends up in the server logs. It needs this for the limits of your plan and for expiry dates.

For devices we keep the name you choose, when you added them and their last contact; of each device's secret code only a fingerprint.

Legal basis: the service you ask for (art. 6.1.b).

How long trips are kept

Each trip gets its deletion date when it ends, based on your plan at that moment:

• Registered: 24 hours
• No ads across the network: 7 days
• iamhere.it PRO: as long as the subscription is active, then another 14 days

During a live trip the points arrive in pieces; on arrival the whole trip replaces them. A live trip with no news for 12 hours closes by itself. You can delete a trip whenever you like, from the app or from the “Your trips” page; “I lost the key” deletes them all together with the key.

Whoever opens a shared trip

A trip link carries the key after the # sign, which the browser never sends to the server: the page downloads the encrypted data and decrypts it in the viewer's browser. Whoever has the link sees that trip and no other.

To draw the map, the viewer's browser downloads the tiles from the OpenStreetMap Foundation servers, which therefore receive their IP address, as with the demo. With a link lacking the right key the map does not open and no request goes to them.

Sharing a link means sharing roads, stops and times: send it only to people you want to see them.

The app

The app sends nothing anywhere except to the address you configure, to our server if you choose it and to the numbers you choose to text. There are no analytics and no third-party services: whoever writes the app cannot see where you go.

The update check

The app and the server can check whether a newer version has come out. It is optional and off by default, because to do it they ask GitHub for a small file, and in asking they tell it their IP address.

When on, the app checks every 7, 14 or 30 days as you choose, and the server every two weeks; both can also be asked on the spot. Nothing about you is sent, and nothing is downloaded or installed: if a new version exists they say so, and that is all.

The maps inside the app

The map is only there to pick destinations and never opens by itself: it appears when you tap Pick on the map or edit a saved point. Anyone using the app with text messages alone, or with an endpoint of their own, never contacts a map service at all.

When you do open it, the tiles come from OpenFreeMap, which therefore receives the request and sees the area you are looking at. Their policy states that they do not normally log IP addresses and may do so only temporarily in case of attacks or abuse, for no more than thirty days, deleting the logs afterwards. They may use Cloudflare as a delivery network.

If you would rather contact no external service, the map settings let you point at a style of your own: from then on the tiles come from wherever you say.

The demo

The journeys you see are generated and belong to nobody. Apart from the web server logs, the same as the site's, nothing you do in there is recorded.

The landing page shows a still image: until you pick a journey, no request leaves for the outside. Once you open a journey, your browser connects directly to the OpenStreetMap Foundation servers to fetch the tiles; from that moment your IP address reaches them.

Their policy states that they collect IP address, browser and device type, operating system, referring page, date and time. The processing rests on legitimate interest, GDPR article 6.1f. The Foundation is based in the United Kingdom. We are not an intermediary and have no control over that processing.

Who sees the data besides us

• The server provider, OVH (a French company, the server is in Germany), which hosts the machines.
• The OpenStreetMap Foundation, when you open a shared trip or the demo, for the map tiles; OpenFreeMap, when you open the map in the app.
• GitHub, only if you turn on the update check.
• For subscriptions, through the portal: Stripe for payments, Aruba for electronic invoices.
• Nobody else: we do not sell or hand over data to anyone.

Where the data lives

On our server in Germany, at OVH. Every day the machines are copied, encrypted, to our backup server in Italy and each copy is kept for at most 90 days: deleted data also disappears from the copies as they are replaced by new ones. No data leaves the European Union.

Your rights

You can ask us for access to your data, rectification, erasure, restriction of processing, portability and object to processing based on legitimate interest (arts. 15-22 GDPR). Write to the address above: we answer within a month.

Many things you can do yourself: from your account area you remove devices and delete trips; on the portal you download your data and delete your profile, which also deletes what is stored here.

If you believe the processing breaches the Regulation you can complain to the Italian supervisory authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it), or to the authority of the country where you live.

If you run the server

The data lives on your hosting and the responsibility is yours. One thing is worth keeping in mind: sharing a journey link means sharing the roads you took, where you stopped and when; over time, your home and your workplace too. A message forwarded into a group by mistake cannot be called back.