Last updated 7 October 2026
Tarjetas works on your device. There is no account to open, no password and no email address. It sends nothing anywhere until you use the half of it that needs somebody else — the classroom or the friends page — and what it sends then is only what has to reach them: the name you type, the emoji you pick, the code people find you by, and the things you deliberately hand over — a class you publish, a friend request you send, a dictionary you give a friend. Moving to a new phone, or linking another of your own devices, when you choose to, carries the rest of what the app keeps for you, sealed so that the server passing it on cannot read it.
The app arrives already pointing at a server, so that those two pages work without anybody having to be told an address. Being pointed at one is not being on it: opening the app writes you nowhere, and drilling your own words never does.
Three things can leave your phone without either of those. If you say an answer, or words for your dictionary, aloud instead of typing them, your phone's own speech recognition may use the network to hear them — see Saying an answer aloud. On Android, reading a word list off a photo or a screenshot uses Google's ML Kit, a library inside the app, which tells Google how its reading went — never the picture, and never the words on it. And if you turn Recognition to "In the cloud" in the settings, a photograph is sent to OCR.space to be read there instead of on the phone. That switch is off unless you turn it on, and it is the only thing in the app that sends a picture anywhere — see Reading a photo or a screenshot.
Tarjetas also runs in a web browser. There it keeps everything in the browser, and two things can go to the browser's own services rather than the phone's: what you say aloud, to be turned into text, and, where the browser has no Spanish voice installed, a word you ask to hear — see Using Tarjetas in a browser.
There is no advertising and no tracking of any kind, and the app keeps no analytics of its own. Nothing about you is sold or profiled, and nothing is shared beyond what this page describes.
None of this is sent to the developer or to anybody else. The one exception is a move to a new phone, or a link to another of your devices, that you make yourself, which carries it — sealed, so that the server passing it on cannot read it — see Moving to a new phone and Linking another of your devices below. Uninstalling the app removes all of it from the device — see Backup below for the one copy that is not on the device and is not the developer's either. In a browser, all of it is in the browser, and clearing that site's data removes it — see Using Tarjetas in a browser.
Only when you use the half of the app that needs somebody else. Tarjetas arrives already pointing at a server — the one described under Where the data is kept — so that the classroom and the friends page work without anybody having to be told an address.
Being pointed at it is not being on it. A device that has never claimed a code is not allowed to claim one on a sync nobody asked for, so opening the app writes you nowhere. Your code is claimed the first time you open the friends or classroom page, add somebody, publish or join a class, or move to a new phone — the half of the app that needs other people or another phone, and the only half that needs a code at all. Somebody who installs Tarjetas, drills their own words for a year and never does any of those has no record on the server at all.
The Server field on the Settings page holds that address and it is yours to change. A teacher running their own server types its address over the top, and this policy stops describing where the data goes — see A server somebody else runs. Emptying the field stops all contact with any server: every screen still works, and nothing about you is sent to one.
When any of it is sent, this is sent — and nothing else:
Your profile. The code you are found by, the name you have typed, your avatar emoji and its colour, and the date you last opened the app. The date is kept for one purpose: so a teacher can see which of their students has used the app lately. It is a date, not a time.
Friends. When you ask somebody or accept a request: the two codes, which of you asked, whether it was accepted, and the date. Somebody you have only asked does not see your name or your emoji until they say yes.
Classes you publish, as a teacher. The class name and code, your name and emoji as its teacher, and each lesson with its words, translations, notes and homework. The group emoji you file your own words under is deliberately removed first — how you organise your own dictionary is not part of the lesson.
Classes you join, as a student. Your code, the class code and the date, so the teacher can see who is in the room — and so can the other students in it, who see your name and emoji. The date you last opened the app is shown to the teacher alone. Somebody you have blocked, or who has blocked you, is not shown to you there, and you are not shown to them. Once the teacher takes you out of a class, only the teacher still sees you listed in it.
Students you take out of a class, as a teacher. Their code, the class code and the date, so the class stops reaching them. Their own phone is told, so they see that their teacher removed them rather than wondering why nothing new arrives. The lessons they already have stay on their phone. The list comes back to you with your own classes, so that a new phone of yours can still let them back in.
A key on a class, as a teacher. If you put a key on a class, the server keeps it beside the class, so that knowing the code is no longer enough to join. It is never handed out with the class: your students do not receive it, and the server gives it to nobody but you — it comes back with your own classes, so that a new phone of yours keeps the class shut rather than publishing it without one. Making a new key replaces it, and taking the key off deletes it. A student who types the key keeps it on their own phone, so that the phone can get back into the class by itself.
Moving to a new phone. If you ask for a move code on the Settings page, your phone makes the code and keeps it. What it sends the server is a scrambled form of the code, from which the code cannot be worked back, and a parcel sealed with the code itself: your settings, the classes you have joined or kept, your homework answers — including any not handed in — and your drill progress. Your dictionary is never in it. The server keeps the two for an hour at most, and less if the code is used or you close it first. It never has the code, so it cannot open the parcel: the phone you type the code on sends a second scrambled form of it, which the server checks against the first. While the parcel waits, the server also locks it a second time, with a key of its own that is kept apart from the database and from every copy of it, so a copy of the database is no way into the parcel either. Typing the code on another phone gives that phone your account — your code, your name and emoji, your classes with everything the server keeps about them, your friends and your blocks — and the parcel, which that phone opens with the code; the server's copy of the parcel goes once that phone first uses your account, moments later. The proof of the account your old phone held stops working as soon as the code is typed, and a scrambled copy of it is kept so that the old phone can be told why and let go of the account, rather than start a new one with your classes on it. That copy names nobody and says nothing about who held it.
Linking another of your devices. The link button on the friends page works as a move does, with three differences. The sealed parcel also carries your dictionary — your words, and how you have grouped them — so the other device starts as a copy of this one. Nobody is signed out: each device holds its own proof of the account, and the server keeps a record of each — a code standing for the device, which only your own devices are shown; whether it says it is a phone, a tablet or a browser; a model name such as "Pixel 7" or "iPad", never the name you gave the device; the date it was linked; and the date it was last used. And the name, emoji and colour you last set are kept apart from what others are shown, so that your other devices take a change you make on one, but never one a moderator has put in its place. Words you send from one of your devices to another wait on the server, as a dictionary sent to a friend does, until that device takes them or either of them is unlinked. Unlinking a device, from any of them, deletes its record and its proof of the account; a scrambled copy of that proof is kept, as for a move, so that the device can be told why and let go of the account.
Homework you hand in, as a student. Your answer as you wrote it, your code, the class code, the lesson it answers and the time you handed it in. Only the teacher of that class can read it; it is not shown to the other students. Handing in again replaces the answer. It is deleted when you delete your account, when the teacher deletes the lesson or the class, or when the teacher deletes their account. While you are out of the class — you left, or the teacher took you out — the teacher does not see it. Your answers are also kept on your own phone, so you can read and correct them without a connection. An answer you have written but not yet handed in stays on your phone and is sent nowhere, except sealed inside a move to a new phone that you make yourself.
Answers you check, as a teacher. The mistakes you mark in an answer — which words, and what you wrote about each — and the time you marked it checked, kept with the answer. Only the student who wrote it receives them, and their phone keeps a copy so they can read them without a connection. Checking again replaces them. They are deleted when the student hands in a different answer, and whenever the answer itself is deleted. What you write about a mistake goes through the same filter as your class notes.
Quizzes you write, as a teacher. Each question, its options or accepted answers with the right ones marked, and the time each question is open, kept on the server beside the class but apart from it. Your students' phones are told only how many questions a quiz has and how long each is open until you run it; while it runs, each question is shown without its answer until its time is up; and a student is sent the whole quiz only once they have taken it, so they can take it again on their own phone. Questions and answers go through the same filter as your class notes. Once a quiz has been run, the server keeps its questions as they were, because everybody's results are held against them. It is deleted when you take the quiz off, or delete the class or your account.
Quizzes you take, as a student. Your answer to each question, when you gave it, what it scored, and whether you took the quiz with the class or later on your own. When the quiz is over, everybody in the class sees the results — each student's name, emoji and score — and your teacher sees whether you took it late. While a quiz is waiting to start, the students who have joined see each other's names. A student who is no longer in the class is shown to the teacher alone. It is deleted when you delete your account, or when the teacher takes the quiz off or deletes the class or their account. Taking a quiz again afterwards happens on your phone, and nothing about it is sent.
Dictionaries you share. When you send your dictionary to a friend: the words and translations in it, both codes, and the date. The group emoji you file your words under is removed first, exactly as it is from a lesson — how you arrange your own dictionary is yours and stays on your device. It waits on the server until your friend takes it, or until either of you removes it.
People you block. When you block somebody: the two codes and the date. Nobody is told they have been blocked, and the list is readable by you alone — it is on your Settings page, which is also where you undo it.
Reports you make. When you report a person, a class or a dictionary somebody has sent you: your code, theirs, which of those three it was, the reason you picked, and a copy of the text you were looking at — a display name, a lesson note, or the words in the dictionary — up to two thousand characters of it. Reporting the same person over the same thing again, a second word from one dictionary say, adds to the first report rather than replacing it, still within those two thousand characters.
That copy is the part worth being plain about, because it is the one thing in this app that sends somebody else's writing somewhere on your say-so. It is sent because a report without it cannot be acted on: by the time anybody reads it the note may have been edited and the dictionary taken back, and what was on your screen is the only copy left. It goes nowhere but the server, it is read by the person who runs it and nobody else, and the person you reported is not told and is not shown what you wrote. Reporting needs a server, so on a device with the Server field emptied the app says so rather than offering the form. Blocking never does.
When typing is switched on in the drill, the microphone button beside the answer field lets you say the answer instead. The app asks for the microphone the first time you press that button and not before, and the microphone is on only while the button is lit. A right answer moves you on to the next card and the microphone stays on for it; it goes off at the first answer that is not right, after a few seconds with nothing said, when you press the button again, or when you move the card on yourself.
The dictionary has a microphone too, on its page for adding many words at once. There you say a word in Spanish and then its translation, in the language picked beside the button, and each pair is written onto the page as a line of text for you to check. The microphone is on only while that button is lit; it goes off after a few seconds with nothing said, when you press the button again, or when you leave the page or the Dictionary tab. Nothing goes into your dictionary until you add the lines yourself.
What you say is turned into text by the speech recognition your phone already has — on Android usually Google's, on iOS Apple's — and the text is put in the answer field, or on the page, exactly as if you had typed it. It is checked there like anything typed, and it is not sent anywhere.
Where your phone has speech recognition installed for the language being heard, it does this on the phone itself. Where it has not, the phone's speech service does it over the network, under Google's or Apple's policy. Tarjetas does not record, keep or send the sound, and none of it reaches the developer or the Tarjetas server.
The dictionary's page for adding many words has a camera button too. It opens your phone's own camera app, and the photo you take is read on the phone: the lines of text found on it are written onto the page for you to check, exactly as if you had typed them. Nothing goes into your dictionary until you add the lines yourself. The photo is deleted as soon as it has been read, and Tarjetas sends neither the photo nor the text read from it anywhere. A few camera apps also keep a copy of every photo they take in your gallery; that copy is the camera app's, and it can be deleted there.
Beside it, a picture button opens your phone's own picture picker, for a screenshot or a photo you took earlier. Tarjetas is given only the picture you pick, and only to read it: it asks for no access to your photos, sees none of the others, and neither copies nor keeps the one you picked. It is read exactly as a photo is.
On iOS the reading is done by Apple's Vision, which is part of iOS, and nothing about it leaves the phone.
On Android it is done by Google's ML Kit, a library built into the app, which reads on the phone and needs no network. ML Kit does report to Google on its own work: the phone's make, model and system version, the app's name and version, the reader's version, the picture's format and resolution, how much was read and how long it took, error codes, and an identifier for this installation of the app that is not meant to identify you or your phone. It does not send the picture or the words read from it. Google says it sends this over an encrypted connection, uses it for diagnostics and usage statistics, and passes it to nobody else — see Google's description of it and Google's privacy policy. None of it reaches the developer or the Tarjetas server.
Reading in the cloud, which is off unless you turn it on. The settings page has a Recognition switch with two ends: this phone, which is how the app arrives and everything above describes, and the cloud. Turning it to the cloud asks first, naming OCR.space and linking this page, and changes nothing unless you agree. Agree, and a photograph is no longer read on the phone: it is sent, as a JPEG of up to a megabyte, to OCR.space, which reads it and sends back the text. Nothing else goes with it but the key it is read under, below — no name, no code, no account, because the app has none of that to send. The service answers with text and the app puts it on the page for you to check, exactly as a photograph read on the phone is. OCR.space says it deletes every picture once it has been read and keeps none. Like any website, it also sees the internet address a picture comes from, and says it logs that address for a month and then deletes it. Their policy is at ocr.space/privacypolicy.
Turning the switch back to this phone stops it, and nothing sent before that can be taken back — a picture once sent has been sent. If you would rather no photograph ever left the phone, leave the switch where it arrives.
The key it is read under. OCR.space wants a key with each picture. The app carries one, on a free plan the developer registered and pays nothing for, shared by every copy of the app; it is good for a fixed number of pictures a month across everybody, and when that is used up the reading fails until the month turns. You can put a key of your own in the settings instead — OCR.space gives them away at ocr.space/ocrapi — and then your pictures are read under your key and not the shared one. Yours is registered to the email address you gave OCR.space for it, so it tells them a picture is yours, where the shared one tells them only that it came from Tarjetas. The key is kept on your phone and sent to OCR.space and to nobody else. The developer cannot see which pictures were read under either key, only how many the shared one has left.
Tarjetas also runs in a web browser, at tarjetas.elzianor.com, on the same server as everything above. It is the same app, and everything on this page holds for it, with these differences.
Where it keeps things. What What stays on your device lists is kept in your browser's own storage for that address, on the computer or phone you are using, and nowhere else. It is in no phone's backup, and your browser does not copy it to your other devices. Clearing that site's data in your browser removes it, just as uninstalling the app does, and so does closing a private window the app was used in, whose storage goes with it. The code people find you by goes too, and nothing can hand it back. The move code described under Moving to a new phone carries an account between a browser and a phone, in either direction. Backup on the Settings tab writes all of it, your account included, into one file wherever you choose, and applies that file again; nothing sends the file anywhere, and whoever has it can use your account. The app asks your browser to keep its storage rather than clear it to make room; most browsers decide that for themselves, and Firefox asks you. Even so, some browsers, Safari among them, delete a site's storage by themselves after a while without a visit — Safari not for the app added to the home screen, which keeps its own.
What it loads. Every file the browser version uses — the app itself, its fonts, and the reader for photos — comes from the app's own address. It loads nothing from any other site: no fonts, scripts or trackers from elsewhere. Its calls go to the same server the phones use, which accepts calls from a browser only when they come from the app's own address. The browser keeps a copy of those files, so that the app opens without a connection; the copy is the app itself and holds nothing about you, and clearing that site's data removes it with the rest.
Saying an answer aloud. In a browser the microphone button uses the browser's own speech recognition, and the browser asks you for the microphone itself, the first time you press the button. What you say is turned into text by the browser's maker: Chrome sends it to Google, Microsoft Edge to Microsoft, and Safari uses Apple's speech recognition, on the device or over the network as Apple decides — each under its maker's privacy policy. Firefox has no speech recognition, so there the button is not shown. As in the app, Tarjetas does not record, keep or send the sound; it is given only the text.
Hearing a word. The speak button uses a Spanish voice your browser provides, and chooses one installed on your computer or phone wherever there is one: that voice speaks on the device and sends nothing. Only where no Spanish voice is installed does it use an online one — Chrome's Google voices are such — which is sent the word in order to say it, under its maker's privacy policy.
Reading a photo or a screenshot. A picture is chosen through your browser's own file chooser — on a phone or a tablet, which can open its camera too — and Tarjetas is given only the one you choose. It is read inside the browser by Tesseract, a text reader the app downloads from its own address the first time it is needed and the browser keeps after; neither the picture nor the text read from it is sent anywhere. Google's ML Kit is no part of the browser version. The Recognition switch and OCR.space work exactly as described under Reading a photo or a screenshot.
Permissions. The browser asks for any permission itself, in its own words: the microphone, the camera where a phone's chooser opens it, and, in Firefox, whether to keep the app's storage. Refusing any of them changes nothing else in the app.
Deleting it. Settings → Account → the bin deletes your account from the server exactly as described under Deleting it. What is in the browser goes when you clear that site's data.
No email address, password, phone number, real name, date of birth, location, contacts, calendar, payment details, recordings of your voice, device identifier or advertising ID.
No crash reporting, no advertising, no social network integration, and no analytics of the app's own. Two third parties can receive anything at all, both described under Reading a photo or a screenshot: Google's ML Kit in the Android app, which reports on its own reading and never the picture; and OCR.space, which receives a photograph itself, but only where you have turned the Recognition switch to the cloud. Each has a privacy policy of its own, linked in that section, and each protects what it receives at least as well as this page protects what reaches the Tarjetas server: OCR.space deletes a picture once it has been read, and Google passes ML Kit's report to nobody. Apart from those, the app talks to one server, which is the one whose address is in its settings, and to nothing else. Saying an answer or a word aloud uses your phone's own speech recognition, or in a browser the browser's, and a word heard in a browser is spoken by the browser's voice, as described above — none of them a service of the app's.
Android — Internet. Used to reach the server address in the settings; OCR.space, where Recognition is set to the cloud; and Google, for ML Kit's report — and only for what is described above.
Android — text-to-speech visibility. A declaration that lets the app see the speech engine already installed on your phone. Speaking happens on the device; nothing is sent anywhere to do it.
Android — microphone. Asked for the first time you press a microphone button, in the drill or on the dictionary's page for adding many words, and used only while that button is lit, to hear an answer or a word said aloud. Refusing it changes nothing else in the app.
Android — speech recognition visibility. A declaration, like the text-to-speech one, that lets the app see the speech recognition already installed on your phone.
Android — camera app visibility. A declaration, like the two above, that lets the app see the camera app already on your phone, which is what takes the photo.
Android — document picker visibility. Another such declaration, for phones older than Android's photo picker: it lets the app see the system's document picker, through which a picture is picked there.
Android — network state. Added by Google's ML Kit, which looks at whether the phone is online before sending its report. It is granted without asking, and it shows nothing of what you do online.
iOS — local network. Asked for only when the server address is on the same network as your phone, which is what happens when a teacher runs one on a laptop in the classroom.
iOS — microphone and speech recognition. Both asked for the first time you press a microphone button, in the drill or on the dictionary's page for adding many words, and used only while that button is lit, to hear an answer or a word said aloud. Refusing either takes the button away and changes nothing else in the app.
iOS — camera. Asked for the first time you press the camera button on the dictionary's page for adding many words, and used only while the camera is open. Refusing it takes the button away and changes nothing else in the app.
The app requests no location, contacts or storage permission, no access to your photos on either platform — a picture is picked through the phone's own picker, which hands over only that one — and on Android no camera permission either: the photo is taken by your phone's own camera app.
In a browser, the browser asks for whatever it needs in its own words, as Using Tarjetas in a browser describes.
Tarjetas allows your phone's own backup, which is on by default on both platforms: Android's auto-backup to your Google account, and iCloud to your Apple account. That takes the app's data with it — your words, your progress and your settings.
This is deliberate, and it is what carries an account to a new phone. Your settings are where the code people find you by is kept, so restoring a backup brings back the same code, the same friends and the same classes. There is no password here and no email address, so without the backup there would be nothing else that could hand any of that back.
The backup is made by your phone into your own account, under Google's or Apple's policy and your own backup settings — not by this app, and not by its developer, who has no access to it and no way to ask for it.
You can turn it off in your device's settings. If you do, a phone that is wiped or replaced comes back as a new user with a new code, and nobody can restore the old one — not the developer, and not the server. The same is true if you move between an Android phone and an iPhone, since neither backup can be read by the other.
Anybody who still has the old phone in hand has a second way, which needs no backup and works between the two platforms: the move code described under Moving to a new phone. The old phone shows it (Settings: the phone with the arrow going out), and the new phone takes it (the phone with the arrow coming in). It needs the old phone because there is no password: the phone that holds the account is the only thing that can vouch for moving it. It carries everything but your words, progress included; exporting and importing your words carries those. Linking a device instead, from the friends page, carries your words too and keeps the account on both — see Linking another of your devices.
A browser has no such backup: what the app keeps there is in that browser alone, and the move code is the only way to carry it to another device — see Using Tarjetas in a browser.
The server this app is shipped pointing at is a virtual machine in the European Union, rented from netcup GmbH. Its database is a single file on that machine, copied continuously to Cloudflare R2 object storage, also held within the European Union. No one else is given access to either.
That copy follows the file within seconds, deletions included, and keeps a day's history as well, so that a mistake on the machine can be undone. Anything deleted from the server is gone from the copy within two days.
Now and then the developer also takes a copy of the whole database onto their own computer — before a change to the server, say — so that it can be put back if the change goes wrong. Such a copy holds the database as it was at that moment, is kept for as long as the developer keeps it, and is deleted by hand rather than on a timetable. Something deleted from the server can therefore still be in a copy made before it was deleted. The copies are used for nothing but putting the server back, and nobody else is given them.
The machine also keeps a log of the requests it answers, for finding faults and abuse — requests for the browser version's files among them: when each came, what it asked for with every code in it blanked out, and the internet address it came from, shortened so that it names a network rather than a device. Each day's log is deleted two weeks later.
From inside the app: Settings → Account → the bin. It asks first, and shows you what will go. Confirming removes, from the server: your code and profile, every friendship and every unanswered request in either direction, the classes you published together with their student lists and the students taken out of them — a class a moderator took down included, with the homework, quizzes and results kept against it — every class you were taken out of, every shared dictionary to or from you, every block you have made and every block made against you, every report you have made and every report made about you, a move or a link you have readied and not used, with its sealed parcel, and the record of every device your account is on, with any words waiting between them. It cannot be undone.
While your account is also on another of your devices, the bin unlinks only the device you press it on, and says so before it does: your account and everything above stay, on the others. Deleting the account is done from the last device it is on.
The reports and blocks go in both directions on purpose, and it is the one part of this that is not obvious. A code nobody holds is handed out again to the next device that asks for one, so a block or a report left behind naming your old code would attach itself to whoever next has it — somebody who has done nothing.
Your words and your drill progress are not touched by this — they were never on the server, save your progress sealed inside a move, which goes with the account if unused. Neither are the classes on your own device: a class you made stays where you wrote it, with its lessons, the same way your dictionary does. What deletion takes from it is everybody else's way in. It is off the server, its code is registered to nobody, no one can join it and its student list is gone. The code is never given out again, to you or anybody: the phones of students who joined still ask for it now and then, and whoever held it next would have them walk straight in. Publish the class again and it gets a new code. Deleting an account is meant to stop you being findable, not to take a term of lesson planning with it. Uninstalling the app removes those, and in a browser, clearing that site's data does.
What deletion cannot reach is a copy somebody else already has. A friend who has taken the dictionary you sent them is holding those words on their own device; a student who has merged your lesson into their own list is holding that. A class you published stays on the phones of the students who joined it, with the name and emoji you had when you published — it simply stops receiving anything new. Deleting your account removes what the server held, and stops any of it being handed out again — it does not travel to the phones where it has already landed. Worth knowing before you rely on it, because "delete my account" reads to most people as "and everything that came from me", and for what has already been given away it is not.
Nothing is kept on the server after deletion but the bare codes of your classes, which name nothing and nobody and are kept only so that nobody can take them. The server's backup lets go of the rest within two days, and a copy the developer took by hand before your deletion keeps what it held until that copy is deleted, as Where the data is kept says. If you would rather ask a person to delete it for you, write to the address at the foot of this page.
You can see everything held about you from inside the app — the friends list, your classes and your profile are the whole of it. You can correct your name and emoji at any time on the Settings page, and you can delete everything as described above. If you would rather ask a person to do any of this, write to the address below.
Tarjetas lets a teacher enter the address of their own server, which is what the Server field is for. If you do that, this policy does not describe where your data goes: it goes to whoever runs that machine, under whatever terms they offer. The app itself behaves identically either way — what changes is who is holding it.
Tarjetas is not directed to children under 13 and is not listed for them. An account is not knowingly opened for anybody under that age, and where we learn one has been, it is removed.
Where a teacher uses the app with a class that includes younger pupils, they do so as the adult running the room. The same removal applies either way: a teacher or a parent who wants a child's data removed can do it from inside the app with the bin described above, or write to the address below and it will be done.
It is built to need as little about a person as possible: no email address, no password, and no real name — the name is whatever you type into the field, and a first name or a nickname is enough. There is no advertising, no tracking and no profiling of anybody, of any age.
If what the app collects ever changes, this page changes with it, and the date at the top changes too. The app is not updated to collect something new without this page saying so first.
Tarjetas — Vladyslav Pysarenko urunokun@gmail.com
The app is written and run by one person rather than a company, and that name is the one the App Store and Google Play show as its developer. It is here so that the person responsible for what this page describes can be identified, which is the whole point of a contact section in a policy like this.