diff --git a/duplicity-backup.conf.example b/duplicity-backup.conf.example
index a467cc0..f90f126 100644
--- a/duplicity-backup.conf.example
+++ b/duplicity-backup.conf.example
@@ -104,6 +104,16 @@ DEST="s3+http://backup-bucket/backup-folder/"
 #DEST="ssh://user[:password]@other.host[:port]/[/]some_dir"
 #DEST="file:///home/foobar_user_name/new-backup-test/"
 
+# DESTINATION BACKEND PASSWORD
+# Instead of setting the password needed for the backup destination in the
+# DEST url, you can supply it in the FTP_PASSWORD variable below, which is
+# used by most, if not all backends, regardless of it’s name.
+# Duplicity's official documentation states:
+#   "Supported by most backends which are password capable. More secure than
+#    setting it in the backend url (which might be readable in the operating
+#    systems process listing to other users on the same machine)."
+#FTP_PASSWORD="password"
+
 # INCLUDE LIST OF DIRECTORIES
 # Here is a list of directories to include; if you want to include
 # everything that is in root, you could leave this list empty (I think).
diff --git a/duplicity-backup.sh b/duplicity-backup.sh
index c926c1b..62e5d46 100755
--- a/duplicity-backup.sh
+++ b/duplicity-backup.sh
@@ -159,6 +159,9 @@ export AWS_ACCESS_KEY_ID
 export AWS_SECRET_ACCESS_KEY
 export PASSPHRASE
 export SIGN_PASSPHRASE
+if [[ -n "$FTP_PASSWORD" ]]; then
+  export FTP_PASSWORD
+fi
 
 LOGFILE="${LOGDIR}${LOG_FILE}"
 DUPLICITY="$(which duplicity)"