PersonalData
⚠️ The documents on this wiki represents work-in-progress from the time where we worked on ensuring GDPR compliance. The documents are no longer updated and don't represent an updated state. For the most recent information, please visit our GDPR Commitment, Privacy Policy, Terms of Use, and Sub-Processors.
This is an overview of the personal data we collect directly on elmah.io and why we do it.
| Field | Description |
|---|---|
| We collect user email in order to send them help during their trial, mails when new errors are logged in their subscription, daily digest and other types of emails that the user opts-in to. | |
| ProviderName | We store the name of the social provider used to log in on elmah.io, to be able to log users in next time they try from the same provider and to avoid problems where two social accounts would user same user id |
| Created | A date and time is stored on all users in order to see when their trial expires |
| LastLoggedIn | The last time the user logged in is stored to show organization admins if their users log in or not and not optimize the search user feature to show results from people the logged in first |
| Name | The users name is stored in order to show a name rather than an email througout both the UI and the notification channels (mail, Slack, etc.). |
| Timezone | Timezone is used throughout the UI to make sure that dates are handled correct. We store everything in UTC, but need the timezone to convert back to the users time. |
| FailedLoginAttempts | When a login using username/password fails, we increment a counter on the user. |
| Field | Description |
|---|---|
| Name | The name of the organization is stored to be able to generate a correct invoice and to show in different locations on the UI. |
| Created | A date and time is stored on all organizations in order to see when their trial expires |
| CompanyName | The name of the organization is stored to be able to generate a correct invoice and since users want their organization named differently than their company name (like if they have more organization on a single company). |
| Address | The address of the organization is stored to be able to generate a correct invoice. |
| Zipcode | The zipcode of the organization is stored to be able to generate a correct invoice. |
| City | The city of the organization is stored to be able to generate a correct invoice. |
| Country | The country of the organization is stored to be able to generate a correct invoice. |
| Vat | The vat of the organization is stored to be able to generate a correct invoice. |
No one in the company has access to Log Data, unless explicitely approved by the customer in order to carry out support. When the support case is closed, the approval expires and a new approval will be needed for the next support case (even if it is the same customoer).
We do not allow remote access to our systems, and we only share data with the following entities.
elmah.io employees have access to the users Personal Data through our backoffice system. The user can restrict this access through the elmah.io UI.
We share the customers name and email, in order to send emails to the customer during the trial period as well as transactional emails about failed payment, new features and similar.
We share the company name of the customer with Paymill. Paymill is used to charge customers the monthly/yearly fee and that requires a named identifier of each customer.
Customers can opt in for our quarterly newsletter. When doing so, we share their name and email with Mailchimp in order to send and personalize the newsletter to each customer.
We use Mandrill for sending transactional emails. We share the customer email with Mandrill in order to be able to send the message.
We use AWS Simple Email Service (SES) for sending transactional emails. We share the customer email with AWS in order to be able to send the message.
All personal data are stored inside Microsoft's data center in West US. Backups are forwarded to Microsoft's data center in East US. We need to spread across at least two data centers, in order to restore customer data in the case of a data center breakdown.
All user data is deleted 13 months after signing up, unless the user is part of a paid subscription. If a user wants her/his data deleted before that, she/he can get in contact for a manual deletion. We want this to be a manual process, in order to disallow people from keep signing up for new trials.
When a user ask for deletion, the user data will be deleted from:
- Our database (Elasticsearch)
- Intercom
- MailChimp (in case the user signed up for the newsletter)
- Backups (we don't want to modify already created backup data, why we create a new total backup and delete the old one)
All users must be able to export all of the personal data we keep about them. Personal data can be requested through our support and will be delivered as a JSON output from our users database.
The user can modify most of the information collected about them (like name, email, etc.). We have some internal properties which are not visible through the UI (see the first paragraph on this page). These information can be updated by contacting our support.