Login
Login

Frequently Asked Questions

Help Center > Frequently Asked Questions

Types of FAQ's

GDPR

Yes, ElephantDrive is GDPR compliant!

We are an active participant of the Privacy Shield Framework. The Privacy Shield Framework guarantees that data transferred from the EU to the USA benefits from the same level of protection.

We have conducted a thorough internal audit reviewing our practices and our compliance.

We have also updated our Privacy Policy to reflect our GDPR compliance.

As a company, ElephantDrive places a high value on privacy and transparency.

So, let’s start by making a couple of things clear about how we protect your data:

  • We collect and process a limited amount of Personal Identifiable Information (PII)
  • We only collect and process PII that is necessary to provide the services our users sign up for:
    • Email and name for logging in and getting in touch
    • Payment info for paying for your plan, and…
    • That’s it
  • We do not sell any of this information
  • We do not share any of this information
  • We only host, store, or interact with this PII on secure systems provided by partners that also comply with our standards, including GDPR.  Examples of such providers are our payment processing solution, our customer support ticketing solution, our email delivery solution, and our infrastructure solutions.

All other data stored by users in their accounts is encrypted during transit and at rest, and is absolutely private (https://support.elephantdrive.com/hc/en-us/articles/205537248-How-is-my-data-secured-at-ElephantDrive-).

Our partners/resellers share our privacy concerns and comply with GDPR. We have subscribed to their updated policies put in place to guarantee GDPR compliance.

Yes. We have everything in place to guarantee that you can use our services to provide GDPR compliant services:

  • We are GDPR-compliant (click here for more information).
  • Your data (or your users’ data if you are a reseller) is encrypted on the user devices, travels via secure protocols, and is stored encrypted. Click here for more information on how your data is secured at ElephantDrive.
  • We are Privacy Shield certified so the data we store on your behalf benefits from the same level of protection in the USA and in the EU and can be securely transferred from the EU to the USA.

From then on, all you have to do is make sure that you comply with your own GDPR requirements.

ElephantDrive only collects “general” Personally Identifiable Information (PII) that is strictly necessary to provide our services to our end-users:

  • Name and Surname
  • Email Address
  • Phone Number
  • Payment-related information:
    • Card Type, Number…
    • Billing Address

ElephantDrive collects this PII when you register for an account and subscribe to use our services.

We do not collect any other type of PII!

As for the data our users back up, store, or share using our services, it is encrypted on the user’s device, travels via secure protocols, and is stored encrypted. For more information on how your data is secured at ElephantDrive: https://support.elephantdrive.com/hc/en-us/articles/205537248-How-is-my-data-secured-at-ElephantDrive-.

Most of our data is stored and processed in the USA. This is why we enrolled in the Privacy Shield Framework for our EU users to guarantee equivalent levels of data protection.

Our partners who help us store and process data are equally compliant with GDPR requirements.

Our service and solution providing partners share our privacy concerns and comply with GDPR. We have subscribed to their updated policies put in place to guarantee GDPR compliance:

We only store Personally Identifiable Information (PII) as long as strictly necessary, i.e. as long as you are an active user of our services.

Upon cancellation, the user’s encrypted data is queued for deletion and purged from our servers within a couple of weeks. We only keep the user’s email address as a cancelled user. Payment information is deactivated and the user is unsubscribed from our email delivery system. No additional processing of personal information is done after cancellation.

As an ElephantDrive user, you have the right to:

  • Access your Personal Identifiable Information (PII).
  • Correct errors related to your PII.
  • Delete personal data.
  • Export PII.
  • Refuse data processing (cancel).

Here is how we implement and guarantee that our users enjoy these rights:

All other Data Access Requests may be directed to dar@35.83.19.187.

Despite only collecting and processing very limited Personally Identifiable Information (PII), we have decided to appoint a Data Protection Officer (“DPO”). (Mainly due to the number of users we service and to guarantee maximum confidence for our users).

Our DPO can be reached at dpo@35.83.19.187.

Getting Started

Important: Please ensure you have correctly installed the ElephantDrive app on your device and logged into the app using your registered account information before managing/configuring backup settings.

Configure and Manage Backup Settings

  1. Click here to login to our user web portal.
  2. Navigate into the Backup Settings tab, then click Manage Device Backups.
  3. Select your device from the drop down menu.
  4. You can edit an existing backup job or add a new backup job.

Getting started with ElephantDrive is fast and easy. First, download and install the ElephantDrive application client on your Windows or Mac device. Once installed, launch ElephantDrive and you will be greeted with a step-by-step guide.

  1. After launching ElephantDrive, you will be asked if you already have an ElephantDrive account or need to create a new one. If you already have an ElephantDrive account, simply choose this option and click Next. If you need to create a new account, you can create one via the app or from the Plans Page.
    Screen Shot 2015 08 28 at 3.58.07 PM
  2. Enter your preferred email address and a password and then click Next.Screen Shot 2015 08 28 at 3.58.18 PM
  3. Choose a plan that you would like to begin with and click Next.1
  4. A folder named My ElephantDrive will be created on your device. Choose a location or use the default location to create this folder and then click Next.
    2
  5. By default, ElephantDrive will select to backup anything on your Desktop and all music and picture files. You can also check Documents to backup all document files on your device. Additionally, you can click New Backup to target any folder on your device to be backed up. When ready, click Next.
    4
  6. Great, your backups ready! We are almost done, but let’s get you familiar with the basic features of ElephantDrive.
  • You can drag or paste any file/folder into the My ElephantDrive folder on your device (we created that folder in step #4) and it will be backed up to your ElephantDrive cloud account.
    5
  • Inside the My ElephantDrive folder is a folder called Everywhere. Anything you put in this folder is synched first to your ElephantDrive cloud account and then synced to the Everywhere folder on any other devices you have connected to your account. 6
  • You can also access your ElephantDrive account online through any device with internet connection. Additionally, you can upload files and manage your backups from anywhere.
    7
  • The ElephantDrive App will just run in the background. If you need to make any changes to your backups, just click the ElephantDrive Icon in the Taskbar on Windows or Menu on Mac.
    8
  • You are all done! Sit back and relax now that you know your important data is being protected by The Herd!9
  1. Login to our user web portal, http://vault.elephantdrive.com/account/login.aspx.
  2. Navigate into the Files tab.
  3. Click into My Computers.
  4. Check the box to select the corresponding device, then click the trashcan icon to delete the device. Or, you can right-click the device and select delete in the context menu. A deleted device and its data (backups) is first moved into your trash folder which must be emptied to finalize the deletion.

Windows, macOS, and Linux, along with the suite of supported NAS platforms require no additional software when running ElephantDrive version 6.0 and above.

 

*Earlier versions required 32-bit Java, version 1.6 or higher (even on a 64 bit machines).

For Users behind a proxy ElephantDesktop may need a bit of info to get passed it. To configure your Proxy settings in ElephantDesktop:  

1. Go to the login screen that comes up when starting ElephantDesktop when you are not logged in:

467c52e4441deb082786bb97ce82a60c972bc73ecf17166524fa3bd66ac5e049

This may mean logging out of your account if needed.

2. Click on the “Configure proxy” link in the login window. This will bring up a second smaller window that will allow you to input your proxy settings:

3071394400e879779f77c0b79654fcb10507a8b9b299e88f5169499a9e66ff6e

3. From there put in the name of your proxy, the port your proxy uses and a user name and password if needed.

Get started with your ElephantDrive online backup and storage account by following these simple steps:

  1. Download the ElephantDrive cloud backup software for free here.
  2. Install the software and sign in. If you haven’t set your password, you can request a new one here.
  3. Start backing up.  Simply right-click on the file/folder you would like to back up and select ‘Add to Backup’ (for PC users); or drag and drop your file/folder into the ‘Backup’ folder within ‘My ElephantDrive’ folder (for Mac users). 
  4. You can access and manage your backups from anywhere by logging in to the website.

There are many more things you can do with your ElephantDrive account. Check out our features to learn more.

Features

ElephantDrive will mark a file/folder as “archived” when the file/folder is deleted from the local device. (The file/folder will also be archived if it has moved from its original location or if it gets renamed.)

Example:

Let’s say you have a file labeled “invoice.pdf” backed up to ElephantDrive from your computer. Then, you delete the “invoice.pdf” file from your computer. Your ElephantDrive backup job will recognize that the file no longer exists at its original location (deleted) and will archive the file in your ElephantDrive account.

Archived files can be retained indefinitely or for a specified number of days. To change how long to retain archived files, please edit your backup settings. (Click here to learn how to modifying your backup settings.)

ElephantDrive backups are incremental. When a file is backed up, ElephantDrive will keep its most recent copy (current version). If the file is modified, ElephantDrive will detect that the file has changed, then upload the modified file and keep the previous version of the file.

Example:

Let’s say you have a text document (file) backed up to ElephantDrive and you decided to make some edits to the text document (i.e. adding more paragraphs, changed formatting, etc.). Once you save the edits, ElephantDrive will upload the modified file with the edits as the most recent copy of the file, but it will also keep the previous copy of this file as a version in your ElephantDrive account.

Settings:

How many versions are kept and for how long can be changed by modifying versioning rules. To change how long to retain versions, please edit your backup settings. (Click here to learn how to modifying your backup settings.)

What is it? The Everywhere folder allows you to synchronize data across multiple devices.

How does it work? When you install the latest version of ElephantDrive on a Windows, Mac, or Mobile (Android/iOS) device, it will automatically create a folder labeled Everywhere on that device. Any files and folders placed inside the Everywhere folder on one device will automatically get synced to the Everywhere folder your other devices. You must have the latest version of ElephantDrive to ensure the Everywhere folder functions properly.

Where is it? You can find the Everywhere folder inside your ElephantDrive folder.

Multiple users (sub-accounts) each with unique login credentials can be administered through one ElephantDrive (main, parent) account. There are two types of sub-accounts.

  • Workgroup Sub-Account
    Workgroup sub-accounts share the same access level as the main account. A workgroup sub-account is essentially a distinct set of login credentials to the same account as its parent. This sub-account is ideal if you need multiple logins to the same account, but data security between parent and sub-account is not an issue (as everybody can see all files in the account).

  • Independent Sub-Account
    Each Independent sub-account has its own access level that isn’t shared with the parent or other workgroup/independent sub-accounts. They are essentially a free-standing account that can be administered through the parent account. Independent sub-accounts do not have access to any objects in the parent account. An independent sub-account is ideal if you need storage, access, or protection for multiple users, but would like to separate access so the parent and sub-accounts don’t have access to each others’ backups.

Sub-accounts can be created by navigating into the My Account tab in our user web portal.

Sharing

File Sharing allows you to quickly share files with friends and colleagues (no more emailing files or transferring over thumb drives)! You can share any file that has been uploaded to your account. A file is shared via a url link. 

  1. Log-in to your account at https://vault.elephantdrive.com/account/login.aspx 
  2. Navigate to the file that you would like to share and select the file.
  3. Once you’ve selected the file, click “Get Shared Link“.

 Screen_Shot_2013-08-20_at_7.07.28_PM.png

 

      4. An url link will be generated. You can share this url with your friends/colleagues. You can also add a password to this url link for extra protection.

 Screen_Shot_2013-08-20_at_7.14.37_PM.png

The ElephantDrive service allows for backup, storage, sync and share functionalities. 

It is not designed nor intended for mass distribution or commercial use. It is not designed to operate as a Content Delivery Network (CDN) or a Content Management System (CMS).

This means that ElephantDrive is very well suited to share files and folders between family members, friends or employees of business.

However, it won’t be the right tool to distribute files to a large number of users or host files for a website or other use. 

For this reason, we monitor bandwidth usage on a general basis. 

In specific cases, we may review bandwidth usage for individual users. One of the triggers for such reviews is bandwidth use vs plan capacity (ie using more bandwidth than the storage associated with your subscription).

This is considered over a period of several months, meaning that it’s not going to be an issue if you go over for a month (Multiple uploads + restores). However, we will most likely get in touch if your bandwidth usage repeatedly goes over your storage capacity.

With our new Collaborative Sharing features, you can now share a folder with your colleagues or friends.  They will need to sign up for their own ElephantDrive account (don’t worry – we make this easy and free).  Once they do so, they can view, edit, and delete files within the shared folder.

One important note before we begin – please make sure the folder you want to share is contained somewhere inside your “Everywhere” folder.  Our synchronization magic only operates inside of Everywhere. So, you cannot share a folder that is not in your Everywhere folder.   Let’s begin…

 

1. First, navigate to your Everywhere folder:

Screen_Shot_2012-08-23_at_1.51.32_PM.png

 

2. Next, select the folder that you’d like to share. I’ve chosen to share the folder !!!!!WTEST

3. Once you’ve selected the folder that you want to share, click “Share Folder” above.

Screen_Shot_2012-08-23_at_1.54.53_PM.png

 

4. Once you click “Share Folder“,  the sharing window will appear:

Screen_Shot_2012-07-02_at_11.32.28_AM.png

 

5. Write in the email address(es) of people you want to share the folder with and add a personal message if you would like.  Once you’ve shared the folder with them, a confirmation page will appear, saying “The folder has been shared successfully”:

Screen_Shot_2012-07-02_at_11.34.44_AM.png

6. The members (people whom you’ve shared the folder with) will be notified of the shared folder via email.

Hi,

Soandso@gmail.com has invited you to a shared folder called “Folder I’d like to Share”.

View “!!!!!WTEST”

 
 

We’re taking sharing to a whole new level!

In addition to our tried and true links sharing (aka “Links“) that allows you to send files to a friend for quick and easy download, we’ve launched a new way for you to share information with friends, colleagues, or business partners in a more collaborative way called Folder Sharing. 

It is a very simple and fast way to fully share the contents of a folder – both you and the people you share with will be able to access the files, add to it, and make edits, and all the updates will be available to all the people sharing as soon as you save changes.  It’s a pretty neat tool for collaborating or just seamlessly delivering files to others with ElephantDrive accounts. If someone does not have an ElephantDrive account, no worries; we’ve designed a quick 2-step process for them to get a Free ElephantDrive account. And it’s available right now for you to test it out!

There are two ways you can take advantage of Folder Sharing.

  1. You can share folders from version 5.1.0 of the ElephantDrive Desktop Client. Just click on any folder from the ElephantDrive client, then click Share. 
  2. Or you can share folders online from the beta version of the online web interface (it has a great new look and feel that we think you’ll enjoy). Click on a folder that you would like to share, then click Share.

You can find our step-by-step How-To-Share-Folder guide.

What is a Shared folder?: A Shared folder is often used to collaborate on a project with colleagues/friends and have the changes everyone makes on the project synched on everyone else’s devices (just like Google Docs, if you’re familiar with that). 

 

How do I start?: In order to take full advantage of all the sharing features available, you need to install ElephantDrive on your computer. You can install ElephantDrive by visiting here: http://home.elephantdrive.com/download/.

 

  • Once you’ve installed ElephantDrive, it will create a special folder called Everywhere on your machine. All shared folders are placed inside the Everywhere folder.
  • The email you received will have a subject ,”yourfriend@xyz.com wants to share ‘Name of Folder’ with you.  Select, “view ‘Name of Folder‘”.  If you are not already logged in, the login screen will appear.  Please login.
  • Next you’ll be asked to Accept or Decline the shared folder.

 

Screen_Shot_2012-07-25_at_11.13.40_AM.png

 

 

  • Once you select “Accept“, you will see the accepted folder and the users it’s being shared amongst.

Screen_Shot_2012-07-25_at_12.54.00_PM.png

 

  • You’ll notice that the shared folder is now in your Everywhere Folder.  Simply select the folder you’d like to open and you’ll see all the files inside it that are accessible to you.
  • You can now add new files or make changes to the existing ones. All changes will be automatically synced to all the members’ devices. 

Access & Restore

  1. After launching and connecting your destination device to ElephantDrive, please login to our user web portal, http://vault.elephantdrive.com/account/login.aspx.
  2. Navigate into the manage device backups section in the Backup Settings tab. 
  3. Select a device from the dropdown menu, edit any backup job, and click into the Includes tab.
  4. In the Includes tab you should find a backup path which will show the correct path formatting which can be used to format a destination path when restoring data to the same device. All paths are case and spelling sensitive.

This article provides a brief overview of how you can restore your data from ElephantDrive after a ransomware attack. If haven’t been affected by ransomware, but still need to restore your data, then please skip to the section below outlining the steps to configure a restore job.

It is important to understand what happens to your data in ElephantDrive when your original files are locked by ransomware. 

  • The ransomware encrypts your files (locking them) and ultimately renames them with a different file extension. 
  • The result of the file name changing will prompt ElephantDrive to “archive” the file in your ElephantDrive account. 
  • Your archived files/folders will serve as the clean backups of your data and can be restored by configuring a restore job. 

Steps to Configure a Restore Job

  1. Login to our user web portal, http://vault.elephantdrive.com/account/login.aspx.
  2. Navigate into the Files tab and right-click a folder and select “restore folder.”
  3. Select the destination device. (ElephantDrive must be running on the destination device in order for the restore to work.) Click “Next” to configure restore settings.
  4. View https://support.elephantdrive.com/hc/en-us/articles/1260806193170-Overview-Restore-Settings for an overview of the restore settings. Most importantly, please select to include archived files and the “most recent” for the point-in-time setting.  
  5. Manually restart the ElephantDrive client. Your restore job will start after the ElephantDrive client is manually restarted at your destination device.
  • Related Article: https://support.elephantdrive.com/hc/en-us/articles/4408951190811-How-Do-I-Find-the-Correct-Formatting-for-the-Destination-Path-to-Properly-Configure-a-Restore-Job-

8-24-2021_3-01-55_PM.png

8-24-2021_3-07-11_PM.png

Restore Name: Label for the restore job. 

Destination Path: This is the destination path and should follow the proper path syntax for your device. This is the path to the folder where the restore will be downloaded.

Start Time: Do not modify this field if you want the restore job to start immediately after settings are applied. You can schedule the restore job to run in the future.

Overwrite Mode: Select to overwrite files if the same file name is detected at the destination location.

Archived Files: Archived data is kept in ElephantDrive according to the archiving rules set for your backup jobs. ElephantDrive can keep locally deleted files. 

Point-in-Time: In most cases, not applicable, so we recommend contacting us (support@35.83.19.187) before configuring a point-in-time restore. In general, a point in time can be selected and ElephantDrive will restore all backups (if available) from that point in time. 

 

* Restore jobs will start after manually restarting the ElephantDrive client on your destination device.

 

Steps to Configure a Restore Job

  1. Login to our user web portal, http://vault.elephantdrive.com/account/login.aspx.
  2. Navigate into the Files tab and right-click a folder and select “restore folder.”
  3. Select the destination device. (ElephantDrive must be running on the destination device in order for the restore to work.) Click “Next” to configure restore settings.
  4. Manually restart the ElephantDrive client after configuring restore settings. Your restore job will start after the ElephantDrive client is manually restarted at your destination device.

Sometimes you need to get the data that has been backed up. One way to do this is using ElephantDesktop. To do this:

1. Click on the ElephantDrive icon in your System Tray/Menu Bar

723afbd79bb4e9d24dd8129b8916d3f88fa5fd3dd1ee317cdeccc2bb74419520

2. In the System Tray/Menu Bar menu scroll over the Actions section and choose Access Files. This will open the Access Files Window

c5498dd6a722ed9dc3ffaa004687065c97227d75285c2e617066267eaeecc934

3. In the Access Files window navigate to the folder/file you want to restore. Select the file/folder and click the Restore button (the Download button is for small one time downloads. Should your computer or ElephantDesktop need to be restarted or stopped during the Download you will need to start over again. a Restore will start up again from where it left off and is better suited for larger download needs)

a982b7e25bdb53ed36cf95f6013e45f0e82d01f4b1f414af628bdf49ba8d0f81

4. Once the Restore button is clicked a new window will come up where you can select where you want the downloaded file/folder to go on your Computer. Just click the Browse button to choose

0825b58c1266b4ecd0cfd04cc4619cc75e8a3648baaa64f57315c45c323b0d0a

Once you have chosen where to place the file/folder just hit the Save button and your download will begin.

All ‘archived‘ data and certain system file types (metadata files)  are hidden by default in order to provide a clean look. To show these files, you can enable “show hidden files” and “show archived files” from the settings button.

 

  1. Go to Files page.
  2. Click on Settings button on the menu bar.
  3. Check ‘archived files’ and/or ‘hidden files’  to view files.

 

Screen_Shot_2013-09-13_at_2.47.11_PM.png

ElephantDrive allows you to access older versions of your files.

  1. Log-in to your account
  2. Navigate to the file that you would like to retrieve an older version of.
  3. Right-Click on the file and select Previous Versions

.Screen_Shot_2013-08-21_at_9.51.09_AM.png

 

        4. The Previous Versions window will show all previous versions with the version date. 

  • You may download, share, or delete any version by clicking on the drop down menu. 

Screen_Shot_2013-08-21_at_9.54.30_AM.png

Files and folders can be retrieved using the Download method. But, only folders can be restored using the Restore method. 

  • For small individual files or small folders, we recommend using the Download method.

 How to download a file/folder (skip these instructions for Restore):

  1. Login to your account (https://vault.elephantdrive.com/account/login.aspx).
  2. Navigate to the file or folder you would like to download.
  3. Select the folder or Right-click the file/folder and select Download. You must have ElephantDrive installed on your device in order to launch the transfer manager. You can download ElephantDrive for your computer via http://35.83.19.187/home/download-and-install/.Select_for_Download.png

 How to restore a folder:

  1. Login to your account (https://vault.elephantdrive.com/account/login.aspx). 
  2. Navigate to the folder you would like to restore.
  3. Select the folder or Right-click the folder and select Restore Folder.Select_for_Restore.png
  4. Select a Destination Device and manually input a valid Restore Path – this is the destination path of the restore and the format is unique to the device type. The destination device must be connected to your account in order to be a valid destination and for it to appear in the dropdown menu.Select_Device_and_Configure_Restore.png
  5. Select a time for the Start Time then click Start Restore Now to finalize the restore settings. Important: Please restart ElephantDrive on your destination device to ensure the restore settings are applied.

Security, Privacy & Compliance

Yes. Privacy and security are top concerns at ElephantDrive and we have shaped our solution according to the well-established best practices in the security world.  For an overview of the principles and practices applied, please visit our FAQ on security design here.

HIPAA and HITECH have put in place specific regulations regarding how Protected Health Information (“PHI”) is to be handled by professionals. In addition to medical professionals, these regulations apply to their partners and subcontractors, requiring them to enter into a Business Associate Agreement (“BAA”).

Our internal reviews meet the compliance standards outlined in HIPAA and 3rd party certification of these hurdles is forthcoming.  We have used the publicly available documentation and the work done by our storage partners at Amazon Web Services (AWS) as key guidelines for evaluation.  For a review of the recommended techniques for deploying HIPAA compliant applications, please view the AWS whitepaper on HIPAA.  

We have drafted a BAA, specifically tailored both to the unique requirements of HIPAA and HITECH regulations and to the specifications of ElephantDrive’s cloud data services. Our BAA is available upon request by our users on a Business or Enterprise subscription. Just email us at support@35.83.19.187.

We hope this information will help you make an informed decision and we hope to have the opportunity to provide you with the compliant cloud storage services you need.

Keep in mind, however, that no system, by itself, can ensure HIPAA compliance. All organizations must adhere to and enforce daily the standards and regulations detailed in HIPAA in order to maintain compliance.

What happens to my data when my account/subscription is canceled?

Upon cancelling an account/subscription, a data purging process is set in motion. Access to data within the account is immediately disabled. Shortly thereafter, each object in the account is moved into a queue for deletion. As each object is deleted, any metadata is removed from our production databases and the underlying data is deleted from its bucket at Amazon Web Services (AWS) S3 storage service.

AWS policy on S3 deletion is:

When an object is deleted from Amazon S3, removal of the mapping from the public name to the object starts immediately, and is generally processed across the distributed system within several seconds. Once the mapping is removed, there is no remote access to the deleted object. The underlying storage area is then reclaimed for use by the system. (see p. 36 of https://d0.awsstatic.com/whitepapers/aws-security-whitepaper.pdf)

AWS policy on storage decommissioning:

When a storage device has reached the end of its useful life, AWS procedures include a decommissioning process that is designed to prevent customer data from being exposed to unauthorized individuals. AWS uses the techniques detailed in NIST 800-88 (“Guidelines for Media Sanitization”) as part of the decommissioning process. (see p. 29, 72 of https://d0.awsstatic.com/whitepapers/compliance/AWS_Risk_and_Compliance_Whitepaper.pdf)

At ElephantDrive, we use many open source and public domain resources.  We created this article as a centralized resource to provide attribution and thanks to the creators of these great software projects.

So, before diving into the legalese of copyrights, licenses and attributions, we want to just say thank you to all who have contributed to these projects – we are really glad that you are out there.

Below, we’ve grouped the libraries and tools according to the licenses they use…

 

In the Public Domain

LZMA SDK http://www.7-zip.org/sdk.html

SQLite – https://www.sqlite.org/

XZ – http://tukaani.org/xz/

Public Domain

No other attributions or postings required. Thanks for making it so easy guys .


Projects distributed under the Apache License, version 2.0

SIGAR – http://sigar.hyperic.com/

Copyright (c) 2004-2011 VMware, Inc.

Apache.org Libraries:

  XML Schema – https://ws.apache.org/commons/XmlSchema/

  Neethi – https://ws.apache.org/neethi/

  Http Core – https://hc.apache.org/httpcomponents-core-dev/

  Axis2/Java – http://axis.apache.org/axis2/java/core/

  Axiom – https://ws.apache.org/axiom/

  Commons Codec – https://commons.apache.org/proper/commons-codec/

  Commons Logging – http://commons.apache.org/proper/commons-logging/

  Commons HttpClient – http://hc.apache.org/httpclient-3.x/

  Commons IO – https://commons.apache.org/proper/commons-io/

  Apache Derby – http://db.apache.org/derby/index.html

  Log4j v. 1.2 – https://logging.apache.org/log4j/1.2/

Copyright 2004-2010 The Apache Software Foundation

Jna https://github.com/twall/jna

Joda Time – http://www.joda.org/joda-time/

RestSharp

Elmah

Apache License

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License.

You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

 

Projects Distributed under the MIT License

Jquery

Copyright (c) 2015 The jQuery Foundation

Bootstrap 3.2

Copyright (c) 2011-2015 Twitter, Inc

Documentation under Creative Commons BY 3.0

CC BY 3.0 : https://creativecommons.org/licenses/by/3.0/

Date Time Picker Add On for Bootstrap

Copyright (c) 2015 Jonathan Peterson (@Eonasdan)

Bootstrap Validator Add On for Bootstrap

Copyright (c) 2015 Cina Saffary

Moment.js

Copyright (c) 2011-2015 Tim Wood, Iskren Chernev, Moment.js contributors

Handlebars

Copyright (C) 2011-2015 by Yehuda Katz

Underscore

Copyright (c) 2009-2015 Jeremy Ashkenas, DocumentCloud and Investigative

Backbone

Copyright (c) 2010-2015 Jeremy Ashkenas, DocumentCloud

Marionette

Copyright (c)2015 Derick Bailey, Muted Solutions, LLC.

jqPlot

Copyright (c) 2009-2013 Chris Leonello

Font Awesome

Font Awesome by Dave Gandy – http://fontawesome.io

Font Awesome licensed under SIL OFL 1.1

Code licensed under MIT License

Documentation under Creative Commons BY 3.0

CC BY 3.0 : https://creativecommons.org/licenses/by/3.0/

RapidJSON – https://miloyip.github.io/rapidjson/

Tencent is pleased to support the open source community by making RapidJSON available. 

Copyright (C) 2015 THL A29 Limited, a Tencent company, and Milo Yip.  All rights reserved.

If you have downloaded a copy of the RapidJSON binary from Tencent, please note that the RapidJSON binary is licensed under the MIT License.

If you have downloaded a copy of the RapidJSON source code from Tencent, please note that RapidJSON source code is licensed under the MIT License, except for the third-party components listed below which are subject to different license terms.  Your integration of RapidJSON into your own projects may require compliance with the MIT License, as well as the other licenses applicable to the third-party components included within RapidJSON. To avoid the problematic JSON license in your own projects, it’s sufficient to exclude the bin/jsonchecker/ directory, as it’s the only code under the JSON license.

A copy of the MIT License is included in this file.

Other dependencies and licenses:

Open Source Software Licensed Under the BSD License:

——————————————————————–

The msinttypes r29 

Copyright (c) 2006-2013 Alexander Chemeris

All rights reserved.

 

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

 

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of  copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

 

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 

Open Source Software Licensed Under the JSON License:

——————————————————————–

json.org

Copyright (c) 2002 JSON.org

All Rights Reserved.

 

JSON_checker

Copyright (c) 2002 JSON.org

All Rights Reserved.

 

Terms of the JSON License:

—————————————————

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

The Software shall be used for Good, not Evil.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

 

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

 

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

 

Projects Distributed under GNU LGPL 2.1

 

Pdf Renderer – https://java.net/projects/pdf-renderer/

JNotify – http://sourceforge.net/projects/jnotify/

Jna – https://github.com/twall/jna

GNU LGPL 2.1 Copyright Notice

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Copy of the license: http://opensource.org/licenses/lgpl-2.1.php

 

Other Licenses

Xuggler – http://www.xuggle.com/xuggler/

This library was used under the LGPL v3 license: http://www.gnu.org/licenses/lgpl-3.0.en.html

 

BOOST – http://www.boost.org/

Boost Software License – Version 1.0 – August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the “Software”) to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished todo so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

 

Entropia File System Watcher (EFSW) – https://bitbucket.org/SpartanJ/efsw

Copyright (c) 2012 Martín Lucas Golini 

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This software is a fork of the “simplefilewatcher” by James Wynn (james@jameswynn.com)

http://code.google.com/p/simplefilewatcher/ also MIT licensed.

 

C++ Format – http://cppformat.github.io/

Copyright (c) 2012 – 2015, Victor Zverovich

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1  Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2  Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 

gSOAP – http://www.cs.fsu.edu/~engelen/soap.html 

Used under the commercial-use license

 

OpenSSL – https://www.openssl.org/

OpenSSL License

Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  1. All advertising materials mentioning features or use of this software must display the following acknowledgment:  “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)”
  1. The names “OpenSSLToolkit” and “OpenSSLProject” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
  1. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSLProject.
  1. Redistributions of any form whatsoever must retain the following acknowledgment:  “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young(eay@cryptsoft.com).This product includes software written by TimHudson (tjh@cryptsoft.com).

 

Original SSLeay License

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. 

The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed.

If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used.

This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement:  “This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)”.  The word ‘cryptographic’ can be left out if the routines from the library being used are not cryptographic related :-).
  1. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:  “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

 

Wsdl4j – http://sourceforge.net/projects/wsdl4j/ – CPL 1.0

No notice necessary – http://opensource.org/licenses/cpl1.0.php

Orange Extensions – http://ymasory.github.io/OrangeExtensions/

BSD License : https://github.com/ymasory/OrangeExtensions/blob/master/LICENSE

This jar was created by decompiling AppleJavaExtensions.jar (completely consistent with its BSD-like license), and adding the new Java 5 methods. 

Apple’s license does not specify that their copyright notice should be included in modified versions (only complete, unmodified ones), so I’m putting it under 3-clause BSD just to protect myself from liability.

Copyright (c) 2010, Yuvi Masory.  All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name Yuvi Masory nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL Yuvi Masory BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Mail-1.4.jar 

Published under CDDL v.1.0 : https://glassfish.java.net/public/CDDLv1.0.html

Twitterizer (GitHub – http://www.twitterizer.net)

Copyright (c) 2010, Patrick “Ricky” Smith.  All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name Twitterizer nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Ajax.Net 2.0

Released under Microsoft Public License : http://opensource.org/licenses/MS-PL

 

Development Tools

Our development work has been made possible by these awesome tools, many of which themselves are open source or publicly licensed projects:

GCC – https://gcc.gnu.org/

CMake – http://www.cmake.org/

GMake – http://www.gnu.org/software/make/

Ninja – http://martine.github.com/ninja/

Clang – http://llvm.org/ 

Privacy and security are top concerns at ElephantDrive and we have architected our solution according the well-established best practices in the security world.  For an overview of the principles and practices applied, please visit our FAQ on security design here: How is My Data Secured at ElephantDrive.

We have not yet provided for our own independent SAS-70 certification, but we have conformed to the standards and partnered with Amazon Web Services for the physical infrastructure.  We’ve used the publicly available documentation and the work done by our storage partners as Amazon Web Services (AWS) as key guidelines for evaluation.  Their organization has provided several statement and papers addressing SAS-70 compliance: 

Amazon Web Service Security White Paper

Amazon Web Service SAS-70 Discussion Thread

We hope this information helps you make an informed decision and we hope we get the opportunity to provide you with compliant cloud storage services.

Data stored with ElephantDrive is maintained (at a minimum) on multiple devices across multiple facilities in a system designed to sustain the loss of data in one of the facilities, so that even large-scale natural disasters do not pose a threat to the integrity and security of our users’ digital assets.  While we do not disclose the exact locations of the facilities , our technical team partners with Amazon Web Services and utilizes their physical infrastructure.

Via Amazon S3, the service offers storage in several different regions within the United States (Virginia, Oregon, and Northern California) and locations around the world (Ireland, Singapore, Tokyo, Sydney, and Sao Paulo).  Currently, our software automatically allocates data across the regions according to internal rules with heavy concentration in US-based locations.

Many end users have expressed concerns about privacy requirements as mandated by the European Union.  We recommend end users consult with their own legal and/or compliance advisors to determine whether our offering is appropriate for their use, noting that Amazon and AWS are participants in the Safe Harbor program developed by the U.S. Department of Commerce and the European Union and have certified that they adhere to the Safe Harbor Privacy Principles agreed upon by the U.S. and the E.U. (the Safe Harbor certification for Amazon.com and its controlled U.S. subsidiaries can be viewed on the U.S. Department of Commerce’s Safe Harbor Web site).

We are currently exploring additional functionality that would allow an end user to designate the specific region in which data associated with their account will be stored.  Once released, this functionality will allow end users who are based in or governed by the EU to select the Ireland storage region for their data, in which case the data will never leave the EU.

The personal encryption key option is one of the available methods with which we encrypt your file. To protect your data privacy, all files you upload to ElephantDrive are encrypted first before leaving your system. You can choose whether to encrypt your data with the generic ElephantDrive key or your personal key.

The Personal Key is derived from your user password. Since ElephantDrive does not store any of our users’ password information in plain text (we store a hashed value that is compared to the hashed value of the input in the password field at login time, which allows for secure authentication without actual knowledge of the original passphrase), the resulting key is known only to the user. Objects uploaded with the Personal Key can only be opened/restored by the user with that key.

 

IMPORTANT: When you first set up your account with ElephantDrive, you are given the choice between using ElephantDrive Keys or Personal Keys.  If you click on the Personal Keys option, you will see the following message:

You can use your ElephantDrive password as a personal key to encrpyt all of your data.  If you forget your password, you cannot decrpyt your data stored on ElephantDrive. 

When you further select the Personal Keys option, the following “final warning” pops up:

Your password is used to derive the personal key.  If you forget your password, you will lose all your data.

Personal keys offer such high protection that if you forget your password, ElephantDrive can manually change your password for you and give you access to your account, but in this case you will no longer have access to any of your files that were previously backed up under the Personal Keys settings and you will need to start your backup from scratch.

If you choose to backup and store your files using the Personal Keys settings, please ensure that you are using a password that you wil remember, or take the necessary steps to store the password in a safe place where you can retrieve it if necessary.

Limitation: File sharing feature is not available if you have customized your encryption settings to encrypt your data with personal encryption keys. 

We have drafted a BAA, specifically tailored both to the unique requirements of HIPAA and HITECH regulations and to the specifications of ElephantDrive’s cloud data services.

Our BAA is available upon request by our users on a Business or Enterprise subscription.

Just email us at support@35.83.19.187.

We are constantly refining our security measures to meet the rapidly evolving threats in the digital space (like viruses, attackers, hackers and all the other bad guys snooping around the internet), as well as to protect against the every day disasters that Murphy’s Law provides us (like fires, floods, thefts, and accidents). We apply classic principles of secure programming with the knowledge of the latest advances threats and countermeasures. Sometimes the principles sound vague, but below we explain them and identify some of the ways in which they are employed. We would rather you understand why your data is more secure with ElephantDrive than just take our word for it.

First, we harden every server and network device and place it in the secure ElephantDrive datacenter. This means applying the time-tested security principles of “Least Privilege” and “Economy of Mechanism.” In simple terms, it means we remove every program and close every port that isn’t absolutely necessary for our systems to operate, and we restrict physical access and enforce strict rules regarding the environment in which the machines are kept. It’s sort of like the military principle of information on a need-to-know basis. Unlike your home or office computer, ElephantDrive machines are there to serve one, and only one, purpose – securely storing and managing your data. There are no additional programs for hackers to exploit. Our computers are housed inside locked cages in a temperature-controlled facility with redundant power, connectivity, and fire/flood protections. Access is monitored and granted to authorized-personnel-only, and food and drink are prohibited. These efforts enable us to dramatically reduce the potential avenues of attack for would-be wrong-doers and the chances of freak accidents.

Second, we insist on persistent authentication at the most granular level. This involves applying two other established security principles, “Fail-safe Defaults” and “Complete Mediation.” In other words, we start by assuming that all requests for information we receive should be denied, and then evaluate whether or not to grant permission (rather than the other way around). Then we apply this analysis to each individual request. For instance, if an ElephantDrive client wants to upload a file, the software not only verifies the client’s identify before the file begins its transfer, but with each chunk of information delivered. This vigilance also helps us to dramatically reduce the opportunities for the bad guys to impersonate a client.

Third, we compartmentalize sensitive data, in accordance with the principles of “Separation of Privilege” and “Least Common Mechanism.” This means that wherever possible we split sensitive information into pieces that are insufficient to reveal anything without their corresponding part, and we keep functionality in narrowest scope possible. A commonly understood example of this that the movies and the military have combined to provide is the use of two independent keys or codes to allow the launch of weapons – one without the other is useless. The best example of this principle in action is a result of our encryption processes. Every file you store with ElephantDrive is encrypted before it ever leaves your computer, and the file and the key with which it was encrypted are stored on separate devices. Furthermore, the ElephantDrive team members separate their administration responsibilities such that the individuals responsible for managing the file do not overlap with those managing the keys. The result is that all files handled by ElephantDrive are completely unreadable by the bad guys, even in the unlikely event  they were able to get a hold of the hard drives holding the files.

We are often asked about the strength of our encryption, so here is a little more information. ElephantDrive files are encrypted with the Advanced Encryption Standard*, also known as AES*, using a 256-bit key*. The key is derived from the file itself. Banks and other institutions handling sensitive data use these similar encryption methods to keep your data secure. The key itself is then encrypted with AES, using either another key provided by ElephantDrive or one of your own choosing, and stored separately, as mentioned above. It is worth noting that should you choose to use your own key, no one at ElephantDrive (not even all the employees working in concert) will be able to access the contents of your files.

Once the files are encrypted on the local machine, these are then transferred over to our servers via a 128 bit SSL (secure sockets layer) channel. This provides an extra layer of security while the data is being transferred from the local machine to our servers.

Lastly, we work hard to be open about the security we provide and make it practical for our users. The first guiding principle here is known as “Open Design.” In lay terms, this means decoupling the mechanisms we use to provide security from the keys we use to enforce the protection. By making the system details transparent we 1) allow our systems to be examined by experts and reviewers who can offer us feedback on future theoretical attacks or existing vulnerabilities, and 2) need only protect a small amount of discrete information. The second rule applied here is “Psychological Acceptance.” This means the security protocols we’ve chosen to implement have to be simple enough to be understood by our end users, and easy enough that we can actually count on you guys to follow them. Hopefully this explanation has helped to provide a better understanding of how we work with you to practice security, and hopefully our software will make it straightforward and painless for you to execute on it.

Never share your password with anyone. ElephantDrive employees will never ask you for it.

Register now and start protecting your valuable data.

Backup

1. Login to your ElephantDrive account (https://vault.elephantdrive.com/account/login.aspx).

Login_to_ED_Web_Portal.png

2. Click the Backup Settings tab and select Manage Device Backups.

Click_Manage_Device_Backups.png  

3. Select your device from the dropdown menu, then click Add Backup.

Select_Device_Add_Backup.png

4.  Input a name in the Backup Name section and select backup Frequency.

Name_Backup.png

5.  Manually input the path of the folder you would like to backup, then click the “+” symbol to add the path. You can add more than one path.

Type_Path_Click_Plus_Button.png

6. Click “Apply Changes” to add your new backup.

To set up an automatic backup from a PC or a MAC:

  1. Open ElephantDrive menu from the task bar on PC or Menu bar on MAC.
  2. Click on “Actions” and then “Add/Edit Backups“. This will open the “Manage Backups” window.

 

                                                       MAC                                                                                                                    PC

 Screen_Shot_2012-10-02_at_7.09.51_PM.png     11111.png 

 

        3.  Click “New Backup” to add a new backup. 

Screen_Shot_2013-08-21_at_9.14.31_AM.png

 

        4.  Set the name for your backup in the “Name” field.

        5.  Click “Add Folder” to add the location of the folder(s) you would like to backup.

22222k_copy.jpg

 

  • You can also choose to backup only certain certain type of files within a folder, i.e. jpeg, .png, .doc, etc.  Click on the “Include only the following types” to configure this (separate each extension with “,”).
  • The frequency of the automatic backup can be modified in the “Scheduling” section. 
  • You may also exclude any child folder within a parent folder using the “Exclusions” section. Files may also be excluded by file type.
  • Once you are finished with configuring the settings, click “Save” to run the new backups. 

ElephantDrive backups are smart and can identify when a backup is set to run on the last day of the month. If the backup is set to run on the 31st, but the month has 30 days, then the backup will start on the 30th. Similarly, in February, if the backup is set to run on the 30th, it will run on the 28th (or 29th) of February.

ElephantDesktop is an application for your PC, MAC, or a Java capable Server. ElephantDesktop application allows you to setup automatic backup jobs, access your data, configure/manage backup settings, and more. 

To use ElephantDesktop, download and install the ElephantDesktop. 

You start the application by double clicking on  the ElephantDesktop icon on your desktop. Log in, and begin to backup your data. You can do this one of two ways:

Run a Backup Category – You can ask ElephantDrive to run a Backup category either by “folder” or by “type”.  For a “folder” Backup category, you select a specific folder on your computer (like “My Documents,” or “important stuff,” or “C://”), and ElephantDrive will make a backup of every file and folder that lives there. For a “type” Backup category, you choose one or more file types (like “doc,” or “xls,” or “mp3”), and ElephantDrive will make a backup of every file of that type it finds in the specified directory.  We have made this process even easier by having a few of these category pre-defined and ready to run — in only two clicks, you can get them started!  Better yet, once created, these jobs will automatically run at regular intervals, so you’ll always be up to date.

You can also select any folder from your PC, right click on the folder and then select to Backup it up with ElephantDrive. No need to move the folder or do anything else, that’s it!

Upload a specific item – You can also move files and folders between your computer and ElephantDrive on an one time basis using the Manual Uploads. Simply drag-and-drop like any other Windows programs.

We’ve got tons of Advanced Options and features available for those of you who like a little more control, but if you want to set-it-and-forget-it or just use ElephantDrive for convenient storage and access, this is all you need to know.

ElephantDesktop is currently supported on:

  • Windows: XP, Vista, Windows 7, 8, 10, Windows 2000, Windows 2003, Windows 2008
  • Mac OS X: 10.4 and above

Elephant Desktop requires the following:

 For information on how to use ElephantDrive Web, please click here.

The upload speed for ElephantDrive can be adjusted to your specific needs and use case. You can change this directly from the website by following the steps outlined below:

  • Access the ElephantDrive website and log in using your account credentials
  • Click on “Backup Settings“

Screenshot_2020-05-27_12-41-13.png

  • Click on “Manage Device Backups“

Screenshot_2020-05-27_12-41-26.png

  • Select the device in the device drop-down and click on “Resource Usage”

Screenshot_2020-05-27_12-41-51.png

  • Use the “Network Usage” and “CPU Usage” settings to adjust how much bandwidth and CPU the ElephantDrive app should use

Screenshot_2020-05-27_12-42-38.png

Screenshot_2020-05-27_12-42-45.png

  • Click on “Apply” to apply the changes to your device’s configuration.

Copyright ElephantDrive Inc. 2021 — v30-BME-967

Twitter Facebook-f Linkedin-in Instagram Envelope Phone