Privacy Policy
This privacy policy is about the FairAuth app. Visits to this website are covered by the website’s own privacy policy. Privacy policy of this website
FairAuth for iPhone and iPad
Last updated: 14 October 2026
The essentials
FairAuth keeps your codes encrypted on your devices. There is no FairAuth account, no analytics, no tracking and no advertising, and we never receive your codes. We receive no data from the app itself; only if you allow it in your device’s settings does Apple provide us with crash reports and aggregated usage figures (see “Crash reports”). FairAuth only connects to Apple: to iCloud if you turn on iCloud Sync, and to the App Store for purchases.
Controller
BYTEPOTATO UG (haftungsbeschränkt)
c/o Daniel Ference Broek
Kurze Str. 6
37073 Göttingen
Germany
Email: contact@bytepotato.com
On your device
- Your accounts (names, setup keys, notes, images, tags) are stored encrypted (AES-256). The key is protected by the Secure Enclave of your device and can only be used after Face ID, Touch ID or your device passcode.
- Face ID and Touch ID are handled by iOS. FairAuth never receives biometric data.
- The camera is only used to read QR codes. Nothing is recorded or saved.
- Settings such as the lock time or the list view are stored on the device and contain no personal data.
- Your codes are not part of the iPhone backup: they are protected by a key that never leaves the device. That’s why FairAuth offers its own backups.
iCloud Sync (optional)
If you turn on iCloud Sync, every account is encrypted on your device before it is stored in the private iCloud database of your Apple Account. The key stays in your iCloud Keychain. Apple stores the encrypted data and processes technical information such as the number and size of entries and the time of changes; neither Apple nor we can read the contents. Apple’s privacy policy applies to iCloud. You can turn off iCloud Sync at any time and delete the data in iCloud.
Backup file (optional)
The backup file is encrypted with your backup password and saved to the place you choose, for example a USB drive or a cloud storage service. For storage with such a service, its privacy policy applies; it only receives the encrypted file.
AutoFill (optional)
If you turn on FairAuth for AutoFill in the iOS settings, the app gives iOS the website and the name of accounts that have a website, so iOS can suggest the right account. This stays on your device. Codes and setup keys are never passed on.
Browser extension for Firefox and Chrome (optional, Mac only)
If Firefox or Chrome is installed on your Mac, FairAuth for Mac places a small file in that browser’s folder that tells the browser where FairAuth is; you can turn this off under Settings › Security › Other Browsers. When you click FairAuth in the browser, press its shortcut, or a code field appears on a website you allowed, the extension passes the name of the current website (for example login.github.com, without the path) to FairAuth on the same Mac. After Touch ID or your login password, FairAuth answers only for the accounts saved with that website, with their name, user name and the code that is valid right now; setup keys are never passed on. So that FairAuth doesn’t ask for Touch ID on every page with a code field, it keeps a list of the saved websites on your Mac, only as checksums, without names and without codes. When you click “Assign in FairAuth” in the extension, it passes the website’s name to FairAuth so you can choose the right account there. The extension has no internet access, stores nothing and sends nothing to us or to third parties. Whether it may show the FairAuth button in code fields is a permission you grant once for all websites; the browser manages it, and you can withdraw it there at any time.
Import and export
Files from other apps are read on your device only. A file you export yourself leaves the device only where you send it; an export without a password contains your codes unprotected.
Purchases
The free trial and the full version are purchases through Apple’s App Store. Apple handles the payment; we receive no personal data. The purchase status is provided on your device by iOS.
Crash reports
If you turn on “Share With App Developers” in the iOS settings under “Privacy & Security” > “Analytics & Improvements”, Apple may provide us with crash reports and usage statistics, aggregated or in a form that does not personally identify you. We use them only to fix errors.
Deletion
Deleting the app removes your accounts from this device. Data in iCloud remains until you delete it in FairAuth or in the iOS settings for iCloud. Backup files stay where you saved them.
Your rights
Since FairAuth does not send personal data to us, we hold no data about you that we could disclose, correct or delete. You nevertheless have the rights under Articles 15 to 21 GDPR and the right to lodge a complaint with a data protection supervisory authority (Article 77 GDPR). For questions, write to contact@bytepotato.com.
FairAuth for Mac
Last updated: 14 October 2026
The essentials
FairAuth keeps your codes encrypted on your devices. There is no FairAuth account, no analytics, no tracking and no advertising, and we never receive your codes. We receive no data from the app itself; only if you allow it in your device’s settings does Apple provide us with crash reports and aggregated usage figures (see “Crash reports”). FairAuth only connects to Apple: to iCloud if you turn on iCloud Sync, and to the App Store for purchases. On the Mac, FairAuth has no permission to open network connections of its own.
Controller
BYTEPOTATO UG (haftungsbeschränkt)
c/o Daniel Ference Broek
Kurze Str. 6
37073 Göttingen
Germany
Email: contact@bytepotato.com
On your Mac
- Your accounts (names, setup keys, notes, images, tags) are stored encrypted (AES-256). The key is protected by the Secure Enclave of your Mac and can only be used after Touch ID or your login password.
- Touch ID is handled by macOS. FairAuth never receives biometric data.
- To read a QR code on the screen, you choose a window or the screen in a dialog of macOS. FairAuth reads one picture of it in memory and keeps nothing. FairAuth does not need permission to record the screen.
- FairAuth’s windows are left out of screenshots, screen recordings and screen sharing.
- Settings such as the lock time or the list view are stored on the Mac and contain no personal data.
- Your codes are not part of a Time Machine backup: they are protected by a key that never leaves the Mac. That’s why FairAuth offers its own backups.
iCloud Sync (optional)
If you turn on iCloud Sync, every account is encrypted on your Mac before it is stored in the private iCloud database of your Apple Account. The key stays in your iCloud Keychain. Apple stores the encrypted data and processes technical information such as the number and size of entries and the time of changes; neither Apple nor we can read the contents. Apple’s privacy policy applies to iCloud. You can turn off iCloud Sync at any time and delete the data in iCloud.
Backup file (optional)
The backup file is encrypted with your backup password and saved to the place you choose, for example a USB drive or a cloud storage service. For storage with such a service, its privacy policy applies; it only receives the encrypted file.
AutoFill (optional)
If you turn on FairAuth for AutoFill in System Settings, the app gives macOS the website and the name of accounts that have a website, so macOS can suggest the right account. This stays on your Mac. Codes and setup keys are never passed on.
Browser extension for Firefox and Chrome (optional)
If Firefox or Chrome is installed on your Mac, FairAuth for Mac places a small file in that browser’s folder that tells the browser where FairAuth is; you can turn this off under Settings › Security › Other Browsers. When you click FairAuth in the browser, press its shortcut, or a code field appears on a website you allowed, the extension passes the name of the current website (for example login.github.com, without the path) to FairAuth on the same Mac. After Touch ID or your login password, FairAuth answers only for the accounts saved with that website, with their name, user name and the code that is valid right now; setup keys are never passed on. So that FairAuth doesn’t ask for Touch ID on every page with a code field, it keeps a list of the saved websites on your Mac, only as checksums, without names and without codes. When you click “Assign in FairAuth” in the extension, it passes the website’s name to FairAuth so you can choose the right account there. The extension has no internet access, stores nothing and sends nothing to us or to third parties. Whether it may show the FairAuth button in code fields is a permission you grant once for all websites; the browser manages it, and you can withdraw it there at any time.
Import and export
Files from other apps are read on your Mac only. A file you export yourself leaves the Mac only where you send it; an export without a password contains your codes unprotected.
Purchases
The free trial and the full version are purchases through Apple’s App Store; one purchase applies on iPhone, iPad and Mac. Apple handles the payment; we receive no personal data. The purchase status is provided on your Mac by macOS.
Crash reports
If you turn on “Share with app developers” in System Settings under “Privacy & Security” > “Analytics & Improvements”, Apple may provide us with crash reports and usage statistics, aggregated or in a form that does not personally identify you. We use them only to fix errors.
Deletion
Deleting the app does not remove its encrypted data from your Mac: macOS keeps it in your user folder under Library > Group Containers > group.com.bytepotato.fairauth, and you can delete that folder. Data in iCloud remains until you delete it in FairAuth or in the iCloud settings of your Mac. Backup files stay where you saved them.
Your rights
Since FairAuth does not send personal data to us, we hold no data about you that we could disclose, correct or delete. You nevertheless have the rights under Articles 15 to 21 GDPR and the right to lodge a complaint with a data protection supervisory authority (Article 77 GDPR). For questions, write to contact@bytepotato.com.