VivaLingua

This Privacy Policy describes how Sevenfires AI LLC ("we," "us," or "our"), located in Wisconsin, United States, the parent company and owner of the VivaLingua mobile application and the website at vivalingua.app (collectively, the "Service"), collects, uses, and shares information. This Policy is written to meet the requirements of the privacy laws that apply to us.

1. DATA WE COLLECT

• Account data: name, email address, username, profile photo (if you add one), hashed password, language preferences, and the standard voice you choose for your translated speech. If you sign in with Google or Apple, we receive your name and email address from them.
• Contacts: the people you add as contacts, and the contact requests you send and receive.
• Usage data: call and session duration, call history, your minute balance, how many minutes you use each day, and purchases and transactions.
• Device data: platform (iOS/Android), app version, and, if you allow notifications, a push-notification token for your device.
• Security logs: account and session activity events
• Support data: when you report an issue in the app, we collect the category and description you submit and technical context including app version, device model, operating-system version, and language settings. We also maintain the ticket's status and internal support notes. Authorized administrators may review this information to investigate and respond to your report.
• Diagnostic and crash data: when something fails in the app — a translation error, a blocked call, or an unexpected crash — we collect an error code, where it happened, the app version, the update identifier, and the platform. For a crash we also collect the technical stack trace and the error message. Before any of this leaves your device, email addresses, web addresses, and long numeric sequences are automatically removed from the message, and file paths are shortened. Unlike the anonymous performance data in section 8, these records are linked to your account so we can investigate a specific report. They never contain what you said or the text of a translation.
• Call diagnostics: after a call or in-person session, the app can send a diagnostic report of speed and error details — counters, timings, settings, and device details such as the phone model and network type (WiFi or cellular), never what was said. For each translated sentence, our servers also record the two languages, how long translation and speech took, and the country your connection came from, which is worked out from your IP address; the IP address itself is not stored. These records are linked to your account so that a specific problem can be investigated. You can turn them off in Settings → Privacy → "Send diagnostic reports", which also deletes the country records already collected.
• Video-call speech: Daily.co carries video-call audio. Each participant's audio is processed with Deepgram for real-time speech-to-text. Finalized source transcript text is then sent to Google Cloud Translation to produce the other participant's selected language.
• Audio Only calls: an Audio Only call is a call with sound and no video. Daily.co sends the sound of the call between the people in it. Their speech is turned into text and translated in the same way as in a video call. During an Audio Only call, the screen of each person shows each sentence two times: in the language that the speaker used, and translated. So the other person can see your words in the language that you spoke, and also their translation. In a video call, the other person sees only the translation.
• Waiting room: we record when your app was last open. When someone calls you and you are not using VivaLingua at that moment, the call starts in a waiting room instead of ringing, and the app may tell the caller that you are not using VivaLingua right now. A call also starts in a waiting room if you miss or decline it. In the waiting room, each person can see whether the other person is in the room and whether they are ready to talk. We keep a record of each waiting room in the call history of the people in it: when it opened, when each person came in, left or said they were ready, and how it ended. This record never contains anything that was said.
• Microphone and connection: during a call, the app tells the other person when your microphone is blocked or when your internet connection is weak, so that they know why they cannot hear you well. A web guest's browser does the same.
• In-person speech: in-person audio is sent through VivaLingua's service to Deepgram for real-time speech-to-text. If cloud transcription fails and an on-device speech model is available, VivaLingua may use that model as a backup. Finalized source transcript text is sent to Google Cloud Translation to produce the selected language.
• AI voice (optional): if you choose to create an AI voice, a recording of you speaking for 30 to 60 seconds, including four words that the app shows you. Section 4 describes it in full.
• Web guests: if a host invites you by link, the name you type, your language, and your voice choice. Section 5 describes it in full.
• Demos (optional): a demo is a short practice conversation in which you talk with an AI assistant. We collect what you say to the assistant during a demo. For each demo, we also keep a short list of facts, such as when the demo started and how many times you spoke. The list does not contain anything you said, as text or as audio. Section 12 describes the demos in full.

2. HOW WE USE YOUR DATA

• To provide and operate the VivaLingua service
• To process payments and manage your minutes
• To understand how people use their minutes, so that we can improve the Service and design plans and prices
• To send transactional emails (account confirmation and password reset)
• To send the notifications you allow, such as incoming calls and contact requests
• To create and use your AI voice, if you choose to have one
• To let hosts invite guests to calls and sessions by link
• To let you try VivaLingua: in a short demo, you talk with an AI assistant, and the app translates the conversation
• To detect and prevent fraud and security violations
• To investigate, respond to, and manage support requests
• To diagnose crashes, errors, and slow translations so we can fix them
• To confirm your email address before granting promotional free minutes, and to give the welcome minutes offered at sign-up only once to each person
• To comply with legal obligations

Where the GDPR or a similar law applies, these are our legal bases:

• Providing the Service you asked for. This includes sending the audio of what you say to the providers in section 3, so that it can be translated. Legal basis: our contract with you.
• Your AI voice: your separate, explicit consent. You can withdraw it at any time by deleting your AI voice in Profile.
• Demos with an AI assistant: the legal basis is your consent. The app asks for your consent each time you start a demo. You can end a demo at any time.
• Optional anonymous performance data (section 8): your choice in Settings.
• Keeping the Service secure, preventing fraud and abuse, and fixing errors: our legitimate interest in running a safe and reliable service.
• Keeping a record of the consents you give, and records the law requires: our legal obligations, and our legitimate interest in being able to show that you gave your consent.

3. DATA SHARING

We NEVER sell your data or share it with third parties for marketing purposes. We only share data with these service providers, each for the purpose named:

• Stripe — for payment processing (contractually protected)
• Cloudflare — for hosting our servers, database, and file storage (contractually protected)
• Daily.co — for video-call infrastructure (contractually protected)
• Deepgram — for real-time speech-to-text during video calls and in-person sessions, and to check the words you read when you create an AI voice (section 4) (contractually protected)
• Google Cloud Translation — to translate finalized video-call transcript text and in-person spoken text (contractually protected)
• Google Cloud Text-to-Speech — to turn the translated text into the spoken audio the other person hears, depending on the language (contractually protected)
• ElevenLabs — to turn the translated text into the spoken audio the other person hears, depending on the language; and, if you choose to create an AI voice, to create your voice model and speak your translated words in it (section 4) (contractually protected)
• Resend — for transactional email delivery (contractually protected)
• Expo — to deliver push notifications, which it passes to Apple's or Google's notification service for your device. A notification can include the name of the person calling you or sending you a request (contractually protected)

Which provider speaks a translation depends on the listener's language and on whether the speaker has an AI voice. If that provider fails, the same translated text may be sent to Google Cloud Text-to-Speech so that the listener still hears it; in that case both providers receive that translation.

Each provider receives only what it needs to provide its service to us, and is contractually bound to protect your data to a standard at least equal to the protections described in this Policy. ElevenLabs' standard terms would allow it to use what we send it to improve its AI; we switched that setting off for our account on September 19, 2026, so since then what we send ElevenLabs is not used to train or improve its AI. We also ask Deepgram, on every request we send it directly or through Daily.co, not to keep the audio to improve its models.

Before VivaLingua sends any of your speech to these providers, the app explains in plain language what is sent and who receives it, and asks for your permission. You can withdraw that permission at any time in Settings; translated calls and in-person sessions cannot run without it. Creating an AI voice needs a separate agreement of its own (section 4).

In the demos (section 12), Deepgram, Google Cloud Translation, Google Cloud Text-to-Speech and ElevenLabs do the same jobs as in calls. ElevenLabs also operates the AI assistant in the demos. To do this, ElevenLabs uses an AI model from Google. You give separate consent before you talk with the AI assistant.

4. AI VOICE (OPTIONAL VOICE CLONING)

Where it is available, you can choose to create an AI voice, so that the people you talk to hear your translated words in a voice that sounds like you. It is optional and needs your separate, explicit agreement in the app, which names ElevenLabs and explains what this section sets out. VivaLingua works normally without it.

• Where it is available: in most countries. It is not available in China. It is not available in Malaysia or South Korea. We are reviewing the laws in those two countries. It is not available in countries and regions under comprehensive United States sanctions. It is also not available to people who live in the US states of Illinois, Texas, Washington or Colorado. Those four states have their own laws on voice data.
• How we check where you are: we use the approximate location of your internet connection to decide whether to offer AI voice. We also use it each time you speak, to decide whether to use your AI voice. Where AI voice is not available, your translations are spoken in a standard voice. We do not store that location. However, when you create an AI voice, the record of your consent notes the country, and the state or region, that your device connected from (section 6). We may change where AI voice is offered.
• What we collect: a recording of you speaking for 30 to 60 seconds, during which you read aloud four words that the app shows you. A recording of your voice, and the voice model made from it, can identify you, so we treat both as biometric data.
• Where it goes: the recording is sent through our servers to Deepgram, which turns it into text so that we can check that the four words were read by the main voice in the recording. This checks that the recording is of a live person reading them, not a playback of someone else's recording; it is not used to identify you. The recording is then sent to ElevenLabs, which uses it to create an AI model of your voice. We do not keep the recording: our servers pass it on without storing it, and the app deletes its copy from your phone once it has been sent, or when you leave without sending it. If the app closes before then, the copy stays in the app's private storage on your phone. The app deletes it the next time you open VivaLingua. We do not send your name, email address, or any account identifier to ElevenLabs with it. ElevenLabs processes your recording and your voice model to provide this service to us. We have switched off ElevenLabs' model-improvement setting for our account, so your recording and your voice model are not used to train or improve its AI.
• What we keep: an identifier for your voice model at ElevenLabs, and a record of when you agreed and which version of the agreement you saw. The app also keeps a short preview of your AI voice on your phone until you delete your AI voice or sign out.
• How it is used: whenever you speak in a call or in-person session — one you started or one you joined — ElevenLabs speaks your translated words to the other participants, including web guests, in your AI voice. People who hear it in the VivaLingua app or on the guest page are shown an "AI Voice" label. If someone listening uses a version of the app that is too old to show that label, or if we cannot tell which version they use, your translated words are spoken in your standard voice instead. When you create it, ElevenLabs also speaks one fixed sample sentence so that you can hear it. Your AI voice is never used to speak anyone else's words, and it is not used for anything else. Some listening languages are not supported yet; listeners in those languages hear your standard voice instead.
• How long it is kept: your voice model stays at ElevenLabs until you delete it in Profile, delete your account, do not use it for 12 months (it counts as used each time it speaks one of your sentences), or do not use VivaLingua at all while signed in for 6 months, whichever comes first. In each case it stops being used at once, and we ask ElevenLabs to delete it straight away. If ElevenLabs cannot delete it at that moment, we keep retrying automatically until it confirms. ElevenLabs may keep a copy in its own backups for longer, on its own schedule, which we do not control. Speech generated in your AI voice is handled like any other translated result (section 6): ElevenLabs saves a copy of each spoken sentence, which we have deleted as soon as it is made, or within 24 hours if it cannot be deleted at once.
• Your choices: you can delete your AI voice at any time in Profile, which withdraws your agreement. Turning off your translation permission in Settings also stops it from being used, because calls and sessions cannot start without that permission; your voice model itself is kept until you delete it or one of the periods above ends.

5. WEB GUESTS

A host can invite someone with a link. The guest can join a video call, or a face-to-face conversation with the host. The guest joins from a web browser, without creating an account. Guests must be 18 or older, and the join page asks them to confirm it.

• What we collect from a guest: the name the guest types, which is shown to the host; the guest's language and voice choice; when the guest joined and was last seen; and the guest's permission for the processing described below. The browser keeps a small identifier so that the guest can rejoin from the same link. When a guest asks to join, the host's phone may be sent a notification that includes the name the guest typed.
• If a video call does not connect or stops working, the guest's browser may send us a technical report about the call, such as how far it got, any error from the video service, whether the camera and microphone could be used, which features the browser supports, the network type, the browser and operating system and their version numbers, and, if the link was opened inside another app such as Instagram or Facebook, which app. It never contains the guest's name, anything said, or the invitation link, and it is deleted after 60 days.
• At the end of every video call, the guest's browser sends us a short technical summary of how well the call worked. The summary contains only times and counts: how long the guest's sentences took to be sent and translated, how long the host's translated sentences took to reach the guest's browser and to start playing, how the browser decided where each of the guest's sentences ended, and how many translated sentences could not be played. It also contains the network type, the browser and operating system and their version numbers, and, if the link was opened inside another app, which app. In addition, for each sentence that a guest says in a video call, our servers record the two languages, how long the translation and the spoken translation took, and the country that the guest's connection came from (not the IP address). The summary and these records never contain the guest's name, anything said, or the invitation link. We use them only to measure and improve the speed and reliability of calls. We delete them after 60 days, or earlier when the guest's other records are deleted.
• A host can also invite a guest to an Audio Only call. Daily.co sends the sound of that call between the host and the guest, and there is no video. The host's screen shows each sentence that the guest said, in the guest's language, and also its translation. The guest's screen shows each sentence that the host said in the same way.
• In a call, a guest waits in the host's waiting room. The host and the guest can each see whether the other is in the room and whether they are ready to talk. When the guest's records are deleted, the record of the waiting room stays in the host's call history, but it no longer shows who the guest was.
• How a guest's speech is processed: in the same way as a user's (sections 1 and 3) — Deepgram for speech-to-text, Google Cloud Translation, Google Cloud Text-to-Speech or ElevenLabs for the spoken translation, and Daily.co when the conversation has video — and only after the guest agrees on the join page, which names each of these providers. A record that the guest agreed is kept as described in section 6. Guests cannot create an AI voice, but may hear a host's AI voice, marked with an "AI Voice" label.
• Guest records are deleted automatically 90 days after the guest's last visit, or sooner if the host deletes their VivaLingua account. A guest can ask us to delete them at any time at contact@vivalingua.app. Translated results from a guest's speech are handled as described in section 6.

6. DATA RETENTION

We retain your account data while your account is active. Upon account deletion, your personal data is removed within 30 days, except where legally required to retain it longer.

There are two exceptions, and we describe them here rather than leave them in that sentence. The first: when you agree to something — our processing of your speech (including a web guest's agreement on the join page), or the creation of an AI voice — we keep a record that you agreed: the date, which version of the text you were shown, the language it was in, and, for an AI voice, the country, and the state or region, your device connected from. We keep that record for 7 years, including after you delete your account, because the laws that require us to obtain your agreement also require us to be able to show that we obtained it, and after an account is deleted there would otherwise be nothing to show. The record contains no recording, no voice model, no message, and no readable email address — your address is stored only as a one-way code that cannot be read or used to contact you, and that we can match only if you give us the address yourself. It is deleted automatically after 7 years.

When you give consent for a demo with the AI assistant, we keep a short note of that consent. The note holds the date, which version of the consent text we showed you, the language of that text, and the version of the app. We keep the note for 7 years, as we do for your other consents.

The second: the welcome minutes offered at sign-up are given once to each person, not once to each account. When an account receives them, we store a one-way code made from its email address and, for an account created with Apple or Google, from the account identifier that Apple or Google gives us. If the account is deleted, we keep that code for 12 months after the deletion, and during that time a new account with the same email address, or with the same Apple or Google account, does not receive welcome minutes again. You can still sign up again, use the Service and buy minutes. Addresses that deliver to the same mailbox, such as an address with a "+" tag or a Gmail address written with dots, count as the same address. The code cannot be read or turned back into an address or identifier, is used for nothing else, and is deleted automatically 12 months after the account is deleted.

From version 1.1.12 of the app, the welcome minutes are also given only once to each phone. On an iPhone, the app asks Apple's DeviceCheck service for a temporary token, and we use that token to read and set a single yes-or-no mark that Apple keeps for that iPhone and our app, recording whether welcome minutes have already been given on that iPhone. We receive and keep no identifier for the iPhone, and the mark stops counting 12 months after we last set it. On an Android phone, the app sends the identifier that Android assigns to our app on that phone, and we store only a one-way code made from that identifier, kept while the account exists and for 12 months after the account is deleted. A phone is marked when an account on it receives welcome minutes, and also when an account that has already received welcome minutes is opened on it. While a phone is marked, a new account created on that phone does not receive welcome minutes; you can still sign up, use the Service and buy minutes. The mark and the code are used for nothing else.

In every version of the app, we also use the push-notification token to give the welcome minutes only once on each phone. The app sends us this token only if you allow notifications (section 1). When an account has received welcome minutes and has sent us a token, we store a one-way code made from that token. We keep the code while the account exists, and for 12 months after the account is deleted. During that time, a new account that sends us the same token does not receive welcome minutes. If a new account received welcome minutes before it sent us the token, we remove the welcome minutes that it has not used. You can still sign up, use the Service and buy minutes. The code cannot be read or turned back into the token. We use the code for nothing else, and we delete it automatically 12 months after the account is deleted.

There is one more exception. When you delete your account, we keep a short entry that shows the account was deleted. The entry holds two things: the date the account was deleted, and a code made from the account's email address. The code is not a password and cannot be used to sign in. No one can read the code. No one can work out the email address from the code. We use the entry for one purpose only: to confirm the deletion if you, or someone acting for you, ask us later. We check the code in one situation only: when you give us an email address and ask us to check it. We delete the entry automatically 2 years after the account was deleted.

Support tickets are deleted when you delete your account. Tickets marked resolved or closed are also automatically deleted 180 days after their last update. Open and in-progress tickets are retained so we can continue investigating and responding to them.

For video calls and in-person sessions, VivaLingua does not persist the source transcript. A translated result — the translated text and the spoken audio generated from it — is cached temporarily to make delivery retries safe and is normally deleted when the call or session ends. If it is abandoned, that result becomes eligible for automated deletion after 24 hours. Because automated cleanup runs daily, it may remain for approximately 48 hours. ElevenLabs saves its own copy of each translation it speaks, text and audio; we have that copy deleted as soon as it is made, or within 24 hours if it cannot be deleted at once. Processing and retention by Daily.co, Deepgram, Google Cloud Translation, Google Cloud Text-to-Speech, and ElevenLabs are also subject to those providers' terms.

A record of each spoken translation — its language, which provider spoke it, how long it took, and a fingerprint of the text used to reuse identical audio, never the text itself — is kept for 90 days to measure speed and reliability.

Diagnostic and crash records, call diagnostics, and the per-sentence records described in section 1 are automatically deleted 60 days after they are received, and are also removed when you delete your account.

Your AI voice is kept until you delete it or your account, until it has not been used for 12 months, or until your account has been inactive for 6 months, whichever comes first; section 4 explains how it is deleted at ElevenLabs. Web guest records are deleted 90 days after the guest's last visit (section 5).

For each demo you start (section 12), we keep one short entry in our database. We keep these entries until your account is deleted, and we delete them with your account.

We also make copies of our database to analyse and improve the Service. Each copy is deleted 30 days after it is made, except for the records of people who have agreed to help us test the Service. A record described in this section may therefore remain in such a copy for up to 30 days after it is deleted from the Service.

To measure whether the Service is getting faster and more reliable, and to plan prices, we keep, without a time limit, statistics and measurements that cannot be linked to anyone: for example, how long a translation took, in which language and on which app version, or how many minutes people used in a week or a month. Before we keep them, we remove every name, email address, account, call or session identifier, device identifier and exact time (keeping only the week or the month), and we keep no detail that fewer than five people share. Nothing in them says who took part in a call or what anyone said.

Email verification codes are stored only as a hash, are single-use, and expire 30 minutes after they are sent.

7. YOUR RIGHTS

You have the right to:

• Access your personal data
• Correct inaccurate data
• Delete your account and data
• Withdraw your permission for us to send your speech to the providers in section 3, at any time in Settings
• Delete your AI voice at any time, in Profile
• Export your data
• Opt out of non-essential communications
• Object to some of our processing, or ask us to restrict it
• Withdraw a consent you have given, at any time. What we did before you withdrew it stays lawful.
• Complain to the government body that oversees data protection where you live

Email contact@vivalingua.app to exercise these rights. We may ask you to confirm your identity first. Where the law allows, you can authorize another person to make a request for you. If we refuse a request, we will tell you why. You can then ask us to reconsider our decision. We will not treat you less favorably because you used your rights.

8. PERFORMANCE METRICS & APP IMPROVEMENT

To improve VivaLingua's translation speed and reliability, we collect anonymous technical performance data: response-time and speed measurements, error rates, queue and cache statistics, device type (iOS/Android only), app and OS version, connection type (WiFi/cellular), call duration in seconds, and which playback mode you used.

We explicitly do NOT collect your name, email, or any identifier; who you called or your contacts; what you said (no recording or transcription); which languages you used; your location; device IDs; IP addresses; or any session identifier that could tie a submission back to you. Submissions are never linked to your account — they are sent without any sign-in information attached.

This data is stored for 90 days and then automatically deleted, except for the statistics and measurements described in section 6, which cannot be linked to anyone. It is never shared with or sold to third parties, and is used solely to find and fix technical issues and to measure whether the Service is improving. You can turn this off anytime in Settings → Privacy → "Help improve VivaLingua," with no effect on how the app works for you. Because nothing we collect identifies you, there is no individual record to delete if you ask — see Settings for details.

This section covers only the anonymous performance data described above. The diagnostic and crash records and call diagnostics in section 1 are a separate set that IS linked to your account, so that a specific failure can be investigated and so that those records can be deleted with your account. They are retained for 60 days.

9. CHILDREN'S PRIVACY

VivaLingua is not intended for anyone under 18, including web guests. We do not intend to collect data from children. If you believe a child has used VivaLingua, email contact@vivalingua.app about it. We will delete the child's data.

10. SECURITY

We use industry-standard encryption and security practices to protect your data. Passwords are never stored in plain text: they are stored as salted PBKDF2-HMAC-SHA256 hashes with 100,000 iterations. Password-reset and email-verification codes are hashed the same way.

11. INTERNATIONAL TRANSFERS

Our servers and main database are hosted by Cloudflare in the United States. To respond quickly, Cloudflare also keeps read-only copies of the database in its data centres in other regions of the world. Your data may also be processed in other countries where our service providers operate. We ensure appropriate safeguards are in place.

12. DEMOS: PRACTICE CONVERSATIONS WITH AN ARTIFICIAL INTELLIGENCE ASSISTANT

A demo is a short practice conversation in which you talk with an artificial intelligence (AI) assistant. The app offers two demos. You do not have to use them. Each demo lasts about one minute. One demo shows a video call. The other demo shows a conversation with someone in the same room. In each demo, the AI assistant speaks a different language, and VivaLingua translates what you both say, as it does in a real conversation. The assistant is an AI, not a person. The app shows that the assistant is an AI throughout the demo. Both demos handle your data in the same way, as described below.

• Your camera: the video call demo never asks for permission to use your camera. If you have already given VivaLingua permission to use your camera, the video call demo shows the picture from your camera in a small window on your own screen. This picture stays on your device. It is not recorded, and it is not sent to us or to anyone else.
• Before a demo starts: the demos are offered only after you have given the permission described in section 3. The first screen of each demo explains that what you say will be translated and sent to an AI assistant, so that the assistant can answer you. The screen also names the companies that operate the assistant: ElevenLabs and Google. If you start the demo from that screen, you agree to have what you say sent to the assistant. If you close that screen instead, nothing is sent. We store the details of your consent. Section 6 says how long we keep them.
• What is sent, and to whom: the app records what you say and sends the recording through our servers to Deepgram. Deepgram turns the recording into text. Google Cloud Translation translates the text into the assistant's language. The translated text is sent to ElevenLabs. ElevenLabs operates the assistant with an AI model from Google, and the assistant writes a reply. Google Cloud Translation translates the reply into your language. The reply is then turned into speech. Google Cloud Text-to-Speech or ElevenLabs does this. ElevenLabs also receives the name of your language. ElevenLabs does not receive your name, your email address, or any account identifier.
• If the assistant does not answer in time, or if the assistant is not available, the demo plays a reply that was prepared in advance. In that case, what you said is still turned into text and still translated, so that the app can show it on the screen.
• What is not kept: we do not store the recording of what you said. We do not store the text of what you said, the assistant's replies, or the audio you hear in a demo. ElevenLabs does not keep the conversation after a demo ends. ElevenLabs operates the assistant in a mode that stores no data. If ElevenLabs speaks a reply, ElevenLabs saves a copy of that audio. We then tell ElevenLabs to delete that copy, as section 6 explains. Processing by Deepgram, Google and ElevenLabs is also subject to their terms.
• What we keep: for each demo you start, we keep one short entry in our database. The entry contains facts and numbers only: which demo it was, your language, the assistant's language, the app version, when the demo started and ended, how many replies from the assistant you heard, how many times you spoke, how many of your sentences the app translated, how many of your sentences the assistant answered, how the demo ended, and which option you chose afterwards. We also store one more fact: whether you closed the invitation to try the demos on the home screen. The entries do not contain anything you said, as text or as audio. We keep the entries until your account is deleted, and we delete them with your account.

13. CONTACT

For privacy inquiries: contact@vivalingua.app

Sevenfires AI LLC, Wisconsin, United States
vivalingua.app