{"id":6440,"date":"2026-07-09T12:20:40","date_gmt":"2026-07-09T12:20:40","guid":{"rendered":"https:\/\/atlascei.com\/?page_id=6440"},"modified":"2026-09-06T21:53:55","modified_gmt":"2026-09-06T21:53:55","slug":"cookie","status":"publish","type":"page","link":"https:\/\/atlascei.com\/de\/cookie\/","title":{"rendered":"Keksen"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\r\n\t \t Legal Information<\/span>\r\n\t

ATLAS Cookie Policy<\/h1>\t <\/div>\r\n\t \t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This Cookie Policy explains how ATLAS uses cookies, local storage, and similar technologies when users access its websites, web applications, and other online services, as well as how users can manage the relevant settings.
This policy should be read in conjunction with the ATLAS User Agreement, the ATLAS Privacy Policy, and other applicable policies.<\/p>\n

1. What are Cookies?<\/h4>\n

Cookies are small data files that websites store on a user’s browser or device when the user visits them.
Cookies help websites recognize a user’s browser, maintain login status, remember user preferences, enhance account security, and assist the platform in analyzing website performance.
In addition to cookies, depending on the actual technical architecture, ATLAS may also use:
Local Storage
Session Storage
Pixel tags (Pixels)
SDK device identifiers
And other technologies with similar functions.
References to “cookies” in this policy include these similar technologies where appropriate.<\/p>\n

2. Why We Use Cookies<\/h4>\n

ATLAS may use cookies and similar technologies for the following purposes:
Maintaining user login status;
Identifying account sessions;
Preventing unauthorized access;
Remembering language, theme, and interface settings;
Supporting the proper functioning of transaction pages;
Saving necessary page states for the user;
Analyzing website performance;
Identifying technical issues;
Enhancing security;
Compiling statistics on product usage;
Improving user experience.
ATLAS will not disclose users’ private chat content, identity documents, or other sensitive information solely due to the use of cookies.<\/p>\n

3. Essential Cookies<\/h4>\n

Essential cookies are cookies required for the platform to function properly.
For example:
Login session \u2192 Authentication \u2192 Security verification \u2192 Account access
These cookies may be used for:
Login status;
Session management;
CSRF protection;
Security verification;
User authentication;
Preventing duplicate submissions;
Transaction security;
Risk control;
Load balancing.
If a user disables essential cookies, some core functions of ATLAS may not work properly.
Therefore, where permitted by applicable law, essential cookies generally do not rely on consent for marketing purposes.<\/p>\n

4. Functional Cookies<\/h4>\n

Functional cookies are used to remember user preferences. For example:
Language;
Time zone;
Day mode \/ Night mode;
Candlestick chart timeframe;
Default trading pair;
Page layout;
Table display format;
Watchlist settings;
Certain interface preferences.
For instance, if a user selects “Night mode,”
the system can use the corresponding setting to maintain the night-mode interface during the next visit.<\/p>\n

5. Analytics and Performance Cookies<\/h4>\n

ATLAS may use analytics cookies to understand how the website and system operate.
For example, tracking statistics such as:
Page views;
Page load speed;
Feature usage frequency;
Error pages;
User navigation paths;
Browser and device types;
Time spent on pages;
Product performance metrics.
This data helps the platform:
Identify issues \u2192 Optimize the system \u2192 Improve user experience.
Where applicable law requires user consent, the platform shall enable the relevant analytics cookies only after obtaining such consent.<\/p>\n

6. Security and Risk Control Cookies<\/h4>\n

As ATLAS involves account and trading services, certain cookies or similar technologies may be used for security and risk control purposes.
For example:
Identifying new login devices;
Preventing account hijacking;
Detecting abnormal access;
Restricting malicious requests;
Preventing abuse of CAPTCHA interfaces;
Detecting abnormal login frequency;
Supporting device risk analysis.
For example:
User account + Device identifier + IP information + Login history = Security risk assessment.
Such information shall be processed in accordance with the Privacy Policy and applicable data protection requirements.<\/p>\n

7. Cookies in Trading Functions<\/h4>\n

ATLAS may use cookies or session storage to the extent necessary to support trading pages.
For example, temporarily saving:
Current trading pair;
Buy\/Sell page status;
Current order type;
Page display settings;
User trading interface preferences.
However, regarding core trading parameters involving actual orders\u2014
such as execution price, order quantity, and final order status\u2014
browser cookies should not be relied upon as the definitive system record.
Final order data must be stored and verified on the platform’s servers and within the actual trading system.<\/p>\n

8. Third-Party Cookies<\/h4>\n

ATLAS may use third-party service providers to support certain functions. Examples include:
Website analytics;
Authentication;
Customer service systems;
Network security;
Content delivery;
Error monitoring;
Other technical services.
Third parties may set cookies based on their own technologies.
If a third party processes user information as an independent data controller, their actions may also be subject to their own privacy policies.
ATLAS should disclose necessary information about third parties in its formal policy, based on the actual service providers used.<\/p>\n

9. Analytics services such as Google Analytics<\/h4>\n

If ATLAS uses Google Analytics or similar website analytics tools, certain website usage data may be collected.
Examples include:
Page views;
Traffic sources;
Device type;
Page interactions;
Approximate location;
Technical errors.
If the platform formally integrates specific analytics services in the future, it is recommended to clearly list the following in the Cookie Policy:
Service name
Purpose
Cookie name
Retention period
Provider
This ensures users clearly understand the specific purposes.<\/p>\n

10. Marketing cookies<\/h4>\n

If ATLAS uses advertising, remarketing, or marketing analytics technologies in the future, these should be distinguished separately:
Marketing \/ Advertising Cookies
Marketing cookies may be used to:
Measure advertising effectiveness;
Analyze marketing campaigns;
Identify advertising sources;
Provide more relevant promotional content (where permitted).
For jurisdictions requiring user consent:
Marketing cookies should only be enabled after obtaining valid consent.
It is not recommended to group marketing cookies with necessary security cookies.<\/p>\n

11. Cookie consent management<\/h4>\n

If applicable laws in the user’s location require cookie consent, a cookie banner may be displayed upon the first visit to the website.
Example:
ATLAS uses necessary cookies to ensure account login and platform security. With your consent, we also use analytics and functional cookies to improve the website experience. You may choose “Accept All,” “Necessary Only,” or “Custom Settings.”
Buttons can be configured as: Accept All
Use Necessary Cookies Only
Customize
Avoid providing only an “Accept” option
without a reasonable option to reject non-essential cookies.<\/p>\n

12. Custom Cookie Settings<\/h4>\n

Users can navigate to:
Settings \u2192 Privacy \u2192 Cookie Settings
To manage settings based on the platform’s actual functionality:
Necessary Cookies: Always enabled
Functional Cookies: On \/ Off
Analytics Cookies: On \/ Off
Marketing Cookies: On \/ Off
If Necessary Cookies are essential for the platform’s basic operation, it may be explicitly stated that they cannot be disabled via the Cookie Center; however, users can still control them through their browser settings.<\/p>\n

13. Browser Settings<\/h4>\n

Most modern browsers allow users to:
View cookies;
Delete cookies;
Block cookies;
Restrict third-party cookies;
Clear browsing history.
Users can manage these settings via their browser’s privacy or security options.
However, deleting login cookies may require the user to log in again.<\/p>\n

14. Impact of Disabling Cookies<\/h4>\n

Disabling certain cookies may result in:
Inability to maintain login status;
Repeated security verification prompts;
Loss of user preferences;
Page settings reverting to defaults;
Certain features failing to function correctly.
Disabling analytics or marketing cookies generally should not render core account and transaction functions unusable, unless the technology also serves necessary security functions and this has been clearly disclosed.<\/p>\n

15. Cookie Retention Periods<\/h4>\n

Retention periods vary by cookie type.
For example:
Session Cookies: Valid only during the current browsing session; may expire upon closing the browser.
Persistent Cookies: Stored on the device for a specific period to remember user settings or security status.<\/p>\n

The names above are examples only; official documentation should align with the actual website code.<\/p>\n

16. Local Storage<\/h4>\n

ATLAS may use browser Local Storage to save non-sensitive interface settings.
For example:
theme = dark
language = zh-CN
chart_interval = 5m
It is not recommended to store the following in plaintext within frontend local storage:
Login passwords;
Full payment details;
Private keys;
API Secrets;
Identity document details;
Other highly sensitive authentication credentials.<\/p>\n

17. Security Requirements<\/h4>\n

Necessary security measures should be applied to cookies and authentication tokens based on technical capabilities.
For example:
Cookie attributes such as Secure, HttpOnly, and SameSite
can be utilized\u2014depending on the specific architecture\u2014to mitigate risks associated with:
Script-based cookie access;
Cross-site requests;
Unencrypted transmission.
Specific technical configurations should be implemented by the platform’s security team in accordance with the system architecture. 18. User Privacy and Cookies
Cookie-related data that can identify a user when combined with user accounts or other information may constitute personal information.
Such processing shall also comply with the *ATLAS Privacy Policy*.
Users may address inquiries regarding cookies and data processing through the designated privacy contact channels.<\/p>\n

18. Policy Updates<\/h4>\n

ATLAS may update this Cookie Policy due to:
technical adjustments;
the launch of new features;
changes in third-party services; or
changes in laws and regulations.
Users will be notified of significant changes via appropriate means in accordance with applicable laws.<\/p>\n

19. Contact Us<\/h4>\n

If you have any questions regarding the use of cookies, please contact us through official channels.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

Legal Information ATLAS Cookie Policy This Cookie Policy explains how ATLAS uses cookies, local storage, and similar technologies when users access its websites, web applications, and other online services, as well as how users can manage the relevant settings.This policy should be read in conjunction with the ATLAS User Agreement, the ATLAS Privacy Policy, and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-6440","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/pages\/6440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/comments?post=6440"}],"version-history":[{"count":23,"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/pages\/6440\/revisions"}],"predecessor-version":[{"id":7301,"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/pages\/6440\/revisions\/7301"}],"wp:attachment":[{"href":"https:\/\/atlascei.com\/de\/wp-json\/wp\/v2\/media?parent=6440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}