Machi-Systems Subprocessors and Cookies
When your information is shared with third-party subprocessors, we remain responsible for it. We work very hard to maintain your trust when bringing on new vendors by requiring data protection agreements that restrict the processing of Users’ Personal Information (as defined in the Privacy Statement).
|GoDaddy||Website Hosting Provider|
|WPMUDEV||Website hosting Provider, HUB provider|
|Amazon Web Services||Email Service Provider|
|Google Workspaces||Customer Ticketing email service provider|
|Sentry.io||Application monitoring provider|
|JIRA||Team collaboration and project management platform|
|Trello||Team collaboration and project management platform|
|Dropbox||File hosting service provider|
|Dropmark||Machi-Systems Mood-board provider|
|Coinbase||Cryptocurrency Payment provider|
|YISP||Server’s network and rack space provider|
|NovoServe||Server’s network and rack space provider|
This page will be updated upon removing, changing, or bringing on a new subprocessor who handles our Users’ Personal Information.
To ensure a consistent and effective user experience and a secure environment, this section of the policy explains the cookies used on our services.
- Session cookies remain in your browser during your browser session only, i.e. until you leave the website.
- Persistent cookies last beyond the current session and are used for many purposes—such as recognizing you as an existing user—and will remain valid until the set expiry date unless deleted by the user prior.
These cookies are further classified into the following categories:
- Strictly Necessary & Security
- These cookies are essential for websites on our platforms to perform their basic functions and are not to be disabled. These are used to make interactions with our Services faster, more reliable, and avoid attacks such as cross-site scripting.
- Performance & Analytics
- These cookies allow visitors and traffic source count in order to evaluate and enhance our site’s performance. This helps to understand the largest and least prominent pages to see how visitors move around the website. All information obtained by these cookies is aggregated, and hence, anonymous. With these, the quality of our services is calculated and evaluated.
Strictly Necessary & Security Cookies
- This cookie is associated with the use of CloudFlare to recognize trusted web traffic and to speed up page load times. It does not contain any information on user identity. It also overrides any security restrictions based on the IP address from which the visitor derives.
- This automatically refreshes client area sessions and keeps you logged in until the tab is closed to improve user experience.
- Our control panel uses this cookie to allow session variables to be stored on the web server. These cookies are essential for the functioning of our website’s client area. This session cookie is lost when the browser is closed.
- This cookie is set on our Control Panel developed on WordPress and Django and helps to protect against Cross-Site Request Forgery protection, which is an attack that makes your browser submit a form that you haven’t requested.
- This is used for the identification of a user session on the Control Panel, having the HTTPOnly flag to strictly prohibit any attempt to access it with any client script.
- This is used to store track sessions and remember logins on our Documentation site based on GitBooks (however, the login part is unavailable for clients).
- Same as the csrftoken, this is used as protection against Cross-Site Request Forgery (XSS) attacks on our Documentation Site.
Performance & Analytics
- These cookies are associated with Google Universal Analytics, which is used to identify specific users by assigning a randomly generated number as a client identifier and throttle the request rate. These are used to evaluate visitor, session, and campaign data for analytics reports.
- These cookies are set by the Google Analytics service and help us to understand how visitors interact with our websites by creating a better experience for our visitors. They are used for features, such as determining new sessions, visits, and distinguishing between users and sessions.
We hope you’ve found this doc useful. Is anything missing? If so, email us at email@example.com and we’ll get it sorted for you.
Questions? Send us a note and we’ll get right back to you.