Privacy
Updated November 19, 2026
FamilyFi is software a household runs itself: a server on its own network, which manages internet access through the household's UniFi gateway, and the FamilyFi app, from the Apple App Store for iPhone, iPad, Mac and Apple Watch and from Google Play for Android and Wear OS, which talks to that server. FamilyFi is made by Nick Berardi, "the developer" below. This policy covers the FamilyFi server, the FamilyFi app on every platform, FamilyFi Me (the app for a child's phone, see Children), FamilyFi support and this website. Apple and Google handle the app's download and installation under their own privacy policies.
What the developer receives
Nothing about your household. FamilyFi has no FamilyFi cloud and no account with us, and has no analytics, advertising, crash reporting or tracking of its own. The server and the app never send the developer your household's names, rules, devices or activity.
On Android, the pairing code scanner is Google's (ML Kit, in Google Play services), which sends Google device and app information, such as the phone's model, OS and app version, and an identifier for diagnostics and usage analytics, as described in ML Kit's data disclosure. You can paste the pairing code instead of scanning it. The iPhone, iPad and Apple Watch app uses no such service: it scans with Apple's VisionKit, on the device.
If you turn on phone alerts, your server sends each alert through the developer's push relay at push.getfamilyfi.com, which hands it to Apple or Google to deliver. Each alert is locked with a key that only your phone and your server hold, so the relay cannot read it. The relay receives your phone's push address, the locked alert, an id for your server and the time, and your home's internet address as any website does. It keeps none of them and logs nothing about the alerts it carries, only a count of deliveries Apple or Google refused. Apple and Google see that your phone received an alert and when, not what it says.
If you email [email protected], the developer receives your email: your address, your name if your email program sends it, and what you write. Cloudflare delivers it to the developer's email inbox and to a private, access-restricted record in the developer's GitHub account, and it is used only to answer you. Ask at the same address and it will be deleted.
What your FamilyFi server connects to
Your server only reaches out for these jobs. Your household's information goes only to your own gateway, and to Ubiquiti or the remote access service where you choose them below:
- Your UniFi gateway, to read its list of devices and write FamilyFi's firewall policies: directly on your network, or through Ubiquiti's cloud if you chose that in setup, in which case Ubiquiti carries that information under its own privacy policy.
- GitHub, to check for FamilyFi updates and download them when you install one. The check sends no household information and no identifier; like any website, GitHub sees your home's internet address. When you first install FamilyFi, Docker also downloads its database and updater from Docker Hub.
- The DNS services your network uses, or that you add in FamilyFi, to report whether they block each category of websites. It looks up sample website names from each category, and nothing else.
- FamilyFi's push relay, only if you turn on phone alerts, to deliver them to your phones. Alerts are locked so that only your phones can read them (see above).
- Remote access, only if you turn it on. With the Quick tunnel or Cloudflare options, the app's connections from away from home pass through Cloudflare's network, and Cloudflare handles them under its own privacy policy; the Cloudflare option also uses your own Cloudflare account. With Tailscale or your own domain, they go through a service or setup you run yourself.
Where your data lives
The names, groups, rules, devices and schedules you set up are stored in your household's own FamilyFi server and database, under your control. The server reads the list of network clients from your UniFi gateway and writes firewall policies to it, named after your rules and, for a pause, the person it pauses, using the key you enter, which it stores encrypted. FamilyFi on the web loads nothing from other websites.
The app's own connections go only to your household's server: over HTTPS, pinned to that server's certificate or checked against your phone's trusted certificates, at home and away from home through the remote access your household sets up. Pairing information and sign-in tokens are kept on the phone in the platform's secure storage. The phone sets up a watch over Apple's or Google's own phone-to-watch connection, which on Android may pass through Google's servers, and the watch then talks to your server itself. Unpairing the phone, or revoking it under Pair Device in FamilyFi on the web, ends its access, and its watch's.
Permissions the app asks for
- Camera (iPhone and iPad): to scan the pairing code. On Android, Google's code scanner needs no permission.
- Local network: to reach your household's server on your home network.
- Live Activities (iPhone) and notifications (Android): to show a timed pause's countdown on your device.
- Notifications: for the reminders and phone alerts you turn on. Your phone's push address goes only to your household's server, and from there with each alert to the push relay.
Deleting your data
Your data is on your own server, so you delete it there: remove a person or device, or revoke a paired phone, in FamilyFi on the web, or remove the server and its database. Before removing the server, delete your groups and rules in FamilyFi so it takes its firewall policies, which can carry people's names, off the gateway; if the server is already gone, delete the leftover FamilyFi policies in UniFi. Unpairing the app, or revoking the phone in FamilyFi on the web, ends its access. To have a support email deleted, write to [email protected].
The public demo
The demo at demo.getfamilyfi.com shows a made-up household that every visitor shares, and the app can pair with it. It runs on Microsoft Azure, keeps nothing between restarts and resets nightly. Don't enter personal information there.
This website
getfamilyfi.com is served by GitHub Pages through Cloudflare, which both keep standard server logs, and loads fonts and icons from Google Fonts and unpkg. It sets no cookies and has no analytics.
Children
FamilyFi is for the adults who administer a household's network. What a household enters about its members is kept on its own server and gateway, and the developer receives none of it.
FamilyFi Me is an app a parent can put on a child's iPhone or iPad. It shows the child their own rules, pauses and schedule, and the household things a parent shares with them, such as the TV, and lets them ask a parent for more time. A parent pairs it from FamilyFi with a code, for the child's group: the child has no account with FamilyFi or with us, and signs in to nothing.
- Where it connects. Only to the household's own server, as the parent's app does: on the home network, or away from home through the remote access the household set up. Its pairing information and sign-in tokens are kept on the phone in the platform's secure storage.
- What it reads. The child's own group: its name, its pause, its schedule, the rules that apply to it, and the name of the parent who paused it or answered an ask. It also reads the things a parent marked Kids can ask: their names, whether they are blocked, and the rules that apply to them. It cannot see anyone else's group or the household's settings.
- What it sends. When the child asks for more time, the ask goes to the household's server, which shows it to the parents in FamilyFi and, if they turned phone alerts on, sends it to their phones through the push relay, locked as described above. On an iPhone or iPad it also tells the household's server whether Screen Time is allowed for it (on, turned down, or taken away), and the server notes when the phone last checked in. It does not collect the child's location, contacts, messages, browsing or app use, and has no analytics, advertising, crash reporting or tracking.
- Screen Time (iPhone and iPad). If a parent allows it, FamilyFi Me uses Apple's Screen Time to block the phone's apps while the child's internet is blocked: during a pause, and during an internet rule's times, at home and away. A parent allows it on the child's phone with their own Apple Account, through Apple's Family Sharing. FamilyFi Me works out these times on the phone from the child's schedule each time it is opened, and Screen Time keeps them on the phone, so a pause a parent starts while the child is out reaches the phone's apps the next time FamilyFi Me is opened: FamilyFi Me doesn't read which apps the child has or uses, and Apple does not share that with FamilyFi Me, the household's server or the developer. While Screen Time is on, only a parent can remove FamilyFi Me.
- What parents see. In FamilyFi, the phone's name, when it last connected, whether Screen Time is on, and the child's asks and their answers. If phone alerts are on, parents can be told when a child asks, when Screen Time is turned off on the phone, and when the phone hasn't checked in for a day.
- Permissions. The camera, to scan the pairing code (the code can be pasted instead); the local network, to reach the household's server at home; Screen Time, if a parent allows it; and notifications, so that the Ask button on a blocked app can leave a notice that opens FamilyFi Me. Its notifications are made on the phone itself: no push address leaves it.
- Removing it. A parent can remove it under Pair Device in FamilyFi on the web or in the app, or on the child's page. Deleting the child's group in FamilyFi signs it out too. While Screen Time is off, the child can also remove it in the app. Removing it ends its access, and FamilyFi Me then stops blocking apps on the phone. Deleting the app removes what it kept on the phone.
Changes
When this policy changes, the date at the top changes with it.
Contact
Questions about this policy: email [email protected]. See Support for other ways to get help.