Plethra

Legal

We want to be completely transparent about what data we store and collect, and what we use it for. We also believe its important we tell you what we're doing to protect your privacy. So here are all the details.

Data We Store

  • Account Registration (User Provided)
    • First & Last Name
    • Userhandle (optional)
    • Userhandles are optional and are for use on our Q&A community at talk.plethra.com. If one is not provided, a non-personal unique identifier is used (i.e. "user123843").
    • Email Address
    • Email addresses are used as the login username. You can change your email address from your user account settings. For your own security, we will not reset email addresses for you for any reason. So if you can't get access to your email account, contact your email provider.
    • Password
    • All passwords are stored on our servers in encrypted form so not even we can tell what they are! If you loose your password, we generate a custom, single-use, time-restricted url for resetting your password and send it to the email address on file.
  • Network Registration (User Provided)
    • Network Name
    • Physical Street Address
    • This is used to facilitate licensing of our software. It is analogous to a "Shipping Address".
  • Network License Key
    • Non-Personally Identifiable Network Properties
  • Purchase Information
    • Only a transaction ID is stored on our servers. All other information is required by Braintree and stored securely on their servers.
    The following applies to purchases prior to 13/04/2016:
  • Purchase Information From Direct Payments (User Provided)
    • First & Last Name
    • Telephone
    • Email Address
    • Company Name (optional)
    • Street Address
    • Card Type, Expiration Date, & Last 4 Digits of Account #
    • All credit card transactions are transmitted encrypted to a financial gateway via SSL using a secure HTTP connection. We never, even temporarily, store entire credit card numbers in our database. After the transaction has occurred, we retrieve and store the last 4 digits of the account number.
  • Purchase Information From Paypal Express Checkout Payments (User Provided)
    • First & Last Name
    • Telephone
    • Email Address
    • Company Name (optional)
    • Paypal BuyerID
    • Account Verification Status

Data We Collect

  • "Google Analytics" on www.plethra.com, plethra.com, and talk.plethra.com
    • Non-Personally Identifiable Web Analytics & Reporting
  • "Sublime Video Analytics" on www.plethra.com and plethra.com
    • Non-Personally Identifiable Video Analytics & Reporting
  • Bug & Crash Reports (User Provided & Initiated)
    • Non-Personally Identifiable Software Logging & Reporting

How We Use the Data

  • To improve our products
  • To improve our marketing
  • To personalize newsletters & emails
  • To monitor and prevent piracy & fraud

How Our Software Installs Work

We hate software that can't be completely removed from a device. Software that leaves little bits and pieces of itself scattered about the operating system, especially after uninstallation, are just annoying. We also hate software that is heavily dependent on bulky 3rd-party executables or frameworks. Our software and installers don't write to files outside of its own installed directory and are almost entirely self-sufficient. However, there are a few unavoidable exceptions:

  • On Windows
    • Bonjour (mDNSResponder.exe)
    • This is Apple's branded zeroconf and its used for network service discovery. It's most popularly used by iTunes. It is required by our software. If you have iTunes installed, this will already be installed and running. If it is not installed, we install it automatically. If it is not running, we turn it on automatically.
    • Windows Service (services.msc)
    • When installed as a windows service (i.e. software that runs in the background), our Windows installer runs the command "AcaciaService.exe install" which adds our software as a windows service and by necessity, creates a single file in the Windows Registry. This tells the operating system our software needs to be started automatically when the computer starts up and restarted automatically when it crashes. This registry file can be deleted by running the command "AcaciaService.exe uninstall" or by running our official uninstaller.
  • On Mac OS X
    • LaunchDaemon (com.plethra.acacia.plist)
    • When installed as a daemon (i.e. software that runs in the background), our Mac installer places a small XML plist file in the LaunchDaemons folder. This tells the operating system our software needs to be started automatically when the computer starts up and restarted automatically when it crashes.
  • On Linux
    • init (AcaciaService)
    • When installed as a daemon (i.e. software that runs in the background), our Linux installer places a script in the /etc/init.d folder. This tells the operating system our software needs to be started automatically when the computer starts up and restarted automatically when it crashes.

How Our Licensing Checks Work

On startup, our software determines whether the network it is currently running on is licensed. This is done by sending non-personally identifiable network properties that uniquely identify the network, to our servers via the internet.

How Our Automatic Updates Work

On startup, our software determines if an update is available. This is done by contacting our servers via the internet. The software determines what version the registered network has requested to use (i.e. Alpha, Beta, Release Candidate, or General Release) via the licensing check, and provides it with a list of dependencies. The software then compares this list with its current dependencies using a hash and downloads the files that have changed, deleting the old ones.

No Eavesdroppers

By default, all private data is sent and received encrypted via SSL using a secure HTTP connection. Our SSL certificates are issued by GoDaddy, a trusted 3rd-party. Secure connections can be identified in the address bar of your browser and should look something like this:

Browser Cookies & Storage

  • www.plethra.com, plethra.com, and talk.plethra.com
  • No browser cookies are used unless you are logged in. When logged in, a single cookie is used to allow your user session to persist between pages and subdomains. When you log out, the cookie is deleted.
  • acacia.plethra.com
  • A browser controlled sql database is used to remember state between sessions (i.e. what panes are open/closed, what columns are being used, etc.). Offline HTML5 appcache is used to speed up the loading of the user interface and allow it to be used when offline. None of this a requirement for the product to function so they can be safely disabled in the browser settings.

Our Q&A Community

All user contributions are covered under a Creative Commons license. See the Q&A FAQ to learn more.

Feedback

We welcome any feedback on this document and our policies.
Submit Feedback