Aplomo
Effective date: September 27, 2026. Ad measurement with Meta applies to the iPhone app from version 1.3.0.
Aplomo is an app for practicing public speaking by arguing out loud against an AI rival. We built it to ask for as little as possible: no account, no ads inside the app, and we never sell your data for money. On iPhone, from version 1.3.0, we measure our own ads on Meta, and your advertising identifier is only shared if you allow tracking.
✅ No account or sign-in. We never ask for your email.
✅ Aplomo never records or stores your voice. Your phone's built-in speech recognition (Apple or Google) turns it into text.
✅ Your profile, sessions, scores and transcripts are stored only on your device.
✅ To create the rival's replies and your feedback, the text of your practice is sent, with your consent, through our proxy to a third-party AI provider. We don't store it. Your name never leaves your phone.
✅ No ads inside the app. On iPhone, from version 1.3.0, the Meta SDK measures which of our ads on Facebook and Instagram bring people to Aplomo. Meta only gets your advertising identifier if you allow tracking in Apple's prompt, and if you say no, the app works exactly the same. What you say, your scenarios, scores and name never go to Meta.
✅ We never sell your data for money, and we don't use it to train AI models. (Under California law, what the Meta SDK sends may count as “sharing”: see section 4.)
Aplomo is operated by Eduardo Javier Crovetto Hartmann, Calle Carles Cervera 14, ground floor, 46003 Valencia, Spain (“we”, “us”). For any question about this policy or your data, email hola@tryaplomb.app.
During setup we ask for your name (optional), whether you work or study, your role or field of study, the skill you want to improve, when you tend to get tongue-tied and what's at stake, so scenarios fit your situation. These details are stored on your device. Your name is never sent, to the AI or anywhere else. The rest may be included in AI requests (see below). We don't ask for your age; if you entered it in an earlier version of the app, the app has deleted it.
When you speak, your device's speech recognition service (Apple's on iOS, Google's on Android) converts your voice into text. Depending on your device and settings, this may happen on Apple's or Google's servers, under their privacy policies. Aplomo only uses the resulting text. We never record, store or upload your audio, and it never reaches our servers or the AI provider.
To generate the rival's objections, your scores, custom scenarios and your reports, Aplomo sends:
Never your name or your audio. This goes over an encrypted connection to our own proxy, hosted on Vercel, which forwards it to a third-party large-language-model provider, Ollama (Ollama's cloud API).
We ask for your explicit consent before the first request. The app shows you what's shared and who processes it, with a link to this policy, and only continues when you tap “I agree — continue”. If you installed Aplomo before this change, you'll see the same screen once, the next time you open the app. Until you agree, the app makes no AI requests. The time you agreed is stored only on your device. You can withdraw this consent anytime in Profile › “Sharing with the AI”.
Our proxy does not store prompts or responses. It logs only the model name, the response status and how long the request took. We don't use your data to train AI models.
To read the rival's reply out loud, the text of that reply is sent through our text-to-speech proxy (also hosted on Vercel) to Microsoft's neural text-to-speech service, which returns the audio. Only the rival's line is sent. Because the AI writes that line in response to you, it may repeat or refer to what you said. Our proxy doesn't save that line in any database, but it travels in the request address: Vercel's network may cache the generated audio for up to 24 hours, keyed by that address, and its technical logs may keep the request for a short time.
Your sessions, transcripts, scores, streak, XP, badges, report, custom scenarios and profile are saved locally on your device so you can track your progress. They are never uploaded to our servers. On Android, app backups are disabled. On iOS, this data may be included in your own device backups (such as iCloud Backup) if you have them turned on.
Subscriptions to Aplomo Pro are paid through Apple (App Store) or Google (Google Play). We use RevenueCat to validate purchases and unlock Pro, identified by an anonymous app ID created on your device. RevenueCat receives that ID and your purchase and subscription status. On iPhone, from version 1.3.0, it also receives the anonymous ID that the Meta SDK creates (see below), your IP address, your device's identifier for vendor (IDFV, an ID Apple gives the apps of each developer on your device) and, only if you allow tracking, your advertising identifier. If you allow tracking, RevenueCat sends Meta, from its servers, when your free trial turns into a paid subscription and each renewal, with the amount and currency, linked to those identifiers, so we know which ads bring subscribers. If you don't allow tracking, RevenueCat sends Meta nothing. In versions of the app where purchases aren't available, RevenueCat isn't used. We never see your card or payment details.
Aplomo shows no ads inside the app, but we do advertise Aplomo on Facebook and Instagram. To know which of those ads bring people to the app, the iPhone app includes the Meta SDK, a software kit from Meta. It starts when you open the app and sends Meta:
The events carry nothing else: what you say, your transcripts, scenarios, scores, reports, profile details, your name and your audio are never sent to Meta. The app attaches nothing else to its own events, and we keep Meta's automatic data-collection options (automatic advanced matching, suggested and codeless events, and automatic logging of in-app purchases) turned off.
You decide about tracking. Before Apple's prompt appears, the app explains what it's for: at the end of setup or, if you were already using Aplomo before version 1.3.0, in a one-time notice. If you say no, the app works exactly the same. If you've turned off “Allow Apps to Request to Track” on your iPhone, Aplomo doesn't ask and treats it as a no.
Whatever you choose, Apple's SKAdNetwork may also tell Meta whether an install came from one of its ads, without saying who you are. We only see aggregated statistics in Meta's tools (for example, how many installs or trials a campaign brought), never who you are. You can change your choice at any time in Settings › Privacy & Security › Tracking on your iPhone, or in Profile › “Ad tracking” in the app. The Android version of Aplomo doesn't include the Meta SDK.
For collecting these events through the SDK and passing them to Meta, we and Meta Platforms Ireland Limited are joint controllers under Meta's Controller Addendum. Once Meta receives them, Meta is an independent controller and uses them under its own privacy policy, which also explains how to exercise your rights with Meta.
Like any web host, Vercel necessarily processes your IP address when the app contacts our proxies. Our AI proxy also uses it to rate-limit requests and prevent abuse. On iPhone, from version 1.3.0, Meta and RevenueCat also receive it, as described above.
No account details, no email, no location, no contacts and no photos. The only advertising SDK in Aplomo is Meta's, in the iPhone app from version 1.3.0 (see above). Your advertising identifier is only collected on iPhone, and only if you allow tracking; the Android version doesn't include the Meta SDK and doesn't collect it.
We use the following providers and send each one only what it needs to do its job for Aplomo. Meta is different: once it receives its data, it's an independent controller (see “Ad measurement with Meta”).
| Provider | What it receives | Why |
|---|---|---|
| Vercel | Requests to our AI and text-to-speech proxies (including your IP address); visits to this website | Hosting this site and our two proxies |
| Ollama | The text of your practice and the situations you describe, scenario or interview details, stats on how you speak, your work/study status, role and goal | Generating the rival's objections, scores, custom scenarios and reports |
| Microsoft | The rival's generated line | Neural text-to-speech voice for the rival |
| RevenueCat | Anonymous app ID, purchase and subscription status; on iPhone, from version 1.3.0, also the Meta SDK's anonymous ID, your IP address, your IDFV and, only if you allow tracking, your advertising identifier | Validating purchases and managing Pro access; on iPhone, if you allow tracking, reporting trial conversions and renewals to Meta |
| Meta | On iPhone, from version 1.3.0: the app events, device and app information, IP address and anonymous ID described above; your advertising identifier only if you allow tracking. Never your practice content, scores or name | Measuring and improving Aplomo's own ads on Facebook and Instagram |
| Apple / Google | Your voice, via the system speech recognition service; your purchase | Speech recognition and payments |
Each provider handles this data under its own privacy policy.
We never sell your personal information for money. We don't show ads in Aplomo, we don't build profiles about you and we don't use your data to train AI models. However, on iPhone, from version 1.3.0, the Meta SDK sends Meta the events and device information described in section 2 so we can measure our own ads. Under California law (CCPA/CPRA), giving this to Meta, especially your advertising identifier when you allow tracking, may count as “sharing” personal information for cross-context behavioral advertising, and possibly as a “sale”.
You can opt out at any time by not allowing tracking in Apple's prompt, or by turning it off in Settings › Privacy & Security › Tracking or Profile › “Ad tracking”. Then neither Aplomo nor Meta gets your advertising identifier, and RevenueCat stops sending your subscription events to Meta. The Meta SDK still sends the events described in section 2 without that identifier, which we use only to measure our campaigns in aggregate; to stop that too, delete the app. The Android version doesn't include the Meta SDK.
Our website (tryaplomb.app) doesn't use cookies, analytics or ad trackers, so there's nothing for a browser's Do Not Track or Global Privacy Control signal to turn off there, and we don't respond to those signals differently. The app isn't a browser and doesn't receive them. On iPhone, the equivalent control is Apple's tracking permission, and Aplomo follows it: if you don't allow tracking, neither Aplomo nor Meta gets your advertising identifier, and RevenueCat doesn't send your subscription events to Meta.
If you allow tracking, a third party, Meta, can collect information about your activity in Aplomo over time and link it with your activity in other companies' apps and websites (see section 2). Even if you don't allow it, the Meta SDK still sends Meta the events described in section 2, without your advertising identifier.
Depending on where you live (for example, California, other US states, the EU or the UK), you may have rights to access, correct or delete your personal information and to opt out of its “sharing” (see section 4), and we won't treat you differently for using them. EU and UK users may also complain to their local data protection authority.
If you are in the EU or UK: we process this data to provide the service you ask for (Art. 6(1)(b) GDPR). Sending your practice to the AI provider also relies on your explicit consent (Art. 6(1)(a)), which we ask for before the first request, and optional features such as notifications rely on your consent too. You can withdraw your AI consent in Profile › “Sharing with the AI” (your history stays), with Reset progress or by deleting the app; the app won't use the AI again until you agree again, and withdrawing doesn't affect processing that already happened.
Ad measurement with Meta on iPhone relies on two legal bases. Sharing your advertising identifier with Meta, and RevenueCat sending your subscription events to Meta, rely on your consent (Art. 6(1)(a)), which you give or refuse in Apple's tracking prompt and can withdraw at any time in Settings › Privacy & Security › Tracking or in Profile › “Ad tracking”. The rest (the events, device information, IP address and anonymous ID that the Meta SDK sends without your advertising identifier) relies on our legitimate interest in knowing whether our advertising works (Art. 6(1)(f)). To keep that balanced, no practice content, profile details or name go to Meta, and we only see aggregated results. You have the right to object to it at any time (Art. 21 GDPR). The app doesn't have a separate switch for this, and because Aplomo has no accounts we can't identify your device to switch the SDK off from our side, so the way to stop it completely is to delete the app. You can also write to us with any objection or question. If you have a Facebook or Instagram account, Meta also lets you control, in its Accounts Center, how it uses the activity that businesses share with it (the setting is called “Activity from other businesses” or “Your activity off Meta technologies”, depending on your region).
Data on your device stays there until you reset your progress or delete the app (see section 6). Our proxies don't store the text you send or the AI's responses; they keep only the minimal operational logs described above, plus the temporary cache (up to 24 hours) of the rival's audio and Vercel's technical logs described in “The rival's voice”. RevenueCat keeps your purchase record, with the identifiers described in “Subscriptions and purchases”, for as long as needed to manage your subscription, and Apple or Google keep your purchase history under their own policies. Meta keeps the data it receives under its own privacy policy. On iPhone, the markers that stop the Meta events from being sent twice stay on your device until you delete the app.
All communication between the app, our proxies and our providers uses encrypted connections (HTTPS). Data on your device is protected by your device's own security, such as your passcode. No system is perfectly secure, but keeping your data on your device means there's very little of it anywhere else.
Our providers may process data on servers in the United States, the European Union or other countries, whose data protection laws may differ from those where you live. In particular, Meta may transfer the data it receives to Meta Platforms, Inc. in the United States, which is certified under the EU-U.S. Data Privacy Framework.
Aplomo is intended for users 16 and older and is not directed to children. We do not knowingly collect personal information from anyone under 16. If we learn that we have collected personal information from someone under 16, we will delete what we hold and, where we can identify it, ask RevenueCat and Meta to delete theirs. If you believe a child has used Aplomo, contact us at hola@tryaplomb.app.
If we update this policy, we'll change the effective date at the top of this page and, if the change is significant, let you know in the app. Adding ad measurement with Meta is one of those changes: from version 1.3.0, the iPhone app shows people who were already using Aplomo a one-time notice about it.
Contact hola@tryaplomb.app