Passify

Sync Basics

Passify offers the ability to sync it's data securely between multiple devices. This can be used in cases such as where you need to have the ability to generate your passwords from more than one device, or need to share passwords with family members.

You can configure sync on your own terms using a Sync Provider of your choice. Passify's synchronization functionality doesn't require you to give a 3rd-party access to your data, and all data is encrypted before leaving your device.

Passify can sync in the background Passify will check if it needs to sync each time you use it. For timely syncing, leave Passify running in the background. Your device's operating system will decide when it is okay for Passify to perform its sync.

Single-device Sync as backup is not recommended If you use Passify to generate your Sync Provider password and you lose access to Passify (device is lost or was reset) and don't have a second sync device, you will not be able to generate your Sync Provider password to restore from sync. For this reason, it is recommended that you sync multiple devices and/or regularly backup your Generator data. Be sure to move your backups to a safe loation off of your device.

Sync Providers

Simply put, a Sync Provider is a place where your store an encrypted copy of your data. All of your devices connect to your Provider and use the shared data so that they can all generate your same passwords.

Instead of utilizing a centralized Cloud database under someone else's control, Passify operates on the principle of file-based syncing. Each device maintains a copy of the database independently, and handles the processes of merging incoming and outgoing changes, updating the data on your Sync Provider as needed.

This abstraction allows Passify to theoretically use any system that can store and retrieve a small file as a Sync Provider for sharing data between devices.

Passify already contains a number of Sync Provider plugins for popular file hosting systems, but we hope to add additional Provider plugins in the future.

Which Sync Provider should I choose?

The choice is up to you. Tehnically speaking, it doesn't matter. Each Provider essentially works the same way with Passify and your Sync Data is always encrypted before being sent to the Provider.

You can switch Providers at any time. If you decide you don't like your chosen Provider, switching is simple and requires only a few steps.

Most Providers offer a free-tier that is sufficient for Passify and some can even be self-hosted, completely eliminating the need for a 3rd-Party:

Provider Free Tier Considerations
Amazon S3 No
S3 Compatible (Self-Hosted) Yes
  • Requires server, S3 compatible software and security certificate
Dropbox Yes
  • Uses Open Authorization (OAuth)
  • Passify access is limited to its own folder
Google Drive Yes
  • Uses Open Authorization (OAuth)
  • Passify access is limited to its own folder
  • App folder is not visible or accessible by account holder
FTPS No
FTPS (Self-Hosted) Yes
  • Requires server, FTPS software and security certificate
iCloud Yes
  • No credentials required
  • Passify access is limited to its own folder
  • Only allows syncing between devices under the same iCloud account
  • Can seem slow to propagate to other devices
MEGA Yes
Microsoft OneDrive Yes
  • Uses Open Authorization (OAuth)
  • Passify access is limited to its own folder
SSH No
SSH (Self-Hosted) Yes
  • Requires server, SSH software and security certificates

Storage Requirements

Passify's storage requirements are extremely low. Around 2 KiloBytes per Generator is all that is required.

That means 200 Generators would require less than 1 MegaByte of storage space. To put that into perspective, Dropbox's free account tier (currently) offers 2 GigaBytes of free storage space. That's enough room for Passify to store over 1 million Generators.

Provider Credential Storing

Some providers require storing of login credentials. Please see the Frequently Asked Question "How are my credentials for Amazon S3, FTPS, SSH, and MEGA stored?" for information on how these credentials are stored.