Sherlane is an app for planning public-transport trips, seeing live departures on a map and keeping your tickets in one place.
This page says what data the app and its servers handle, why, for how long, and what you can do about it. It describes what the
software does today.
Write to this address with any question about your data, to ask for a copy, or to delete your account.
In short
You can use Sherlane as a guest, without an account: the map, live departures, trip planning, saved trips, favourite stops
and tickets you type in by hand. A guest’s trips, favourite stops and tickets stay on the phone and are not stored on
Sherlane’s servers.
An account is needed to read a ticket from a photo or a file, because Sherlane’s server reads it. With an account your trips,
favourite stops and tickets are also kept on the server, so you have them on another phone. When you sign in, the app moves a
guest’s favourite stops into your account, and asks before it moves trips and tickets.
If you allow it, a ticket from a photo, a PDF or an email that Sherlane’s software cannot read exactly is also read by an AI
service, Claude by Anthropic. The app asks you once, and you can change the answer in Profile.
Sherlane does not store the IP address or the device of a sign-in. An address is read in memory only, to slow down abuse,
and is not saved.
Your location is used on your phone. It leaves the phone only as the starting point of a route the app plans for you (a
trip you plan from “my location”, or a new route the app looks for when a trip you follow breaks), and as the map area you
are looking at, to show stops and vehicles and to search.
Ads are shown by Google AdMob. Where the law requires it, you are asked for your consent first.
If the app closes unexpectedly it offers to send a crash report. Nothing is sent unless you press Send.
Your email address, your name and a password. The password is stored only as a one-way hash, so nobody can read it. If you
sign in with Google: the email address and name of your Google account and Google’s identifier for it. Sherlane never
receives your Google password. The time of your last sign-in.
Why
To create your account and sign you in (providing the service you asked for).
How long
Until you delete your account.
Staying signed in, and the security log
What
When you sign in, the app receives a long random token that keeps you signed in. The server keeps only a one-way hash of it,
with its dates. A security log records events such as registering, signing in, a failed sign-in, a password change and
signing out, each with your account’s id and the time. Neither holds an IP address, a device name or a browser identifier:
Sherlane does not store them.
Why
To keep you signed in, to notice a stolen sign-in and to investigate abuse (the security of the service).
How long
Expired sign-in tokens are not removed automatically; they hold a hash and dates only, and are deleted with your account.
The security log has no automatic end. After you delete your account its entries stay, attached to the blank account record
described under Deleting your account: an id and a time, nothing else.
Settings and favourite stops
What
Your choices for theme, language, notifications and map style, and the stops you marked as favourites (the stop’s id and
name).
Why
So they follow you to another phone when you sign in.
How long
Until you remove them or delete your account.
As a guest, your favourite stops stay on your phone and are not stored on the server. The ids of the stops you star do travel in
the address of the map page (see “The map, searching and planning”).
Saved trips
What
The trips you save: the name you gave, your notes, the dates, and each leg with its start and end places (names and
coordinates, which can be your own location if you planned from “my location”), the operator and a price estimate.
For a trip saved from the map, each leg also keeps its route line, the stops between its ends and the train number, so
the map can draw the trip as it was.
Why
To show your trips on every phone you sign in on, and to remind you of them.
How long
Until you delete the trip or your account.
As a guest, the trips you save stay on your phone and are not stored on the server.
On your phone the app also keeps the trip you are following, its reminders and a history of past trips, with the places
involved. That stays on the phone. It is removed when you delete your account in the app, or when you uninstall the app.
Tickets you import
What
You can add a ticket by photo, by a file (PDF, wallet pass, calendar entry, an email you saved) or by hand. The server stores
the file exactly as you sent it. That file can show your name and other personal details, and a saved email
carries its header lines, with addresses. It also stores what the app read from it: the stations, the operator, the price,
the validity times and the ticket’s code (QR code or barcode) with a picture of the code. A ticket’s code works like the
ticket itself: whoever holds it can travel. If you allowed the AI reading (below), the AI
service’s reading of the ticket is kept with the upload too: its name, route, stations, operator, price, validity and times,
each with the short piece of printed text it was read from.
Why
To show your ticket and its code in the app, on every phone you sign in on. The file is read by Sherlane’s own software. It is sent to an AI
service only if you allowed it and the software cannot read it exactly (see below). The legal basis for the AI reading is your
consent, which you can withdraw at any time in Profile.
How long
The original file and the picture of the code are deleted 30 days after the ticket has ended (used or expired), and
immediately when you delete the ticket in the app. A ticket with no end date keeps its file until you delete the
ticket. A file you uploaded but never turned into a ticket is deleted after 24 hours, with any AI reading of it. The AI reading of a
ticket is removed when you save the ticket. The ticket’s details (stations,
operator, price, times and code), without the file, stay with your account until you delete your account.
Reading a ticket from a photo or a file needs an account. As a guest you can type a ticket in by hand; it stays on your phone
and is not stored on the server. On your phone, tickets and their codes are stored encrypted.
The AI reading, if you allow it. When you first add a photo or a file, the app asks whether an AI service may
read the tickets that Sherlane’s software cannot read exactly. If you say yes, the software sends the service a copy of the photo
(made smaller), the PDF, or an email’s subject, its sender’s name, its text and up to three of its photos or PDFs. The service,
Claude by Anthropic, reads the ticket’s printed details and sends them back, and you check every field before you save the
ticket. Under its commercial terms, Anthropic may not train its models on this data. It deletes the data within 30 days, or keeps
it for up to 2 years if its safety systems flag it. Anthropic is a company in the United States. Its data processing addendum
includes the EU Standard Contractual Clauses for data that leaves the EU. The AI is not used when the software reads the ticket
exactly (from an airline or rail code, a wallet pass, a calendar entry or the booking details in an email), when a file has more
than one code, when a PDF has more than 10 pages, or when a photo is in HEIC format. If you say no, nothing is sent, and the ticket
is read as it always was. You can change your answer in Profile at any time. After that, no file is sent to the AI service.
Your location
What
The app asks for permission to use your location, for the “you are here” dot on the map, to start a trip from “my location”
and, only if you choose to watch a journey, to see how far you are from your stop while the app is closed (a notification is
shown while it does). The app does not use background location permission.
Where it goes
Your location is processed on your phone. It leaves the phone in two cases. First, as the start point when you plan a trip
from “my location”, and when the app looks for an alternative connection for a journey you are watching: it goes to Sherlane’s
routing server to calculate the route and is not stored there. Second, as part of the map area you are looking at: searches for
stops and addresses send the position of the centre of the map, to five decimal places (about one metre), to rank the
results, and the map’s own requests for stops, bikes and vehicles send the centre or the corners of the area, rounded to
about a kilometre. If you save a trip, its places are stored with it
(see Saved trips).
Why
To show where you are and plan from there (your consent, given through the permission; you can withdraw it in your phone’s
settings).
The map, searching and planning
What
The map picture is loaded straight from OpenFreeMap, so OpenFreeMap sees your phone’s IP address and which part of the map
you view, as any web server would. If you download offline maps, the files come from Sherlane’s storage on Microsoft Azure
through a temporary link.
The address of the map page carries the ids of the stops you star and, after “Show alternatives”, the start and end of the
route. Sherlane’s map server does not write these to its own logs; like any web host, the hosting service sees the address of
each request.
When you search for an address or a place, the text you typed, the country and the centre of the map go to Sherlane’s servers, which look it up on Sherlane’s own routing server (OpenStreetMap data). They are not sent to anyone else.
Why
To show the map, find places and plan trips.
How long
Searches and plans are not stored with your account. A place you pick from a search is counted without your account, as
described under “What search learns from your picks”.
Prices
What
To price a trip, the server may look up public prices on an operator’s own website (for example HŽPP or FlixBus). It sends
only the stations or cities and the date. No personal data goes to them.
Messages you send
What
Feedback from the feedback screen: your message (up to 4000 characters), an optional subject, an optional
email address for a reply (the app can fill in your account’s address), the category, the app version and the platform.
Reports about map data (a wrong time, a missing stop): the message, an optional link, an optional email
address, the app version, the platform and the station you reported. Crash reports: if the app closed
unexpectedly, the next time it starts it asks whether to send a report. You can read the exact text first. If you press
Send it goes in as feedback in the category “Crash”, with no email address. It holds the type, message and technical trace of
the error, the app version and build, the Android version, the time, and the last few failures the app recorded (for each:
where in the app it happened, a short technical description, the type of the error, an error code, a server reference and
the time). Before the report is made, web addresses are cut down to the site’s name, and email addresses, coordinates, file
paths and identifiers are taken out. If you press Don’t send, it is deleted. If you close the question without answering,
the report is kept and the app asks again the next time it starts.
Survey answers: if you answer the one-question survey on the Home screen, your score (1 to 5), an optional
comment (up to 1000 characters), the survey’s name, the app version and the platform. They are sent as feedback in the category
“Survey”, with no email address and no account, so they are not tied to you. The survey comes back at most every 120 days, and
“Don’t ask again” stops it. Ratings: on a Google Play install the app may ask Google Play to show its rating
prompt. What you rate or write there is Google’s; Sherlane receives nothing from it.
Why
To fix problems and answer you.
How long
Until they have been dealt with and removed. There is no automatic deletion. They are not tied to your account except by an
email address you chose to include.
Android’s own crash and freeze reports for apps are collected by Google, if you have chosen to share diagnostics with Google.
That is Google’s collection, not Sherlane’s.
Feedback and reports about map data are read once a week
by an AI service, Anthropic, to sort them by subject and kind and to group them. Before anything is sent, email addresses,
phone numbers and web links are removed from the text, and the app version, the platform and your email address are not
sent. A name written in the text is not removed. The AI only suggests a subject, a kind and which part of Sherlane a report
belongs to: it does not change a timetable or a price, and I check its suggestions. This runs only once AI is switched on
for these reports.
Checking that the app is genuine
What
Before the map and live data are shown, the app proves to the map server that it is the genuine app. It sends a random
install number that the app makes up on your phone (it is not your advertising id or any device identifier) and a one-time
proof from Google Play Integrity, which the server checks with Google. The server answers with a short session (24 hours).
The in-app map keeps that session in a cookie named gt_app, which is needed for the map to work. Nothing is stored
in a database.
Why
To keep the map data for the people the app is for, and to stop abuse.
How long
The server’s log records the session’s number, the result and a short fingerprint of the install number, for up to 3 days.
Ads
What
The app shows ads from Google AdMob. Google may use your phone’s advertising id and other data its software collects, as
described in Google’s policy. Where the law requires it, a Google consent form asks for your choice first (personalised or
not), and the app offers it again from its privacy options. You can reset or delete your advertising id in your phone’s
Android settings (under Privacy, then Ads; the exact place depends on your phone).
Why
Ads are how the app is paid for. Your choice in the consent form is respected.
Counts of how well tickets were read
What
When a ticket file is read, the server counts which reader worked, which field it found and whether you changed it, with
the operator’s name. These counts hold no account, no ticket content and no file. The daily counts of AI readings hold none either: how many readings
ended, why, and by file type. A change you make to a field the AI read is counted with the operator’s name, as the other changes are.
How long
The reader counts are deleted after 180 days. The daily counts of AI readings belong to no one and are not deleted automatically.
What search learns from your picks
What
When you pick a place from a search, Sherlane counts the text you typed and the place you chose. Up to two texts you typed
earlier in the same search box are counted too. Nothing about you is kept with the count: no account, device, session, IP
address or position. A text with a number, an email address, a phone number or a link is not counted, and an address is never counted.
Why
To make search find places by the words riders use.
How long
A text is deleted after 30 days without a pick, unless its place was picked on five different days. Then it stays until 12
months after its last pick. A text the owner has removed or blocked is kept, so that the decision holds.
IP addresses and logs
What
A server must read the IP address of whoever connects. Sherlane uses it in memory only, to limit how fast one caller can
make requests, and does not write it to its database or its logs. In particular a sign-in does not store it. The server for
accounts and tickets keeps no log files. The map server keeps its application logs for up to 3 days. They hold technical events:
errors, counts and the app-session lines described above. They hold no
name, email address or password.
Hosting
Like any host, Microsoft Azure handles the network traffic to the servers.
Who receives data
Microsoft Azure. The accounts and tickets server and its database run on Azure in the Italy North region.
The map server uses Azure Blob Storage for offline map files.
Google. Sign in with Google, Play Integrity, AdMob and its consent form, and Google Play’s in-app updates.
Google acts under its own privacy policy.
Anthropic (the Claude AI service). Once a week it receives the text of feedback and map reports, with email
addresses, phone numbers and links removed, to sort and group them. If you allowed the AI reading of tickets, it also receives the photo, PDF or email of each ticket that
Sherlane’s software could not read exactly (see “Tickets you import”). Anthropic processes all of this for Sherlane under its Data
Processing Addendum, and does not train its models on it.
OpenFreeMap. Map pictures, as described above.
Operators’ public websites (for example HŽPP, FlixBus): price lookups with stations and date only.
Route planning runs on Sherlane’s own routing server, not with a third party. Sherlane does not sell your data. The app contains
no analytics or tracking software. Apart from Sherlane’s own servers and storage, the app itself contacts only the Google services
named above and OpenFreeMap (map pictures).
Deleting your account
You can delete your account in the app (Profile, then Account, then Delete account) or by email. The steps are on
this page. In the app it takes effect at once. By email it is done within 30 days.
What deleting removes: your name, email address, password and sign-in methods; your saved trips, favourite
stops and settings; your sign-in tokens; all your imported tickets and uploads, with their files, codes and AI readings; your answer to the question whether an AI service
may read your tickets; and your email address
from feedback messages that carry it.
What it keeps:
The account record itself stays as an empty placeholder with a made-up address (deleted-…@deleted.invalid), no
name and no way to sign in. Nothing in it identifies you. The same email address or Google account can register again as a new,
empty account.
The wallet, purchase and ticket records belonging to that placeholder, never with a name or an email address. They are
bookkeeping records. Nothing can be bought in the app today, so there is nothing to keep but the empty wallet.
The security log entries (an id and a time).
The text of feedback and map reports. An email address you typed into a map report stays until you ask me to remove it.
The counts of how well tickets were read, and the daily counts of AI readings, which belong to no one.
Data that Google holds under its own policy (for example advertising data) is not removed by deleting your Sherlane account.
Your rights
You have the right to ask for access to your data and a copy of it, to have it corrected or erased, to have its use restricted,
to object to it, and to receive it in a usable format. Where you gave consent (location, ads, crash reports, the AI reading of tickets) you can withdraw it at
any time, which does not affect what was done before. To use any of these rights, write to the address in
Who is responsible for your data; I answer within one month.
If you think your data is handled unlawfully, you can complain to the Croatian data-protection authority, the Agencija za
zaštitu osobnih podataka (azop.hr), or to the authority in the country where you live.
Children
Sherlane is for people aged 16 or over. It is not meant for anyone younger, and an account should not be created for them.
Security
The app and the servers talk over encrypted connections only. Passwords and sign-in tokens are stored as hashes. Tickets and their
codes are stored encrypted on your phone. Android’s automatic backup may carry some app settings; saved tickets, ticket codes,
trips and favourite stops are excluded from it.
Changes to this page
The date at the top shows when this page was last changed. It always describes what the software does at that date.