Data Retention and Privacy Policy
Non Public Personal Information
Origins:
- Collected automatically from a user
- Collected on account creation
Examples:
- Email address
- Phone Number
Maximum Retention Period:
- Until user deletes/changes the account settings
- Until company account is deleted/closed with ReloShare
Non-Personal User Data Collected
Origins:
- Collected automatically from a user
Examples:
- Data collected by ReloShare about user account activity (first login, last login, account verified)
Maximum Retention Period:
- Indefinitely
Non-Personal User Data Collected
Origins:
- Provided by user
Examples:
- Data collected by events associated with user event activity (search history)
Maximum Retention Period:
- After 120 days, it will be deleted, aggregated, or de-identified
Non-Personal Information Not Associated With a User Account
Origins:
- Collected automatically from various users
Examples:
- Counts of how many times certain events have occurred (e.g. successful bookings)
Maximum Retention Period:
- After 120 days, it will be deleted, aggregated, or de-identified
Definitions
Personal Information means information you provide us or information we collect from you that identifies or could be used to personally identify you.
Examples of public Information would include your IP address or your name if it is disclosed under your user profile.
Examples of non-public Information would include your IP address if you edit while logged in or your email address, if you provided one to us during account registration (but didn’t post it publicly).
Data is de-identified when it has been aggregated or otherwise retained in a manner such that it can no longer be used to identify the user.
Data is aggregated when the data associated with a specific user has been combined with data from others to show general trends or values without identifying specific users.
Exceptions to these guidelines
Data may be retained in system backups for longer periods of time, not to exceed 5 years.
Research: There is a short-term extension applying to data collected as part of experimental features. In order to collect and analyze sufficient data, this data must be kept beyond the standard 120-day period.
Audits and Improvements
ReloShare is committed to continuous evaluation and improvement of these guidelines, and to periodic audits in order to identify such improvements. As we make changes to existing and systems, we will update these guidelines to reflect our changing practices.
System Design
In order to support these data retention periods and our overall privacy policy, new tools and systems implemented by ReloShare will be designed with privacy in mind. This will include:
- Inclusion of these data retention guidelines as requirements during the design process
- Legal consultation during the design and development process
- Inclusion of privacy considerations in the code review process
Ongoing Handling of New Information
Despite our best efforts in designing and deploying new systems, we may occasionally record personal information in a way that does not comply with these guidelines. When we discover such an oversight, we will promptly comply with the guidelines by deleting, aggregating, or de-identifying the information as appropriate.
Contact Us
If you think that these guidelines have potentially been breached, or if you have questions or comments about compliance with the guidelines, please contact us at privacy@reloshare.com.