The short version
- No ads, analytics or trackers.Not on this website, and not in our apps.
- We don't sell or share personal information.We don't use it for advertising or to build profiles.
- Your Handbrake journal stays yours.It lives on your device and, if you use iCloud, in your own iCloud account. Mafua, LLC has no server that receives it and can't read it.
- Location only when you ask for it.While you record a drive, or once when you check the weather before one.
- Family sees only what you share.Invited family members get a read-only view. Routes and reflections stay private unless you turn them on.
- Aloe calls go straight between phones.They're encrypted end to end. Captions are made on the speaker's own iPhone, and only the words travel. Nothing is recorded.
- Aloe's server doesn't know who you are.It helps phones ring and connect using random codes. It never receives names, phone numbers, emails, voices or words.
Who we are
Mafua, LLC (“Mafua”, “we” or “us”) makes the mafua.com website and the apps listed on it. This policy covers the website, Handbrake, Aloe and Hopscotch. When we add an app, we'll add a section for it here.
Some features rely on Apple services, such as iCloud, Apple's push notifications and the App Store, and Handbrake uses the National Weather Service for weather. Apple handles its services under Apple's privacy policy. Aloe also uses Cloudflare to run its small server and to relay calls that can't connect directly, under Cloudflare's privacy policy. This policy explains what our apps send to those services and why.
The mafua.com website
The website has no accounts, forms, cookies, analytics or advertising, and it doesn't load scripts or fonts from other companies.
It's hosted on Amazon Web Services. As with any website, the hosting service receives the technical information your browser sends with each request, such as your IP address, browser type and the page you asked for, so it can deliver the page and protect the service. We don't use this information to identify you or to build a profile of you. If we turn on hosting access logs, we use them only for security and troubleshooting and delete them within 90 days.
On the Aloe page, what you type into “Try it” is turned into a pretend caption in your browser. It isn't sent anywhere.
Links to other sites, such as the App Store, take you to services with their own privacy policies.
Handbrake
Handbrake is a road journal for learner drivers and the family members they invite. You don't need an account with us to use it. There is no Handbrake server, sign-in, analytics or advertising code, and no third-party software libraries. The app talks only to Apple services. Links to outside pages, such as Florida's licensing requirements, open in your browser.
What Handbrake keeps
- Your profile: your name, an optional emoji or photo for your avatar, the name of your usual supervising adult, your state and practice goals, the date your learner permit was issued if you enter it, and your reminder and sharing settings.
- Your drives: date and times, practice intervals, daytime and nighttime minutes, a title, and the supervising adult's name and confirmation. For drives you record with GPS, Handbrake also keeps the route (positions with time, speed and accuracy), weather conditions recorded along the way, possible firmer braking or acceleration estimated from GPS speed, a count of how often the phone moved, and an optional short reflection on the drive.
- A drive in progress, so it can be recovered if the app closes.
- A short session history of up to 200 entries, each with a date, the type of event, a random session ID and a count of route points. It helps recover and troubleshoot drives. It contains no names, locations or sensor readings, it isn't included in device backups, and it never leaves your device.
If you choose a photo for your avatar, Handbrake uses Apple's photo picker, so the app sees only the photo you pick. It keeps a small 256-pixel copy without the photo's original details, such as where it was taken.
Where it's stored
- On your device, in Handbrake's private storage, protected by iOS data protection. It's included in your device backups.
- In your iCloud. If you're signed in to iCloud, Handbrake syncs your profile and completed drives to your private iCloud database using Apple's CloudKit. Drives in progress stay on your device. Your private iCloud database is stored by Apple, and Mafua, LLC can't access it. Your profile is stored in CloudKit's encrypted fields, and drives are stored as iCloud assets that Apple encrypts. How the encryption keys are protected depends on your Apple Account settings, such as Advanced Data Protection. See iCloud data security overview.
- In your iCloud Drive, only for spreadsheet and JSON exports you choose to save there (Files › iCloud Drive › Handbrake › Exports).
You can use Handbrake without iCloud. Recording and PDF export still work, but sync, family sharing and saving exports to iCloud Drive need an iCloud account.
Location and motion
- Recording a drive: with your permission, Handbrake uses precise location while you record a drive, including when the phone is locked. iOS shows its location indicator while this happens. Location is used to record your route, distance and speed, and to work out how much of the drive was in daylight or at night. Tracking stops when you pause or finish.
- Checking the weather: before a drive, the weather postcard takes one approximate location reading, accurate to about a kilometer, to fetch nearby station observations. That weather-request location isn't saved separately.
- Motion: during a drive, Handbrake uses the phone's motion sensors to notice when the phone itself moved, which lowers its confidence in braking and acceleration observations. Motion readings aren't saved, only a count.
Braking and acceleration observations are estimates from changes in GPS speed. They aren't a safety score and don't judge your driving. You can change location and motion permissions at any time in Settings › Privacy & Security.
Services Handbrake uses
- National Weather Service (NWS): for the weather postcard and about every ten minutes during tracking, Handbrake sends approximate coordinates (rounded to two decimal places) directly to api.weather.gov to find nearby station observations. NWS receives the requested location and your network IP address under its privacy policy. NWS may retain request URLs, IP addresses, timestamps and request-status information in service logs for operation, usage analysis and security. No learner name, account or session identifier is sent. Handbrake uses an in-memory network cache and saves the observation, timestamp, station identifier and source with the drive; it does not save the weather-request coordinate separately. Earlier development/test weather is no longer displayed or used. NWS is the only weather source.
- Apple Maps (MapKit): showing a route or map loads map images from Apple, so Apple receives the map area being displayed. This happens in any app that shows an Apple map.
- iCloud (CloudKit): for sync and family sharing, as described here.
- Apple Intelligence: on supported devices, Handbrake writes a short reflection on a drive using Apple's on-device language model. Only summary observations are used, such as practice time, event counts and weather conditions, never names, addresses or route locations. The processing happens on your device. Where the model isn't available, Handbrake uses a simple built-in explanation instead. No cloud AI service is used.
- App Store: for optional tips, described below.
Family sharing
Family sharing is off until you invite someone. Invitations use iCloud's private sharing. Only the people you invite, who accept with their own Apple Account, can see your shared journal, and they can't edit it, add drives or control your sessions.
- What they see: your name, your state and practice goals, and your completed drives: title, date and times, practice intervals, daytime and nighttime minutes, and the supervising adult's name. They can also save or print a PDF practice log of what you share.
- Only if you turn it on: routes and finished reflections. These settings apply to everyone you've invited.
- Never shared: weather readings, braking and acceleration observations, phone-movement counts, drives in progress, your avatar, and your permit date.
You can remove people with iCloud's share controls in Handbrake, or stop sharing completely, which deletes the shared copy for everyone. Copies someone already saved or printed can't be recalled. If you're the one invited, Handbrake shows the shared journal while you're viewing it and doesn't keep its own copy.
Exports and printouts
You choose when to export, which dates to include, and where the file goes.
- PDF practice log: your name and state, and each drive's date, start and finish times, supervising adult, and daytime, nighttime and total minutes. For Florida, it can include the official, unmodified certification form, with signature lines left blank.
- Spreadsheet (XLSX) and JSON: the same practice-log details, plus drive titles and practice intervals. They leave out routes, weather, motion observations, reflections, deleted drives and drives in progress, and they're saved to your iCloud Drive.
Once you share or print a file, it's in your hands. If you give it to a licensing office such as the Florida Department of Highway Safety and Motor Vehicles, their policies apply.
Optional tips
Tips are optional and unlock nothing. Apple processes them through the App Store, and we never see your payment details or Apple Account. Handbrake doesn't keep a record of your tips. Apple gives us sales reports that don't identify you.
Notifications and Live Activities
The only notification Handbrake sends is an optional reminder to finish a drive after a long stop. It's scheduled on your device, not sent from a server, and contains no name or location. Handbrake doesn't use push notifications.
While you record a drive, a Live Activity can show elapsed time, distance, and whether you're driving in daylight or at night on your Lock Screen and in the Dynamic Island. It contains no names or locations, but anyone who can see your Lock Screen can see it. You can turn Live Activities off in Settings.
Aloe
Aloe makes video calls you can read: the other person's words appear as live captions while they talk. It's made first for people who are deaf or hard of hearing. There's no form to fill in and no password: you sign in once with Apple, and Aloe's server never gets your name or email. Aloe has no advertising or tracking code, and its server counts only totals. Calls use WebRTC, an open-source library for calls that talks only to the other phone and the services described here.
Your Aloe identity
Aloe has no phone numbers or passwords. The first time you invite someone or accept an invite, Aloe creates a set of encryption keys on your iPhone and keeps them in your iCloud Keychain, so your other Apple devices are the same you. If iCloud Keychain isn't available, the keys stay on that device. Aloe's private keys never leave your devices. Your keys stay in your keychain if you delete Aloe, so installing it again keeps you the same person to your contacts.
- Your profile: your name (if Apple shares it at the sign-in, Aloe fills it in for you to keep or change) and an optional emoji or photo for your avatar, your caption settings, and the languages you speak. If you choose a photo, Aloe uses Apple's photo picker, so the app sees only the photo you pick, and keeps a small 256-pixel copy. These sync to your other devices through your iCloud account.
- Your people: each contact's name, avatar emoji, public keys and the codes that let you ring each other, and your open invites. They sync to your other devices through your private iCloud database (CloudKit), which Mafua, LLC can't access.
You can use Aloe without iCloud. Everything then stays on that one device.
Calls and captions
- Calls go straight between phones, encrypted end to end. Each phone proves it holds the keys of the person you saved before the call connects. When a network won't allow a direct connection, Cloudflare relays the call, passing along encrypted data it can't read.
- Captions are made on the speaker's iPhone. When the person you're talking to turns on captions, your iPhone turns your speech into text with a speech model that runs on the device: NVIDIA's, on iPhones that can run it, or Apple's speech recognition. Only the text is sent, over the call's encrypted connection, to the other phone. Your voice is never sent anywhere to be transcribed. A label on your screen shows while your phone is making captions.
- Nothing is recorded. Aloe doesn't record audio or video. Captions are kept in memory during the call, so you can scroll back, and they're gone when it ends.
- Each phone sees the other's network address, as in any call that goes straight between devices, unless the call is relayed.
What Aloe's server keeps
A small server, run for us by Cloudflare, helps phones ring and connect, then steps aside. It doesn't know who you are: it never receives your name, your phone number, your email, your contacts' names, or anything said in a call, and it never keeps your Apple Account. It keeps:
- A scrambled code for your sign-in: when you first open Aloe, you sign in once with Apple. Aloe doesn't ask for your email. Apple may share your name with the app, which only fills in the name your people see; it never reaches the server. The server turns the sign-in into a scrambled code that can't be reversed, keeps only that code, and throws the sign-in away. Sign-ins made earlier with Google are kept the same way. The code only sets how much you can do, such as how many calls you can start in a day.
- Proof you're a real device: Aloe asks Apple to confirm it's running on a real iPhone (App Attest), then gets anonymous passes that let you make calls and invites without the server knowing who is calling. The server keeps the key that proves it, with your sign-in's code.
- A coded account ID: a one-way hash made from a secret on your devices. It groups your devices together and can't be turned back into the secret or linked to you.
- Your devices: a random ID for each install of Aloe and the push token Apple gives it, so the server can ring your iPhone when Aloe is closed. A device is forgotten when Apple reports its token no longer works, such as after you delete Aloe.
- Ring codes: random codes, one for each person you've added and each open invite, linked to your coded account ID. Someone can ring you only with a code you gave them. A code is deleted when you remove or block that person, or cancel the invite.
- Calls that are ringing, for up to a minute, and missed calls, for up to 7 days or until one of your devices has shown them: the call's random ID, the ring code and the time. Not who called. Your iPhone works out who it was from its own contacts.
- Invite replies: when someone accepts your invite, their reply waits on the server until your phone collects it, for up to 48 hours. It's encrypted so that only your phone can open it.
- Call setup: while a call connects, the server passes connection details between the two phones, including their network addresses. It keeps a call's setup for up to a few minutes, and temporary relay passwords until they expire.
- Technical logs: Cloudflare keeps records of requests to the server, which can include network addresses, for up to 7 days. We use them only to fix problems.
- Counts: the server counts events in total, such as how many calls rang today. The counts carry no codes, addresses or names.
Deleting your account
Settings → Delete account removes your key, your people and your invites from all your devices, and the server forgets your coded account ID, your ring codes and your devices. So that you can set Aloe up again, your phone shows the server your sign-in's scrambled code as it deletes, and the server gives back what setting up cost. That's the only moment it sees your sign-in and your Aloe account together, and it keeps nothing that ties them. Your sign-in's code is forgotten after a year unused.
Invites and nearby phones
- Invite links carry your name, your avatar emoji, your public keys and the codes needed to reach you. The invite is in the part of the link after the “#”, which browsers never send to a server, including when the link opens Aloe's small web page for people who don't have the app yet. Each invite works once, within 48 hours, and anyone who has the link can use it, so send it only to the person you're inviting.
- On the same Wi-Fi, while Aloe is open, your iPhone announces itself to other phones with Aloe on that network, so your people can call you directly: your name, your avatar emoji, a random ID and a short fingerprint of your public key. Aloe stops when it's closed. Only your people can ring you, wherever you are.
Permissions
- Camera and microphone, so the person you call can see and hear you, and so your phone can make captions of your speech.
- Speech recognition, to turn your speech into captions on your iPhone.
- Local network, to find your people on the same Wi-Fi.
- Notifications, to tell you who called when you missed a call. These notifications are written on your phone from your own contacts. The server's push to ring your phone carries only a ring code and a call ID, never a name.
You can change these at any time in Settings. Calls ring on the iPhone's own call screen, with the name you saved for the caller, and Aloe keeps them out of your Phone app's call history.
Services Aloe uses
- iCloud (Keychain, CloudKit and key-value storage): for your keys, your people and your settings, as described above.
- Apple Push Notification service: to ring your iPhone when Aloe is closed. Apple receives your device's push token and the ring code and call ID in each push.
- Sign in with Apple: to sign in once, without sharing your email. If you let Apple share your name, it stays with the app and the people you call.
- App Attest: Apple's check that Aloe is running on a real iPhone.
- NVIDIA's speech model, from Hugging Face: on iPhones that can run it, Aloe downloads the model (about 600 MB) once, from Hugging Face, which sees your device's network address when it does, as any website would. Aloe sends it nothing else. The model runs on your iPhone: your voice is never sent to it or anyone else to be transcribed.
- Apple speech recognition: on iPhones that can't run NVIDIA's model, and on the others until it has downloaded. It runs on your iPhone, and iOS downloads the language models it needs from Apple.
- Tips, through Apple: tips are optional and unlock nothing. Apple handles the payment; we see only Apple's sales totals, never your name or card.
- Cloudflare: runs Aloe's server, helps phones find a way to connect, and relays calls that can't connect directly.
Hopscotch
Hopscotch is a collection of board, word, sport and arcade games for solo play or matches between nearby devices. There are no accounts, ads, analytics, tracking libraries or Hopscotch servers. Internet access isn't required to play.
What stays on your device
A friendly adjective/noun/three-digit player name is generated once and saved. You can edit it. Your name, sound and haptic choices, paddle controls, match length and computer difficulty are saved in the app's local preferences. Match state is kept in memory while you play; it isn't saved as a history or restored after you close the app. Deleting the app removes its local preferences, subject to device backups.
What nearby players can see
When you open Find a nearby player, Hopscotch uses Apple's Multipeer Connectivity to advertise your chosen player name, a protocol version and a random identifier to nearby devices. Your name is visible during discovery, so use a nickname rather than private information. You choose whom to invite, and the other player must accept.
A room holds up to four people. Invitations include the current roster of player names and random room identifiers; room members see that roster. Invitations, game selections and session heartbeats travel through encrypted Multipeer Connectivity connections. The room host’s device relays moves, scores, pause/resume and rematch messages only to the people in that match. An inactive host still relays those messages; other inactive room members receive no gameplay packets. They aren't sent to Mafua, LLC or a game server. In Battleship, the hidden fleet stays on its owner’s device. Readiness sends a salted fleet commitment, and turns exchange only shot coordinates, results and sunk ship outlines. The fleet and salt are revealed to the other player after game over to check that the results match. Advertising stops when you connect. The room host continues browsing for people to invite while there is room and no match is underway. Returning to the arcade keeps the room together. Leaving, backgrounding or losing connection removes that person and returns the remaining room to the arcade. If the host leaves or loses connection, the room closes. No room or match history is retained.
Permissions and services
Local Network access is used to find and connect to nearby players. Keep Wi-Fi and Bluetooth enabled; you don't need to join a Wi-Fi network. Solo play works without this permission. Hopscotch doesn't request your location, contacts, camera, microphone, photos or notifications, and doesn't use iCloud to sync its preferences.
If you use TestFlight, send support email, or choose to share diagnostics through Apple, the general sections below explain what Mafua may receive. None of that adds an in-app analytics or tracking service.
What Mafua, LLC receives
This is the complete list:
- Emails you send us. We use them to answer you.
- TestFlight beta information. If you join a beta, Apple shares the name and email address you were invited with, the devices and builds you install, and any feedback, screenshots and crash reports you choose to send. We use it only to run the beta and fix problems.
- Crash reports and diagnostics. If you turn on Share With App Developers in Settings › Privacy & Security › Analytics & Improvements, Apple may share crash reports and usage diagnostics with us. Apple doesn't link them to your name.
- App Store reports. Apple gives developers summary information such as downloads, tips and countries. It doesn't identify you.
- Aloe's server records. The coded account ID, random device IDs, push tokens, ring codes, missed-call times, encrypted invite replies and technical logs described in What Aloe's server keeps. We use them only to make calls ring and connect.
We don't receive your driving journal, your location, your photos, your family's information, your contacts, anything seen, said or captioned in an Aloe call, or your Hopscotch player name and match data.
No selling, sharing or ads
We don't sell personal information, share it for cross-context behavioral advertising, use it for targeted advertising, or use it to build profiles. We don't work with data brokers. Our apps don't track you across other companies' apps and websites, so they never ask for App Tracking Transparency permission.
We disclose information only when the law requires it, and only information we actually have.
Keeping and deleting data
- A drive: deleting it in Handbrake removes its details. To keep your devices in sync, iCloud keeps a small deletion marker with a random ID and the time of deletion, and nothing else.
- Everything on a device: deleting the app removes its data from that device. Device backups made earlier still contain it until those backups are replaced or deleted.
- Everything in iCloud: in Settings, tap your name, then iCloud, then the storage settings, and choose Handbrake to delete its iCloud data. Exports in iCloud Drive can be deleted in the Files app.
- Family sharing: stopping sharing deletes the shared copy for everyone you invited.
- Aloe's people and settings: removing someone in Aloe deletes them from all your devices and deletes their ring code from the server. Your people and settings in iCloud can be deleted the same way as Handbrake's, by choosing Aloe in iCloud's storage settings.
- Aloe's server records: kept only as long as described in What Aloe's server keeps. Because the server doesn't know who you are, we can't find your records from your name or email. Remove your people in Aloe to delete their codes.
- Hopscotch: local preferences are removed when you delete the app, subject to device backups. Match state is held only in memory. There is no Hopscotch account or server record to delete.
- Emails and beta feedback: we keep them only as long as we need them to help you and to run the beta, then delete them.
Teens and children
Handbrake is for learner drivers, who are usually teenagers, and the adults who supervise them. It isn't directed to children under 13, and Mafua, LLC doesn't knowingly collect personal information from children under 13. A learner's journal stays on their device and in their own iCloud, so we don't receive it at all.
Hopscotch can be played with family members. It has no accounts or chat. A chosen player name is visible to nearby players while looking for a match; use a nickname and accept invitations only from someone you intend to play with.
Aloe is for families too, and children may be on calls, but it isn't directed to children under 13. Aloe's server never receives names, faces, voices or words, so it holds no personal information about anyone on a call.
If you think a child under 13 has sent us personal information, email privacy@mafua.com and we'll delete it.
Security
Handbrake stores your journal with iOS data protection and syncs it only to your own iCloud account, over Apple's encrypted connections. Mafua, LLC runs no server that holds your journal, so there's no Handbrake database to break into.
Aloe encrypts calls end to end and checks, before a call connects, that the other phone holds the keys of the person you saved, so even someone in control of the server couldn't listen in. Invite replies are encrypted so only your phone can read them, and the server holds no names or messages to steal.
Hopscotch requires encrypted Multipeer Connectivity sessions for nearby matches and sends no game data to Mafua. The player name used for local discovery is visible to other nearby devices.
No storage or transmission method is perfectly secure, so protect your device with a passcode and your Apple Account with two-factor authentication.
Your choices and rights
Your Handbrake journal is in your control. You can view, correct, export and delete it in the app and in iCloud, choose what family members see, and change permissions in Settings. In Aloe, you choose who can ring you, and you can rename, block or remove anyone.
Depending on where you live, privacy laws may give you the right to know, access, correct, delete or get a copy of your personal information, to object to or restrict some uses, to opt out of sale, sharing, targeted advertising or profiling, and not to be treated differently for using these rights. We extend these rights to everyone, wherever you live.
For information Mafua, LLC holds, such as emails or beta feedback, write to privacy@mafua.com. We may need to confirm the request came from you, and you may use an authorized agent where the law allows. We'll respond within the time the law requires, which is usually 30 to 45 days. If we turn down a request, you can appeal by replying to our decision, and you can also contact your local privacy or consumer protection authority.
We don't sell or share personal information or use it for targeted advertising, so there's nothing to opt out of. Browser signals such as Global Privacy Control are respected automatically.
Privacy laws and platform rules
Here's how our practices relate to the main privacy rules that may apply:
- Apple App Store guidelines
- Handbrake explains why it needs each permission, uses data only for the feature you're using, and includes no third-party software libraries. Its privacy manifest declares no tracking and no data collected by us. Aloe explains each permission too, and every call push it receives rings on the iPhone's call screen. Its App Store privacy details list what its server keeps, and declare no tracking.
- Children's privacy (COPPA)
- Neither Handbrake nor Aloe is directed to children under 13, and we don't collect personal information from them. See Teens and children.
- U.S. state privacy laws, including California (CCPA/CPRA)
- We don't sell or share personal information or use it for targeted advertising. Precise location, which some state laws treat as sensitive, is used only to record the drives you ask Handbrake to record, and it stays on your device and in your iCloud. Aloe turns speech into text only on the speaker's phone and keeps no recordings or voiceprints. The rights described above apply to everyone.
- EU and UK data protection (GDPR and UK GDPR)
- Handbrake processes your journal on your device and in your iCloud, under your control. Aloe's calls and captions go between your phones, and your people and settings stay in your iCloud. For the limited information Mafua, LLC receives, Mafua, LLC is the controller. We process Aloe's server records because they're needed to provide the calls you ask for, and we rely on legitimate interests to answer you, run betas and fix problems, and on your consent for crash reports you choose to share. We are based in the United States, and our service providers, Apple, Amazon Web Services and Cloudflare, may process information in the United States and other countries.
Changes to this policy
If we change this policy, we'll update the date at the top. If a change affects how your information is handled in a meaningful way, we'll explain it on this page and, where appropriate, in the app before it takes effect.
Contact
Mafua, LLC
privacy@mafua.com