Select a category on the left, to get your answers quickly
This document attempts to cover the Opensolr Data Security and Data Privacy policies that are already implemented and active. This is subject to change, so please check back for updates, or, Contact Us, with your suggestions.
Here are the security mechanisms implemented by Opensolr.com
In order to perform AJAX HTTP Authenticated requests, you will have to submit a support ticket, and let us know what are the origins where you are making your requests from, so that we can whitelist those, in our cloud infrastructure settings.
You will also have to indicate your index/cluster name, and account registration email address.
Dataimport (DIH) can not be reached
Due to certain security concerns, the dataimport (DIH) Solr feature is now globally disabled, form the entire Opensolr ecosystem.
However, you are still free to use the dataimport (DIH) Solr feature, by requesting that we enable it for your index(es), using our Support Helpdesk, at: https://opensolr.freshdesk.com/ or, directly via email, at support@opensolr.com
Important:
Becoming an Opensolr member, is only possible via the Opensolr Registration Form.
By becoming an Opensolr member, you agree with the Terms of Service, the General Privacy Policy, and this GDPR Privacy Agreement.
Opensolr collects mandatory minimal information about the user for the purpose of registration.
Such mandatory data is limited to: Email, Chosen Password.
Opensolr members, may at any time alter the Chosen Password.
The registration email address may only be updated through a formal request to support@opensolr.com
Opensolr members have the right, to optionally add more personal data, such as (but not limited to): Personal Website, Facebook ID, etc.
Opensolr members have the right, to optionally create Opensolr Cloud Index(es) and store any type of data in them.
Opensolr does not directly collect, store or process any personal, billing, or payment information from the Opensolr members or any other 3rd parties, whatsoever.
Your Opensolr Index Data (the data in your Solr Index), will never be reachable to the Opensolr staff, Opensolr Subcontractors, Upstream Service Providers, or any other 3rd party, without your consent, or, only if required by critical technical emergencies, in order to restore the Service to it's normal parameters.
Opensolr will never make public, any member's personal data information, nor will Opensolr ever sell or trade this information with any 3-rd party.
Opensolr will use the email as identification upon every login action.
Opensolr provides strict security measures for the data that is being stored and processed via the Opensolr Shared or Dedicated Cloud Servers.
Details on the Opensolr Cloud Data Security can be found at: https://opensolr.com/faq/view/security.
As stated at #2, Opensolr will never directly collect, store or process any billing or payment information from the Opensolr members, or any other 3rd parties, whatsoever.
All payments, and billing present on the Opensolr website, and, inside the Opensolr Billing Control Panel, is a front-end to the highly secure PCI Compliant, APIs of Stripe.com
All data going through any Opensolr container, server, or other Opensolr infrastructure, is secured by SSL.
Our SSL certificates are re-keyed and re-issued every 1 year.
The Opensolr.com website, will alaways use EV-SSL.
All Opensolr accounts have the option to activate the Two Factor Authentication (TFA), via SMS or the Authy app. The TFA implementation is made via SSL requests to our TFA provider: Twillio.com
Opensolr will never send any unsolicited emails, postal letters, of any kind.
All Opensolr communications are fully mandatory when becoming an opensolr member.
All Opensolr communications will be limited to the following:
You can enable TFA in your Opensolr account as follows: