Privacy

By default your codes never reach a server of ours: they stay on your devices, and on Apple devices in your own iCloud. Here is everything, in plain words.

Draft, updated November 2, 2026. This policy awaits legal review, and Rotor2FA isn’t released yet. It describes how Rotor2FA is being built, not a service that is running.

The short version

  • We can’t read your codes. They’re encrypted on your device before anything leaves it, and the key never leaves your devices. Our server stores only that locked copy, has no way to unlock it, and so can’t see, use or hand over your codes, even if asked.
  • You can use Rotor2FA without an account and without giving us anything personal. By default, the only thing it sends our server is an anonymous daily usage report, and a switch turns that off.
  • On iPhone, iPad and Mac your encrypted codes are also kept in your own iCloud, and sync between your Apple devices automatically.
  • Our server is involved only if you choose it: to create the free Rotor2FA account for Windows and Android, or to get security updates by email. Even then, your accounts reach it only encrypted. It also keeps your email address and the details below.
  • No outside ads and no trackers, in the apps or on this site, and no analytics on this site. The main screen shows the companies whose engineers build Rotor2FA (ServerPoint, ColossusCloud and A+ Hosting); tapping one opens its website. The app’s anonymous usage reports go only to our own server, never to a third party.

On your devices

Your accounts, their setup keys and codes, and their names are kept in an encrypted database on each device. The key that unlocks it stays in your device’s secure storage (Keychain, Android Keystore or Windows Credential Manager). On phones and tablets, Rotor2FA can ask for Face ID, Touch ID or your fingerprint before it shows your codes.

Encrypted backup files you create are protected by a password only you know. We never see the file or the password.

Anonymous usage

Once a day, the app sends our own server a short report about the day before, so we can see what works and what breaks. It’s on unless you turn it off, in Settings › Security and privacy › Share anonymous usage. Off, nothing is sent.

  • The device: its type and model (such as iPhone 16 Pro), the system version, processor type, memory and screen size in ranges, and accessibility settings such as larger text or a screen reader.
  • The app: its version, language, theme, which settings are on, where it was installed from, and whether iCloud, a Rotor2FA account, a backup file and the lock are on.
  • Your codes, as counts only: how many you have, in ranges; how you added or imported them, and from which app; their kind (6 or 8 digits, 30 or 60 seconds); and how many belong to well-known services in Rotor2FA’s own icon list, such as GitHub or Google. Any other service is counted only as “other”, never by name.
  • How it went: how often you opened Rotor2FA, copied and searched, how fast you found a code, which screens you opened, and how many crashes, sync errors and failed imports there were.

Never in it: your codes or setup keys, account names, your email address, your Rotor2FA account, your device’s own identifier, or exact times.

The install number. The app makes one random number when it’s installed, so we can count how many people use Rotor2FA and how many come back. It isn’t your device’s identifier and isn’t tied to your account, email or Apple Account. Our server keeps it only in a scrambled form, with the days it reported, and deletes it 13 months after its last report. Deleting the app, or turning the switch off, erases it on your device; turning the switch back on makes a new one.

What we keep. Our server notes your country, from Cloudflare, and adds the report to daily totals across everyone, kept for 2 years. It never stores your report itself or your IP address, and never keeps the device model or the services beside the install number. In our own reports, anything fewer than 20 installs share (a rare model, a rare service) shows only as “Other”.

Apple and iCloud

On iPhone, iPad and Mac, Rotor2FA keeps your encrypted codes in your own iCloud (the app’s private CloudKit database) and its key in iCloud Keychain, which Apple encrypts end to end. That is how your codes reach your other Apple devices and come back after a reinstall. This data is in your Apple account, under Apple’s terms. We can’t read it or reach it.

If you sign in to the free Rotor2FA account with Apple, we receive an identifier Apple creates for Rotor2FA and the email address Apple shares, which can be a private relay address. If you allow notifications for new-device requests, our server keeps your device’s Apple push token; Apple can see that a notification was sent. It carries no details: it only tells Rotor2FA to check for changes.

If you choose our server

If you…We store
Do neither of the belowNothing that identifies you. Unless you turn it off, Rotor2FA sends the anonymous daily usage report, kept as described there. On Windows, if update checks are on (Settings), Rotor2FA fetches a small file from rotor2fa.com once a day, with no identifier; Cloudflare sees your IP address and the app version, as with any web request.
Create the free Rotor2FA accountYour email address, the language of our emails and your sign-in method; for email sign-in, a keyed hash (HMAC, made with a secret only our server holds) of a key derived from your password, never the password itself; your encrypted accounts and encrypted keys; how many there are, their size and when they change; your devices’ platforms and when each was last seen; a record of sign-ins, devices joining or removed, and recovery, with the device’s platform and, for 30 days, its IP address. The Rotor2FA account and its sync are free. Nothing is sold, so we hold no payment details.
Add an email for security updatesThe address, the language of our emails, when you confirmed it, whether you chose news and offers, and which wording you agreed to
Use either of the aboveServer logs with IP addresses, the address of each request and the app version, kept for 30 days. Email addresses, codes, tokens and encrypted data are masked in the logs.
Use either of the aboveA nightly backup copy of the data above, on our server, kept for 7 days. Your accounts in it are still encrypted.

What we never see

  • Your codes and setup keys, or the account names they belong to. The names of services are never sent; the usage report only counts codes for well-known services, and you can turn it off.
  • Your password, your spare key, or the keys that decrypt your accounts
  • Your device names, vault names, notes and icons (they’re encrypted too)
  • Whether your backup is on: backup reminders are notifications on your device, never email

Email

Giving us an email address is optional, and Rotor2FA works the same without it. We ask you to confirm the address from a link before we keep it (double opt-in).

  • Security alerts and important updates: for example, that a new device joined your Rotor2FA account.
  • News and offers, including from ColossusCloud.com, only if you ticked that separate box.

Every email has a link to stop news and offers or all email, and mail apps can unsubscribe in one click. It takes effect at once.

Who else is involved

  • Apple holds your iCloud data and delivers push notifications, as described above.
  • Cloudflare serves this site and carries our server’s traffic, including the anonymous usage reports. It sees what our server sees, including IP addresses.
  • SendGrid delivers our email. It sees the address and the message.
  • The app stores (Apple, Google, Microsoft) handle downloads and updates under their own policies.

We don’t sell or rent your data, and we don’t share it with anyone beyond those named here.

Deleting your data

  • Codes on a device: delete them in Rotor2FA, or delete the app. Deleted accounts wait 30 days in Recently deleted, then disappear from every device.
  • Your iCloud copy: remove Rotor2FA’s data in your Apple account’s iCloud storage settings.
  • Your Rotor2FA account: delete it in Rotor2FA, under Settings › Backup and sync › Your Rotor2FA account › Delete account. The deletion happens 30 days later, so a stolen device or mailbox can’t erase your account at once: every device of yours is told, any of them can cancel it, and we email you a reminder 3 days before. Then the encrypted copy on our server is erased and your other devices are signed out; the codes on your devices stay. You can also write to us (Contact) and we’ll help you delete it. If you also gave an email for security updates, that stays until you remove it.
  • Your email address: stop all email from the link in any message, or remove the address in Rotor2FA, under Settings › Security and privacy › Security updates by email. To have it erased from our records, write to us.

After a deletion, some records stay for a while. The account’s security history (sign-ins, devices joining or removed, and settings changes) stays for 90 days, without your email address (an address change keeps at most a masked form, such as a***@e***.com), so that misuse can still be looked into; IP addresses in it are erased after 30 days. Server logs stay for up to 30 days, and our nightly backups keep a copy for up to 7 days. After that, one record remains: that the account was deleted and how, with a few counts, never your email address or your accounts. Any action our staff took on the account stays in our own administrative records.

Getting a copy

With a Rotor2FA account, Rotor2FA can download everything our server holds about it: your account, your email choices, your devices (their names stay encrypted), how many vaults and accounts you have, and 90 days of security events, with IP addresses for the last 30. It never includes your codes: our server can’t read them, and they’re already on your devices.

Your rights

Wherever you live, you can ask us for a copy of what we hold about you, to correct it, or to erase it, and you can stop all email at any time. With a Rotor2FA account you can download the copy and delete the account yourself, in the app.

In the EU, the UK and Switzerland: we use your data to run the account and the email you asked for (a contract with you), to keep the service safe (our legitimate interest), for the anonymous usage report (our legitimate interest; the switch turns it off), and for news and offers only with your consent. You can complain to your data protection authority. Our server is in the United States, so your data goes there.

In California: we don’t sell or share your personal information, and we don’t treat you differently for using your rights.

Write to us (Contact); we answer within 30 days.

Children

Rotor2FA isn’t meant for children under 13, or the higher age your country sets. We don’t knowingly hold data about them. If you believe a child gave us an email address, write to us and we’ll erase it.

Cookies

This site sets no cookies. The web version of Rotor2FA keeps your data in your own browser’s storage, on your computer; nothing in it reaches us unless you use the Rotor2FA account.

Changes to this policy

If we change this policy in a way that matters to you, we’ll say so in the app, or by email if you gave us one, before the change applies. The date at the top shows the last change.

Contact

Rotor2FA is provided by Intelligence Software Labs, a business name of A+ Hosting, Inc. (a Nevada company), 10620 S Highlands Pkwy, Suite 110-491, Las Vegas, NV 89141, USA. Write to us at that address.