Cookies and sessions in Django both serve the purpose of remembering and preserving information about the current state or context of a user's interaction with the application across multiple requests, but they do so in fundamentally different ways.

It is important to point out that Atrium Cloud relies heavily on its cache mechanism for its functional operations. However, most of the data being cached is only related to the site's owner data or the software itself, which allows its functionality.

We primarily use two types of cache mechanisms: FileBasedCache and RedisCache. Both of these are stored on our servers, not on the user's side. You can be at ease, because none of your data is being cached by us unless we explicitly describe it as such. Here, you will find the data we cache from you and for you:

1. Cookies

Cookies are small pieces of data stored directly on the user's browser. When a Django application sets a cookie, it sends this data to the client, which is then sent back to the server with each subsequent request. This makes cookies ideal for storing user-specific settings, preferences, and non-sensitive data that needs to persist across browser sessions. Since cookies are stored on the client's side, they are also subject to size limitations and security considerations, as they can be easily accessed and manipulated by the user.

2. Sessions

On the other hand, Sessions in Django store data on the server side, associated with a unique session ID that is kept in a cookie on the client’s browser. When a user interacts with the web application, Django uses this session ID to retrieve and update the corresponding session data on the server. This method provides a more secure and scalable way to manage user data, as the actual session data is never exposed to the client and can include more extensive and sensitive information like user authentication status, cart contents, and temporary data. The session ID cookie itself is typically lightweight and doesn’t hold any meaningful data, reducing the risk of client-side data manipulation and enhancing overall security.

3. What Data Do We Gather?

We gather various types of data based on your interaction with our services. This includes data for normal use, extensive use, and limited automatic deletion. The data collected helps us improve our services, ensure security, and personalize your experience.

• After manually deleting cookies and sessions, the only cookies retained on both the client-side and server-side are:
  • `csrftoken`: This cookie is used to prevent Cross-Site Request Forgery (CSRF) attacks. It is a unique token generated by Django for each user session and is required to validate forms submitted on the website.
  • `messages`: This cookie is used by Django to store messages that are passed between views in the request/response cycle. It allows messages like success, error, warning, and info to persist across redirects.

4. Client-Side Cookies

For normal usage, we collect cookies and session data to enhance your browsing experience and maintain security. This includes:

• `gdpr_consent`: To record your consent for data processing.
• `MCPopupClosed`: To remember if you've closed the marketing consent popup.
• `csrftoken`: For preventing Cross-Site Request Forgery attacks.
• `visitorid`: To track your visits.
• `language_preference`: For displaying content in your preferred language.
• `darkmode`: To remember your dark mode preference.
• `rateLimitFalse and rateLimitTrue`: To manage rate limiting.
• `dark_mode_disabled_until` and `like_disabled_until`: To manage temporary disabling of features.
• Settings like language, theme, or other personalized data to enhance your user experience.

5. Server-Side Cookies

In extensive use scenarios, we gather additional data to provide enhanced services. This includes:

• We may collect your IP address for security purposes if the rate limiter detects multiple suspicious requests.
• `sessionid`: A unique identifier for your session, which includes save_info (boolean), email, full name, phone number, item bags, country, and download password.
• `save_info`: To remember your preferences.
• `download_password` or `password` (for guests): For secure access to downloads.
• `full_name`, `email`, `country`, `phone_number`: For personal identification and communication.
• `username`: For account management.
• `order_number`: To track your orders.
• `payment gateway`: To process payments.
• `item_bag`: To manage items in your shopping cart.
• `__stripe_sid`, `__stripe_mid`: To manage Stripe sessions for payment processing.

6. Limited Automatic Deletion

Certain data is stored on our server and accessed only via the `sessionid`. This data is automatically deleted after a successful payment unless manually cleared by you. This includes:

• save_info
• download_password or password (for guests)
• full_name
• email
• country
• phone_number

7. Third Party Cookies

We share certain data with Stripe for legal reasons and to process orders. This data is not deletable and includes:

• Username
• Currency
• Language preference
• Order number
• Name and amount of items purchased

Additional personal data entered during payment, such as:

• Phone number
• Email
• Country
• Full name

These details are stored in Stripe's database to fulfill legal requirements

8. Orders

When you place an order, even if you delete your user account and remove cookies, some data is retained for legal reasons. This includes:

• Order number
• Phone number
• Email
• Country
• Full name
• Payment gateway
• Item bag
• __stripe_sid
• __stripe_mid

This data is also stored by Stripe to comply with legal obligations.

9. Other Third Parties

Other third-party services that may use cookies include:

• AWS3
• Heroku
• Cloudflare
• Redis
• Github
• Supabase
• Heroku PostgreSQL.
• Mailchimp
• EmailJS
• Google Services
• Stripe