Full Context Development Subprocessors and Cookies
Full Context Development provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details our subprocessors, and how we use cookies.
Effective date: December 1, 2021
Full Context Development Subprocessors
When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we do our best to only enlist them if their processing of Users' Personal Information is in line with our Privacy Policy and this document.
Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location | GDPR Data Protection |
---|---|---|---|---|
Amazon Web Services EMEA SARL | Transactional email service | Europe, Frankfurt | 38 Avenue John F. Kennedy, L-1855, Luxembourg | DPA, Compliance |
Redis EMEA Ltd | Data hosting | Europe, Frankfurt | Tower 42 25 Old Broad St, London EC2N 1HN, UK | DPA |
Cloudflare, Inc. | Network security services | United States | 101 Townsend St, San Francisco, CA 94107, US | DPA, Introduction |
Vercel Inc. | Website hosting and Infrastructure provider | United States | 340 S Lemon Ave #4133 Walnut, CA 91789, US | DPA |
New Relic, Inc. | Logging service | Europe | 188 Spear Street, Suite 1000, San Francisco, CA 94105, US | DPA, FAQ |
When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via Support.
Cookies on Full Context Development
Full Context Development uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our Privacy Statement if you’d like more information about cookies, and on how and why we use them.
Since the number and names of cookies may change, the table below may be updated from time to time.
Service Provider | Cookie Name | Description | Expiration* |
---|---|---|---|
Full Context Development | fcd-session-id | This cookie is used to track the action flow of users for support, debugging and security purposes. | Session |
Full Context Development | fcd-device-id | This cookie is used to track recognized devices for security purposes. | Session |
Full Context Development | metal-session | This is an essential cookie to keep the logged in state and other basic information of authenticated users between page reloads. | 15 days |
Paddle Inc. | paddlejs_campaign_referrer | This cookie is generated by Paddle to track campaign referrers. We use Paddle to handle our product payments. | One month |
Cloudflare Inc. | __cf_bm | This cookie is generated by Cloudflare and stores technical information that is used for bot protection, a security concern. | 30 minutes |
* The expiration dates for the cookies listed below generally apply on a rolling basis.
(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
License
This document is based on Github Subprocessors and Cookies and is simiarly licensed under this CC BY license.
© 2021 - 2023 All Rights Reserved
József Miskolczy