Privacy policy
As of November 9, 2026
In short
Your trips live on your phone, and there is no account. Something leaves the phone only for a feature that needs a service, and each time Tervaya opens, to ask our service whether a correction of the app is waiting and, on the iPhone, to check what your Apple Account bought. On Android, that check begins only once you have started a purchase on Google Play. Where a law requires it, Tervaya also asks your app store about your age. Each is listed below with what it carries and when. The app has no advertising and no analytics of our own. What Smart capture reads trains no AI model, ours or Microsoft's.
Who is responsible
Responsible under the GDPR is:
Dmitri Brosowski
Hermann-Beuttenmüller-Str. 10
75015 Bretten
Germany
hello@tervaya.app
Tervaya runs on your phone
Your trips, expenses and settings are stored on your phone.
There is no account and nothing to sign up for.
A Tervaya widget on your home screen shows the open trip's figure as the overview shows it, with the trip's name, its day and its days, to anyone who sees your screen. On the iPhone's Lock Screen a widget shows the figure, or before the trip when and where it begins, never the trip's name, and marks the figure as private. The iPhone hides it while locked only once you no longer allow access to Lock Screen widgets while locked, under Face ID & Passcode in its settings.
Tervaya sends what a widget shows to nobody. On the iPhone, Tervaya keeps it in a file that only Tervaya and its widgets read, and the iPhone can show a widget wherever you add it, also on your Mac or on your car's screen with CarPlay. On Android, Tervaya draws the widget as a picture that your home screen app shows. While the app lock is on, a widget shows no amount, no name and no place, only which day of the trip it is or how many travel days it has.
What leaves the device
Exchange rates
Once when the app starts, in the background.
The app asks our service in the EU for the day's rates. The request carries no trip and no amount, only the question what a currency is worth and, as every request on the internet does, the phone's IP address. Our service fetches the rates from a public rate service once a day for everybody, so the phone's address never reaches it.
Legal basis: our legitimate interest in showing amounts in your currency (Art. 6(1)(f) GDPR). Processor: Microsoft (Azure, region Germany West Central). Our service fetches the rates from ExchangeRate-API (AYR Tech (Pty) Ltd, South Africa) without any data about you.
Corrections of the app
When the app starts, also when the phone starts it in the background for a shared trip, and when you come back to it after an hour away.
The app asks our service in the EU whether there is a correction for this version of the app, and fetches it if there is. The question carries the phone's system, which version of the app it is and which correction it runs, and, as every request on the internet does, the phone's IP address. No number for this installation, no trip and no amount. Our service keeps none of it. The app runs a correction only if we signed it.
Legal basis: our legitimate interest in an app that works and stays safe (Art. 6(1)(f) GDPR). Reading which correction your phone runs, fetching a correction and keeping it on your phone needs no consent, since a correction only repairs the app you use (§ 25(2) No. 2 TDDDG). Processor: Microsoft (Azure, region Germany West Central).
Maps and place names
While a map is on screen, when a place is added to an expense, and for a place saved without a name once the phone is online again. Once you turn on “Add the place by itself”, also as soon as you start a new expense, even one you then do not save.
The part of the world a map shows, the point a place is named for, or the name of the trip's destination, to find it on the map. It goes to the phone's own map service, Google on Android and Apple on iPhone. While a map is on screen, Google's map component on Android also sends Google how the map is used, crash reports from its own code, the phone's model and system, and an identifier of its own. No trip and no amount goes with it.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). The app reads your location only at the moments named under “Permissions”, which needs no consent (§ 25(2) No. 2 TDDDG). Recipient: Google (Android) or Apple (iPhone, Apple Distribution International Limited, Ireland), directly from the phone and with your IP address, each as a controller under its own privacy policy. Google's map component also sends Google the data named above for Google's own purposes. Google LLC is certified under the EU-US Data Privacy Framework.
Place search
Only when you search for a place by name, with words you type or, from an expense's place, with its title.
On Android, the words you search for, typed or an expense's title, which for a card payment is often the shop's name as your bank or wallet wrote it. With them go the trip's country, the area to look in first, which is the box around that country or around the islands the trip goes to, the app's language and version, the phone's system and a random number for this installation, so that a monthly limit can hold. Our service in the EU passes the words, the country, the area and the language on to Google and keeps nothing but a count per month. On the iPhone, the words go from the phone straight to Apple's map service when you search, with the same area to look in first, and our service is not involved. Of an expense only its title goes, never its note, its amount, its date or who paid. On Android, the request also carries the app's proof, as described under “Proof that it is Tervaya”.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). Processor on Android: Microsoft (Azure, region Germany West Central). Recipient on Android: Google (Places API), which receives the words, the trip's country, the area to look in first and the app's language from our service under its own terms as a controller, but not your IP address. Google LLC is certified under the EU-US Data Privacy Framework. Recipient on the iPhone: Apple (Apple Distribution International Limited, Ireland), directly from the phone and with your IP address, as a controller under its own privacy policy.
Smart capture
When you speak or write a sentence in the bar or into a form, when a text you shared into Tervaya from another app opens in a form, when you scan a receipt from the plus, and when you attach a receipt to a form without an amount, also one you shared into Tervaya from another app. Never while Smart capture is switched off in Settings, and never once its free readings are used and no bought ones are left.
The recording of what you said, what you wrote or shared as text, or the receipt photo, also the picture your phone makes of a PDF's first and last page. With it go the trip's categories and currencies, today's date and the time, the app's language and version, the phone's system and a random number for this installation, so that the limits can hold, and, except with a receipt, the people's names. Our service in the EU passes it to Microsoft's Azure OpenAI in the EU, which turns a recording into words, and gives back what was read. Our service keeps none of it. Microsoft may store a request its abuse monitoring flags, in the EU, for review by its staff in the EEA, and does not say for how long. No budget and no other expense goes with it. A receipt or a shared text can hold more than the expense needs, such as a name or a phone number, part of a card number, or a pharmacy's or a doctor's line that tells of someone's health (Art. 9 GDPR), and Smart capture reads all of it. Cover such lines on a receipt before you take the photo, or attach the photo or PDF only once the expense has its amount, which keeps Smart capture from reading it. Share only the part of a text the expense needs, or switch Smart capture off in Settings before you share it. The request also carries the app's proof, as described under “Proof that it is Tervaya”.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). Processor: Microsoft (Azure OpenAI, region Sweden Central, within the EU data zone). Neither we nor Microsoft use it to train AI models.
Proof that it is Tervaya
With each Smart capture reading and, on Android, each place search. To get ready, also as soon as you allow Smart capture or switch it on and when the app starts while it is on, on Android each time and on the iPhone once per installation, and again if our service no longer accepts the key.
On Android, the app asks Google Play on your phone for a token confirming that the request comes from Tervaya as Google Play installed it, on a phone that passes Google's checks. Google Play gets a check value made from the request and the random number for this installation, not the request itself, and asks Google's servers, which also learn the app's version and signature, whether the Google account on the phone got Tervaya from Google Play, and data of the phone with which Google judges whether it is genuine. The token goes with the request to our service in the EU, which has Google read it, learns whether the app and the phone passed, which version the app is and whether Tervaya came from Google Play, and keeps none of it. On the iPhone, the app makes a key that never leaves the phone's secure chip and has Apple confirm it once. Our service in the EU receives Apple's confirmation and the key's public part, and with each reading a check value of the request signed with the key. It keeps that public part and a counter under a number it makes from this installation's number, until two years after their last use, and besides only a count per day of the requests that proved themselves and those that did not. No trip, no amount and no name goes to Google or Apple for this.
Legal basis: our legitimate interest in keeping Smart capture and the place search, which cost us money with every request, for the genuine app and safe from misuse (Art. 6(1)(f) GDPR). Asking Google Play on Android and making the key on the iPhone need no consent, since without them our service cannot provide these functions you use safely (§ 25(2) No. 2 TDDDG). Recipients: Google (Google Play) and Apple (Apple Distribution International Limited, Ireland), directly from the phone and with your IP address, each as a controller under its own privacy policy. Google also reads the token for our service. Processor: Microsoft (Azure, region Germany West Central). Google LLC is certified under the EU-US Data Privacy Framework. For now, every request is served with or without this proof. Before that changes, this page will say from when a request without it gets no free Smart capture reading and no place search. Readings you bought work without it.
Shared trips
When you make a trip's first invitation, and then on a trip you share or joined: when the app opens, a few seconds after a change, and every minute while it is open. On a trip whose notifications you switched on, also now and then in the background, when the phone lets it. Also when you open an invitation, to check that it still works, and when you keep or use a recovery code.
A shared trip's name, dates, destinations, the people's names and the shared expenses and payments. They are encrypted on your phone with the trip's key, which only its phones and its invitation links hold, so our mailbox stores them without being able to read them. Beside them, it sees random ids for the trip and each of its phones, each phone's public key, when a phone joined and when and how much it wrote, and, as with every request, the phone's IP address, which it does not keep. An invitation link carries that key with the trip's name, your name and the name of the person it is for. Send it only to that person. The organiser's recovery keys are kept there too, locked with the recovery code. Your budget, your cash, what you spend only for yourself, receipts, and how and where you paid never go into the mailbox. Everything a trip holds there is deleted 30 days after the last change anyone in the trip made. While a shared trip is under way or still ahead, one of its phones looking into the mailbox counts as a change, so the trip is not deleted while it is in use. The phone knows this from the trip's dates, which the mailbox cannot read. A closed trip counts as over, and one without an end date as under way until it is closed. For this the mailbox notes the last day one of the trip's phones looked in, not which one, and nothing else.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). Processor: Microsoft (Azure, region Germany West Central), which stores the encrypted parcels with the ids, keys and times named above and cannot read them without the trip's key.
Google Drive backup
When you fetch a backup from Drive, and once you switch Drive on in the settings, after a change, when you open the app, return to it or leave it, at most once an hour.
Your whole record as in a backup file, which receipt photo belongs to which expense, the photos themselves, also the pictures your phone made of PDFs, and your phone's name, on the iPhone its model, so that another phone can tell your backups apart, into a hidden folder of your own Google Drive that only Tervaya can open. The sign-in gives Tervaya your Google account's name and email address, which stay on your phone, and access to this folder and nothing else in your Drive. It goes from your phone to Google directly; our service is not involved.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). Recipient: Google, as the provider of your own Google Drive, under the terms between you and Google; we receive nothing. Google's sign-in also receives your IP address, from which Google may estimate roughly where the phone is, to prevent fraud. Google LLC is certified under the EU-US Data Privacy Framework.
iCloud backup
Only on the iPhone. When you fetch a backup from iCloud, and once you switch iCloud on in the settings, after a change, when you open the app, return to it or leave it, at most once an hour. Also while the first welcome is open, on a new install or after “Delete all data”, as it opens and each time you return to it, to see whether your iCloud holds backups of Tervaya. That reads only their list and writes nothing.
Your whole record as in a backup file, which receipt photo belongs to which expense, the photos themselves, also the pictures your phone made of PDFs, how many trips and expenses a backup holds, and your iPhone's model, so that another phone can tell your backups apart, into Tervaya's own place in your iCloud, which your Apple Account keeps and we cannot open. It goes from your phone to Apple directly; our service is not involved.
Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR). Recipient: Apple (Apple Distribution International Limited, Ireland), as the provider of your own iCloud, under the terms between you and Apple; we receive nothing.
Tervaya Pro and tips
On the iPhone, whether or not you bought anything: when the app starts or comes back to the front, after a purchase, when you tap “Restore purchase”, and when the App Store tells the app of a purchase or a refund made elsewhere. On Android, when the app starts or comes back to the front, after a purchase, when you tap “Restore purchase”, and when Google Play tells the app that a purchase waiting for its payment went through, but only once the phone has the id of our own that your purchases on Google Play carry. The app makes it when you first start a purchase there, and a backup, or Google Play with Pro for ever, brings it back. Also with each Smart reading once you have bought readings.
What Apple signed about this download of Tervaya and about what you bought in it: the app and its version, when it was first downloaded, a check value Apple makes from an identifier of this iPhone, and, for each purchase the App Store keeps for Tervaya, what was bought, when, its price and currency, the store's country and any refund, with the numbers Apple gives them, one of which stays the same for your Apple Account across your iPhones. With a Smart reading, only what Apple signed about the download goes along. With it goes a random number for this installation, so that the limits can hold, and, as with every request, the phone's IP address. Our service in the EU checks Apple's signature and keeps per purchase only Apple's number for it, what was bought and when, how many Smart readings it brought and how many are used, a refund, and when Apple last signed it. It files them under a number it makes from Apple's number for your Apple Account in Tervaya, with a key only it holds. If you never bought anything, it keeps nothing. Apple also tells our service directly of a purchase, a refund or its reversal. For the prices of Pro and the three tips, the phone also asks the App Store when the app starts or comes back to the front, which goes to Apple, not to us. No trip, no amount you logged and no name goes with it. On Android, the id of our own, which the app hands to Google Play with every purchase, keeps on your phone and writes into your backups, and the token Google Play gives each purchase in Tervaya that it still holds for you, which is Pro for ever and any other purchase until our service has confirmed it. With a Smart reading, only the id goes along. With it goes a random number for this installation, so that the limits can hold, and, as with every request, the phone's IP address. Our service in the EU reads each of these purchases from Google Play with an account of our own. Google tells it what was bought and when, its order number, the id it was bought with, your billing country and whether it is paid or cancelled. Our service keeps per purchase only Google's order number for it, what was bought and when, how many Smart readings it brought and how many are used, a refund, and the time of Google's latest word on it. It files them under a number it makes from the id, with a key only it holds. Beside them it keeps, for each purchase but a tip, a number it makes from the order number with that key, with what was bought and when, so that a refund finds its purchase. Once it has counted a purchase, it confirms it to Google Play, as Google requires. Each night it reads Google Play's list of the purchases of Tervaya refunded or cancelled in the last two days, and takes back those it counted. If you never bought anything, it keeps nothing. For the prices of Pro and the three tips, the country of your Google Play account and the purchases of Tervaya that Google Play holds for you, the phone also asks Google Play when the app starts or comes back to the front, which goes to Google, not to us. No trip, no amount you logged and no name goes with it. A tip goes the same way and unlocks nothing. Our service checks it only so that the App Store or Google Play stops handing it over, and keeps nothing of it.
Legal basis: giving your Apple Account what it bought on each of its iPhones, as the terms of use describe Pro, and completing a tip you leave, as they describe tips (Art. 6(1)(b) GDPR). Reading what the App Store has stored about your purchases on the iPhone needs no consent, since Pro cannot work and a tip cannot be completed without it (§ 25(2) No. 2 TDDDG). Processor: Microsoft (Azure, region Germany West Central), which stores what our service keeps. Apple handles the sale of Pro and every tip under its own terms, in the EU as Apple Distribution International Limited, Ireland, and processes your purchase as a controller under its own privacy policy. What our service keeps stays, since the App Store gives a pass and Pro for ever back to every iPhone of your Apple Account for good, and a purchase forgotten would count a second time. To learn what it keeps, or to have it deleted, send us the order ID from Apple's receipt email. After a deletion, Tervaya counts again only what the App Store still gives back, Pro for ever and your latest pass, each with all its readings. That pass's 30 days then count from the day you bought it, and readings you have not used from earlier passes or from packs of 100 are lost. On Android, the legal basis is giving what was bought under the id of our own to each phone that has the id, as the terms of use describe Pro, and completing a tip you leave, as they describe tips (Art. 6(1)(b) GDPR). Keeping the id on your phone and reading what Google Play holds there about your purchases need no consent, since Pro cannot work and a tip cannot be completed without them (§ 25(2) No. 2 TDDDG). Google handles the sale of Pro and every tip on Google Play under its own terms, in the EU as Google Commerce Limited, Ireland, and processes your purchase as a controller under its own privacy policy. What our service keeps stays, since Google Play gives Pro for ever back to every Android phone of your Google account for good, a backup brings back the id with everything bought under it, and a purchase forgotten would count a second time or be lost. To learn what it keeps, or to have it deleted, send us the order number from Google Play's receipt email. After a deletion, Tervaya counts again only what Google Play still gives back, Pro for ever with all its readings. A running pass and the readings you have not used from passes or from packs of 100 are lost. Google LLC is certified under the EU-US Data Privacy Framework.
A backup or an export
Only when you ask for one.
A backup and a trip's PDF or Excel file go into a folder you pick or through the system's share sheet. A CSV export goes through the share sheet. Where they land is your choice.
Nothing reaches us: the phone hands the file to the app or place you choose.
A trip's keepsake
Only when you share it.
A closed trip's picture goes through the system's share sheet. It shows the trip's photo, or without one the outline of its country, the trip's name, dates and destinations, how many days it had and what it cost you, or all of you together where you pay from one purse. A dot stands for each day, larger the more was spent that day. Where it lands is your choice. It carries no other traveller's name and none of the data stored in the photo file, such as the place and time it was taken.
Nothing reaches us: the phone hands the file to the app or place you choose.
Nothing else, except what the phone's own speech recognition may send to Google or Apple, as described under “Permissions”, the phone's question to your app store about your age range, as described under “Your age range”, and an email you send us yourself, as described under “Emails to us”. No analytics, advertising identifier or crash reports of our own, and no fonts loaded from anywhere.
Everything Tervaya itself sends travels encrypted over TLS. A file or picture you hand to another app through the share sheet travels as that app sends it.
Everyone this page names as receiving data from Tervaya has to protect it: our processors, Microsoft and Cloudflare, under data processing terms that bind them to the GDPR and to what this page says, and the others, as controllers of their own, under the GDPR, outside the EU together with the EU-US Data Privacy Framework or the EU standard contractual clauses.
If you let your phone share usage and diagnostics with Google, Google Play may show us reports of the app's crashes, without your name.
If you let your iPhone share analytics with app developers, Apple may show us reports of the app's crashes, without your name. We read these reports only to find and fix the app's errors, on the basis of our legitimate interest in an app that works (Art. 6(1)(f) GDPR). You can switch the sharing off in your phone's settings at any time.
Our own service
Exchange rates, place search on Android, Smart capture, the check of purchases and tips, the mailbox of shared trips, the corrections of the app and the app's proof run as a function on Microsoft Azure, region Germany West Central, under Microsoft's Products and Services Data Protection Addendum. It writes no request body and no IP address to a log.
Microsoft keeps the data of this function in the EU and uses the network data of each call to run and secure Azure, in logs it pseudonymises. Where its EU Data Boundary allows access from outside the EU, the EU standard contractual clauses in its addendum apply, and Microsoft is certified under the EU-US Data Privacy Framework.
This function uses your IP address in memory only, to limit how many requests may come from one address, so that neither a loop nor a script can overload it (Art. 6(1)(f) GDPR). It forgets an address at the latest eleven minutes after the last request from that address. It counts under a random number the app draws once and the service keeps only hashed: place searches on Android per month, removed after the month that follows; Smart capture per day, removed two days later; and the free readings of Smart capture you have used, removed at the end of the month two years after your last one.
The app draws this number the first time you use one of these features or Drive, or it checks your purchases on Google Play, on the iPhone already at its first start, and keeps it on your phone, where it also tells your phone's backups in Drive and iCloud apart from another phone's. Beside it, the app keeps how many of Smart capture's free readings are left, whether the phone had Pro and which trips had its free first steps. Without them the limits cannot hold, and without the limits the features cannot be offered, so keeping them needs no consent (§ 25(2) No. 2 TDDDG).
This website
These pages are served by Cloudflare (Cloudflare, Inc., USA) with Cloudflare Pages, as our processor under its Data Processing Addendum. As with every website, Cloudflare receives your IP address with each visit, since it needs it to send you the page. Legal basis: our legitimate interest in delivering these pages reliably and safely (Art. 6(1)(f) GDPR). The pages load nothing from anywhere else and set no cookies.
If you pick light or dark on these pages, your browser remembers that choice for your next visit, and nothing else. It is never sent to us, and since it only keeps what you asked for, it needs no consent (§ 25(2) No. 2 TDDDG). Clearing this site's data in your browser removes it.
Cloudflare keeps a log of the visits for us for 31 days, with details such as the IP address, the browser, the page and the country.
Cloudflare also uses the data of each visit as a controller of its own, under its own privacy policy, to run, secure and improve its network, for example to recognise and block attacks, and sells none of it.
Only when Cloudflare takes a visit for an attack may it ask your browser to pass a check first, and then it sets a cookie that remembers the check was passed.
Cloudflare serves the pages from data centres around the world, usually one near you. Cloudflare, Inc. is certified under the EU-US Data Privacy Framework.
Emails to us
When you write to us, we receive your email address and what you write, and use both only to answer you. Legal basis: Art. 6(1)(b) GDPR where you ask about your use of Tervaya, otherwise our interest in answering you (Art. 6(1)(f) GDPR).
An email you start from Settings › About Tervaya already names the app's version and your phone's model and system version, so we can answer without having to ask. You see them in the email and can delete them before you send it.
Mail to hello@tervaya.app goes through Cloudflare (Cloudflare, Inc., USA), which forwards it as our processor under its Data Processing Addendum and keeps each mail's sender, subject and time for 31 days, but not the mail itself. We read and keep the mail in a Gmail mailbox, which Google (Google Ireland Limited) provides as a controller under its own terms and privacy policy, not as our processor. The legal basis for this is our interest in a dependable mailbox (Art. 6(1)(f) GDPR). Cloudflare and Google may process the mail outside the EU; Cloudflare, Inc. and Google LLC are certified under the EU-US Data Privacy Framework. We delete the mail six months after the last message, unless a law requires us to keep it longer.
Other people on a trip
Naming somebody on a trip puts a name on your phone. They need no app, no account and no phone. On a shared trip their name goes along encrypted, as described above under “Shared trips”, and Smart capture sends it with every sentence, shared text or recording it reads, so that it can tell who paid. The phone's own speech recognition gets it too, as described under “Permissions”.
If somebody named you on a trip, our service keeps your name only on a shared trip and only encrypted, so we cannot read it. Smart capture sends it to Microsoft while it reads, as described above, and the speech recognition on that person's phone may send it to Google or Apple, as described under “Permissions”. The person who named you can rename or remove you at any time. For your rights, write to hello@tervaya.app.
Your data is yours
The backup file, restoring from it and the CSV export are never locked away. A backup is a plain file you can open and read.
“Delete all data” in the settings removes every trip, expense and setting from your phone, with the keys of your shared trips, the copies of photos and exports Tervaya made along the way, and your Google sign-in for Drive. It cannot be undone. Only a random number for this installation stays, with whether the phone had Pro, which of its free readings and first steps it used and, where it has one, the id your purchases on Google Play carry, so none is given twice, an ended pass still finds its Drive backups and what you bought is found again. It ends your shared trips as deleting each would, where our mailbox answers: those you organise close for everybody, the others you leave. What a shared trip has in our mailbox stays there while the others use the trip and is deleted 30 days after its last change.
On the iPhone, what our service keeps about your purchases stays, since it belongs to your Apple Account, and the app finds it again at its next start. On Android it belongs to the id of our own that your purchases on Google Play carry. “Delete all data” leaves that id on your phone, so the app finds your purchases again there too, and after Tervaya is uninstalled, Google Play brings the id back if you bought Pro for ever, as does any backup made since your first purchase.
Uninstalling Tervaya on Android removes everything it keeps on your phone, and the phone's own backup to Google never includes it. A backup in Google Drive stays until you delete it with “Delete backups from Drive” in the settings, which stands there while Drive is off. “Delete all data” does not touch it.
On the iPhone, a backup in iCloud stays until you delete it with “Delete backups from iCloud” in the settings, which stands there while iCloud is off, or in the iPhone's settings under your name › iCloud. “Delete all data” and uninstalling Tervaya do not touch it.
On the iPhone, the phone's own backup to iCloud or to a computer includes your trips, expenses, photos and settings, as it does for every app. Apple keeps an iCloud backup under the terms between you and Apple, and we receive nothing. To leave Tervaya out, switch it off in the list of apps under Settings › your name › iCloud › iCloud Backup.
Uninstalling Tervaya on the iPhone removes your trips, expenses, photos and settings from it. The iPhone's keychain can keep two things past that. One is what “Delete all data” keeps, so that none of it is given twice when you install Tervaya again on this iPhone. The other, unless you deleted all data first, is the keys of your shared trips, whether the lock was on and your Google sign-in for Drive. Erasing the iPhone removes both.
Your age range
Some laws make apps check a person's age with their app store, as Texas does in the United States. Where the App Store says such a law applies to you, Tervaya asks it for your age range when you first open the app and once a year after that. On Android it asks nothing yet.
Tervaya uses the answer only to decide whether it opens, in the United States for people aged 18 and over, elsewhere for people aged 16 and over. It tells the United States by your app store's country, never by your location. On your phone it keeps only the day of the check, never your age range, and it sends neither to us nor to anyone else. “Delete all data” and uninstalling Tervaya remove the day. Apple answers under its own terms and privacy policy.
Legal basis: our legitimate interest in offering Tervaya where such laws apply (Art. 6(1)(f) GDPR). Where a law requires the check, asking your app store needs no consent (§ 25(2) No. 2 TDDDG).
Permissions
The camera and your photos, only when you attach a receipt or choose a photo for a closed trip, and only at that moment. On the iPhone, Tervaya asks to add to your photos only when you save a trip's keepsake there. That allows adding, never reading. The photo is saved on your phone. Tervaya puts a trip's photo in no backup file, no Drive or iCloud backup, no shared trip and no export. It leaves your phone only in the trip's keepsake, when you share it yourself, and on the iPhone with the phone's own backup, as described above under “Your data is yours”. While Smart capture is on, AI reads a receipt through our service to fill an empty form. Our service keeps none of it.
Your location, when you ask for where you are, for an expense or on a map. Once you have allowed it, also when the map for picking a place opens with nothing on it yet, so that it opens where you are, and, once you turned on “Add the place by itself”, so that every new expense you type, say or scan gets the place where you are. You can remove that place from the expense at any time. A point is saved with an expense on your phone only when you save the expense with it, or when you give an expense somebody else wrote on a shared trip a place of your own. That place stays on your phone and in your own backups and never goes into the trip.
The microphone, only while you speak an expense or a cash movement. While Smart capture is on and has readings left, the recording goes to our service to be turned into words and is deleted on your phone right after. While Smart capture is off, once its free readings are used and no bought ones are left, or where our service cannot answer, the phone's own speech recognition turns your words into text instead, and gets the names on the trip so that it spells them right. Where it cannot do that on the phone, your words and these names go to Google on Android or to Apple on iPhone. Legal basis: the use of the app you asked for (Art. 6(1)(b) GDPR); Google and Apple act as controllers under their own privacy policies.
The app lock, only if you turn it on in Settings: the phone itself checks your face, your fingerprint or its unlock code and tells Tervaya only whether that worked. None of them reaches Tervaya. The app sends nothing and keeps only whether the lock is on, on this phone alone. No backup brings it to another phone.
Sharing a backup opens the system's share sheet; that is the system's dialog, not ours.
Notification access on Android, only if you allow it in the phone's settings: Tervaya reads the notifications of a listed bank or wallet app. Those that name an amount (a number beside a currency sign or a code such as EUR) are held on your phone until you next open Tervaya, which then keeps only the amount, currency, merchant and time of a card payment made while a trip runs and drops the rest. It stays on your phone until you add it as an expense. Before that, only its merchant's name goes out, and only if you search for the payment's place by that name. Other apps' notifications are ignored. So that a notification posted twice waits only once, Tervaya remembers, for each of the last 200 it held, a fingerprint that does not contain its words. Tervaya deletes these fingerprints when you delete all data, or when you open it after turning the access off.
Notifications, only if you switch them on for a shared trip: Tervaya then looks into the mailbox now and then in the background, when the phone lets it, and tells you what the others entered or changed there. With the app lock on, the notification says only that something is new. Nothing is pushed to your phone, and no address for notifications leaves it.
Apple Pay on iPhone, only if you set up an automation in Apple's Shortcuts app that runs Tervaya's action “Hold a Payment”: the amount and the merchant of a payment at a till, with its time, held on your phone until you next open Tervaya, which keeps them only for a payment made while a trip runs. It stays on your phone until you add it as an expense. Before that, only its merchant's name goes out, and only if you search for the payment's place by that name. Until you delete all data, Tervaya also remembers when the action last ran, to show it in Settings, and sends that nowhere.
How long
On your phone, everything stays until you delete it. What “Delete all data” keeps stays until you uninstall Tervaya, and on the iPhone it can outlast that, as described above under “Your data is yours”. What came in from outside and waits for you is forgotten after 30 days unless you add it.
In our mailbox, everything a shared trip holds, its encrypted parcels and the ids, keys and times beside them, is deleted 30 days after the last change anyone in the trip made. The organiser's recovery keys go with it.
While a shared trip is under way or still ahead, one of its phones looking into the mailbox counts as a change, so the trip is not deleted while it is in use. The phone knows this from the trip's dates, which the mailbox cannot read. A closed trip counts as over, and one without an end date as under way until it is closed. For this the mailbox notes the last day one of the trip's phones looked in, not which one, and nothing else.
Your rights
You have the right of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15 to 21 GDPR), and you can withdraw a consent at any time for the future. Write to hello@tervaya.app. Most of your data exists only on your phone, where you can export or delete it yourself.
Our mailbox knows no names and no email addresses, so we cannot tell from a message which shared trip is yours (Art. 11 GDPR). What its parcels carry is on your phone and in a backup, readable. Leaving a trip ends your phone's access at once. What you entered stays with the others, and in the mailbox until 30 days after the trip's last change.
Where we rely on our legitimate interest (the exchange rates, the corrections of the app, the app's proof, the loop guard of our service, the age check, crash reports, emails to us and this website), you may object at any time for reasons arising from your situation (Art. 21 GDPR).
You are not obliged to provide any data. A feature that needs a service works only with the data named for it above. Where a law requires the age check and you have not shared your age range or confirmed your age with your app store, Tervaya does not open. No decision with legal or similarly significant effects on you is made automatically (Art. 22 GDPR).
You can also complain to a supervisory authority (Art. 77 GDPR), in particular in the country where you live or work, or to the one responsible for us: the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg.
Children
Tervaya is not meant for children under 16.
Where your app store tells Tervaya that you are younger than it is meant for, it stays closed.
Changes to this page
This page describes the app as it is. When the app changes what it does with data, this page changes in the same release, and the date at its top says when. A new use that needs your consent is asked for in the app first.